Ubuntu Touch is no longer supported.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Won't Fix
--
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
https://wiki.ubuntu.com/Bugs/Importance
** Changed in: pulseaudio (Ubuntu)
Importance: Critical => High
--
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
** Tags added: pulse-touch
--
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
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.
Hello,
Is there any update this bug?
I have an Aquaris 4.5 on OTA-15 and I am still having that same issue
with my new Pioneer car audo. Can pick up calls but sound is not routed
through car speakers and car microphone does not seem to record sound.
I had the same issue with an Alpine care
I too have just brought a Pro 5 and have hissing over car phone
Bluetooth, seemingly the mx4 does not have this issue.
Playing music through Bluetooth speaker bar there is no issues, just
with calls.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Same problem with Meizu Pro 5 (OTA-11) and bluetooth headset Samsung
HM1500
--
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
I have a similar problem on Meizu Pro 5 Ubuntu edition (Factory installed).
OS - Ubuntu 15.04 (OTA-10.2)
I have a "Ford B-MAX" (built in 2013) with factory built-in "SYNC" hands-free.
Phone properly paired, properly synchronize phonebook. I can dial a phone
number and I can answer on call using
Please open a new bug (actually two, since you appear to wish to report two
problems). Both appear to be different to the original reported here.
Bugs are not discussions for lots of problems. One concrete problem per
bug, and we duplicate those which have the same underlying fix required.
--
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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
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
** Tags added: bluetooth-ota10
--
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
@Matthias: Yes lets take the disconnection as separate bug so that we
can close this one. The bug you've tested now landed in rc-proposed and
will be part of OTA10.
That the connection times out smells really like a different problem so
another bug is the right way. Can you attach the log files
@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:
@Matthias: Yes let take #1500242 separately to not confuse things.
Sounds good that this seems to be an improvement for you. However lets
monitor this for a bit as it could be a thing which only happens after
some (however in your logs I never saw it detecting the sink.fake.sco
sink from pulse
@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:
@Uranicus
Yes, citrain device-upgrade is the command you should run.
The 'pin' in this case is the code that you use to unlock the screen
which also happens to be a user password. The citrain needs it for sudo.
The 'silo' is 47 for this fix.
Best,
Konrad
--
You received this bug notification
@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:
Ok, pushed a "possible" fix to silo 47.
@Matthias: Can you try if the problem goes away after installing silo
47?
--
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
I got this down to pulseaudio not being able to find the sink.fake.sco
sink element we have in place to do the suspend/resume handling of the
SCO stream. Trying some small tweaks to see if they bring the same
effect here. If they do I will push those changes to silo 47 to see if
that helps to fix
I went through the logs now and found the cause for what you see (no
audio on local or remote side).
We have lock in place which should keep the stream inside pulseaudio up
while we're not really streaming anything through it as this completely
done in software. However in your case the lock
There was a bug in pulseaudio which was brought in while we added
support for Android 5.x. This is only valid for current rc-proposed. A
fix is available in silo 47 (see https://requests.ci-
train.ubuntu.com/#/ticket/1059 for details). If you want to help
verifying the fix feel free to install the
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
Can confirm.
I have the same problem since OTA9.
Worked fine with OTA8.
I am using a Parrothands-free kit in my car.
--
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
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
I have a Citroen C4
When I try to pair the phone the car says that is not compatible.
I think there is a problem in my car but in the past I was able to pair them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
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
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
** Tags added: bluetooth
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Milestone: None => ww08-2016
** Changed in:
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
** Also affects: canonical-devices-system-image
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/1546310
Title:
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
32 matches
Mail list logo
