[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Will someone pick this issue up? Or are you dropping this bug because there will be a re-write of the bluetooth framework for the snappy image later on? Please let us know a bit of what is going on. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
Hi Thomas, I raised this bug and I am still affected by the bug (e.g. with the Audi A3). Due to the switch to the snap based OS I do not expect to see any progress in the coming months for our phones (being a Aquaris e4.5 user). I think the expectation is that our phones only get security fixes. I nevertheless hope heavily that the devs are considering these issues with bluetooth, which have been encountered in the last years and find a solution for the future. It seems that this issue (bluetooth with cars, headsets, speakers, ...) is not as simple as implementing bluez 5.xx and that's it. Nevertheless the "alternative OS" developers find their solutions to this issue so I hope the Ubuntu team can do it alike. I am not a dev, just a user. So we can raise the awareness that this is still requested and work on this subject highly appreciated. Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
@Simon I wanted to give you a feedback on my testings. I am now on: current build number: 275 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-08 06:14:58 version version: 275 version ubuntu: 20160308 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid still with the silo installation I did on 2016-03-02 (so I have gradually updated my rc-proposed without having re-installed silo47 (I hope this is as you have expected it). I had no issues with my bluetooth until this morning (2016-03-09, approx. 8:26 h CET). This issue might have something to do with the changes coming from silo47 or are just bad luck ... I was in a longer telephone call. All of a sudden the bluetooth connection got interrupted. Looking at the logs I found around that time the following log statement from bluetooth: Mar 9 08:26:31 ubuntu-phablet bluetoothd[899]: Start: Connection timed out (110) The call itself still was active just the phone disconnected from my car. Has this something to do with your modification or is this a different / new bug? Logs are attached. Matthias ** Attachment added: "20160309_0847.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+attachment/4594256/+files/20160309_0847.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
Simon, thanks for the feedback. I have logged the new finding as bug: 1555608 (you have seen this already). Thanks for updating rc-proposed with the solution for bug: 1546310 Do I need to do something special with my rc-proposed, since I have installed silo47? Or will the next update correct all of that automatically? Regards, Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Hi Konrad, thanks for working on this issue! I am on the following version: current build number: 286 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-18 08:33:28 version version: 286 version ubuntu: 20160318 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid I have checked with above command that bluez 5.37 is installed. I have checked if the Jabra 250 works before installing silo 67 and I experienced the same behaviour as before: directly after the pairing process it works as expected and as soon as I shut off the bluetooth device and reconnect this connection does not work. I then followed step 2. I have installed silo 67. Just to cross check: I got from the terminal the information that the following parts will be updated: The following NEW packages will be installed: libgeonames0 The following packages will be upgraded: libsystemsettings1 ubuntu-system-settings 2 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,240 kB of archives. After this operation, 517 kB of additional disk space will be used. Get:1 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ vivid/main libgeonames0 armhf 0.1+15.04.20160315-0ubuntu1 [352 kB] Get:2 http://ppa.launchpad.net/ci-train-ppa-service/landing-067/ubuntu/ vivid/main ubuntu-system-settings armhf 0.3+15.04.20160318-0ubuntu1 [880 kB] Get:3 http://ppa.launchpad.net/ci-train-ppa-service/landing-067/ubuntu/ vivid/main libsystemsettings1 armhf 0.3+15.04.20160318-0ubuntu1 [8,114 B] Is this as you have expected? I then tried to reconnect the Audi A3. It did not work. But I got a bit further than during my last attempts. The phone seemed to be able to extablish a connection (but the car did not verify this connection, it just said in the IN CAR display: "please wait ...". I was able to start a command line while the phone was connected to start bluetoothctl: [Audi UHV 4272]# info Device 00:0E:9F:E8:3A:24 Name: Audi UHV 4272 Alias: Audi UHV 4272 Class: 0x200408 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no But finally I had to give up after several connections and disconnections. Log files are attached. Best success in finding the root cause! If I can help furhter, please let me know! ** Attachment added: "20160318_2146.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4603727/+files/20160318_2146.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Konrad I will run the following on my phone: sudo rm /var/lib/bluetooth/* -rf This should empty the directory as you have indicated. Then I will reconnect to Seat & Audi. One question: do you want me to reinstall silo 67? I am on: current build number: 298 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-30 06:12:51 version version: 298 version ubuntu: 20160330 version device: 20160323-1467d3c version custom: 20160324--36-54-vivid and I have not re-flashed my device since I have installed silo 67. So do you think I can just give it a go as it is? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Konrad I hope I did what you have expected: at first I tried to forget the device (Seat_BT, 4C:74:03:64:75:ED). But even after that and after a reboot I could find a directory with the address of the device in (var/lib/bluetooth/4C:74:03:64:75:ED). In a second step I deleted the content of the bluetooth directory with: sudo rm /var/lib/bluetooth/* -rf The directory was then empty - as expected. In a second step I reconnected my Seat_BT with the phone. It worked again as it should. If you are looking at the logs it was at 30.03.2016 at approx 18:08 h CET. (You can also find the same attempts earlier). I can do calls, listen to music, etc. I then also tested the Audi (30.03.2016 20:45 h CET). For this test I have not deleted the profile of the Seat_BT - should I?? During the attempt to connect to the Audi I still have the same issue as before: The phone finds the Audi as "Audi UHV 4272". The phone asks for the pairing key (1234). This is the correct key since another phone can be connected to the Audi with this pairing key. It creates an entry in the list of devices in system-settings, bluetooth menu. But in var/lib/bluetooth/ no additional directory has been added. But the car itself never recognizes that a phone is connected to the car. Approx. 30 seconds after the connection it (phone or car? I do not know) disconnects again. Waiting for approx. 30 - 60 sec. repeats this action (connect, after approx. 30 seconds disconnect). I have attached the logs again. I will "loose" my test candidate (the Seat_BT) tomorrow since I have to hand in the car again. So for the Seat device I can not do any more testing. I will keep the Audi and the Jabra250! The ones that do not work with my phone :-(( ... ;-) .. Matthias ** Attachment added: "20160330_2052.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4617439/+files/20160330_2052.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
I have also attached a screenshot of the bluetoothctl output (of the results from 17:54 h - 17:58 h) where you see that the device connects and disconnects. ** Attachment added: "screenshot20160331_175905629.png" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4618465/+files/screenshot20160331_175905629.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Konrad I have now isolated as requested the Audi only. Please check the logs from 31.03.2016 17:45 h CET onwards. If you need anything else, please let me know, I am happy to support! ** Attachment added: "20160331_1800.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4618464/+files/20160331_1800.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] [NEW] In CAR bluetooth not working
Public bug reported: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20160216_2054.tar.gz" https://bugs.launchpad.net/bugs/1546310/+attachment/4573090/+files/20160216_2054.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in bluez package in Ubuntu: New Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
By the way, if someone wants to check when I had the issues and on which time zone I am: I am on CET. I had this issues with phone calls at: 20:35 h 20:38 h 20:39 h 20:44 h Uranicus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in bluez package in Ubuntu: New Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
I have a new insight on the bug. I experienced today the following: The call (to be a bit more precise: the connection between my phone and the number I have dialed) is established. The sound of the call is not routed via the loudspeaker of the car. I can hear the voice only if I choose internal loudspeaker of the phone or the normal ear loudspeaker of the phone (via the menu of the phone while the call is in progress). But the bluetooth loudspeaker does not get the sound (and I believe that also the microphone of the car is not in use). I still need to test if music can be played via bluetooth to the loudspeaker of the car (I expect not but will report later on that). Uranicus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
Dear all, I have an update on this issue. I am now on: device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-18 06:52:03 version version: 262 version ubuntu: 20160218 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid Same issue as before but a bit more precise: - I want to place a call via my car bluetooth set (Seat Alhambra), I get not output to the loudspeakers - I can activate the phone loudspeaker and then also the microphone (of the phone) works NEW: - listening to music (music app, podbird, uradio, ) WORKS! I can listen to music via bluetooth! I have the updated logs of today attached. Uranicus ** Attachment added: "20160218_1606.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1546310/+attachment/4574572/+files/20160218_1606.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
Dear all, comment #7 (and most likely comment #6) do not relate to the issue I am reporting here. I was on OTA9 AND IT WORKED (see bug report). I have verified it today where I went back to OTA9 and tried it again. I was able to call from the car and to hear the counterpart via my car loudspeakers. As it should be. Just for completion I will add the syslog of this morning to the reporting. My report wants to say: between OTA9 and the current rc-proposed a negative change appeared in the bluetooth implementation. Uranicus ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1546310/+attachment/4576532/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Simon Thanks for picking this up again. Topic 1. Audio A3: I will test this this evening or tomorrow and will give you a feedback. I am very sure that the pin I have entered was correct but I will check this again. Topic 3. Logitec Bluetooth Mouse For both channels (OTA9.1 & rc-proposed (current: 270)) I can now connect the mouse. Output during pairing is: [NEW] Device 00:80:00:00:15:76 Bluetooth Mouse [CHG] Controller 4C:74:03:64:75:ED Discoverable: no [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes [CHG] Device 00:80:00:00:15:76 RSSI: -33 [CHG] Device 00:80:00:00:15:76 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Device 00:80:00:00:15:76 Connected: yes [CHG] Device 00:80:00:00:15:76 Modalias: usb:v099Ap0500d011B [CHG] Device 00:80:00:00:15:76 UUIDs: 1124--1000-8000-00805f9b34fb [CHG] Device 00:80:00:00:15:76 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 00:80:00:00:15:76 Paired: yes [CHG] Device 00:80:00:00:15:76 Trusted: yes I was mistaken myself and therefore also my writing in the past: this in NOT a Logitech mouse. It is LogiLink (looks like Logitech, ...) and the packaging simply states: ID0078. Do you need any more information for topic 2. Jabra headset? Thanks for the work, Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
Dear all, I have a new insight which might correlate to this bug or contribute to the understanding. Maybe first of all, I just tested the above scenario with: current build number: 270 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-01 15:29:28 version version: 270 version ubuntu: 20160301 version device: 20160108-efc96d8 version custom: 20160111-926-36—vivid this issue is still the same. But I haven't expected it differently since you seemed to be busy with other stuff. Now the new insight: - I have had a similar issue with OTA9.1 but only in the following circumstance: I start to call (and I establish this call fully) before I start the bluetooth of my car. I have expected that the bluetooth of the car picks this call up and I can continue with it via my car microphone & speaker. But I ended with the same behaviour as described above (but only in this circumstance with OTA9.1!): I can not hear anything via my car speakers only if I turn on the phone speaker (inner & outer speaker) I could hear it via these speakers. I you want to have a look at these logs: start of the call: 26.02.2016 at 18:38 h CET start of the in car bluetooth system: approx. 18:42 h I have verified this on later occasions again, this is a reproducible situation for my phone/car/bluetooth combination. ** Attachment added: "20160226_2117.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+attachment/4585578/+files/20160226_2117.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Simon Now the promised update to topic 1. Audio A3: I have used the correct PIN: 1234. I have tested this with another Android phone which I have paired with the car using this PIN. Then I retried the pairing with my Ubuntu Phone with the same result as above. I started this at: 01.03.2016, 21:20 h CET I have updated the log files with todays result of the pairing test using the following OS version: current build number: 30 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2016-03-01 16:16:34 version version: 30 version ubuntu: 20160217.1 version tag: OTA-9.1 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid If you need anything else, please let me know, Matthias ** Attachment added: "20160301_2127.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+attachment/4585892/+files/20160301_2127.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
@Simon Thanks for the fix. I am happy to test it! Can you please give me a hand what I need to do to install silo47? If I am on rc-proposed do I just need to run: citrain device-upgrade 47 I read for another silo that the command is: citrain device-upgrade 0 (What does mean? I found this at: https://wiki.ubuntu.com/Touch/DisplayCasting) Does this influence any further updates? Thnaks for your support, Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1546310] Re: In CAR bluetooth not working
@Simon, @Konrad, I have tested it with the following configuration: current build number: 271 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-02 13:27:37 version version: 271 version ubuntu: 20160302 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid I have added silo47 to this configuration. I have then tested the issue with my Seat as described above and it works. At least with the standard test case I have always used. I will monitor this of cause in the coming days. My logs are attached. Just for information: the issues around bug: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242 are still there. You can see the reaction of the phone regarding the other two bluetooth devices (Jabra, Audi) also in the logs. Shall I post this additionally in bug 1500242? Matthias ** Attachment added: "20160302_1401.tar.gz" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+attachment/4586545/+files/20160302_1401.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Dear all, in case there is something new on rc-proposed please let me know. I will then test it according to my procedure above and will give you a feedback, merry Christmas and a happy new year, Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Is there something I can do to push this over the finish line before OTA9 freeze? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
@Tony Today I was able to monitor and track the issues with the battery indicator of my car. I am on: current build number: 242 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-26 07:13:53 version version: 242 version ubuntu: 20160126 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid This evening I had once a correct battery indication of my in car display (Seat Alhambra 2013 model). Then after a restart of the car I had again a full battery (eventhough the battery was <50%). Then I restarted the car several times without success. I have also turned off / on bluetooth without success. Only a restart of the phone led to the result that the battery index showed again the correct result. In the syslog I have: Jan 26 18:53:39 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,2\r\n\r\nOK\r\n Jan 26 20:31:46 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n Jan 26 20:33:44 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n Jan 26 20:34:59 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,2,0,5\r\n\r\nOK\r\n Jan 26 20:36:02 ubuntu-phablet ofonod[2006]: Server: > \r\n+CIND: 1,0,0,0,3,0,5\r\n\r\nOK\r\n Jan 26 20:38:13 ubuntu-phablet ofonod[1992]: Server: > \r\n+CIND: 1,0,0,0,5,0,2\r\n\r\nOK\r\n where "2" is the correct battery index. I have restarted the phone between 20:36 h and 20:38 h (indicator switches from 5 -> 2). Between the reconnects on 20:31 h, ... 20:36 h I have stopped and restarted the car (pulled the key and waited for some seconds) and once turned off / on bluetooth via GUI of system settings. I have attached the log files for your information to trace down this issue. Matthias / Uranicus ** Attachment added: "20160126_2052.tar.gz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479438/+attachment/4557056/+files/20160126_2052.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ofono package in Ubuntu RTM: Fix Released Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Do you need any additional input from me? I have changed my phone to OTA-9 (stable channel) today and I have experienced the same issue there. Please let me know if you need something to be tested in this area. Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Best success! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Status in ofono package in Ubuntu: Confirmed Status in ofono package in Ubuntu RTM: Confirmed Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493386] Re: IN CAR: SIM2 calls cann not be routed via car audio
Are there any news on this bug? How about the implementation progress on supporting 2 SIM cards used with bluetooth? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: In Progress Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
Attachement to my report. ** Attachment added: "20160106_2155.7z" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479438/+attachment/4545171/+files/20160106_2155.7z -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ofono package in Ubuntu RTM: Fix Released Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479438] Re: IN CAR: Battery levels not shared via bluetooth for in car experience
I have an interesting finding about the battery status in the car. I am on: current build number: 222 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-06 19:35:20 version version: 222 version ubuntu: 20160106 version device: 20151216-378d4f3 version custom: 2015--36-46-vivid In this rc-proposed version and also the version before (January, 5th) I have once the real battery status of the phone shown in the car and after a restart of the car (not the phone) I have the indication of a full battery level. I have two SIM cards in my phone but the second SIM card is locked (I have not entered the PIN code). I have attached sys.log and dbus.log of today. I have changed to the lastest rc-proposed today at 19:35 h ish and after this there was the occasion that the real battery status was shown in the car and after I re-started the car again (after a short break) the display in the car showed a full battery level. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1479438 Title: IN CAR: Battery levels not shared via bluetooth for in car experience Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Fix Released Status in ofono package in Ubuntu: Fix Released Status in ofono package in Ubuntu RTM: Fix Released Bug description: STEPS: Requirements: DUT a car with bluetooth and phone connection kit (Skoda Superb 2013 in my instance) 1. Connect the DUT to the car 2. On the display panel the battery always shows full EXPECTED: I expect to see the actual level of the battery on the device ACTUAL: The display always shows the battery at 100% I assume the default if no info is available. VERSIONS: current build number: 71 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-28 18:01:08 version version: 71 version ubuntu: 20150728 version device: 20150709-8965e37 version custom: 20150716-819-8-42 MODIFICATIONS: Installation of silo19 for in car bt fix To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1479438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1533716] [NEW] Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system
Public bug reported: My system: current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 08:28:26 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Since several days (not weeks, so something has changed in the last couple days!) I have the following situation with my BQ 4.5 in my car. When I initiate a call from the IN CAR system (where my phone is connected to) I experience sometimes the normal behaviour that the call is directly established. Sometimes nothing happens. The call is not established and my in car system says that the attempt to carry out a call has failed (this message comes after approx. 15 seconds after initiation of the call). Then approx. 60 seconds after the initiation of the call the call is all of a sudden established (without any further interaction). I currently was not able to find a logic in this. Here my "log"-file of what I did today: - 13.01.2016 9:00 h call initiated from car, call directly established 9:03 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:06 h call initiated from car, call directly established 9:09 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:26 h New pairing between phone and car, retry 9:30 h call initiated from car, call directly established 9:33 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:36 h call initiated from car, call directly established 9:39 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:42 h call initiated from car, call directly established 9:45 h call initiated from car, call directly established (this time again via phone book) 9:48 h call initiated from car (via voice command), approx. 60 sec. delay between initiation and call being established 9:52 h call initiated from phone itself, call established and correctly routed via car speaker I have added the syslog, upstart-files to the bug report for further analysis. Uranicus ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20160113_1122.tar.gz" https://bugs.launchpad.net/bugs/1533716/+attachment/4549339/+files/20160113_1122.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1533716 Title: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system Status in bluez package in Ubuntu: New Bug description: My system: current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 08:28:26 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Since several days (not weeks, so something has changed in the last couple days!) I have the following situation with my BQ 4.5 in my car. When I initiate a call from the IN CAR system (where my phone is connected to) I experience sometimes the normal behaviour that the call is directly established. Sometimes nothing happens. The call is not established and my in car system says that the attempt to carry out a call has failed (this message comes after approx. 15 seconds after initiation of the call). Then approx. 60 seconds after the initiation of the call the call is all of a sudden established (without any further interaction). I currently was not able to find a logic in this. Here my "log"-file of what I did today: - 13.01.2016 9:00 h call initiated from car, call directly established 9:03 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:06 h call initiated from car, call directly established 9:09 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:26 h New pairing between phone and car, retry 9:30 h call initiated from car, call directly established 9:33 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:36 h call initiated from car, call directly established 9:39 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:42 h call initiated from car, call directly established 9:45 h call initiated from car, call directly established (this time again via phone book) 9:48 h call initiated from car (via voice command), approx. 60 sec. delay between initiation and call being established 9:52 h call initiated from phone itself, call established and correctly routed via car speaker I have adde
[Kernel-packages] [Bug 1533716] Re: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system
Dear all, I have tested it today several times on: current build number: 232 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-16 08:03:38 version version: 232 version ubuntu: 20160116 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid and it works great. Thanks to all developers for this great piece of work! Very well done, Uranicus -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1533716 Title: Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Fix Committed Status in bluez package in Ubuntu RTM: Invalid Status in ofono package in Ubuntu RTM: Fix Released Bug description: My system: current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 08:28:26 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Since several days (not weeks, so something has changed in the last couple days!) I have the following situation with my BQ 4.5 in my car. When I initiate a call from the IN CAR system (where my phone is connected to) I experience sometimes the normal behaviour that the call is directly established. Sometimes nothing happens. The call is not established and my in car system says that the attempt to carry out a call has failed (this message comes after approx. 15 seconds after initiation of the call). Then approx. 60 seconds after the initiation of the call the call is all of a sudden established (without any further interaction). I currently was not able to find a logic in this. Here my "log"-file of what I did today: - 13.01.2016 9:00 h call initiated from car, call directly established 9:03 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:06 h call initiated from car, call directly established 9:09 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:26 h New pairing between phone and car, retry 9:30 h call initiated from car, call directly established 9:33 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:36 h call initiated from car, call directly established 9:39 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established 9:42 h call initiated from car, call directly established 9:45 h call initiated from car, call directly established (this time again via phone book) 9:48 h call initiated from car (via voice command), approx. 60 sec. delay between initiation and call being established 9:52 h call initiated from phone itself, call established and correctly routed via car speaker I have added the syslog, upstart-files to the bug report for further analysis. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Dear Konrad, sorry for not replying so long With the current rc: current build number: 431 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-09-17 07:25:24 version version: 431 version ubuntu: 20160917 version device: 20160606-ab415b2 version custom: 20160831-991-38-18 the connection the the Audi A3 and Jabra does not work. I have attached a screen shot where I tried the connection manually with bluetoothctl. I have also attached my logs of that day. I hope this helps to get a bit deeper in this issue. Matthias ** Attachment added: "Bug Bluetooth Audi A3.tar.bz2" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4744533/+files/Bug%20Bluetooth%20Audi%20A3.tar.bz2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] [NEW] Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Public bug reported: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Simon, thanks for the answer. How can I find out if I am still on OTA5? I expect to be on OTA6 since I have applied all updates. What can I do more than: go to "Settings" select "Updates" an the phone tells me "Software is up-to-date" (I am using the German version of the phone, so my translation might be not exactly matching with the current English terms) Matthias -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1493386] [NEW] IN CAR: SIM2 calls cann not be routed via car audio
Public bug reported: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1493386] IN CAR: SIM2 calls cann not be routed via car audio
Thanks for the swift response, Matthias Am Dienstag, 8. September 2015 16:19:13 CEST schrieb Simon Fels: > This should be fixed as soon as we have landed bluez5. > > ** Tags added: after-bluez5 bluetooth > -- Mit Dekko von meinem BQ Aquaris 4.5 Ubuntu-Telefon gesendet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1493386 Title: IN CAR: SIM2 calls cann not be routed via car audio Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5 with 2 SIMs, 2nd phone, a car with blue tooth phone support (Seat Alhambra 2012 in my case) 1. Connect the Aquaris to the car (with two SIM cards, car kid shows the provider of the 2nd SIM card in the display) 2. From the second device call the number of SIM1 3. Phone & car sound rings and call can be taken 4. From the second device call the number of SIM2 5. Phone does ring but car kit not. 6. Call 2nd phone from Aquaris connected to the car with SIM1 (via the phone directly or using the car kit) 7. Normal behaviour with in car phone & audio system 8. Call 2nd phone from Aquaris connected to car with SIM2 (only possible dialling from the phone) 9. No sound on the phone, no microphone support EXPECTED: I expect that calls from SIM2 can be taken and performed as from SIM1 ACTUAL: SIM2 seems not to work when phone is connected to blue tooth of car whereby SIM1 works flawlessly VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Dear all, Audi A3, car kit: I have tested the rc-propsed version with my Car kit Audi A3 2012 model. There has been no significant change with this set-up. I can pair the phone with the car kit but can not establish a connection between the two. So there is not much to report here -- Jabra BT250: OLD PROCEDURE WHEN I FILED THE BUG (OTA-7) STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device NOW WITH rc-proposed (Ubuntu 15.04, r191, 30.11.2015) 3. Phone finds Jabra BT250 and DOES NOT ask for pairing code Jabra BT250 is connected and I can take a call with the headset and end a call with the headset. BUT: Once I have disconnected the headset (turned off the headset) and wanted to reconnect it again (automatic reconnection enabled in the phone), the device will not be reconnected again. Instead of the headset symbol it shows a loudspeaker symbol ...). I need to restart the phone and pair it again to use it propoerly (until I disconnect it again). --- Car kit of Seat Alhambra (2012 model) There were the following issues with the car kit: now solved: German Umlaut (ä, ö, ü) not correctly displayed in phone book now solved: battery indicator always showing full battery It works. First I came to a different conclusion because I expected a different behaviour. With 67% battery power (phone) the car kit showed a full battery (4/4 battery blockes). When I was travelling the last days I saw that: 40% battery power switches between 2/4 to 3/4 blocks of battery power in the display approx. 65% battery power switches between 3/4 to 4/4 blocks of battery power in the display So it works but the calibration between battery power phone vs. car should be improved. not solved yet: list with: incoming, missed, placed calls empty not tested yet: 2nd SIM (I currently do not have a 2nd SIM) - Bluetooth mouse After OTA-8 I wanted to test the convergence features with my BQ Aquaris 4.5. I bought a bluetooth mouse (Logitech, LogiLink ID0078). Nothing happend, eventhough I could pair the mouse (including the phone asking for a pairing code) I was not able to use the mouse. Now with r191 I was able to pair the mouse successfully (even several times, so this shows a different bahaviour than the Jabra device). --- Thanks for all the development work you put into this great product. I hope my feedback helps a bit -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
@Simon: I will retest with the debugging bluetooth tips. Abou the A3 issue. I wrote: - Audi A3, car kit: I have tested the rc-propsed version with my Car kit Audi A3 2012 model. There has been no significant change with this set-up. I can pair the phone with the car kit but can not establish a connection between the two. So there is not much to report here - So it is not yet fixed! I will roll back to rc-proposed and follow the above mentioned steps hopefully during the weekend. I hope to give you then a good feedback. @Tony & Simon: I did the test with the following rc-proposed version: current build number: 191 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-11-30 17:03:26 version version: 191 version ubuntu: 20151130 version device: 20151028-869191d version custom: 2015--36-46-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: New Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
First a feedback of the tests with the Jabra BT250 device. Please see my report and the logfiles in the attachment. I am also posting the plain text here which I have attached as pdf & odt-file. - Text Reporting on Bluetooth bug 1500242 System Information of the device Detailed image information of the system used for testing system-image-cli -i: current build number: 196 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-05 18:28:01 version version: 196 version ubuntu: 20151204.1 version device: 20151028-869191d version custom: 2015–36-46-vivid hciconfig -a hci0: Type: BR/EDR Bus: UART BD Address: 4C:74:03:64:75:ED ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING PSCAN RX bytes:1054 acl:0 sco:0 events:56 errors:0 TX bytes:3734 acl:0 sco:0 commands:56 errors:0 Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'Aquaris E4.5 Ubuntu Edition' Class: 0x5c0110 Service Classes: Rendering, Capturing, Object Transfer, Telephony Device Class: Computer, Handheld HCI Version: 4.0 (0x6) Revision: 0x0 LMP Version: 4.0 (0x6) Subversion: 0x0 Manufacturer: MediaTek, Inc. (70) bluetoothctl [NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default] [NEW] Device 90:03:B7:46:8E:E9 SEAT_BT [NEW] Device 00:80:00:00:15:76 Bluetooth Mouse [bluetooth]# show Controller 4C:74:03:64:75:ED Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x5c0110 Powered: yes Discoverable: no Pairable: yes UUIDs: Headset AG(1112--1000-8000-00805f9b34fb) Generic Attribute Profile (1801--1000-8000-00805f9b34fb) A/V Remote Control(110e--1000-8000-00805f9b34fb) SIM Access(112d--1000-8000-00805f9b34fb) Generic Access Profile(1800--1000-8000-00805f9b34fb) PnP Information (1200--1000-8000-00805f9b34fb) A/V Remote Control Target (110c--1000-8000-00805f9b34fb) Audio Source (110a--1000-8000-00805f9b34fb) Audio Sink(110b--1000-8000-00805f9b34fb) Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) Message Notification Se.. (1133--1000-8000-00805f9b34fb) Phonebook Access Server (112f--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0523 Discovering: no Modifications on the device (debugging information) sudo mount -o remount,rw / Since no bluetooth-override file was available I used: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I was not 100% sure about the ofono modifications: “Add '-d' to the exec line in /etc/init/ofono.override”. I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I tested this 2 times. 1. I have restarted the phone after these modifications (logfile start with 1_*). 2. I have not restarted the phone and carried out the tests directly thereafter (logfile start with 2_*). Issue with Jabra BT250 device I followed the connection & pairing process with [bluetooth]# devices and made two screen shots: [bluetooth]# devices Device 90:03:B7:46:8E:E9 SEAT_BT Device 00:80:00:00:15:76 Bluetooth Mouse I put the Jabra is search mode and the phone found the device: [bluetooth]# devices Device 90:03:B7:46:8E:E9 SEAT_BT Device 00:80:00:00:15:76 Bluetooth Mouse [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [NEW] Device 00:07:A4:00:A7:05 JABRA 250 [CHG] Device 00:07:A4:00:A7:05 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [CHG] Device 00:07:A4:00:A7:05 RSSI: -38 [CHG] Controller 4C:74:03:64:75:ED Discoverable: no [CHG] Device 00:07:A4:00:A7:05 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes The I pressed “connect” in the screen of the Jabra of the phone: [CHG] Device 00:07:A4:00:A7:05 Connected: yes [CHG] Device 00:07:A4:00:A7:05 UUIDs: 1108--1000-8000-00805f9b34fb [CHG] Device 00:07:A4:00:A7:05 UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 00:07:A4:00:A7:05 Paired: yes [CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 111e--1000-8000-00805f9b34fb [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 1108--1000-8000
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
One add-on to the Jabra device: I realized that I have missed to put the "bluetoothctl", "info" data in the report above (1). So I did the same procedure as above again today and acquired the info data. But I also managed to get the info data the second time after I have turned the Jabra off and back on again before it looses connection (2). The difference is that the "ConnectedProfiles:" section is empty: Information about the Jabra device directly after pairing before I have turned it off and on again: [JABRA 250]# info Device 00:07:A4:00:A7:05 Name: JABRA 250 Alias: JABRA 250 Class: 0x200404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes ConnectedProfiles: Headset (1108--1000-8000-00805f9b34fb) Handsfree (111e--1000-8000-00805f9b34fb) LegacyPairing: yes UUIDs: Headset (1108--1000-8000-00805f9b34fb) Handsfree (111e--1000-8000-00805f9b34fb) Information about the Jabra device after I have turned it off and on again (before it looses connection to the phone): [JABRA 250]# info Device 00:07:A4:00:A7:05 Name: JABRA 250 Alias: JABRA 250 Class: 0x20040c Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes ConnectedProfiles: None LegacyPairing: yes UUIDs: Headset (1108--1000-8000-00805f9b34fb) Handsfree (111e--1000-8000-00805f9b34fb) Hope this also helps in finding the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
ergh ..., sorry I missed that, please find attached ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4530801/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default
Knowing that this bug is in progress, I want to share an interesting finding (at least for me). I am on rc-proposed (with bluez5, see details below). When SIM 1 is (randomly picked) used, the battery status is shown in the car display. When SIM 2 is used, the battery status shows 100% loading. system-image-cli -i: current build number: 196 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-05 18:28:01 version version: 196 version ubuntu: 20151204.1 version device: 20151028-869191d version custom: 2015–36-46-vivid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1418040 Title: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Invalid Status in ofono package in Ubuntu: Triaged Status in telephony-service package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu RTM: Triaged Bug description: What happened Placed call from car over bluetooth Call was placed on my first SIM card, even though I selected my second SIM as default for calls What should have happened The call should have been placed on my second SIM ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20150124-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.15.1-0ubuntu4 Architecture: armhf Date: Wed Feb 4 14:25:44 2015 InstallationDate: Installed on 2015-02-02 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150202-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Reporting on Bluetooth bug 1500242 I have send such a report on December, 6th 2015 where I have tested the rc-proposed with my Jabra device. At that time the syslog-file was missing which I have added later. I found out later, that syslog is a rolling log, therefore maybe not all test logs are part of that syslog. I have taken the time today to retest all that with the following devices. I attach the log files: Audi A3 car kit (2012 model) Seat Alhambra car kit (2012 model) Jabra BT250 head set Logitech bluetooth mouse LogiLink ID0078 (Compatible to BT1.1/2.0/3.0+EDR) Before testing I deleted all existing pairings with the devices and started from scratch. System Information of the device Detailed image information of the system used for testing system-image-cli -i: current build number: 196 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-05 18:28:01 version version: 196 version ubuntu: 20151204.1 version device: 20151028-869191d version custom: 2015–36-46-vivid hciconfig -a hci0: Type: BR/EDR Bus: UART BD Address: 4C:74:03:64:75:ED ACL MTU: 1021:4 SCO MTU: 184:1 UP RUNNING RX bytes:8537 acl:181 sco:0 events:502 errors:0 TX bytes:221664 acl:460 sco:0 commands:72 errors:0 Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'Aquaris E4.5 Ubuntu Edition' Class: 0x7e0110 Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio, Telephony Device Class: Computer, Handheld HCI Version: 4.0 (0x6) Revision: 0x0 LMP Version: 4.0 (0x6) Subversion: 0x0 Manufacturer: MediaTek, Inc. (70) bluetoothctl [NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default] [bluetooth]# show Controller 4C:74:03:64:75:ED Name: Aquaris E4.5 Ubuntu Edition Alias: Aquaris E4.5 Ubuntu Edition Class: 0x7e0110 Powered: yes Discoverable: no Pairable: yes UUIDs: Headset AG(1112--1000-8000-00805f9b34fb) Generic Attribute Profile (1801--1000-8000-00805f9b34fb) A/V Remote Control(110e--1000-8000-00805f9b34fb) SIM Access(112d--1000-8000-00805f9b34fb) Generic Access Profile(1800--1000-8000-00805f9b34fb) PnP Information (1200--1000-8000-00805f9b34fb) A/V Remote Control Target (110c--1000-8000-00805f9b34fb) Handsfree (111e--1000-8000-00805f9b34fb) Audio Source (110a--1000-8000-00805f9b34fb) Dialup Networking (1103--1000-8000-00805f9b34fb) Audio Sink(110b--1000-8000-00805f9b34fb) Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) Message Notification Se.. (1133--1000-8000-00805f9b34fb) Phonebook Access Server (112f--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0523 Discovering: no Modifications on the device (debugging information) sudo mount -o remount,rw / Since no bluetooth-override file was available I used: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I was not 100% sure about the ofono modifications: “Add '-d' to the exec line in /etc/init/ofono.override”. I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap Audi A3 [bluetooth]# devices At this time devices shows no results (nothing paired yet). Audi A3 in search mode and the two found each other: [bluetooth]# devices [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [NEW] Device 00:0E:9F:E8:3A:24 Audi UHV 4272 [CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [CHG] Device 00:0E:9F:E8:3A:24 RSSI: -49 [CHG] Controller 4C:74:03:64:75:ED Discoverable: no Connect Audi A3 with the phone (manually press the connect button in the bluetooth menue): [bluetooth]# [CHG] Device 00:0E:9F:E8:3A:24 RSSI: -67 [bluetooth]# [CHG] Device 00:0E:9F:E8:3A:24 RSSI: -52 [CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Controller 4C:74:03:64:75:ED Discoverable: yes 8:58 h: Enter the pairing code 1234 (nothing happens) 9:00 h: Enter pairing code a second time [CHG] Device 00:0E:9F:E8:3A:24 RSSI is nil [CHG] Controller 4C:74:03:64:75:ED Discovering: no [CHG] Controller 4C:74:03:64:75:ED Discovering: yes [CHG] Device 00:0E:9F:E8:3
[Kernel-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
report in odt, pdf and log files ** Attachment added: "Bug 1500242 2015_12_09.7z" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4531794/+files/Bug%201500242%202015_12_09.7z -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Incomplete Status in ofono package in Ubuntu: Incomplete Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
