Frenzie
commented
4 months ago Do you mean something like this?
- press the menu button
- press up/down
Closed SpartanHeavy closed 3 months ago
Frenzie
commented
4 months ago Do you mean something like this?
SpartanHeavy
commented
3 months ago Do you mean something like this?
1. press the menu button 2. press up/down
Pressing the menu button opens the top menu, and pressing up/down does nothing.
Frenzie
commented
3 months ago @NiLuJe Could this be related to https://github.com/koreader/koreader/pull/11807?
NiLuJe
commented
3 months ago Possibly, I'd need logs to confirm (a.k.a., "Please don't ignore the issue template", wink, wink, nudge, nudge)
NiLuJe
commented
3 months ago And my k2i appears to be sleeping the sleep of the dead, so that's as far as I can go on my own ;).
SpartanHeavy
commented
3 months ago Sorry about that. Here's the logs:
Commodore64user
commented
3 months ago And my k2i appears to be sleeping the sleep of the dead, so that's as far as I can go on my own ;).
Funky bass line starts playing in the background.
🎵 Let's go! 🎵
Steve walks warily down the street With the brim pulled way down low Ain't no sound but the sound of his feet Machine guns ready to go
NiLuJe
commented
3 months ago Does it work any better if your unpack the attached archive in the koreader/libs folder? (it should replace an existing libfbink_input.so.1 file).
EDIT: Oops, first version wasn't a Kindle build -_-".
NiLuJe
commented
3 months ago @Commodore64user: Feel free to double-check that this didn't break the K4, as mine appears only slightly less dead than the K2i ;).
EDIT: Sign of life on the K4, yay.
NiLuJe
commented
3 months ago Commodore64user
commented
3 months ago @Commodore64user: Feel free to double-check that this didn't break the K4, as mine appears only slightly less dead than the K2i ;).
K3 and K4 went unscathed, at least nothing obviously bad has happened... yet. Fingers crossed 🤞
EDIT: Sign of life on the K4, yay.
🥳
NiLuJe
commented
3 months ago Oops, updated the attachment in https://github.com/koreader/koreader/issues/12178#issuecomment-2237318441, the first one wasn't actually built for Kindle ;p.
SpartanHeavy
commented
3 months ago The first version of that file caused all the buttons to stop working. I was getting ready to post updated logs when you posted version 2.
It fixed the problem, and the joystick works normally now. Thanks!
NiLuJe
commented
3 months ago And it still looks sensible on the K4:
┌─(ROOT@kindle:pts/0)──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────(~)─┐
└─(0.41:47%:20:28:15%:#)── ./input_scan ──(Sat, Nov 13)─┘
[FBInk] /dev/input/event0: `tequila-keypad` = KEY | PAGINATION_BUTTONS | HOME_BUTTON | MENU_BUTTON
[FBInk] /dev/input/event1: `fiveway` = KEY | DPAD
[FBInk] /dev/input/event2: `volume` = KEYI'll fold that in a bump later tonight, thanks ;).
Commodore64user
commented
3 months ago FYI, here is the K3 for good measure:
[FBInk] /dev/input/event0: `mxckpd` = KEY | PAGINATION_BUTTONS | HOME_BUTTON | MENU_BUTTON
[FBInk] /dev/input/event1: `fiveway` = KEY | DPAD
[FBInk] /dev/input/event2: `volume` = KEYbtw I am also getting the same warning WARN could not load liblipclua: module 'liblipclua' not found: as https://github.com/koreader/koreader/issues/12178#issuecomment-2237240228
NiLuJe
commented
3 months ago btw I am also getting the same warning
WARN could not load liblipclua: module 'liblipclua' not found:as #12178
That one's perfectly normal, the Lua lipc bindings appeared on FW 5.x ;).
Commodore64user
commented
3 months ago btw I am also getting the same warning
WARN could not load liblipclua: module 'liblipclua' not found:as #12178That one's perfectly normal, the Lua lipc bindings appeared on FW 5.x ;).
Okay, so it’s kinda like that scene in Madagascar (2) where the engine being on fire is perfectly normal and it only becomes troublesome when it stops being on fire… ;)
mergen3107
commented
3 months ago btw I am also getting the same warning
WARN could not load liblipclua: module 'liblipclua' not found:as #12178That one's perfectly normal, the Lua lipc bindings appeared on FW 5.x ;).
Stupid question- shouldn’t this lipc check be device-guarded then? What’s the point?
NiLuJe
commented
3 months ago What’s the point?
It's pcalled, and the try failure is caught to switch to the binding-less codepaths.
mergen3107
commented
3 months ago In that case I think it should also falling back to etc etc :D
I know, I know, it’s just a warning, but still
NiLuJe
commented
3 months ago That's an implementation detail, anyone who cares about lipc will understand what's going on and why when reading the logs.
(i.e., this is not a user-facing UI warning).
Issue
After updating to 2024.07 on my Kindle 2, the five-way joystick does not function at all in KOReader. The other buttons seem to work normally, but I can't navigate through the menus. I couldn't figure out how to exit KOReader without the joystick, so I had to hard reset to get back to the Kindle UI. I tried doing a clean reinstall of KOReader, and the joystick still did not work.