-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input not working on Libra h2o #10
Comments
Running Software 4.21.15015 KOreader and Plato boots up fine, so I am pretty sure KFMon is installed correctly. |
It’s the same on Kobo glo, however I’ve noticed it’s only the touch buttons that don’t work. Lists work and icons seem to work somewhat |
same issue here on a kobo aura |
Same issue. Is there an issue between QT and QT5 Kobo plugin? |
same here on kobo libra |
Did anyone manage to get it to work with kobo libra h2o? I am having the same issue where the screen is non-responsive to touch and any settings I've tried does not work. Any help would be appreciated. Thank you. |
I'm getting the same error on my libra |
Same here. Looking forward to using it when the Libra's supported. Also, happy to assist with any QA/testing along the road to making that happen. |
I managed to temporarily fix this by changing the default line to this in the ultimatemangareader.sh export QT_QPA_PLATFORM=kobo:touchscreen_rotate=auto:touchscreen_invert_x=1:touchscreen_invert_y=1:logicaldpitarget=108 |
Looks like with 2.5+ version now, this works on Libra H2O ... well, with some changes on the config. Changing the .sh config to use:
And now this works for me in portrait mode. Thanks! |
Installed KFMon and was able to launch ultimatemangareader.png successfully, and I am presented with a UI, but none of the input works. I can still lock the screen and so I think the device is still functioning - but without input I can't do anything. When I unlock the screen, I will see a "Connecting to Wifi" screen, and then it goes away. End up with a soft reboot instead to get back to normal.
The text was updated successfully, but these errors were encountered: