This is a missing feature. Needs to be implemented.
--
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/1479440
Title:
IN CAR: Missed calls are not shared with the car via
** 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.
https://bugs.launchpad.net/bugs/1494225
Title:
Call audio is not rou
uez (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Tags: bluetooth bluez5
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (m
Public bug reported:
With bluez 5.33 on Nexus 4 and silo 43 installed:
* pair and connect a headset over HFP
* Establish an outgoing call or accept an incoming one
* Once the call is established the call audio isn't routed through the
handsfree device
** Affects: canonical-devices-system-image
this similar.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Tags: bluetooth bluez5
** Changed in: bluez (Ubuntu)
Assignee: (unassigned
@Nephilim1973: /var/log/syslog is what I need.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Please see http://www.spinics.net/lists/linux-bluetooth/msg64098.html
for details about this. It is obviously a problem with the driver which
needs to be fixed. The mail thread has some pointers but a real solution
seems to need quite some more work in the kernel bluetooth driver stack.
** Also
ged 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.
https://bugs.launchpad.net/bugs/1494250
Title:
HID devices doesn't reconnect re
** Description changed:
With bluez 5.33 on Nexus 4 with silo 43 installed.
* Pair and connect a HID device (mouse or keyboard)
-> pairing/connect works
* Use them for a bit
* Power HID device off
* Power HID device on again
* Start using the HID device
-> It doesn't reconnect
l be
added in the future.
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Tags added: after-bluez5 bluetooth
** Changed in: canonical-devices-system-image
Status: New => Incomp
We don't support sharing something via bluetooth at the moment. It's a
missing feature we will implement in the future.
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Tags ad
** Tags removed: bluez5
** Tags added: after-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/1492892
Title:
Implement standalone bluetooth agent handler
Status in
Rather than a bug this was just a incorrect usage of the available
tools. Normally when we connect a device through the UI it gets marked
as trusted directly. However when just doing that with bluetoothctl this
remains a manual step the user has to do.
** Changed in: bluez (Ubuntu)
Status:
There seems to something wrong with the whole management of audio over
bluetooth between bluez <-> pulseaudio <-> media-hub as also switching
between speakers and A2DP speaker doesn't work reliable and causes media
playback to be not usable as long as a A2DP speaker is connected in some
cases.
**
On 16.09.2015 10:32, Matthias Apitz wrote:
> I have pulled the tar files for the device and channel and the file
> channel.ini is fine in the archive version-25.tar.xz;
>
> more:
> the file has in all three locations:
> - my BQ r25
> - the version-25.tar.xz
> - the damaged file in my wife's BQ
>
Currently trying to find a solution together with Pat for this.
--
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/1487889
Title:
After disconnnecting from car bluetooth, audio
** Tags added: after-bluez5
** Tags added: blutooth
--
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/1235726
Title:
Bluetooth dosent work at all
Status in bluez package in
For sharing files over bluetooth you're using the OPP profile. See
https://git.kernel.org/cgit/bluetooth/bluez.git/tree/doc/obex-api.txt
for API details. I know there was some work going on to implement this
but it wasn't continued as we're currently migrating from BlueZ 4 to
BlueZ 5.
--
You
What happens here is now pretty clear:
The car gets disconnected but the rfcomm/sco channels aren't. Due to
that the audio card is still kept in PulseAudio which in turn lets the
UI think it can still use it.
However what is not clear yet is why this happens. The attached syslog
sadly doesn't
@Jamie: really?
Will double check that on monday.
** Tags added: bluetooth bluez5
** Tags removed: bluez5
** Tags added: after-bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc-android-config in
Ubuntu.
** Project changed: ubuntu-system-image => bluez (Ubuntu)
** Also affects: urfkill (Ubuntu)
Importance: Undecided
Status: New
** Tags added: after-bluez5 bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags removed: blutooth
** 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/1235726
Title:
Bluetooth dosent work at all
Status in bluez package in
That is fine. We will implement this once we come to it in our backlog.
--
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/1496107
Title:
Bluetooth option missing when trying
@Jim: It looks like you copied only half of the command from
https://wiki.ubuntu.com/DebuggingBluetooth
Can you repeat the steps?
** Tags added: after-bluez5 bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez
** Also affects: canonical-devices-system-image
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 Ubuntu.
https://bugs.launchpad.net/bugs/1492368
Title:
Calls made through
** Changed in: bluez (Ubuntu)
Status: In Progress => Fix Committed
--
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/1419877
Title:
[bluetooth] krillin advertized as
Please note that the kernel subsystem performs various initialization
steps for each HCI controller. Depending on if a controller passes this
it gets up in bluetoothd or not. If a HCI controller is still flagged
with HCI_SETUP or HCI_CONFIG then something is wrong. Even if the
controller turns up
Please note that 15.10 ships bluez 5.33!
Next the "15:10: bluetoothd reports "Not enough handles to register
service" at start" message doesn't have anything to do with this.
Let me look at the log files to see if there is something obviously
going wrong.
--
You received this bug notification
So what happens here is that the authentications fails with a
MGMT_STATUS_AUTH_FAILED error code. Because of this bluez retries the
authentication multiple times. That is why you get the multiple PIN code
requests in a row.
Can you please elaborate a bit more on the exact steps you do? Please
** Tags added: bluetooth
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
** 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/1499858
Title:
bluetoothd[650]: Failed to obtain handles for "Service Changed"
: after-bluez5 bluetooth
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Can you check if the package bluez-obexd is installed?
--
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/1499858
Title:
bluetoothd[650]: Failed to obtain handles for "Service
-image
Importance: Undecided
Status: New
** 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.
https://bugs.launchpad.net/b
This pretty much looks like the adapter is just not automatically
enabled again after you restart the service. There is currently a udev
workaround rule in place to active a Bluetooth adapter directly at
login-screen time which wouldn't kick in here again. If there is no
general power state saver
** Tags added: after-bluez5 bluetooth
** 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.
https://bugs.launchpad.net/bugs/1498
Public bug reported:
Currently the bluez-cups package depends on cups but that should be more
a recommendation as we don't want the user to require installing cups.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: after-bluez5 bluetooth
--
You received this
** 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
@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
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.
** 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
@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
@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
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
** 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
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
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.
@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
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
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,
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
** 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
@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.
Did a first look and it seems that your headset initates the connection
and wants to connect on HSP
Dec 17 17:59:38 ubuntu-phablet bluetoothd[895]: src/profile.c:ext_confirm()
incoming connect from 00:21:3C:A0:14:A6
Dec 17 17:59:38 ubuntu-phablet bluetoothd[895]: src/service.c:btd_service_ref()
@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:
** Changed in: wpa (Ubuntu)
Status: New => In Progress
** Changed in: wpa (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 wpa in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: In Progress => Invalid
** Changed in: bluez (Ubuntu)
Status: Invalid => Won't Fix
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: Fix
Public bug reported:
With our package for wpa-supplicant a call
$ sudo gdbus call -y -d fi.w1.wpa_supplicant1 -o
/fi/w1/wpa_supplicant1/Interfaces/1 -m
org.freedesktop.DBus.Properties.GetAll 'fi.w1.wpa_supplicant1.Interface'
fails always with
Error:
Attached is the log from Pat which shows the actual problem together
with some verbose logging.
>From the log the reason for the continous hold wakelock MT662x are therm
events we're receiving from the WiFi/BT/.. combo chip. They start to
flood at one point which will keep the device awake. One
Something like in the attached patch should fix this.
** Patch added: "fix-stations-property-getter.patch"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1528173/+attachment/4538345/+files/fix-stations-property-getter.patch
--
You received this bug notification because you are a member
@hasselmm: Can you please follow
https://wiki.ubuntu.com/DebuggingBluetooth so that we get some more
details on what is going wrong?
Btw. what do you mean with "File transfers simply timeout."? We don't
support file transfers over bluetooth on Ubuntu Touch yet.
--
You received this bug
Did you connect the BT headset when you were registered with a telephony
network operator?
--
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
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
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
** 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.
** 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
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
>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
-
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.
Also can you give me the exact name of the mouse you're using?
--
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/1519718
Title:
Screen doesn't change after connecting a BT
Can you please attach the missing syslog as mentioned in
https://wiki.ubuntu.com/DebuggingBluetooth
That is the most interesting one.
** Tags added: bluez5
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Class 0x260404 is major class 'Audio/Video' and minor class 'Wearable
Headset Device'. With this marking this device as headset is the right
thing to do as we don't have any other way to find out what it is.
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Incomplete => Invalid
**
Can you reproduce this bug with following
https://wiki.ubuntu.com/DebuggingBluetooth? The logs attached doesn't
contain any debug information which would be really helpful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
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.
** 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
That isn't that easy as you looks like. It depends hardly on what the
device says it is. Can you please follow the steps for bluetoothctl on
https://wiki.ubuntu.com/DebuggingBluetooth so find out what the class-
of-device for this device is? This field encodes what type of device the
speaker says
*** This bug is a duplicate of bug 1334315 ***
https://bugs.launchpad.net/bugs/1334315
"no support to the phone contacts": Done
" no last 10 calls (in/out) list": No work started yet, duplicates 1479442
" no indication of GPRS/3G signal strength": Done, landed with bluez5 in
rc-proposed now
@hasselmm: No. Ignore "Not enough free handles to register service".
That is just because of some internal things and doesn't cause any
problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
This is quite confusing. Does
> 3.Make a call to DUT
> >Ringtone sounds from the phone
mean you heard the ringtone on the phone or is just your expectation?
> No sounds for the call in both sides
You mean you didn't heard a ringtone on both phones you used to setup
the call? Or you didn't
Can you verify this still happens with bluez5 landed in rc-proposed? If
yes, please follow https://wiki.ubuntu.com/DebuggingBluetooth to add
additional information to this bug report we absolutely need to start
work.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
** Tags added:
** Tags added: 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/1515179
Title:
[nexus7][bluez5] Unable to pair with Arc Touch Bluetooth
Status in ubuntu-nexus7:
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
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
** Tags added: bluetooth-ota0
** Tags removed: bluetooth-ota0
** 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/1519718
Title:
Screen doesn't
** 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/1519594
Title:
No sounds for ongoing call in both sides when connecting a BT speaker
Status in
** 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/1505241
Title:
Phone does not suspend
Status in Canonical System Image:
In Progress
Status
Looks like I've found the reason for this. Seems to be the timing which
is somehow different on your side to what I saw before. Will give some
more details later today where to get the updated pulseaudio packages
from to test on your side.
** Tags added: bluetooth-ota9 bluez5
--
You received
It looks like the mouse is correctly hooked up into the system:
Nov 26 02:41:47 ubuntu-phablet kernel: [ 310.071943] hid-generic
0005:046D:B014.0001: unknown main item tag 0x0
Nov 26 02:41:47 ubuntu-phablet kernel: [ 310.072340] input: Bluetooth Mouse
M336/M337/M535 as
Did you reboot after following the wiki page? The new syslog still
doesn't seem to have the debug switches enabled.
--
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
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
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
** 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
** 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.
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
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"
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
101 - 200 of 363 matches
Mail list logo
