- 修复 OneUI 上因激进优化导致的 hook 失败 - Fix hook failure on OneUI because of aggressive Java optimization
🥰126👍32❤23🤣19👎12🔥6🌭4🤔3

Channel
@HideMyApplist
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cite this entry
40,893subscribers
+23 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001237731284 |
|---|---|
| Type | Channel |
| Username | @HideMyApplist |
| Description | 隐藏应用列表 Release / Beta 通道 @nullptr_dev |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 5 September 2026 |
| Measurements held | 26 |
| Confirmed unchanged | 1 time, most recently 5 September 2026 |
| On Telegram | t.me/HideMyApplist |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 5 Sept 2026, 03:19 | 40,893 | -10 |
| 3 Sept 2026, 11:40 | 40,903 | +1 |
| 1 Sept 2026, 07:38 | 40,902 | -5 |
| 31 Aug 2026, 07:24 | 40,907 | +1 |
| 30 Aug 2026, 07:59 | 40,906 | -1 |
| 29 Aug 2026, 04:36 | 40,907 | -5 |
| 28 Aug 2026, 06:36 | 40,912 | +5 |
| 27 Aug 2026, 03:29 | 40,907 | +5 |
| 26 Aug 2026, 01:41 | 40,902 | +1 |
| 25 Aug 2026, 00:46 | 40,901 | -15 |
| 23 Aug 2026, 15:34 | 40,916 | -2 |
| 21 Aug 2026, 23:37 | 40,918 | +9 |
| 20 Aug 2026, 21:35 | 40,909 | +21 |
| 19 Aug 2026, 19:35 | 40,888 | -6 |
| 18 Aug 2026, 16:46 | 40,894 | -14 |
| 17 Aug 2026, 19:07 | 40,908 | -10 |
| 16 Aug 2026, 16:16 | 40,918 | +6 |
| 15 Aug 2026, 00:59 | 40,912 | +7 |
| 13 Aug 2026, 13:58 | 40,905 | +10 |
| 12 Aug 2026, 11:58 | 40,895 | first reading |
20 posts held, back to 12 December 2022 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 62 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 1 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 5 September 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.
12,018 reactions across 20 posts, in 26 distinct kinds. The most used accounts for 49.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 5,942 | 49.4% | |
| ❤ | 2,144 | 17.8% | |
| 🔥 | 1,202 | 10.0% | |
| 🥰 | 1,169 | 9.73% | |
| 🤯 | 241 | 2.01% | |
| 👎 | 229 | 1.91% | |
| 😱 | 176 | 1.46% | |
| 👏 | 138 | 1.15% | |
| 🍌 | 119 | 0.99% | |
| 🤣 | 107 | 0.89% | |
| 🎉 | 69 | 0.574% | |
| 🤬 | 69 | 0.574% | |
| 🌚 | 62 | 0.516% | |
| 🤔 | 62 | 0.516% | |
| ❤🔥 | 58 | 0.483% | |
| 😁 | 41 | 0.341% | |
| 💯 | 39 | 0.325% | |
| 🌭 | 30 | 0.25% | |
| 🤩 | 29 | 0.241% | |
| 🏆 | 24 | 0.2% | |
| 6 further kinds | 68 | 0.566% |
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 20 of the 20 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 12,018 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 12 December 2022 to 1 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @HideMyApplist. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 20 most recent posts we hold for this entry, published 12 December 2022 to 1 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
- 修复 OneUI 上因激进优化导致的 hook 失败 - Fix hook failure on OneUI because of aggressive Java optimization
🥰126👍32❤23🤣19👎12🔥6🌭4🤔3
- 升级到 libxposed API 101 - Update to libxposed API 101
🥰172👍50❤24🤣9🍌4🔥4😁4❤🔥3
部分模块(例如 Activity 跳转拦截器)通过将原始 Intent 替换为指向模块自身组件的 Intent 来实现拦截功能。如果使用 HMA 隐藏了这些模块,并启用了 HMA 的激进的意图过滤功能,目标应用将无法解析或访问这些模块提供的 Intent,因此相关模块功能可能无法正常工作。 Some modules (such as Activity Start Manager) implement intent interception by replacing the target Intent with an Intent that points to the module itself. If these modules are hidden from an app and HMA's Aggressive Intent Filtering is enabled, the app will be unable to r…
👍97❤33🔥5
- 添加对不支持的 Xposed 框架实现的说明 - 在 PMS 获取应用列表 - 修复白名单模式过滤问题 - 修复其他小问题 - Added a note for unsupported Xposed framework implementations - Got the app list from PMS - Fixed filtering issues in whitelist mode - Fixed other minor issues 自上个版本开始,部分 hook 逻辑移动到 native lib,因此需要 Xposed 框架添加规则 allow system_server apk_data_file file execute 才能正常加载模块。
👍186❤41😱10🥰6🌭5👏3🤩2💯1
- 更换 hook 方案,大幅提升性能,可能不稳定。要求框架实现允许在系统服务中加载原生库 - 提升应用列表加载速度 - Switched to a new hooking approach, significantly improving performance, but it may be unstable. Requires framework to implement permission for loading native libraries within the system server - Improved app list loading speed
❤328😱38👎24👍16🤣9🥰8🤔7😁7
- 修复对 A11 的支持 - Fixed support for A11
👍217❤39😱38👎17🌚15🥰5😢5🔥4
- 最低支持版本提升至 Android 11 - 重构应用可见性过滤逻辑,提升性能与稳定性 - 新增可按应用单独设置的激进意图过滤选项 - 优化配置与列表刷新流程 - 移除 Firebase - Raised the minimum supported Android version to Android 11 - Refactored the app visibility filtering pipeline for better performance and stability - Added a per-app aggressive intent filtering option - Improved config handling and app list refresh behavior - Removed Firebase
❤219👍39😱27👎9🌚8🤣8🔥4🎉3
经研究,某些加固(如 Protectt.ai)通过直接启动对应应用主界面(如 KernelSU 管理器)的方式进行检测。由于直接启动活动并不在软件包可见性的限制范围内,用户需要手动启用激进的意图过滤器,HMA 才能拦截。之前我认为这种方式会破坏用户体验,因此加固不会使用,看来我高估它们的底线了。 举个例子说明为什么默认不启用该功能:如果用户对京东启用了白名单,且未将微信加入可见应用列表,则若未开启激进的意图过滤器,京东是可以直接拉起微信支付的;若开启了激进的意图过滤器,京东则无法拉起微信。因此,建议用户在任何时候都只使用黑名单模式。 此外,AOSP 仍存在大量软件包可见性问题(如我们昨天发现,通过传递错误的 display id 可以在不启动应用的情况下探测软件包存在性),考虑到谷歌认为非跨用户的软件包可见性问题均为低危,在可预计的将来,HMA 将仍是必需品。 ————————————— Research has sho…
👍548❤160🤯60🤬18🤣17🔥12👎4👏4
V3.6.1 Always enable ActivityStarter hook Support edge-to-edge Fix minor issues 永远启用 ActivityStarter 钩子 支持边到边 修复一些小问题
❤346👍54🔥14🤣9👎8🥰6👏3🤔3
V3.6 Implement aggressive intent filter Fix a few UI bugs 实现激进的意图过滤器 修复一些界面问题
❤507👍114🥰20🌚14👎14🤬10💯7🙏5
BTW: All ads removed 另外,移除了所有广告
👍762🥰94❤62🤯35😁16🔥13🌭10👏9
V3.5 Address startActivity() exploit below A13 Rework hook for getArchivedPackage() Improve logging performance 处理低于 A13 的 startActivity() 漏洞 重写 getArchivedPackage() 漏洞修复 提升日志性能
🔥273👍78❤40🥰16👎9🏆5🌚4❤🔥2
Showing the 12 most recent of 20 posts we hold for @HideMyApplist. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 30 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 5 September 2026 — this entry's latest reading, not the date you are reading this.
“Hide My Applist” (@HideMyApplist), 40,893 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/HideMyApplist.
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.