View Single Post
Old 03-14-2022, 05:20 AM   #6
tsowell
Junior Member
tsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five wordstsowell can name that ebook in five words
 
Posts: 4
Karma: 37912
Join Date: Mar 2022
Device: Kobo Libra 2
Quote:
Originally Posted by Cootey View Post
I'm very intrigued in this project. I purchased a $20 Bluetooth presentation device off Amazon that worked initially to turn pages except the Kobo kept dropping the BT connection if I took too long to read a page. Then I'd have to dig back into the settings to reactivate the pairing. Too much work! Also, the pairing period became shorter and shorter, so I eventually returned the device.

I suspect the cheap device was at fault. How long do devices stay paired using your utility?
Kobo is pretty aggressive about disabling Bluetooth when it isn't being used - the timeout is 150 seconds if I remember correctly. I was able to find a heartbeat mechanism that the built-in audio book player uses to keep Bluetooth enabled, and my utility uses that to keep Bluetooth on for 10 minutes after the last input event.

tylpk's solution (toggling the "Force Wi-Fi On" setting) should also work if your Bluetooth device already works with Kobo.

I'm actually not sure how my code will work with devices that can already turn pages... I think you would get duplicate page turn events. If you only want to make use of the Bluetooth keep-alive feature, you could try specifying a bogus method in the device configuration file - instead of "nextPage" and "prevPage", use "noOp", for example.
tsowell is offline   Reply With Quote