KOreader on Android

[tetra]

Originally Posted by Frenzie

Just ignore it. That's meaningless planned obsolescence gibberish from Google. It has nothing to do with privacy.

Sure, but why not compile it with a more recent Android SDK version?

[Frenzie]

At the very least someone would have to do quite a bit of testing to see what happens. Iirc there were also library loading issues on Android 13+ (if set as intended for Android 13, currently it's set as intended for Android 11) but those may have been resolved now that we switched to a "monolibtic" library.

[kandwo]

My white Onyx Go 7 (BW) has lost support for setting the full screen refresh frequency since the latest Koreader, including the latest development builds.

When doing the compatibility test it states that the device is "already supported", but "EPD: none". The "Onyx/Qualcomm" driver works for that, but for whatever reason seems to have been deactivated since the latest stable build.

Where should this bug be reported so that the correct EPD driver can be activated for this model again?

[Frenzie]

It says here there were bugs with it https://github.com/koreader/android-...ncher/pull/563

You didn't experience any?

[kandwo]

Originally Posted by Frenzie

It says here there were bugs with it https://github.com/koreader/android-...ncher/pull/563

You didn't experience any?

Sure, Koreader sometimes turns into a black screen on many Onyx devices, which is resolved by restarting it. However, I don't see how removing the driver is a solution. If I can't set full refresh to every page turn, I can't read at all.

Occasionally just killing the app and starting it again, while slightly annoying, is a price I'm willing to pay until it gets fixed.

[Frenzie]

If you're willing to help test, please consider answering on that GH issue.

[giggi10]

Originally Posted by kandwo

Sure, Koreader sometimes turns into a black screen on many Onyx devices, which is resolved by restarting it. However, I don't see how removing the driver is a solution. If I can't set full refresh to every page turn, I can't read at all.

Occasionally just killing the app and starting it again, while slightly annoying, is a price I'm willing to pay until it gets fixed.

Hello there, I'm a new user here so be patient with me lol
There are so many useful tips around here to help us make the most out of our ebook readers that I'm really excited even now writing to you...

1) I would like to report the same issue with my recently bought Palma 2 while using Koreader; at times when I turn the screen on after some period of stand-by mode, the above-mentioned black screen appears and I'm forced to restart the app...

Has anyone good news on that?

2) the last bug is less important but still annoying: the bookmark tag is too small to see in the top right corner of my epubs, even if I adjust the margins or DPI...
I guess it's due to the rounded bezel/frame of the Palma 2 and its form factor; it would be nice to fix it so that the bookmark shows up correctly on the top right corner of any given page

[Rand Brittain]

I installed the patch from the linked issue on my Palma 2 and Tab Pro Ultra C, and while it's kinda too soon to say, I haven't seen the black screen issue in the past 24 hours since installing.

[giggi10]

Originally Posted by Rand Brittain

I installed the patch from the linked issue on my Palma 2 and Tab Pro Ultra C, and while it's kinda too soon to say, I haven't seen the black screen issue in the past 24 hours since installing.

So basically you followed these steps mentioned by sndwichm4n?
I'll try to do the same even if I'm pretty noob at that, thanks

https://github.com/koreader/koreader...ent-1913156584

[Rand Brittain]

Yeah, so far using the patch seems to get rid of that problem altogether.

I wanted to ask if anybody else has seen another issue, which I've experienced on both those devices (both before and after using that patch). It seems like on occasion KOreader will just stop responding to taps altogether. It still responds to swipes, and the rest of the device's software still recognizes taps, but the only way to resolve the issue is to close the KOreader app.

Has anybody else seen this?

[hius07]

Originally Posted by Rand Brittain

It seems like on occasion KOreader will just stop responding to taps altogether.

Already fixed, install the latest nightly build.

[Rand Brittain]

Originally Posted by hius07

Already fixed, install the latest nightly build.

Well, that's just aces.

[giggi10]

Originally Posted by Rand Brittain

Yeah, so far using the patch seems to get rid of that problem altogether. "....."

Unfortunately I wasn't lucky then because apparently there is no improvement by my side as I'm forced to close KOReader quite often; I just switched to the stock app instead 'Neo reader' on my Palma 2 Boox which is performing great: the only downside is that the dictionary's interface is not as functional as on koreader, where searching for missing words is made easier through online search

[Rand Brittain]

I was gonna say "that's unfortunate; it hasn't happened to me since I installed the patch" but then it happened to me. Only once so far, though.

[giggi10]

Originally Posted by Rand Brittain

I was gonna say "that's unfortunate; it hasn't happened to me since I installed the patch" but then it happened to me. Only once so far, though.

I'll keep on monitoring the situation but in the meantime I'm mainly on the native app, neo reader Boox...

In any case I have not tried to get the nightly builds of KOReader but only the official ones because it's easier to install