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

[hawhill]

Oh dear, this thread's gotten long (and it's probably full of stuff that doesn't apply anymore). I don't think we ever planned to abandon a device, so if it doesn't work on the Kobo Touch, that would be clearly a bug. I'd really like to see the debug output from the command that @Markismus suggested in https://www.mobileread.com/forums/sho...postcount=1193

[simonchik]

@hawhill: I posted it already in #1196. If you have any ideas where to go next, I'd be more than happy to give it a try. I could try with the same thing with the latest nightly build? but then it will say that it can't find the light device...

[Markismus]

Originally Posted by simonchik

@hawhill: I posted it already in #1196.

I would rather see the full koreader.log and if possible the ev.log that is generated when you run reader in debug mode. The event log shows all the touch and button events and might give an indication for the tap problem. I posted an excel sheet and minimal explanation to change the ev.log to something readable here.

Are other users with an Touch mark3 experiencing the same problems with tapping?

[tshering]

v2014.04-139-gbac02ff runs nice on my Kobo Touch mark 3, and also on my Kobo Touch mark 4.

[WS64]

2 questions to Koreader, one I asked already in post #201 of this thread, but at least about one year ago when I posted the question first I did not see any answers.
Is it possible to keep the "toggle bold" setting persitent?
Koreader forgets it whenever i change books or even let the reader go to sleep. Since all other settigns seem to stay that sounds like a bug to me.

Second, I am a big fan of the tapzones, but I mainly tap at the very lower part of the screen. Unfortunately tapping at the very bottom of the screen Koreader just changes the appearance of the mini progressbar. Is it possible to keep the progress bar fixed and use the part of the screen to with the page turning tap zones? Maybe even without the progress bar at all...

[ipse]

How does one about suggesting a feature? I poked around github but didn't find a way to make a suggestion or request a feature.
Mine is very simple: resume the last open book from where it was left. Looks like a pretty basic functionality for a book reader.

PS. I might very well embarrass myself by requesting this when the feature actually exists...if it does, please guide me without slapping the innocent

[WS64]

Originally Posted by ipse

How does one about suggesting a feature? I poked around github but didn't find a way to make a suggestion or request a feature.
Mine is very simple: resume the last open book from where it was left. Looks like a pretty basic functionality for a book reader.

PS. I might very well embarrass myself by requesting this when the feature actually exists...if it does, please guide me without slapping the innocent

This feature is there.
You need to edit the place where reader.lua starts and remove the path behind.
I don't have my Kobo here right now but it is something like this:
Don't start
./reader.lua /mnt/onboard 2> crash.log
but
./reader.lua 2> crash.log

[hawhill]

Hm, doesn't the "history" menu option jump to the last used position? Otherwise, WS64 is correct, there is a certain invocation.

In any case: Just open an "issue" in github. It is a means of bringing things to attention - and feature requests, too.

WS64: I suggest to do the same for the things you mentioned. That "bold" setting going away sounds like a bug to me, too. As for tap zones, I'm not sure if we have a configurable for that in defaults.lua (a not-so-intuitive way to configure things we don't have a GUI for).

[Ken Maltby]

Originally Posted by ipse

How does one about suggesting a feature? I poked around github but didn't find a way to make a suggestion or request a feature.
Mine is very simple: resume the last open book from where it was left. Looks like a pretty basic functionality for a book reader.

PS. I might very well embarrass myself by requesting this when the feature actually exists...if it does, please guide me without slapping the innocent

Have you tried the History list? The top one has always been my current read on the last page I was in with all the settings as I left them.

You can also have "reader.lua" start without an argument, the default argument is "/mnt/onboard". I use "/mnt/sd/.Koreader/Books" as I have my library on the external uSD card. Without an argument it is supposed to open in the last document/book.

Luck;
Ken

The "koreader_kobo.sh" that the Start Menu uses is located here: /.kobo/kbmenu/onstart/koreader_kobo.sh this is the one you need to change for starting reader.lua using the Start Menu.

[ipse]

Originally Posted by Ken Maltby

Have you tried the History list? The top one has always been my current read on the last page I was in with all the settings as I left them.

That's how I use it now...but as you know, other readers (CR) can go straight to your last book/ last open page.

I will try to edit the reader.lua file - but assuming that works, will I still be able to get to the "Open file" menu to change books?
See, ignorance is bliss: for whoever uses the default Nickel, these are non-existing questions...when I look at my GF's (unrooted) Sony T1, I feel like crying

[simonchik]

@tshering: what firmware are you using? Did you try with kobo-file-monitor also?
I'll give your version a try anyway. *** EDIT: OK, doesn't work, neither with nickel nor kobostartmenu (I'm back on firmware 3.3.0, version 201401 works well except for the tapping issue):

./luajit: ./ffi/kobolight.lua:74: cannot open light device
stack traceback: [C]: in function 'assert' ./ffi/kobolight.lua:74: in function 'open' frontend/ui/device/kobopowerd.lua:16: in function 'init' frontend/ui/device/basepowerd.lua:16: in function 'new' frontend/ui/device.lua:240: in function 'getPowerDevice' ./reader.lua:180: in main chunk [C]: in function 'dofile' ./koreader-base:22: in main chunk [C]: at 0x0000c440

@markismus hahaha my mistake, didn't see the '-d'.......
OK, so here's what I have, after opening a small dejavu file, selecting some text - which is always easy, I can 'paint' as it says in the log when I tap and hold, the problem is when I tap normally, it's probably detected as a double-tap or something? - turning one or two pages, and trying to quit (never easy to get the "home" button!)
Anyway, here is my crash log, my ev log, and the ev log predigested by your excel script. Thank you so much!
**EDIT: Are these " 855686 EV_SYN 0 0 " extra events? Wondering what they mean. Some kind of parasite events?

[Markismus]

Originally Posted by hawhill

As for tap zones, I'm not sure if we have a configurable for that in defaults.lua (a not-so-intuitive way to configure things we don't have a GUI for).

There seems to be no tap zone defined for the mini-bar. Rather the tapzone for the config menu has been disabled to allow for the tapping of the minibar. See issue #506 where chrox introduced the minibar.

[tshering]

Originally Posted by simonchik

@tshering: what firmware are you using? Did you try with kobo-file-monitor also?

I am using FW 2.6.1 on the mark 3 Touch, and 3.4.1 on the mark 4 Touch. I am running both with the latest version of Kobo Start Menu. I did not try with fmon.

[Markismus]

Originally Posted by simonchik

OK, so here's what I have, after opening a small dejavu file, selecting some text - which is always easy, I can 'paint' as it says in the log when I tap and hold, the problem is when I tap normally, it's probably detected as a double-tap or something? - turning one or two pages, and trying to quit (never easy to get the "home" button!)
Anyway, here is my crash log, my ev log, and the ev log predigested by your excel script. Thank you so much!

Looking through the log the only thing that really differs from my logs is the fact that touch events are fed, while you're in hold state. It could be the difference between protocols, since the Aura is multitouch and the Touch is single touch only.

**EDIT: Are these " 855686 EV_SYN 0 0 " extra events? Wondering what they mean. Some kind of parasite events?

Every touch event generates a packet of data. The end of a packet is signaled by EV_SYN events. Not parasite, but order events. For an anarchist they might be the same, but it would involve much more code to organize the data.

Did you try swiping to change page instead of tapping? Did you turn multiple pages then, too?

[simonchik]

@tshering: something must differ in the hardware... I will try again with 2.6.1, but I would be _very_ surprised if it worked.