KeyStar Support

KeyStar supports any device running One UI 4 (based on Android 12) and later. This will mainly be Samsung devices from 2019 and later, but non-Samsung devices running One UI custom ROMs should also be supported.

Note that some features might not be supported on certain Android versions. For example, the Back button cannot be mapped on Android 16.

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.

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.

It should be possible to disable this message by using RegiStar to map the side button to do nothing.

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.

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.

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 volume buttons to pass through normally and not perform any actions. By default, the Samsung Camera and Clock are excluded.

If your device has a fingerprint scanner on the Side 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 2-second window after unlocking your device during which the lock screen context remains active. If a Side Button action is triggered within this window, your device will also be locked again automatically.

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.

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

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

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.

This typically happens when your device's operating system kills the KeyStar background process due to memory management or battery optimization, even if your device has plenty of free memory. To prevent this, grant KeyStar the "Ignore Battery Optimisations" permission and set up Shizuku (see the How can I set up Shizuku? section). Additionally, it is also recommended to enable KeyStar in Tasker's "Keep Accessibility Running" setting.

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, start Shizuku 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.