Delay of approx. 60 seconds when an outgoing call is innitiated by the IN CAR bluetooth system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
John McAleely | ||
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
bluez (Ubuntu RTM) |
Invalid
|
Undecided
|
Unassigned | ||
ofono (Ubuntu) |
Fix Released
|
Critical
|
Simon Fels | ||
ofono (Ubuntu RTM) |
Fix Released
|
Critical
|
Simon Fels |
Bug Description
My system:
current build number: 228
device name: krillin
channel: ubuntu-
last update: 2016-01-13 08:28:26
version version: 228
version ubuntu: 20160113
version device: 20160108-efc96d8
version custom: 20151111-
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
Related branches
- Tony Espy: Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 618 lines (+505/-2)10 files modifiedMakefile.am (+7/-2)
configure.ac (+5/-0)
debian/changelog (+11/-0)
debian/rules (+6/-0)
include/wakelock.h (+100/-0)
plugins/android-wakelock.c (+212/-0)
src/main.c (+4/-0)
src/ofono.h (+3/-0)
src/voicecall.c (+6/-0)
src/wakelock.c (+151/-0)
tags: | added: lt-blocker |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in ofono (Ubuntu): | |
status: | New → Confirmed |
Changed in ofono (Ubuntu RTM): | |
status: | New → In Progress |
Changed in bluez (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in bluez (Ubuntu RTM): | |
status: | New → Invalid |
Changed in ofono (Ubuntu): | |
assignee: | nobody → Simon Fels (morphis) |
Changed in ofono (Ubuntu RTM): | |
assignee: | nobody → Simon Fels (morphis) |
Changed in ofono (Ubuntu RTM): | |
status: | In Progress → Fix Committed |
importance: | Undecided → Critical |
Changed in ofono (Ubuntu): | |
importance: | Undecided → High |
importance: | High → Critical |
status: | Confirmed → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
tags: | removed: lt-blocker |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
I can reproduce the problem with a Garmin Nüvi and latest krillin rc-proposed. It seems that the call is not initiated when the device is suspended. As soon as the device wakes up, the call starts.