![]() |
#526 |
Member
![]() ![]() Posts: 22
Karma: 172
Join Date: Dec 2010
Device: PRS-600
|
|
![]() |
![]() |
![]() |
#527 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,781
Karma: 731691
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
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.
|
![]() |
![]() |
![]() |
#528 |
Evangelist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 486
Karma: 11708254
Join Date: Dec 2020
Device: Boox, Bigme, Hisense, Kobo
|
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? |
![]() |
![]() |
![]() |
#529 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,781
Karma: 731691
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
It says here there were bugs with it https://github.com/koreader/android-...ncher/pull/563
You didn't experience any? |
![]() |
![]() |
![]() |
#530 | |
Evangelist
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 486
Karma: 11708254
Join Date: Dec 2020
Device: Boox, Bigme, Hisense, Kobo
|
Quote:
Occasionally just killing the app and starting it again, while slightly annoying, is a price I'm willing to pay until it gets fixed. |
|
![]() |
![]() |
![]() |
#531 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,781
Karma: 731691
Join Date: Oct 2014
Location: Antwerp
Device: Kobo Aura H2O
|
If you're willing to help test, please consider answering on that GH issue.
![]() |
![]() |
![]() |
![]() |
#532 | |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Oct 2025
Device: palma 2 boox
|
Quote:
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 |
|
![]() |
![]() |
![]() |
#533 |
Bookmaker
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 429
Karma: 2143650
Join Date: Sep 2010
Device: Cybook Opus
|
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.
|
![]() |
![]() |
![]() |
#534 | |
Junior Member
![]() Posts: 4
Karma: 10
Join Date: Oct 2025
Device: palma 2 boox
|
Quote:
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 Last edited by giggi10; 10-12-2025 at 02:11 PM. |
|
![]() |
![]() |
![]() |
#535 |
Bookmaker
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 429
Karma: 2143650
Join Date: Sep 2010
Device: Cybook Opus
|
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? |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Koreader running on Kobos (all of them, hopefully!) | giorgio130 | KOReader | 3535 | 07-09-2025 01:37 PM |
Koreader doesn't work on 5.4.3 | vr4y | Kindle Developer's Corner | 13 | 04-15-2014 03:40 AM |
coolreader/koreader without fmon | peyton | Kobo Developer's Corner | 17 | 03-30-2014 04:06 PM |
framebuffer settings for koreader | shadoooo | Kobo Developer's Corner | 15 | 01-01-2014 11:20 AM |
Koreader v. Coolreader | 93terp | Kobo Developer's Corner | 8 | 11-05-2013 04:37 AM |