Telegram RegisterThe public register of Telegram
Telegram profile photo for LSPosed

Channel

LSPosed

@LSPosed

On this record: Topic · Also posting the same content · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cross-platform identity · Cite this entry

189,190subscribers

+2,461 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001499638348
TypeChannel
Username@LSPosed
DescriptionOfficial webpage: lsposed.org Discussion Group: @LSPosedDiscussion CI Builds: @LSPosedArchives Admin Log: @lsposed_log
CreatedBetween 1 October 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live20 August 2026
Measurements held14
Confirmed unchanged1 time, most recently 20 August 2026
On Telegramt.me/LSPosed

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Also posting the same content

This channel’s posts match, word for word or near enough, posts on 1 other registered channel, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.

Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

186,729189,190187,959.56 August 2026 — 186,729 subscribers7 August 2026 — 186,827 subscribers8 August 2026 — 186,960 subscribers9 August 2026 — 187,088 subscribers10 August 2026 — 187,265 subscribers11 August 2026 — 187,413 subscribers12 August 2026 — 187,599 subscribers14 August 2026 — 187,773 subscribers15 August 2026 — 188,051 subscribers16 August 2026 — 188,227 subscribers17 August 2026 — 188,386 subscribers18 August 2026 — 188,654 subscribers19 August 2026 — 188,975 subscribers20 August 2026 — 189,190 subscribers6 August 202620 August 2026
14 measurements spanning 14 days, net +2,461. 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 186,360–189,559 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
20 Aug 2026, 21:36189,190+215
19 Aug 2026, 18:56188,975+321
18 Aug 2026, 19:07188,654+268
17 Aug 2026, 21:22188,386+159
16 Aug 2026, 21:47188,227+176
15 Aug 2026, 16:23188,051+278
14 Aug 2026, 06:38187,773+174
12 Aug 2026, 21:02187,599+186
11 Aug 2026, 18:06187,413+148
10 Aug 2026, 15:38187,265+177
9 Aug 2026, 12:31187,088+128
8 Aug 2026, 15:15186,960+133
7 Aug 2026, 13:37186,827+98
6 Aug 2026, 19:02186,729first reading

Engagement

20 posts held, back to 4 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 33 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
59.1%
avg views ÷ 189,190 subscribers
Avg views / post
112,000
3 posts measured
Reaction rate
0.765%
reactions ÷ views · ER floor
Posts in window
3
of 20 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 4 August 2026
Posts held20 (4 September 20254 August 2026)
Views total335,300
Reactions total2,565
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 22:18 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
27
Videos
3
Links
52

Lifetime counters from Telegram’s own channel header, read 20 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.

Video runtime
4m 09s
Average length
2m 05s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

16,498 reactions across 20 posts, in 13 distinct kinds. The most used accounts for 44.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
7,27844.1%
👍6,74140.9%
🔥4742.87%
🍾3682.23%
🥰3041.84%
🎉2981.81%
❤‍🔥2331.41%
🤩1871.13%
👏1701.03%
🏆1580.958%
💯1480.897%
🤗870.527%
😍520.315%

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 16,498reactions 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 4 September 2025 to 4 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.

Telegram Stars

Stars received
652
across the posts below
Posts paid on
20
of 20 we hold a reading for · 100%
Most on one post
111
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @LSPosed. 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 4 September 2025 to 4 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.

Recent posts

4 Aug 2026, 16:29 UTC≈75,200 views1,174 reactions5 Starsread 20 August 2026

我们在 Android 17.0 中发现了一个特权进程任意代码执行漏洞。该漏洞已在 Android 17 QPR1 中修复,但 AOSP 安全公告中并未提及。结合 dirty frag 漏洞(CVE-2026-43284),我们在 Android 17.0 上成功实现了完整的 root 权限提升。 这是一个典型的 1day 漏洞。尽管补丁已发布,但用户无法获得漏洞修复,因此仍面临被攻击的风险:任何人都可以通过对比分析发现该漏洞的细节。而 dirty frag 漏洞虽已于三个月前披露,但至今仍可被利用。这是因为谷歌推迟了漏洞补丁的发布频率,将安全公告从每月一次改为每季度一次。在 AI 时代,这种做法不可理喻。由于 Pixel 系统镜像中泄露的漏洞细节,Android 生态中的大量设备都容易受到攻击,未参与 Beta 测试计划的 Pixel 设备也无法幸免。 因此,我们利用两个“已经”修复过的漏洞,演示了对安装有最新安全补丁的

👍890163🤩46❤‍🔥21🍾13🔥11🤗9💯8

4 Aug 2026, 16:28 UTC≈68,100 views434 reactions3 Starsread 20 August 2026
Video

We discovered a privileged process arbitrary code execution vulnerability in Android 17. This vulnerability was patched in Android 17 QPR1 but was not included in any security bulletin. Combined with the dirty frag vulnerability (CVE-2026-43284), we achieved full root privilege escalation on Android 17.0. The DirtyFrag vulnerability was disclosed 3 months ago but is still exploitabe, because Google has delayed the r

👍28083🔥32👏14💯7❤‍🔥5🏆4🍾3

23 Jul 2026, 16:20 UTC≈192,000 views957 reactions4 Starsread 20 August 2026

v2.1.1 新增 - 最低支持版本提升至 Android 9(API 28) - 高级隐藏功能现可支持 A12+ - 允许一键清空已选作用域 改进 - 优化安全模式对 System UI 的检测阈值 - 恢复管理器中的模块数量徽标 - 改进错误报告发送流程 修复 - 修复部分情况下无法启动守护进程的问题 - 修复 XposedHelpers.findField API 行为 - 修复 Android 17 下服务连接接口不兼容的问题 - 修复模块详情页弹出菜单显示层级异常的问题 - 修复 Markdown 样式在部分页面中显示异常的问题 Added - Raised the minimum supported version to Android 9 (API 28) - Advanced hiding is now supported on Android 12 and above - Added an option

689👍142❤‍🔥29🤩18🥰15🏆14🍾13🎉13

9 Jul 2026, 23:46 UTC≈177,000 views1,003 reactions3 Starsread 20 August 2026
Video

Successfully root my K90PM using CVE-2026-43499

682👍114🔥81👏31🍾22🏆22❤‍🔥12🤗12

15 Jun 2026, 10:43 UTC≈335,000 views1,189 reactions19 Starsread 20 August 2026

v2.1.0 新增 实现 libxposed API 102 适配 Android 17 QPR1 Beta 4 维护 原计划 2.1.0 废弃 New XSharedPreferences 推迟到 2.2.0,强烈建议 legacy 模块尽快迁移到 libxposed 改进 大幅提升被 hook 方法的性能 优化还原内联钩子逻辑 优化 dex 优化器包装的挂载逻辑 优化一系列的 UI 体验 修复 修复 XposedBridge.unhookMethod 行为异常 修复了一个全局检测点 修复 TalkBack 重复朗读、未朗读勾选状态等无障碍问题 Added Implemented libxposed API 102 Adapted for Android 17 QPR1 Beta 4 Maintaince Postponed the planned deprecation of New XSharedPreferen

👍810201🔥41🤩33❤‍🔥25🥰20😍18🍾16

1 Jun 2026, 16:16 UTC≈418,000 views1,079 reactions12 Starsread 20 August 2026
File

Changes since latest release: Added - Provided high-speed CDN for the module repository. If you dislike ads, please switch to backup CDN in settings - Added SystemUI safe mode Improved - Enhanced hook compatibility and performance - Improved homepage device name recognition Fixed - Fixed Android 17 QPR1 Beta 3 crash issues - Fixed a series of M3E theme-related issues - Fixed Markdown WebView reload handling issues

👍696226🔥33❤‍🔥22💯21🥰21🎉17🏆16

29 May 2026, 07:21 UTC≈249,000 views300 reactions2 Starsread 20 August 2026

libxposed API 102 is now under RFC. Please give us suggestions regarding the API design. https://github.com/libxposed/api/pull/62

👍18566🎉15🥰13❤‍🔥7🔥7🏆6💯1

28 May 2026, 12:51 UTC≈211,000 views343 reactions2 Starsread 20 August 2026

libxposed API 102 snapshots are now available. Join our internal test program to get LSPosed with API 102 support so you can test it. Please note that it's NOT final so NEVER use snapshots in production. Open an issue on GitHub if you have any suggestion. Usage: add snapshot maven to settings.gradle.kts maven { url = uri("https://central.sonatype.com/repository/maven-snapshots/") mavenContent { snaps

250👏25👍23🔥17❤‍🔥8🤩7🥰6🏆4

20 May 2026, 11:22 UTC≈295,000 views850 reactions14 Starsread 20 August 2026

v2.0.3 released: Major Behavioral Changes - Legacy modules are no longer allowed to call libxposed API; modules with targetApiVersion ≥ 102 will not be allowed to call legacy API; 101 modules are unaffected New Features - Introduced Material 3 Expressive style manager - Enhanced theme-related settings to support dynamic color schemes and dark mode, and improved the display of cards, menus, bottom navigation, and dia

619👍99🎉36🔥25🥰14💯12😍12🍾11

16 May 2026, 07:54 UTC≈169,000 views417 reactions16 Starsread 20 August 2026

kind reminder: you can also use lsposed.zip to download the latest public lsposed.

306👍52❤‍🔥15🎉14💯10🤩7🍾6🔥6

10 May 2026, 16:13 UTC≈182,000 views359 reactions4 Starsread 20 August 2026
Forwarded from @magiskalphaFile

无法规避的Magisk识别方案已经公开:https://github.com/eltavine/Duck-Detector-Refactoring/pull/22 检测方法说明和概念验证app:https://github.com/LSPosed/DirtySepolicy

246🍾34👍27🔥21🤗15🤩6❤‍🔥5🏆5

23 Apr 2026, 14:13 UTC≈390,000 views1,724 reactions61 Starsread 20 August 2026
File

Changes since last release: Added Enabled dynamic blur based on device state (e.g. power saving mode, performance class) Added collapsing for long module descriptions Added tapjacking mitigation toggle and hint Hid the "install to other user" option when the module is already installed Improved Reduced per-method callback count to limit crash propagation caused by faulty modules Ensured Xposed service is re-delivere

1,330👍185🔥55🍾38🥰26❤‍🔥25😍18🤩16

Showing the 12 most recent of 20 posts we hold for @LSPosed. 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.

Citation-graph rank

Citation-graph rank — 12,430 of 1,569,089entries 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 12 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.

Channels Telegram recommends alongside this one

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.

5ec1cff
@real5ec1cff · 35,187
#1
Real Nullptr
@nullptr_dev · 18,067
#2
HyperCeiler | Canary Test
@cemiuiler_canary · 17,394
#3
Magisk alpha
@magiskalpha · 65,349
#4
AdClose Official
@AdClose · 12,073
#5
Android Software Hub
@ksc666 · 14,799
#6
akashaProxy ci channel
@akashaProxy · 1,689
#7
Reveny
@reveny1 · 7,434
#8
Voyager HyperOS Update
@VoyagerMIUIUpdate · 20,519
#9
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 21,399
#10
科技圈🎗在花频道📮
@zaihuapd · 277,400
#11
橘橘橘子汁 & 🍊
@microblock_pub · 14,938
#12
风向旗参考快讯
@xhqcankao · 159,147
#13
RandomFree
@c001apk · 6,756
#14
我喜欢你
@bakaPD · 9,913
#15
Sakion Team
@Sakion_Team · 1,918
#16
Magisk Base || Magisk modules and other
@magiskmodules22 · 12,845
#17
InstallerX
@InstallerX · 8,540
#18
NPatch
@NPatch · 18,518
#19
欢乐花园
@MaterialDesign3 · 9,172
#20
LibChecker CI
@libchecker_ci · 3,446
#21
QAuxiliary CI Builds
@QAuxiliary_CI · 19,375
#22
蓝点网订阅频道
@landiansub · 43,710
#23
QQ/TIM Update Log
@qq_updatelog · 6,577
#24
LoopDNS资讯播报
@DNSPODT · 71,128
#25
QQ Updates
@QQUpdates · 10,102 (as read 17 August 2026)
#26
HyperCeiler | Release & Notice
@cemiuiler_release · 25,983
#27
XiReiki
@xiayinlily · 2,849
#28
Pillboard
@Pillboard · 3,518
#29
Pzqqt's News Channel
@pzqqt_c · 3,898
#30
VPS信号旗播报
@vps_xhq · 48,854
#31
每日消费电子观察
@CE_Observe · 73,382
#32
Project X Channel
@projectXtls · 29,767
#33
柒柒的鱼骨头
@Sandrone0721 · 1,080
#34
Bilibili Android Apk w/ HD
@bilibili_apk · 3,186 (as read 17 August 2026)
#35
Hakuma is cute ~
@huskydg · 4,163 (as read 17 August 2026)
#36
秋风のとおり道
@AWAvenue · 26,005
#37
Wa Enhancer Updates & Tips
@waenhancher · 35,150
#38
Pixel Props
@PixelProps · 14,114
#39
GApps Leaks
@GappsLeaks · 21,283
#40
WSTprojects
@WSTprojects · 28,304
#41
Play integrity fix NEXT
@PifNEXT · 6,662
#42
DrDisagree's Projects
@DrDsProjects · 9,287
#43
Loop Projects | #TeamFiles
@loopprojects · 9,733
#44
Mishaal's Android News Feed
@MishaalAndroidNews · 11,895
#45
Android dumps
@android_dumps · 5,586
#46
[DISCONTINUED] Rboard Themes
@rkbdigboard · 6,102
#47
PUI The Newsroom 😍
@PUINewsroom · 13,833
#48
Nagram
@nagram_channel · 64,481
#49
XPL-EX
@xpl_ex · 3,046
#50
Nullgram
@NullgramClient · 8,049
#51
SafetyNet, CTS, and Play integrity
@ctsfixes · 2,419
#52
APC - Android Ports Cloud
@apcports2 · 8,779
#53
不要糖醋放椒盐
@saltplayerupdate · 17,085
#54
MrSluffy's Prjkt
@mrsluffy_releases · 6,099
#55
SnapEnhance
@snapenhance · 9,334
#56
RKBDI channel
@RKBDIchannel · 1,911
#57

Read from Telegram’s recommendation API, most recently 17 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.

Appears in Telegram’s recommendations for other channels

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.

Github_2dust
@github_2dust · 90,693
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 17 August 2026
Clash Verge Rev Channel
@clash_verge_re · 77,683
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 19 August 2026
Legado|开源阅读|频道
@Legado_Channels · 92,886
Telegram ranks this channel #30 of 61 here — alongside 60 others — read 17 August 2026

This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q114903881 on Wikidata, read 16 August 2026
LabelLSPosed
DescriptionAndroid module framework based on EdXposed
Official sitehttps://lsposed.org/

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

“LSPosed” (@LSPosed), 189,190 subscribers as measured 20 August 2026. Telegram Register, tgregister.com/channel/LSPosed.

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.