Nexus Kernel | SM8250 Channel pinned «Weird Changelog: - Rebased kernel (Based on latest Lineage qcom sm8250) - Merged cip124 - KernelSU Next latest -Unicode support (No sdcard support) - LTO build (Pabagi gaming 120 fps) - A16 support - Fixed ramdisk failure»

Channel
Nexus Kernel | SM8250 Channel
@NexusKernelSm8250Channel
On this record: Also posting the same content · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
641subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001722507998 |
|---|---|
| Type | Channel |
| Username | @NexusKernelSm8250Channel |
| Created | Between 1 December 2021 and 30 April 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 | 3 |
| Confirmed unchanged | 2 times, most recently 13 August 2026 |
| On Telegram | t.me/NexusKernelSm8250Channel |
Also posting the same content
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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 21:32 | 641 | +1 |
| 6 Aug 2026, 17:31 | 640 | no change |
| 6 Aug 2026, 13:06 | 640 | first reading |
Engagement
16 posts held, back to 30 May 2024 — 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 pageof 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 16 posts for this entry, the most recent from 6 October 2025. An engagement rate over an empty window would be a number about nothing.
Reaction mix
318 reactions across 11 posts, in 14 distinct kinds. The most used accounts for 50.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 160 | 50.3% | |
| 👍 | 53 | 16.7% | |
| 🔥 | 33 | 10.4% | |
| 🫡 | 25 | 7.86% | |
| 😁 | 15 | 4.72% | |
| ❤🔥 | 14 | 4.40% | |
| 😭 | 5 | 1.57% | |
| 🤣 | 4 | 1.26% | |
| 🗿 | 3 | 0.943% | |
| 👏 | 2 | 0.629% | |
| 🌚 | 1 | 0.314% | |
| 👎 | 1 | 0.314% | |
| 👨💻 | 1 | 0.314% | |
| 🥰 | 1 | 0.314% |
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 11 of the 16 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 318reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 16 most recent posts we hold, published 30 May 2024 to 6 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
Weird Changelog: - Rebased kernel (Based on latest Lineage qcom sm8250) - Merged cip124 - KernelSU Next latest -Unicode support (No sdcard support) - LTO build (Pabagi gaming 120 fps) - A16 support - Fixed ramdisk failure
😁4❤3🔥2
Build took : 11 minute(s) and 51 second(s) | For Poco F3 (alioth) | Android (13174946, +pgo, +bolt, +lto, +mlgo, based on r547379) clang version 20.0.0 | MD5 Checksum : 1b11a39742870dd34812f2b98af62c6d
❤3🔥3❤🔥2👎1
Nexus Kernel | SM8250 Channel pinned «Changelog: - Fixed apollo gcam - Added Polly optimizations - Improved CASS - Use O3 optimizations to clang - Picked more scheduler changes from mainline - Reduced scheduler latency Things to test: - Memory - Battery - Stability - Performance - Smoothness»
Changelog: - Fixed apollo gcam - Added Polly optimizations - Improved CASS - Use O3 optimizations to clang - Picked more scheduler changes from mainline - Reduced scheduler latency Things to test: - Memory - Battery - Stability - Performance - Smoothness
👍10❤3❤🔥1😁1
Build took : 5 minute(s) and 32 second(s) | For Poco F3 (alioth) | Android (12806354, +pgo, +bolt, +lto, +mlgo, based on r547379) clang version 20.0.0 | MD5 Checksum : 2f71b7a10701bb7336cee0a06257e136
❤4👍3🔥2
Nexus Kernel | SM8250 Channel pinned «Changelog: - New base new life - Implemented MGLRU - Added CASS support - LZ4 (v1.9.4) Zram compression - Built with Aosp clang 20 - Kernel SU Next is present - Increased scheduler performance and latency Things to test: - Memory - Battery - Stability -…»
Build took : 3 minute(s) and 22 second(s) | For Poco F3 (alioth) | Android (12806354, +pgo, +bolt, +lto, +mlgo, based on r547379) clang version 20.0.0 | MD5 Checksum : bebc916352b77847ef7fc14b1372b5af
❤7👍3🔥1😁1
Changelog: - New base new life - Implemented MGLRU - Added CASS support - LZ4 (v1.9.4) Zram compression - Built with Aosp clang 20 - Kernel SU Next is present - Increased scheduler performance and latency Things to test: - Memory - Battery - Stability - Performance
❤🔥10
Not an end? 👀 Happy new year everyone! 🥳
🔥18❤2👍2👏1🥰1
Nexus Kernel | SM8250 Channel pinned «As many of you may have noticed, the Nexus kernel hasn't received updates lately due to my lack of time. Recently, I started a full-time job during my school holidays. After the holidays ended, I had to juggle both work and studies, leaving me with very little…»
As many of you may have noticed, the Nexus kernel hasn't received updates lately due to my lack of time. Recently, I started a full-time job during my school holidays. After the holidays ended, I had to juggle both work and studies, leaving me with very little time to dedicate to Nexus. Currently, my mother has undergone spinal surgery and is unable to perform daily tasks, so I need to take care of her. Thus, I re…
❤56🫡17👍9😭5❤🔥1
Showing the 12 most recent of 16 posts we hold for @NexusKernelSm8250Channel. 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
Citation-graph rank — 326,014 of 1,480,688entries 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.
Forward network
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.
Mentions
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.
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.
Cite this entry
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Nexus Kernel | SM8250 Channel” (@NexusKernelSm8250Channel), 641 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/NexusKernelSm8250Channel.
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.