Bluetooth page turning for Kobo eReaders

[kobol2]

I think BT devices emulating a mouse, keyboard will have eventX.
But if it emulates multimedia keys, then it won't have eventX

[KissMeKiwi]

I am using a random bluetooth adapter i found on amazon. I got evtest running on my raspberry pi to check values, but I am unable to get this work.

I just am confused a little bit because when pressing one button, I get a ton of info from evtest.

For example, this is everything I got from pressing the right button:

Event: time 1685400399.224799, type 2 (EV_REL), code 0 (REL_X), value 2047
Event: time 1685400399.224799, type 2 (EV_REL), code 1 (REL_Y), value -2047
Event: time 1685400399.224799, -------------- SYN_REPORT ------------
Event: time 1685400399.254743, type 2 (EV_REL), code 0 (REL_X), value -40
Event: time 1685400399.254743, type 2 (EV_REL), code 1 (REL_Y), value 80
Event: time 1685400399.254743, -------------- SYN_REPORT ------------
Event: time 1685400399.284739, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1685400399.284739, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1685400399.284739, -------------- SYN_REPORT ------------
Event: time 1685400399.314727, type 2 (EV_REL), code 0 (REL_X), value -40
Event: time 1685400399.314727, -------------- SYN_REPORT ------------
Event: time 1685400399.344737, type 2 (EV_REL), code 0 (REL_X), value -40
Event: time 1685400399.344737, -------------- SYN_REPORT ------------
Event: time 1685400399.374727, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1685400399.374727, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1685400399.374727, -------------- SYN_REPORT ------------
Event: time 1685400399.404742, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1685400399.404742, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1685400399.404742, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1685400399.404742, type 3 (EV_ABS), code 0 (ABS_X), value 3328
Event: time 1685400399.404742, -------------- SYN_REPORT ------------
Event: time 1685400399.434724, type 3 (EV_ABS), code 0 (ABS_X), value 3400
Event: time 1685400399.434724, -------------- SYN_REPORT ------------
Event: time 1685400399.464726, type 3 (EV_ABS), code 0 (ABS_X), value 3100
Event: time 1685400399.464726, -------------- SYN_REPORT ------------
Event: time 1685400399.494727, type 3 (EV_ABS), code 0 (ABS_X), value 2800
Event: time 1685400399.494727, -------------- SYN_REPORT ------------
Event: time 1685400399.524717, type 3 (EV_ABS), code 0 (ABS_X), value 2500
Event: time 1685400399.524717, -------------- SYN_REPORT ------------
Event: time 1685400399.554728, type 3 (EV_ABS), code 0 (ABS_X), value 2200
Event: time 1685400399.554728, -------------- SYN_REPORT ------------
Event: time 1685400399.584746, type 3 (EV_ABS), code 0 (ABS_X), value 1900
Event: time 1685400399.584746, -------------- SYN_REPORT ------------
Event: time 1685400399.614727, type 3 (EV_ABS), code 0 (ABS_X), value 1600
Event: time 1685400399.614727, -------------- SYN_REPORT ------------
Event: time 1685400399.644738, type 3 (EV_ABS), code 0 (ABS_X), value 1300
Event: time 1685400399.644738, -------------- SYN_REPORT ------------
Event: time 1685400399.674729, type 3 (EV_ABS), code 0 (ABS_X), value 1000
Event: time 1685400399.674729, -------------- SYN_REPORT ------------
Event: time 1685400399.704723, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1685400399.704723, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1685400399.704723, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1685400399.704723, -------------- SYN_REPORT ------------
Event: time 1685400399.704739, type 3 (EV_ABS), code 0 (ABS_X), value 700
Event: time 1685400399.704739, -------------- SYN_REPORT ------------

Which should I use?

[NiLuJe]

EV_KEY:BTN_LEFT seems like the best bet, but that thing's a mess.

(Unless there's supposed to be a gyro or a stick or something in there?).

[KissMeKiwi]

Originally Posted by NiLuJe

EV_KEY:BTN_LEFT seems like the best bet, but that thing's a mess.

(Unless there's supposed to be a gyro or a stick or something in there?).

Okay wanted to make sure I wasn't crazy! Will try to buy a better one.



this is what is was. Hopefully better luck with the next one. Should evtest be usually 1 input to 1 line?

[Jaunx]

Some bluetooth devices require installation of a kernel module:

https://www.mobileread.com/forums/sh...d.php?t=352280

[NiLuJe]

Originally Posted by KissMeKiwi

Should evtest be usually 1 input to 1 line?

For a key/button? nearly. Basically a press and a release.

e.g., a keyboard:

Event: time 1685556515.095613, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70029
Event: time 1685556515.095613, type 1 (EV_KEY), code 1 (KEY_ESC), value 1
Event: time 1685556515.095613, -------------- SYN_REPORT ------------
Event: time 1685556515.214620, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70029
Event: time 1685556515.214620, type 1 (EV_KEY), code 1 (KEY_ESC), value 0
Event: time 1685556515.214620, -------------- SYN_REPORT ------------

[Lola5711]

Originally Posted by tsowell

Hi everyone,

I've written a little plugin (using the wonderful NickelHook) for Kobo eReaders that allows the use of arbitrary Bluetooth devices for turning pages. I've been using it with a Kobo Libra 2 and an 8BitDo Zero 2 controller, but I think it should work with other Bluetooth-capable Kobo eReaders, and you can configure which Bluetooth input events trigger page turning.

Device configuration is unfortunately quite manual. You need to find the Linux input events you want to use as triggers and put them in a configuration file, but that at least only needs to be done once per device.

The code is here: https://github.com/tsowell/kobo-btpt

Installation and usage instructions are in the README, and you can grab a pre-built KoboRoot.tgz from the releases page: https://github.com/tsowell/kobo-btpt/releases

If anyone gets a chance to try it out, let me know how it goes. PRs are also welcome.

--
Tom

Im itrying to follow your guide. But to be honnest im totally new in how this works. Can you or someone else tell the read.me more detailed? I'm stuck at the part "Add
configuration files for your Bluetooth devices there" i dont know which files these are and where to find them.

[Mnementh]

Originally Posted by Lola5711

Im itrying to follow your guide. But to be honnest im totally new in how this works. Can you or someone else tell the read.me more detailed? I'm stuck at the part "Add
configuration files for your Bluetooth devices there" i dont know which files these are and where to find them.

Device configuration is unfortunately quite manual. You need to find the Linux input events you want to use as triggers and put them in a configuration file, but that at least only needs to be done once per device.


This is the relevant section, you need to create the file yourself using the information in the original post and dotted through this thread.

[Renate]

I own, but don't use Kobo, and stumbled upon this thread.
I'm a big fan of BT clickers and always use one with my Onyx Poke3.

But I don't get. Can't you get this all to work with just a keylayout file?
I use both USB HID over BT Usage Pages 0x07 (keyboard) and 0x0c (consumer).

[WalkingSilentz]

Originally Posted by shiplap

I'm trying to get the same remote working. When I telnet into the device and try to run evtest to figure out what inputs to use, it tells me evtest is not present.

Can't find my logs either, I hit the save to file option in Nickelmenu but can't find any files on the device.

Figured I'd try all the keys I could think of that might match, but still not triggering anything:

I'm a third person trying to get this product working for this use! Works fine on the devices they officially support of course so getting it to work with my Libra 2 would simply be a bonus.

When connected to a phone, the buttons seem to emulate mouse/touches that either swipe from the top down, tap in the middle, or swipe from the bottom up. I've got access to evtest thanks to NiLuJe. Whilst the "D01" BT device is connected I don't seem to be able to get anything from it using evtest (but I get outputs if I use evtest on my Arch Linux device).

If I try 'logread -f' with the D01 ring connected it just shows a lot of "void BluetoothManager:bjectManagerInterfacesRemoved" and then the same but with "Added" instead of removed.

Any other ideas? I have the same EV_KEYS entries as Shiplap, so tried their config also. Just to confirm, I also have the config for btpt in the .btpt folder, and it's simply named "D01" (definitely a 0, not O) with no extensions on the filename.

Would be amazing to get this working! Getting cold in town and I don't want to turn pages with an exposed hand.

[jospalau]

Originally Posted by WalkingSilentz

I'm a third person trying to get this product working for this use! Works fine on the devices they officially support of course so getting it to work with my Libra 2 would simply be a bonus.



When connected to a phone, the buttons seem to emulate mouse/touches that either swipe from the top down, tap in the middle, or swipe from the bottom up. I've got access to evtest thanks to NiLuJe. Whilst the "D01" BT device is connected I don't seem to be able to get anything from it using evtest (but I get outputs if I use evtest on my Arch Linux device).



If I try 'logread -f' with the D01 ring connected it just shows a lot of "void BluetoothManager:bjectManagerInterfacesRemoved" and then the same but with "Added" instead of removed.



Any other ideas? I have the same EV_KEYS entries as Shiplap, so tried their config also. Just to confirm, I also have the config for btpt in the .btpt folder, and it's simply named "D01" (definitely a 0, not O) with no extensions on the filename.



Would be amazing to get this working! Getting cold in town and I don't want to turn pages with an exposed hand.

Take a look to this:
https://github.com/Tangent128/lua-evdev

You can cross-compile the module so it can run in Kobo.

Sent from my 22081212UG using Tapatalk

[NiLuJe]

Originally Posted by jospalau

You can cross-compile the module so it can run in Kobo.

Or you can simply use standard API calls via FFI with LuaJIT .

(I would link to KOReader, but input is one of the very earliest thing that was written, so most of it is not actually handled via FFI, but as a Lua C module).

[jospalau]

Originally Posted by NiLuJe

Or you can simply use standard API calls via FFI with LuaJIT .



(I would link to KOReader, but input is one of the very earliest thing that was written, so most of it is not actually handled via FFI, but as a Lua C module).

That's awesome!

Sent from my 22081212UG using Tapatalk

[Henk2001]

Hello everyone,

Has anyone figured out the solution for finding the best event codes? I bought this bluetooth button: https://nl.aliexpress.com/item/10050...yAdapt=glo2nld it's called the JX-03. And these are the results of the evtest tool:

On connection

Select the device event number [0-21]: 21
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x5ac product 0x22c version 0x11b
Input device name: "JX-03"
Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
Event code 114 (KEY_VOLUMEDOWN)
Event code 115 (KEY_VOLUMEUP)
Event code 320 (BTN_TOOL_PEN)
Event code 330 (BTN_TOUCH)
Event code 374 (KEY_KEYBOARD)
Event type 3 (EV_ABS)
Event code 0 (ABS_X)
Value 0
Min 0
Max 4095
Event code 1 (ABS_Y)
Value 0
Min 0
Max 4095
Event code 40 (ABS_MISC)
Value 0
Min 0
Max 1
Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Property type 1 (INPUT_PROP_DIRECT)
Testing ... (interrupt to exit)

##Upper button:##

Event: time 1694963254.779283, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963254.779283, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963254.779283, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963254.779283, type 3 (EV_ABS), code 40 (ABS_MISC), value 1
Event: time 1694963254.779283, type 3 (EV_ABS), code 0 (ABS_X), value 1904
Event: time 1694963254.779283, type 3 (EV_ABS), code 1 (ABS_Y), value 1300
Event: time 1694963254.779283, -------------- SYN_REPORT ------------
Event: time 1694963254.816806, type 3 (EV_ABS), code 1 (ABS_Y), value 1400
Event: time 1694963254.816806, -------------- SYN_REPORT ------------
Event: time 1694963254.839495, type 3 (EV_ABS), code 1 (ABS_Y), value 1700
Event: time 1694963254.839495, -------------- SYN_REPORT ------------
Event: time 1694963254.876831, type 3 (EV_ABS), code 1 (ABS_Y), value 2000
Event: time 1694963254.876831, -------------- SYN_REPORT ------------
Event: time 1694963254.899267, type 3 (EV_ABS), code 1 (ABS_Y), value 2300
Event: time 1694963254.899267, -------------- SYN_REPORT ------------
Event: time 1694963254.929305, type 3 (EV_ABS), code 0 (ABS_X), value 1898
Event: time 1694963254.929305, type 3 (EV_ABS), code 1 (ABS_Y), value 2500
Event: time 1694963254.929305, -------------- SYN_REPORT ------------
Event: time 1694963254.959393, type 3 (EV_ABS), code 0 (ABS_X), value 1895
Event: time 1694963254.959393, type 3 (EV_ABS), code 1 (ABS_Y), value 2600
Event: time 1694963254.959393, -------------- SYN_REPORT ------------
Event: time 1694963254.989289, type 3 (EV_ABS), code 0 (ABS_X), value 1890
Event: time 1694963254.989289, type 3 (EV_ABS), code 1 (ABS_Y), value 2900
Event: time 1694963254.989289, -------------- SYN_REPORT ------------
Event: time 1694963255.019247, type 3 (EV_ABS), code 0 (ABS_X), value 1888
Event: time 1694963255.019247, type 3 (EV_ABS), code 1 (ABS_Y), value 3200
Event: time 1694963255.019247, -------------- SYN_REPORT ------------
Event: time 1694963255.049282, type 3 (EV_ABS), code 0 (ABS_X), value 1882
Event: time 1694963255.049282, type 3 (EV_ABS), code 1 (ABS_Y), value 3500
Event: time 1694963255.049282, -------------- SYN_REPORT ------------
Event: time 1694963255.079261, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963255.079261, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963255.079261, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963255.079261, type 3 (EV_ABS), code 0 (ABS_X), value 1877
Event: time 1694963255.079261, type 3 (EV_ABS), code 1 (ABS_Y), value 3800
Event: time 1694963255.079261, -------------- SYN_REPORT ------------

##Middle button:##

Event: time 1694963328.490195, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963328.490195, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963328.490195, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963328.490195, type 3 (EV_ABS), code 0 (ABS_X), value 1904
Event: time 1694963328.490195, type 3 (EV_ABS), code 1 (ABS_Y), value 1904
Event: time 1694963328.490195, -------------- SYN_REPORT ------------
Event: time 1694963328.512640, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963328.512640, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963328.512640, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963328.512640, -------------- SYN_REPORT ------------

##Lowest button##

Event: time 1694963354.492886, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963354.492886, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963354.492886, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963354.492886, type 3 (EV_ABS), code 1 (ABS_Y), value 2500
Event: time 1694963354.492886, -------------- SYN_REPORT ------------
Event: time 1694963354.522860, type 3 (EV_ABS), code 1 (ABS_Y), value 2400
Event: time 1694963354.522860, -------------- SYN_REPORT ------------
Event: time 1694963354.552828, type 3 (EV_ABS), code 1 (ABS_Y), value 2300
Event: time 1694963354.552828, -------------- SYN_REPORT ------------
Event: time 1694963354.582821, type 3 (EV_ABS), code 1 (ABS_Y), value 2000
Event: time 1694963354.582821, -------------- SYN_REPORT ------------
Event: time 1694963354.612829, type 3 (EV_ABS), code 1 (ABS_Y), value 1800
Event: time 1694963354.612829, -------------- SYN_REPORT ------------
Event: time 1694963354.642890, type 3 (EV_ABS), code 1 (ABS_Y), value 1700
Event: time 1694963354.642890, -------------- SYN_REPORT ------------
Event: time 1694963354.672903, type 3 (EV_ABS), code 1 (ABS_Y), value 1500
Event: time 1694963354.672903, -------------- SYN_REPORT ------------
Event: time 1694963354.702943, type 3 (EV_ABS), code 1 (ABS_Y), value 1400
Event: time 1694963354.702943, -------------- SYN_REPORT ------------
Event: time 1694963354.732888, type 3 (EV_ABS), code 1 (ABS_Y), value 1100
Event: time 1694963354.732888, -------------- SYN_REPORT ------------
Event: time 1694963354.762883, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1694963354.762883, -------------- SYN_REPORT ------------
Event: time 1694963354.792933, type 3 (EV_ABS), code 1 (ABS_Y), value 500
Event: time 1694963354.792933, -------------- SYN_REPORT ------------
Event: time 1694963354.822941, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963354.822941, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963354.822941, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963354.822941, type 3 (EV_ABS), code 1 (ABS_Y), value 200
Event: time 1694963354.822941, -------------- SYN_REPORT ------------

##Double click middle button:##

Event: time 1694963426.988613, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963426.988613, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963426.988613, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963426.988613, type 3 (EV_ABS), code 1 (ABS_Y), value 1904
Event: time 1694963426.988613, -------------- SYN_REPORT ------------
Event: time 1694963427.018593, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.018593, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963427.018593, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963427.018593, -------------- SYN_REPORT ------------
Event: time 1694963427.101061, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.101061, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963427.101061, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963427.101061, -------------- SYN_REPORT ------------
Event: time 1694963427.131005, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.131005, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963427.131005, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963427.131005, -------------- SYN_REPORT ------------


Thankyou!!!!

[tylpk]

Originally Posted by Henk2001

##Upper button:##

Event: time 1694963254.779283, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963254.779283, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963254.779283, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963254.779283, type 3 (EV_ABS), code 40 (ABS_MISC), value 1
Event: time 1694963254.779283, type 3 (EV_ABS), code 0 (ABS_X), value 1904
Event: time 1694963254.779283, type 3 (EV_ABS), code 1 (ABS_Y), value 1300
Event: time 1694963254.779283, -------------- SYN_REPORT ------------
Event: time 1694963254.816806, type 3 (EV_ABS), code 1 (ABS_Y), value 1400
Event: time 1694963254.816806, -------------- SYN_REPORT ------------
Event: time 1694963254.839495, type 3 (EV_ABS), code 1 (ABS_Y), value 1700
Event: time 1694963254.839495, -------------- SYN_REPORT ------------
Event: time 1694963254.876831, type 3 (EV_ABS), code 1 (ABS_Y), value 2000
Event: time 1694963254.876831, -------------- SYN_REPORT ------------
Event: time 1694963254.899267, type 3 (EV_ABS), code 1 (ABS_Y), value 2300
Event: time 1694963254.899267, -------------- SYN_REPORT ------------
Event: time 1694963254.929305, type 3 (EV_ABS), code 0 (ABS_X), value 1898
Event: time 1694963254.929305, type 3 (EV_ABS), code 1 (ABS_Y), value 2500
Event: time 1694963254.929305, -------------- SYN_REPORT ------------
Event: time 1694963254.959393, type 3 (EV_ABS), code 0 (ABS_X), value 1895
Event: time 1694963254.959393, type 3 (EV_ABS), code 1 (ABS_Y), value 2600
Event: time 1694963254.959393, -------------- SYN_REPORT ------------
Event: time 1694963254.989289, type 3 (EV_ABS), code 0 (ABS_X), value 1890
Event: time 1694963254.989289, type 3 (EV_ABS), code 1 (ABS_Y), value 2900
Event: time 1694963254.989289, -------------- SYN_REPORT ------------
Event: time 1694963255.019247, type 3 (EV_ABS), code 0 (ABS_X), value 1888
Event: time 1694963255.019247, type 3 (EV_ABS), code 1 (ABS_Y), value 3200
Event: time 1694963255.019247, -------------- SYN_REPORT ------------
Event: time 1694963255.049282, type 3 (EV_ABS), code 0 (ABS_X), value 1882
Event: time 1694963255.049282, type 3 (EV_ABS), code 1 (ABS_Y), value 3500
Event: time 1694963255.049282, -------------- SYN_REPORT ------------
Event: time 1694963255.079261, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963255.079261, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963255.079261, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963255.079261, type 3 (EV_ABS), code 0 (ABS_X), value 1877
Event: time 1694963255.079261, type 3 (EV_ABS), code 1 (ABS_Y), value 3800
Event: time 1694963255.079261, -------------- SYN_REPORT ------------

##Middle button:##

Event: time 1694963328.490195, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963328.490195, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963328.490195, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963328.490195, type 3 (EV_ABS), code 0 (ABS_X), value 1904
Event: time 1694963328.490195, type 3 (EV_ABS), code 1 (ABS_Y), value 1904
Event: time 1694963328.490195, -------------- SYN_REPORT ------------
Event: time 1694963328.512640, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963328.512640, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963328.512640, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963328.512640, -------------- SYN_REPORT ------------

##Lowest button##

Event: time 1694963354.492886, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963354.492886, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963354.492886, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963354.492886, type 3 (EV_ABS), code 1 (ABS_Y), value 2500
Event: time 1694963354.492886, -------------- SYN_REPORT ------------
Event: time 1694963354.522860, type 3 (EV_ABS), code 1 (ABS_Y), value 2400
Event: time 1694963354.522860, -------------- SYN_REPORT ------------
Event: time 1694963354.552828, type 3 (EV_ABS), code 1 (ABS_Y), value 2300
Event: time 1694963354.552828, -------------- SYN_REPORT ------------
Event: time 1694963354.582821, type 3 (EV_ABS), code 1 (ABS_Y), value 2000
Event: time 1694963354.582821, -------------- SYN_REPORT ------------
Event: time 1694963354.612829, type 3 (EV_ABS), code 1 (ABS_Y), value 1800
Event: time 1694963354.612829, -------------- SYN_REPORT ------------
Event: time 1694963354.642890, type 3 (EV_ABS), code 1 (ABS_Y), value 1700
Event: time 1694963354.642890, -------------- SYN_REPORT ------------
Event: time 1694963354.672903, type 3 (EV_ABS), code 1 (ABS_Y), value 1500
Event: time 1694963354.672903, -------------- SYN_REPORT ------------
Event: time 1694963354.702943, type 3 (EV_ABS), code 1 (ABS_Y), value 1400
Event: time 1694963354.702943, -------------- SYN_REPORT ------------
Event: time 1694963354.732888, type 3 (EV_ABS), code 1 (ABS_Y), value 1100
Event: time 1694963354.732888, -------------- SYN_REPORT ------------
Event: time 1694963354.762883, type 3 (EV_ABS), code 1 (ABS_Y), value 800
Event: time 1694963354.762883, -------------- SYN_REPORT ------------
Event: time 1694963354.792933, type 3 (EV_ABS), code 1 (ABS_Y), value 500
Event: time 1694963354.792933, -------------- SYN_REPORT ------------
Event: time 1694963354.822941, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963354.822941, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963354.822941, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963354.822941, type 3 (EV_ABS), code 1 (ABS_Y), value 200
Event: time 1694963354.822941, -------------- SYN_REPORT ------------

##Double click middle button:##

Event: time 1694963426.988613, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963426.988613, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963426.988613, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963426.988613, type 3 (EV_ABS), code 1 (ABS_Y), value 1904
Event: time 1694963426.988613, -------------- SYN_REPORT ------------
Event: time 1694963427.018593, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.018593, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963427.018593, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963427.018593, -------------- SYN_REPORT ------------
Event: time 1694963427.101061, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.101061, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1
Event: time 1694963427.101061, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1
Event: time 1694963427.101061, -------------- SYN_REPORT ------------
Event: time 1694963427.131005, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042
Event: time 1694963427.131005, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0
Event: time 1694963427.131005, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0
Event: time 1694963427.131005, -------------- SYN_REPORT ------------


Thankyou!!!!

I am not sure what evtest tool you used to test your device. The evtest of linux can know more codes than evtest of kobo device.

From your log, you could use below configuration to turn page. However, the event codes of three buttons are the same, I don't have idea how to do previousPage action.

nextPage 1 330 1