Idk

[Android 16 / HyperOS 3] configure tun interface: invalid argument (Xiaomi 13T)

Operating system

Android

System version

Android 16, Xiaomi 13T, HyperOS 3

Installation type

sing-box for Android Graphical Client

Client version

1.14.0-rc.3

Description

start or reload service: start inbound/tun[tun-in]: configure tun interface: invalid argument

This occurs immediately when starting the VPN with a TUN inbound, on every
attempt, regardless of the stack value used (tested system, gvisor,
and mixed — identical error every time).

Reproduction

{
"log": { "level": "debug" },
"dns": {
"servers": [
{ "tag": "dns-direct", "type": "udp", "server": "1.1.1.1" }
],
"final": "dns-direct"
},
"inbounds": [
{
"type": "tun",
"tag": "tun-in",
"interface_name": "tun0",
"address": [ "172.19.0.1/30" ],
"auto_route": true,
"strict_route": false,
"stack": "mixed",
"mtu": 1500
}
],
"outbounds": [
{ "type": "direct", "tag": "direct" }
],
"route": {
"auto_detect_interface": true,
"final": "direct"
}
}

Additional notes

• VPN permission is granted successfully; the error happens right after,
  during tun configuration.
• Disabling "MIUI/HyperOS optimization" in Developer options did not help.
• Disconnecting any other active VPN app on the device did not help.
• Tested with a minimal direct-only outbound (as above) to rule out any
  proxy/server-related cause — same result.
• This is a brand new device/OS combination (HyperOS 3, Android 16), so this
  may be a new incompatibility with this specific kernel/TUN driver version.

Integrity requirements

• I confirm that I have read the documentation, understand the meaning of all the configuration items I wrote, and did not pile up seemingly useful options or default values.
• I confirm that I have provided the simplest configuration that can be used to reproduce the error I reported.
• I confirm that I have provided the complete configuration files and logs.

Reproduce the supplied minimal TUN configuration on Android 16/HyperOS 3 with a Xiaomi 13T, then trace the TUN setup path that reports “configure tun interface: invalid argument.” Compare behavior across the tested stack values and verify the fix by starting or reloading the service successfully with the listed configuration.