有原生系统用KernelSU下安装小米互传模块运行成功的吗 整了老手机 想顺便看能不能修一下原生安卓14系统下的小米互传

Channel
小米快传|小米互传 频道
@r_mishare
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Cite this entry
163subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001536588152 |
|---|---|
| Type | Channel |
| Username | @r_mishare |
| Created | Between 1 August 2021 and 15 April 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/r_mishare |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 7 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 05:57 | 163 | -2 |
| 14 Aug 2026, 21:34 | 165 | +1 |
| 8 Aug 2026, 16:31 | 164 | no change |
| 7 Aug 2026, 23:10 | 164 | first reading |
Engagement
15 posts held, back to 15 April 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 1 page 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 15 posts for this entry, the most recent from 2 July 2024. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 2m 48s
- Average length
- 2m 48s
Measured directly from 1 video 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
27 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 92.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 25 | 92.6% | |
| 😁 | 2 | 7.41% |
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 9 of the 15 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 15 April 2022 to 2 July 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Recent posts
FuckMIShare v1.2 禁止小米快传的10分钟自动关闭 #Xposed #FuckMIShare
👍1
将小米互传更新到了2.15.0 (手搓的,GithubAction自动打包的脚本出了一些问题) 优化了权限获取(首次安装需从桌面启动,会自动获取需要的权限) 2.15.0的版本会10分钟自动关闭(政策要求) 懒得修做Hook去删除这个功能了(我回MIUI了,想做的自己fork我的模块仓库,提交pr) https://github.com/iamr0s/MiShare-Magisk-Module/releases/tag/v2.3-4090121866-941cba2
👍4
Channel name was changed to «小米快传|小米互传 频道»
在酷安发了小米快传的帖子,被屏蔽了~ 允许自由分享的我的小米快传版本,二改需要授权。 转发和二改需要带上打赏链接: https://iamr0s.github.io/post/1/ 打赏:Github
👍8😁1
Photo, posted without a caption
👍4
捐赠通道:Github Blog v2.2 禁止混淆mishare-sdk.jar,解决部分闪退bug。 自动清理设备记录,解决冗余的设备列表和设备不在身边的bug。 v2.1 修复搜索设备列表闪退 优化搜索设备界面和逻 优化代码结构 更新SDK文件 新增点击列表发送
😁1
v2.1 实现文件正常收发 已撤包
👍1
v2.0版本已更,可在magisk中检测更新。 还不能发文件,unbind会导致Service发生错误,下个版本修。
👍2
后续更新模块可直接在Magisk中检测和下载更新。
👍4
上个版本未能成功将模块打包进去。 ### v1.7 更换实现方式为Lspatch实现,关于什么是Lspatch请参考:https://github.com/LSPosed/LSPatch 。 具体实现请参考:https://github.com/iamr0s/XposedMiShare 。 修复全局弹出对话框。 新增完全自定义设备名称。
File, posted without a caption
Showing the 12 most recent of 15 posts we hold for @r_mishare. 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.
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“小米快传|小米互传 频道” (@r_mishare), 163 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/r_mishare.
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.