Koreader running on Kobos (all of them, hopefully!)

[gmw]

@NiLuJe very good. I had not noticed that distinction. No LED blinking, just the blinking squares which I had taken to mean a full restart. (To be clear: There is an LED that blinks during a power-on - it does not come on after KOReader exit.) Time difference doesn't seem obvious. (H2O v2 Product ID 378, FW v4.8.11073. kfmon v1.0.0)

[NiLuJe]

@gmw: I'm going to assume everything's peachy, then .

Note that there may still be something going slightly wonky somewhere, Mark7 handling is still a bit rough around the edges in general .

That, or those devices just cold boot significantly faster .

[gmw]

@NiLuJe Yes, all peachy on my device.

Maybe the Mark7 is faster, or maybe the fact that I only side-load epubs (there are no kepubs at all on this device at the moment) has an effect? Just guessing.

[NiLuJe]

@gmw: How much time does it actually take? (To cold boot, and to restart nickel on KOReader's exit).

Because if all is well, a restart should take less than 10s. When it takes a bit longer, it usually means that I did something wrong ^^ (or that Nickel is in a mood).

EDIT: I'd also ask you for your KOReader version, but with a H2O²r2, it's got to be pretty recent anyway .

[gmw]

As per my first post on the previous page, KOReader build 2018.06.02, with that minor config change.

After KOReader exit it's around 6-7 seconds (the first couple of those are still on the open book with no action apparent, presumably KOReader closing down, then about 4s of blink squares).

Power up is hard to get an exact start point, but there seems to be about 6s from first LED on until blinking squares, and then about 4s of those until up and running. So we're talking around 3s extra time over all ... very roughly.

[NiLuJe]

@gmw: Then yeah, I'd say everything's going according to plan, so, good news .

[CH23]

Originally Posted by NiLuJe

@CH23: Nnnnnnngh. If we need to dig into another weird Kobo sleep behavior, that's going to be fun fun fun...

hah yeah, i've read quite a lot throughout the years about that...

Anyway, thank you very much .

EDIT: On the off-chance there's something interesting in it about the suspend/reboot issues: what does koreader/crash.log says?

launching...
_ _____ ____ _
| |/ / _ \| _ \ ___ __ _ __| | ___ _ __
| ' / | | | |_) / _ \/ _` |/ _` |/ _ \ '__|
| . \ |_| | _ < __/ (_| | (_| | __/ |
|_|\_\___/|_| \_\___|\__,_|\__,_|\___|_|

It's a scroll... It's a codex... It's KOReader!
[*] Current time: 06/15/18-21:52:46[*] Version: v2015.11-1735-g14e7730_2018-06-02

ffi.load: blitbuffer
ffi.load (warning): libblitbuffer.so: cannot open shared object file: No such file or directory
ffi.load: SDL2
ffi.load (warning): libSDL2.so: cannot open shared object file: No such file or directory
ffi.load: SDL
ffi.load (warning): libSDL.so: cannot open shared object file: No such file or directory
06/15/18-21:52:46 ERROR Could not open file: /sys/class/backlight/lm3630a_led1b/bl_power
06/15/18-21:52:46 ERROR Could not open file: /sys/class/backlight/lm3630a_led1b/brightness
06/15/18-21:52:46 ERROR Could not open file: /sys/class/backlight/lm3630a_led1a/bl_power
06/15/18-21:52:46 ERROR Could not open file: /sys/class/backlight/lm3630a_led1a/brightness
06/15/18-21:52:46 INFO initializing for device Kobo_nova
06/15/18-21:52:46 INFO framebuffer resolution: {
["h"] = 1448,
["w"] = 1072
}
[ko-input] Forked off fake event generator(pid:1300).
ffi.load: libs/libfreetype.so.6
ffi.load: libs/libmupdf.so
ffi.load: libs/libwrap-mupdf.so
06/15/18-21:52:47 INFO opening file /mnt/onboard/books/seven.epub
06/15/18-21:52:48 INFO Loading plugins from directory: plugins
ffi.load: sqlite3
ffi.load: z
ffi.load: sqlite3
06/15/18-21:52:48 INFO Plugin plugins/hello.koplugin/main.lua has been disabled.
06/15/18-21:52:48 INFO Plugin plugins/autofrontlight.koplugin/main.lua has been disabled.
06/15/18-21:52:48 INFO RD loaded plugin SSH at plugins/SSH.koplugin
06/15/18-21:52:48 INFO RD loaded plugin AutoSuspend at plugins/autosuspend.koplugin
06/15/18-21:52:48 INFO RD loaded plugin backgroundrunner at plugins/backgroundrunner.koplugin
06/15/18-21:52:48 INFO RD loaded plugin batterystat at plugins/batterystat.koplugin
06/15/18-21:52:48 INFO RD loaded plugin calibrecompanion at plugins/calibrecompanion.koplugin
06/15/18-21:52:48 INFO RD loaded plugin coverbrowser at plugins/coverbrowser.koplugin
06/15/18-21:52:48 INFO RD loaded plugin evernote at plugins/evernote.koplugin
06/15/18-21:52:48 INFO RD loaded plugin goodreads at plugins/goodreads.koplugin
06/15/18-21:52:48 INFO RD loaded plugin keepalive at plugins/keepalive.koplugin
06/15/18-21:52:48 INFO RD loaded plugin kobolight at plugins/kobolight.koplugin
06/15/18-21:52:48 INFO RD loaded plugin kosync at plugins/kosync.koplugin
06/15/18-21:52:48 INFO RD loaded plugin newsdownloader at plugins/newsdownloader.koplugin
06/15/18-21:52:48 INFO RD loaded plugin perception_expander at plugins/perceptionexpander.koplugin
06/15/18-21:52:48 INFO RD loaded plugin readtimer at plugins/readtimer.koplugin
06/15/18-21:52:48 INFO RD loaded plugin send2ebook at plugins/send2ebook.koplugin
06/15/18-21:52:48 INFO RD loaded plugin statistics at plugins/statistics.koplugin
06/15/18-21:52:48 INFO RD loaded plugin systemstat at plugins/systemstat.koplugin
06/15/18-21:52:48 INFO RD loaded plugin terminal at plugins/terminal.koplugin
06/15/18-21:52:48 INFO RD loaded plugin timesync at plugins/timesync.koplugin
06/15/18-21:52:48 INFO RD loaded plugin zsync at plugins/zsync.koplugin
06/15/18-21:52:58 ERROR Could not open file: /sys/class/backlight/lm3630a_led1b/bl_power
06/15/18-21:52:58 ERROR Could not open file: /sys/class/backlight/lm3630a_led1b/brightness
06/15/18-21:52:58 ERROR Could not open file: /sys/class/backlight/lm3630a_led1a/bl_power
06/15/18-21:52:58 ERROR Could not open file: /sys/class/backlight/lm3630a_led1a/brightness
./luajit: frontend/ui/screensaver.lua:27: cannot open /mnt/onboard/.adds/koreader/wallpapers/: No such file or directory
stack traceback:
[C]: in function 'dir'
frontend/ui/screensaver.lua:27: in function 'getRandomImage'
frontend/ui/screensaver.lua:231: in function 'show'
frontend/device/generic/device.lua:143: in function 'onPowerEvent'
frontend/ui/uimanager.lua:93: in function 'Suspend'
frontend/ui/uimanager.lua:943: in function 'suspend'
frontend/ui/uimanager.lua:111: in function 'handler'
frontend/ui/uimanager.lua:797: in function 'handleInputEvent'
frontend/ui/uimanager.lua:860: in function 'handleInput'
frontend/ui/uimanager.lua:904: in function 'run'
./reader.lua:195: in main chunk
[C]: at 0x000139b9

It does seem like something to be fixed, but adding the wallpapers directory, and an image in it, makes it work correctly.

Would be nice if it would check if the wallpaper directory set in the settings, exists.

[NiLuJe]

@CH23: *huge sigh of relief* .

Yeah, at the very least not horribly crashing would be better, yeah .

EDIT: Done .

EDIT²: And the matching PR.

[CH23]

Originally Posted by NiLuJe

@CH23: *huge sigh of relief* .

Yeah, at the very least not horribly crashing would be better, yeah .

EDIT: Done .

EDIT²: And the matching PR.

great!

Didn't have a chance to test this yet, but since it's a very minor adjustment, i doubt it could bring wreckage to the program

[hfpop]

As a general rule, I noticed that the same user font is rendered visibly bolder by KOReader than by Nickel on my KA1-LE. Is this really the case? Can I adjust KOReader to have the same weight as Nickel?

[NiLuJe]

@hfpop: There's a contrast setting both in Nickel & KOReader. But since they're two different renderers, you probably won't be able to make them agree in every circumstances.

(Although switching KOReader to Native hinting may help close the gap on most decently hinted fonts).

[cramoisi]

@hfpop I've seen threads on the kobo forum about differences in fonts rendering on kindle and kobo (which is more or less the same issue). These things can be corrected by changing one value (panose) in the font with fontforge (but just now I'm too lazy to search it back) ; If I'm not wrong, GERGE is the person you should seek for advice.

There is also some tips at the end of the wiki page for using fontforge : https://wiki.mobileread.com/wiki/Kobo_eReader

and IIRC there is a script to "koboify fonts" : the result seems to make them more the same when you use them on nickel and on koreader.

Whatever the result, these are some funny things to try :-)

[roger64]

I never tried to play around with panose values but this could prove interesting to modify side-loaded fonts.

I just took a screenshot of the wiki signalled by cramoisi and of an illustration about panose values.

[NiLuJe]

IIRC, some renderers entirely bypass the Panose metadata. I can't remember which though (might be Kindle/M7, Kindle/KF8, might be Nickel/ADE, might be Nickel/kePub, and I don't think we care in KOReader either, because we're not using fontconfig).

Do note that I'm pretty sure this doesn't affect weight at all, it affects what the renderer *thinks* the weight of that font is. i.e., that specific bit in the WiKi is to fix Nickel 'missing' the Book/Medium weight, and instead falling back to bold, and as such rendering (mostly) everything with the bold style of the family.

[hfpop]

Thank you all for your help. I have one more question in the actual file names scheme. The base name of the files have to match the internal font name. In the case given in the cited wiki, I have the following, in FontForge:

Element / Font Info / PS Names:
Fontname: AmazonEmber-Regular
Family Name: Amazon Ember
Name For Humans: Amazon Ember
Base Filename: Same as Fontname

Element / Font Info / TTF Names:
Family: Amazon Ember
Styles: Regular
Fullname: Amazon Ember

The file is saved as AmazonEmber-Regular.ttf, but the windows font viewer sees the font name as Amazon Ember. Question: I should rename the file to read Amazon Ember-Regular.ttf, even if it is saved as AmazonEmber-regular.ttf, right ?

Thank you.