lgg
Add and maintain a dedicated Android networking section covering VPN/proxy/tunneling clients, local censorship/DPI-bypass tools, and diagnostics. ## Completed - [x] Add the VPN/proxy clients currently collected from the device screenshots: - [x] v2RayTun - [x] sing-box (SFA) - [x] V2rayGG - [x] Shadowrocket for Android (Cross Ltd.) - [x] Tailscale - [x] V2BOX - [x] V2Ray Client+ / V2ray VPN Client: Xray Vless - [x] Happ — Proxy Utility - [x] Hiddify - [x] Add **Outline Client** and document that it is compatible with standard Shadowsocks servers. - [x] Add **ByeByeDPI / ByeDPI for Android** as a separate local DPI/censorship-bypass tool. - [x] Clearly separate: - remote VPN/proxy/tunneling clients; - local DPI/censorship-bypass tools; - diagnostic tools such as RKNHardering. - [x] Add source repositories when verified, otherwise official sites / Google Play. - [x] Add install links and important caveats (BYO server/config where applicable, closed-source status, Android VPN-slot conflict, etc.). - [x] Update both `README.md` and `README-ru.md`. ## Remaining - [ ] Add a dedicated **practical Android networking guide** centered on the recommended pair: **v2RayTun + ByeByeDPI**. - [ ] Explain when to use v2RayTun and when to use ByeByeDPI. - [ ] Explain the Android `VpnService` limitation and the correct ways to combine tools without fighting for the same VPN slot. - [ ] Document **correct routing / split-tunneling in v2RayTun**. - [ ] Document **per-app routing**: how to enable the tunnel/bypass only for selected applications instead of the whole device. - [ ] Document ByeByeDPI split tunneling / per-app mode. - [ ] Explain how to add convenient **home-screen shortcuts/widgets** for connect/disconnect or profile actions where the app/launcher supports them. - [ ] Explain Android **Quick Settings tiles** (the pull-down control panel with Wi-Fi/Bluetooth/brightness controls) and how to add/connect relevant VPN/proxy actions there when supported. - [ ] Document **autostart / start-on-boot**, battery-optimization caveats and background reliability. - [ ] Add **MacroDroid automation recipes** for advanced scenarios, for example: - enable a tunnel when selected apps are opened; - disable it after those apps close; - use different behavior on Wi-Fi vs mobile data; - react to a specific SSID/network; - launch a selected profile/config; - recover/restart the service if Android/OEM kills it. - [ ] Keep screenshots/labels version-specific and note the Android/app version tested. - [ ] Compare the other clients and document which ones are best suited to specific scenarios (for example: VLESS/Reality, sing-box profiles, Shadowsocks/Outline, mesh/private-network access). - [ ] Re-check version-sensitive clients periodically, especially projects whose source/distribution status changes. The catalog is now populated; this issue stays open for the hands-on guide, routing/automation examples and recommendation/comparison pass.