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

[tshering]

Originally Posted by Ost

I have tried the 2013-12-21 nightly on a Kobo Touch (N905 in small print at the bottom of the device) with firmware 3.0.1 (644485e229), and touch input is very strange.

From the file launcher, I've managed to stumble on epubs and the top menu by tap-tapping everywhere on the screen, but I haven't managed to turn pages or make sense of the offsets. Maybe I could if I managed to get events printed live with their original/transformed coordinates. The home button (meant to bring back the home screen) is unresponsive and the only way to exit is to power off. Other nightlies (2013-12-01, 2013-11-09) have the same issues.

Maybe this post is helpful. You might have to restart the reader after applying the changes to make them effective.

[Ost]

Originally Posted by tshering

Maybe this post is helpful. You might have to restart the reader after applying the changes to make them effective.

No luck. I'd like to get the home button working, I'm doing an awful lot of rebooting without it.

By the way, where are lua prints going? They don't seem to land when I redirect stdout and stderr in koreader_kobo.sh.

[Markismus]

I have a problem with tapping filenames in filemanager on a Kobo Aura since the latest nightly (build 713). I have to tap slightly lower than usual: just below the line I want to tap.

Does anybody else has this problem, too? Or am I just that confused about tapping?



On a side note: credocuments got dictionary support tonight!! So epub-, mobi-files and 10 others (see lines 279-291 for all extentions supported by coolreader engine) can now be read with word lookup!

Only thing Kobo Nickel now really has on Koreader for epubs is annotations and font tweaking. For mobi I Koreader is already better. I found Kobo's software to generate many errors, while koreader had no problem whatsoever.

[Ken Maltby]

Originally Posted by Markismus

I have a problem with tapping filenames in filemanager on a Kobo Aura since the latest nightly (build 713). I have to tap slightly lower than usual: just below the line I want to tap.

Does anybody else has this problem, too? Or am I just that confused about tapping?
.

I notice a little of that on my AuraHD as well. I also noticed that the blank line(s) between the top listed item and the page title "History" are gone now.

Luck;
Ken

[Ken Maltby]

Originally Posted by Ost

No luck. I'd like to get the home button working, I'm doing an awful lot of rebooting without it.

By the way, where are lua prints going? They don't seem to land when I redirect stdout and stderr in koreader_kobo.sh.

My koreader.log.########## files are in the /koreader directory. Reader call: "./reader.lua /mnt/sd/.Koreader/Books 1> koreader.log.`date +%s` 2>&1"

Luck;
Ken

[xping]

What's about Build 735?

Is the problem of touch wrong offset solved?

Anything new?

thxx

[xping]

My mother has a kobo touch. I installed koreader build 735 this morning and it is afflicted by x-y coordinates inversion problem.

Does someone solved this issue?

Edit: problem solved editing Lines 27-28 in input.lua

[Ken Maltby]

Build 735 has fixed the image rendering. Updating from 713, so it might have been fixed in one of those nightlys between. Thanks, Hawhill. Highlighting on selection and spacing of items in lists has been tweaked, as well.

Luck;
Ken

[Markismus]

Originally Posted by xping

My mother has a kobo touch. I installed koreader build 735 this morning and it is afflicted by x-y coordinates inversion problem.

Does someone solved this issue?

Edit: problem solved editing Lines 27-28 in input.lua

Great!

What would be better is that we would know which model it is, so that we can update the code to work for all future installs.

Could you check which model is reported?
It's dumped to screen if you're running from a terminal. If not you could modify your call to lua line:

# finally call reader
./reader.lua -d /mnt/onboard 1> koreader.log 2>&1

The "-d" flag enables debugging,
"mnt/onboard" is your startup directory,
"1>koreader.log" redirects standard output from screen to "koreader.log",
"2>&1" redirects error output to standard output.

When I run it likes this, the first 9 lines of koreader.log look like:

Auto-detected Kobo
Device model=
Kobo_phoenix
Firmware revision
3.1.1
Screen height =
1024
Screen width =
758

I would like the exact string of Device model or better the koreader.log file and the working input.lua file, so it the code can be modified.

[xping]

[QUOTE=Markismus;2723853]Great!

What would be better is that we would know which model it is, so that we can update the code to work for all future installs.... etc. etc

If I look on the box I read this:

Product no:N905-KBO-B
S/N: N905K342***** -B


Well. Here are results of redirection in koreader.log:

NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
Auto-detected Kobo
Device model=
Kobo_trilogy
Firmware revision
3.0.1
Screen height =
800
Screen width =
600
....

In attachment zip file with all ueseful files.

I have to say that now on kobo touch all seems to work fine. (Dictionaries should work? cause they don't)

Only a word aboud Koreader_kobo.sh. Here is mine:

#!/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"

# stop Nickel
killall -STOP nickel
killall -STOP hindenburg

# finally call reader
./reader.lua -d /mnt/onboard 1> koreader.log 2>&1

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




ABOUT This lines:
...
killall -STOP hindenburg
...
./reader.lua /mnt/onboard 2> crash.log
...
killall -CONT hindenburg


If I had -stop hindenburg before calling reader.lua I feel the device more responsive, or almost I think it is.

What kind of process shoud "Hindenburg" be?

THXX

[Ken Maltby]

"Hindenburg" is Kobo's internet browser, as I understand it, I just Killall it in my koreader_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 and related processes
killall -STOP nickel
killall adobehost
killall dbus-daemon
killall hindenburg


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


# continue with nickel

killall -CONT nickel


And my AuraHD is pretty responsive.

Luck;
Ken

[xping]

Originally Posted by Ken Maltby

"Hindenburg" is Kobo's internet browser, as I understand it, I just Killall it in my koreader_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 and related processes
killall -STOP nickel
killall adobehost
killall dbus-daemon
killall hindenburg


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


# continue with nickel

killall -CONT nickel


And my AuraHD is pretty responsive.

Luck;
Ken

It's a great idea to close all this stuff.... I will try on my aura Hd, wich is "a little" laggy... Thx!

[Markismus]

Originally Posted by xping

Product no:N905-KBO-B
S/N: N905K342***** -B

So I don't know yet how to differentiate between Kobo Touches.

For those with telnet access:
Could people dump their ntx_hwconfig -s -p /dev/mmcblk0 output? Could especially those with a Kobo Touch also give their product and serial numbers?

[Markismus]

@xping
Running the following command on a Kobo Glo gives your error:
[root@(none) ~]# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.3 , size=35 bytes :
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
...

So it has nothing to do with koreader, but it is an warning error from Kobo software.

[Markismus]

Originally Posted by xping

[Dictionaries should work? cause they don't

They work if you install stardict files in koreader/data/dict. For scanned text you can get koreader to OCR the words and feed them to the dictionary. Then you would have to install Tesseract-OCR traineddata-files to koreader/data/tessdata.

For more info see the discussion here.