etatto Posted April 22, 2017 Share Posted April 22, 2017 Hi! Sorry if it is already covered but I didn't find a complete answer on the subject on the forum... So I have activated the uart3 overlay and enable CTS and RTS on an own-build Armbian 5.27 dev flavor for my NanoPi NEO Air. But I was unable to get the AP6212 Bluetooth working, I've try some infos/commands found elsewhere without any luck My question: Is Bluetooth on Nanopi NEO Air (or any H3 board with AP6212) still WIP on Armbian? Thanks. Emmanuel. Link to comment Share on other sites More sharing options...
Igor Posted April 22, 2017 Share Posted April 22, 2017 Kernel 4.x for H3 is still considered WIP and Bluetooth in general is not high priority. I also thought we fixed this - it should work with help of this firmware uploading script: https://github.com/igorpecovnik/lib/blob/master/scripts/ap6212-bluetooth ... which should be a part of the system. It's possible that it worked and we break it. But what and where ... ? Link to comment Share on other sites More sharing options...
etatto Posted April 22, 2017 Author Share Posted April 22, 2017 Yes I first try with this ap6212-bluetooth script but without success. A "bcm43xx_init" always time out, like "Initialization timed out." Link to comment Share on other sites More sharing options...
alex_ad Posted June 28, 2017 Share Posted June 28, 2017 (edited) Hello, I have the same problem. I am using nanopi neo air with armbian 5.32(mainline). I want to look into rfkill not listing bluetooth device. How to debug this? Edited June 28, 2017 by Tido removed 'quote' Link to comment Share on other sites More sharing options...
Henrik Larsson Posted July 2, 2018 Share Posted July 2, 2018 Maybe this thread is of help: Link to comment Share on other sites More sharing options...
Recommended Posts