New crDroid update for Xiaomi MI9 🔖 Codename: cepheus 📱 crDroid version: 12.8 📅 Build date: 20260316 ✅ MD5: B481AECDB865BCC9A26073217A28E46F 🧑💻 Maintainer: raystef66
❤14🔥2
Signed Berkay

Channel
@cepheus_updates
On this record: Topic · Observations · Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
1,842subscribers
+6 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001461086537 |
|---|---|
| Type | Channel |
| Username | @cepheus_updates |
| Created | Between 1 April 2019 and 31 August 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/cepheus_updates |
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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
Posts published here appear word for word on 1 other registered channel. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @cepheus_updates/558 · this entry12 Dec 2025, 11:21 UTC | @Mi9updates/93012 Dec 2025, 13:51 UTC | 1.00 | 2.5 hours |
| @Mi9updates/94316 Mar 2026, 18:26 UTC | @cepheus_updates/573 · this entry16 Mar 2026, 20:09 UTC | 1.00 | 1.7 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @Mi9updates | 9 (8/8 hand-verifiable sample passed) | 0.99 | 1.7 hours | this entry (5–4) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 4 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.
“Published first” means first in this corpus. We hold 20 comparable posts for this entry, running 18 October 2025 to 16 March 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Across the whole group of 2, the earliest publisher we hold is @cepheus_updates — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_mutual, last confirmed 7 August 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.
This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 05:11 | 1,842 | +4 |
| 7 Aug 2026, 14:04 | 1,838 | +2 |
| 6 Aug 2026, 14:17 | 1,836 | first reading |
20 posts held, back to 18 October 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 16 March 2026. An engagement rate over an empty window would be a number about nothing.
243 reactions across 20 posts, in 10 distinct kinds. The most used accounts for 43.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 105 | 43.2% | |
| 🔥 | 81 | 33.3% | |
| 👏 | 16 | 6.58% | |
| 😱 | 15 | 6.17% | |
| 👎 | 12 | 4.94% | |
| 👍 | 8 | 3.29% | |
| 🤯 | 2 | 0.823% | |
| 🥰 | 2 | 0.823% | |
| 😁 | 1 | 0.412% | |
| 🤔 | 1 | 0.412% |
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 20 of the 20 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 243reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 18 October 2025 to 16 March 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.
New crDroid update for Xiaomi MI9 🔖 Codename: cepheus 📱 crDroid version: 12.8 📅 Build date: 20260316 ✅ MD5: B481AECDB865BCC9A26073217A28E46F 🧑💻 Maintainer: raystef66
❤14🔥2
Signed Berkay
💥 crDroid 12.8 — 16.03 build 💥 ENJOY https://xdaforums.com/t/rom-16-0-official-cepheus-retrofit-crdroid-v12-8-16-03-2026.4758108/post-90523835
❤5🔥3
Signed Berkay
HyperOS 3.0.304.0.WFACNXM | Android 16 | CN Thanks to Xirudly🙌 Changelog: •Follow Xiaomi 17 OS3.0.304.0.WPCCNXM update •Update ReSukiSU to the latest version Bug (for reference only): •DC dimming, color adjustment, eye protection mode •Delay in turning on the screen shortly after turning off the screen Notes: •To use the camera portrait mode, you need to first turn off the dual camera function in the camera setting…
❤7🥰2👍1
Signed Berkay
HyperOS 2.0.16.0.UFACNXM | Android 14 | CN Thanks to Xirudly🙌 Changelog: •Based on Xiaomi 11 LE OS2.0.16.0.UKOCNXM port •Update ReSukiSU to the latest version •Correct the model display in My device - Certification •Remove AI key function •Fix jagged edges around the screen Recovery instructions: •Device tree source code adaptation for Xiaomi 9 based on @Helium_Studio, merging dynamic and static partition support •B…
❤3🤔1😁1
Signed Berkay
#EvolutionX 11.6.2 | 2026/03/09 For Xiaomi Mi 9 Android version: 16 Evolution X Version: 11.6.2 Filename: EvolutionX-16.0-20260307-cepheus-11.6.2-Official Changelogs: Xiaomi Mi 9 Changelog Downloads: Download ROM | Download Recovery Instructions / Website: Evolution X cepheus XDA Forum: Watch cepheus on XDA Want to support Evolution X? Evolution X on OpenCollective #KeepEvolving #Android16 #bka #Xiaomi #cepheu…
🔥9👎6❤1
Signed Berkay
HyperOS 3.0.301.0.WFACNXM | Android 16 | CN Thanks to Xirudly🙌 Changelog: •Follow Xiaomi 17 OS3.0.301.0.WPCCNXM update •Synchronize OS2.0.216.4 kernel updates •Remove the unsupported 80211.ax from the hotspot •Correct the model display in My device - Certification and add support for dark mode •Complete the super macro and gesture photography functions in the camera •Fix inability to connect to WiFi that requires aut…
❤17
Signed Berkay
HyperOS 2.0.216.4.VFACNXM | Android 15 | CN Thanks to Xirudly🙌 Changelog: •Re-merge the latest v4.14.356-openela source code •Update ReSukiSU and KernelSU-Next to the latest version •Fix some issues with Bluetooth (such as LDAC not being available before) •Remove AI key function •Remove full screen AOD to fix the issue of hide notch failing •Remove the unsupported 80211.ax from the hotspot •Correct the model display …
❤13
Signed Berkay
HyperOS 3.0.300.9.WFACNXM | Android 16 | CN Thanks to Xirudly🙌 Changelog: •Base on Xiaomi 17 OS3.0.300.9.WPCCNXM •Some bug fixes (thanks to @KameYuki, @雪糕小豪, @Ambassador_SM8450 for their help) Bug (short testing time, for reference only): •DC dimming, color adjustment, eye protection mode •Screen delay within 3 seconds after turning off the screen Notes: •To use the camera portrait mode, you need to first turn off …
🔥20❤5🤯2
Signed Berkay
New crDroid update for Xiaomi MI9 🔖 Codename: cepheus 📱 crDroid version: 12.7 📅 Build date: 20260221 ✅ MD5: F96EE888FC588ACD70902E9A04EEB7B6 🧑💻 Maintainer: raystef66
🔥7❤1
Signed Berkay
💥 crDroid 12.7 — 21.02 build 💥 ENJOY https://xdaforums.com/t/rom-16-0-official-cepheus-retrofit-crdroid-v12-7-21-02-2026.4758108/post-90495140
🔥10
Signed Berkay
LineageOS 23.2 QPR2 (unofficial) for Mi 9 📅 Build date: 2026-02-15 🛡️Security patch:2026-02-01 🗒Changelog 👨💻Maintainer Download - Github
🔥5❤1👍1
Signed Berkay
HyperOS 2.0.216.2.VFACNXM | Android 15 | CN -Thanks to Xirudly 🙌 Changelog: •Update ReSukiSU and KernelSU-Next to the latest version •Backport the BPF of 5.10 and enable CONFIG_XDP_SOCKETS to prepare for Android 16 •Fix the issue of infrared sensor failure •Using another method to fix bluetooth silence issue (based on @KameYuki 's suggestion) •Free themes and widgets (From @我们的天空sky) •Fix the issue of not being able …
😱3
Signed Berkay
Showing the 12 most recent of 20 posts we hold for @cepheus_updates. 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.
Citation-graph rank — 728,039 of 1,151,006entries 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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@cepheus_updates named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Mi 9 | Updates” (@cepheus_updates), 1,842 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/cepheus_updates.
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.