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

[Markismus]

@xping Thanks. Did it get more frequent with the changes? Could you also send an ev.log?

Too bad that you didn't get rid of the config error. Better delete the entire koreader directory before you update to get rid of the [WARNING]Config version too old !! Please update config file !!

UPDATE: I see the bug now. You can get rid of the concatenate-error by changing in gesturedetector.lua in koreader/frontend/ui/:

• line 84: add --

This comments out the DEBUG line I used.
You can also get rid of the concatenate-error by not using the -d flag while calling reader.lua.

I would still like to see the ev.log's. Appearently, rather often there are touch events without x- or y-coordinates. Eventually, this should be fixed in input.lua.

I didn't see it, because I confused it with this error:

/luajit: ./frontend/ui/gesturedetector.lua:149: attempt to perform arithmetic on field 'y' (a nil value)

[Markismus]

@xping Could you replace all ".." by "," in line 84 of gesturedetector.lua and see if you get rid of the error?
The DEBUG function could allow nil values, while the string concatenate function ".." doesn't.

[xping]

Originally Posted by Markismus

@xping Thanks. Did it get more frequent with the changes? Could you also send an ev.log?

Too bad that you didn't get rid of the config error. Better delete the entire koreader directory before you update to get rid of the [WARNING]Config version too old !! Please update config file !!

UPDATE: I see the bug now. You can get rid of the concatenate-error by changing in gesturedetector.lua in koreader/frontend/ui/:

• line 84: add --

This comments out the DEBUG line I used.
You can also get rid of the concatenate-error by not using the -d flag while calling reader.lua.

I would still like to see the ev.log's. Appearently, rather often there are touch events without x- or y-coordinates. Eventually, this should be fixed in input.lua.

I didn't see it, because I confused it with this error:

/luajit: ./frontend/ui/gesturedetector.lua:149: attempt to perform arithmetic on field 'y' (a nil value)

I have no ev.log file. I activate logging using the string you specified some posts before (U can find it in mi zip file).

Give me instructions on how to activate event logging...

Now will try mods proposed up....
For now I can say that I get out from koreader almost on a page turning on ten (every 8/10 pages)...
thx

[Markismus]

I usually get ev.log as soon as I enable debugging mode with the flag -d after reader.lua. I have no idea why on your reader ev.log is not or cannot be created.

Could you try the modification of post #887 first?

[xping]

Originally Posted by Markismus

I usually get ev.log as soon as I enable debugging mode with the flag -d after reader.lua. I have no idea why on your reader ev.log is not or cannot be created.

Could you try the modification of post #887 first?

I tried modifications of post 887. I have to say that on my kobo mini the problem for now is solved. No accidental exit to nickel. I noticed only that the reader is less responsive (maybe the modifies to lines 440 662 and 665 in input.lua???)....

On my aura hd I have accidental exit when I modified back (restored to original) lines 440 662 and 665.... Now I am trying devices (mini and aura hd)...

A question: If I comment (adding --) line 84 in gestures.lua, do I get useful log files??

I have to say that I use ken maltby mod to koboreader_kobo.sh:
#!/bin/sh
export LC_ALL="en_US.UTF-8"

# we're always starting from our working directory
cd /mnt/onboard/.kobo/koreader/

# export trained OCR data directory
export TESSDATA_PREFIX="data"

# export dict directory
export STARDICT_DATA_DIR="data/dict"

# Decrease the reasons for crashes. Search forum for cgm999's explanation.
exec 3<&-

# stop Nickel
killall -STOP nickel
killall -STOP hindenburg

# finally call reader
./reader.lua /mnt/sd/.Library 1> koreader.log.`date +%s` 2>&1

# continue with nickel
killall -CONT hindenburg
killall -CONT nickel


to return to nickel after exiting koreader. I noticed that with this mod I get more responsiveness to koreader. Instead, if I use standart koboreader_kobo.sh, the reader is so slow that hardly can be used. Is it right????

[Markismus]

Originally Posted by xping

I tried modifications of post 887. I have to say that on my kobo mini the problem for now is solved. No accidental exit to nickel. I noticed only that the reader is less responsive (maybe the modifies to lines 440 662 and 665 in input.lua???)....

Please return the lines in input.lua to the original state, if the swap from ".." to "," works in line 84 in gesturedetector.lua

Originally Posted by xping

A question: If I comment (adding --) line 84 in gestures.lua, do I get useful log files??

Yes, but you lose some info. If you use the swap you still have the info.
Either you prefix with "--" and the line is turned into a comment and ignored, or you swap and you get the info.
I used that line to compare the touch events in ev.log to the events table processed by the function GestureDetector:feedEvent(tevs). Without the first, the second is near useless. It would only give an insight as to how some events are without x- or y-coordinates.

Originally Posted by xping

I have to say that I use ken maltby mod to koboreader_kobo.sh:...
Is it right????

He has it from a good source, so at least I think it is alright. I pushed the -STOP/-CONT lines to github, so I expect that the next nightly build includes those lines.

Could you upload the working Mini and Aura HD koreader.log's?

[xping]

Originally Posted by Markismus

Please return the lines in input.lua to the original state, if the swap from ".." to "," works in line 84 in gesturedetector.lua


Yes, but you lose some info. If you use the swap you still have the info.
Either you prefix with "--" and the line is turned into a comment and ignored, or you swap and you get the info.
I used that line to compare the touch events in ev.log to the events table processed by the function GestureDetector:feedEvent(tevs). Without the first, the second is near useless. It would only give an insight as to how some events are without x- or y-coordinates.


He has it from a good source, so at least I think it is alright. I pushed the -STOP/-CONT lines to github, so I expect that the next nightly build includes those lines.

Could you upload the working Mini and Aura HD koreader.log's?

Well well well, "," instead of ".." works fine. On my kobo mini I wasn't able to make koreader crash turning pages!!! fine!

Here is "debugfiles.zip" of my kobo mini with conf that allow to use koreader without making it crash. It seems to work with PDF reflow wich is (according to me) the most "delicate" point of the questions. With EPUB till now no problem
The speed is optimal: turning page happens in a moment!

With my aura hd the question is harder. Some attempts with the same changes result in a complete failure. koboreader is too slow and often it crashes exiting to nikel. I will post crash and koreader logs this evening when I will be at home (I haven't my aura HD with me, sorry).

Anyway, just think that "," instead of ".." allowing nil value is the right choice! Goood

[Markismus]

Originally Posted by xping

Here is "debugfiles.zip" of my kobo mini with conf that allow to use koreader without making it crash.

I see that you haven't changed input.lua back to its original state. Good to see that the function Input:handlePhoenixTouchEv also works for Kobo devices, when those lines are uncommented.

I would keep input.lua in its original state and only swap ".." with "," in line 84 of gesturedetector.lua These changes will be in future builds of koreader.

[Ken Maltby]

It "sounds" like you two are getting it straight for two devices (and probably all Mark 4).
My AuraHD doesn't seem to have the issue anymore, although I do still get the occasional koreader.log with an "x" or "y" (a nil value) error.

The code in my devices includes what I have found to work the best for me, and includes all the good advice from many great postings here. Most certainly "Markismus's" advice is included in my koreader_kobo.sh file. I try and remember to give credit when I provide others with "what I am using" or "what works for me", but sometimes there are many and I am not always sure what originated with who.

My current line 84:
DEBUG("tev fed to GestureDetector|",tev.x.."|"..tev.y.."|"..tev.id.. "|"..tev.slot.."|"..tev.timev.sec.."|"..tev.timev. usec)

Are you guys talking about replacing all the ".." with "," ? Or just certain ones, like the trailing or leading ones? Or do you mean to replace the "," in ",tev.x.." with ".." to match the others?

Luck;
Ken

[Markismus]

Originally Posted by Ken Maltby

My current line 84:
DEBUG("tev fed to GestureDetector|",tev.x.."|"..tev.y.."|"..tev.id.. "|"..tev.slot.."|"..tev.timev.sec.."|"..tev.timev. usec)

Are you guys talking about replacing all the ".." with "," ? Or just certain ones, like the trailing or leading ones? Or do you mean to replace the "," in ",tev.x.." with ".." to match the others?

When you're done line 84 in gesturedetector.lua should look like this:

DEBUG("tev fed to GestureDetector|",tev.x,"|",tev.y,"|",tev.id,"|",tev.slot,"|",tev.timev.sec,"|",tev.timev.usec)

See the changes on github here.

[Ken Maltby]

Ok made the changes.
Now it is actually doing it again. Maybe it didn't take, I'll try power off and restart.
Now it is working with no crash to nickel. And the koreader.log has no error listed.

Looks like the changes are working.

Luck;
Ken

[xping]

Originally Posted by Ken Maltby

Ok made the changes.
Now it is actually doing it again. Maybe it didn't take, I'll try power off and restart.
Now it is working with no crash to nickel. And the koreader.log has no error listed.

Looks like the changes are working.

Luck;
Ken

I think that placing "," instead of ".." necessary solves The question of nil value error. But what ' s about The speed of koreader on your aura hd? For me is faster on kobo mini and I can' t explain. Maybe too much infos because of higher resolution? Can't make It work at usable speed...

[giorgio130]

Wouldn't it be simpler to just comment out the line? If it's needed for testing, a developer can easily re-enable it, and for most people it would be useless.

[Markismus]

Originally Posted by giorgio130

Wouldn't it be simpler to just comment out the line? If it's needed for testing, a developer can easily re-enable it, and for most people it would be useless.

Yes, it would. So that was the first solution.

However, it also nice to know whether the DEBUG function has a problem with nil-values. It doesn't.

[Ken Maltby]

Originally Posted by xping

I think that placing "," instead of ".." necessary solves The question of nil value error. But what ' s about The speed of koreader on your aura hd? For me is faster on kobo mini and I can' t explain. Maybe too much infos because of higher resolution? Can't make It work at usable speed...

I don't have a mini to compare to, but my AuraHD seems as quick as ever. How is it slow, what is taking longer than it should? Are we talking seconds?
How many?

Luck;
Ken