![]() |
#61 | |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 193
Karma: 1074916
Join Date: Jan 2021
Device: Likebook Ares
|
Quote:
This is to install the Webserver in Kobo: $ wget https://github.com/tylpk1216/KoboPag...0/KoboRoot.tgz $*cp KoboRoot.tgz /run/media/jospalau/KOBOeReader/.kobo This is the Android app: $ wget https://github.com/tylpk1216/KoboPag...HTTPClient.apk It shouldn't be difficult to make a simple app for IPhone to so something similar or maybe there is something similar to Task. I made a simple Linux demon to use the headphones like this: Code:
import subprocess from evdev import InputDevice, categorize, ecodes dev = InputDevice('/dev/input/event24') print(dev) def getKey(): for event in dev.read_loop(): if event.type == ecodes.EV_KEY: c = categorize(event) if c.keystate == c.key_down: yield c.keycode keygenerator = getKey() while True: c = next(keygenerator) print(c) if c == 'KEY_PLAYCD': subprocess.run("curl http://192.168.50.101/right", shell=True, check=True) Sent from my CPH2021 using Tapatalk |
|
![]() |
![]() |
![]() |
#62 |
Enthusiast
![]() Posts: 28
Karma: 10
Join Date: Jun 2008
Device: Sony PRS-500
|
I spent a bunch of time last Friday setting up the $5 ($7 for me) bluetooth camera remote previously mentioned.
I had weird missteps along the way but it did indeed work with the Reddit-linked steps. My main problem is figuring out how to use NickelMenu to toggle bluetooth. I am able to turn it on and off AFTER the bluetooth switch is turned on in the settings. I suspect it's a "hardware" switch. As I have to do it every time I turn on the reader it feels clunky. I had an idea that maybe rfkill would turn it on but apparently /dev/rfkill doesn't exist. Code:
[admin@io root]# rfkill list bluetooth rfkill: /dev/rfkill: No such file or directory Code:
menu_item :reader :Bluetooth (toggle) :cmd_output :500 :quiet :/sbin/lsmod |/bin/grep uhid || /sbin/insmod /mnt/onboard/.adds/kobo-libra2-uhid-module/uhid.ko chain_success:skip:2 chain_failure :dbg_toast :problem installing uhid module chain_always:skip:-1 chain_success :cmd_output :500 :quiet :/bin/bluetoothctl list |/bin/grep -q Kobo chain_success:skip:2 chain_failure :dbg_toast :please start bluetooth from settings chain_always:skip:-1 chain_success :cmd_output :500 :quiet :/bin/bluetoothctl show |/bin/grep -q "Powered: no" chain_success:skip:3 chain_failure :cmd_output :1500 :quiet :/bin/bluetoothctl power off chain_success :dbg_toast :bluetooth turned off chain_always:skip:-1 chain_success :cmd_output :1500 :quiet :/bin/bluetoothctl power on chain_success :dbg_toast :bluetooth turned on I don't really want to mess with stopping/starting bluetoothd. |
![]() |
![]() |
Advert | |
|
![]() |
#63 | |
Groupie
![]() ![]() ![]() Posts: 195
Karma: 245
Join Date: Aug 2009
Location: USA
Device: Kobo Clara Blue PRS 350
|
Quote:
|
|
![]() |
![]() |
![]() |
#64 | |
Groupie
![]() ![]() ![]() Posts: 195
Karma: 245
Join Date: Aug 2009
Location: USA
Device: Kobo Clara Blue PRS 350
|
Quote:
Also, I noticed that when I connected a bluetooth speaker, it added this to the Kobo ereader.config. [BluetoothSettings] DefaultAudioDevice=/org/bluez/hci0/dev_28_F0_01_D3_5E_C7 LeftVolume_org_bluez_hci0_dev_98_52_3D_E8_DE_F0=12 5 RightVolume_org_bluez_hci0_dev_98_52_3D_E8_DE_F0=1 25 SoftwareVolume_org_bluez_hci0_dev_98_52_3D_E8_DE_F 0=false Is there anything like that in your Kobo ereader.config with a working device? By the way, I reset my reader which took that out so it wouldn't interfer and I am on the original firmware as well. Thanks! |
|
![]() |
![]() |
![]() |
#65 | |
Enthusiast
![]() Posts: 28
Karma: 10
Join Date: Jun 2008
Device: Sony PRS-500
|
Quote:
I noted that it takes me about 9 screen taps after waking up from sleep to re-enable Bluetooth which gets old. And if I use the book to help me sleep, I end up doing this several times a night until I give up and use the reader buttons. First world problems. |
|
![]() |
![]() |
Advert | |
|
![]() |
#66 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 77
Karma: 24492
Join Date: Jul 2013
Location: France
Device: Kindle 4, PBk Lux 2, PBk Lux 3, K Aura, K Libra H2O, K Libra2
|
Hello,
I bought thisTiktok ring https://www.amazon.fr/dp/B09YHMGY8P?...roduct_details for my Libra 2, I patched kobo-libra2-uhid-module using the guide https://github.com/tylpk1216/kobo-libra2-uhid-module but the ring still not works in my case ![]() For those interested on, here the evtest result from my PC: Code:
Input device ID: bus 0x5 vendor 0x5ac product 0x22c version 0x11b Input device name: "D01" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 139 (KEY_MENU) Event code 172 (KEY_HOMEPAGE) 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 1904 Min 0 Max 4095 Event code 1 (ABS_Y) Value 1904 Min 0 Max 4095 Event code 40 (ABS_MISC) Value 1 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) ############################################################################# Switch NEXT closed clip side ########################### Event: time 1673767852.727950, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673767852.727950, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1673767852.727950, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1 Event: time 1673767852.727950, type 3 (EV_ABS), code 1 (ABS_Y), value 3200 Event: time 1673767852.727950, -------------- SYN_REPORT ------------ Event: time 1673767852.728038, type 3 (EV_ABS), code 1 (ABS_Y), value 2600 Event: time 1673767852.728038, -------------- SYN_REPORT ------------ Event: time 1673767852.728130, type 3 (EV_ABS), code 1 (ABS_Y), value 2300 Event: time 1673767852.728130, -------------- SYN_REPORT ------------ Event: time 1673767852.741218, type 3 (EV_ABS), code 1 (ABS_Y), value 2000 Event: time 1673767852.741218, -------------- SYN_REPORT ------------ Event: time 1673767852.771245, type 3 (EV_ABS), code 1 (ABS_Y), value 1700 Event: time 1673767852.771245, -------------- SYN_REPORT ------------ Event: time 1673767852.801314, type 3 (EV_ABS), code 1 (ABS_Y), value 1400 Event: time 1673767852.801314, -------------- SYN_REPORT ------------ Event: time 1673767852.831417, type 3 (EV_ABS), code 1 (ABS_Y), value 1100 Event: time 1673767852.831417, -------------- SYN_REPORT ------------ Event: time 1673767852.861428, type 3 (EV_ABS), code 1 (ABS_Y), value 800 Event: time 1673767852.861428, -------------- SYN_REPORT ------------ Event: time 1673767852.891383, type 3 (EV_ABS), code 1 (ABS_Y), value 500 Event: time 1673767852.891383, -------------- SYN_REPORT ------------ Event: time 1673767852.921399, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673767852.921399, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1673767852.921399, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0 Event: time 1673767852.921399, type 3 (EV_ABS), code 1 (ABS_Y), value 200 Event: time 1673767852.921399, -------------- SYN_REPORT ------------ ############################################################################# Switch NEXT opened clip side ########################### Event: time 1673767988.794856, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673767988.794856, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1673767988.794856, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1 Event: time 1673767988.794856, type 3 (EV_ABS), code 1 (ABS_Y), value 1012 Event: time 1673767988.794856, -------------- SYN_REPORT ------------ Event: time 1673767988.794985, type 3 (EV_ABS), code 1 (ABS_Y), value 1100 Event: time 1673767988.794985, -------------- SYN_REPORT ------------ Event: time 1673767988.795188, type 3 (EV_ABS), code 1 (ABS_Y), value 1400 Event: time 1673767988.795188, -------------- SYN_REPORT ------------ Event: time 1673767988.809090, type 3 (EV_ABS), code 1 (ABS_Y), value 1700 Event: time 1673767988.809090, -------------- SYN_REPORT ------------ Event: time 1673767988.839143, type 3 (EV_ABS), code 1 (ABS_Y), value 2000 Event: time 1673767988.839143, -------------- SYN_REPORT ------------ Event: time 1673767988.869207, type 3 (EV_ABS), code 1 (ABS_Y), value 2300 Event: time 1673767988.869207, -------------- SYN_REPORT ------------ Event: time 1673767988.899142, type 3 (EV_ABS), code 1 (ABS_Y), value 2600 Event: time 1673767988.899142, -------------- SYN_REPORT ------------ Event: time 1673767988.929105, type 3 (EV_ABS), code 1 (ABS_Y), value 2900 Event: time 1673767988.929105, -------------- SYN_REPORT ------------ Event: time 1673767988.959090, type 3 (EV_ABS), code 1 (ABS_Y), value 3200 Event: time 1673767988.959090, -------------- SYN_REPORT ------------ Event: time 1673767988.989242, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673767988.989242, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1673767988.989242, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0 Event: time 1673767988.989242, type 3 (EV_ABS), code 1 (ABS_Y), value 3500 Event: time 1673767988.989242, -------------- SYN_REPORT ------------ ############################################################################# Middle switch ########################### Event: time 1673768034.234654, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673768034.234654, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 Event: time 1673768034.234654, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 1 Event: time 1673768034.234654, type 3 (EV_ABS), code 1 (ABS_Y), value 1904 Event: time 1673768034.234654, -------------- SYN_REPORT ------------ Event: time 1673768034.234682, type 4 (EV_MSC), code 4 (MSC_SCAN), value d0042 Event: time 1673768034.234682, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 0 Event: time 1673768034.234682, type 1 (EV_KEY), code 320 (BTN_TOOL_PEN), value 0 Event: time 1673768034.234682, -------------- SYN_REPORT ------------ Code:
prevPage EV_ABS ABS_Y 3500 nextPage EV_ABS ABS_Y 200 |
![]() |
![]() |
![]() |
#67 |
Enthusiast
![]() Posts: 25
Karma: 80
Join Date: Apr 2019
Device: Kindle Paperwhite3, Hisense A5, HyRead Gaze Pocket, Kobo Elipsa
|
If your ring device can appear in /dev/input/eventXX (XX means number for your ring device), you don't need to use kobo-libra2-uhid-module.
If your evtest report is from the Linux of Kobo, the value is hexadecimal. When you use kobo-btpt, you need to convert the value to decimal number. The ABS_Y is for the location of touching panel, I am not sure whether you can use it in kobo-btpt. In my experience, the evtest of PC Linux can get more information when you use bluetooth device. You can get the right event, like EV_KEY - KEY_VOLUMEDOWN ... Then you can use suitable event in kobo-btpt. |
![]() |
![]() |
![]() |
#68 |
Connoisseur
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 77
Karma: 24492
Join Date: Jul 2013
Location: France
Device: Kindle 4, PBk Lux 2, PBk Lux 3, K Aura, K Libra H2O, K Libra2
|
Hello,
the events shown are coming from a Linux PC. Unfortunately I am no more able to test this because my Libra 2 bricked during an update. Back to the supplier. Thanks for your sharing tylpk. |
![]() |
![]() |
![]() |
#69 |
Enthusiast
![]() Posts: 28
Karma: 10
Join Date: Jun 2008
Device: Sony PRS-500
|
Too bad. Next time if you get a replacement try to remote into the device. Not only is there evtest, the bluetooth page turner code puts debug data in the event log, which helped me find my way to a solution.
|
![]() |
![]() |
![]() |
#70 | |
Junior Member
![]() Posts: 1
Karma: 10
Join Date: Jan 2023
Device: Kobo Libra 2
|
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: Quote:
|
|
![]() |
![]() |
![]() |
#71 |
Groupie
![]() ![]() ![]() Posts: 195
Karma: 245
Join Date: Aug 2009
Location: USA
Device: Kobo Clara Blue PRS 350
|
Well, I tried 2 different bluetooth remote devices with no luck
![]() So, I saw this reddit post and ended up buying a SYUKUYU RF Remote Control Page Turner. Works great! Plus I can use it on all my ereaders. Kobo should definitely add a page turner to their devices. Certainly an excellent selling point. |
![]() |
![]() |
![]() |
#72 | |
Enthusiast
![]() Posts: 28
Karma: 10
Join Date: Jun 2008
Device: Sony PRS-500
|
Quote:
evtest is on my Kobo Libra 2. logread is also available. My page turnin' activites from last night from when I turned on Bluetooth to when it went on standby (I fell asleep): Code:
[admin@io root]# logread |grep BluetoothPageTurner <snip> Jan 26 22:05:44 nickel: (BluetoothPageTurner) checking /proc/bus/input/devices for new devices Jan 26 22:05:44 nickel: (BluetoothPageTurner) skipping Bus=0018 Vendor=0000 Product=0000 Version=0000 Jan 26 22:05:44 nickel: (BluetoothPageTurner) skipping Bus=0018 Vendor=001b Product=0000 Version=0000 Jan 26 22:05:44 nickel: (BluetoothPageTurner) skipping Bus=0018 Vendor=0416 Product=1001 Version=28bb Jan 26 22:05:44 nickel: (BluetoothPageTurner) skipping Bus=0019 Vendor=0001 Product=0001 Version=0100 Jan 26 22:05:44 nickel: (BluetoothPageTurner) skipping Bus=0019 Vendor=0001 Product=0001 Version=0100 Jan 26 22:05:44 nickel: (BluetoothPageTurner) found Bus=0005 Vendor=2717 Product=0040 Version=0023 Jan 26 22:05:44 nickel: (BluetoothPageTurner) acquired device event5: 0c3aca52dffc Jan 26 22:05:44 nickel: (BluetoothPageTurner) devices scanned Jan 26 22:07:14 nickel: (BluetoothPageTurner) nextPage Jan 26 22:08:37 nickel: (BluetoothPageTurner) prevPage Jan 26 22:09:43 nickel: (BluetoothPageTurner) nextPage Jan 26 22:10:31 nickel: (BluetoothPageTurner) nextPage Jan 26 22:11:55 nickel: (BluetoothPageTurner) nextPage Jan 26 22:13:12 nickel: (BluetoothPageTurner) nextPage Jan 26 22:14:33 nickel: (BluetoothPageTurner) nextPage Jan 26 22:16:11 nickel: (BluetoothPageTurner) nextPage Jan 26 22:17:06 nickel: (BluetoothPageTurner) nextPage Jan 26 22:18:06 nickel: (BluetoothPageTurner) nextPage Jan 26 22:20:08 nickel: (BluetoothPageTurner) nextPage Jan 26 22:21:34 nickel: (BluetoothPageTurner) nextPage Jan 26 22:21:40 nickel: (BluetoothPageTurner) prevPage Jan 26 22:21:42 nickel: (BluetoothPageTurner) nextPage Jan 26 22:23:05 nickel: (BluetoothPageTurner) nextPage Jan 26 22:24:31 nickel: (BluetoothPageTurner) nextPage Jan 26 22:24:34 nickel: (BluetoothPageTurner) prevPage Jan 26 22:24:35 nickel: (BluetoothPageTurner) nextPage Jan 26 22:26:32 nickel: (BluetoothPageTurner) nextPage Jan 26 22:38:36 nickel: (BluetoothPageTurner) lost device Jan 26 22:38:36 nickel: (BluetoothPageTurner) waiting for input devices |
|
![]() |
![]() |
![]() |
#73 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,788
Karma: 6990707
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
|
Yeah, sorry about the delay; I've barely had any time for kobo stuff this year...
|
![]() |
![]() |
![]() |
#74 |
Junior Member
![]() Posts: 7
Karma: 10
Join Date: Feb 2023
Device: Kobo Libra 2
|
I don't get `/dev/input/event3` after pairing and connected my bluetooth pageturner. Any idea how I can troubleshoot?
|
![]() |
![]() |
![]() |
#75 |
Junior Member
![]() Posts: 7
Karma: 10
Join Date: Feb 2023
Device: Kobo Libra 2
|
```
Mar 1 14:15:07 bluetoothd[1825]: Bluetooth daemon 5.63 Mar 1 14:15:07 bluetoothd[1825]: src/main.c:check_options() Unknown key InitVolume for group General in /etc/bluetooth/main.conf Mar 1 14:15:07 bluetoothd[1825]: Starting SDP server Mar 1 14:15:07 bluetoothd[1825]: src/rfkill.c:rfkill_init() Failed to open RFKILL control device Mar 1 14:15:07 bluetoothd[1825]: Bluetooth management interface 1.9 initialized Mar 1 14:15:09 bluetoothd[1825]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Unknown Command (0x01) Mar 1 14:15:09 bluetoothd[1825]: Endpoint registered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/1 Mar 1 14:15:09 bluetoothd[1825]: Endpoint registered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/2 Mar 1 14:15:09 bluetoothd[1825]: Player registered: sender=:1.0 path=/com/kobo/bluetooth/MediaPlayer Mar 1 14:15:10 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 Mar 1 14:15:13 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 Mar 1 14:27:37 bluetoothd[1825]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down Mar 1 14:27:37 bluetoothd[1825]: Endpoint unregistered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/1 Mar 1 14:27:37 bluetoothd[1825]: Endpoint unregistered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/2 Mar 1 14:30:04 bluetoothd[1825]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Unknown Command (0x01) Mar 1 14:30:04 bluetoothd[1825]: Endpoint registered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/1 Mar 1 14:30:04 bluetoothd[1825]: Endpoint registered: sender=:1.3 path=/org/bluez/hci0/A2DP/SBC/Source/2 Mar 1 14:30:04 bluetoothd[1825]: Player registered: sender=:1.0 path=/com/kobo/bluetooth/MediaPlayer Mar 1 14:30:05 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 Mar 1 14:30:07 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 Mar 1 14:32:06 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 Mar 1 14:32:07 bluetoothd[1825]: src/service.c:service_accept() input-hog profile accept failed for A0:9D:FC:63:AD:86 ``` I noticed this last line input-hog profile accept failed for ... |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Accessories New hand stick Bluetooth for turning page! | guitu | Amazon Kindle | 16 | 07-23-2021 12:20 AM |
Kobo Clara HD - Quick page turning | Rarronno | Kobo Reader | 7 | 09-06-2019 01:26 AM |
Bluetooth Page Turning | hismaimai8888 | General Discussions | 2 | 11-25-2018 11:37 AM |
Bluetooth Page Turning | copaw | General Discussions | 14 | 11-17-2015 02:09 PM |
Kobo app page turning animation?? | morgan freeman | Android Devices | 0 | 03-23-2013 11:15 PM |