Kindle -- KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3)

[roger64]

Hi

For the last 8 or 10 months, I have been a nearly exclusive Koreader user on Kobo Glo. Following the lastest jailbreak, I am now an exclusive Koreader user on PW3.

There were some crashes, mistakes while setting it up. Now, after one and a half day, I am trying hard to find any defects to Koreader.

Everything seems to work smoothly: OTA incremental updates, I can use my unchanged Evernote settings for highlights; Stardict dictionaries (3), side-loaded fonts. Even the missing mini-bar selection options can be installed and work. Too nice!! Is this normal?

Thank you so much to all who do a great job of supporting it.

[Belendir]

Hi

Yesterday I successfully applied the 5.6.5 JB on my Paperwhite 2 and updated to the new Amazon firmware afterwards. Now if I use Koreader there's an unusual problem when I view epubs with the framework enabled - every now and then, elements from the Amazon software pop up on top of the text I am reading with koreader. Mostly it's the clock in the upper right, sometimes the battery status as well. Other times the whole page gets blanked out with stuff from the new Amazon homescreen.
This happens with framework enabled only. Unfortunately I use KPVBooklets which seems to start with the framework.

I use the latest stable release of KOReader. Would do screenshots but don't know how. Thanks.

[NiLuJe]

@Belendir:

No completely unexpected, but annoying :/.

Note to self: check if this is still sane on 5.7.2.

[Belendir]

Sorry if I complicated things for you . Let me know if I can test anything to help.

[NiLuJe]

Nah, I'm just not at home right now, so I don't have my PW2 on hand to check .

[eschwartz]

I made this copy of the Kindle support thread and moved it to the KOReader forum.

(There is a notice in the OP for both copies, regarding which forum to post in, under what circumstances).


Ken, it's all yours.

[Ken Maltby]

Originally Posted by eschwartz

I made this copy of the Kindle support thread and moved it to the KOReader forum.

(There is a notice in the OP for both copies, regarding which forum to post in, under what circumstances).


Ken, it's all yours.

It makes sense to have them all here, and I will try to keep the local moderation working for all of them, but I sure hope the supportive Kindle users keep a subscription to the thread. I know very little about the Kindle devices.

Luck;
Ken

[gett]

Hi,
Is it possible to sync the reading position between PW3 and Android KOReader?

[Ken Maltby]

Originally Posted by gett

Hi,
Is it possible to sync the reading position between PW3 and Android KOReader?

I have had the progress sync work between my Kobo Aura HD and Android KOReader on my ASUS TF-101 tablet. I don't see any reason it couldn't work from your Kindle to your Android device - As long as both can run KOReader.

Luck;
Ken

[gett]

Originally Posted by Ken Maltby

I have had the progress sync work between my Kobo Aura HD and Android KOReader on my ASUS TF-101 tablet.

Thanks for answer.
Sorry for my ignorance - I can't find were and how to setup sync....

[Ken Maltby]

Originally Posted by gett

Thanks for answer.
Sorry for my ignorance - I can't find were and how to setup sync....

https://github.com/koreader/koreader/wiki/Progress-sync

A fuller explanation is needed though. As I remember it, it was where I had copies of the book on both devices and I had the Progress Sync set for the book on my Kobo. Then when I happened to open the book on my tablet, it asked if I wanted to sync it. I said yes or OK, and the book opened on the page I was on with the Kobo.
( Don't forget to turn the WiFi on.)

Luck;
Ken

I tried it again just now with the 8mb+ Recluse series that I am rereading now. I didn't have it on my tablet, so I used Zsync to send a copy from my Kobo to my tablet. Then when I opened the copy on my tablet it synced to the page I was on in the Kobo. (I had it set to "auto sync" in the book on the Kobo.)

[roger64]

Evernote plugin

I switched from Kobo to PW3 after the jailbreak (of course...) but I kept using Koreader. On the Kindle, I have not been able to use the OTA incremental updates. For some reason, it triggers a mistake everytime I try to use it.

So, some weeks ago I installed the v 2015.11-175-g7611491 version as an update. It works well, but I cannot find the Evernote plugin that I used before on the Kobo.

How could I expect to improve this (mainly the second point about the Evernote plugin)?

EDIT: the Evernote plugin is included with the latest update that I just downloaded. Sorry for this question. New version is v2015.11-318-g8c4c274
The Evernote plugin is working also.

and now, even the OTA incremental update has been successful for the first time (for me) because I now have v2015.11-328-g6f02b2c

Excellent!!

[roger64]

Mini-bar question

It happened two times already after a full update: the previous customized settings for my mini-bar changed.

Fortunately, I know how to get back to them following this path:
frontend/apps/reader/modules/readerfooter.lua and write your own settings with true/false.

Question: is it possible to keep these settings in default.persistent.lua?

You can see in the joint attachment my customized settings for the mini-bar: I only care about battery, time, and page progress (together).

and here as they are written within readerfooter.lua file

Spoiler:

function ReaderFooter:init()
self.pageno = self.view.state.page

self.settings = G_reader_settings:readSetting("footer") or {
disabled = false,
all_at_once = true,
progress_bar = false,
toc_markers = false,
battery = true,
time = true,
page_progress = true,
pages_left = false,
percentage = false,
book_time_to_read = false,
chapter_time_to_read = false,
}

[Ken Maltby]

Originally Posted by roger64

Mini-bar question

It happened two times already after a full update: the previous customized settings for my mini-bar changed.

Fortunately, I know how to get back to them following this path:
frontend/apps/reader/modules/readerfooter.lua and write your own settings with true/false.

Question: is it possible to keep these settings in default.persistent.lua?

You can see in the joint attachment my customized settings for the mini-bar: I only care about battery, time, and page progress (together).

and here as they are written within readerfooter.lua file

Spoiler:

function ReaderFooter:init()
self.pageno = self.view.state.page

self.settings = G_reader_settings:readSetting("footer") or {
disabled = false,
all_at_once = true,
progress_bar = false,
toc_markers = false,
battery = true,
time = true,
page_progress = true,
pages_left = false,
percentage = false,
book_time_to_read = false,
chapter_time_to_read = false,
}

The KOReader User Interface (UI) Reader Menu includes "Status bar" settings for those. (You need to reload the book to see the changes.)
While there isn't a persistent option that would survive an update, it should be easy to restore the settings to what you want after an update.

There is currently some discussion, at Github, about how this issue should be addressed. As to a separation of "defaults" into those for their respective functional areas or the existing global defaults. [ I would prefer separate treatment for the File Manager (global) options and for the Reader, CR3 & MU, options.]

Luck;
Ken

[roger64]

Originally Posted by Ken Maltby

The KOReader User Interface (UI) Reader Menu includes "Status bar" settings for those. (You need to reload the book to see the changes.)

Well, true, it's a matter of some clicks but I had failed to see it..
Should be a Linux bias.