Quote:
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????