还得是一加,就是喜欢乱改内核,gki不就是统一吗?文件操作结构体这个byd删了一个字段搞我偏移错误,今天一加到了才定位到问题,还是小米好用,你可以发现刷模块变砖或者升级root管理器卡开机,百分之80都是一加
👍68❤6👎2

Channel
@bbtswd
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
144,394subscribers
-8,258 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1002097645414 |
|---|---|
| Type | Channel |
| Username | @bbtswd |
| Created | Between 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 October 2026 |
| Measurements held | 38 |
| Confirmed unchanged | 1 time, most recently 15 October 2026 |
| On Telegram | t.me/bbtswd |
Gaming — 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 9 August 2026 and assigned it the closest of 31 fixed categories, at 45% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Oct 2026, 07:19 | 144,394 | -187 |
| 14 Oct 2026, 03:28 | 144,581 | -195 |
| 11 Oct 2026, 22:38 | 144,776 | -353 |
| 7 Oct 2026, 10:02 | 145,129 | -404 |
| 2 Oct 2026, 12:36 | 145,533 | -1,337 |
| 18 Sept 2026, 16:00 | 146,870 | -189 |
| 16 Sept 2026, 08:38 | 147,059 | -87 |
| 14 Sept 2026, 12:42 | 147,146 | -59 |
| 13 Sept 2026, 00:20 | 147,205 | -152 |
| 11 Sept 2026, 04:41 | 147,357 | -304 |
| 8 Sept 2026, 07:59 | 147,661 | -388 |
| 5 Sept 2026, 02:57 | 148,049 | -159 |
| 3 Sept 2026, 09:29 | 148,208 | -111 |
| 2 Sept 2026, 06:45 | 148,319 | -115 |
| 1 Sept 2026, 06:58 | 148,434 | -147 |
| 31 Aug 2026, 06:13 | 148,581 | -122 |
| 30 Aug 2026, 05:55 | 148,703 | -110 |
| 29 Aug 2026, 05:53 | 148,813 | -18 |
| 28 Aug 2026, 06:44 | 148,831 | -157 |
| 27 Aug 2026, 03:33 | 148,988 | first reading |
116 posts held, back to 23 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 157 pages of 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 13 October 2026 |
|---|---|
| Posts held | 116 (23 July 2026 – 13 October 2026) |
| Views total | 562,630 |
| Reactions total | 4,639 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 15 Oct 2026, 02:06 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.
Measured directly from 17 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.
8,318 reactions across 116 posts, in 33 distinct kinds. The most used accounts for 79.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 6,650 | 79.9% | |
| ❤ | 1,023 | 12.3% | |
| 🤣 | 171 | 2.06% | |
| 😱 | 54 | 0.649% | |
| 🍌 | 47 | 0.565% | |
| 🥰 | 38 | 0.457% | |
| 🤩 | 36 | 0.433% | |
| 👎 | 33 | 0.397% | |
| 🔥 | 32 | 0.385% | |
| 😍 | 32 | 0.385% | |
| 💩 | 31 | 0.373% | |
| 🤡 | 27 | 0.325% | |
| 🖕 | 26 | 0.313% | |
| 🤓 | 20 | 0.24% | |
| 😁 | 19 | 0.228% | |
| 🌭 | 12 | 0.144% | |
| 🤔 | 9 | 0.108% | |
| 🤮 | 9 | 0.108% | |
| 👏 | 7 | 0.084% | |
| 😭 | 7 | 0.084% | |
| 13 further kinds | 35 | 0.421% |
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 116 of the 116 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 8,318 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 116 most recent posts we hold, published 23 July 2026 to 13 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.
还得是一加,就是喜欢乱改内核,gki不就是统一吗?文件操作结构体这个byd删了一个字段搞我偏移错误,今天一加到了才定位到问题,还是小米好用,你可以发现刷模块变砖或者升级root管理器卡开机,百分之80都是一加
👍68❤6👎2
我们是什么陀螺仪,陀螺仪还能是虚拟的啊,在哪里才是最重要的 硬件中断(陀螺仪)->内核子系统->HAL->[我们在这里]内核->native层[模块陀螺仪hook c在这里]->java层[xp hook差不多在这里]->App
👍91❤6🥰3😈3
市面上有哪家驱动支持pte断点? 要支持寄存器读取与写入 rt最新版仅支持读 Paradise虽然API表面上支持读取与写入,但是调用写入的时候发现调用失败了😅 打印一下参数也是对的 其实我想试试pte断点写入的隐蔽性的,实在不行就只能用基于开源wxshadow了 但是不想适配杂七杂八的内核API
👍134❤4🖕3🤯3😍1
Signed zowooll
平板好白啊,睡了睡了这周休息会
👍107🍌39🤩16🤣11😍10❤9🖕4💩3
Signed Neko
衍生更新10月10日 ◾️仅增加一个超广角,此版本仅支持ditpro_kpm133版本 ◾️都没有问题再支持dits ◾️超广角使用方法:[打开辅助设置->超广角->调到你想要的视野->开始断点->游戏设置->人称设置->第三人称镜头视野随便调一个值,变动就行,你松手的时候断点触发就ok了,一把一调,上面操作请在5秒内完成]
👍137❤4🥰2🤔1
ditpro_kpm[133] ◾️因为衍生和腹黑需要,增加硬件断点能力 [5.15 6.1 6.6 6.12] ◾️ko延后,看看适配范围
👍136❤7🤣3🥰1
byd小米,睡一觉醒来手机怎么绿线了,小米通病吗我看很多人都有这个问题,用3年突然绿线了,二手一加ace5pro和至尊版那个强,刚好一加用驱动有bug,能排一下问题
👍123❤4🖕3🥰1
好长时间没有发反馈图了,我看有人反馈打PUBG全球服梯子延迟很大,我给你们推荐一个几乎免费的,一个月只用1块100G流量每天签到还送1-10G,根本用不完 https://16.76.177.124/auth/register?code=OOAXkCBo
👍92❤1🥰1
Signed Neko
⭐广告位 10月10-17日 17:19⭐ ⚡️止痛药内核已公益!真的已经公益了!老牌项目 😄止痛药😇🙃😉加入点我 @ZTYNH6 💎采用硬件断点追踪,无模块陀螺仪漏打 (兼容4-6系全系设备 丝滑流畅不卡顿) ✔️支持坐标解密以及数组(算法)解密 ✔️拥有安全区信息以及头甲包绘制功能 还拥有战斗模式 开启后隐藏部分绘图,以简洁为主不挡视野方便战斗 ✔️驱动为自写独家驱动 稳定性杠杠的 ⭐拥有【烟雾过滤】【载具不追】【掉血追踪】一系列人性化功能选项 部分实用功能介绍如下:🌟 ⚡️支持每把枪械单独调节自瞄范围圈以及追踪范围圈,支持单独调节枪械的追踪概率 ⚡️快捷控件拥有:自瞄控件/追踪控件/狂暴模式控件 狂暴控件介绍:遇到绝境或者打不过的情况下开启狂暴模式 参数以及范围大小自动拉满头追(慎重使用) ⚡️拥有自保模式,打开后五米内敌人靠近范围圈自动拉300范围 ⚡️追踪部位:头部/胸部/指哪打哪 《指哪打哪:有15个部位 非常真…
👍69❤3
启动器同步更新了衍生新版本,我刚从学校回来,启动器还有啥要更新的可以发在消息下方,我也想给你们更新更多东西,但目前我不负责辅助更新啊,如果我后期可以给你们更新辅助肯定给你们更新漏打那些的
👍66❤2🔥2🥰1
Signed Neko
我觉得有个透视,软自喵和广角就够了,我觉得挺完美的
👍63🤣9❤4🥰1
⭐广告位 10月9-16日 2:51⭐ Wink(原FK)页表断点追无视检测 解决硬件断点槽位检测拉闸的问题👍 ✅采用APK云更新—伪装Wink ✅UI简洁含多种绘图 功能全面 ✅Phys X模型漏打 不动内存 ✅独家HOOK无痕驱动适配天玑 ✅独家断点解密不和谐不动内存 🔥内核级陀螺仪自瞄无视检测 🔥PTE断点追踪无任何过检测 🎮数组解密 闪框解密 密钥解密 全网首发拦截坐标加密下发功能 ✅纯算法陀螺仪压枪+断点无后 ✅迫击炮 大地图雷达 巡查预警 🎮添加秒刷新美化完全裸奔✅ 💝目前已有2100张高质量反馈 对标所有高价项目 稳定性全面拉满 😇🙃😉 https://t.me/WinkNH
👍27❤9
Showing the 12 most recent of 116 posts we hold for @bbtswd. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@bbtswd named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 15 October 2026 — this entry's latest reading, not the date you are reading this.
“巴巴托斯公益” (@bbtswd), 144,394 subscribers as measured 15 October 2026. Telegram Register, tgregister.com/channel/bbtswd.
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.