v4.0.3 stopped detecting side buttons #2030
Description
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?
Likely because of 0058c0c, side button events are no longer recorded nor trigger defined actions, even though the key events are seen by the bridge service.. A single button press sometimes (?!) results in multiple EV_UNK events, but the action I had defined for it did work well on 4.0.2 regardless..
02/11 18:55:35.621 INFO Starting trigger recording. Evdev recording: true
02/11 19:09:13.502 INFO Grab evdev devices for key map detection: GrabTargetKeyCode(name=gpio_key-func, bus=25, vendor=250, product=250, extraKeyCodes=[]), GrabTargetKeyCode(name=TitanKey, bus=0, vendor=9523, product=9523, extraKeyCodes=[])
02/11 19:09:37.932 DEBUG Navigation: Navigating to Log with key log
02/11 19:09:41.498 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 495918 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 1 }
02/11 19:09:41.500 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 495918 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
02/11 19:09:41.624 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 621696 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 0 }
02/11 19:09:41.626 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 621696 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
02/11 19:09:41.628 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 623215 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 1 }
02/11 19:09:41.629 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 623215 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
02/11 19:09:41.630 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 624625 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 0 }
02/11 19:09:41.631 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 624625 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
02/11 19:09:41.633 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 625101 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 1 }
02/11 19:09:41.634 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 625101 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
02/11 19:09:41.635 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 627199 }, event_code: EV_UNK { event_type: 1, event_code: 250 }, value: 0 }
02/11 19:09:41.635 DEBUG systembridge: Evdev event: InputEvent { time: TimeVal { tv_sec: 1770833381, tv_usec: 627199 }, event_code: EV_SYN(SYN_REPORT), value: 0 }
What did you expect to happen?
work like before
What would the developer need to do to reproduce the bug?
…
App version
4.0.3-foss
Android version
Android 15
Device model and manufacturer
Unihertz Titan 2
Extra info
- My device is rooted