Stellar

300PSA · Tools

Verified safeOpen sourceExclusive

Download APK

—

No reviews reviews

downloads

7.0

android

AI summary

Customized Shizuku framework offering privileged system-level APIs via ADB wireless debugging or root. Adds granular multi-level permissions, follow-startup service binding, dual-process guarding, and re-enabled deprecated Shizuku features like newProcess() and runtime permission management. Includes a Shizuku compatibility layer for existing apps.

Generated by AI. May contain inaccuracies.

Screenshots

About this app

Stellar 是 Shizuku 的深度定制版本，专为开发者提供更灵活、更强大的特权 API 框架。通过 ADB 无线调试或 Root 权限启动服务后，应用程序可以调用需要系统级权限的 API，而无需应用本身拥有 Root 权限。

🧩核心特性 Stellar 相比原版 Shizuku 进行了以下核心改进：

权限系统增强・全新权限架构 - 摒弃单一权限模式，引入精细化的多维度权限管理体系分级权限控制： ①stellar - 核心 API 访问权限，授予基础服务调用能力 ②follow_stellar_startup - 服务伴随启动权限，实现应用与 Stellar 服务的生命周期绑定・智能权限回调 - 增强回调机制，客户端可精准感知授权类型（永久授权/一次性授权）・完整权限管理 API - 提供全套权限查询、申请、撤销接口，满足复杂业务场景需求

🧩启动与服务优化・开机启动 - 应用可尝试通过开机广播、无障碍权限和 Root 权限实现开机自启・服务伴随启动 - 应用可注册为 Stellar 服务的伴随进程，实现服务启动时自动唤醒・双进程互守 - 可开启守护进程，Stellar 服务与守护进程相互监测异常关闭并重新启动

🧩架构重构・服务层重构 - 重新设计核心服务架构，优化模块间通信机制，提升整体性能与响应速度・UserService 重写 - 全面重构用户服务层，优化服务架构设计，提升代码可维护性与扩展性・Shizuku 兼容性修复 - 修复原 Shizuku 遗留的已知问题，增强框架稳定性

🧩UI/UX 改进 Stellar 对用户界面进行了全面重构，带来更现代、更直观的使用体验：

・全新授权管理界面 - 采用 Material Design 3 设计语言，打造简洁优雅的授权管理中心・授权页面焕新 - 重新设计授权交互流程，操作更加流畅自然・权限可视化展示 - 授权页清晰呈现各项细分权限，用户一目了然・应用列表优化 - 改进已授权应用列表，权限状态一览无余・引导流程升级 - 重新设计启动引导页面，新用户上手更轻松

⭕与 Shizuku 的主要区别 ✅移除的功能・rish - 移除 Shizuku 内置的 root shell 工具・Sui - 移除了 API 对 Zygisk-Sui 的支持 ✅新增的功能・跟随启动机制 - 应用可跟随 Stellar 服务自动启动・细分权限系统 - 支持多种权限类型的精细化管理・权限回调增强 - 支持一次性授权感知降权激活 - Root 启动后可降权到 Shell 用户运行，提高安全性

🧩重新启用的功能 Stellar 重新启用了 Shizuku 最新版本中已标记为弃用的功能：

・newProcess() API - 直接创建特权进程的方法，Shizuku 已弃用但 Stellar 保留支持・运行时权限授予/撤销 - 通过 grantRuntimePermission() 和 revokeRuntimePermission() 为其他应用授予或撤销 Android 运行时权限这些功能在某些场景下仍然非常实用，Stellar 选择继续支持以提供更完整的 API。

🧩架构优化・100% Kotlin 代码・精简模块结构・规范化命名

🧩Shizuku 兼容层 Stellar 内置了 Shizuku 兼容层，允许使用 Shizuku API 的应用无需修改代码即可使用 Stellar 服务。

⛔启用/禁用 Shizuku 兼容层默认启用。如需禁用，可在 Stellar 管理器的设置页面中关闭「Shizuku 兼容」开关。

⚠️注意事项・兼容层会自动拒绝来自 Shizuku Manager 的请求，避免冲突・使用 Shizuku API 的应用需要在 AndroidManifest.xml 中配置 ShizukuProvider ・建议新应用直接使用 Stellar API 以获得完整功能支持

🌿降权激活降权激活功能允许以 Root 权限启动 Stellar 服务后，自动降权到 Shell 用户（uid=2000）运行，提高安全性。 ✅启用方式在 Stellar 管理器的设置页面中，开启「降权激活」开关即可。 ⚠️注意事项降权激活仅在 Root 启动模式下生效 ADB 启动模式本身就是 uid=2000，无需降权降权后服务将失去 Root 特有的能力（如写入系统属性、访问受保护目录等）

✒️界面语言：中文

📝其他具体使用详情请于项目作者github主页查询 ①项目作者：github@洛夕(roro2239) ②作者主页：https://github.com/roro2239 ③项目详情：https://github.com/roro2239/Stellar

*note：如作者无意愿将本项目分享至appteka，请告知分享者，侵删。与appteka无关。

🎯 Project author:github@

shizuku privileged api adb root open source tools

What's new

v1.0.18Jul 24, 2026

● New functions ·Added quick authorization function if you are redirected
Some apps may not execute the request permission code, but instead require the user to manually authorize after jumping to Stellar. This function can detect whether the source App is authorized after being jumped. When the authorization status is query, Stellar will automatically pop up the request permission pop-up window
·Added hidden background function ·Added the function of saving commands as desktop icons ·Add a quick start button when wireless debugging is not turned on during wireless debugging startup
It is not a jump to the developer option. This feature is only available when connected to WiFi
·Added warm-up mode during booting
Used for situations where you want to boot without WiFi after booting up in a WiFi environment once, but you don't want to actually start Stellar services
● Improvement ·Support Japanese, Portugal, Spanish and Brazilian Portugal ·Adjusted the service log page log refresh mechanism, changing manual refresh to automatic refresh every second ·Adjusted the service log page log type filter style to increase readability ·The experience of the service log page log type filter has been adjusted, so that the filter selection will be persisted instead of being cleared after exiting the page ·Optimize the UI of authorized application pages ·Optimize settings page boot options UI
● Repair ·Fixed the problem where spaces were missing on the left and right sides of the application name in the authorization pop-up window ·Fixed an issue where the "Once Only" option appeared following the launch authorization pop-up window ·Fixed the issue where the follow-up boot cannot be followed when the follow-up boot is authorized but the basic permissions are not authorized ·Fixed the issue where all authorized applications were pulled up when Stellar service was launched ·Fixed an issue where the service launch listener does not work on authorized applications ·Fixed the issue where permission request results may be attributed to wrong permissions ·Fixed an issue where Stellar authorizes an unrunning application and then launches it does not take effect ·Fixed the problem where multiple process clients with UID overwrite each other, resulting in loss of callbacks ·Fixed a problem where third-party apps may still receive connections after Binder failed to connect ·Fixed the issue where third-party applications may not be able to call the Stellar interface after service restart ·Fixed an issue where the same Binder connection event may cause third-party applications to repeatedly trigger certain logic ·Fixed an issue where some third-party applications could not be recognized to follow the launch announcement ·Fixed the issue where the authorization list omitted the application that only declares follow-up permissions ·Fixed an issue where Stellar may not be able to correctly determine whether a service is running ·Fixed a problem where following start commands and terminal commands may get stuck ·Fixed an issue where apps that support Shizuku but not native Stellar but declare that they will follow the launch are classified as Stellar native apps