рабочий вариант, но скороть 10 МБит

clients/android/README.md

@@ -17,19 +17,18 @@ Implemented now:
 - run as a normal fabric node with the `vpn-client` service role. The local
   `VpnService` TUN is the IPv4 ingress for that node, and packet channels are
   routed by the farm to an authorized `ipv4-egress` pool. The supported
-  dataplane is the QUIC fabric runtime only. HTTP batch forwarding, WebSocket
-  packet relay, direct backend packet relay, and old VPN protocols are removed
-  from the runtime path.
-- user-facing HOME-first screen: connect/disconnect is primary, while backend,
-  cluster, organization, login, and password are kept in the settings dialog;
+  dataplane is the QUIC fabric runtime only. The Android node never contacts
+  the farm over HTTP; control, profile refresh, channel request, packet uplink,
+  and downlink all go through the farm protocol.
+- user-facing HOME-first screen: connect/disconnect is primary, while cluster,
+  organization, login, and password are kept in the settings dialog;
 - saved connection settings in app preferences so repeat connects do not require
   retyping the profile.
 - encrypted refresh-token storage through Android Keystore. If the trusted
   device session is revoked or expires, the app asks for the password once and
   then rotates the device keys/profile again.
 - no separate diagnostic foreground service: runtime status is reported by the
-  node/VPN service itself, so the Android build does not keep a parallel legacy
-  control process alive.
+  node/VPN service itself.
 
 This is still a lab runtime. The required target model is Android as a farm
 node with the `vpn-client` role. The VPN service must attach to the mesh as