Robert LabTeam Posted July 6, 2018 Share Posted July 6, 2018 Hi guys, I am using bluetooth (AP6212) and it works pretty well. After several hour of open connection I lost signal and need to reconnect. But I can't. Bluetoothctl returns "No default controller available", however one minute before it worked I tried to restart bluetooth service, rfkill (soft and hardware does not lock anything) , but the problem still exist. Only reboot can back the module to work. Is there any other way to restart the module without reboot? Link to comment Share on other sites More sharing options...
arox Posted July 7, 2018 Share Posted July 7, 2018 try : hciconfig hci0 up hcitool dev or hciconfig hci0 reset hciconfig hci0 up hcitool dev or ps -ef | grep hciattach if not present, respawn hciattach process (check command line after boot) then re-up hci0 there should be a gpio for hard reset but it depends on uboot, DT and kernel version ... How to restart bluetoothd depends on system and version. You may need to re-up hci0 after restarting bluetoothd and handle hciattach yourself before starting bluetoothd : because it is hardware dependant, it is always a dirty tweak in startup scripts ... You should provide some information about SBC, ap6212 rev, Armbian version, Bluez version, firmware version (downloaded by hciattach) ... So somebody may perhaps help ... Link to comment Share on other sites More sharing options...
Recommended Posts