@Andriopoulos: I have some questions to the log file you attached: * Did you power off Bluetooth at some point through the UI? * You say "calls" but I only see one call being made in that log file. Can you please describe the exact steps you performed after you powered on your phone? * What is the exact model of the Car you're using?
>From the log you attached it looks like the HCI controller signals us that the Bluetooth device wents down so bluez is just reacting on incoming events and brings everything else also down: Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_added() /ril_1/voicecall01 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() /ril_1/voicecall01 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() state dialing Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() cli 6944***** (number removed) Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() Multipary False Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_new() CALL_STATUS_DIALING Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator "callsetup" 0->2 Jul 31 19:39:02 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength Jul 31 19:39:10 ubuntu-phablet bluetoothd[854]: message repeated 2 times: [ audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength] Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() path /ril_1/voicecall01 Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() property State Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() State alerting Jul 31 19:39:11 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator "callsetup" 2->3 Jul 31 19:39:12 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength Jul 31 19:39:17 ubuntu-phablet bluetoothd[854]: message repeated 2 times: [ audio/telephony.c:handle_network_property_changed() in handle_registration_property_changed(), the property is Strength] Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() path /ril_1/voicecall01 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() property State Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:handle_vc_property_changed() State disconnected Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_free() /ril_1/voicecall01 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.h:telephony_update_indicator() Telephony indicator "callsetup" 3->0 Jul 31 19:39:19 ubuntu-phablet bluetoothd[854]: audio/telephony.c:call_removed() /ril_1/voicecall01 [...] Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_event() cond 1 Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_event() Received 10 bytes from management socket Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: plugins/mgmtops.c:mgmt_new_settings() hci0 new settings Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: src/adapter.c:adapter_remove_connection() Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/manager.c:state_changed() /org/bluez/854/hci0 powered off Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/telephony.c:telephony_exit() Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/telephony.c:modem_removed() /ril_1 Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: audio/headset.c:telephony_deinit() Telephony deinitialized Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: Adapter /org/bluez/854/hci0 has been disabled Jul 31 19:39:29 ubuntu-phablet bluetoothd[854]: src/adapter.c:set_mode_complete() This pretty much looks to me like problems in the lower communication layers (HCI, ..) and need more investigation. -- 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
