MobileRead Forums - View Single Post - KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

roger64 · 03-10-2016, 10:22 AM

Hi

Updating

I succeeded to update Koreader to version 2015.11-175-g7b11491 using the Tools menu at the bottom of the Koreader main menu and then choosing Update KOReader option which is something we could not do on Kobo.

OTA incremental updates are still a no-go but this is less important now that I know how to update the other way.

Progress bar settings

I had lost a mini-bar setting which I reactivated using
frontend/apps/reader/module/readerfooter.lua (quite a hidden setting...)

I still have a thin horizontal progress bar three millimeters from the top even if I selected 1 for the progress bar options. There must be some other hidden setting that I forgot...

A good thing, the Kindle clock is now absent when reading. Thanks a lot for this!

Reader's setting

I recently had some problems to come back to my reading settings after using the file manager. This is now resolved and it works now normally.

03-10-2016, 10:22 AM	#942
roger64 Wizard Posts: 2,625 Karma: 3120635 Join Date: Jan 2009 Device: Kindle PW3 (wifi)	Hi Updating I succeeded to update Koreader to version 2015.11-175-g7b11491 using the Tools menu at the bottom of the Koreader main menu and then choosing Update KOReader option which is something we could not do on Kobo. OTA incremental updates are still a no-go but this is less important now that I know how to update the other way. Progress bar settings I had lost a mini-bar setting which I reactivated using frontend/apps/reader/module/readerfooter.lua (quite a hidden setting...) I still have a thin horizontal progress bar three millimeters from the top even if I selected 1 for the progress bar options. There must be some other hidden setting that I forgot... A good thing, the Kindle clock is now absent when reading. Thanks a lot for this! Reader's setting I recently had some problems to come back to my reading settings after using the file manager. This is now resolved and it works now normally. Last edited by roger64; 03-10-2016 at 10:26 AM.