@Simon

Regarding the battery mismatch, the HFP 1.6 specification ( section
4.33.2 AT Capabilities Re-Used from GSM 07.07 and 3GPP 27.007 )
documents that the battery level is indicated by an integer between 0
and 5.  For a battery percentage of 1 or less, we indicate 0.   Above
1%, we divide by 20 and add 1, giving us roughly five equal ranges in
20% increments.

If the battery display in the car has only four bars ( as opposed to
five ), then it's not going to match up correctly, and the results will
be skewed.   I'm changing the ofono task to Incomplete.

@Uranicus

Thanks for your thorough testing!  When testing non-standard images (
eg. from rc-proposed ), please attach the details image information from
the command 'system-image-cli -i' ( run on the device ).

It sounds like Bluez5 improves one of the two original devices in your
description ( eg. the Jabra ), however there still are some issues with
it.  I'll leave it up to Simon as to whether he'd like you to open a new
bug for the specific re-connection failure described.

More work is needed apparently to get things working with your A3.

Also, regarding your A3, I'd be interested if it displays more bars for
the phone battery level than the Seat.

** Changed in: ofono (Ubuntu)
       Status: New => Incomplete

-- 
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/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:
  New
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to