Bluetooth page turning for Kobo eReaders

[Renate]

Hey! I forgot that Kobo is compatible for RPi and I already had that built.
It executes on my Aura2 but I don't even have anything HID.

Actually, the easiest will be if you just copy the report descriptor.
I usually do ioctl, but I forgot that it's in /sys anyway.
Look in /sys/bus/hid/devices/ for your ring thingy.
cd to that, then

cp report_descriptor report.bin

Then zip it and post it here.

Ha. Even this works:

# ./inscan
 # Key Abs Rel Sw  Msc Name
-- --- --- --- --- --- --------------------------------
 0  X           X   X  gpio-keys
 1  X   X              elan-touch

[silvern0va]

Originally Posted by Renate

Hey! I forgot that Kobo is compatible for RPi and I already had that built.
It executes on my Aura2 but I don't even have anything HID.

Actually, the easiest will be if you just copy the report descriptor.
I usually do ioctl, but I forgot that it's in /sys anyway.
Look in /sys/bus/hid/devices/ for your ring thingy.
cd to that, then

cp report_descriptor report.bin

Then zip it and post it here.

Ha. Even this works:

# ./inscan
 # Key Abs Rel Sw  Msc Name
-- --- --- --- --- --- --------------------------------
 0  X           X   X  gpio-keys
 1  X   X              elan-touch

I'm unsure if I'm doing this correctly but this is what I ended up with

00000000 05 0c 09 01 a1 01 85 03 15 00 25 01 75 01 95 0b |..........%.u...|
00000010 09 e9 09 ea 09 cd 0a ae 01 09 30 09 40 09 46 0a |..........0.@.F.|
00000020 23 02 09 b6 09 b5 81 02 95 01 75 0d 81 03 c0 05 |#.........u.....|
00000030 0d 09 02 a1 01 85 02 09 22 a1 02 09 42 15 00 25 |........"...B..%|
00000040 01 75 01 95 01 81 02 09 32 81 02 95 06 81 03 75 |.u......2......u|
00000050 08 09 51 95 01 81 02 05 01 26 ff 0f 75 10 55 0e |..Q......&..u.U.|
00000060 65 33 09 30 35 00 46 b5 04 81 02 46 8a 03 09 31 |e3.05.F....F...1|
00000070 81 02 c0 05 0d 09 54 95 01 75 08 81 02 85 08 09 |......T..u......|
00000080 55 25 05 b1 02 c0 |U%....|
00000086

[Renate]

Originally Posted by silvern0va

I'm unsure if I'm doing this correctly but this is what I ended up with

I was just looking for the binary file, but I can deal with a text dump.

05 0c    Usage page (Consumer)
09 01    Usage (Consumer control)
a1 01    Collection (Application)

85 03    Report id (3)

15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 0b    Report count (11)
09 e9    Usage (Volume increment)
09 ea    Usage (Volume decrement)
09 cd    Usage (Play/Pause)
0a ae 01 Usage (AL Keyboard layout)
09 30    Usage (Power)
09 40    Usage (Menu)
09 46    Usage (Menu escape)
0a 23 02 Usage (AC Home)
09 b6    Usage (Scan previous track)
09 b5    Usage (Scan next track)
81 02    Input (Variable, Absolute)

95 01    Report count (1)
75 0d    Report size (13)
81 03    Input (Constant)

c0       End collection

05 0d    Usage page (Digitizer)
09 02    Usage (Pen)
a1 01    Collection (Application)

85 02    Report id (2)

09 22    Usage (Finger)
a1 02    Collection (Logical)

09 42    Usage (Tip switch)
15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

09 32    Usage (In range)
81 02    Input (Variable, Absolute)

95 06    Report count (6)
81 03    Input (Constant)

75 08    Report size (8)
09 51    Usage (Contact identifier)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

05 01    Usage page (Desktop)
26 ff 0f Logical maximum (4095)
75 10    Report size (16)
55 0e    Unit exponent (-2)
65 33    Unit (in³)
09 30    Usage (X)
35 00    Physical minimum (0)
46 b5 04 Physical maximum (1205)
81 02    Input (Variable, Absolute)

46 8a 03 Physical maximum (906)
09 31    Usage (Y)
81 02    Input (Variable, Absolute)

c0       End collection

05 0d    Usage page (Digitizer)
09 54    Usage (Contact count)
95 01    Report count (1)
75 08    Report size (8)
81 02    Input (Variable, Absolute)

85 08    Report id (8)

09 55    Usage (Contact count maximum)
25 05    Logical maximum (5)
b1 02    Feature (Variable, Absolute)

c0       End collection

That's pretty much ok.

I wouldn't (and I don't) put Physical maximum in. That complicates things.
Without that, 2048 means the center of the screen no matter how big it is.
Once you start putting in Physical maximum in, 2048 means 6" down on a display that might not even be that big.
OTOH, they do specify the units as cubic inches, so it's probably ignored anyway.

Usage 0x32 & 0x42 on the digitizer are correct.
I'd guess that hid.ko is mangling that and that evtest is working correctly.

In any case, it looks like it sends two HID reports, 0x03 (keys) and 0x02 (digitizer) all the time.

Did you try playing with all the modes on the ring?
It seems complicated to me.

[silvern0va]

Originally Posted by Renate

I was just looking for the binary file, but I can deal with a text dump.

05 0c    Usage page (Consumer)
09 01    Usage (Consumer control)
a1 01    Collection (Application)

85 03    Report id (3)

15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 0b    Report count (11)
09 e9    Usage (Volume increment)
09 ea    Usage (Volume decrement)
09 cd    Usage (Play/Pause)
0a ae 01 Usage (AL Keyboard layout)
09 30    Usage (Power)
09 40    Usage (Menu)
09 46    Usage (Menu escape)
0a 23 02 Usage (AC Home)
09 b6    Usage (Scan previous track)
09 b5    Usage (Scan next track)
81 02    Input (Variable, Absolute)

95 01    Report count (1)
75 0d    Report size (13)
81 03    Input (Constant)

c0       End collection

05 0d    Usage page (Digitizer)
09 02    Usage (Pen)
a1 01    Collection (Application)

85 02    Report id (2)

09 22    Usage (Finger)
a1 02    Collection (Logical)

09 42    Usage (Tip switch)
15 00    Logical minimum (0)
25 01    Logical maximum (1)
75 01    Report size (1)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

09 32    Usage (In range)
81 02    Input (Variable, Absolute)

95 06    Report count (6)
81 03    Input (Constant)

75 08    Report size (8)
09 51    Usage (Contact identifier)
95 01    Report count (1)
81 02    Input (Variable, Absolute)

05 01    Usage page (Desktop)
26 ff 0f Logical maximum (4095)
75 10    Report size (16)
55 0e    Unit exponent (-2)
65 33    Unit (in³)
09 30    Usage (X)
35 00    Physical minimum (0)
46 b5 04 Physical maximum (1205)
81 02    Input (Variable, Absolute)

46 8a 03 Physical maximum (906)
09 31    Usage (Y)
81 02    Input (Variable, Absolute)

c0       End collection

05 0d    Usage page (Digitizer)
09 54    Usage (Contact count)
95 01    Report count (1)
75 08    Report size (8)
81 02    Input (Variable, Absolute)

85 08    Report id (8)

09 55    Usage (Contact count maximum)
25 05    Logical maximum (5)
b1 02    Feature (Variable, Absolute)

c0       End collection

That's pretty much ok.

I wouldn't (and I don't) put Physical maximum in. That complicates things.
Without that, 2048 means the center of the screen no matter how big it is.
Once you start putting in Physical maximum in, 2048 means 6" down on a display that might not even be that big.
OTOH, they do specify the units as cubic inches, so it's probably ignored anyway.

Usage 0x32 & 0x42 on the digitizer are correct.
I'd guess that hid.ko is mangling that and that evtest is working correctly.

In any case, it looks like it sends two HID reports, 0x03 (keys) and 0x02 (digitizer) all the time.

Did you try playing with all the modes on the ring?
It seems complicated to me.

Yes! The other mode is touch inputs only though so I wasn't sure there was anything useful with that. I'm starting to think I just need to get something else. I just wanted something small with 2 button inputs.

[lumping-sugar66]

Originally Posted by silvern0va

Sorry I don't have the option to edit posts. This will be the last response and hopefully have all the info. I got all the inputs I can do via evtest on my Kobo

Input device name: "D01 Pro"
Supported events:
Event code 115 (VolumeUp)
Event code 116 (Power)
Event code 139 (Menu)
nothing working except for some reason double tapping up is causing it to wake/sleep.

try:
nextPage EV_KEY KEY_VOLUMEUP 0
or
nextPage EV_KEY 115 0

I don't know what that hex codes at the end of your commands is supposed to be but the plugin in my case expects 0 or 1 to make the click act either on press or release.

[silvern0va]

Originally Posted by lumping-sugar66

try:
nextPage EV_KEY KEY_VOLUMEUP 0
or
nextPage EV_KEY 115 0

I don't know what that hex codes at the end of your commands is supposed to be but the plugin in my case expects 0 or 1 to make the click act either on press or release.

Unfortunately that's not working either. Here's all the options I've tried.
prevPage EV_MSC SCANCODE 0xc00b5
nextPage EV_MSC SCANCODE 0xc00b6
nextPage EV_MIS SCANCODE c00b5
nextPage EV_MIS SCANCODE c00e9
nextPage EV_MIS SCANCODE c0040
nextPage EV_MIS SCANCODE c0046
prevPage EV_MIS SCANCODE c00b6
prevPage EV_MIS SCANCODE c00ea
prevPage EV_MIS SCANCODE c0030
nextPage EV_KEY SCANCODE c00b5
nextPage EV_KEY SCANCODE c00e9
nextPage EV_KEY SCANCODE c0040
nextPage EV_KEY SCANCODE c0046
prevPage EV_KEY SCANCODE c00b6
prevPage EV_KEY SCANCODE c00ea
prevPage EV_KEY SCANCODE c0030
nextPage 4 4 c00b5
nextPage 4 4 c00e9
nextPage 4 4 c0040
nextPage 4 4 c0046
prevPage 4 4 c00b6
prevPage 4 4 c00ea
prevPage 4 4 c0030
nextPage EV_ABS ABS_X 512
prevPage EV_ABS ABS_X 3328
prevPage EV_KEY KEY_ESC 1
prevPage EV_KEY KEY_VOLUME_DOWN 1
nextPage EV_KEY KEY_VOLUME_UP 1
prevPage EV_KEY KEY_POWER 1
nextPage EV_KEY KEY_MENU 1
nextPage EV_KEY KEY_NEXTSONG 1
prevPage EV_KEY KEY_PREVIOUSSONG 1
nextPage EV_KEY KEY_HOMEPAGE 1
nextPage EV_ABS ABS_X 2047
nextPage EV_ABS ABS_Y 2047
nextPage EV_ABS ABS_X 1024
prevPage EV_ABS ABS_Y 512
nextPage EV_MSC MSC_SCAN 0xc0030
prevPage EV_MSC MSC_SCAN 0xc0046
prevPage EV_KEY KEY_ESC 0
prevPage EV_KEY KEY_VOLUME_DOWN 0
nextPage EV_KEY KEY_VOLUME_UP 0
prevPage EV_KEY KEY_POWER 0
nextPage EV_KEY KEY_MENU 0
nextPage EV_KEY KEY_NEXTSONG 0
prevPage EV_KEY KEY_PREVIOUSSONG 0
nextPage EV_KEY KEY_HOMEPAGE 0
nextPage EV_KEY 115 0
nextPage EV_KEY 115 1

I think this page turner is just too complex and annoying to properly work with the plugin? I'm looking for other options but I already have the other remote that clips on, I was just looking for something smaller and more convenient. It should not be this hard to find a ring with two button inputs and bluetooth but here we are!

[Renate]

Alright, I'm all confused.
I don't know what this "config" file is.
Is that supposed to be part of standard Linux?
Normally all the stuff coming over HID should just work.

See this: https://github.com/torvalds/linux/bl...-input.c#L1160
The codes are already there.
Maybe I'm being stupid.

[lumping-sugar66]

Originally Posted by Renate

I don't know what this "config" file is.

If you're asking about the the config file I mentioned earlier, I am referring to the file you're suppose to create to map your bluetooth devices buttons to actions. the file needs to go into .btpt/<DEVICENAME>. The device name bit is important. My bluetooth device is called BOOD 202 so my config file is

.btpt/BOOD 202

8bitdo users do

.btpt/8BitDo Zero 2 gamepad

There's no need to modify the system files for this to work.

The plugin expects decimal or linux enum names for the actions as they're defined here:
https://github.com/torvalds/linux/bl...-event-codes.h
That's why I mentioned 115 or KEY_VOLUMEUP because they're identical:

#define KEY_VOLUMEUP 115

[lumping-sugar66]

Originally Posted by silvern0va

Unfortunately that's not working either. Here's all the options I've tried.

....

I think this page turner is just too complex and annoying to properly work with the plugin? I'm looking for other options but I already have the other remote that clips on, I was just looking for something smaller and more convenient. It should not be this hard to find a ring with two button inputs and bluetooth but here we are!

Well, anything you can't figure out is complex until it isn't. Personally I didn't find the application of this too complicated but it could be frustrating if you can't find the right combination to work.

Maybe your buttons aren't triggering the event you're expecting them to. Do you have a linux computer that you can evtest on? I found on an ubuntu machine the evtest told me different information.

Here's another test for you. The plugin will output a console message if your button presses are detected but you're not in reading view. So go ahead and pair your device, go to your home screen and through SSH/Telnet run "logread -f", then press your bluetooth buttons. If you're seeing on the console "Not in reading view" or something like that, then your config file is incorrect. If you're not seeing this message, I'm afraid you still need to figure out why your device hasn't paired properly yet. Do check out uhid.ko patch, it's sometimes required. Mentioned in this thread somewhere.

[Renate]

Thanks. Apparently this .btpt is not related to anything but Kobo.

[lumping-sugar66]

Originally Posted by Renate

Thanks. Apparently this .btpt is not related to anything but Kobo.

Ah, yes. the .btpt sits at ~/.btpt or /mnt/onboard/.btpt and stores the text config file. Once again, config file must absolutely match the device name No extensions! (like BOOD 202.txt etc.)

[bohn]

in case anyone was wondering about devices that work out of the box - the logitech r500s works for me without doing much to get it going - only thing is, it needs wifi on (to keep Bluetooth on).