Is this a known imperfection that no one else is worried about? Is this something people haven't queried before? Have I missed a setting in KOReader?-please tell me what and don't read anymore since you understand the situation. In the example above I would expect 8 chapter marks (3 for the Parts (with Part One starting after some front matter), 3 for the Chapters, 2 for the Sections) but only 5 appear: 8ĭon't have the expected number of chapter marks appear in the status bar. Not a huge problem for me as I know it, but perhaps easy to solve ?ītw, I observed the same behaviour on my Samsung S7 mobile with Android 8 so it is not specific to Onyx deviceĬhapter 3. KOReader: got error waiting for events: ffi/input_a:168: KOReader: Engine thread destroy requested! If it was already open before, it shows these lines: I ActivityManager: START u0 from uid 10083Īnd then, if KOreader was not running before I see later that it gets started and it opens. I've collected logcat logs to see what is going on and see that CC starts Koreader apparently with this: I have Calibre Companion 5.4.4.19 on Onyx BOOX Poke 2 (Android 9)Īnd I use to open books directly from CC by clicking the Read button there to open Koreader (2020.08.01) with that book.īut this works only if Koreader was not running before, if KOReader was already open with another book before, it remains hanging. This problem is not a big inconvenience and I didn't find this problem reported anywhere else so I'm not expecting a fix but I thought the developers would like to know. Sorry, I can't give steps to replicate as I've never resolved the fault. In March 2020 I updated to the then current version of KOReader and the fault remained.Ī few hours ago I updated KOReader, KUAL (coplate) and MRPI to the latest versions. The only thing I did on the trip was occassionally exit KOReader to read PDFs in the native Kindle mode then relaunch KOReader. I know I had made no changes immediately before the fault developed (or for the nine months since jailbreaking) as I was a couple of weeks into an out of town trip without a computer and there was no WiFi to connect to. Both had previously been working for the around nine months since installing KOReader. In January 2020 while running the version of KOReader (and KUAL and Kindle firmware) that was current at March 2019, the start the file manager and the start the file manger (ASAP) options stopped opening the filmanager and instead opened the last book.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |