Channel
@InstallerX
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Telegram's recommendations · Cite this entry
8,540subscribers
+64 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001942449571 |
|---|---|
| Type | Channel |
| Username | @InstallerX |
| Description | A modern and functional Android app installer. (You know some birds are not meant to be caged, their feathers are just too bright.) |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 18 August 2026 |
| On Telegram | t.me/InstallerX |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Aug 2026, 03:43 | 8,540 | +30 |
| 14 Aug 2026, 22:16 | 8,510 | +19 |
| 11 Aug 2026, 11:05 | 8,491 | +12 |
| 8 Aug 2026, 03:58 | 8,479 | +3 |
| 7 Aug 2026, 14:01 | 8,476 | no change |
| 7 Aug 2026, 13:49 | 8,476 | first reading |
18 posts held, back to 29 December 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 16 pagesof 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 18 posts for this entry, the most recent from 16 March 2026. An engagement rate over an empty window would be a number about nothing.
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.
Measured directly from 11 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.
463 reactions across 17 posts, in 7 distinct kinds. The most used accounts for 82.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 381 | 82.3% | |
| 🔥 | 44 | 9.50% | |
| 🤔 | 21 | 4.54% | |
| 😁 | 9 | 1.94% | |
| 👎 | 4 | 0.864% | |
| 😱 | 3 | 0.648% | |
| 🤬 | 1 | 0.216% |
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 18 of the 18 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 463reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 29 December 2025 to 16 March 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.
从我的想法来看，现在的各种 Claw 的正确路线应该是部署在手机上，比如小米的 MiClaw，能通过电源键或语音唤醒。 如果要用 A 手机控制 B 手机，就在 B 手机上装好接口供 Claw 调用。电脑上也装好接口给手机调用。以手机做为一个操作终端，其它一切设备提供接口去给手机调用。 而不是现在的好多把模型部署在电脑上，然后接到 qq、微信之类的聊天软件当中去。 甚至在家中设备或者服务器上部署好大模型，手机只有一个小型模型，下达任务后，简单任务就手机小模型处理，复杂任务就传到大算力设备上的模型去处理，手机只充当一个调度中心，调度算力和任务分配。 这样才算是真正的分布式系统，mcp 本质不就是 ai 远程调用一个工具，工具返回结果告诉你完成的怎么样？就和米家远程操控个洗衣机，洗衣机返回洗衣状态一样的？米家本可以把自己的协议作为 ai 时代的标准协议的，在如此深厚的米家生态设备基础上，哪轮得上现在的 mcp 协议上位。 本来…
👍74👎4🔥3🤬1
ruto-phone-mcp 则是我撰写并开源的运行在手机端或者任何能adb连接手机的位置。 你可以通过向其中加入更多的 skill（说明书），让你的AI更加聪明，更加灵活的帮你操作手机简化工作。 当然，还有第二方面，你可以建立一个MCP服务器把手机开放给OpenClaw等小龙虾。让手机的应用生态也能成为小龙虾🦞能管理的一部分，具体可以看上面的视频演示。 项目地址：https://github.com/iamr0s/ruto-phone-mcp/ 很遗憾的是我的工作太忙了，目前还有很多没有完成，Web界面、输入文字等
👍27
这是我写的一个说明书模板：微信使用说明书。 在这个程序当中，说明书的实现参考了Agent SKILLS的概念，也就是说渐进式披露。 在开始前AI只会知道它有哪些说明书，而不知道具体的内容，当要用到的时候，才会翻开相应软件的说明书进行阅读。 AI其实分不清猫狗，但是有一群数据标注员给AI提供了猫狗的样本图片，告诉AI猫的特征是什么，狗的特征是什么。 而今天，想要让AI真正学会帮助人类操控软件，自然要从撰写软件说明书开始。 欢迎大家分享自己撰写的软件说明书，讨论、完善、优化、分享。
👍9
还记得你第一次使用手机打开你刚下载的软件，你可能要经过好长一段时间的摸索，才能够掌握这个软件的使用技巧。 其实AI也是一样的，当你给AI下达任务，帮我给某某某发个红包时，AI看着屏幕上显示的画面，它可能不知道红包在哪个位置，屏幕内一堆扁平化的按钮图标，放大镜、箭头、三角形、圆形、椭圆到底在哪个里面？所以你可能经常看到AI在运行的过程中会犯错、会陷入死胡同，找不到要执行的任务的入口。 所以想要解决这个问题，只有两条路可以走，要么对AI进行专业的训练，也叫做模型微调。当训练的次数足够多，AI会使用的软件也会逐渐增多。 但是软件的个数是无限的，就像明天也可能会有一个新软件发布。所以，让AI学会如何使用软件，还有另一条路可走。就是给AI准备一个软件说明书。 当你让AI帮你给某某发红包时，在没有说明书时，AI仅通过屏幕分析，根本找不到红包功能在哪里。我们使用了这个软件成百上千次，当然知道放大镜可能是搜索按钮，一个箭头可能是返回，可…
👍16😱1
PicoClaw 小龙虾接收TG消息实现远程操控手机
🔥5
AI在阅读微信使用说明书后，一次跑通发红包流程。
😁6
联发科用不了 Shizuku 激活的试试刚传上去的新版本 prelease。 加了一个 Shizuku Terminal 模式，绕过UserService 的一个实现方式。 https://github.com/iamr0s/Ruto-GLM/releases
👍25🔥2
预览版发了 支持Shizuku和ROOT多种授权 统一界面 https://github.com/iamr0s/Ruto-GLM/releases
👍30
ROOT 做好支持了，等下发 今天发不了了，发现出了点 bug，修了再发
👍62🔥8
下载链接 Releases Ruto 正在参加 AutoGLM 实战派开发者激励活动！ 如果您喜欢这个项目，请为我们投上宝贵的一票，点一个 star。 🚀 Ruto (Run, Auto) v1.0.0 发布 Ruto 的第一个正式版本！Ruto 不仅仅是一个自动化工具，它是一个赋予 Android 系统“多线程并行”能力的 AI 任务框架。 AI 自动化任务: 基于 Open-AutoGLM 模型，Ruto 可以理解您的指令，并在您的设备上自动执行 UI 操作，如点击、滑动等。 虚拟屏幕与应用多开: 创建独立的虚拟屏幕，让应用在其上运行。这不仅能实现应用的多实例运行（应用分身），还能在后台执行任务而不干扰您的前台操作。 桌面级多窗口管理: 我们开发了一个全新的、类似桌面系统的多窗口管理界面，让您在 Android 上也能体验高效的多任务处理。 AI 对话集成: 内置了与大语言模型对话的界面，您可以轻松添加自己的模型 …
👍60🤔7🔥4
https://github.com/iamr0s/Ruto-GLM 麻烦帮我点 star 🙏🙏（参加智谱的比赛） 后续在这里发源码
👍52🔥4
准备做个任务执行的历史纪录，就把这个也做进去了
🔥17👍2
Showing the 12 most recent of 18 posts we hold for @InstallerX. 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.
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 1 seed channel's Telegram-generated recommendation list 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 18 August 2026 — this entry's latest reading, not the date you are reading this.
“InstallerX” (@InstallerX), 8,540 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/InstallerX.
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.