View Single Post
Old 08-15-2024, 08:58 AM   #7
lumping-sugar66
Zealot
lumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trollslumping-sugar66 doesn't feed trolls
 
lumping-sugar66's Avatar
 
Posts: 100
Karma: 81981
Join Date: Oct 2023
Location: Ontario, Canada
Device: Kobo Aura Edition 2, Kobo Clara 2E
Hi, it looks like you're making good progress.

That screenshot confirms that the bluetooth is turned on properly, unfortunately it doesn't say anything about connection (it never does).

If your device is getting added to event4, then you need to modify device.lua patch to have it connect to /dev/input/event4.

You need to add
Code:
    local success, err = pcall(function()
        self.input.open("/dev/input/event4")
    end)
to device/kobo/device.lua right under
Code:
self.input.open("fake_events")
. Currently there's a bug with the plugin auto connecting, so all inputs need to be opened through the koplugin code. This also means you need to "Restart KOreader" after turning on bluetooth via the plugin.

I too have the plugin installed on nickel, it won't break your installation, as nickel isn't working when koreader is working.

Since you say that event code 4 works on Nickel page turner I won't press too much on this but event code 4 seems suspicious. You can cross-check with your .btpt/ config file.

What's your bluetooth device by the way? If the above don't work, please share your device.lua and main.lua files, and let's have a look. When you do that, kindly let me know where is your koreader installation in the device. A good way of letting me know is to cd into bluetooth.koplugin folder and do
Code:
pwd
and show me the result.
lumping-sugar66 is offline   Reply With Quote