Xiaomi 17 4.0.0.9 Xiaomi 17 Pro 4.0.0.22 Xiaomi 17 Pro Max 4.0.0.20 Xiaomi 17 Ultra 4.0.0.10 REDMI K90 4.0.0.18 REDMI K90 Pro Max 4.0.0.15 Xiaomi Pad 8 4.0.0.23 Xiaomi Pad 8 Pro 4.0.0.24
🎉36👍9❤8🤔1

Channel
@VoyagerMIUIUpdate
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
19,972subscribers
+130 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001718128483 |
|---|---|
| Type | Channel |
| Username | @VoyagerMIUIUpdate |
| Description | MIUI/HyperOS提取&更新推送.请认真看置顶和文件说明 若安装提取版apk后出现问题请卸载更新甚至清除对应apk的全部数据 部分apk对于一些底层和系统版本会产生崩溃甚至导致系统出现黑屏等问题 若是不看注意导致出现了一些严重的后果,频道主概不负责 |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/VoyagerMIUIUpdate |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 14:06 | 19,972 | +20 |
| 12 Aug 2026, 11:24 | 19,952 | +9 |
| 11 Aug 2026, 12:36 | 19,943 | +17 |
| 10 Aug 2026, 13:07 | 19,926 | +31 |
| 9 Aug 2026, 09:51 | 19,895 | +17 |
| 8 Aug 2026, 06:28 | 19,878 | +35 |
| 7 Aug 2026, 07:41 | 19,843 | +1 |
| 6 Aug 2026, 22:46 | 19,842 | first reading |
82 posts held, back to 3 August 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 19 pagesof 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. It is computed over the 77 of 81 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 14 August 2026 |
|---|---|
| Posts held | 82 (3 August 2026 – 14 August 2026) |
| Views total | 173,150 |
| Reactions total | 523 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Aug 2026, 08:06 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.
Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video 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.
523 reactions across 73 posts, in 9 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 200 | 38.2% | |
| 👍 | 189 | 36.1% | |
| 😁 | 46 | 8.80% | |
| 🎉 | 36 | 6.88% | |
| 🥰 | 18 | 3.44% | |
| 😱 | 16 | 3.06% | |
| 🤔 | 14 | 2.68% | |
| 😢 | 2 | 0.382% | |
| 🤩 | 2 | 0.382% |
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 77 of the 82 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 523reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 82 most recent posts we hold, published 3 August 2026 to 14 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.
Xiaomi 17 4.0.0.9 Xiaomi 17 Pro 4.0.0.22 Xiaomi 17 Pro Max 4.0.0.20 Xiaomi 17 Ultra 4.0.0.10 REDMI K90 4.0.0.18 REDMI K90 Pro Max 4.0.0.15 Xiaomi Pad 8 4.0.0.23 Xiaomi Pad 8 Pro 4.0.0.24
🎉36👍9❤8🤔1
Voyager HyperOS Update pinned a file
#小米运动健康 #应用内推送 #Mi_Fitness target api:35 min api:26 arm64-v8a, armeabi-v7a 新增 OS4 widget(小部件) 更新日志: 1、优化分屏及系统小部件适配体验 2、修复已知问题
👍5
REDMI KPad 3.0.308.0
考虑到本身就是基于并给 HyperOS 3 Xiaomi 17 Pro 写的,不少功能和背屏联动很多所以就没怎么考虑正屏 后续会优化一下非背屏用户的体验,并且隐藏背屏的相关联动功能 UI 方面因为想着显示功能健康度,中间改了好几次逻辑,所以不少作用域目前健康度 UI 逻辑可能不统一。我也比较纠结,有建议或者想法也可以提,目前主要是功能优先 显示健康度可以让用户知道目前版本 Hook 到底工作了吗,或者不工作的话哪些炸了,炸了多少 还有什么问题也可以群里或者评论区里面提 还是顺带一提,禁止在国内平台分享和传播本模块
👍8❤4
#全球上网 #Mi_Roaming #商店推送 target api:33 min api:29 arm64-v8a, armeabi-v7a 更新日志: 1. 优化了支付体验 2. 修复了已知问题,提升稳定性
👍1
#小游戏服务 #商店推送 推送机型:#Mi17ProMax #popsicle target api:37 min api:29 arm64-v8a, armeabi-v7a min api:28 -> 29 1.31.5.4(13150401) 更新日志: 1.修复了偶现崩溃问题 2.修复了个人中心展示异常问题
👍1
#小米画报 #商店推送 #Mi_Wallpaper_Carousel target api:35 minapi:28 arm64-v8a, armeabi-v7a, armeabi 25100304-CAROUSEL 更新日志: 部分细节优化
👍1
#小米视频 #Mi_Video #商店推送 target api:33 min api:26 arm64-v8a v2026081390(MiVideo-UN)
👍1
REDMI Pad 2 3.0.307.0 REDMI Pad 2 Pro 3.0.308.0 REDMI Pad 2 Pro 5G 3.0.305.0
❤1
啪,很快啊,WPS Office 就已经适配 HyperOS 4 了(26.8.0)
#KeiMi #HyperOS3 为 HyperOS 补全查找、跨设备互联、锁屏与背屏体验。 - 跨设备通知:扩展 iPhone 与小米、小米与小米之间的通知同步,支持第三方 App、名单与渠道管理、关键词过滤、重复与媒体通知过滤,以及可选的本地同步历史。 - 互联与互传:恢复跨区双向剪贴板,并在妙享桌面连接时自动避让;支持可信设备自动接收、Apple/OPPO 系设备名称补全,以及系统分享面板修复。 - 锁屏与媒体:让锁屏通知与通知中心保持一致;在原生媒体卡、沉浸封面和底部音乐胶囊间切换,支持媒体卡轮播、专辑信息、播放进度与 AOD。 - 系统快捷操作:扩展双击电源键,可执行直接动作或呼出 SystemUI 快捷面板,并支持相机、手电筒、门卡、快捷码及主屏/背屏任务投送。 - 背屏增强:加入左右/上滑快捷操作、App 与 Activity 启动准入、任务投送、音乐 App 扩展、焦点通知、游戏防误触、背屏计算器和快捷码超级岛…
❤35👍6🤩2
Showing the 12 most recent of 82 posts we hold for @VoyagerMIUIUpdate. 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.
@VoyagerMIUIUpdate 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.
Citation-graph rank — 251,508 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“Voyager HyperOS Update” (@VoyagerMIUIUpdate), 19,972 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/VoyagerMIUIUpdate.
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.