MobileRead Forums - View Single Post - KOReader bug

hyurte · 09-18-2020, 09:28 AM

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. Both had previously been working for the around nine months since installing 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. The only thing I did on the trip was occassionally exit KOReader to read PDFs in the native Kindle mode then relaunch KOReader.

In March 2020 I updated to the then current version of KOReader and the fault remained.

A few hours ago I updated KOReader, KUAL (coplate) and MRPI to the latest versions. The fault remains.

Sorry, I can't give steps to replicate as I've never resolved the fault. 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.

09-18-2020, 09:28 AM	#1
hyurte Junior Member Posts: 10 Karma: 10 Join Date: Sep 2020 Device: kindle	KOReader bug - start filemanager opens book 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. Both had previously been working for the around nine months since installing 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. The only thing I did on the trip was occassionally exit KOReader to read PDFs in the native Kindle mode then relaunch KOReader. In March 2020 I updated to the then current version of KOReader and the fault remained. A few hours ago I updated KOReader, KUAL (coplate) and MRPI to the latest versions. The fault remains. Sorry, I can't give steps to replicate as I've never resolved the fault. 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.