Throne for Android: Developed an Android client for Throne

[dsfkjlweuyr]

Hello everyone and the ThroneProj team,

I am writing this post to share a community effort to bring Throne to Android, and to open a discussion about potentially bringing this project under the official ThroneProj organization.

Background & Motivation

As many of us know, the original NekoBox series was one of the most versatile and well-maintained Sing-box clients across multiple platforms. However, after the PC version was discontinued, it found new life and active development here as Throne (Desktop).

On the Android side, while the original repository exists, official updates have been silent for over half a year. The community has seen various forks pop up to keep features and core updates alive, but the lack of an "official home" makes it hard for users to find a unified, trustworthy Android client that matches the evolution of Throne Desktop.

I didn't want to see such an excellent client fade away. Therefore, I built ThroneForAndroid.

About ThroneForAndroid

Repository: https://github.com/dsfkjlweuyr/ThroneForAndroid

Base: Built upon the active community mod version (starifly/NekoBoxForAndroid), rebranded, and adjusted to align with Throne's design/branding.

Goal: Continuously sync with the latest upstream community fixes/features while maintaining logical, visual, and operational parity with Throne Desktop.

Proposal to ThroneProj

My ultimate goal is not just to maintain another isolated fork, but to fill the missing piece in the Throne ecosystem.

I would be more than happy to transfer/donate this repository to the ThroneProj organization (or maintain it as an official sub-project/contributor) if the maintainers are open to it. Having both Desktop and Android versions under the same official umbrella would bring great clarity and confidence to the community.

Feel free to check out the repository, try it out, or share your thoughts below! Any feedback or suggestions from both the maintainers and the community are warmly welcome.

Thanks for keeping this ecosystem alive!

[xmha97]

@dsfkjlweuyr Looks like a great idea to me! I think it could be a great addition to the Throne ecosystem.

Also, please consider enabling Issues on the repository so the community can report bugs and share suggestions.

[dsfkjlweuyr]

Thank you for the recognition! As you've noticed, we have introduced alignment and ecosystem interoperability features—such as "Import from Throne Desktop"—and put significant effort into refactoring the upstream modified libcore to ensure complete kernel version parity between T4A and Throne.

The Issue section for this project is now open. That said, I personally check Dayo's group more frequently, so if you run into any issues, tagging me in the Telegram group might get a faster response.

[xmha97]

Thanks for the clarification! I’ll keep that in mind and report any issues in Dayo’s group. Great work on the interoperability and kernel parity!

[dsfkjlweuyr]

Hi @Mahdi-zarei, would you like to give the latest T4A v1.5.6 a try? Among the many NekoBoxForAndroid forks, T4A stays the closest to Throne's core logic—we would love to hear any feedback or suggestions from the official Throne team!

[Mahdi-zarei]

There actually is a good continuation of nekobox: github.com/xchacha20-poly1305/husi
Though i think it would be nice to have a Throne-styled android client, there will be some technical difficulties due to android's restrictive environment, but i think most of Throne's features still can be ported there.

[dsfkjlweuyr]

Yes, that is precisely the direction T4A is aiming for. When considering new features, T4A carefully evaluates the underlying implementation to maintain maximum compatibility with Throne without distorting Android sing-box's native logic.

I actually noticed the husi project early on. In fact, it was thanks to borrowing from husi's implementation that T4A was able to complete the transition from NB4A's original modified core to the official sing-box core (matching Throne's setup) so quickly.

While husi is indeed more feature-complete than the current T4A, it represents a more aggressive branch—for example, directly tracking sing-box beta releases. In contrast, I believe Throne’s approach of reliably following official stable releases is much more stable and production-ready. I hope to bring this hassle-free and balanced experience across platforms, which is the original motivation behind T4A.