Throne for Android

Android GUI proxy utility, empowered by Sing-box

Supports Android 7.0 (API 24) and newer, including Android TV.

Documentation: throneproj.github.io

Supporting Throne

If Throne is useful to you, you can support its development with crypto (USDT, USDC, TRX or Monero) or through GitHub Sponsors.

Note on upgrading from 1.x

Releases from v2.0.0 on are signed with a new key, so Android refuses to install them over a 1.x release (signature conflict). Uninstall the old release first, then import your subscriptions and profiles again: old local configurations are not migrated.

GitHub Releases (APK)

Features

• Groups and subscriptions that work like Throne desktop: per-group subscription options (filters, clean-up, URL test after an update), front / landing proxy, HWID headers, scheduled updates with change reports
• Backups in the desktop's .thrbackup format, restorable on either side: save, share or sync over WebDAV
• Route profiles shared with desktop, preloaded from routeprofiles, plus Android-only rule conditions: apps, Wi-Fi network (SSID / BSSID), network type and metered networks
• Auto Selector profiles that keep the best server of one or more groups ranked and switch automatically
• Cloudflare WARP: registration (WireGuard or MASQUE identity) and a built-in WARP mode for routing
• URL, IP / country and speed tests, with a bulk-test panel (live progress, latency histogram, fastest servers, sort / remove unavailable / connect to fastest)
• The sing-box dashboard built in (live traffic, connections, logs)
• JSON editor with sing-box schema checking, completion and formatting
• Home-screen widgets, a quick settings tile, and server switching from the notification
• Android TV: launcher banner, D-pad navigation, previous / next server

Supported protocols

• SOCKS
• HTTP(S)
• Shadowsocks
• Trojan
• VMess
• VLESS
• TUIC
• Hysteria
• Hysteria2
• AnyTLS
• Mieru
• Snell
• NaïveProxy
• Juicity
• TrustTunnel
• ShadowTLS
• Wireguard
• AmneziaWG
• MASQUE
• SSH
• Xray VLESS
• OpenVPN/OpenConnect
• Custom Outbound (Both Sing-box and Xray)
• Custom Config (Both Sing-box and Xray)
• Chaining outbounds

Subscription Formats

Various formats are supported, including share links, various JSON representation of Sing-box configs, and v2rayN link format as well as limited support for Shadowsocks and Clash formats. Only the outbounds (servers) of a subscription are imported; its routing rules are ignored.

Deeplinks are also supported, read the documentation for more information.

Credits

• throneproj/sing-box, a fork of SagerNet/sing-box
• throneproj/Xray-core, a fork of XTLS/Xray-core

Android GUI:

• MatsuriDayo/NekoBoxForAndroid
• SagerNet/SagerNet
• shadowsocks/shadowsocks-android

FAQ

How does this project differ from NekoBox for Android?
It started as a NekoBox for Android fork. v2.0.0 replaced its core and data model with Throne desktop's: the same sing-box and Xray core, profile types, share links, route profiles and backup format. The legacy plugin system was removed, since the built-in core covers what the plugins provided.

Where are the downloadable route profiles/rulesets coming from?
They are located at the routeprofiles repository, the same one Throne desktop uses.

Why are some servers skipped when I import a link or a subscription?
As on desktop, Extra Core, Chain and Auto Selector profiles are never imported from links, subscriptions or shared route profiles; create them in the app instead. Nodes the app cannot run are skipped too, and the import reports what was left out.

Star History