Thread: Bluetooth Page Turner plugin for Kobo KOReader
View Single Post
Old 12-28-2025, 11:30 PM   #82
lumping-sugar66
Groupie
lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.lumping-sugar66 knows better than to ask about the Gravitic Imploder Lance.
 
lumping-sugar66's Avatar
 
Posts: 152
Karma: 87635
Join Date: Oct 2023
Location: Ontario, Canada
Device: Kobo Aura Edition 2, Kobo Clara 2E, Kobo Libra 2
I made some changes in a special branch https://github.com/onatbas/bluetooth.koplugin/tree/mtk

Using @OG-Booksmith's changes from kobo.koreader (mentioned here https://www.mobileread.com/forums/sh...00&postcount=3), I added an MTK backend alternative methods to bluetooth events. This is highly experimental and not tested. But if colour/bw/elipsa users could load this up, can you check Diagnostics > Device Type and see if isMTK flag is being detected correctly?

If so, there’s a chance the other methods may work, too. This is not tested on a real device don’t have the device to test, but if you’re willing to give it a shot, please do and create an issue in the GitHub repository or shoot me an email.

Apart from potentially triggering the kernel issue https://github.com/koreader/koreader/issues/12739, I don’t believe this would cause a lot of long-term trouble.
lumping-sugar66 is offline   Reply With Quote