Android12 beta 4.1已经发布 https://developer.android.com/about/versions/12/release-notes Fixed an issue where, after connecting the phone to a VPN, the phone could not connect to the internet. (Issue #196237480)

Channel
ShadowsocksRb
@ShadowsocksRb
On this record: Topic · Growth · Engagement · Posts · Handles named that no longer answer · Cite this entry
634subscribers
-21 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001163998818 |
|---|---|
| Type | Channel |
| Username | @ShadowsocksRb |
| Created | 8 October 2019 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 20 November 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 20 November 2026 |
| On Telegram | t.me/ShadowsocksRb |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 20 Nov 2026, 14:17 | 634 | -2 |
| 11 Nov 2026, 00:51 | 636 | -1 |
| 28 Oct 2026, 06:07 | 637 | -3 |
| 21 Oct 2026, 15:18 | 640 | -2 |
| 14 Oct 2026, 03:16 | 642 | -1 |
| 6 Oct 2026, 14:39 | 643 | -2 |
| 25 Sept 2026, 18:20 | 645 | +1 |
| 11 Sept 2026, 04:20 | 644 | -2 |
| 2 Sept 2026, 17:56 | 646 | -2 |
| 27 Aug 2026, 12:54 | 648 | -2 |
| 21 Aug 2026, 07:13 | 650 | -2 |
| 14 Aug 2026, 22:06 | 652 | -3 |
| 6 Aug 2026, 17:30 | 655 | no change |
| 6 Aug 2026, 13:24 | 655 | first reading |
Engagement
17 posts held, back to 8 October 2019 — 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 17 posts for this entry, the most recent from 26 August 2021. An engagement rate over an empty window would be a number about nothing.
Recent posts
https://issuetracker.google.com/issues/196271165 ShadowsocksRb 不会处理该问题,这是 beta4 自身问题,任何应用的VPN功能都无法正常工作,可能在 beta 4.1或 beta5 由系统更新修复。 可以工作的代理应用是为网络设置了HTTP代理,该HTTP代理信息仅对应用起建议作用,与WLAN的手动设置代理完全相同。
适配 Android 12 加入配置文件搜索 支持配置socks5,当未连接服务时会通过此代理更新订阅(对于HTTP代理,请使用系统WIFI设置进行配置,shadowsocksRb没有提供必要) =============== Android 12 正式发布后推送更新提示。 现在的版本是 beta 内测,不是稳定版。有问题请尽快反馈。
bot已经注销,原讨论群进入只读状态。 新讨论群为本频道关联群组,供自助讨论。
由于持续无法同步上游,本项目停止维护,除非 Android 平台出现影响使用的问题,否则不再更新。 推荐更换 @clash_for_android_channel Clash具有所有主流代理协议支持,包括SSR: https://github.com/Dreamacro/clash/pull/805 PS: SSR转Clash https://acl4ssr.netlify.app
适配 Android11; 使用cloudflare测试延时; 保护隐私,修改对外连接的UserAgent去掉设备标识符; 卸载时支持选择保留数据,需要系统支持。
在将SSR插件移植到shadowsocks-rust之前,本项目无限期暂停同步上游。
File, posted without a caption
https://github.com/shadowsocks/shadowsocks-android/pull/2454
来自上游的更新:修复绕过局域网。
支持批量修改UDP配置。 更新订阅界面,移除自动更新订阅。 修正了多项错误,并提升了稳定性。 来自上游的更新: 支持订阅,支持 IPv6 ACL规则。
修复gfwlist使用问题,允许运行时更新自定义ACL。 添加保存日志功能,在关于的右上角。(日志含有敏感内容,切勿公开分享) 修复混淆后shortcut图标资源丢失。 来自上游的更新:修复绕过局域网问题;默认关闭IPv6与TCP fast open,处理个别应用连接问题;自动删除服务器名前后空格。
Showing the 12 most recent of 17 posts we hold for @ShadowsocksRb. 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.
Handles this channel named that no longer answer
- Dead references
- 1
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 1
- vacant every time we have ever looked
@ShadowsocksRb 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.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 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 20 November 2026 — this entry's latest reading, not the date you are reading this.
“ShadowsocksRb” (@ShadowsocksRb), 634 subscribers as measured 20 November 2026. Telegram Register, tgregister.com/channel/ShadowsocksRb.
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.