出现了一些问题 别急🫣 忘签名而已,重新下载
💊19

Channel
@onpatch
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,918subscribers
+103 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002163306347 |
|---|---|
| Type | Channel |
| Username | @onpatch |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/onpatch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 17:36 | 3,918 | +37 |
| 11 Aug 2026, 01:32 | 3,881 | +57 |
| 7 Aug 2026, 22:00 | 3,824 | +9 |
| 7 Aug 2026, 12:17 | 3,815 | first reading |
17 posts held, back to 5 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 3 pagesof 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 7 August 2026 |
|---|---|
| Posts held | 17 (5 July 2026 – 7 August 2026) |
| Views total | 16,061 |
| Reactions total | 200 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 06:10 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.
420 reactions across 17 posts, in 11 distinct kinds. The most used accounts for 27.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 117 | 27.9% | |
| 👍 | 112 | 26.7% | |
| 🤔 | 78 | 18.6% | |
| 😭 | 37 | 8.81% | |
| 🎉 | 20 | 4.76% | |
| 💊 | 19 | 4.52% | |
| 🔥 | 12 | 2.86% | |
| 👻 | 9 | 2.14% | |
| 😡 | 8 | 1.90% | |
| 🍌 | 5 | 1.19% | |
| 🌭 | 3 | 0.714% |
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 17 of the 17 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 420reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 5 July 2026 to 7 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.
出现了一些问题 别急🫣 忘签名而已,重新下载
💊19
fix:移除 bypass_sig.cpp 中不穩定的 inline hook 與 FD 追蹤 fix:本機模式作用域同步 - 引進 FallbackModuleServiceWrapper 以攔截 IModuleService 的 IPC 請求 - 將遠端偏好設定同步至目標應用程式的本機 NPatchRemoteStore 快照中 - 當遠端 Manager 被殺掉或無法連線時,無縫降級至本機備援機制
👍13
Why do your feel that the installation package is getting smaller and smaller, but I feel that it is not good? Shouldn’t I be praised? The main reason for the small size is that the core is streamlined, so the built product is smaller.
❤19👍3
- Updated and adapted to the latest kernel changes Due to some changes, you may need to clear your data or uninstall and reinstall NPatch.
🎉16❤6😭4👍3🤔1
fix(loader): 強化管理器斷連防護與模組範疇快取機制 解決管理器服務斷連或死亡時,RemoteException / DeadObjectException 傳播至背景宿主程序導致崩潰的問題。 新增模組快取機制,避免離線時丟失已載入的模組範疇,確保本地模組持續生效。
👍26❤4🔥3
我又一次同步了大部分程式碼在 7723mod/NPatch ~
❤7
更新了內核,修正了一些相容性問題
👍25❤4👻3
feat(remote): 完善 Modern API 遠端資料支援 統一 API 101/102 的 Remote Preferences 與 Remote Files,讓模組設定 App 和被注入程序安全存取同一份 Manager Remote Store,同時維持目標程序唯讀、模組 App 可寫的權限邊界 fix: 提升本地模式冷啟動與離線容錯 Manager Provider 與 Binder 連線加入逾時、重試和本地快取回退,避免 Manager 冷啟動或暫時不可用時卡住應用啟動、重複載入模組或產生狀態競爭 fix(bootstrap): 讓本地模式修補包完整自包含 Loader Dex 與必要原生核心直接寫入修補 APK,不再於應用啟動時跨 UID 讀取或臨時提取 Manager APK 內容;Manager 僅負責模組、作用域與 Remote 資料 fix(loader): 重建 AppComponentFacto…
❤18🤔8
feat: 升級至 NPatch v1.0.7 並對齊 Miuix 導覽設計 重整主畫面導覽、頁面切換與底部導覽列佈局,統一 Miuix 視覺與互動方式,並改善小螢幕及橫向畫面的顯示效果 feat(api102): 完成 Modern API 102 模組載入與熱重載鏈路 以 Vector master 為核心基準重整 Modern API,保留原有 API 101 相容路由,加入執行中目標追蹤、模組世代更新、Binder 死亡清理及受控熱重載流程 feat(logging): 完整接合模組日誌與 Java 崩潰輸出 統一 Legacy 與 Modern 模組的檔案日誌橋接,補齊 API 101/102 模組輸出,並攔截未處理的 Java 例外,讓應用程式崩潰資訊可寫入 NPatch 日誌 feat(stealth): 新增 xhook GOT/PLT 簽章繞過模式 透過 xhook 重導應用程式原生庫對 APK 路徑與檔案資訊…
❤11🎉3🤔3
原 v1.0.6-7xx 的更新日誌請忽視
❤1
Posted without readable text
🤔53❤7👻6👍4
fix(manager): improve manager UI styling - Standardized group header styles across all pages - Fixed the off-center loading icon in the installation popup - Removed the dark overlay from custom backgrounds https://github.com/7723mod/NPatch/discussions/93#discussioncomment-17643286
❤13🔥3
Showing the 12 most recent of 17 posts we hold for @onpatch. 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 — 256,243 of 1,345,403entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 1 registered channel — 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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“ONPatch” (@onpatch), 3,918 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/onpatch.
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.