- KOReader version: v2024.07
- Device: Xiaomi 7 Reader (rk3566_eink)
Issue
Xiaomi 7 Reader has asymmetrical (Kindle Oasis style) physical page turn buttons on the right-hand side of the screen.

When the device is in up-right portrait position, buttons are triggering key events 24 & 25 which are handled correctly (upper button results in page back, lower button in page forward).
|
[24] = "LPgBack", -- VOLUME_UP |
|
[25] = "LPgFwd", -- VOLUME_DOWN |
However when the device is upside down, buttons which are now on the left-hand side are triggering inverted key events. The upper button triggers 24 and the lower triggers 25, meaning that system is doing some kind of translation based on the rotation state of the device.
The issue is that KOReader is doing another translation of his own and now event 24 (upper button) results in page forward, event 25 (lower button) in page back, which is counterintuitive.
Is there a way to disable that translation in KOReader for Android devices with physical buttons?
Steps to reproduce
- Turn device upside down.
- Press lower physical page turn button.
Expected: page turn forward.
Actual: page turn back.
Issue
Xiaomi 7 Reader has asymmetrical (Kindle Oasis style) physical page turn buttons on the right-hand side of the screen.
When the device is in up-right portrait position, buttons are triggering key events 24 & 25 which are handled correctly (upper button results in page back, lower button in page forward).
koreader/frontend/device/android/event_map.lua
Lines 15 to 16 in f300590
However when the device is upside down, buttons which are now on the left-hand side are triggering inverted key events. The upper button triggers 24 and the lower triggers 25, meaning that system is doing some kind of translation based on the rotation state of the device.
The issue is that KOReader is doing another translation of his own and now event 24 (upper button) results in page forward, event 25 (lower button) in page back, which is counterintuitive.
Is there a way to disable that translation in KOReader for Android devices with physical buttons?
Steps to reproduce
Expected: page turn forward.
Actual: page turn back.