Koreader on H2O Edition 2 (H2O2)

[gilali]

Hello,

Is there a thread to follow Koreader developpement for this specific device ?
I can not open a bugtracking because it's not really a bug. It's only a device NOT supported yet...

My way is to install the latest nightly update, every 2-3 days, and try to run the app since are working KSM08 and pbchess. But after few iterations it's boring...

I am OK to test new updates on my device if someone need, as a beta tester.

Thank you all

EDIT :
KOREADER IS NOW SUPPORTED ON H2O2
You need to apply this
And for Natural Light, apply this

[Frenzie]

Other than https://github.com/koreader/koreader/pull/3372 which I added just so it would hopefully display something, there isn't any development without people like you who have the device.

A big one to try might be this one.

touch_alyssum_protocol = true,

That's in frontend/device/kobo/device.lua as part of the KoboSnow (H2O2) definition.

[gilali]

Thank you

Here my test on v2015.11-1401-g5faddfd/ 07-Nov-2017 06:40

added "touch_alyssum_protocol = true," like this :

-- Kobo Aura H2O2:
local KoboSnow = Kobo:new{
    model = "Kobo_snow",
    hasFrontlight = yes,
    touch_phoenix_protocol = true,
    touch_alyssum_protocol = true,
    display_dpi = 265,
    -- the bezel covers the top 11 pixels:
    viewport = Geom:new{x=0, y=11, w=1080, h=1429},
}

RESULT :

• Displaying the KOREADER File Browser /mnt/onboard
• No touch response
• Frontlight is on
• I had to reboot

Same results either on KSM or Nickel but on KSM :

• Frontlight setting looks different
• Screen upside down

Next ?

[Frenzie]

Ideally you should check if the program outputs any useful debugging info. The easiest but more labor-intensive way would be to add -d to the KSM KOReader command. Either in the KSM script or here:

https://github.com/koreader/koreader...reader.sh#L124

./reader.lua -d "${args}" >>crash.log 2>&1

Then the crash.log will contain the full debugging output. (You could rename it debug.log if you prefer. :P)

The ultimately easier way is to use something like USBNet or SSH so you can easily change configurations and tail the debug output in your console, and of course kill KOReader so you don't have to reboot.

Regarding the screen orientation, I should've mentioned that it's very important not to assume that the touch orientation and display orientation are the same. It could even be mirrored. So basically just try some taps all around the screen, probably starting with top center and bottom center.

As far as what next, I can't really help you there. From what I've seen I don't think it should be necessary to write any new implementation, but some combination of already existing stuff should do: https://github.com/Frenzie/koreader/...e.lua#L20-L134

We know the DPI, we know it has a frontlight and the viewport is probably the same as on the H2O (not terribly important just for getting it to work) but other than that all bets are off. :P

Note that on most Kobos you can play around with the visual rotation like this (in koreader.sh prior to ./reader.lua):

CUR_ROTATE="$(cat "/sys/class/graphics/fb0/rotate")"
# this suffices on normal devices, but H2O is stupid and sets the opposite
echo "${CUR_ROTATE}" >"/sys/class/graphics/fb0/rotate"
# this therefore turns it around on H2O (and other potential idiots) and merely
# innocently repeats on sane devices
# shellcheck disable=SC2094
cat "/sys/class/graphics/fb0/rotate" >"/sys/class/graphics/fb0/rotate"

You can also reset it (and/or mess it up) using

/usr/sbin/fbset -depth 32

In principle I don't think the display should turn around compared to KSM unless KSM still does /usr/sbin/fbset -depth 16 somewhere (a workaround for older versions of KOReader since Kobo used to be 16 bit).

[Jipyan]

I've been trying to get Koreader on my H2O2 too.
I'll briefly explain what I've done so far.

1.
- Installed KSM08
- KSM was upside down and touch did not work
- a patch fixed the problems with KSM (https://www.mobileread.com/forums/sh...&postcount=805)

2.
- Installed most recent Koreader (nightly 20171023) using the recommended method
- Loaded Koreader using KSM, but Koreader was upside down and no touch response.
- Koreader versions before nightly 20171023 do not work (no response/reboots)

3.
- Uninstalled everything from 1 and 2
- Installed Koreader using the alternative method (through Kobo File Manager)
- Koreader starts in the correct orientation, but no touch.

4.
- I found the current thread and added the code to the KoboSnow definition.
- Koreader loads but still no touch.
- After removing the other touch_(...)_protocol, Koreader does not start (device reboots).

5.
- Removed Kobo FileManager
- Installed KSM08 with H2O2 patch and Koreader again.
- Added the code to the KoboSnow definition, but still no touch.

Orientation notes:
Koreader orientation is fine when starting through FileManager.
KSM08 is upside down at first. After the H2O2 patch KSM08 is OK, but then Koreader is upside down.
I did not test Koreader's orientation without the H2O2 patch. (I could not start it without touch)

Touch notes:
The H2O2 patch fixed touch in KSM08, maybe that's something to check out for Koreader coders?

If there is anything else I could check, please let me know

[Jipyan]

I made a debug log.

-Started Koreader.
-Touched the screen a lot.
- Put it to sleep
- Woke it up
- Touched the screen
- Switched it off

Upon first inspection it seems the touches are registered.

[tshering]

Originally Posted by Jipyan

Orientation notes:
Koreader orientation is fine when starting through FileManager.
KSM08 is upside down at first. After the H2O2 patch KSM08 is OK, but then Koreader is upside down.
I did not test Koreader's orientation without the H2O2 patch. (I could not start it without touch)

You could try inserting into koreader.sh

# somewhere at the beginning, does not matter where exactly
echo 0 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

and

#before "exit $RETURN_VALUE"
echo 2 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

If this code works it should go into the KSM script that calls koreader.sh, but for testing purposes it is easier to insert the script directly into the koreader code.

[Frenzie]

Originally Posted by Jipyan

I made a debug log.

-Started Koreader.
-Touched the screen a lot.
- Put it to sleep
- Woke it up
- Touched the screen
- Switched it off

Upon first inspection it seems the touches are registered.

What are the precise conditions of those logs? I imagine you didn't tap quite that quickly? Normally a tap would look something like this:

11/08/17-12:37:43 DEBUG input event => type: 3, code: 57(nil), value: 0, time: 1510141063.446016
11/08/17-12:37:43 DEBUG input event => type: 3, code: 53(nil), value: 202, time: 1510141063.446022
11/08/17-12:37:43 DEBUG input event => type: 3, code: 54(nil), value: 403, time: 1510141063.446024
11/08/17-12:37:43 DEBUG input event => type: 0, code: 0(nil), value: 0, time: 1510141063.446025
11/08/17-12:37:43 DEBUG in tap state...
11/08/17-12:37:43 DEBUG set up hold timer
11/08/17-12:37:43 DEBUG AutoSuspend: onInputEvent
11/08/17-12:37:43 DEBUG input event => type: 3, code: 57(nil), value: -1, time: 1510141063.539426
11/08/17-12:37:43 DEBUG input event => type: 0, code: 0(nil), value: 0, time: 1510141063.539428
11/08/17-12:37:43 DEBUG in tap state...
11/08/17-12:37:43 DEBUG set up tap timer
11/08/17-12:37:43 DEBUG in tap timer true
11/08/17-12:37:43 DEBUG single tap detected in slot 0 {
    ["y"] = 403,
    ["x"] = 202,
    ["h"] = 0,
    ["w"] = 0
}

There are three primary things I'd try first if I had the device myself (besides evtest).

Nothing:

local KoboSnow = Kobo:new{
    model = "Kobo_snow",
    hasFrontlight = yes,
    display_dpi = 265,
    -- the bezel covers the top 11 pixels:
    viewport = Geom:new{x=0, y=11, w=1080, h=1429},
}

touch_phoenix_protocol = true (like my own H2O from 2014)

local KoboSnow = Kobo:new{
    model = "Kobo_snow",
    hasFrontlight = yes,
    touch_phoenix_protocol = true,
    display_dpi = 265,
    -- the bezel covers the top 11 pixels:
    viewport = Geom:new{x=0, y=11, w=1080, h=1429},
}

touch_alyssum_protocol = true (it has been featured on at least one 2016 model)

local KoboSnow = Kobo:new{
    model = "Kobo_snow",
    hasFrontlight = yes,
    touch_alyssum_protocol = true,
    display_dpi = 265,
    -- the bezel covers the top 11 pixels:
    viewport = Geom:new{x=0, y=11, w=1080, h=1429},
}

[gilali]

Context:
Koreader from KSM

Result:
alyssum selected : KO
phoenix selected : KO
nothing selected: OK, i can put only a single touch with a response. And after, no any response.

little good news

My 3 logs in attach.

The ultimately easier way is to use something like USBNet or SSH so you can easily change configurations and tail the debug output in your console, and of course kill KOReader so you don't have to reboot.

On KSM, I've activated WIFI, an I was able to ping the device. But NO SSH access. Either by USBNet or by adding this code in [general] section :

useDropbear=true

.
So, I had to use the classic method to obtain logs.

[gilali]

Pbchess that works perfectly displays 305 dpi on the same device, as the screenshot :



Is there a way to make a mistake on the screen resolution, as big as the official Kobo website that displays 265 dpi ???

[gilali]

https://www.sven.de/dpi/ count 265 dpi too.
It seems to be the right value

[gilali]

Starting through KSM, KOReader screen stays upside down despite the patch

# somewhere at the beginning, does not matter where exactly
echo 0 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

#before "exit $RETURN_VALUE"
echo 2 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

[Frenzie]

Originally Posted by gilali

Context:
Koreader from KSM

Result:
alyssum selected : KO
phoenix selected : KO
nothing selected: OK, i can put only a single touch with a response. And after, no any response.

little good news

My 3 logs in attach.

Did you also try both at once? The behavior I see with none (mistaken hold gesture) is typically fixed by the Phoenix protocol. It's a reverse-engineered custom multitouch protocol used by multiple Kobo devices: https://github.com/koreader/koreader...input.lua#L427

(I have no idea why they don't just use the standard. Hopefully they didn't update it in some way.)

[Frenzie]

Originally Posted by gilali

Starting through KSM, KOReader screen stays upside down despite the patch

# somewhere at the beginning, does not matter where exactly
echo 0 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

#before "exit $RETURN_VALUE"
echo 2 > /sys/class/graphics/fb0/rotate
cat /sys/class/graphics/fb0/rotate > /sys/class/graphics/fb0/rotate

You might also want to try the reverse.

[tshering]

Originally Posted by Frenzie

You might also want to try the reverse.

You are right. I got confused. It is the exactly the other way round.