touch-packages team mailing list archive

[Uranicus <sliding.paul@xxxxxx>]

First a feedback of the tests with the Jabra BT250 device. Please see my
report and the logfiles in the attachment.

I am also posting the plain text here which I have attached as pdf &
odt-file.

---------------------  Text ------------------------

Reporting on Bluetooth bug 1500242
System Information of the device
Detailed image information of the system used for testing
system-image-cli -i:

current build number: 196
device name: krillin
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2015-12-05 18:28:01
version version: 196
version ubuntu: 20151204.1
version device: 20151028-869191d
version custom: 20151111–36-46-vivid


hciconfig -a

hci0:	Type: BR/EDR  Bus: UART
	BD Address: 4C:74:03:64:75:ED  ACL MTU: 1021:4  SCO MTU: 184:1
	UP RUNNING PSCAN 
	RX bytes:1054 acl:0 sco:0 events:56 errors:0
	TX bytes:3734 acl:0 sco:0 commands:56 errors:0
	Features: 0xbf 0x3e 0x8d 0xfe 0xdb 0xff 0x5b 0x87
	Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
	Link policy: RSWITCH SNIFF 
	Link mode: SLAVE ACCEPT 
	Name: 'Aquaris E4.5 Ubuntu Edition'
	Class: 0x5c0110
	Service Classes: Rendering, Capturing, Object Transfer, Telephony
	Device Class: Computer, Handheld
	HCI Version: 4.0 (0x6)  Revision: 0x0
	LMP Version: 4.0 (0x6)  Subversion: 0x0
	Manufacturer: MediaTek, Inc. (70)


bluetoothctl

[NEW] Controller 4C:74:03:64:75:ED Aquaris E4.5 Ubuntu Edition [default]
[NEW] Device 90:03:B7:46:8E:E9 SEAT_BT
[NEW] Device 00:80:00:00:15:76 Bluetooth Mouse


[bluetooth]# show

Controller 4C:74:03:64:75:ED
	Name: Aquaris E4.5 Ubuntu Edition
	Alias: Aquaris E4.5 Ubuntu Edition
	Class: 0x5c0110
	Powered: yes
	Discoverable: no
	Pairable: yes
	UUIDs:
	  Headset AG                (00001112-0000-1000-8000-00805f9b34fb)
	  Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	  SIM Access                (0000112d-0000-1000-8000-00805f9b34fb)
	  Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	  PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	  A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	  Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	  Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	  Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	  Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	  Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0523
	Discovering: no
Modifications on the device (debugging information)
sudo mount -o remount,rw /
Since no bluetooth-override file was available I used:

sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf
sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf
I was not 100% sure about the ofono modifications: “Add '-d' to the exec line in /etc/init/ofono.override”. I have modified the line in ofono.override to:

exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

I tested this 2 times. 
1. I have restarted the phone after these modifications (logfile start with 1_*).
2. I have not restarted the phone and carried out the tests directly thereafter  (logfile start with 2_*). 


Issue with Jabra BT250 device
I followed the connection & pairing process with [bluetooth]# devices and made two screen shots:

[bluetooth]# devices
Device 90:03:B7:46:8E:E9 SEAT_BT
Device 00:80:00:00:15:76 Bluetooth Mouse

I put the Jabra is search mode and the phone found the device:

[bluetooth]# devices
Device 90:03:B7:46:8E:E9 SEAT_BT
Device 00:80:00:00:15:76 Bluetooth Mouse
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[NEW] Device 00:07:A4:00:A7:05 JABRA 250
[CHG] Device 00:07:A4:00:A7:05 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:07:A4:00:A7:05 RSSI: -38
[CHG] Controller 4C:74:03:64:75:ED Discoverable: no
[CHG] Device 00:07:A4:00:A7:05 RSSI is nil
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes

The I pressed “connect” in the screen of the Jabra of the phone:

[CHG] Device 00:07:A4:00:A7:05 Connected: yes
[CHG] Device 00:07:A4:00:A7:05 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Paired: yes
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 ConnectedProfiles: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:07:A4:00:A7:05 Trusted: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discoverable: no

After this the Jabra changed from search mode into operational mode.
This is how the bluetooth window looked like after the pairing process
(correct symbol of the head set):


I can place calls and receive calls. I can end the calls with the button on the bluetooth device.
Then I turned the Jabra device off (power off of the device) ...

[CHG] Device 00:07:A4:00:A7:05 Connected: no

… and put it back on. I expect that the device automatically reconnects
to the phone. So first I did nothing just waiting.

[CHG] Device 00:07:A4:00:A7:05 Class: 0x20040c
[CHG] Device 00:07:A4:00:A7:05 Icon: audio-card
[CHG] Device 00:07:A4:00:A7:05 Connected: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Device 00:07:A4:00:A7:05 Connected: no
[CHG] Controller 4C:74:03:64:75:ED Discoverable: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no
[CHG] Controller 4C:74:03:64:75:ED Discovering: yes
[CHG] Controller 4C:74:03:64:75:ED Discovering: no

I was alos not able to manually reconnect it.
The bluetooth window looked like the following (see the changed symbol!):

The window of the Jabra device looked like:


I have attached the debugging files:

/home/phablet/.cache/upstart/application-legacy-ubuntu-system-settings-.log 
/home/phablet/.cache/upstart/dbus.log

in version 1_* and 2_* as described above. Both habe been generated
during these session of the above steps. I hope this helps. If you need
anything further please let me know.

** Attachment added: "Bug 1500242.7z"
   https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+attachment/4530310/+files/Bug%201500242.7z

-- 
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 devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions