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

[kwokhin]

Hello there (especially ken,
After a few days with Koreader, I have experienced some issues. It always suddenly forces back to KSM! It always does when I am trying to look up in the dictionary or highlighting. It's kind of annoying. Also, when I try to go to page 24, for example, it goes to page 544. Does this happen to you guys' devices? Is it that Koreader has not yet fully support Kobo Glo HD? I'm currently using the version built in May. I tried the latest build but it seems worse.

[embryo]

This is a cross-post to the koreader - cool reader thread, for the same problem that I have with both of them (I think they use the same epub engine..).

The problem is that when I read an epub that uses proportional and monospaced fonts the monospaced are much bigger than my chosen proportional fonts.
So how can I change the monospaced font?
Can I rename my chosen monospaced font with the name of my favorite font family and make the reader use them instead?
If so, with what name.

Any other way?

SOLVED: kaznelson gave me the solution for the coolreader (which applies to koreader too)!

[Ken Maltby]

Originally Posted by kwokhin

Hello there (especially ken,
After a few days with Koreader, I have experienced some issues. It always suddenly forces back to KSM! It always does when I am trying to look up in the dictionary or highlighting. It's kind of annoying. Also, when I try to go to page 24, for example, it goes to page 544. Does this happen to you guys' devices? Is it that Koreader has not yet fully support Kobo Glo HD? I'm currently using the version built in May. I tried the latest build but it seems worse.

I don't have or use a Glo HD, and it is very new to Koreader, but you should not be seeing those kind of issues. Is this only with PDFs? You could try adding another stardict dictionary file to those you already placed in /.adds/koreader/data/dict/. I have 4 or 5. "Go to page" works fine for me. You might want to open an issue at the project on Github, this is the kind of thing that gets addressed, relatively quickly for newly added devices. If there are any other Glo HD Koreader users, who are encountering such issues, it would help to hear from them as well.

So far there has been only two nightly releases with Glo HD support.

Luck;
Ken

[xor_]

Based on running koreader build 249 on my Glo HD for a few days:

Overall koreader works very well on my Glo HD. No frequent crashes for me. I tried some of the things kwokhin mentioned, but none of them crashed koreader for me.

I did see an occasional crash or two, but not frequent enough to bother me, and without me noticing a pattern. I also have occasional crashes on the old Glo, the HD isn't doing any worse in that regard.

A minor thingie I've seen recently, both on the Glo and the Glo HD, is that "unhighlight" doesn't work.

I did see a relatively short battery cycle, and surprisingly big load percentage point drops. But it was the first charge cycle, so I don't think any big conclusions can be drawn from that yet.

The menu icons are a bit smaller than on the Glo, and the menu bar doesn't fill out the whole screen width. But not by much.

Overall, it seems very usable. Thanks for supporting the new device so quickly.

[Ebri]

Kwokhin have you tried it with different books? Does it work perfectly on (more than one) other readers and apps?

[church mouse]

Originally Posted by xor_

One minor issue I've seen on the
HD: when I search for a book from calibre library, and then try to open a book from the resulting list, the loading fails with a path error. So the search function finds the book, but somehow the loading function treats the book subdirectory as an absolute path. When I just walk the file manager list, and select the book by hand, it works.

XOR - in the defaults.lau file in the koreader folder(or your persistents version if you have created one) you will see towards the bottom lines for:
SEARCH_LIBRARY_PATH =
SEARCH_LIBRARY_PATH2 =

complete these with the path for your library such as "/mnt/onboard"

and see if this works.

[xor_]

Edit:
Ah, I have it working. I think it was related to my old Calibre version that still had settings for the non-HD Glo. So not a koreader problem. Sorry.

[kwokhin]

Originally Posted by Ken Maltby

I don't have or use a Glo HD, and it is very new to Koreader, but you should not be seeing those kind of issues. Is this only with PDFs? You could try adding another stardict dictionary file to those you already placed in /.adds/koreader/data/dict/. I have 4 or 5. "Go to page" works fine for me. You might want to open an issue at the project on Github, this is the kind of thing that gets addressed, relatively quickly for newly added devices. If there are any other Glo HD Koreader users, who are encountering such issues, it would help to hear from them as well.

So far there has been only two nightly releases with Glo HD support.

Luck;
Ken

Thank you Ken for your help.
Since I had been changing between builds and installing different softwares, I chose to do a factory reset and start all over again.
I installed koreader-nightly-20150604 and everything seems to work nicely. I haven't experienced any crashes since then. Regarding the strange page jump from page 34, for example, to 355, is because of the fact that I always accidentally pressed the links that transfer to the Appendix Now I swipe to the left instead of pressing and it seems to help avoid that.

I will definitely report on Github if I always encounter problems. Again, thank you Also, it's my bad to ask for help immediately before really trying to figure it out myself in the first place

[kwokhin]

Originally Posted by Ebri

Kwokhin have you tried it with different books? Does it work perfectly on (more than one) other readers and apps?

It turned out that it was my fault because I always accidentally pressed the words that would take me to the Appendix. My bad. Koreader runs perfectly on my Glo HD ever since I have done a factory reset and install the koreader-nightly-20150604.
Thanks for the suggestion I'm very happy with the PDF reading experience Koreader brings and the high quality screen Glo HD has!

[kwokhin]

Originally Posted by xor_

Based on running koreader build 249 on my Glo HD for a few days:

Overall koreader works very well on my Glo HD. No frequent crashes for me. I tried some of the things kwokhin mentioned, but none of them crashed koreader for me.

I did see an occasional crash or two, but not frequent enough to bother me, and without me noticing a pattern. I also have occasional crashes on the old Glo, the HD isn't doing any worse in that regard.

A minor thingie I've seen recently, both on the Glo and the Glo HD, is that "unhighlight" doesn't work.

I did see a relatively short battery cycle, and surprisingly big load percentage point drops. But it was the first charge cycle, so I don't think any big conclusions can be drawn from that yet.

The menu icons are a bit smaller than on the Glo, and the menu bar doesn't fill out the whole screen width. But not by much.

Overall, it seems very usable. Thanks for supporting the new device so quickly.

I'm on my first battery cycle too. I'm surprised how fast the battery drops. I don't have a reference of how long should the battery of a ereader lasts but for my Glo HD, I will have to charge it every few days.

I hope that the battery performance would improve after the first few battery cycle.

[freekobo]

Keep wifi off its a battery drain

[xor_]

I'm trying to understand what happens on my Glo HD device when I suspend it with the magnet cover mechanism while koreader is running. (No nickel in the background, started from KSM)

The background is, I easily get 30 percentage point charge drops per day, with my Glo HD sitting still being "suspended" by the cover. And that just seems too much. I used to think the device just wakes up occasionally when I move it around during the day in my bag. But I get those drops even when I make sure it just sits still all day. It does show the book cover screensaver and the "Suspended" message.

I've always felt that on the old Glo the battery cycles were shorter than under nickel, but it's never been as drastic as what I see on the Glo HD (which I think is supposed to have a stronger battery).

I assumed the suspend.sh script would be involved, and thought maybe it would help if I tried an

echo disk > /sys/power/state

instead of the suspend to RAM command involved. But I was surprised to see that when I put a debug statement like

date >> /mnt/onboard/mydate.txt

into suspend.sh, that file never gets written when the sleep cover is activated. It looks like that script isn't being executed.

So I thought instead of digging into the code trying to understand what's happening, I'd ask in case someone knows off the bat.

[Markismus]

Originally Posted by xor_

I'm trying to understand what happens on my Glo HD device when I suspend it with the magnet cover mechanism while koreader is running. (No nickel in the background, started from KSM).

We've been discussing it on github issue #1356. Remembering your hacks a few years back, I welcome your contribution to the discussion.

[xor_]

Originally Posted by Markismus

We've been discussing it on github issue #1356. Remembering your hacks a few years back, I welcome your contribution to the discussion.

Gee, thanks. But those really only were minor, and dirty, hacks. Not sure how much I can contribute. But I'll take a look.

//////////

Edit: I made sure to observe that battery charge dropping for several days in a row before I posted. But sure enough, the day after my post, my Glo HD is only losing a respectable 2% during standby. I hate it when that happens. Of course I did upgrade to the latest nightly build yesterday, so maybe that has something to do with it? I'll keep monitoring it.

Anyway, I played around at the command line a bit today, to catch some of the default processor settings. Seems like the Glo HD is engaging the interactive governor. Max freq 996, min freq 396. Maybe that min freq could be lowered a bit? I'm attaching the findings in case someone more CPU-savvy than me can spot something. Including a dmesg of a couple of suspend/resume cycles. I will try to replicate that next time I encounter a large drop.

[jberd]

The front light on my Kobo H2o isn't coming back on when it wakes from sleep.
Is anyone else having this issue?

I have the latest KSM (with update 4) and the latest koreader nightly. Koreader goes to sleep well enough, but when it wakes up, even if the light was on before, the front light is off.

I'm not sure what KOBO_LIGHT_OFF_ON_SUSPEND is supposed to do, but I tried putting it in defaults.lua, both true and false, and nothing changed. I had KOBO_LIGHT_ON_START = -1 before, which I thought was supposed to do the right thing, but for now I changed it to KOBO_LIGHT_ON_START = 10, which starts up the light upon awakening regardless of the previous state.