https://kernelsu.org/guide/module-config.html

Channel
KernelSU
@KernelSU
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
61,415subscribers
+3,287 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
Register entry
| Telegram ID | -1001854258679 |
|---|---|
| Type | Channel |
| Username | @KernelSU |
| Created | Between 1 October 2022 and 31 August 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 19 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 19 September 2026 |
| On Telegram | t.me/KernelSU |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 9 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 19 Sept 2026, 05:00 | 61,415 | +178 |
| 16 Sept 2026, 17:59 | 61,237 | +171 |
| 14 Sept 2026, 18:38 | 61,066 | +98 |
| 13 Sept 2026, 06:21 | 60,968 | +132 |
| 11 Sept 2026, 11:57 | 60,836 | +156 |
| 8 Sept 2026, 17:16 | 60,680 | +234 |
| 5 Sept 2026, 08:59 | 60,446 | +94 |
| 3 Sept 2026, 09:43 | 60,352 | +68 |
| 2 Sept 2026, 04:52 | 60,284 | +45 |
| 1 Sept 2026, 06:04 | 60,239 | +62 |
| 31 Aug 2026, 03:24 | 60,177 | +95 |
| 30 Aug 2026, 03:29 | 60,082 | +199 |
| 29 Aug 2026, 02:44 | 59,883 | +115 |
| 28 Aug 2026, 04:56 | 59,768 | +115 |
| 27 Aug 2026, 02:26 | 59,653 | +57 |
| 26 Aug 2026, 00:56 | 59,596 | +55 |
| 25 Aug 2026, 03:13 | 59,541 | +60 |
| 23 Aug 2026, 22:17 | 59,481 | +149 |
| 22 Aug 2026, 07:27 | 59,332 | +81 |
| 20 Aug 2026, 18:52 | 59,251 | first reading |
Engagement
20 posts held, back to 31 August 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 89 pages 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 22 November 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 5s
- Average length
- 5s
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.
Recent posts
https://kernelsu.org/guide/metamodule.html
KernelSU provides systemless modification of the system through overlayfs, but this feature has become a major and fragile detection point, with many detection methods for KernelSU stemming from it. Therefore, we plan to launch the metamodule feature, which will transfer certain capabilities of the module system to the metamodule. This will maintain the stability and security of KernelSU itself while releasing greate…
https://github.com/tiann/KernelSU/releases/tag/v2.0.0
You can choose to install the KernelSU manager exclusively in Private Space on Android 15 now.
KernelSU has been around for nearly two years and has stabilized, and we plan to move to 1.0 in the future; here are some adjustments: 1. In principle, we only accept Bug Reports and do not accept external Feature Requests; if you want new features, you are welcome to submit a Pull Request. We will still develop new features that we think are interesting/cool, such as sulog, ksufs, webui, etc. 2. Since non-GKI kerne…
If you wish to contribute code to KernelSU, here are some good first issues: - https://github.com/tiann/KernelSU/issues/1664 - https://github.com/tiann/KernelSU/issues/1571 - https://github.com/tiann/KernelSU/issues/1542
The installation guide has been updated, with added instructions for LKM mode: https://kernelsu.org/guide/installation.html#introduction
https://github.com/tiann/KernelSU/releases/tag/v0.9.2 - [manager]: Support offline patching of the kernel. - [kernel]: Fix issue with ColorOS. - [kernel]: Hide traces of LKM in user space. - [manager]: Fix possible errors during OTA upgrades.
KernelSU now supports installation through kernel modules (LKM) (GKI Only), you can use it with official kernels or third-party kernels; at the same time, the manager has also added installation functionality, you can choose to patch files, install directly, or install after OTA. Regarding the new LKM installation method, there are some tips: 1. LKM does not support non-GKI kernels, and will not support them in the …
https://github.com/tiann/KernelSU/releases/tag/v0.8.1 And the webui docs
KernelSU version 0.8.0 use sparse image to storage module files. If you do not wait patiently for the module installation process to end after upgrading (it takes time to migrate the old version to the new version), but forcefully stop the process and then switch to the old version of the manager, then serious problems will occur at this time. Because the old version of the manager cannot handle sparse image, it tre…
Showing the 12 most recent of 20 posts we hold for @KernelSU. 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.
Mentions
Named by 4 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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@APatchChannel · 25,112#1
@KernelSUmodules · 9,859#2
@PifNEXT · 6,713#3
@magiskmodules22 · 12,837#4
@AppManagerChannel · 13,044#5
@Projkt113 · 1,419#6
@LSPatchArchives · 10,296#7
@LSPosed · 193,348#8
@PixelProps · 14,197#9
@reveny1 · 7,454#10
@GappsLeaks · 21,382#11
@PeterSpaceXiaomi · 2,537#12
@apcports2 · 8,778#13
@Projkt113Dumps · 2,191#14
@hyperosfirmware · 23,025#15
@xtrbasement · 1,196#16
@Dmfontss · 373#17
@Gudangtdspya · 4,038#18
@Sakion_Team · 1,958#19
@Exy9810ROMs · 831#20
@N0kernels · 2,934#21
@ctsfixes · 2,423#22
@furbanoramos25_channel · 411#23
@whyred_update · 710#24
@MishaalAndroidNews · 11,819#25
@HyperX_Archive · 406#26
@NHA_projects · 625#27
@Blank_Ports · 615#28
@seal_app · 24,974#29
@SamsungTweaks · 3,166#30
@nfsreleases · 5,179#31
@revanced_extended · 19,623#32
@real5ec1cff · 36,523#33
@magiskalpha · 65,706#34
@nullptr_dev · 19,799#35
@ProjectInfinityX · 27,647#36
@pcsx2_emuator · 843#37
@rezygisk · 3,726#38
@VoyagerMIUIUpdate · 21,457#39
@OxygenPlusKernel · 1,949#40
@cemiuiler_canary · 18,690#41
@wallpaperdepot · 1,405#42
@se_extended_ci · 2,378#43
@Depth_Wallpapers_official · 7,198#44
@BlissROM_Updates · 4,929#45
@projectmatrixx · 5,044#46
@weebo_setup · 983#47
@snapenhance_ci · 7,026#48
@scrape0 · 1,415#49
Read from Telegram’s recommendation API, most recently 14 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@APatchChannel · 25,112
Telegram ranks this channel #1 of 37 here — alongside 36 others — read 14 September 2026
@LSPosedArchives · 25,293
Telegram ranks this channel #15 of 36 here — alongside 35 others — read 14 September 2026
@seal_app · 24,974
Telegram ranks this channel #34 of 45 here — alongside 44 others — read 15 September 2026
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 19 September 2026 — this entry's latest reading, not the date you are reading this.
“KernelSU” (@KernelSU), 61,415 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/KernelSU.
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.