touch-packages team mailing list archive

[Launchpad Bug Tracker <1512851@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package dialer-app -
0.1+16.04.20151207-0ubuntu1

---------------
dialer-app (0.1+16.04.20151207-0ubuntu1) xenial; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk.

  [ Tiago Salem Herrmann ]
  * Disable call button while telepathy is not ready. (LP: #1512851)

 -- Tiago Salem Herrmann <tiago.herrmann@xxxxxxxxxxxxx>  Mon, 07 Dec
2015 17:54:37 +0000

** Changed in: dialer-app (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1512851

Title:
  No network error when making call

Status in Canonical System Image:
  Fix Committed
Status in dialer-app package in Ubuntu:
  Fix Released

Bug description:
  When the dialer app is not running and I get redirected to it in order
  to make a call, the first time I hit the "call" button I invariably
  get the error message: "no network" even though the phone is connected
  to the GSM network. (My phone has the language set to Norwegian, so I
  am guessing this is the English equivalent to the message I get.)

  Here is what I do in detail: 
  - I choose a number from the contacts list
  - I hit the phone icon next to the number to make a  call, 
  - the dialer app screen opens
  - I hit the "call" button, 
  - message "no network"

  The status bar at the top shows the phone has a GSM connection the
  whole time.

  When I try again a couple of seconds later, the call gets placed
  normally.

  The same thing happens when switching from the messaging app to the
  dialer in order to call the person I have been texting.

  However, if I wait a moment after entering the dialer before pressing
  the "call" button, everything runs normally.

  If the dialer-app is already active in the background when the
  redirection happens, the bug does not occur.

  Some kind of slow start issue? Screen appearing before the app is
  actually ready to take the command?

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