Now, does it not work for me because the *.hcd needs to go to a different location (as everything else is *.bin) in addition to this location? Could it be the naming of the hcd file? Is there some command to force load the *.hcd file into the kernel? do I need to remove some other piece of software? Can I load the driver I created using 'System Settings' > 'Software and Updates' > drivers tab? The image below shows the final step of the solution to the post I linked to. I followed this instruction manual to the T! The only problem is that it didn't work for me. Have a look: Bluetooth Broadcom 43142 isn't working That out of very many posts with similar unanswered issues, there is a gem which explains how to fix this issue. I have spent over 8 hours looking through posts on this issue, and I can say Image #3 - when I run dmesg | grep -i blue the result is as follows (confirms the issue is a firmware problem): Image #2 - Core of problem, no option to output sound to connected Bluetooth device: Image #1 - Bluetooth is connected to Bluetooth card in PC (screen shot is of 'blueman' software as suggested in Bluetooth won't find devices!): Basically I am not able to load the *.hcd file I made from a *.hex file into the kernel (my interpretation of this issue with my very limited understanding). The problem is that the O/S does not provide an option to send audio output to the Bluetooth controller - this is a Bluetooth controller firmware issue. I am able to establish a connection between a Bluetooth ear-piece and the Bluetooth controller in the PC.

Broadcom bcm20702 driver