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

[simonchik]

@Markismus: thank you. Yes, that must be a protocol problem. Swiping gestures don't work at all.
So the touch events are the "39161 EV_SYN 0 0 " (# tev fed| 32 | 739161 | 209 | 114 | -1 | Evt 0) thingies, huh?
Maybe could we try in, say, input.lua or gesturedetector.lua to block those tevs? I see that in input.lua there is "if Device:getModel() ~= 'Kobo_phoenix", could this be used for the mark3 as well? Or maybe the function "function GestureDetector:feedEvent(tevs)" could be hacked?

[tshering]

Originally Posted by simonchik

@tshering: something must differ in the hardware...

My mark 3 Touch is model N905B. I don't know what is the difference to even older models, apart perhaps from the internal SD card.

Originally Posted by simonchik

I will try again with 2.6.1, but I would be _very_ surprised if it worked.

Me too.

[Markismus]

Originally Posted by simonchik

@Markismus: thank you. Yes, that must be a protocol problem. Swiping gestures don't work at all.
So the touch events are the "39161 EV_SYN 0 0 " (# tev fed| 32 | 739161 | 209 | 114 | -1 | Evt 0) thingies, huh?
Maybe could we try in, say, input.lua or gesturedetector.lua to block those tevs? I see that in input.lua there is "if Device:getModel() ~= 'Kobo_phoenix", could this be used for the mark3 as well? Or maybe the function "function GestureDetector:feedEvent(tevs)" could be hacked?

You have two touch events associated with a tap. Screen touch and touch release. The -1 is a release, the 1 at the same location in other tev fed is a touch.

If the touch release doesn't happen for a while, than the code interprets it as a hold. If you touch very slightly and touch again --trembling fingers or something like that-- it could be registered as a double tap.

A single tap gesture would turn the page, a hold gesture would select a word for highlighting or translation and a double tap would zoom the page (if enabled in defaults.lua.)

Everything can be hacked. But I would suggest that you get telnet up and running, that you get the debug output to the telnet terminal instead of the log file, that you experiment with what kind of touches generate what kind of gestures.

When you have a clear idea what is happening, I would suggest hacking gesturedetector.lua until you have something that works. Important are the constants in GestureDetector (line 44-55). First try fiddling with these to see what the do and what impact they have on your gestures. Open an issue in github to address your problem and report your findings. The developers are really helpful.

[simonchik]

@tshering: mine is a 2011 fnac kobo, I think N905 non B..

[simonchik]

@markismus: alright, I'll do that then. Thank you!

[Markismus]

Originally Posted by simonchik

./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

This issue is still non resolved. However a workaround is suggested by commenting out a line. Could you change line 16 in kobopowerd.lua to self.fl = {} and see whether it gets rid of the crash?
It's fixed in the next release.

Shouldn't this be a problem for the Kobo Mini, too? Or did Mini owners learn the hard way not to fiddle around with the frontlight settings?

[simonchik]

@markismus:

Could you change line 16 in kobopowerd.lua to self.fl = {} and see whether it gets rid of the crash?

It doesn't, but

self.fl=nil

does. Wonderful! Except that now, tapping doesn't work _at all_ on this version. I'll investigate. My!

[simonchik]

@markismus: about version 20140602, here's my output now:

# hold_release detected in slot 0
# in tap state...
# set up hold timer
# in tap state...
# hold gesture detected in slot 0
# in hold state...
# in hold state...
# in hold state...
# in hold state...
# in hold state...
# in hold state...
# in hold state...
# hold_release detected in slot 0

[simonchik]

@markismus: about versions that 'work' on my kobo, I now have a clearer idea about what's happening: if I put my finger on the screen, I get

# tev fed| 558 | 291854 | 342 | 307 | 1 | Evt 0
# in tap state...
# set up hold timer
# hold gesture detected in slot 0
# in hold state...
# tev fed| 558 | 405127 | 341 | 307 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 504107 | 341 | 308 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 688109 | 340 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 558 | 872074 | 339 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 27735 | 339 | 310 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 225903 | 338 | 311 | 1 | Evt 0
# in hold state...
# tev fed| 559 | 749673 | 337 | 311 | 1 | Evt 0
# in hold state...
# tev fed| 560 | 4570 | 337 | 309 | 1 | Evt 0
# in hold state...
# tev fed| 560 | 13418 | 337 | 309 | -1 | Evt 0
# in hold state...
# hold_release detected in slot 0

which means that tev is populated with touch events from very close coordinates, as if I were moving my finger, except I'm not. There is no multitouch, no "two finger-tap" and so on, so I think the best think would be to put a threshold, like 5 points or so on this device, below which a touch event on hold state would be discarded?

[Markismus]

Originally Posted by simonchik

@markismus: about versions that 'work' on my kobo, I now have a clearer idea about what's happening: if I put my finger on the screen, I get [CODE]# tev fed| 558 | 291854 | 342 | 307 | 1 | Evt 0
# in tap state...
# set up hold timer
# hold gesture detected in slot 0
# in hold state...

Let's move the work to this dedicated github issue.

[simonchik]

Oh, you've done the work already! Thanks a million! I was about to open myself an account..

[Ken Maltby]

With the "Start with last open file" checked on the "File Manager" home page menu, how do you get out of that file and able to select another. Every time I start koreader I am in that file or in a black page where koreader stops responding. I can't get back to the File Manager and its menu, to change the setting.

Luck;
Ken

[simonchik]

@Ken: I think it gets back to Nickel when you close the file, not to the file manager.

[Ken Maltby]

Originally Posted by simonchik

@Ken: I think it gets back to Nickel when you close the file, not to the file manager.

Thanks, but there is no Nickel on my Android tablet. It works fine with the current build on my AuraHD 3.2.0, leaving the book returns to the File Manager and I can uncheck the selection. Leaving the book in Koreader on Android, with the option checked, puts me back on the Android page I launched Koreader from. It would be great if it worked in Android the same way it does on my AuraHD.

Luck;
Ken

You can clear the app's data, but that's pretty drastic, for an issue like this.

[WS64]

I know these are not stable, but did anyone notice more crashes than usual in the last two days nighties (June 6 and 5)?
I can't read at all since they crash after about 2 minutes reading...
Is there anything I can do to find out why they are crashing?