Touchscreen and Top Menu not functioning while reading on Mobiscribe Wave Color

[plaindinks]

• KOReader version: v2024.07 (ARM apk from releases)
• Device: Mobiscribe Wave Color

Issue

Gestures do not work at all while in a document with finger or pen. The top menu also does not work no matter what I try so I cannot change any settings. The file manager works to browse to a file and the plus. I have to press the back button to exit the app properly. Pop-up menus seem to work from the file manager and to exit the app. When using a keyboard, I can open the bottom menu and that seems to function with touch and I can also page switch with a keyboard.

Steps to reproduce

Start the app for the first time or select any document from the file browser after exiting the app once.

[plaindinks]

The device runs a customized Android 12.

[Frenzie]

I'm afraid that sounds like a device issue. Touch simply comes from the Android system. But if the device has a way to trigger refresh there's a small chance it's doing things and you're just not seeing all of it?

[plaindinks]

It does not work even if I use an external mouse but using an external keyboard works to change pages so it does seem like it refreshes properly. The touchscreen works properly in other apps, in the KOReader file manager, and in some menus I manage to pull up. It only doesn't work with gestures or taps while reading.

[Frenzie]

There's no difference between how taps and gestures work in the file browser vs the reader or the top menu (or for pretty much all intents and purposes, between Android devices).

To see if touches are indeed reaching the program I suppose you could follow this comment: https://github.com/koreader/koreader/issues/10395#issuecomment-1537131597

[NiLuJe]

And enable verbose debug logs first so we get more details ;).

[plaindinks]

Here is a log from pidcat of me starting KOReader, entering a document with the file manager, and then the inputs not doing anything except when I press back while actually reading a document. (I had to manually enable verbose debug logging by editing the settings lua) koreader_pidcat.log

[NiLuJe]

Input events look sane at a glance, can you check an ePub in case it's somehow just a weird PDF quirk?

[plaindinks]

I get the same behavior from epubs.

[NiLuJe]

Could we get logs from that attempt?

[plaindinks]

koreader_pidcat.log Here is a log of me opening an epub and then exiting with the back button. I also opened it again and used keyboard inputs to show that it does indeed work using keyboard inputs. I also tried stylus inputs that did nothing. (Still can't open the top menu)

[NiLuJe]

Well, that's mysterious.

Input looks good, GestureManager looks good, hell, event the crap event_hook thingy works as AutoTurn gets the memo, but, then... poof? As if no touch zones were registered and/or InputContainer's onGesture handler was disabled (which it isn't).

Did you perhaps migrate from another device and imported your old config?

[plaindinks]

I have not copied any configs over and this persists over multiple versions of the app I have tried, even after deleting the koreader folder and app data in android's application settings. The only modification I have done was to enable debugging via the settings lua file to send the logs here after I experienced the issue every time I tried the app on this device only.

[NiLuJe]

Speaking of versions, which ones did you try? (And did that include a recent nightly?)

[plaindinks]

I have tried the latest stable, a nightly from about 2 days ago, and v2024.04. I found this video on a subreddit of someone having the same issue with an older version on the non-color version of the device, seemingly a version from 2023. https://youtu.be/QIcuHMEP-FQ

[pazos]

Based on the video: https://www.youtube.com/watch?v=QIcuHMEP-FQ

mobiscribes are totally broken. You might want to try "settings->screen->timeout->keep screen on.

That's the only workaround we have for this kind of brokeness :(. Otherwise we'll need a proper driver from a developer with the device.

[plaindinks]

Manually setting that via the lua file did not seem to help. The screen doesn't seem to turn off in the first place anyway.

[pazos]

Manually setting that via the lua file did not seem to help.

Is there any reason for you to set this manually and not using the UI? AFAICR the file manager works fine on your case. Is the reader that gets stuck. Did I miss something?

The screen doesn't seem to turn off in the first place anyway.

Eink screens are never turn on or off. They get "high voltage" pumps when they're refreshing screen contents. That's it. But "keep screen on" also prevents the cpu to enter the suspend state. That's what most new android devices do. The crappy ones are unable to figure out KOReader is a proper application as we lock & post directly to a native window instead of using the android view hieararchy.

[plaindinks]

The top menu does not function at all but the file manager does and the bottom menu can work if activated via keyboard shortcut. When the device is locked, it has a separate image it displays. I can also pull down to activate the bar with the navigation buttons and press back to activate the prompt to close KOReader or cancel and that prompt works.