It did.
--
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/1479445
Title:
IN CAR: Signal Strength not shown in car display
Status in Canonical System Image:
In Progress
Status in bluez
@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
@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
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
This is simply not implemented in our version of BlueZ we use at the
moment. Needs further investigation what we need to exactly to get this
working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in 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
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1479438
@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
)
Assignee: (unassigned) = Simon Fels (morphis)
--
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/1445376
Title:
A2DP skips when conneted to handsfree device
Status in Canonical System
@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 the
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
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
@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
.
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: In Progress
** Tags: bluetooth
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) = Simon Fels (morphis)
** Changed in: bluez (Ubuntu)
Status: New = In Progress
--
You
Fix in https://code.launchpad.net/~morphis/bluez/unquote-hostname
--
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/1482688
Title:
Bluez reports quoted hostname
Status in bluez package in
@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
** Tags added: 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/1484980
Title:
AVRCP support for Ubuntu Phone
Status in bluez package in Ubuntu:
Confirmed
Bug description:
It should.
--
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/1479445
Title:
IN CAR: Signal Strength not shown in car display
Status in Canonical System Image:
New
Status in bluez
@Peter: Address book download isn't really implemented today.
--
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/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
@Simon: Really? Then I just didn't found the pointers in the code ...
--
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/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to
@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 Kernel
Packages, which is subscribed to bluez in
@pitti: Yes, they implemented it to allow us to replace our hack udev
rule
(https://bazaar.launchpad.net/~bluetooth/bluez/ubuntu/view/head:/debian/50
-bluetooth-hci-auto-poweron.rules) with that. "that some distributions "
includes Ubuntu.
--
You received this bug notification because you are a
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of
Nothing we have to change on media-hub just need to enable bluez to
forward those events to media-hub. Will come with bluez5.
** Changed in: media-hub (Ubuntu)
Status: Confirmed => Invalid
** Changed in: media-hub (Ubuntu RTM)
Status: New => Invalid
--
You received this bug
** Changed in: bluez (Ubuntu)
Importance: Undecided => 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/1505241
Title:
Phone does not suspend
Status in Canonical System Image:
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Importance: Undecided => Medium
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels
I tried to reproduce this with two MX4:
- First one running rc-proposed, the newer kernel with upgraded bluetooth stack
and bluez4.
- Second one running rc-proposed, the newer kernel with upgraded bluetooth
stack and bluez5.
Pat was running the first combination. I saw similar kernel suspend
Worth to mentioned but doesn't prove anything yet: When turning
bluetooth off
Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696811]
[HCI-STP][I]hci_stp_close:hdev(0xd91de000)
Nov 13 06:06:18 ubuntu-phablet kernel: [60938.696829]
[HCI-STP][I]hci_stp_flush:done
Nov 13 06:06:18 ubuntu-phablet
Disabling WiFi as next step lets the device suspend (but being woken up
by EINT shortly afterwards again).
--
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/1505241
Title:
Phone does not
QA did a test run and measure power usage on an MX4 device. Results are
stored at http://people.canonical.com/~platform-qa/power-
results/?Chttp://people.canonical.com/~platform-qa/power-
results/?C=M;O=D=M;O=D Test run number is 166.
According to QA they don't show anything significant
Generally I see aborted suspends because of the MT662x wakeup source
also on rc-proposed with its current kernel but not in such a high
frequency as Pat or I saw them before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in
** Changed in: bluez (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchp
** Tags added: after-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/1481136
Title:
Bluetooth mouse fails to reconnect after suspend + resume
Status in canonical-pocket-desktop:
telepathy-ofono does things.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: bluez (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
** Summary changed:
- BLUEZ5: Connecting a keyboard shows no pip popup
+ BLUEZ5: Connecting a keyboard shows no pin popup
--
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/1499789
Title:
** Tags removed: bluez5
** Tags added: after-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/1499858
Title:
bluetoothd[650]: Failed to obtain handles for "Service Changed"
We will release a fully updated bluetooth stack soon to the images and
this hopefully improves this interoperability issue. If not we will take
further actions from there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: bluez (Ubuntu)
Status: New => Invalid
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: pulseaudio (Ubuntu)
Status: New
** Changed in: bluez (Ubuntu)
Status: New => In Progress
--
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/1499789
Title:
BLUEZ5: Connecting a keyboard shows no pin popup
Status in
** Branch linked: lp:~morphis/ubuntu-system-settings/bluez5-support
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Simon Fels (morphis)
--
You received this bug notification because you are a
** Changed in: ofono (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Tags added: 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/1479438
Title:
IN CAR: Battery levels
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1494242
Title:
Try to auto conn
Can you please elaborate a bit more on what you think doesn't work? I am
not sure I fully understand what you describe as bug here.
--
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/1375766
We could just bind this to the condition if /sys/class/bluetooth is
available or not. So a
...
ConditionPathIsDirectory=/sys/class/bluetooth
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Great!
--
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/1506774
Title:
package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess
installed post-installation script returned
There is nothing we can do from bluez side. If the kernel interface we
need to do *any* work is not available we can't do anything else but
fail. The "bluetooth" module needs to be loaded or the kernel compiled
with CONFIG_BT=y rather than CONFIG_BT=m.
Is there any reason not to compile bluetooth
: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Affects: telepathy-ofono (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
This will be implemented as part of the ongoing BlueZ 5 porting work.
** Also affects: ofono (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ofono (Ubuntu)
Status: New => In Progress
** Changed in: bluez (Ubuntu)
Status: Triaged => Invalid
--
You received
This is fixed now and working with silo 43 and 52.
** Changed in: media-hub (Ubuntu)
Status: New => Invalid
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: bluez (Ubuntu)
Status: New => Fix Committed
** Changed in: p
Public bug reported:
Right now the user doesn't have any way to find out on which Bluetooth
profiles he is connected. The only thing he knows from the settings app
or the bluetooth indicator is that he is connected in some way with a
remote bluetooth device.
Android for example allows you to
** Tags added: after-bluez5 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/1448472
Title:
I can not connect phone with bluetooth with Lexus 400 RX 400H
Status in bluez
@joihap: Does the car gets listed under Connect automatically when
detected on your phone? If yes that is a good indicator that the car
got at least paired. What happens then if you connect the car manually?
--
You received this bug notification because you are a member of Kernel
Packages,
@JoiHap: At the time you called bluez-list-devices what was the state of
the entry in the settings app? As the output reports the car as being
paired / trusted / connected which is what we want.
--
You received this bug notification because you are a member of Kernel
Packages, which is
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)
** Changed
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 Kernel
Packages,
@JoiHap: Can you describe a bit more what you experience? So I need
answers for the following quesitons:
* Does the connection not happen directly after you paired the device
successfully?
* Please check with /usr/bin/bluez-list-devices if you car is paired. Optimal
would be if you can attach
Public bug reported:
[Impact]
[Test Case]
[Regression Potential]
[Other Info]
** Affects: linux-flo (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Affects: linux-mako (Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis
: linux-flo (Ubuntu) = linux-mako (Ubuntu)
** Also affects: linux-flo (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-flo (Ubuntu)
Assignee: (unassigned) = Simon Fels (morphis)
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1479442
Title:
IN CAR: Previous Calls log is not sh
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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
This can get rather serios if remote device doesn't allow connection
with specific types of device like my carkit. It doesn't want to connect
with my krillin device as it has a wrong device type (being a laptop)
set.
--
You received this bug notification because you are a member of Kernel
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1419877
Title:
[bluetooth] krillin advertized as t
Fixing just the device class is pretty easy but we should bind this
somehow to the type of device we're running on. For tablets/phone that
doesn't make a difference but having a more general solution in place
which lets bluez determine the type of device on startup would be
optimal.
--
You
>From what jhodap told me the sound indicator might be the one
responsible for this.
** Also affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bluez (Ubuntu)
Status: Confirmed => Invalid
** Also affects: indicator-sound
Importance: Undecided
@JoiHap: Can you test this again with the latest rc-proposed image?
--
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/1435040
Title:
Ubuntu Phone (BQ E4.5) does not connect to
After some more analysis the BT HID stack in the krillin kernel seems to
be horrible broken. We will not going to fix but replace this pretty
soon with a complete new bluetooth stack which will be based on an
recent upstream kernel (4.2). We have to wait until this is done until
we have a solution
Sounds good. There were some bluetooth bug fixes between 4.1 and 4.2 so
good chance that this solved your problem. Closing this bug for now.
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
*** This bug is a duplicate of bug 1479438 ***
https://bugs.launchpad.net/bugs/1479438
** This bug has been marked a duplicate of bug 1479438
IN CAR: Battery levels not shared via bluetooth for in car experience
--
You received this bug notification because you are a member of Kernel
Which phone is this?
It would be also quite helpful if you can provide some more verbose
debug logs. To do that follow https://wiki.ubuntu.com/DebuggingBluetooth
and reproduce the problem. Afterwards attach the syslog file here or
shared privately with me if you mind pushing it here.
--
You
When connecting a device doesn't work this normally means that there is
no handler for the profiles bluez tries to connect with. "Connecting
with a bluetooth device" means "Connecting with a profile". When you
enter "connect " in bluetoothctl bluez will go through all
profiles the remote devices
@Nephilim1973: No, we can't "learn" anything here from Android. We have
a completely different bluetooth stack which you can't compare with the
Android one. Config files in /etc/bluetooth/*.conf don't help. Those
problems are at other layers.
> Why the BT handling is so different between Touch
** Tags added: 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/1492892
Title:
Implement standalone bluetooth agent handler
Status in Canonical System Image:
New
Status in bluez
Public bug reported:
Currently the settings app registers an agent instance against BlueZ
which can only be triggered when the application is currently active. To
provide a better user experience we need a different place to implement
the agent to have it running in the background all the time.
(Ubuntu)
Importance: Undecided
Assignee: Simon Fels (morphis)
Status: New
** Affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
** Tags: bluetooth
** Also affects: ubuntu-system-settings (Ubuntu)
Importance: Undecided
Status: New
@Pat: You had any success in reproducing this again?
--
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/1487889
Title:
After disconnnecting from car bluetooth, audio is still routed to
This should be fixed as soon as we have landed bluez5.
** Tags added: after-bluez5 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
The used SIM card for HFP is currently picked randomly depending on
which modem device in ofono turns up first. See
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1418040 for more
details on this. However this needs to be reworked to support incoming
calls from two SIM cards rather than just
** Tags added: after-bluez5 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/1418040
Title:
Calling from car using bluetooth, call is placed on ril_0, even though
ril_1 is
Both Gustavo and me tried to reproduce this with our cars but couldn't
see the behavior Pat is describing. Waiting right now for Pat to get
this reliable reproduced with verbose debug logging enabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is
lso affects: bluez
Importance: Undecided
Status: New
** Project changed: bluez => canonical-devices-system-image
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
Kernel fix for this is submitted and waiting for review.
--
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/1491484
Title:
Anker keyboard doesn't send key events to krillin
Status in
** Summary changed:
- wrong keyboard layout
+ Bluetooth keyboard is configured with wrong keyboard layout
** Tags added: 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/1491340
>From what I hear from the Mir/UI guys this is something which isn't
implemented yet on their side. BlueZ itself doesn't have any control
over this as its just exposing an input device which is then configured
and used by the UI.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
** Changed in: bluez (Ubuntu)
Status: Confirmed => In Progress
--
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/1419877
Title:
[bluetooth] krillin advertized as type "computer"
Just add-apt-repository doesn't work as the priority of a silo is below
the regular archive so those things aren't pulled in.
At best you use the citrain command line tool for this. However if
you're installing a silo you will put your device into unsupported state
and have to reflash to avoid
Can you please do the following to generate a more verbose output:
$ sudo systemctl stop bluetooth
$ MGMT_DEBUG=1 sudo bluetoothd -n -d &> bluetoothd-multiple-adapters.log
In another terminal:
$ bluetoothctl
[bluetooth]# list
Please add all output here and attach the file bluetoothd-multiple-
>From BlueZ side we provide an input device which already reports the
necessary key events we now only need someone to use them.
--
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/1484980
Also a test with a latest rc-proposed image and silo 22
(https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-022/) would be great from someone who
experience problems here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This is a missing feature. Needs to be implemented.
--
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/1479440
Title:
IN CAR: Missed calls are not shared with the car via bluetooth
Status
** Changed in: bluez (Ubuntu)
Assignee: (unassigned) => Simon Fels (morphis)
--
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/1494225
Title:
Call audio is not routed to head
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 Kernel
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
Status in
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 Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1494250
Title:
HID devices doesn't reconnect reliable
** 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
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
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
** Tags removed: bluez5
** Tags added: after-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/1492892
Title:
Implement standalone bluetooth agent handler
Status in Canonical
1 - 100 of 306 matches
Mail list logo