KOreader on Android

[almaviva]

This is excellent news about the Pixel cutout. I can confirm it works beautifully on my old (but still great) Pixel 4a.

Can anyone tell me how to thank the developers? I'd love to make a donation.

Thanks,
Oliver H.

[pazos]

Originally Posted by almaviva

This is excellent news about the Pixel cutout. I can confirm it works beautifully on my old (but still great) Pixel 4a.

Can anyone tell me how to thank the developers? I'd love to make a donation.

Thanks,
Oliver H.

There's https://liberapay.com/KOReader

But a simple thank you is good enough.

[NiLuJe]

Originally Posted by mkozlows

the most relevant thing seemed to be the PR about fixing screen refresh issues on the Sage

Extremely unlikely, that targets a very very very specific display driver bug that you'll recognize if you ever see it; in a very specific context (toggling wifi).

I'd have been mighty interested in seeing verbose debug logs of that issue, because the only input issue I'm aware of is *missed* taps, not *repeated* taps, and is specific to power-management (specifically, autosuspend), and we've worked around it for a good long while now, so it shouldn't be an issue in KOReader (but you might still encounter it in Nickel).

(For others following at home, it's also specific to the sunxi devices; and it also affects the Elipsa's touch panel (to a much greater extent, because it *also* has non-PM related issues with buggy handling of spurious 0-pressure events)).

[mallomar]

Noticed a bug recently on my Onyx Boox Note Air 2 and my wife's Nova Air C where KOReader doesn't respect the system brightness and automatically goes to auto brightness at night. The only way I've been able to figure it out is by turning auto-brightness off in KOReader. This is a somewhat recent bug in the past month or so.

[mergen3107]

Onyx Boox is a mess, including brightness. I resorted to system only controls of light

[ext23]

I just got a Hisense A9 and immediately installed KOReader because it worked so well on my old Kindle.

The Hisense has a programmable button that lets you refresh the screen, turn the light on/off, turn pages, that kind of thing.

The main reason I got the A9 is because it's also a really good music player, so I set the button for a single press to play/pause music, and a double press to skip to the next track. These options work throughout Android, but in KOReader, only the double press works...I tried setting the single press to turn to the next page, and KOReader didn't recognise that either. The light on/off on single press DID work, though, I guess because it's a system setting and not dependent on what app you're using.

So, KOReader is registering the double press, but not the single press. How can I fix this? Or tell it to let the system have control of button presses or whatever? Please help!!

[pazos]

Media keys are all already forwarded to the system, that includes play/pause, stop, next and previous. The only keys we might consume and thus not forward to system are volume up/down (check the setting in "settings" -> "navigation".

That means that, most likely, the key events your device emits are not standard android keys. We eat all those keys, because that's mandatory for us to be able to remap them.


Have a look at https://github.com/koreader/koreader...customize-keys. The last link in the section will give you instructions to know which key events your device emits.

Hopefully you will be able to figure out the keys id (a number) emited by single presses on those buttons. Please report them here so we can forward them to the system. It is not possible to do it with remaps yourself if they're not standard because that part of the logic is buried deep inside our input handler

[ext23]

Thank you so much! I was able to get the keypress log:

08-27 08:17:10.179 12180 12210 V KOReader: key event => code: 126 (nil), value: 1, time: 3912.711000
08-27 08:17:10.183 12180 12210 V KOReader: key event => code: 126 (nil), value: 0, time: 3912.711000

This is for a single press. Can this be forwarded to system?

[pazos]

Originally Posted by ext23

Thank you so much! I was able to get the keypress log:

08-27 08:17:10.179 12180 12210 V KOReader: key event => code: 126 (nil), value: 1, time: 3912.711000
08-27 08:17:10.183 12180 12210 V KOReader: key event => code: 126 (nil), value: 0, time: 3912.711000

This is for a single press. Can this be forwarded to system?

Thanks! Yes it can

Sorry, it was my bad, I didn't notice AKEYCODE_MEDIA_PLAY
.Most handsets and controllers use "AKEYCODE_MEDIA_PLAY_PAUSE" instead.

Give me a couple of days to submit a patch.

[ext23]

Originally Posted by pazos

Give me a couple of days to submit a patch.

Thank you so much! This is great news for me because honestly this device has been a bit of a headache, but this fix will make everything much more enjoyable.

Connecting to Calibre over wifi crashes the app, for example, but the exact same thing works perfectly on my old Paperwhite.

[pazos]

Originally Posted by ext23

Connecting to Calibre over wifi crashes the app, for example, but the exact same thing works perfectly on my old Paperwhite.

That stuff should work the same on all the platforms and devices, so feel free to report a bug on github following the issue templates.

Forums are good for questions (and for those who have an opinion on each single topic ). Github is way better for the issue at hand

[pazos]

Originally Posted by pazos

That stuff should work the same on all the platforms and devices, so feel free to report a bug on github following the issue templates.

Forums are good for questions (and for those who have an opinion on each single topic ). Github is way better for the issue at hand

Edit: but first make sure you're able to reproduce on anything different than v2023.6.1. There's a known bug on android related to wifi handling which was fixed a long time ago but isn't yet part of any "monthly" releases.

Both v2023.06 or any nightly of the past 3 weeks are ok to test if you can reproduce. If so please do follow my advice above


Edit2: lol, instead of editing my previous comment I made a mess quoting my previous comment. Hopefully the intent is still clear.

[ext23]

Originally Posted by pazos

That stuff should work the same on all the platforms and devices, so feel free to report a bug on github following the issue templates.

Forums are good for questions (and for those who have an opinion on each single topic ). Github is way better for the issue at hand

OK I will do this in future (never used Github before but I'll try)!

I tried connecting wireless again and...this time it worked without crashing. No idea what changed, this Hisense device has a mind of its own sometimes.

Looking forwards to the button hotfix, thanks again, I'll be sending a donation your way.

[ext23]

Originally Posted by pazos

Give me a couple of days to submit a patch.

Sorry for the double post. How can I keep track of when this patch goes live?

[ppirx]

Hello everyone,
I was looking for a hint about my koreader on a tolino shine3 (android 4.4.2) not updating to newest releases stable nor nightly. "your device seems to be unable to download packages" even the built in browser cannot handle the file format. "... not supportd". I am wondering, because i think it worked once!? Would be grateful for any help. I installed it via rhe fibonacci search dev environment beside the simple ink launcher
Cheers Daniel