Unfortunately, the solutions suggested previously on message #4 and #6 don’t work. I’ve tried to do an hex2hcd of the .hex file used by my windows, then put it in /lib/firmware with the good name and it didn‘t work at all, bluetooth is still unusable.
For the solution proposed in #6, I don’t really understand how to rename the .hcd, if the name matters, I might have done an error, but if not, it simply doesn’t seem to work. The solution that looked the most promising was to use ndiswrapper on the windows driver, device seems to be recognized, but still not working unfortunately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366418 Title: Bluetooth BCM43142A0 doesn’t work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1366418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
