Confirming this also happens on my Honda Civic.
--
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/1447761
Title:
Car bluetooth shows no signal
Status in bluez package in Ubuntu:
Confirming this on another car (2015 Honda Civic).
However, in my case, I can play audio, and the phone's speakers are used.
Changing songs with the car's audio controls doesn't work either.
What logs can I post to help solve this?
--
You received this bug notification because you are a member
Forgot to mention - phone is a BQ Aquaris E4.5 (Krillin) running Vivid
r26.
--
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/1409047
Title:
Bluetooth audio not working with Volvo
I didn't get to try the silo.
After your comment, I found this very strange and took a better look:
Before, I used to wait for the car to find the phone, and after being
found the car requested me to enter in the phone for pairing (which
failed immediately).
What is occurring now, is that
Ok, I can confirm that I am unable to pair the phone with that car's bluetooth
system if I have the car's system try to find and pair with the phone.
However, if I let the phone try to find the car's system, pairing works without
issue.
I will retest using 'bluetoothctl' just to make sure I
Did this fix land in OTA11?
Because I can now pair the car's bluetooth system with the phone without any
issues.
--
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/1539158
Title:
Unable to
@Marco Graziotti:
The syslog is nothing special. You can find it in "/var/log/syslog".
There is also this:
https://wiki.ubuntu.com/DebuggingBluetooth
I recently found that documentation, and I am planning on getting that info out
here. But sofar I haven't had the chance to try it.
It will
@Marco
Woha, I actually asked the askubuntu referenced question. Talk about full
circle.
Anyway, I have gotten my system on rw mode, using "sudo mount -o remount,rw /".
I did this to insert a new ringtone on my phone (which can now be done via the
GUI without changing the image to rw mode).
In
Attached is the syslog from my Krillin device from a few minutes before
attempting the pairing until failure.
I hope this may help speed things up.
I'm willing to test new stuff to help fix this issue.
** Attachment added: "syslog (trimmed to the last few minutes before pairing)"
Public bug reported:
After OTA-9 I started having trouble with my bluetooth connection to the car
hands-free system (no sound, and incoming calls no longer displayed the
number), so I have reset both the car and the phone connections (eg. forgot the
devices).
Now I can't even pair the phone
Could be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1435040
But it might not be, since my issue only started with OTA-9.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
This has started to happen to me after OTA-9.
Phone: BQ Aquaris e4.5
Car: 2015 Honda Civic Tourer
I had reported
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158
but it might be a duplicate...
--
You received this bug notification because you are a member of Kernel
Packages, which
@MarcoGraziotti:
Could you connect before OTA9?
--
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/1539158
Title:
Unable to pair with in-car hands-free system after OTA-9 update
Status in
Ok, I think I stripped any sensitive information from that log.
I hope it contains what you need.
Let me know if you require anything else (including potential solutions for
testing).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
Sorry about the spam. I forgot the attachment.
** Attachment added: "Syslog with verbose bluetooth"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158/+attachment/4579464/+files/syslog_stripped.tar.xz
--
You received this bug notification because you are a member of Kernel
Ok, I have generated a verbose bluetooth log.
However, this log contains some personal information, that I would prefer not
to make public (email address, partial wifi credentials, etc). How can I make
it avaialable to devs in a more private way?
Here is what I did:
Make "/" rw
Edit
Humm... I guess I'll have to read a bit on how to do the reflashes.
Worst case scenario I'll have to wait until OTA10, which should be released
somewhere in April IIRC.
I will report back if I make some progress on this front (hopefully with enough
time before OTA10 lands for any further
@Marco:
Just "press" "Enter" and the file should be saved. Don't worry about that
message. Nano always asks that question before saving a file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Marco
Sorry, I cannot reproduce that. In both my desktop and my phone, pressing
"Enter" on the save dialog will result in saving the file...
You may wish to try "Ctrl+X" instead of "Ctrl+O", to try to work around the
problem, but I'm not sure it will achieve anything...
--
You received this
@Simon
Thanks!
Just to make sure: in order to try this, all I have to do is add the PPA to
sources.list and install it using apt-get?
Or is there more to this, such as re-flashing the device with some daily build
image?
If procedures other than adding the PPA are required, would you please point
Problem persists after updating to OTA10.
The symptoms appear to be the same.
I will enable verbose logging again and report back.
This time I will most certainly try any silos you may provide as I have already
learned a bit more abut the system.
--
You received this bug notification because
Fix Released - Is there some silo I can try to test this?
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/1539158
Title:
Unable to pair with in-car hands-free system after OTA-9
That's great news!
I'll try it again tomorrow morning and report back.
--
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/1539158
Title:
Unable to pair with in-car hands-free system after
Attaching a stripped syslog, using the same procedure as done in comment #14.
I hope it contains the required information.
Upon a quick uninformed look, the error seems to be the same as before, but I
may well be missing something.
** Attachment added: "Syslog with verbose bluetooth"
I can confirm that it is not working for me either.
However, there is a small difference from the previous tries:
Now the car system asks for the pin code, and it takes 4-5 seconds before
failing, whereas previously it instantly failed.
I will report back later with the debug log.
--
You
Sorry about the delay. I'll try this ASAP, which is likely before the weekend.
I'll report back with results soon.
--
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/1539158
Title:
Unable
Ok, so I think I'm ready to test that silo.
Are these instructions up-to-date, (especially the recovery process)?
https://wiki.ubuntu.com/LandingTeam/SiloTestingGuidelines
Or should I get them from somewhere else?
--
You received this bug notification because you are a member of Kernel
Sorry about the noise, but is there any further info I can provide, or patches
I can try?
This is a critical functionality for me.
--
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/1539158
@Konrad
Great idea.
Ok, so I went here[1] to get info on running "bluetoothctl" and pairing a
device via this interface.
Here's the result:
Pairing works via "bluetoothctl". I did not have to enter a PIN code as before
and as mentioned in the car's instructions.
After pairing was working, I was
Public bug reported:
After working around bug
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1539158 I was able
to pair the phone (BQ Aquaris E4.5) with the car hands-free system.
However, thing don't quite work as expected.
I can use the car's system to place a call using the phone, but
I should also add that *before* OTA9 the entire system worked
flawlessly, so this is likely related to the update to Bluez5.
--
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/1578176
Title:
Public bug reported:
When the phone is connected to the in-car hands free bluetooth system and I
receive a call, I expect the caller ID to be displayed in the car's
infotainment system. This was working until OTA9, which has made the system
display "Unknown" when receiving a call.
I can use
You are welcome. Let me know if you need me to test something else.
I have also opened 2 new tickets for the 2 "downstream" reported issues:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
--
You received this bug
I cannot seem to find the log you requested anywhere.
I found similar files under ~/.cache, but they seemed to be specific logs (for
system updates, for example), not a generic one like the mentioned ones. Wiki
pages also refer the file location you mentioned, but it does not seem to exist
, network bridging and cups left to configure) and I'll get to
the silo afterwards. Thanks for your work and I'll be back on testing ASAP.
Francisco
On 10-05-2016 07:22, Konrad Zapałowicz wrote:
> @Stunts
>
> I wonder if you had time and chance to test the possible fix. Let me
>
I am attaching the log with OTA10.1.
As far as I can tell, the error is still the same. But all the experience I
have with debugging bluetooth errors is what you see in this bug report.
** Attachment added: "Syslog with verbose bluetooth after OTA10.1"
I don't think it's a dupe.
This issue tracks the problem with reading the phone number and name from the
phone, bug #1578176 is about the audio during the calls.
Yes, both bugs are probably related, but I don't think they are dupes.
--
You received this bug notification because you are a member
Hi Konrad,
OTA13 freeze is tomorrow. Is the fix from silo 46 landing there? The latest
upstream Bluez is mentioned in the landings email, but I didn't see any
references to this issue (but I could have missed it in a previous email).
Thanks.
--
You received this bug notification because you
This was solved for me with OTA10. Has been working fine ever since.
So I guess this is a "Works for me" post.
--
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/1409047
Title:
Bluetooth
@mike-jelfs:
Please check if this bug also applies in your case:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
--
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/1578176
@higuita:
These are being tracked in these bugs:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578176
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1578178
Is it the same issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thank you Konrad!
Eagerly waiting for OTA13.
--
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/1539158
Title:
Unable to pair with in-car hands-free system after OTA-9 update
Status in
@Marco and @Cesar:
Were you able to pair the phone with the car's HFS before OTA9?
If that is not the case, you may wish to track bug #1435040 (if you are not
tracking it already).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
YES! Confirming that OTA13 has solved the pairing issue. I can now pair
my BQ Aquaris E4.5 with the HFS without any problems.
Furthermore - once pairing is done, I get the "volume" notification with the
title: "Bluetooth speakers" and I can play music via the car's speakers (albeit
I can't
@monserwade:
You may be interested in bug #1578176. It's kind of like the follow up to this
one:
Pairing works as intended, connection is performed, contacts also work, but
calls don't.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Just adding that after OTA13 the issue remains.
--
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/1578176
Title:
Cannot place or recieve calls when using in-car bluetooth system
Status in
Would it be interesting for debugging to have a verbose bluetooth log depicting
the behaviour highlighted by @fvkigg ?
I can obtain that if there is a chance it can help solve the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This looks a lot like bug #1546310
But in that case, there seems to be a fix released (OTA10 I assume). Just
thought it could be interesting to have it linked here for reference.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
Ok, so it turns out I'm still having some issues with this after OTA-14.
I can still pair the phone with the Hands Free System (HFS), but...
I can only do this if I make the phone search for the HFS. If I try the pairing
by having the HFS search for the phone, I get an error - the PIN (hardcoded
Issue remains after OTA 14.
I have attached a syslog with verbose bluetooth and pulseaudio logs.
The log is trimmed to the reboot just before trying to place a call.
To further help, the device that fails to show audio name is "Honda HFT". I
have attempted two calls, both failed to route the
50 matches
Mail list logo
