touch-packages team mailing list archive

[Tony Espy <1533716@xxxxxxxxxxxxxxxxxx>]

** Also affects: ofono (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: ofono (Ubuntu RTM)
   Importance: Undecided
       Status: New

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

** Changed in: ofono (Ubuntu RTM)
       Status: New => In Progress

** Branch linked: lp:~morphis/ofono/ota9-suspend-fix

** Changed in: bluez (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: bluez (Ubuntu RTM)
       Status: New => Invalid

** Changed in: ofono (Ubuntu)
     Assignee: (unassigned) => Simon Fels (morphis)

** Changed in: ofono (Ubuntu RTM)
     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/1533716

Title:
  Delay of approx. 60 seconds when an outgoing call is innitiated by the
  IN CAR bluetooth system

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu RTM:
  Invalid
Status in ofono package in Ubuntu RTM:
  In Progress

Bug description:
  My system:

  current build number: 228
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-01-13 08:28:26
  version version: 228
  version ubuntu: 20160113
  version device: 20160108-efc96d8
  version custom: 20151111--36-46-vivid

  Since several days (not weeks, so something has changed in the last
  couple days!) I have the following situation with my BQ 4.5 in my car.
  When I initiate a call from the IN CAR system (where my phone is
  connected to) I experience sometimes the normal behaviour that the
  call is directly established.

  Sometimes nothing happens. The call is not established and my in car system says that the attempt to carry out a call has failed (this message comes after approx. 15 seconds after initiation of the call).
  Then approx. 60 seconds after the initiation of the call the call is all of a sudden established (without any further interaction). I currently was not able to find a logic in this. Here my "log"-file of what I did today:

  -----

  13.01.2016

  9:00 h call initiated from car, call directly established
  9:03 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established
  9:06 h call initiated from car, call directly established
  9:09 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established

  9:26 h New pairing between phone and car, retry

  9:30 h call initiated from car, call directly established
  9:33 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established
  9:36 h call initiated from car, call directly established
  9:39 h call initiated from car (phone book), approx. 60 sec. delay between initiation and call being established
  9:42 h call initiated from car, call directly established
  9:45 h call initiated from car, call directly established (this time again via phone book)
  9:48 h call initiated from car (via voice command), approx. 60 sec. delay between initiation and call being established
  9:52 h call initiated from phone itself, call established and correctly routed via car speaker

  I have added the syslog, upstart-files to the bug report for further
  analysis.

  Uranicus

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