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 · Referenced elsewhere · Cite this entry

195,604subscribers

+8,875 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 August 2019 and 31 January 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 October 2026
Measurements held35
Confirmed unchanged1 time, most recently 4 October 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,729195,604191,166.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 subscribers22 August 2026 — 189,402 subscribers23 August 2026 — 189,669 subscribers25 August 2026 — 189,860 subscribers26 August 2026 — 190,079 subscribers27 August 2026 — 190,277 subscribers28 August 2026 — 190,495 subscribers29 August 2026 — 190,602 subscribers30 August 2026 — 190,769 subscribers31 August 2026 — 191,003 subscribers1 September 2026 — 191,114 subscribers2 September 2026 — 191,255 subscribers3 September 2026 — 191,392 subscribers5 September 2026 — 191,678 subscribers9 September 2026 — 192,028 subscribers11 September 2026 — 192,302 subscribers13 September 2026 — 192,568 subscribers15 September 2026 — 192,713 subscribers16 September 2026 — 193,017 subscribers19 September 2026 — 193,348 subscribers25 September 2026 — 194,124 subscribers4 October 2026 — 195,604 subscribers6 August 20264 October 2026
35 measurements spanning 59 days, net +8,875. 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 185,398–196,935 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 35
Measured (UTC)SubscribersChange
4 Oct 2026, 08:56195,604+1,480
25 Sept 2026, 16:41194,124+776
19 Sept 2026, 06:15193,348+331
16 Sept 2026, 23:41193,017+304
15 Sept 2026, 01:18192,713+145
13 Sept 2026, 13:40192,568+266
11 Sept 2026, 17:21192,302+274
9 Sept 2026, 03:59192,028+350
5 Sept 2026, 21:16191,678+286
3 Sept 2026, 18:02191,392+137
2 Sept 2026, 13:35191,255+141
1 Sept 2026, 10:37191,114+111
31 Aug 2026, 10:25191,003+234
30 Aug 2026, 07:16190,769+167
29 Aug 2026, 04:25190,602+107
28 Aug 2026, 05:46190,495+218
27 Aug 2026, 03:25190,277+198
26 Aug 2026, 03:46190,079+219
25 Aug 2026, 02:25189,860+191
23 Aug 2026, 18:56189,669first reading

Engagement

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

ERR · 30 days
40.0%
avg views ÷ 195,604 subscribers
Avg views / post
78,200
4 posts measured
Reaction rate
0.754%
reactions ÷ views · ER floor
Posts in window
4
of 27 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 5 October 2026
Posts held27 (4 September 2025 – 5 October 2026)
Views total312,600
Reactions total2,358
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Oct 2026, 09:23 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
57

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

21,247 reactions across 27 posts, in 24 distinct kinds. The most used accounts for 43.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍9,22843.4%
❤8,01037.7%
😭8614.05%
🔥6633.12%
🍾4332.04%
🥰3571.68%
🎉3141.48%
❤‍🔥2831.33%
🤩2301.08%
👏1940.913%
🏆1720.81%
💯1640.772%
🤗1120.527%
😍750.353%
😱730.344%
🤣220.104%
🤨220.104%
😡90.042%
🌚60.028%
💅60.028%
4 further kinds130.061%

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

Measured over the 27 most recent posts we hold, published 4 September 2025 to 5 October 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
668
across the posts below
Posts paid on
24
of 27 we hold a reading for · 89%
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 27 most recent posts we hold for this entry, published 4 September 2025 to 5 October 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

5 Oct 2026, 02:39 UTC≈17,300 views476 reactionsread 5 October 2026

LSPosed v2.2.1 从本次更新开始,安装包使用 XZ 压缩以减小体积,2024 年 8 月后的所有 root 实现均已支持 XZ 压缩方式。 Starting with this update, installation packages use XZ compression to reduce their size. All root implementations released after August 2024 support XZ compression. 新增 - 恢复提供 riscv64 ABI 支持 - 支持 Android 17 QPR 3 - 提升 KernelSU 最低管理器版本要求到 1.0.1 - 新增开发者模式与命令行工具 lspctl,支持管理模块及作用域等功能 - 新增禁用安全模式的选项 - 新增横移返回手势开关 改进 - 大幅优化调用链性能,钩子执行成本约 27x speedup …

👍371🔥43❤35😡9🌚6🗿4👎3💯2

14 Sept 2026, 11:38 UTC≈84,000 views1,191 reactionsread 5 October 2026

The libxposed organization has been flagged by GitHub, to access the source code or java doc, you can download the relevant files from the Maven Central Repository. libxposed 组织已被 GitHub 封锁,如需查阅源代码或文档,可在 maven 中央仓库下载相关文件。 https://repo.maven.apache.org/maven2/io/github/libxposed

😭860👍108😱73❤55🍾22🤣22🤨22🔥14

10 Sept 2026, 13:07 UTC≈98,300 views342 reactions6 Starsread 5 October 2026

libxposed future proposal: DexSQL DexSQL lets you query Android DEX files with SQL, it replaces the DexParser that was deprecated in libxposed API 100. It is now available for early access—feedback on slow or failing SQL statements is welcome. libxposed 新功能提案:DexSQL DexSQL 允许使用 SQL 语句查询 Android DEX 文件结构,它取代了libxposed API 100 中被废弃的DexParser。 现在可以抢先试用,欢迎反馈缓慢或者失败的SQL语句。 https://dexsql.lsposed.org/

👍227❤63🔥34🍾8🥰6🤗3😭1

9 Sept 2026, 01:14 UTC≈113,000 views349 reactions1 Starread 5 October 2026

https://github.com/LSPosed/LSPromise

👍239🔥43❤40🥰14👏7💯4❤‍🔥2

3 Sept 2026, 05:19 UTC≈122,000 views699 reactions6 Starsread 5 October 2026

Due to the increasing prevalence of AI and the accelerated submission of new modules, we plan to upgrade our module repository to an automated approval mode. Following the approach of the Maven Central Repository, submitters will need to prove they control the domain name to which the module package name belongs. If there is no domain name, you can use io.github.[user name].[module name], which will automatically app…

👍526❤113😍19🔥11🤗7🥰6🍾5🎉5

31 Aug 2026, 14:39 UTC≈115,000 views382 reactionsread 5 October 2026
File

另外系统自带 docker,在 /data/docker/docker

👍303❤32❤‍🔥13🍾10🤗10🤩4🥰4🔥3

30 Aug 2026, 04:07 UTC≈186,000 views665 reactions3 Starsread 5 October 2026

v2.2.0 重要 - New XSharedPreferences 计划于 2.3.0 正式移除,模块页面已为有兼容风险的模块加入废弃警告。判断逻辑为 legacy 模块声明支持 nsp 并存在 others 可读 xml。升级到 libxposed 或将 xposedminversion 设置为 82 并删除 xposedsharedprefs 以移除警告。 新增 - 支持注入 HyperOS Runtime 应用(需要兼容 Zygisk Next API 的 Zygisk 实现) - 在 A17 及以上以注入方式处理 dex2oat 包装器,避免挂载泄漏(需要兼容 Zygisk Next API 的 Zygisk 实现) 改进 - 提升多进程应用中模块服务连接的稳定性 - 优化管理器中的兼容性状态展示与异常提示 修复 - 修复资源 Hook XML 重写长期失效的问题 - 修复模块热重载失败后可能产生状态异常的问题 …

👍458❤116🔥24🤩24🥰15❤‍🔥12🍾6👏5

4 Aug 2026, 16:29 UTC≈210,000 views1,426 reactions5 Starsread 5 October 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 设备也无法幸免。 因此,我们利用两个“已经”修复过的漏洞,演示了对安装有最新安全补丁的 …

👍1,050❤220🤩57❤‍🔥27🍾18🔥15🤗12👏10

4 Aug 2026, 16:28 UTC≈181,000 views552 reactions3 Starsread 5 October 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…

👍330❤135🔥37👏16❤‍🔥7💯7🍾5🥰5

23 Jul 2026, 16:20 UTC≈312,000 views1,062 reactions4 Starsread 5 October 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 …

❤765👍150❤‍🔥35🤩22🥰17🏆16🍾15🎉15

9 Jul 2026, 23:46 UTC≈246,000 views1,024 reactions3 Starsread 5 October 2026
Video

Successfully root my K90PM using CVE-2026-43499

❤696👍115🔥82👏32🍾24🏆23🤗13❤‍🔥12

15 Jun 2026, 10:43 UTC≈405,000 views1,202 reactions19 Starsread 5 October 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…

👍816❤204🔥42🤩33❤‍🔥26🥰20😍20🍾16

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

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 15 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 · 37,726
#1
Real Nullptr
@nullptr_dev · 20,605
#2
HyperCeiler | Canary Test
@cemiuiler_canary · 19,480
#3
Magisk alpha
@magiskalpha · 65,878
#4
AdClose Official
@AdClose · 12,246
#5
Android Software Hub
@ksc666 · 14,905
#6
akashaProxy ci channel
@akashaProxy · 1,771
#7
Reveny
@reveny1 · 7,503
#8
Voyager HyperOS Update
@VoyagerMIUIUpdate · 21,720
#9
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 21,834
#10
在花🎗️科技圈
@zaihuapd · 284,519
#11
橘橘橘子汁 & 🍊
@microblock_pub · 15,497
#12
风向旗参考快讯
@xhqcankao · 164,187
#13
RandomFree
@c001apk · 6,676
#14
我喜欢你
@bakaPD · 10,397
#15
Sakion Team
@Sakion_Team · 1,978
#16
Magisk Base || Magisk modules and other
@magiskmodules22 · 12,848
#17
InstallerX
@InstallerX · 8,797
#18
NPatch
@NPatch · 19,394
#19
企业级欢乐花园
@MaterialDesign3 · 9,190
#20
LibChecker CI
@libchecker_ci · 3,541
#21
QAuxiliary CI Builds
@QAuxiliary_CI · 19,573
#22
蓝点网订阅频道
@landiansub · 45,562
#23
QQ/TIM Update Log
@qq_updatelog · 6,861
#24
LoopDNS资讯播报
@DNSPODT · 72,312
#25
QQ Updates
@QQUpdates · 10,215
#26
HyperCeiler | Release & Notice
@cemiuiler_release · 27,156
#27
XiReiki
@xiayinlily · 2,855
#28
Pillboard
@Pillboard · 3,489
#29
Pzqqt's News Channel
@pzqqt_c · 3,965
#30
VPS信号旗播报
@vps_xhq · 49,990
#31
每日消费电子观察
@CE_Observe · 75,687
#32
Project X Channel
@projectXtls · 29,938
#33
柒柒的鱼骨头
@Sandrone0721 · 1,110
#34
Bilibili Android Apk w/ HD
@bilibili_apk · 4,092
#35
Hakuma is cute ~
@huskydg · 4,150
#36
秋风のとおり道
@AWAvenue · 25,975
#37
Wa Enhancer Updates & Tips
@waenhancher · 35,830
#38
Pixel Props
@PixelProps · 14,249
#39
GApps Leaks
@GappsLeaks · 21,506
#40
WSTprojects
@WSTprojects · 28,116
#41
Play integrity fix NEXT
@PifNEXT · 6,710
#42
DrDisagree's Projects
@DrDsProjects · 9,344
#43
Loop Projects | #TeamFiles
@loopprojects · 9,708
#44
Mishaal's Android News Feed
@MishaalAndroidNews · 11,788
#45
Android dumps
@android_dumps · 5,706
#46
[DISCONTINUED] Rboard Themes
@rkbdigboard · 6,002
#47
PUI The Newsroom 😍
@PUINewsroom · 13,874
#48
Nagram
@nagram_channel · 69,969
#49
XPL-EX
@xpl_ex · 3,076
#50
Nullgram
@NullgramClient · 8,559
#51
SafetyNet, CTS, and Play integrity
@ctsfixes · 2,435
#52
APC - Android Ports Cloud
@apcports2 · 8,825
#53
不要糖醋放椒盐
@saltplayerupdate · 17,349
#54
MrSluffy's Prjkt
@mrsluffy_releases · 6,035
#55
SnapEnhance
@snapenhance · 9,447
#56
RKBDI rant channel
@RKBDIchannel · 1,896
#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.

Hide My Applist
@HideMyApplist · 40,955
Telegram ranks this channel #1 of 24 here — alongside 23 others — read 30 August 2026
Magisk alpha
@magiskalpha · 65,878
Telegram ranks this channel #1 of 40 here — alongside 39 others — read 21 August 2026
Real Nullptr
@nullptr_dev · 20,605
Telegram ranks this channel #2 of 54 here — alongside 53 others — read 28 September 2026
LSPosedArchives
@LSPosedArchives · 25,167
Telegram ranks this channel #2 of 36 here — alongside 35 others — read 14 September 2026
5ec1cff
@real5ec1cff · 37,726
Telegram ranks this channel #2 of 51 here — alongside 50 others — read 2 September 2026
QAuxiliary
@QAuxiliary · 44,776
Telegram ranks this channel #3 of 58 here — alongside 57 others — read 12 September 2026
HyperCeiler | Canary Test
@cemiuiler_canary · 19,480
Telegram ranks this channel #5 of 49 here — alongside 48 others — read 4 October 2026
Surfboard News
@surfboardnews · 28,419
Telegram ranks this channel #5 of 64 here — alongside 63 others — read 9 September 2026
哔哩漫游
@biliroaming · 56,265
Telegram ranks this channel #6 of 50 here — alongside 49 others — read 12 September 2026
KernelSU
@KernelSU · 62,696
Telegram ranks this channel #8 of 49 here — alongside 48 others — read 14 September 2026
SCENE Downloads
@scene2023 · 55,646
Telegram ranks this channel #12 of 50 here — alongside 49 others — read 12 September 2026
Github_2dust
@github_2dust · 91,770
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 17 August 2026
LuckyTool
@LuckyTool · 28,962
Telegram ranks this channel #15 of 56 here — alongside 55 others — read 12 September 2026
Nagram Tips
@NagramTips · 48,389
Telegram ranks this channel #17 of 49 here — alongside 48 others — read 30 August 2026
APatch Updates
@APatchChannel · 25,263
Telegram ranks this channel #18 of 37 here — alongside 36 others — read 14 September 2026
BSG MGC Public Release Channel
@Channel_MGC_BSG · 43,152
Telegram ranks this channel #23 of 58 here — alongside 57 others — read 7 September 2026
FlClash Channel
@FlClash · 47,993
Telegram ranks this channel #23 of 53 here — alongside 52 others — read 28 August 2026
Clash Verge Rev Channel
@clash_verge_re · 82,153
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 19 August 2026
NPatch
@NPatch · 19,394
Telegram ranks this channel #25 of 48 here — alongside 47 others — read 2 October 2026
QAuxiliary CI Builds
@QAuxiliary_CI · 19,573
Telegram ranks this channel #26 of 56 here — alongside 55 others — read 1 October 2026
HyperCeiler | Release & Notice
@cemiuiler_release · 27,156
Telegram ranks this channel #26 of 51 here — alongside 50 others — read 12 September 2026
Legado|开源阅读|频道
@Legado_Channels · 93,071
Telegram ranks this channel #30 of 61 here — alongside 60 others — read 17 August 2026
Matsuridayo GitHub
@MatsuriDayo · 45,476
Telegram ranks this channel #31 of 58 here — alongside 57 others — read 30 August 2026
FunProject
@QToolCI · 49,647
Telegram ranks this channel #33 of 51 here — alongside 50 others — read 12 September 2026

This channel appears in 34 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026
LabelLSPosed
DescriptionAndroid module framework based on EdXposed
Official sitehttps://lsposed.org/

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Xposed Framework (en.wikipedia.org)
“…|access-date=18 August 2026}}{{Cite web |title=LSPosed |url=https://t.me/LSPosed/324 |access-date=2026-09-11 |website=Telegram}} === Vector…”
read 13 September 2026

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

“LSPosed” (@LSPosed), 195,604 subscribers as measured 4 October 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.