View Single Post
Old 06-28-2021, 08:37 PM   #18
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Skydog View Post
Bug for audio, BT or both?
Bug for whatever you were trying to use the keyboard with.
Quote:
It clearly connects to the audio devices I listed in the first post and many more. Further, the connection was confirmed via automated voice built in to some of my devices. Interestingly, every device discovered/listed was preceded by "audio_card" (including the smart tv).
And that is probably largely OS level support. It might actually be harder to prevent it than to just let it sit there using a few resource. It doesn't matter much as there is no way to use it. There are no audio applications in the firmware. And having this, does let Kobo add an audio application at some time in the future. But, I think it is more likely to happen in another device than be added to the Elipsa.
davidfor is offline   Reply With Quote