View Single Post
Old 10-02-2023, 03:46 PM   #113
Renate
Onyx-maniac
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: 3,743
Karma: 16196313
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Quote:
Originally Posted by NiLuJe View Post
(The fact that, so far, every device coming out has had a slightly or not so slightly different BT chip and associated software quirks did not help, FWIW).
C'mon, this stuff is trivial. All you have to do is read the manual.
(The Bluetooth documentation is about 3700 pages the last that I checked.)

But seriously, you should be able to get this stuff to work.
I've made 4 Bluetooth devices with my own hardware and software.
I've modded 4 other stock Bluetooth devices (keyboards & clickers) to have custom names and custom keypresses.
I've reverse-engineered a bunch of stock Bluetooth devices (iRig BlueBoard, heart monitor) so that I could write custom Android handlers.

Usually the problem is to get the BT to send commands (like PgDn) and to get the apps to honor them.

My biggest problem is the accessories showing that they are connected but the device not acknowledging them.
This is usually because I have so many loose devices that are paired already to them.

Last edited by Renate; 10-02-2023 at 07:40 PM.
Renate is offline   Reply With Quote