KOA2 KOReader on KOA2: Possible yet?

[7hir7een]

I copied the example text in the fbink thread since I don't know what I'm doing . That did indeed work just fine

Spoiler:

[root@kindle root]# fbink -c -p -m -y 10 -S 6 "Thanks for fbink NiLuJe"
[FBInk] Variable fb info: 1264x1680, 8bpp @ rotation: 0
[FBInk] Fontsize set to 48x48.
[FBInk] Line length: 26 cols, Page size: 35 rows.
[FBInk] Fixed fb info: smem_len 4587520, line_length 1280
[FBInk] Enabled Kindle Oasis 2 device quirks
[FBInk] Kernel's HZ value appears to be 100
Printing string 'Thanks for fbink NiLuJe' @ column 0, row 10 (inverted: false, flashing: false, centered: true, left padded: true, clear screen: true, font scaling: x6)
[root@kindle root]#

Where should that strace file be placed on the kindle, because /mnt/us/ directory did not appear to be the answer. Should it be replacing the one in the usbnet directory?

[NiLuJe]

@7hir7een: You can basically put it anywhere, as long as you call that one, and not USBNet's.

I usually put those kind of testing things in root's $HOME, since it's a tmpfs, but in this specific case, replacing USBNet's binary is a good idea, since that one is mostly broken on the KOA2 anyway . And then you can just call "strace" since USBNet's one is in your PATH .

EDIT: Just to be perfectly clear: you did get to see that string printed on your screen, right? ^^. That'd be a good news, since KOReader should mostly do the same thing...

EDIT²: Err, of course, you have to unpack the tarball, first . tar xvzf strace-koa2.tar.gz .

[7hir7een]

ssh output attached

Actions taken: (roughly, some button presses had to be repeated because this slowed down the device a lot and it appeared not to be responding)

Spoiler:

Along the top menu:
- "Home"
- "Back" (this opened goodreads but airplane mode was on so... "Cancel" on turn airplane mode on prompt)
- "Settings"
In the drop-down tray:
- "Airplane mode"
- "Bluetooth"
- "Sync my kindle"
- "All settings"
Back on top menu bar:
- "Goodreads"
- "Store"
- "Search"
- Typed "test" and hit enter
- "X" next to search bar to cancel out of results
- "Home"
- "My Library"
- Attempted to change dropdown to "All" instead of "Docs" to change pages in library, but device did not respond
- Hit "All" (vs Downloaded) to display more than one page in library (multiple times, device did not want to respond)
- Attempted to change pages in library by swiping, but no response
- Touched page "1 of 9"
- Typed "2" in page number to go to and hit "Go"
- Attempted to change pages in library via swiping again
- Gave up and hit "Home" again
- Opened a book (took forever)
- Changed pages via tapping (four of them registered, but again device was very slow)
- Opened menu within book at top
- Opened "Aa display" menu
- Tapped to "Page" settings.
- Changed spacing to third option and margins to third option and Xed out of that menu
- Opened menu within book again
- Touched the three dots
- Attempted to open "Notes" but framework finally decided enough was enough and restarted

And yes, the text did print on the screen (screenshot attached)


ETA: If you would like me to take less actions in a specific order, just let me know. I was trying to do a bit of everything haha

[NiLuJe]

@7hir7een: Thanks! That'll give me something to check against, I'll keep you all posted .

[downeaster59]

Thanks @NiLuJe & 7hir7een! I haven't had a chance to get started on USBNet yet.

[NiLuJe]

Okay, I'll be merging the KOReader changes soon, in the meantime, just to check that I did not break anything, could one of you check if the newly released FBInk 0.9.12 still works?

[7hir7een]

It does indeed

[NiLuJe]

Yay, thanks!

I'll give you a shout once an OTA w/ the latest changes pops up .

[NiLuJe]

@7hir7een: In the meantime, I guess I can ask you a few more things to try...

Does

hexdump /dev/input/by-path/platform-gpiokey.0-event

work [it'll 'hang' until you tap some keys if it does] (if it doesn't, is there something remotely looking like it might point to the physical keys in /dev/input/by-path/? [i.e., send me a ls -lash /dev/input/by-path/ & a cat /proc/bus/input/devices ]).

If it works, tap a few times on each physical buttons and send me the output (again, in a specific order so I can figure out which is which ^^).

----

And the final thing: does it still rotate automatically based on its physical orientation?

If yes, does

lipc-get-prop -s com.lab126.winmgr accelerometer

yield something?

And if it does, what about

cat /proc/bus/input/devices | grep -e 'Handlers\\|EV=' | grep -B1 'EV=d'| grep -o 'event[0-9]'

?

With that answered, I should be able to match the KOA1 feature-set .

[7hir7een]

Sure thing

The first bit of code returns a file not found

[root@kindle root]# hexdump /dev/input/by-path/platform-gpiokey.0-event
hexdump: /dev/input/by-path/platform-gpiokey.0-event: No such file or directory

ETA: here's what I got from the corrected path

Spoiler:

[root@kindle root]# hexdump /dev/input/by-path/platform-gpio-keys-event
0000000 ced9 5b38 d24e 0009 0001 0068 0001 0000
0000010 ced9 5b38 d24e 0009 0000 0000 0000 0000
0000020 ced9 5b38 2663 000c 0001 0068 0000 0000
0000030 ced9 5b38 2663 000c 0000 0000 0000 0000

0000040 ceda 5b38 4ee3 0007 0001 006d 0001 0000
0000050 ceda 5b38 4ee3 0007 0000 0000 0000 0000
0000060 ceda 5b38 6ae0 0009 0001 006d 0000 0000
0000070 ceda 5b38 6ae0 0009 0000 0000 0000 0000

0000080 cedb 5b38 9069 000d 0001 0068 0001 0000
0000090 cedb 5b38 9069 000d 0000 0000 0000 0000
00000a0 cedc 5b38 66ba 0000 0001 0068 0000 0000
00000b0 cedc 5b38 66ba 0000 0000 0000 0000 0000

00000c0 cedc 5b38 a981 000a 0001 006d 0001 0000
00000d0 cedc 5b38 a981 000a 0000 0000 0000 0000
00000e0 cedc 5b38 a011 000c 0001 006d 0000 0000
00000f0 cedc 5b38 a011 000c 0000 0000 0000 0000

That's top, bottom, top, bottom (spaces inserted for legibility) -- with the device upright (buttons on right side)

---

Here are the other things you asked for if you still need them:
by-path

Spoiler:

[root@kindle root]# ls -lash /dev/input/by-path/
0 drwxr-xr-x 2 root root 120 Jun 30 23:14 .
0 drwxr-xr-x 3 root root 300 Jun 30 23:14 ..
0 lrwxrwxrwx 1 root root 9 Jun 30 23:14 platform-30370000.snvs:snvs-powerkey-event -> ../event0
0 lrwxrwxrwx 1 root root 9 Jun 30 23:14 platform-30a30000.i2c-event -> ../event6
0 lrwxrwxrwx 1 root root 9 Jun 30 23:14 platform-gpio-keys-event -> ../event5
0 lrwxrwxrwx 1 root root 9 Jun 30 23:14 platform-max77796-key-event -> ../event1

devices

Spoiler:

[root@kindle root]# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0000 Version=0000
N: Name="30370000.snvs:snvs-powerkey"
P: Phys=snvs-pwrkey/input0
S: Sysfs=/devices/platform/soc/30000000.aips-bus/30370000.snvs/30370000.snvs:snvs-powerkey/input/input0
U: Uniq=
H: Handlers=kbd event0 evbug
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="max77796-key"
P: Phys=max77796-key/input0
S: Sysfs=/devices/platform/3c.max77796/max77796-key/input/input1
U: Uniq=
H: Handlers=kbd event1 evbug
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="SX9310 Cap Touch"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=kbd event2 evbug
B: PROP=0
B: EV=3
B: KEY=81c

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="hall_sensor_disp"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 evbug
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="hall_sensor_usb"
P: Phys=
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=event4 evbug
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input5
U: Uniq=
H: Handlers=kbd event5 evbug
B: PROP=0
B: EV=3
B: KEY=2100 0 0 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="cyttsp5_mt"
P: Phys=1-0024/input0
S: Sysfs=/devices/platform/soc/30800000.aips-bus/30a30000.i2c/i2c-1/1-0024/input/input6
U: Uniq=
H: Handlers=event6 evbug
B: PROP=2
B: EV=f
B: KEY=6420 0 0 0 0 0 0 0 0 0 0
B: REL=0
B: ABS=6608000 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="max44009_als"
P: Phys=
S: Sysfs=/devices/virtual/input/input7
U: Uniq=
H: Handlers=event7 evbug
B: PROP=0
B: EV=9
B: ABS=100 0

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="max44009_als1"
P: Phys=
S: Sysfs=/devices/virtual/input/input8
U: Uniq=
H: Handlers=event8 evbug
B: PROP=0
B: EV=9
B: ABS=100 0

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="bma2x2"
P: Phys=
S: Sysfs=/devices/virtual/input/input9
U: Uniq=
H: Handlers=event9 evbug
B: PROP=0
B: EV=9
B: ABS=100 7

I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="bma_interrupt"
P: Phys=
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=event10 evbug
B: PROP=0
B: EV=d
B: REL=3c6
B: ABS=3000000

---

Yes, the KOA2 retains the accelerometer. Switching between upright (buttons on right side) and reversed (buttons on left side):

Spoiler:

[root@kindle root]# lipc-get-prop -s com.lab126.winmgr accelerometer
U
[root@kindle root]# lipc-get-prop -s com.lab126.winmgr accelerometer
D

But that second bit

Spoiler:

[root@kindle root]# cat /proc/bus/input/devices | grep -e 'Handlers\\|EV=' | gre
p -B1 'EV=d'| grep -o 'event[0-9]'
[root@kindle root]#

[NiLuJe]

@7hir7een: Thanks, that was massively helpful . I should be able to get the physical buttons working, as well as the orientaiton support with all this .

And the final command failing can be explained by the fact that there's >9 input devices, but I should be able to figure it out thanks to the manual cat I asked you for, so all's good .

EDIT: Also, Lua escaping, ooops.

[NiLuJe]

@7hir7een: Hmm, quick question, what's the default mapping for the top button? Backward or Forward?

(I'm looking at a K4 and it was Backward, but looking at the KOA code and what you've logged, it looks like Forward, unless they inverted the keycode between the KOA and the KOA2...)

EDIT: Looked at the KOA2 user's guide, it's indeed in the reverse order than on a K2/K3/K4, so, all's good . (i.e., top is forward).

[NiLuJe]

OTA 1753 is out and features the result of this latest batch of changes .

[7hir7een]

No go, unfortunately. I can't really see anything different in the crash log, but it's freezing on a blank screen as before when attempting to start the filemanager.

Is there some way to get more in-depth feedback from terminal, maybe?

[NiLuJe]

@7hir7een:

Hmm. You can try debug mode, see if something better pops up in the logs that way...

In koreader/koreader.sh, switch ./reader.lua to ./reader.lua -d (c.f., https://github.com/koreader/koreader...reader.sh#L236) (with a decent text/code editor that won't mangle *nix line endings).

And on the off-chance I messed that up, does the path /sys/class/backlight/max77796-bl/brightness actually point to something?

EDIT: As for terminal output, I guess our best friend strace might be of help again...

strace -fitv -p $(pidof reader.lua | sed -e 's/ / -p /g')

This might be extremely verbose (or not), depending on what's causing the trouble...