KeyStar can map the power button on Android 10 and later. Choose the power button in KeyStar, assign an action to a trigger, and check for conflicting system shortcuts. No root is needed, but power button mapping requires a one-time purchase.

Check compatibility and the licence

KeyStar supports Android 8 and later, but power button mapping starts at Android 10. Button availability and behaviour can vary by device and Android version.

Power and navigation button mapping are licensed features. The licence is a one-time purchase for lifetime access, with no subscription or ads. Check the purchase screen inside KeyStar for your regional price. You can try volume button mapping for free before buying a licence.

Samsung also offers built-in Side button settings for some actions. If those already provide the shortcut you need, use them. KeyStar is useful when you want additional triggers, different actions per app, or your own custom actions.

Choose a button, trigger, and action

  1. Install and set up KeyStar. Enable the service and follow any permission prompts it shows.
  2. Open the power button configuration. Use the General context to start with a mapping that is not restricted to a particular foreground app.
  3. Choose your trigger. For example, select a long press for a torch shortcut, or a double press for media playback.
  4. Assign the action. Choose Torch → Toggle for the torch, Media Control for music, or Open App to launch an app.
  5. Save and enable the mapping. Check that the chosen action works without a second action running alongside it.

Once the first mapping works, add other triggers. Keep the device's normal power and emergency controls in mind when choosing the shortcuts that work for you.

Avoid two actions running at once

If KeyStar and the device both assign an action to the same trigger, both actions can run. Check the device's power button settings and any other button-mapping apps. For example, disable the default camera double-press shortcut if you are using that same trigger for a KeyStar action.

If you see a “Bixby is disabled” message, the Bixby message support answer explains the RegiStar workaround.

If your fingerprint scanner is on the power button, unlocking can change the context while you are trying to trigger a lock-screen action. KeyStar's Persist lockscreen context option provides a configurable window after unlocking during which that context stays active.

Use app contexts and Tasker

Contexts let the same side-button gesture perform different actions depending on the foreground app. You can also choose Tasker Task as an action to run an automation you have built in Tasker.

Use the Tasker mapping guide for an example workflow, or visit KeyStar Support for timing, permissions, and startup troubleshooting.

Keep exploring

KeyStar supportAll mapping guides