This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
** Changed in: bluez (Ubuntu)
Status: Won't Fix => Invalid
--
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/301480
Title:
can't connect to PAN NAP
Status in bluez package in
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status:
This is reported against an old version of Ubuntu. Because of that we
won't fix this issue however if this behavior repeats on a modern
version please fill a bug report against it and we will take it from
there.
** Changed in: bluez (Ubuntu)
Status: New => Won't Fix
--
You received this
*** This bug is a duplicate of bug 1398193 ***
https://bugs.launchpad.net/bugs/1398193
Hey,
we know about this issue and for you to know it is a missing feature at
the moment. We do, however, keep this in our minds and will work on this
in the near future [think perhaps OTA12].
Best
**
Tested using bq Aquaris E4.5 and Sony SBH52 headset. The BT has not been
disconnected during a call that lasted 6:42.
OS build number: r325
Ubuntu Image part: 20160505
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
I absolutely understand and good luck with finishing all of the updates.
Sounds like you had a lot of fun hacking :-)
--
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:
@Stunts
I wonder if you had time and chance to test the possible fix. Let me
know because if it works then we could include it in the upcoming OTA
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Stunts
I have made an improvement and I wonder if it will have any positive
effect on your side. Could you install silo 00 on your device and try if
that fixes the problem for you?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez
** Branch linked: lp:~kzapalowicz/ubuntu-system-settings/fix-1539158
--
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
It seems that I know what is happening and why the pairing is denied. I
think that it is because the device when added to the internal data
structures is not yet fully initialized as the properties are gathered
asynchronously. In the same time the pin request is executed that tries
to use the yet
This is awesome, thank you for performing the test case. Now I know that
the flaw is still somewhere in the Ubuntu System Settings and it is most
probably a race.
As for the other issues that you have observed I would prefer to first
solve the pairing bug and the other you mention will be waiting
@Stunts:
There is one thing, however, that you could try on your phone. In order
to make sure that the flaw is still in the Ubuntu System Settings you
could try to pair and connect with the car using the bluetoothctl
commandline interface w/o even opening the Bluetooth settings scope.
In order
Hey, the Bluetooth bugs with cars are our top priority at the moment and
we are putting the effort into fixing them as soon as we can.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Could you test with the latest image that contained bluez 4.x and that
would be pre OTA 8.5 as bluez 5 has been introduced there. It is also
important to flash everything including kernel. This is to narrow down
the update that could cause it also proving that this is in fact bluez 5
update
The Ubuntu System Settings log contains such a warning:
14:15:08,530 - WARNING - file:///usr/share/ubuntu/settings/system/qml-
plugins/bluetooth/DevicePage.qml:156: TypeError: Cannot read property
'paired' of null
This corresponds to the pairing request that has been issued at the same
time.
14:15:05 here the car infotainment system is discovered during the
device discovery process. The bluez correctly handles the device.
src/adapter.c:device_found_callback() hci0 addr 38:C0:96:BC:D1:10, rssi -52
flags 0x0003 eir_len 5
src/device.c:device_create() dst 38:C0:96:BC:D1:10
@ssweeny
Could you retest with newest images and attach syslog. 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/1552410
Title:
Cannot pair mako with 2014 Subaru Forester
Status
*** This bug is a duplicate of bug 1539158 ***
https://bugs.launchpad.net/bugs/1539158
What I have found in the syslog:
15:21:25 here the car is connecting to the phone, the bluez correctly handles
the device:
src/adapter.c:connected_callback() hci0 device 00:1A:77:F6:D5:2B connected
*** This bug is a duplicate of bug 1539158 ***
https://bugs.launchpad.net/bugs/1539158
It seems like a Settings bug that has been fixed a while ago and
reopened afterwards.
** This bug has been marked a duplicate of bug 1539158
Unable to pair with in-car hands-free system after OTA-9
*** This bug is a duplicate of bug 1539158 ***
https://bugs.launchpad.net/bugs/1539158
Agent is requested however it replies with "Agent
/com/canonical/SettingsBluetoothAgent/adapteragent replied with an
error: org.bluez.Error.Rejected, The request was rejected:
RequestPinCode"
--
You
This is related to
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242
--
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
Yes, it might be related.
--
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/1563768
Title:
Bluetooth HFP indicates a permanent ongoing call
Status in Canonical System Image:
Confirmed
@Uranicus
Are you abel to do this test, i.e.try to pair and connect with your car
however using the bluetoothctl and *not* opening the system settings at
all. This is to tell if we should be still worried about our recent
update to the system-settings or we can rule this out and seek some
other
@Uranicus,
Thanks for the logs and screenshot. I had some time to review these and
they do put some light on the whole issue. It is still far to find the
root cause (or perhaps it is just around a corner;) nevertheless we are
looking into it.
--
You received this bug notification because you
@Uranicus
Thanks for the try and if you could do one more with Audi however this
time w/o the previous history so after forgetting all of the devices and
the reboot. This is to isolate the issue and reduce the noise in the
logs.
--
You received this bug notification because you are a member of
@Uranicus
You could try first to remove the devices [forget] using the Settings ->
Bluetooth. You do not need to reinstall the silo once it has been
already installed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Uranicus:
Could you remove the local devices database [forget devices, make sure
that /var/lib/bluetooth contains nothing], reboot and try connecting to
Audi or Seat? This is for isolating the issue. Thanks in advance.
--
You received this bug notification because you are a member of Kernel
I have analyzed the syslog and must say that this is a strange one to
figure out.
There is a strange line in the syslog saying that the error is "Device
or respurce busy" and it happens for many actions such as SDP Query for
example. It is reported for bonding attempts which fail with code either
** Changed in: bluez (Ubuntu)
Status: Invalid => Fix Released
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
First there are many errors such as: "Not enough free handles to
register service" in the syslog for the Bluetooth service.
Then the attributes of the BLE devices are not read due to the auth
issue: "Error reading Report value: Attribute requires authentication
before read/write"
--
You
** Tags added: bluez-classic
--
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/1557298
Title:
[Xenial][Bluez5] Low Energy Keyboard is paired incorrectly
Status in Unity Control Center:
Hi,
We will try to resolve this issue, hopefully, in the coming days/weeks or get
closer to understanding the root cause. However before we start I would like you
to retest again because we have made a significant change recently with updating
the BlueZ version to 5.37 as well as we might have a
The attachment contains the logs: syslog and pulseaudio state (where
arrows); captured for the following test case:
## Test Case:
connect BT
-->
play
disconnect BT
-->
play
connect BT
-->
play
disconnect BT
incoming call
-->
The further test have concluded that the line
1. [pulseaudio] sink-input.c: Successfully moved sink input 0 to
bluez_sink.68_76_4F_6C_31_E9.
is missing because module-switch-on-connect skips switching for default
sink
2. [pulseaudio] module-switch-on-connect.c: koza: not switching to internal
*** This bug is a duplicate of bug 1552128 ***
https://bugs.launchpad.net/bugs/1552128
** This bug has been marked a duplicate of bug 1552128
Music audio is not transferred to headset after it is connected
--
You received this bug notification because you are a member of Kernel
Packages,
The information from debugging pulseaudio:
0. Info
phablet@ubuntu-phablet:~$ pactl info
Server String: /run/user/32011/pulse/native
Library Protocol Version: 30
Server Protocol Version: 30
Is Local: yes
Client Index: 26
Tile Size: 65496
User Name: phablet
Host Name: ubuntu-phablet
Server Name:
After receiving the media key event BlueZ sends in over the DBus to the
media player. However there are no entries in the captured DBus log that
would show the evidence of calling the Play, Pause, Next, Previous
methods:
That should look like:
method call sender=:1.123 ->
Just a quick test has revealed that the media key presses are captured
on the receiving side:
bluetoothd[887]: profiles/audio/media.c:previous()
bluetoothd[887]: profiles/audio/media.c:next()
bluetoothd[887]: profiles/audio/avctp.c:handle_panel_passthrough() AV/C: REWIND
pressed
There are two differences in the logs.
First:
In case there is no call in between of disconnection and connection
after the connection is made the 'card' is created with the profile set
to 'off'. This is later reset to profile a2dp_sink.
[pulseaudio] backend-ofono.c: New HF card found:
If there is an incoming call between disconnecting the accessory and
connecting it back again the music plays just fine over the BT.
connect accessory
play music (goes through BT)
disconnect accessory
incoming call (reject or accept/terminate)
connect accessory
play music (goes through BT)
in
I observed a similar issue with music playback, i.e. I'm unable to
play/pause/ff/rev the music from the remote accessory.
--
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/1398193
Title:
I just have tested E4.5 with recent rc-proposed plus silo 39 [bluez
5.37] and silo 47 [pulseaudio]. There were no issues with the test case
as stated in this bug report.
** Tags added: bluez-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is
Good, I will mark this as Fix Commited then and we will take it from
there.
** Changed in: bluez (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
@Geoff,
You could capture logs as stated here:
https://wiki.ubuntu.com/DebuggingBluetooth
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/1494225
Title:
Call audio is not routed
@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
I confirm this with krillin running rc-proposed from 27th of Feb with
silo 47 [pulseaudio fix].
During the call audio in not in the headset however it is possible to
transfer it between the phone [works ok] and back through the Bluetooth
[silence]. Will capture and attach logs later today.
**
I cannot reproduce this on kirillin and frieza running recent rc-
proposed channels.
--
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/1488170
Title:
Bluetooth initiated after quitting
phablet@ubuntu-phablet:~$ hciconfig -a
hci0: Type: BR/EDR Bus: UART
BD Address: 4C:74:03:5F:10:BE ACL MTU: 1021:4 SCO MTU: 184:1
UP RUNNING PSCAN
RX bytes:73786 acl:706 sco:0 events:6532 errors:0
TX bytes:3446513 acl:6213 sco:0 commands:437 errors:0
** Description changed:
Device and Ubuntu version
=
Tested on Krillin [Aquaris E4.5], with BlueZ 5.37
phablet@ubuntu-phablet:~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
phablet@ubuntu-phablet:~$
+
+ Tested with:
+ 1. Sony SBH52
Public bug reported:
Device and Ubuntu version
=
Tested on Krillin [Aquaris E4.5], with BlueZ 5.37
phablet@ubuntu-phablet:~$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04
phablet@ubuntu-phablet:~$
Tested with:
1. Sony SBH52 headset
2. Philips SHB5500
>From a quick assessment I agree that the root cause might be a lack of
"key up" event as this would explain the repetitions.
** Tags added: ubuntu-classic
** Tags added: ubuntu-touch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: bluez-touch
** Tags added: bluez-classic
--
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/1551131
Title:
Cannot pair Jabra Classic headset
Status in bluez package in
** Tags added: bluez-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/1551131
Title:
Cannot pair Jabra Classic headset
Status in bluez package in Ubuntu:
New
Bug description:
** Tags added: bluez-classic
--
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/297635
Title:
Any user can manage bluetooth devices
Status in bluez package in Ubuntu:
New
Bug
** Tags added: bluez-classic
--
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/292042
Title:
Logitech Bluetooth keyboards (Mediaboard & Di Novo) not working on
Intrepid
Status in Ubuntu
** Tags added: bluez-classic
--
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/292030
Title:
Bluetooth mouse stops after a while
Status in bluez package in Ubuntu:
Confirmed
Bug
** Tags added: bluez-classic
--
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/277211
Title:
Dell Wireless 355 Bluetooth card can't turned on in Ubuntu
Status in bluez package in Ubuntu:
** Tags added: bluez-classic
--
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/287132
Title:
bluetoothd crashed with SIGSEGV in calloc()
Status in bluez package in Ubuntu:
Triaged
Bug
** Tags added: bluez-classic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/123920
Title:
Bluetooth Logitech Dinovo Keyboard/Mouse don't work
Status in Bluez Utilities:
New
Status in
** Tags added: bluez-classic
--
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/124743
Title:
Sony Sixaxis Controller does not work over bluetooth
Status in Ubuntu PS3 Port:
New
Status
** Tags added: bluez-classic
--
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/212492
Title:
cell/mobile phone has to be added as an input device to be used as a
Bluetooth remote control
** Tags added: bluez-classic
--
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/219057
Title:
Bluetooth does not coexist with WiFi
Status in bluez package in Ubuntu:
Confirmed
Bug
** Tags added: bluez-classic
--
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/61413
Title:
Logitech DiNovo MediaPad should not toggle Numlock
Status in bluez package in Ubuntu:
Nice that you managed to get the log, well done. As for the personal
info I suppose that it is better you remove it however if that is too
complicated just let us know and we will figure something out. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages,
I just have done a quick assessment and I see here two issues actually.
First is related to the Call functionality and could be summarized as:
not possible to get the call audio through the BT speaker/headset. I was
thinking that this is because the Audio Connection setup somehow fails
however
301 - 398 of 398 matches
Mail list logo
