Example
🥰15❤2

Channel
@installerx_revived
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Polls · Citations · Cite this entry
11,035subscribers
+720 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002818740200 |
|---|---|
| Type | Channel |
| Username | @installerx_revived |
| Created | Between 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 29 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/installerx_revived |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 19 August 2026 and assigned it the closest of 31 fixed categories, at 79% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
8,490 average views per post against 11,035 subscribers — an engagement rate of 76.9%. Across the 2,556 registered channels in the same cohort — 10,020–31,610 subscribers, posting mainly in Chinese — the middle half sit between 1.62% and 9.31%, with a median of 3.99%.
| Window | 30 days (11 August 2026 – 10 September 2026) |
|---|---|
| Posts measured | 18 of 18 published in the window (0 exact, 18 rounded by Telegram) |
| Views totalled | 152,740 |
| Mature posts only | 76.9% over 18 posts read at least 24h after publication |
| Subscribers | 11,035 measured 8 September 2026 |
| Cohort | b10000:zho · 2,556 channels · p10 0.492% · p25 1.62% · p50 3.99% · p75 9.31% · p90 20.0% |
| Position in cohort | 99.413th percentile · 19.3× the cohort median |
| Uncertainty | ±0.264% of the figure, from Telegram’s rounding |
| Post language | Chinese · 75.0% of the window’s posts |
When this is recorded. A channel is listed here only when its engagement rate sits at or above the 99th percentile of its cohort and is at least 3× away from that cohort’s median — above it — on both the all-readings figure and the mature-only figure. The percentile alone would be circular: a percentile cut puts the same share of every cohort in the tail whatever the data looks like. The distance from the median is what makes it a statement about this channel.
This is not a verdict, and the direction is not a quality signal. A low rate has many innocent causes — audiences that read in the Telegram app without opening the channel, a subscriber base built long before the current output, an audience in a different timezone from our reading. A high rate has innocent causes too: a post that travelled far beyond the channel’s own subscribers will do it. We publish the measurement and the distribution it sits in. The full cohort baselines are downloadable, so this comparison can be reproduced rather than trusted.
Recorded under the key err_high, last confirmed 10 September 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 22:38 | 11,035 | +46 |
| 5 Sept 2026, 14:19 | 10,989 | +42 |
| 3 Sept 2026, 16:00 | 10,947 | +29 |
| 2 Sept 2026, 09:43 | 10,918 | +19 |
| 1 Sept 2026, 11:55 | 10,899 | +13 |
| 31 Aug 2026, 12:07 | 10,886 | +30 |
| 30 Aug 2026, 14:04 | 10,856 | +23 |
| 29 Aug 2026, 16:12 | 10,833 | +22 |
| 28 Aug 2026, 17:52 | 10,811 | +23 |
| 27 Aug 2026, 17:07 | 10,788 | +29 |
| 26 Aug 2026, 17:55 | 10,759 | +15 |
| 25 Aug 2026, 19:35 | 10,744 | +27 |
| 24 Aug 2026, 16:09 | 10,717 | +28 |
| 23 Aug 2026, 03:46 | 10,689 | +27 |
| 21 Aug 2026, 12:38 | 10,662 | +23 |
| 20 Aug 2026, 15:02 | 10,639 | +17 |
| 19 Aug 2026, 13:43 | 10,622 | +17 |
| 18 Aug 2026, 14:16 | 10,605 | +27 |
| 17 Aug 2026, 12:37 | 10,578 | +47 |
| 16 Aug 2026, 04:38 | 10,531 | first reading |
37 posts held, back to 19 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 40 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 31 August 2026 |
|---|---|
| Posts held | 37 (19 July 2026 – 31 August 2026) |
| Views total | 152,740 |
| Reactions total | 1,974 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:32 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
5,910 reactions across 37 posts, in 38 distinct kinds. The most used accounts for 24.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 1,437 | 24.3% | |
| 👍 | 829 | 14.0% | |
| 😭 | 744 | 12.6% | |
| ❤ | 449 | 7.60% | |
| 💯 | 449 | 7.60% | |
| 👌 | 387 | 6.55% | |
| 🤩 | 245 | 4.15% | |
| 🎉 | 201 | 3.40% | |
| ❤🔥 | 200 | 3.38% | |
| 🔥 | 193 | 3.27% | |
| 😱 | 152 | 2.57% | |
| 😁 | 136 | 2.30% | |
| 🌚 | 110 | 1.86% | |
| 🤔 | 92 | 1.56% | |
| 👏 | 70 | 1.18% | |
| 🤯 | 29 | 0.491% | |
| 🫡 | 28 | 0.474% | |
| 🌭 | 25 | 0.423% | |
| 🤡 | 24 | 0.406% | |
| 😡 | 20 | 0.338% | |
| 18 further kinds | 90 | 1.52% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 37 of the 37 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 5,910 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 37 most recent posts we hold, published 19 July 2026 to 31 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @installerx_revived. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 37 most recent posts we hold for this entry, published 19 July 2026 to 31 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Example
🥰15❤2
Support signature analysis of this apk, Android 17+ is required. Also, V3.2 signature analysis is availvable on Android17+.
🥰22❤3
File, posted without a caption
❤42🥰14👏1
清理AndroidManifest中的无用标签 安装历史支持禁用 Android17自更新完成被systemui恢复后,也会记录这次更新的历史 更新了很多依赖 更新翻译 Cleaned up unused tags in AndroidManifest Added support for disabling installation history On Android 17, self-updates restored by SystemUI after completion will now also be recorded in installation history Updated many dependencies Updated translations
🔥89🥰18❤11👏7👍4
大杂烩了 这该死的可维护性
🥰68🌚13❤3🤡3😁3
zn部分由lsposed负责,因此模块侧无需再安装zn模块 更新日志见 https://github.com/wxxsfxyzm/MiuiBackGestureHook/releases/tag/0.11.3 用不了的可能需要等下一个zygisk next更新
❤40😱4👍1
https://github.com/wxxsfxyzm/MiuiBackGestureHook/releases/tag/0.10.2 妙妙魔法时间: 现在(理论上)自动支持所有OS4,53xx以及往后的所有桌面(只要小米不大改),native hook也无需手动提取偏移,开箱即用 lsp模块主页可以检测和zn的通信状态 (自己写的,之后会迁移到官方API) 支持修改 CrossTask 动画为 OneUI 样式 支持启用 Google 圈定即搜 支持启用 Google 圈定即搜中的实时翻译 修复了很多问题 以上内容仅在 OS4 Xiaomi 17 ProMax / Xiaomi 17 Ultra 上测试过 OS3完全未测试,也不打算维护了,有问题的话自己PR吧
👍59❤16🥰7🔥2🤔1
下半年开始,我会开始硕士学业,因此花在业余爱好上的精力将会大幅减少。在这个月以内,InstallerX Revived会发布今年最后一个稳定版本,新功能请求的处理将会暂缓。 这不是停更,prerelease/频道更新将继续,只是频率可能会变低。与此同时,鼓励任何形式的pull request,这对我,对这个项目的帮助都很大。 Starting in the second half of this year, I will begin my master's studies, so the amount of time and energy I can spend on my hobbies will be significantly reduced. Within this month, InstallerX Revived will release its final stable version of the year,…
🥰400👍97🫡28😭21❤11💯8👏6😱6
同时支持4371和5334桌面 引入了一种类似Ghostlock的偏移提取机制,只要有桌面的偏移就能(大概)生成新的profile使用,之后不会频繁发包,有需要的可以自行适配偏移 OS3用户仍然建议更新,只装apk即可 OS4的LSP作用域不需要勾选桌面(勾了也没啥事) 不能隐藏手势提示线! edit: 仅在17pm上通过测试,17pro反馈有效,其他机器汇报无效,我没设备,鼓励进一步开发并pr给我 edit2:收到了PR,现在k90应该可以使用,欢迎更多pr
👍47❤8🥰3⚡1🔥1🤔1
仅支持桌面版本 8.01.02.4371 请先安装Zygisk Next 和 LSPosed API 102 模块有风险,刷入需谨慎 https://github.com/wxxsfxyzm/MiuiBackGestureHook/tree/OS4 希望能为Rust应用的hook提供一些参考 TYPE_RETURN_TO_HOME没写,这个超出我的能力了
🥰36❤5🤯5👍3⚡1🎉1🔥1
已经在 HyperOS 4 成功 Hook Rust+Flutter 桌面并修复预测返回 实话说没啥难度,因为小米这个rust基本就是对着java版本“翻译”一遍,懂的都懂,没啥新意
🥰109🎉14❤7
Got Android 17 today so here comes the sample! Update your Android OS to 17 to see the effect !
👍58❤9🥰2🎉1
Showing the 12 most recent of 37 posts we hold for @installerx_revived. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@installerx_revived edited 2 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
online和offline合并为一个
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 37 most recent posts we hold, published 19 July 2026 to 31 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 2 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 8 September 2026 — this entry's latest reading, not the date you are reading this.
“InstallerX Revived” (@installerx_revived), 11,035 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/installerx_revived.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.