touch-packages team mailing list archive

[Michael Terry <michael.terry@xxxxxxxxxxxxx>]

OK, unity8 has the following piece of code that gets run when the user
presses the green call button:

            if (shell.locked && callManager.hasCalls) {
                // We just received an incoming call while locked.  The
                // indicator will have already launched dialer-app for us, but
                // there is a race between "hasCalls" changing and the dialer
                // starting up.  So in case we lose that race, we'll start/
                // focus the dialer ourselves here too.  Even if the indicator
                // didn't launch the dialer for some reason (or maybe a call
                // started via some other means), if an active call is
                // happening, we want to be in the dialer.
                startLockedApp("dialer-app")
            }

This tries to focus the already-focused dialer-app.  Due to a bug in
qtmir (around line 412 of application_manager.cpp), focusing an already
focused app will do a suspend/resume cycle on that app.  But Gerry says
that code is short-lived and not worth fixing.

So he's asked that we guard the call in unity8 instead, which isn't a
bad thing to do regardless.  So that's what I'll do.  Working on a
branch.

** No longer affects: dialer-app (Ubuntu)

** No longer affects: dialer-app (Ubuntu RTM)

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

** Changed in: dialer-app
       Status: New => Invalid

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

Title:
  [Call]The call interface sometimes disappears when making emergency
  call

Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  This is the public version of the following bug:
  https://bugs.launchpad.net/barajas/+bug/1393641

  After debugging seems the issue is that the application is getting
  deactivated and then activated (via Qt.application.active) when making
  a call in greeter (emergency) mode. This is causing problems for the
  app as it pops pages when it gets deactivated and causes the bug
  sometimes. The underlying problem is that this signal should not be
  occuring when the app is clearly in the foreground. It doesn't happen
  when not in greeter mode.

  An easy way to test is to install telepathy-ofono deb which is
  attached and set a fake emergency number to allow you to dial a normal
  number in emergency mode to help test by running this command at the
  shell:

  mc-tool set ofono/ofono/account0
  string:fakeEmergencyNumber=<yourNumber>

  Then adding console.log() to the applicationActive signal in dialer-
  app.qml will verify. When pressing the call button the app is
  deactivated then reactivated.

  Steps to reproduce:
  1) install attached telephathy-ofono deb and reboot
  2) run
  mc-tool set ofono/ofono/account0 string:fakeEmergencyNumber=<yourNumber>
  and then follow secondary instructions (if any)
  3) lock phone
  4) press emergency call button
  5) dial <yourNumber> which will be a fake emergency call
  6) press the call button
  7) sometimes you will see a blank Emergency Call page after you press the call button, and when it works you will see the live call page
  8) adding debug to dialer-app.qml will show the active=false then active=true behavior after performing step 6.

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