@Nephilim1973: No, we can't "learn" anything here from Android. We have a completely different bluetooth stack which you can't compare with the Android one. Config files in /etc/bluetooth/*.conf don't help. Those problems are at other layers.
> Why the BT handling is so different between Touch and Desktop ? There are quite a lot differences: * different BT chip * different UI handlers * newer kernel with updated Bluetooth stack We're currently working quite hard to update the bluetooth stack on Touch (which dates back to 2012) to a newer, more stable and reliable one. Can't give any timeline yet but it will happen soon. What I really need is a log of bluetoothd in debug mode. See https://wiki.ubuntu.com/DebuggingBluetooth for details. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
