Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader

Notices

Reply
 
Thread Tools Search this Thread
Old 10-11-2023, 02:12 PM   #121
Renate
Wizard
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 2,031
Karma: 8298341
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Quote:
Originally Posted by danosaurus_rex View Post
... by double clicking ...
Death to double clicking!
Renate is online now   Reply With Quote
Old 10-24-2023, 03:34 AM   #122
esteban2023
Junior Member
esteban2023 began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Oct 2023
Device: Kobo 2
Getting close but not there yet...

I've found a couple of use cases where having a bluetooth page turner would be quite useful.
I've tried with 4 devices...
So far I've managed to make it work with just one, a cheap bluetooth joystick.
I want to make it work with a selfie remote control.
I've checked with evtest and it is generating a KEY_VOLUMEUP event.
But I've tried to configure that and it is not working...
With a second clicker it generates one KEY_VOLUMEUP and KEY_VOLUMEDOWN in loop (a different event on each click)
Any ideas on how to continue...
esteban2023 is offline   Reply With Quote
Old 10-24-2023, 08:40 AM   #123
Renate
Wizard
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 2,031
Karma: 8298341
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
I've tried a bunch of cheap remotes. The single button (or Android/Apple two button) ones usually don't do anything useful. Some of them do Enter.

Ok, I know that this part is not useful for most people. In the past, when selfie clickers were not so popular many of them used a masked ROM for the Bluetooth stack and an EEPROM for the OEM's code. Finding and altering the USB HID descriptor was easy. Then you could have the clicker generate any key code. You just needed an I²C interface to reprogram. I did this to one clicker and then put it into a little foot switch. Since then I've just replaced it with my own Bluetooth circuit.

The other way is to make a custom /system/usr/keylayout/Vendor_1234_Product_5678.kl that will remap your useless button to what you want. This will work fine, but it means that you can't use your clicker on a random device.

There are clickers with "5 way" controls, but I've found the mechanical properties ungainly.

Quote:
Originally Posted by esteban2023 View Post
I've checked with evtest and it is generating a KEY_VOLUMEUP event.
It sounds like the keylayout is the way to go for you?
Renate is online now   Reply With Quote
Old 10-25-2023, 07:54 PM   #124
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,657
Karma: 6254413
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by Renate View Post
/system/usr/keylayout/
Kobo eReaders don't run android.
geek1011 is offline   Reply With Quote
Old 10-25-2023, 08:32 PM   #125
Renate
Wizard
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 2,031
Karma: 8298341
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5
Quote:
Originally Posted by geek1011 View Post
Kobo eReaders don't run android.
You have a point there.
Google made a few changes to the Linux-like kernel.
It's not really "Android" because it's running underneath the Android subsystem.

I have an English Bluetooth keyboard and a Russian Bluetooth keyboard.
I can grab either one and it just works (without any language selection) on my Androids.
I don't think you can do this with most straight Linux systems, can you?

You could also modify your reader app (even in Kobo) to respond to VolUp or Enter (the usual two keys on $1 clickers).

As I said, the clickers with EEPROMs are easy to hack.
I bought a dozen Chinese clickers a while ago and they were the ones without EEPROMs.
If anybody knows a source for the ones with EEPROMs.
OTOH, most selfie clickers time out in under a minute.
A page can be longer than a minute if you end up thinking.
I've run into problems trying to stretch that out.
In the end I opted for completely custom hardware/software.

An article about $1 clicker hacking:
https://hackaday.com/2016/09/14/hack...etooth-device/

Ha! I reread that article and it reminded me of another problem with badly written clickers.
They present themselves as full keyboards.
On Android that means that on-screen keyboards will not pop up by default (although there is an option now) while you are using a clicker.
The option causes problems too because on-screen keyboards will then pop up when using a regular Bluetooth keyboard.

When I write my USB HID descriptors I make it clear that they can't send A-Z or 0-9 so it won't be confused with a "keyboard".

Last edited by Renate; 10-25-2023 at 08:51 PM.
Renate is online now   Reply With Quote
Old Yesterday, 12:10 PM   #126
psycholark
Junior Member
psycholark began at the beginning.
 
Posts: 1
Karma: 10
Join Date: Dec 2023
Device: Kobo Libra 2
Quote:
Originally Posted by Henk2001 View Post
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:

Spoiler:
On connection

Code:
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!!!!
Did you ever find a config that worked? I also have a JX-03 and would love to get it working to turn pages.

Last edited by DNSB; Yesterday at 02:38 PM. Reason: added spoiler tags.
psycholark is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Accessories New hand stick Bluetooth for turning page! guitu Amazon Kindle 16 07-23-2021 01:20 AM
Kobo Clara HD - Quick page turning Rarronno Kobo Reader 7 09-06-2019 02:26 AM
Bluetooth Page Turning hismaimai8888 General Discussions 2 11-25-2018 12:37 PM
Bluetooth Page Turning copaw General Discussions 14 11-17-2015 03:09 PM
Kobo app page turning animation?? morgan freeman Android Devices 0 03-24-2013 12:15 AM


All times are GMT -4. The time now is 07:24 AM.


MobileRead.com is a privately owned, operated and funded community.