Sorry for my mistake, Files have been re-uploaded, also updated the link in the previous post Also for KSUN kernel please use 3.3 KSUN apk Thanks for understanding 🙏
❤1

Channel
@NotDheeraj06_Updates
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
307subscribers
+58 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002486697418 |
|---|---|
| Type | Channel |
| Username | @NotDheeraj06_Updates |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/NotDheeraj06_Updates |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 12:59 | 307 | +14 |
| 31 Aug 2026, 04:35 | 293 | +9 |
| 25 Aug 2026, 02:46 | 284 | +30 |
| 16 Aug 2026, 17:05 | 254 | +5 |
| 8 Aug 2026, 21:15 | 249 | no change |
| 8 Aug 2026, 21:02 | 249 | first reading |
20 posts held, back to 15 June 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 1 page of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
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.
218 reactions across 15 posts, in 14 distinct kinds. The most used accounts for 52.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 115 | 52.8% | |
| 🔥 | 53 | 24.3% | |
| 👏 | 12 | 5.50% | |
| 💔 | 9 | 4.13% | |
| 👍 | 7 | 3.21% | |
| 😨 | 7 | 3.21% | |
| 🤯 | 5 | 2.29% | |
| 🍌 | 2 | 0.917% | |
| 😭 | 2 | 0.917% | |
| 🥰 | 2 | 0.917% | |
| ❤🔥 | 1 | 0.459% | |
| 😁 | 1 | 0.459% | |
| 😢 | 1 | 0.459% | |
| 🤣 | 1 | 0.459% |
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 15 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 218 reactions 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 15 June 2026 to 6 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.
Sorry for my mistake, Files have been re-uploaded, also updated the link in the previous post Also for KSUN kernel please use 3.3 KSUN apk Thanks for understanding 🙏
❤1
If you are facing slow charging in InfinityX beryllium, please flash this kernel https://t.me/NotDheeraj06_Builds/88972?single Please let me know if you are facing any issues. Thanks for understanding 🙏
❤4
NotDheeraj06 Updates pinned a photo
#ROM #Beryllium #InfinityX #BKA #OFFICIAL #QPR2 #k4.19 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: POCO F1 - Beryllium Updated: 04/08/'26 ▪️Download ▪️Recovery ▪️Screenshots ▪️Flash Guide ▪️Support Notes: • This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 • Changelogs: Device | Source • Android 16 QPR2 Build • Vanilla Users Please Read this: Here • Kernel 4…
❤8🔥3
#ROM #InfinityX #BKA #OFFICIAL #QPR2 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: Motorola Edge 30 - Dubai Released: 02/08/2026 ▪️Downloads: ROM | Recovery ▪️Screenshots ▪️Support group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • For play integrity, read this: Click here • Gapps and Vanilla Builds Included • For K…
🔥2❤🔥1🤯1
There is something important that I need to share, from now on My Poco F1 Trees (4.19 based) are private, as much as I like Open Source Trees, it's really hard for me to make my trees private just to be safe from kangers 💔, I will try to forget what happened yesterday and move on. If new builders need to use my trees they can contact me directly I will provide them with the trees. Thanks for Understanding 🙏
❤27👍7🥰2🍌1😢1
https://t.me/jiro007/97 Bro don't even know what a kanged commit is, and sends this as a proof that I kang commits lol, learn what a kanged commit is and then talk
https://github.com/LineageOS/android_device_motorola_rtwo/commit/a4818c8d23bb58ccfffbb3becce9aa364725a231 https://github.com/KT-beryllium/android_device_xiaomi_beryllium-419/commit/3fd9b6467b52e8fdf29ff4e25bd9edbea6089fee He (Bugjiro688) is back at it again kanging commits and he thinks i don't notice what he is doing, This is not the first time he has done this, not only that, he picked all my common tree commits …
💔9🍌1🔥1
#ROM #InfinityX #BKA #OFFICIAL #QPR2 #k4.19 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: POCO F1 - Beryllium Released: 12/07/2026 ▪️Download: ROM | Recovery ▪️Screenshots ▪️Flash Guide ▪️Support Group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • Android 16 QPR2 Build • Kernel 4.19 Based • Dynamic Partitions • You c…
🔥14❤4👏4
#ROM #InfinityX #BKA #OFFICIAL #QPR2 #EOL Project Infinity X | v3.12 | OFFICIAL | Android 16 | EOL Device: Motorola Edge 30 - Dubai Released: 11/07/2026 ▪️Downloads: ROM | Recovery ▪️Screenshots ▪️Support group This will be the Final Android 16 Build, Next InfinityX Update will be Android 17 Notes: • Changelogs: Device | Source • For play integrity, read this: Click here • Gapps and Vanilla Builds Included • For K…
❤1😁1😭1
LineageOS website now has flash tools for fastboot and adb! One improvement it has over Google Platform Tools is sideloading percentage actually goes up to 100% instead of that weird 47% we are used to seeing heh 👍 https://download.lineageos.org/flash/adb
❤7🔥1
#Motorola #Dubai #Test Exciting new test build for Motorola Edge 30 - Dubai is up! This Contains fix for Audio distortion at above 75% volume, Dolby Changes, removed FP Changes from previous test build. report the bugs, if any Note: You Can dirty flash over latest official release Downloads: ROM: Here ROM Recovery: Can use official recovery
Showing the 12 most recent of 20 posts we hold for @NotDheeraj06_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.
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 1 registered channel — 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.
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.
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.
“NotDheeraj06 Updates” (@NotDheeraj06_Updates), 307 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/NotDheeraj06_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.