Full mode Availability on android

[Mohammad48h]

Hello , i have a active tunnel node and a app script deployment ( CodeFull.gs) and need to use Full tunnel mode and load Telegram and other apps with it however i have some problems. first of all:

• I've set the VPS's address and TUNNEL_AUTH_KEY and AUTH_KEY in the deployment

• the /health GET returns ok

• I'm sure i have set all keys correctly

However,, mhrv still decides to forward tcp traffic directly and websites through google servers although I have set the Deployment url of the deployment which has been set to tunnel though my tunnel node.
also, IP lookup websites dont show my vps's ip address instead they show google's ip address and my original ip address beacuse of the forwarded for header not getting stripped correctly
does the android client of mhrv rs not support full mode or is the problem something else?

[therealaleph]

Reviewed via Anthropic Claude.

@Mohammad48h — your tunnel-node is fine (/health returns ok). The issue is client-side mode selection.

Android UI doesn't expose a "Full mode" checkbox yet — to use Full mode on Android, you must edit config.json directly:

1. Stop mhrv-rs Android app.

2. Find the config: /data/user/0/com.therealaleph.mhrv/files/config.json — accessible via:

   • Easier: in mhrv-rs Android app → Config → "Edit JSON" button (if visible).
   • adb method: adb pull /sdcard/Android/data/com.therealaleph.mhrv/files/config.json → edit on PC → adb push back.

3. Add/change:

4. Make sure:

   • Your tunnel-node deployment ID is the NEW one with CodeFull.gs (not the old Code.gs).
   • Both TUNNEL_AUTH_KEY (in tunnel-node Docker env + in CodeFull.gs source) match exactly.

5. Restart mhrv-rs Android app.

Diagnostic: log first 30 lines after restart should show mode=full + tunnel POST https://<your-vps>:443/api. If it still says apps_script mode, the JSON edit didn't persist (file permissions on Android storage are flaky — try the in-app "Edit JSON" button instead).

About Telegram: even with Full mode + working tunnel, Telegram Android uses MTProto-over-TCP not HTTP, so it bypasses HTTP/SOCKS5 proxy stacks. mhrv-rs detects + raw-tcp routes it which doesn't help with DPI. Telegram needs an MTProto-aware proxy (xray with mtproto inbound, or Telegram's built-in MTProxy). Can chain: Telegram → xray:1080 SOCKS5 → mhrv-rs:8086 SOCKS5 (xray strips MTProto envelope, then mhrv-rs tunnels the inner TCP).

Leaving open until your Android Full mode is verified — please confirm mode=full shows in the log after the JSON edit.

[therealaleph]

Correction (the JSON in step 3 got dropped by shell escaping):

{
  "mode": "full",
  "script_id": "<your CodeFull.gs deployment ID>"
}

The rest of the steps still apply.