ch
Feedback

不要被骗子欺骗!Telemetrio 会找到并标记这些频道 👉 如果想查看标记,请订阅

KernelSU Next

KernelSU Next

前往频道在 Telegram

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

显示更多
未指定国家技术与应用5 678

📈 Telegram 频道 KernelSU Next 的分析概览

频道 KernelSU Next (@ksunext) 英语 语言赛道中的 是活跃参与者。目前社区聚集了 23 736 名订阅者,在 技术与应用 类别中位列第 5 678。

📊 受众指标与增长动态

自 невідомо 创建以来,项目保持高速增长,吸引了 23 736 名订阅者。

根据 15 十月, 2026 的最新数据,频道保持稳定运转。过去 30 天订阅人数变化为 1 865,过去 24 小时变化为 551,整体触达仍然可观。

  • 认证状态: 未认证
  • 互动率 (ER): 平均受众互动率为 44.56%。内容发布后 24 小时内通常能获得 18.87% 的反应,占订阅者总量。
  • 帖子覆盖: 每篇帖子平均可获得 10 355 次浏览,首日通常累积 4 386 次浏览。
  • 互动与反馈: 受众积极参与,单帖平均反应数为 79。
  • 主题关注点: 内容集中在 kernel, ksun, branch, lkm, dev 等核心主题上。

📝 描述与内容策略

作者将该频道定位为表达主观观点的平台:
“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”

凭借高频更新(最新数据采集于 16 十月, 2026),频道始终保持新鲜度与高覆盖。分析显示受众积极互动,使其成为 技术与应用 类别中的关键影响点。

23 736
订阅者
+55124 小时
+1 3297 天
+1 86530 天
帖子存档
Dev Manager Build (Normal) #ci_3392

Commit
Workflow run

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

Handy feature to have
Handy feature to have

Well if you get annoyed
Well if you get annoyed

I lied soft reboot works 😂

Oh btw those who uses soft reboot you will lose strong integrity. You need a normal reboot for now

Avoid them

Only the pixel 10 - 11 props wont give you strong with old hardware attested keyboxes

For those with teesim if you still cant get strong then disbale Tee rkp-only option

TEESimulator-v4.0-73-03842dd-Release.zip16.97 MB

Tee simulator works too

photo content
+3

+1
Tricky-Store-OSS-v3.1.0-199-dda5277-Release.zip1.29 MB

Fix 2 Tricky store oss (latest ci) with old hardware attested keybox Play integrity fix/fork (latest ci) with pixel 6/6a prop
+3
Fix 2 Tricky store oss (latest ci) with old hardware attested keybox Play integrity fix/fork (latest ci) with pixel 6/6a props

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.

Solution! RKP keybox with the latest CI of Play integrity Fork = strong yet again. Good luck getting RKP keyboxes 😂
+2
Solution! RKP keybox with the latest CI of Play integrity Fork = strong yet again. Good luck getting RKP keyboxes 😂

Basic even with my RKP keybox 😂
+3
Basic even with my RKP keybox 😂

Hardware key attestation = Bad
+1
Hardware key attestation = Bad

Remote key attestation = good
+1
Remote key attestation = good

Unlocked bootloader with RKP disabled to do hardware attestation you cant pass strong the usual way anymore. Keyboxes are not
+1
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.