Volume Down turns screen off after unlock when Power double press is mapped with Shizuku Expert Mode

[gunther82]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

I created a trigger with double press of Power button to launch Google Wallet app with Do Not Remap option enabled. The app opens correctly but there is a side effect.

Problem:
After every unlock the first single press of Volume Down turns the screen off as if it were the Power button.
After that, Volume Down works normally until the next unlock.

What I tested:

• Changed trigger from scan code 116 to key code 26: no change
• Changed double press duration from 300 ms to 200 ms: no change
• Changed the app assigned to double press Power: no change
• Key Mapper log shows Volume Down is correctly detected as KEY_VOLUMEDOWN (keyCode=25, scanCode=114)
• Power is correctly detected as KEY_POWER

Additional note:
If the option “Do Not Remap” is not enabled, the first press of the Power button after the wrong lock by Volume Down button is "lost", nothing happens.
And also the system shortcuts Power + Volume Down for screenshot and Power + Volume Up for boot menu are broken.

What did you expect to happen?

Expected behavior:

• Volume Down should never act like Power

Possible cause:
This looks like an issue with key interception or event pass-through in Shizuku Expert Mode on OriginOS 6 when the Power button is used as a trigger.

What would the developer need to do to reproduce the bug?

Setup:

• Shizuku enabled
• Expert Mode enabled
• Double press Power mapped to launch Google Wallet with Do Not Remap option enabled
• Same issue also happens if I assign a different app, so it is not Wallet-specific

App version

4.1.0 251

Android version

16

Device model and manufacturer

Vivo x300 global with originOS 6

Extra info

• My device is rooted

[jambl3r]

Can you turn on extra logging in the app and reproduce it and then send us the log please?

[gunther82]

key_mapper_log_20260710-120903.txt

This is the log.
The sequence of steps I did is the following (all single press):

• Power for lock
• Unlock
• Volume down that wrongfully locks the device
• Unlock
• Volume down that this time works well and reduced the volume
• Power for lock
• Unlock
• Volume down that wrongfully locks the device again

The double press for triggering the desired action works fine.

I did all this with version 4.1.0

I don’t know if this helps or only adds confusion, but in the meantime I received the update to version 4.2.1, and I noticed that with that version the power button sometimes does not behave correctly either. Sometimes a single press with the same trigger and action locks and then immediately unlocks the phone, but I did not investigate it in detail enough to find the exact pattern of what happens.

With version 4.1.0, the behavior is exactly as I reported here, and it seems deterministic.

EDIT: I just figured out that all this happens if I lock the phone with power button, if I lock the phone with double tap on display the issue with volume down does not occur