KernelSU Next
A Kernel-based root solution for Android devices. (Next experimental branch) https://github.com/KernelSU-Next/KernelSU-Next https://kernelsu-next.github.io/webpage/ Come join the discussions! https://t.me/ksunext_community
Show more📈 Analytical overview of Telegram channel KernelSU Next
Channel KernelSU Next (@ksunext) in the English language segment is an active participant. Currently, the community unites 23 736 subscribers, ranking 5 678 in the Technologies & Applications category.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 23 736 subscribers.
According to the latest data from 15 October, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by 1 865 over the last 30 days and by 551 over the last 24 hours, overall reach remains high.
- Verification status: Not verified
- Engagement rate (ER): The average audience engagement rate is 44.56%. Within the first 24 hours after publication, content typically collects 18.87% reactions from the total number of subscribers.
- Post reach: On average, each post receives 10 355 views. Within the first day, a publication typically gains 4 386 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 79.
- Thematic interests: Content is focused on key topics such as kernel, ksun, branch, lkm, dev.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“A Kernel-based root solution for Android devices. (Next experimental branch)
https://github.com/KernelSU-Next/KernelSU-Next
https://kernelsu-next.github.io/webpage/
Come join the discussions!
https://t.me/ksunext_community”
Thanks to the high frequency of updates (latest data received on 16 October, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
Loading data
| Date | Subscriber Growth | Mentions | Channels | |
| 16 October | +498 | |||
| 15 October | +551 | |||
| 14 October | +153 | |||
| 13 October | +181 | |||
| 12 October | +119 | |||
| 11 October | +225 | |||
| 10 October | +64 | |||
| 09 October | +41 | |||
| 08 October | +30 | |||
| 07 October | +26 | |||
| 06 October | +35 | |||
| 05 October | +18 | |||
| 04 October | +43 | |||
| 03 October | +35 | |||
| 02 October | +14 | |||
| 01 October | +26 |
| 2 | Susfs lkm support for x86_64 (emulator, avd, waydroid)
Its a beta build, arm64 and x86_64 users should test both architectures to find any issues | 1 675 |
| 3 | Handy feature to have | 6 125 |
| 4 | Well if you get annoyed | 4 703 |
| 5 | I lied soft reboot works 😂 | 5 542 |
| 6 | Oh btw those who uses soft reboot you will lose strong integrity. You need a normal reboot for now | 5 480 |
| 7 | Avoid them | 5 677 |
| 8 | Only the pixel 10 - 11 props wont give you strong with old hardware attested keyboxes | 6 299 |
| 9 | For those with teesim if you still cant get strong then disbale Tee rkp-only option | 6 125 |
| 10 | TEESimulator-v4.0-73-03842dd-Release.zip | 6 748 |
| 11 | Tee simulator works too | 6 352 |
| 12 | No text... | 6 612 |
| 13 | +1 Tricky-Store-OSS-v3.1.0-199-dda5277-Release.zip | 7 775 |
| 14 | Fix 2
Tricky store oss (latest ci) with old hardware attested keybox
Play integrity fix/fork (latest ci) with pixel 6/6a props | 12 458 |
| 15 | So for my understanding, if a device doesn't have RKP like an old non-RKP device, unlocking bootloader means you will have to use a RKP based keybox 😂 until there is a solution to keep using old hardware keyboxes, there should be a solution cuz old phones won't suddenly lose strong integrity even if it's not unlocked. | 6 413 |
| 16 | Solution!
RKP keybox with the latest CI of Play integrity Fork = strong yet again.
Good luck getting RKP keyboxes 😂 | 8 776 |
| 17 | Basic even with my RKP keybox 😂 | 5 767 |
| 18 | Hardware key attestation = Bad | 5 915 |
| 19 | Remote key attestation = good | 5 885 |
| 20 | Unlocked bootloader with RKP disabled to do hardware attestation you cant pass strong the usual way anymore.
Keyboxes are not a problem, neither is fingerprint, google is enforcing RKP and also added new detections to droid guard to stop you from getting strong on a unlocked bootloader. | 6 890 |
