KeyStar and PenStar work without root. Setup supports Shizuku, ADB, or wireless debugging. For ongoing use, the recommended Shizuku setup runs logcat through Shizuku and helps avoid repeated one-time log-access prompts. The startup options below refer to the Shizuku fork linked by the developer.
Choose your setup method
Follow the instructions inside KeyStar or PenStar for the access your version needs. You have three supported setup routes:
- Shizuku: a useful option for ongoing log access and the startup behaviour described below.
- ADB: follow the app's displayed setup instructions from an authorised computer.
- Wireless Debugging: use the setup path supported by your device and the app.
The built-in pairing flow for wireless debugging is available on Android phones from Android 11. Earlier Android versions use a USB-based ADB setup before a wireless connection. See Android's official ADB instructions for connection details.
The steps below use the Shizuku fork by thedjchi linked in the app support pages. Its Start on boot, Watchdog, and TCP mode options should not be assumed to exist in every Shizuku release.
Install, pair, and start Shizuku
- Install the recommended fork. Download it from the thedjchi/Shizuku releases page.
- Pair and start Shizuku. Follow its instructions for Wireless Debugging on devices that support pairing. Use the ADB route provided by Shizuku when appropriate for your Android version.
- Check that Shizuku is running. Pairing alone is not the same as starting its service.
- Configure ongoing startup. In this fork's settings, enable Start on boot, Watchdog, and TCP mode, as described in the KeyStar and PenStar support pages.
If your device has trouble pairing or keeping the connection, use the fork's troubleshooting guide. Device settings and menu names can vary.
Connect KeyStar or PenStar to Shizuku
- Open your mapping app's settings. Enable Run logcat through Shizuku.
- Allow the Shizuku access request. Follow any access prompt shown by Shizuku or the mapping app.
- Turn the service on. This starts the service with the selected log-access method.
- Check the result. With the setup working, the app should no longer show the one-time log-access dialog when you enable it. Try a simple button or S Pen action.
If you use both apps, enable Run logcat through Shizuku in each app separately. Continue to grant any other permission required by a particular action; log access does not replace every app permission.
Get ready after a reboot
Enable Start on boot in KeyStar or PenStar if you want the app to start automatically. On Android 13 and later, the recommended Shizuku setup avoids the manual one-time log-access step that otherwise interrupts automatic startup.
For the fork's automatic-start setup, the device should connect to a Wi-Fi network shortly after restarting. Check that Shizuku is running and that the mapping app is enabled. If either service is stopped, review its startup settings and your device's background or battery restrictions.
If you're on Android 13 or later and do not use Shizuku, you can still opt to start the app manually after reboot. A notification is shown to let you know it needs to be started manually on every boot.
If it still does not work
Check the KeyStar Shizuku answer or PenStar Shizuku answer. If Shizuku stops when locking or unlocking the device, start with the fork's troubleshooting guide.
When contacting the developer, include your device model, Android version, mapping app version, Shizuku version, setup method, and the exact point where the process fails. These details help distinguish log-access problems from action-specific permissions.