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

[JosephWebber]

(Not having had a reply on the main KOReader board, I thought maybe this was the more appropriate place for it).
I have a PW1 which used to run KOReader.
I made the mistake of switching on wifi and it was updated to 5.6.1.1 so now KOReader does not work although the KUAL extensions (calculator etc) do.
I have installed the hotfix using Update Your Kindle but if I try to open an epub it says “Application Error: the selected application could not be started”, and if I try to start KOReader from KUAL the message “KOReader starting” appears for a few seconds and then goes off..
I copied the contents of kindle-5.4-jailbreak.zip to Kindle root, then [HOME] -> [MENU] > Settings -> [MENU], but Update Your Kindle is greyed out (although I know the update bin was there).
I also tried the MRPI approach. I successfully installed it and copied KOReader into mrpackages, but when I ran it it said no mrpackages were found.
Help would be much appreciated, both in unravelling whatever I have done wrong and in describing the sequence of steps to do it correctly.
Many thanks.

[shamanNS]

Try newer nightly build of KOreader. There was a build that had those same problems on my PW3 with fw 5.6.5. It couldn't open any epub or mobi books. And the same build of KOreader for Android would just hang on black screen.
KOreader v2015-11-253-gcf9dc26 works without problem on my PW3 with fw 5.6.5. I have a PW1 also but it's still on fw 5.4.4 so I can't help you test different KOreader nightly.

[pefilix]

...

sorry wrong koreader topic

[nestown]

hi,
i'm a very fresh user of kindle paperwhite et e-reader in general.
I add the mod Koreader wich is excellent, i'm just wondering if there is a way to add the epub directly on the home page ?
Or do we have to browse the kual menu >koreader...etc..

Thanks in advance,

Nes

[NiLuJe]

@nestown: Via KPVBooklet, yes (see the wiki on github for more details).

[roger64]

Hi

One of the freedoms Koreader provides is that it allows you to use the font of your choice. On my PW3, I can use the fonts provided by Amazon for the Kindle, the ones provided by Koreader and others that I added myself.

The problem is that it's a bit too much. Though I ordinarily use less than half a dozen, my screen is cluttered by four pages of fonts. See a screenshot for one of these pages. For example I don't even remember using once Helvetica Neue or Futura (though I like Bookerly).

We have no control at all regarding Kindle fonts. Regarding them, is there a way to clean their display? (select some, put away others).

Also, if I suppress some of the Koreader fonts, will I get them back at the next OTA update?

[nestown]

Originally Posted by NiLuJe

@nestown: Via KPVBooklet, yes (see the wiki on github for more details).

Thanks a lot for your reply , i'll check that.

Nes

[Ken Maltby]

Originally Posted by roger64

Hi

One of the freedoms Koreader provides is that it allows you to use the font of your choice. On my PW3, I can use the fonts provided by Amazon for the Kindle, the ones provided by Koreader and others that I added myself.

The problem is that it's a bit too much. Though I ordinarily use less than half a dozen, my screen is cluttered by four pages of fonts. See a screenshot for one of these pages. For example I don't even remember using once Helvetica Neue or Futura (though I like Bookerly).

We have no control at all regarding Kindle fonts. Regarding them, is there a way to clean their display? (select some, put away others).

Also, if I suppress some of the Koreader fonts, will I get them back at the next OTA update?

It looks like they are listed alphanumerically, you could try renaming the ones you don't use with a zz at the start of the file name. You might need to change the name in the file's properties, as well. Then they would appear on the last page.

Caution the font's name can be critical to its use, but depending on where the list building is getting the name used for the listing, it could work. You might also be able to order the list with numbers at the start. (Tried adding a 2 in front of one of my fonts and it worked in the Vlasovsoft File Manager but the listing remained the same in KOReader (the font worked also, the 2 in the name had no effect).

Luck;
Ken

[NiLuJe]

@roger64: The startup script setups a bunch of loop mounts to "catch" every nook and cranny where fonts could be hidden on Kindles .

You could zap one of those if you wanted to disable *a full set* of those (say, *all* the default Amazon fonts), but you can't really pick and choose that way.

(Unless you do that, and *copy* the fonts you're actually interested in in KOReader's default font location).

@Ken Maltby: Can't really do that, they're hosted on the read-only rootfs, and some are instrumental in successfully booting the device .

----

@roger64: Note that, for the same reason, you'll probably want to do your copies from KOReader's FM *before* killing the loop-mount if you don't have shell access to your device .

[roger64]

Thank you for your replies.

I don't dare interfer with the script set-ups. I understand that asking a simple question does not mean that there is a simple solution...

[kopuu]

Hi

I just bought PW3 and Jailbreaked with exactly the same steps of https://www.mobileread.com/forums/sho...d.php?t=275877 then install KUAL+Helper+MR Package Installer from https://www.mobileread.com/forums/sho...44&postcount=1 and KOReader from https://www.mobileread.com/forums/sho...45&postcount=2

I just want to read PDF and EPUB files on PW3 so I choose to use KOReader.
I tried to start KOReader from KUAL by tapping "Start the filemanager" but it just show "Starting KOReader..." then nothing is happen, just a flush display.
Tapping "(no framework)" and "(ASAP)" options are the same result, nothing happened just move to home page.
I tried some other version of KOReader which available on https://github.com/koreader/koreader/releases, for example "koreader-kindle-arm-linux-gnueabi-v2015.11-507-gef260f0.zip" but nothing was changed, the same failure.

Here is a crash.log I can get from KUAL:

--------------------------------------------------------------------------------
[1/1/16 12:05 AM] KUAL (v. 2.6)

java.security.AccessControlException: access denied (java.io.FilePermission /var/tmp/KUAL.mbx read)
at java.security.AccessControlContext.checkPermission (Compiled Method)(Unknown Source)
at java.security.AccessController.checkPermission(Com piled Method)(Unknown Source)
at java.lang.SecurityManager.checkPermission(Compiled Method)(Unknown Source)
at java.lang.SecurityManager.checkRead(Compiled Method)(Unknown Source)
at java.io.File.isFile(Compiled Method)(Unknown Source)
at com.mobileread.ixtab.kindlelauncher.Util.sureFileR eader(Util.java:49)
at com.mobileread.ixtab.kindlelauncher.resources.Mail boxProcessor.isRinging(MailboxProcessor.java:89)
at com.mobileread.ixtab.kindlelauncher.resources.Mail boxProcessor.access$000(MailboxProcessor.java:9)
at com.mobileread.ixtab.kindlelauncher.resources.Mail boxProcessor$1.run(MailboxProcessor.java:61)
at com.mobileread.ixtab.kindlelauncher.timer.JTimerAd apter$1.run(JTimerAdapter.java:14)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
at java.lang.Thread.startup(Unknown Source)


PW3 version is v5.7.4 (upraded by the step of https://www.mobileread.com/forums/sho...d.php?t=275877 )

I did not do anything except above, not register the kindle, connect to WiFi, login etc.
Does anyone have any idea?

Should I upgrade or downgrade PW3 firmware?
Should I install a specific version of KOReader for PW3?

[NiLuJe]

@kopuu: Okay a few unrelated things, so, in more or less random order:

* That KUAL crash.log is for, well, KUAL itself, it's not related to KOReader. And there's nothing particularly worrying about it, it's a known issue, most often seen on first launch (especially afer a cold boot). For more details and potential workarounds (i.e, gawk), check the KUAL thread.

* KOReader should definitely run on your device, regardless of the FW. So, we're going to need to see another crash.log, KOReader's . (Should be in koreader/crash.log).
I can't recall the particulars, but, yeah, on a PW3, you'll probably want a recent nightly (possibly even an OTA build if you have a White PW3), and not the latest release.

[kopuu]

Originally Posted by NiLuJe

@kopuu: Okay a few unrelated things, so, in more or less random order:

* That KUAL crash.log is for, well, KUAL itself, it's not related to KOReader. And there's nothing particularly worrying about it, it's a known issue, most often seen on first launch (especially afer a cold boot). For more details and potential workarounds (i.e, gawk), check the KUAL thread.

* KOReader should definitely run on your device, regardless of the FW. So, we're going to need to see another crash.log, KOReader's . (Should be in koreader/crash.log).
I can't recall the particulars, but, yeah, on a PW3, you'll probably want a recent nightly (possibly even an OTA build if you have a White PW3), and not the latest release.

Thanks for letting me know!
I found the KUAL crash.log and it says;

./luajit: frontend/device/kindle/device.lua:396: unknown Kindle model 90
stack traceback:
[C]: in function 'error'
frontend/device/kindle/device.lua:396: in main chunk
[C]: in function 'probeDevice'
frontend/device.lua:38: in main chunk
[C]: in function 'require'
frontend/ui/uimanager.lua:1: in main chunk
[C]: in function 'require'
./reader.lua:96: in main chunk
[C]: at 0x0000be9d



My PW3 is White version and arrived a few days ago. The serial # starts with G090KB.
Are there any crews?

[NiLuJe]

@kopuu: You'll probably need to wait for a more recent OTA build, or the next nightly.

And I need to fix that error message, it's not accurate in your case .

[johnnyb]

Originally Posted by kopuu

Thanks for letting me know!
I found the KUAL crash.log and it says;

./luajit: frontend/device/kindle/device.lua:396: unknown Kindle model 90
stack traceback:
[C]: in function 'error'
frontend/device/kindle/device.lua:396: in main chunk
[C]: in function 'probeDevice'
frontend/device.lua:38: in main chunk
[C]: in function 'require'
frontend/ui/uimanager.lua:1: in main chunk
[C]: in function 'require'
./reader.lua:96: in main chunk
[C]: at 0x0000be9d



My PW3 is White version and arrived a few days ago. The serial # starts with G090KB.
Are there any crews?

I basially had the same problem on the same device and "solved" it by just switching to the latest nightly (props on the new num-pad!)... Smooth sailing so far, no hickups...