Still the same in syslog. Can you verify all steps in
https://wiki.ubuntu.com/DebuggingBluetooth manually?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519594
Title:
No s
Thanks for the detailed syslog!
Can you run
$ sudo btmon -w test.snoop
then reproduce the bug (remove the mouse in settings first and then
reconnect/repair).
Afterwards send me the test.snoop by mail.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** Tags added: bluetooth-ota9 bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1520161
Title:
The sound of music is not heard by a BT headset,it still comes from
inte
This isn't bluetooth specific but should count for any keyboard being
connected somehow if its bluetooth or usb.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Can you describe a bit more in detail what happens after you've ended
the call? Is music played again or not? Is the music coming throught he
phone speaker or the HFP headset? ...
** Tags added: bluetooth-ota9 bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch
>From the last kernel log this looks like a bug which was recently fixed
upstream in the linux kernel.
See
-
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/net/bluetooth?id=75e34f5cf69bd731d3b7375a786d4a15494fb8c6
-
https://git.kernel.org/cgit/linux/kernel/git/
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Thanks. That issue is known and nothing related to bluetooth or bluez
itslef but more an issue with the general way of how we do audio routing
and switching between different outputs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Also affects: telepathy-ofono (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in U
** Changed in: bluez (Ubuntu)
Status: Incomplete => Invalid
** Tags removed: bluetooth-ota9 bluez5
** Tags added: touch-audio-routing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launch
Can you please follow https://wiki.ubuntu.com/DebuggingBluetooth and
attach a syslog with debug output enabled? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1520161
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519809
Title:
No sound is routed to bluetooth headset after a
Added some debug statements to the arale kernel and now waiting for the
problem to reappear here to find out more details.
** Patch added: "0001-Add-STP-MT662x-wakelock-traces.patch"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4526227/+files/0001-Add-STP-
If somebody else wants to do this too the used boot.img for arale is
attached here.
** Attachment added: "boot.img"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1505241/+attachment/4526228/+files/boot.img
--
You received this bug notification because you are a member of Ubu
It would be awesome if you can follow
https://wiki.ubuntu.com/DebuggingBluetooth so that we get some more
debug information.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1520
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Changed in: bluez (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: bluez (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1519594
Title:
No sounds for ongoing call in both sides
Possible, but I am missing the syslog file here and without it its
pretty hard to say anything more and reproducing isn't even possible
too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1520584
Title:
[Meizu MX4] Sound shuttering using Bluetooth car connection
Status in bluez package in Ubuntu:
** Tags added: bluez5
** Tags added: bluetooth-ota9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1520584
Title:
[Meizu MX4] Sound shuttering using Bluetooth car connectio
There are two connections for HFP. One is the service level connection
which is used for exchanging AT commands which is setup all the device
the device is connected on HFP even if no call is active. This way we
also accept/decline calls. The second connection is the actual SCO
channel fo sending t
@Pat: No that is not a file descriptor leak. That is just an internal
handle not related to any file descriptors to store GATT related
attributes. This due to some unconverted profiles after
API/infrastructures changes and known upstream. Ignore that.
Also ignore that there is no bluetooth-touch-a
It would be awesome if you get the crash file from
/var/crash/_usr_lib_bluetooth_bluetoothd.0.crash and could send it to
me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1521
Examined the crash file I got from Pat:
#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
85 ../sysdeps/arm/armv6t2/strlen.S: No such file or directory.
(gdb) bt
#0 strlen () at ../sysdeps/arm/armv6t2/strlen.S:85
#1 0xb6f13ebc in avrcp_handle_media_player_list (session=0xb8f339c0,
se
Have a fix for the crash. Uploading a new bluez package to silo 9.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
Status in Canonical
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1521737
Title:
Cannot enable bluetooth
Status in Canonical Sy
** Tags added: bluetooth-ota9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1500242
Title:
Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected
with BQ Aq
@Tony: Can you have a look at the battery glitches?
** Also affects: ofono (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
I went through Pats log file and it looks basically like this: The
system doesn't go into sleep mode as their is still ongoing data flowing
over the transport to the BT/WiFi/GPS combo chip. If that is real or a
bug isn't clear yet. I am currently going through the responsible
driver and see how th
@Tony: Thanks!
@Uranicus:
A couple of questions:
- First: For all things please follow
https://wiki.ubuntu.com/DebuggingBluetooth so that we get some more
detailed logs of what is going on in your system. That would be great
and would allow us to debug this.
- When you disconnect your Jabra hea
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Also affects: pulseaudio (Ubuntu)
Impo
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Also affects: ofono (Ubuntu)
Impo
If you can it would be awesome if you can test this again with silo 9
being installed.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Also affects: canonical-devices-system
Ah sorry, confused that. The log files for the A3 would be great too
then.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad
@Uranicus: Awesome writeup! Thanks a lot. However the most important
thing is missing: A copy of /var/log/syslog which would be the primary
source of information for us to debug this. The others are only side
note information.
--
You received this bug notification because you are a member of Ubun
I looked through the code in the mx4 kernel now a bit more and the
reason for the hold wakelock is that there is simply data flowing. What
triggers the data flow or what data is actually flowing is not clear yet
but I don't see any HCI frames receiving on the bluetooth stack side so
far when this
@Pat: Does it print out something like:
Suspend blocking wakelocks:
None
Resume wakeup causes:
None
Suspend failure causes:
None
Suspends:
0 suspends aborted (0.00%).
0 suspends succeeded (0.00%).
total time: 0.00 seconds (0.00%).
minimum: 0.00 seconds.
maximum: 0.00
@Till: You could easily go and push a MP against
https://code.launchpad.net/~phablet-team/lxc-android-config/trunk
yourself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
https://bugs.launchpad.
** Tags added: bluetooth bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1524939
Title:
Using telephony in car with bluetooth not possible after second
connection
S
It should.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479445
Title:
IN CAR: Signal Strength not shown in car display
Status in Canonical System Image:
New
Status in
@Peter: Address book download isn't really implemented today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to car-bl
@Simon: Really? Then I just didn't found the pointers in the code ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect t
We're actively working on getting this done and BlueZ 5.23 is being
prepared and should soon appear in wily. There is a ppa already which
has all necessary packages for vivid and wily (see https://launchpad.net
/~ubuntu-desktop/+archive/ubuntu/transitions). If you want to help us
testing those feel
@Pat: Thanks for the pointer.
@Mark: How should reverse engineering help here? Its simply an
interoperability issue and we're using completely different software
than Android does. However the interface to the BT chip is standardized
so no need to reverse anything here. We need to find out where e
e in BlueZ needs to be changed to ignore the quotes from the value.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: In Progress
** Tags: bluetooth
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
Fix in https://code.launchpad.net/~morphis/bluez/unquote-hostname
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1482688
Title:
Bluez reports quoted hostname
Status in blue
@Mark: You can. Follow https://wiki.ubuntu.com/DebuggingBluetooth to
generate logs with debugging statements and then please attach them
here. But please check those for any private data before or send them to
me by private mail.
--
You received this bug notification because you are a member of U
@seb128 Yeah this is really related. As Alfsono already said the
selection of the modem device is currently not deterministic and needs
to be tweaked in order to be reliable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to blu
** Tags added: bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1484980
Title:
AVRCP support for Ubuntu Phone
Status in bluez package in Ubuntu:
Confirmed
Bug de
@Mark: That is good to hear. My suspection now is that it's either a
problem with the BT chipset firmware or something in in-kernel bluetooth
management layer as the Meizu has a newer kernel than the BQ device
(Meizu: 3.10, BQ: 3.4).
--
You received this bug notification because you are a member
@Ananda: Can you please provide more details about what is not working
and which exact steps you're performing with your Ubuntu phone? Also
please provide logs with debug mode enabled. See
https://wiki.ubuntu.com/DebuggingBluetooth for details how to enable
this.
--
You received this bug notifica
It did.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479445
Title:
IN CAR: Signal Strength not shown in car display
Status in Canonical System Image:
In Progress
Statu
I tried to reproduce this under similar conditions with a headset as I
don't have access to any carkit at the moment but didn't had success.
There are two possible reasons for this:
* the device doesn't get disconnect any stays connected as device for bluez
* the device disconnects properly but th
gs which I have at
https://code.launchpad.net/~morphis/ubuntu-system-settings/fix-device-
actions
Second problem requires to backport fixes from upstream bluez to
correctly enable the reconnect mode of HID devices.
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis
Fixes for 1. and 2. are in Silo 009 and 059. Wily should be not affected
as we already landed bluez5 there.
@Daniel: If you want to test get and install packages from silo 059 in
your vivid desktop installation.
--
You received this bug notification because you are a member of Ubuntu
Touch seede
I ruled out that this is a bug with bluez. Actually system-settings does
show the mouse as its falling into the device-type "Network" which we
don't display in settings. We should actually stop limiting the number
of devices we're displaying and allow them all.
** Also affects: ubuntu-system-setti
Please note that trusty still comes with bluez5 which doesn't support BT
LE HOG devices like the mouse referenced here. I've tested with John
that the mouse is working fine on >= wily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Its rather important when you set the video-param-encoding-bitrate
parameter for the encoder. The code should look like
android_recorder_setParameter(recorder, "video-param-encoding-bitrate=2048");
...
android_recorder_prepare(recorder);
android_recorder_start(recorder);
The parameters are not ap
See https://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/wily/bluez/wily/view/head:/audio/telephony-ofono.c#L1346
for details.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1
The cause for this is that with the deprecation of HAL we also dropped
battery query support from BlueZ and never brought it back. We need to
interface BlueZ correct with upowerd so we can send out the correct
battery level.
--
You received this bug notification because you are a member of Ubuntu
This comes from the fact that our BlueZ version still relies on an older
API version of ofono as we have implemented. It listens for changes to a
"SignalStrength" property on the org.ofono.NetworkRegistration interface
which doesn't exist. The propery is named just "Strength" these days.
See https
@Andriopoulos: Did you reboot after you executed the steps mentioned on
https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system-
settings#Bluetooth-1 ? Those things will only be effective when you
reboot so the relevant services get restarted (you could restart them
manually but to keep the s
@Andriopoulos: I have some questions to the log file you attached:
* Did you power off Bluetooth at some point through the UI?
* You say "calls" but I only see one call being made in that log file. Can you
please describe the exact steps you performed after you powered on your phone?
* What is th
)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1445376
Title:
A2DP skips when conneted to handsfree device
Status
This is a matter of defining the right class in
/etc/bluetooth/main.conf. There are some generators out there like http
://bluetooth-pentest.narod.ru/software/bluetooth_class_of_device-
service_generator.html
For me it looks like 0x73020C would be what we should set as our COD:
Major Service Clas
301 - 365 of 365 matches
Mail list logo
