4.19等非GKI谨慎更新,APatch群爆出兼容性问题 4.19 and other non-GKI kernels require cautious updates; APatch group reports compatibility issues.
❤13😱7👍1

Channel
@FolkPatch
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
10,517subscribers
+914 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003417958683 |
|---|---|
| Type | Channel |
| Username | @FolkPatch |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/FolkPatch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 04:39 | 10,517 | +16 |
| 2 Sept 2026, 18:36 | 10,501 | +31 |
| 1 Sept 2026, 17:34 | 10,470 | +19 |
| 31 Aug 2026, 14:37 | 10,451 | +13 |
| 30 Aug 2026, 14:15 | 10,438 | +31 |
| 29 Aug 2026, 17:25 | 10,407 | +37 |
| 28 Aug 2026, 14:34 | 10,370 | +10 |
| 27 Aug 2026, 12:58 | 10,360 | +20 |
| 26 Aug 2026, 15:53 | 10,340 | +36 |
| 25 Aug 2026, 14:34 | 10,304 | +13 |
| 24 Aug 2026, 13:03 | 10,291 | +46 |
| 22 Aug 2026, 23:29 | 10,245 | +52 |
| 21 Aug 2026, 12:46 | 10,193 | +55 |
| 20 Aug 2026, 11:47 | 10,138 | +19 |
| 19 Aug 2026, 14:27 | 10,119 | +44 |
| 18 Aug 2026, 13:13 | 10,075 | +52 |
| 17 Aug 2026, 15:28 | 10,023 | +151 |
| 14 Aug 2026, 05:36 | 9,872 | +110 |
| 10 Aug 2026, 21:31 | 9,762 | +138 |
| 7 Aug 2026, 12:27 | 9,624 | first reading |
39 posts held, back to 31 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 40 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 39 (31 July 2026 – 28 August 2026) |
| Views total | 124,960 |
| Reactions total | 616 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Aug 2026, 15:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
900 reactions across 39 posts, in 15 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 399 | 44.3% | |
| 👍 | 384 | 42.7% | |
| 🔥 | 28 | 3.11% | |
| 👏 | 26 | 2.89% | |
| 🥰 | 16 | 1.78% | |
| 😱 | 12 | 1.33% | |
| 😍 | 7 | 0.778% | |
| 😐 | 7 | 0.778% | |
| 👀 | 5 | 0.556% | |
| 🥴 | 5 | 0.556% | |
| 🏆 | 3 | 0.333% | |
| 🤔 | 3 | 0.333% | |
| 🌭 | 2 | 0.222% | |
| 🤷♂ | 2 | 0.222% | |
| 🤨 | 1 | 0.111% |
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 39 of the 39 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 900 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 39 most recent posts we hold, published 31 July 2026 to 28 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
4.19等非GKI谨慎更新,APatch群爆出兼容性问题 4.19 and other non-GKI kernels require cautious updates; APatch group reports compatibility issues.
❤13😱7👍1
kp: bump to 0.13.6 init support 6.18 & fix some bugs
❤16👍1🥰1
https://github.com/LyraVoid/Shirone 帮我给我的新项目点一下Star Please help me give my new project a Star
👍35❤12😱1
Photo, posted without a caption
👍18❤4🥰1
无法规避的Magisk识别方案已经公开:https://github.com/eltavine/Duck-Detector-Refactoring/pull/22 检测方法说明和概念验证app:https://github.com/LSPosed/DirtySepolicy
❤8
1.新增SElinux隐藏功能,落地到了常规-隐藏SElinux选项(实现性API) 2.废除自动加载KPM的功能,改用一个叫做安装的新概念,他会比旧版的自动加载KPM更加可靠 3.修复部分FolkPatch KP HOOK功能无法在开机启动的问题 1. Add SElinux hidden feature, implemented in the conventional - hidden SElinux option (implementation API) 2. Remove the automatic loading of KPM function, and replace it with a new concept called installation, which is more reliable than the old automatic loading of KPM 3. Fix the issue where…
❤23🔥3😱3🌭2👀1👍1
QQ群2166069263
👍10❤6
目前只会同步上游代码但是不发版,等待稳定
👍15❤4🔥1
内核升级 KernelPatch 0.13.5,修复 4.x 老内核热补丁失败/无法启动的问题 补丁流程重构:初始化更可靠,失败自动重试,不再出现"卡住"状态 修复手动刷机后 ori.img 迁移失效的问题(更新前该功能其实从未生效) Shizuku 日志页全新 M3e 界面,顶部按钮收进菜单,更简洁 语言设置:显示 app 自己的语言名(如"简体中文"),选择后立即生效 底层加固:修补 su、模块安装、配置解析等多个安全漏洞 Kernel update KernelPatch 0.13.5, fixing the issues with hot patching failing/not booting on 4.x old kernels Patch process restructured: more reliable initialization, automatic retry on failure, no "stuck…
👍30❤17🥰1
FolkPatch v115020 更新日志 - 新增:内置 Shizuku 服务端日志功能,可查看/搜索/导出/清空服务端日志与 logcat,支持跨重启排查(入口:Shizuku 授权页) - 改进:设置页组件交互与视觉效果优化(Surface 材质化、主题色涟漪反馈、combinedClickable) - 同步:KernelPatch 升级至 0.13.4(新增 selinux_hide/策略增强、修复新内核兼容与稳定性问题) - 同步:APatch 主线三个提交(kp 版本同步、重建触发) - 翻译:Shizuku 日志功能全部文案补齐 17 种语言/中文变体 - 其他:应用版本号 115019 → 115020 FolkPatch v115020 Update Log - Added: Built-in Shizuku server log function, allowing viewing/searching/e…
❤23👍23👏4🤔1
Recently, I've been working on a new project, and may not be updating as frequently. 最近在维护新项目,可能少更新
❤20🥰6👀4
我替换了一个版本,请下载115019 I replaced a version, please download 115019
👍18❤5😍3😱1
Showing the 12 most recent of 39 posts we hold for @FolkPatch. 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.
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.
Named by 2 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.
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 4 September 2026 — this entry's latest reading, not the date you are reading this.
“FolkPatch” (@FolkPatch), 10,517 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/FolkPatch.
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.