31 Jan 2026, 21:06 UTC627 viewsread 9 August 2026
File
https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/05d7efe3760042617864be1ae45143c7307491dc
Channel
LeanCore Kernel 发布
@LeanCoreKernel
On this record: Growth · Engagement · Posts · Citations · Cite this entry
121subscribers
+2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003343927457 |
|---|---|
| Type | Channel |
| Username | @LeanCoreKernel |
| Created | Between 1 November 2025 and 29 December 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/LeanCoreKernel |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 04:07 | 121 | +1 |
| 15 Aug 2026, 19:17 | 120 | +1 |
| 9 Aug 2026, 04:31 | 119 | no change |
| 7 Aug 2026, 18:13 | 119 | first reading |
Engagement
20 posts held, back to 29 December 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 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 20 posts for this entry, the most recent from 31 January 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
31 Jan 2026, 01:38 UTC516 viewsread 9 August 2026
File
Enable and default iosched bfq for gayming https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/9746202a68fec5b0b05324bd349d6781a45fedd8
30 Jan 2026, 17:15 UTC523 viewsread 9 August 2026
Bore en hyperos causa congelación en miui no tuve ese problema
30 Jan 2026, 06:27 UTC511 viewsread 9 August 2026
File
https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/4e2062ec39606d515a4c8f967c52fcc87c0da0f2
20 Jan 2026, 16:33 UTC538 viewsread 9 August 2026
File
kgsl: Drop WQ_UNBOUND - Enable WQ_HIGHPRI fs/f2fs: drop WQ_UNBOUND sched: 8 pelt https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/af85c714e098b0f5d95f0831c3d0fa3bd5487b98
19 Jan 2026, 07:52 UTC424 viewsread 9 August 2026
File
https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/4f9e168cf2b2f9891aa6d229945384a848a41133
19 Jan 2026, 07:50 UTC385 viewsread 9 August 2026
Y también usar A-soul Games Optimization Plus en mode=2
19 Jan 2026, 00:36 UTC366 viewsread 9 August 2026
Si desea FPS estables para jugar use @scene2023 o FeasHelper (si su dispositivo es Marble úselo con Feas4Marble)
18 Jan 2026, 21:17 UTC350 viewsread 9 August 2026
Next update Delete iosched ssg Delete mglru TickTimes 100hz less is more
16 Jan 2026, 22:29 UTC351 viewsread 9 August 2026
File
https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/d72e20b4687b9c230cfb04bfe60aa63276cb2f1e
16 Jan 2026, 16:25 UTC323 viewsread 9 August 2026
Photo
🥵🥵🥵🥵
16 Jan 2026, 07:05 UTC282 viewsread 9 August 2026
File
https://github.com/LeanxModulostk/android_kernel_xiaomi_common/tree/1179ccb19cbd96f9790510e5771e5b1a69888db4
Showing the 12 most recent of 20 posts we hold for @LeanCoreKernel. 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 — 211,153 of 1,627,068entries 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.
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
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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“LeanCore Kernel 发布” (@LeanCoreKernel), 121 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/LeanCoreKernel.
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.