Android Troubleshooting

Find the message or the symptom you see, then follow the steps. Messages are quoted as the English app shows them. For problems with Throne desktop, see Troubleshooting.

The VPN does not start or has no traffic

When a start fails, Throne shows the reason in a bar at the bottom of the screen, with a Logs button. The message stays until you swipe it away, tap Logs, or start again.

"Permission denied to create a VPN service"

Android did not give Throne the VPN permission. Usually you declined the request. Android also refuses without asking when another VPN app is set to Always-on VPN.

1. Tap the connect button again and allow the request.
2. If no request appears, open Android's VPN settings and turn off Always-on VPN for the other app.
3. If Throne shows "VPN confirmation unavailable", your device has no screen for this request. See VPN permission.

Android refuses to create the VPN

Android gave the permission but then refused to create the VPN interface. The "Failed: …" message then usually contains "configure tun interface".

1. Disconnect other VPN apps, and check in Android's VPN settings that none of them is set to Always-on VPN.
2. Restart the device and connect again.

Other messages when you connect

Message	Cause	What to do
"Please select a profile"	No profile is selected.	Tap a profile, then connect.
"Failed: Profile … has a type this build cannot use: …"	The profile type exists only on desktop, for example Tailscale or Extra Core.	Use another profile. See below.
A message about routing or WARP	A problem in the routing profile or in the WARP settings.	See Routing errors and WARP errors.
Any other "Failed: …" message	The core reported an error.	Tap Logs and read the last lines.

Connected, but nothing loads

1. Tap the bar at the bottom of the screen. "Success: HTTP handshake took …ms" means that the profile works. "Failed: …" means that the profile or its server does not work.
2. If it failed, tap ⋮ → URL test and select a profile that works. See Testing & Auto Selector.
3. Check per-app proxy: open Settings → TUN / VPN → Apps VPN mode to see the app list. With Proxy, only the selected apps use the VPN. With Bypass, the selected apps do not use it. If no app is selected, all apps use the VPN. See Per-app proxy.
4. Switch to the Default routing profile with ⋮ → Routing profile, and test again. If it works now, a rule in your own routing profile is the cause. See Routing.
5. Check DNS: Settings → DNS → Remote DNS (default https://8.8.8.8/dns-query). Try another server. See DNS.
6. If you turned on Tun IPv6 or Tun routing in Settings → TUN / VPN, turn them off and test again. Use Tun IPv6 only when your server supports IPv6. If some apps or websites fail while others work, set MTU on the same screen to 1500 and reconnect.
7. To find out whether VPN mode causes the problem, set Settings → General → Service mode to Proxy only and connect. Then set an app that has its own proxy setting to the SOCKS5 proxy 127.0.0.1, port 2080 (see Settings → Inbound → Proxy port). If that app works, go back to VPN mode and try another TUN implementation. See VPN & Proxy Modes.

No internet while Throne is off

Android's Always-on VPN is on together with "Block connections without VPN". Android then blocks all traffic while Throne is not connected. Connect Throne with a working profile, or turn this option off in Android's VPN settings. See Always-on VPN.

Some apps have no internet after you disconnect

Settings → DNS → Enable FakeDNS gives apps fake addresses that work only through Throne. Throne warns about this: "Other apps may need a restart to reconnect to the network after the proxy stops". Restart those apps, or turn off Enable FakeDNS.

Throne stops in the background

Typical signs: the VPN disconnects while the screen is off, the notification disappears, the connection stops working after you unlock the phone, or the buttons of the notification or a widget do nothing.

1. Open Settings → General → Battery optimization. It must show "Unrestricted". If it does not, tap it and allow Throne to run without restrictions. See Battery optimization.
2. Open Settings → General → Background & auto-start. Allow Throne to start automatically and to run in the background. See Manufacturer settings.
3. Keep Reset outbound connections when device wakes from sleep on (the default). When the device wakes from deep sleep, Throne closes the old connections, and apps connect again. Keep Reset outbound connections when network changes on as well.
4. Turn on Always-on VPN, so that Android starts Throne again by itself. See Always-on VPN.
5. On some devices, swiping Throne away in the list of recent apps stops it. Leave it in the list, or lock it there if your device offers this.

Subscription problems

When you update a subscription by hand, errors appear at the bottom of the screen as the group name followed by the message. Automatic updates write their errors only to Logs.

Message	Cause	What to do
"Request with proxy but no profile started."	Use proxy is on in Settings → Subscriptions, or the service mode is Proxy only, and Throne is not connected.	Connect first. In VPN mode, you can also turn off Use proxy.
"Error transferring … - server replied: …"	The server refused the request, for example with 403 or 404.	Check the URL. Many providers accept only some apps: set the user agent your provider names, or turn on HWID sending.
"No profiles found in the subscription; it was left unchanged."	The answer contains no profiles that Throne can read, for example a web page.	Often the same user agent or HWID problem. Also check the import formats.
"Insecure redirect"	The server redirected an https:// URL to http://. Throne does not follow such redirects.	Ask your provider for the correct https:// URL.
"Too many redirects"	The server redirects in a loop.	Check the URL with your provider.
"Response larger than 64 MB"	The subscription is too large.	Ask your provider for a smaller list.
"Still in use, so kept instead of deleted" or "The running profile was kept."	The update, or a clean-up option after it, would remove the profile you are connected to, so Throne kept it. You see this in the change report or in Logs.	Nothing. To remove it anyway, turn on Allow stopping the active profile in Settings → Subscriptions.

To change the user agent or HWID for one group, open Groups in the drawer, tap the Edit button of the group, and open Advanced. It has User agent and Send HWID. The settings for all groups are in Settings → Subscriptions. See User-Agent and HWID.

The provider accepts updates only from your own connection

While Throne is connected, its own requests, such as subscription updates, also go through Throne and follow your routing profile. Some providers accept update requests only from your own internet connection. Add a rule that sends the domain of the subscription to direct:

1. Open Routing in the drawer. Open the menu of the current routing profile and choose Edit.
2. Choose Add rule.
3. Set Outbound to direct. In Domain suffix, enter the host name of the subscription URL, for example sub.example.com.
4. Save the rule and the routing profile. Place the rule above other rules that match the same domain.

If the provider wants the request to come from one of its servers, choose that server as the Outbound instead.

Routing errors

Message	Cause	What to do
"The routing profile is referencing outbounds that no longer exist, consider revising your settings"	A rule sends traffic to a server profile that was deleted, for example by a subscription update.	Open the routing profile (Routing → its menu → Edit). Rules with a deleted server show "Missing server (#…)". Choose another outbound.
"Unknown rule-set "…" in rule "…" of routing profile "…""	A rule uses a rule-set name that Throne does not know.	In Routing, tap Refresh repository list, or use the URL of an .srs file.
"The rule-set list is not available. …"	The list of rule-set names was not downloaded.	In Routing, tap Refresh repository list.
"raw routing profiles are not supported on Android"	You imported a raw routing profile from Throne desktop.	Use a structured or remote routing profile.

WARP errors

Message	Cause	What to do
"WARP is enabled but its config has not been generated. Generate it in Settings › Routing › WARP."	WARP is on, but there is no WARP config for the selected mode.	Open Settings → Routing → WARP and tap Generate WARP config.
"Failed: Warp is enabled but its config has not been generated. Please generate the Warp config first in Routing Settings."	The same problem, shown when you connect.	The same.
"Failed to generate WARP config"	The registration at Cloudflare failed. It is blocked in some networks.	Connect to a working profile, turn on Use proxy in Settings → Subscriptions, and generate again.
No message, but nothing loads while WARP is on	In WireGuard mode, WARP needs a profile that forwards UDP.	Set Mode to MASQUE and HTTP version to HTTP/2, which needs only TCP. Generate a config for the new mode.

See Cloudflare WARP.

Update problems

• "The download is signed with a different key than this build, so Android cannot install it as an update. Back up, uninstall this build and install the release from GitHub." Your copy was not signed with the Throne release key. Create a backup (drawer → Tools → Create backup), uninstall Throne, install the APK from GitHub, and restore the backup.
• "This update cannot be installed from the app (…). Download it from the release page." Tap Open in browser, download the APK for your device and install it over the current app.
• "Could not check for updates": Throne could not reach GitHub. Connect to a working profile and try again.
• Android does not install 2.0.0 over an older Throne for Android. See Upgrading from 1.x or NekoBox.

A profile works on desktop but not on Android

1. Check the profile type. Tailscale and Extra Core profiles do not work on Android. TLS spoof settings are ignored on Android.
2. Compare the settings that change how profiles connect: the presets in Settings → Presets (multiplex, TLS fragment, TLS tricks, uTLS) and Settings → Core → Xray VLESS preference. The VLESS preference is applied when profiles are imported, so update the subscription again after you change it. See sing-box vs Xray.
3. To get the same settings as on desktop, restore a desktop backup. See Moving between desktop and Android.
4. If it still fails, report the problem with the logs of both apps.

Logs

Open Logs in the drawer. It shows the log of the core. The toolbar has Update (reloads the view), Share logs and Clear logs. The menu has Save logs…, Hide sensitive data and Hide destinations.

Share logs and Save logs… create one text file with:

• a header with the app and core versions, the Android version, the device model, the ABI, the service mode and some settings that contain no secrets;
• the core log, and the core log of the previous connection;
• the last 2000 lines of the app's system log.

Hide sensitive data is on by default. Keep it on. In the exported file it replaces:

• the path and query of every URL, and user names and passwords in URLs (the host name stays);
• passwords, keys, tokens, UUIDs and similar values;
• server addresses, SNI and host names in the configuration;
• public IP addresses (private addresses stay);
• Wi-Fi names.

Hide destinations also hides the domain names in connection and DNS lines. You can turn it on only while Hide sensitive data is on, and Throne does not keep it after the app restarts. The hiding is best effort: read the file before you post it.

For more detail, set Settings → Core → Log level to info or debug, and tap Apply to restart the app. Reproduce the problem, then share the logs. Set the level back to warn afterwards.

After a crash, Throne restarts and offers to share a log file with sensitive data hidden.

Reporting a problem

Report problems with the Android app at github.com/throneproj/ThroneForAndroid/issues. Include:

• what you did, what you expected and what happened;
• the log file from Share logs or Save logs…, with Hide sensitive data on;
• the profile type (for example VLESS with REALITY) and the service mode.

The log file already contains the app version, the core version and the device model. For general advice, see Reporting a Bug.