KeyStar Support

KeyStar supports all Android devices running Android 8 and later. However, some buttons might not be supported on certain Android versions. For example, the power button cannot be mapped on Android 8 and 9.Link to this answer

KeyStar only strictly requires the "Notifications" and "Read Logs" permissions to function. All other permissions are optional and are only requested when you attempt to use specific features. The app provides clear explanations for why each optional permission is needed when you enable those features.Link to this answer

KeyStar itself does not collect any data. However, KeyStar uses the Google Play Billing Library for purchases, and that library sends some data to Google. This is handled by Google and is outside the developer's control.Link to this answer

Yes, KeyStar can start on boot. Ensure that the "Start on boot" option is enabled in the app settings.

On devices running Android 12 or earlier, no further action is needed. For Android 13 and later, to allow KeyStar to start on boot without requiring you to manually grant one-time log access, you must set up Shizuku (see the How can I set up Shizuku? section). With Shizuku set up, it will automatically start on boot once your device is connected to a Wi-Fi network.Link to this answer

You can disable this message by using RegiStar to map the side key press and hold action to open an app that is no longer installed on the device. Simply install any app, set it to open that app, then uninstall it.Link to this answer

Disable any action configured outside KeyStar for the same button gesture. For example, if you assign a KeyStar action to a double press of the power button, disable your device's default double-press action that opens the Camera.Link to this answer

The standard press delay is the amount of time you have to press a button again to advance to the next slot (e.g., from a single to a double press). For example, if you have an action assigned to a single and double press, and the standard press delay is 250ms, you will have 250ms after the first press to press the button again to trigger the double press action. If the time expires, the single press action will trigger instead. Note that the last assigned action in a sequence (in this case, the double press) is executed instantly without waiting for the delay to expire.Link to this answer

The long press delay is the amount of time you must hold a button for it to register as a long press. For example, suppose you have an action assigned to a triple long press, with a standard press delay of 250ms and a long press delay of 300ms. To trigger this action, you must press the button for less than 300ms, then within 250ms press it again for less than 300ms, and finally, within another 250ms, hold the button for at least 300ms.Link to this answer

If an app uses the volume buttons for its own functions, you can add that app to the "Excluded apps" list in KeyStar settings. When an excluded app is in the foreground, KeyStar will allow the disabled buttons to pass through normally and not perform any actions. By default, the built-in Camera and Clock apps are excluded.Link to this answer

When the notification shade or Quick Settings is open, KeyStar cannot detect the foreground app. This prevents KeyStar from knowing if an excluded app is currently active. If the feature still does not work when the notification shade is closed, contact the developer for assistance.Link to this answer

If your device has a fingerprint scanner on the power button, you may accidentally unlock your device while trying to trigger a lock screen action. To solve this, you can enable the "Persist lockscreen context" option in KeyStar settings. This provides a configurable window of time after unlocking your device during which the lock screen context remains active.Link to this answer

It is currently not possible to prevent the volume buttons from changing the device volume when the screen is completely off (Always On Display not showing). As a workaround, you can enable the "Restore volume" setting. This will automatically restore your volume to its previous level after an action is triggered in this scenario.Link to this answer

This happens when you set a custom volume change step in Sound Assistant. Enable the "Custom volume change step" setting to fix this issue.Link to this answer

Starting from Android 17, volume control and sound mode actions might not work when KeyStar is started in the background. If this happens, tap the Enable Audio Controls notification when it appears, or use Shizuku (see the How can I set up Shizuku? section).

For advanced users, the ADB command "adb shell cmd audio set-enable-hardening disable" might be able to disable the restrictions.Link to this answer

You can use apps located in a Secure Folder or Work Profile with KeyStar. To do this, KeyStar must only be installed on your primary user profile.

If the target app can also be installed on your primary profile, install it there, configure your KeyStar actions, and then uninstall the app from the primary profile. Your configuration will remain and can still be modified in the future.

If the app cannot be installed on your primary profile, set up your desired KeyStar configuration using a dummy app. Export your configuration using the "Backup" option in settings, open the backup file, and replace all instances of the dummy app's package name with the package name of the app in your Secure Folder or Work Profile. Finally, restore the modified configuration.Link to this answer

Without Shizuku, Last App relies on Android's app usage history, which can include apps that have been swiped away from Recents. When Shizuku is active in KeyStar, an improved Last App implementation is automatically used, avoiding this issue. See the How can I set up Shizuku? section below.Link to this answer

Yes, you can use the "Tasker Task" action to trigger any task you have created in Tasker, allowing for limitless possibilities.Link to this answer

Yes, KeyStar has Tasker Plugin support. This allows you to Enable, Disable, Backup, and Restore KeyStar from Tasker. For example, you can create a Tasker profile that automatically restores a specific KeyStar configuration whenever your device enters Power Saving mode.Link to this answer

First, enable Control KeyStar using intents in KeyStar settings. You can then send either of these broadcast intent actions to start or stop KeyStar:

• com.threestars.keystar.action.START_SERVICE
• com.threestars.keystar.action.STOP_SERVICE

For example, the ADB command adb shell am broadcast -a com.threestars.keystar.action.START_SERVICE starts KeyStar.Link to this answer

This usually happens when Android kills KeyStar due to memory management or battery optimization. If the issue still occurs after granting the "Ignore Battery Optimisations" permission, it is recommended to set up Shizuku (see the How can I set up Shizuku? section).

If you notice that the accessibility service is also being killed, enable KeyStar in Tasker's "Keep Accessibility Running" setting.Link to this answer

It is highly recommended to use the "Run logcat through Shizuku" option in KeyStar settings. Properly configuring Shizuku ensures that KeyStar survives being killed by the operating system, eliminating the need for manual restarts. Additionally, you will no longer need to grant one-time log access when enabling the service, which also allows KeyStar to start on boot without manual intervention.

Follow these steps to set up KeyStar with Shizuku:

1. Download and install the latest Shizuku fork by thedjchi from here.
2. Once installed, pair Shizuku and start it using Wireless Debugging.
3. In Shizuku settings, enable Start on boot, Watchdog, and TCP mode.
4. In KeyStar, enable Run logcat through Shizuku.
5. Turn KeyStar off and then back on.

If done correctly, you will no longer see the one-time log access dialog when turning on KeyStar. If you notice that Shizuku stops when unlocking or locking your device, or have other issues, refer to the troubleshooting guide.Link to this answer