Telegram RegisterThe public register of Telegram

Channel

FolkPatch

@FolkPatch

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

9,762subscribers

+159 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003417958683
TypeChannel
Username@FolkPatch
DescriptionRoot access to the kernel can be achieved simply by patching the Boot partition for reflashing. This solution is based on a non-parallel extended branch of APatch, with a primary focus on UI/UX design
CreatedBetween 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 10 August 2026
On Telegramt.me/FolkPatch

Growth

9,6039,7629,682.56 August 2026 — 9,603 subscribers7 August 2026 — 9,624 subscribers10 August 2026 — 9,762 subscribers6 August 202610 August 2026
3 measurements spanning 4 days, net +159. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 9,579–9,786 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Aug 2026, 21:319,762+138
7 Aug 2026, 12:279,624+21
6 Aug 2026, 21:319,603first reading

Engagement

28 posts held, back to 31 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
36.8%
avg views ÷ 9,762 subscribers
Avg views / post
3,590
28 posts measured
Reaction rate
0.527%
reactions ÷ views · ER floor
Posts in window
28
of 28 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 10 August 2026
Posts held28 (31 July 202610 August 2026)
Views total100,480
Reactions total530
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 14:49 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.

What this channel posts

Photos
42
Videos
1
Links
20

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

530 reactions across 28 posts, in 12 distinct kinds. The most used accounts for 43.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍23143.6%
22342.1%
🔥244.53%
👏193.58%
😐71.32%
🥰71.32%
😍61.13%
🥴50.943%
🏆30.566%
🤔20.377%
🤷‍♂20.377%
🤨10.189%

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 28 of the 28 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 530reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 28 most recent posts we hold, published 31 July 2026 to 10 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.

Recent posts

10 Aug 2026, 14:49 UTC≈1,970 views19 reactionsread 12 August 2026

我替换了一个版本,请下载115019 I replaced a version, please download 115019

👍134😍2

10 Aug 2026, 13:33 UTC≈2,450 views23 reactionsread 12 August 2026
File

1.修复部分文本颜色的问题 2.Shizuku API支持软件隔离级权限控制,可以在基础Shell和Root Shell权能选择 1. Fix the issue with text color 2. Shizuku API supports software isolation level permission control, which can be selected between basic Shell and Root Shell privileges

👍148👏1

10 Aug 2026, 07:43 UTC≈2,350 views19 reactionsread 12 August 2026
File

Shizuku提升到root权限级别 Shizuku elevated to root permission level

👍96👏4

10 Aug 2026, 06:32 UTC≈2,300 views24 reactionsread 12 August 2026
File

Shizuku支持持久化配置,并支持更多API,支持调度MT管理器等软件 Shizuku supports persistent configuration and more APIs, supporting scheduling of MT Manager and other software

👍129👏3

9 Aug 2026, 20:00 UTC≈2,340 views29 reactionsread 12 August 2026
File

1. 内置 Shizuku 服务 —— 无需安装第三方应用。新增授权弹窗和应用授权管理,服务启动更稳定,开机自启更可靠。 2. 越狱模式支持加载 KPM —— 现已支持在越狱模式下加载 KPM。注意:该功能依赖内核兼容性,并非所有内核/设备都支持,若你的内核不支持则无法生效。 3. 体验优化与修复 —— 超级用户搜索更流畅,修复打开模块 WebUI 时背景音乐重叠、下载管理器闪退等问题,并对界面做了整体打磨。 1. Built-in Shizuku service -- No need to install third-party applications. New authorization popup and app authorization management have been added, making the service start more stable and the boot-up more relia

12🔥10👏4😍3

8 Aug 2026, 06:37 UTC≈3,020 views22 reactionsread 12 August 2026
File

1.挂载能力已经对齐Magic_mount扩展模块,和旧板挂载能力完全对齐,如果你没有更深度的定制需求,完全可以不需要安装元模块,设置打开Folk Mount API即可回到APatch旧版一致的挂载能力 2.修复一些用户的导航使用问题 3.插件添加对中文扩展语言的支持 1. The mounting capability has been aligned with the Magic_mount extension module, and it is fully aligned with the old board's mounting capability. If you don't have more in-depth customization needs, you can completely avoid installing the meta module by simply enabling the Folk Mo

👍118👏1🔥1😍1

7 Aug 2026, 13:02 UTC≈3,120 views39 reactionsread 12 August 2026
File

日常稳定性维护修复一些常见的问题 Daily stability maintenance fixes some common issues

👍30🥰42🤔2🔥1

6 Aug 2026, 15:12 UTC≈3,790 views41 reactionsread 12 August 2026
File

1. Added a jailbreak mode, which can load LKM modules to temporarily gain root privileges when SElinux is set to permissive, and equipped with hot system restart. Although not all functions are available, it can achieve system framework HOOKing. 2. Added the ability to enable listening in SU compatibility mode. 3. Adjusted the entry point of the plugin system to the settings section. 4. Moved functions to the menu. 1

👍298🔥3🤨1

5 Aug 2026, 15:46 UTC≈3,950 views24 reactionsread 12 August 2026
File

本次更新同步了 KernelPatch 修复:针对部分 OPPO、一加等骁龙设备上偶发的随机黑屏重启问题,内核在启动时若未能从补丁工具预置 kCFI 相关符号地址,将自动通过 kallsyms 在运行时重新解析,确保 kCFI 绕过防护不再静默缺失。对 Android 13+ GKI(启用 CONFIG_CFI_CLANG)的设备,钩子函数被间接调用时不再触发 "CFI failure" 崩溃,显著提升稳定性 This release syncs a KernelPatch fix for random black-screen reboots on some Snapdragon devices (e.g., OPPO/OnePlus): when the patcher fails to preset the kCFI-related symbol addresses, the kernel now re-resolves

17👍4🏆3

5 Aug 2026, 15:09 UTC≈3,380 views9 reactionsread 12 August 2026
Sticker

Sticker, posted without a caption

6👍3

Showing the 12 most recent of 28 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.

Citation-graph rank

Citation-graph rank — 998,506 of 1,169,250entries 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

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.

Mentions

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.

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 10 August 2026 — this entry's latest reading, not the date you are reading this.

“FolkPatch” (@FolkPatch), 9,762 subscribers as measured 10 August 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.