Dialer app reports "No network" even though cellular is connected

Bug #1442962 reported by Michał Sawicz
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
Bill Filler
dialer-app
Fix Released
Undecided
Unassigned
telepathy-ofono
Fix Released
Undecided
Tiago Salem Herrmann
dialer-app (Ubuntu)
Fix Released
Critical
Tiago Salem Herrmann
telepathy-ofono (Ubuntu)
Fix Released
Critical
Tiago Salem Herrmann
Vivid
Fix Released
Critical
Tiago Salem Herrmann

Bug Description

current build number: 165
device name: m75
channel: ubuntu-touch/vivid-proposed
last update: 2015-04-08 05:43:13
version version: 165

It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work.

When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again):

     Account: ofono/ofono/account0
Display Name: Nju
     Enabled: enabled
        Icon: im-ofono
    Connects: automatically
     Service: ofono

Presences:
   Automatic: available (2) ""
     Current: offline (1) ""
   Requested: available (2) "online"
    Changing: yes

      (string) modem-objpath = /ril_0

Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone).

Please let me know what else to collect when this happens again.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dialer-app 0.1+15.04.20150330-0ubuntu1
Uname: Linux 3.10.35+ armv7l
ApportVersion: 2.17-0ubuntu1
Architecture: armhf
Date: Sat Apr 11 22:34:04 2015
InstallationDate: Installed on 2015-04-08 (3 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203)
SourcePackage: dialer-app
SystemImageInfo:
 current build number: 165
 device name: m75
 channel: ubuntu-touch/vivid-proposed
 last update: 2015-04-08 05:43:13
 version version: 165
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Michał Sawicz (saviq) wrote :

Just realized this also means I don't get incoming calls. :|

description: updated
Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Michał Sawicz (saviq) wrote :

$ ps aux | grep telepathy-ofono
phablet 1654 0.0 0.3 57612 6900 ? Sl kwi12 0:00 /usr/lib/telepathy/telepathy-ofono

So it's running, but did not get online.

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Michał Sawicz (saviq) wrote :

<tiagosh> Also, after that, kill tp-ofono and check what happens.
Nothing happened, it remained off even when I launched dialer-app.

$ mc-tool reconnect ofono/ofono/account0
Doesn't help either.

What finally helped was killing mission-control-5 and triggering it again.

Bill Filler (bfiller)
Changed in telepathy-ofono (Ubuntu):
importance: Undecided → Critical
Changed in dialer-app (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in telepathy-ofono (Ubuntu):
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in canonical-devices-system-image:
importance: Undecided → Critical
assignee: nobody → Bill Filler (bfiller)
milestone: none → ww17-2015
Revision history for this message
Michał Sawicz (saviq) wrote :

It is possible that my second ril account ($HOME rsynced from krillin) was triggering this. I've now removed it and will report back if that changed anything.

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

I noticed my device was in the same bad state this morning. I flashed it yesterday and I had only one account, so I assume it is probably not related to your $HOME synced from another device. I wonder if this is only happening after a long deep sleep over night.

Revision history for this message
Michał Sawicz (saviq) wrote : Re: [Bug 1442962] Re: Dialer app reports "No network" even though cellular is connected

W dniu 23.04.2015 o 17:16, Tiago Salem Herrmann pisze:
> I noticed my device was in the same bad state this morning. I flashed it
> yesterday and I had only one account, so I assume it is probably not
> related to your $HOME synced from another device. I wonder if this is
> only happening after a long deep sleep over night.

That's likely, it was always happening to me in the afternoon after I've
not used the phone for a few hours. I don't get it in the morning since
I'm usually charging overnight.

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

Next time you reproduce the issue, can you try reconnecting with "mc-tool reconnect ofono/ofono/account0" and then grab the following output?

dbus-send --print-reply --type=method_call --dest=org.freedesktop.Telepathy.AccountManager /org/freedesktop/Telepathy/debug org.freedesktop.Telepathy.Debug.GetMessages > mission_control.log

Revision history for this message
Michał Sawicz (saviq) wrote :

Here you go, mc-tool reconnect didn't change anything.

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

Thanks, the reconnect command was just to add some useful information to the log output.
Can you also provide the output of the following command?

dconf read /org/gnome/empathy/use-conn

Also, do you usually disable wifi/data overnight?

Revision history for this message
Michał Sawicz (saviq) wrote :

W dniu 27.04.2015 o 19:32, Tiago Salem Herrmann pisze:
> Thanks, the reconnect command was just to add some useful information to the log output.
> Can you also provide the output of the following command?
>
> dconf read /org/gnome/empathy/use-conn

I will next time I notice the issue.

> Also, do you usually disable wifi/data overnight?

Not actively, although WiFi sometimes gets disconnected as signal is low
in my bedroom. But as said before, this actually rarely happens
overnight, more often it happens in the afternoon after I leave it be
for a few hours.

Revision history for this message
Michał Sawicz (saviq) wrote :

> dconf read /org/gnome/empathy/use-conn

That's "false".

Revision history for this message
Michał Sawicz (saviq) wrote :

One more misson_control.log

Revision history for this message
Michał Sawicz (saviq) wrote :

And one more, after toggling use-conn.

Changed in canonical-devices-system-image:
milestone: ww17-2015 → ww21-2015
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

So, the problem here is that mission-control now uses an internal account property (always_dispatch) to control the account availability when there is no network. Previously this behavior was completely disabled with a dconf key, which was triggered by the ofono-setup script (the one responsible for creating the accounts during startup)

Unfortunately there is no way to set the always_dispatch property via mc-tool, so it make it impossible to continue using ofono-setup to create the accounts. After a discussion with boiko we agreed the approach taken by jolla with telepathy-ring was the right way to go. They have a mission-control plugin that provisions the accounts and also set all the required properties (including always_dispatch=true). This approach will avoid having duplicate accounts (a bug we fixed some weeks ago) and make sure we will always have the right number of accounts (one for each sim slot).

The plugin is in a separate package as it only makes sense to have it installed on devices with ril modems, this way it can be pulled by another package (not sure which yet) for each specific device as needed.

Changed in canonical-devices-system-image:
milestone: ww21-2015 → ww22-2015
Bill Filler (bfiller)
Changed in canonical-devices-system-image:
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dialer-app (Ubuntu):
status: New → Confirmed
Changed in telepathy-ofono (Ubuntu):
status: New → Confirmed
Changed in telepathy-ofono (Ubuntu):
status: Confirmed → In Progress
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Changed in canonical-devices-system-image:
status: In Progress → Fix Released
Changed in telepathy-ofono (Ubuntu Vivid):
importance: Undecided → Critical
status: New → Confirmed
status: Confirmed → In Progress
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in dialer-app:
status: New → Confirmed
Changed in telepathy-ofono:
assignee: nobody → Tiago Salem Herrmann (tiagosh)
status: New → In Progress
Changed in dialer-app (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-ofono - 0.2+15.10.20150603-0ubuntu1

---------------
telepathy-ofono (0.2+15.10.20150603-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Tiago Salem Herrmann ]
  * Set account display name in gsettings if empty. (LP: #1460111)

 -- CI Train Bot <email address hidden> Wed, 03 Jun 2015 19:28:00 +0000

Changed in telepathy-ofono (Ubuntu):
status: In Progress → Fix Released
Bill Filler (bfiller)
Changed in dialer-app:
status: Confirmed → Fix Released
Changed in dialer-app (Ubuntu):
status: Triaged → Fix Released
Changed in telepathy-ofono:
status: In Progress → Fix Released
Changed in telepathy-ofono (Ubuntu Vivid):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.