[regression] Ubuntu touch cannot get GSM signal if not joined to a WLAN network

Bug #1252737 reported by Timo Leppiniemi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
telepathy-mission-control (Ubuntu)
Fix Released
Critical
Didier Roche-Tolomelli
telepathy-ofono (Ubuntu)
Invalid
Critical
Tiago Salem Herrmann

Bug Description

Ubuntu Touch release information:

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04 (r24)

Ofono: version 1.12+bzr6839-0ubuntu1
network-manager: version 0.9.8.4-0ubuntu3

Bug might also be in network-manager.

Bug is also present in r24

Handset used: LGE Nexus 4

After updating from r22 to r23 phone could not get GSM signal. Rebooting phone did not make any difference.
Once wireless networking was enabled and phone has joined to a WLAN network phone get's signal.
If WLAN is enabled during boot and phone is able to join the network phone get GSM signal without any additional work.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Could you please attach the following:
- /var/log/syslog
- output of /usr/share/ofono/scripts/list-contexts
- output of /usr/share/ofono/scripts/list-modems

Revision history for this message
Tony Espy (awe) wrote :

My guess is that this is an indicator bug, as not much has changed in the core ofono code that would cause this.

Please attach the output of 'list-modems' both before *and* after connecting to Wi-Fi.

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

Attached file contains /var/log/syslog contents, phone booted and bug is "on"

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

Err! Disregard comment #3, I had WiFi on when phone rebooted!
See attached file on this comment, it has the right content.

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

Output of /usr/share/ofono/scripts/list-context

root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
    [ /ril_0/context1 ]
        Username =
        Protocol = ip
        Name = dna internet
        Settings = { }
        IPv6.Settings = { }
        Active = 0
        AccessPointName = internet
        Password =
        Type = internet

Output of /usr/share/ofono/scripts/list-modems

root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-modems
[ /ril_0 ]
    Features = sms gprs sim
    Emergency = 0
    Powered = 1
    Lockdown = 0
    Interfaces = org.ofono.MessageManager org.ofono.VoiceCallManager org.ofono.ConnectionManager org.ofono.NetworkTime org.ofono.SimManager
    Online = 0
    Model = Fake Modem Model
    Revision = M9615A-CEFWMAZM-2.0.1700.48
    Type = hardware
    Serial = 356489054005959
    Manufacturer = Fake Manufacturer
    [ org.ofono.MessageManager ]
    [ org.ofono.VoiceCallManager ]
        EmergencyNumbers = 08 000 999 110 112 911 118 119
    [ org.ofono.ConnectionManager ]
        Powered = 1
        Attached = 0
        Bearer = none
        RoamingAllowed = 1
    [ org.ofono.NetworkTime ]
    [ org.ofono.SimManager ]
        Retries =
        MobileCountryCode = 244
        FixedDialing = 0
        SubscriberNumbers = +358447733292
        PreferredLanguages = fi en sv
        BarredDialing = 0
        ServiceNumbers = [Numeropalvelu] = '118' [Asiakaspalvelu] = '+35844144044'
        CardIdentifier = 8935806120724027819
        LockedPins =
        MobileNetworkCode = 12
        SubscriberIdentity = 244121110862781
        Present = 1
        PinRequired = none

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

see attached file for /var/log/syslog content after enabling WiFi

root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
    [ /ril_0/context1 ]
        Username =
        Protocol = ip
        Name = dna internet
        Settings = { DomainNameServers=62.241.198.245,62.241.198.246, Method=static Netmask=255.255.255.192 Address=10.240.107.223 Interface=rmnet_usb0 Gateway=10.240.107.193 }
        IPv6.Settings = { }
        Active = 1
        AccessPointName = internet
        Password =
        Type = internet
root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-modems
[ /ril_0 ]
    Features = net sms gprs sim
    Emergency = 0
    Powered = 1
    Lockdown = 0
    Interfaces = org.ofono.CallVolume org.ofono.NetworkRegistration org.ofono.MessageManager org.ofono.VoiceCallManager org.ofono.ConnectionManager org.ofono.NetworkTime org.ofono.SimManager
    Online = 1
    Model = Fake Modem Model
    Revision = M9615A-CEFWMAZM-2.0.1700.48
    Type = hardware
    Serial = 356489054005959
    Manufacturer = Fake Manufacturer
    [ org.ofono.CallVolume ]
        Muted = 1
        SpeakerVolume = 0
        MicrophoneVolume = 0
    [ org.ofono.NetworkRegistration ]
        Status = registered
        Strength = 25
        Name = dna
        LocationAreaCode = 202
        Mode = auto
        MobileCountryCode = 244
        Technology = umts
        CellId = 1353457
        MobileNetworkCode = 12
    [ org.ofono.MessageManager ]
    [ org.ofono.VoiceCallManager ]
        EmergencyNumbers = 08 000 999 110 112 911 118 119
    [ org.ofono.ConnectionManager ]
        Powered = 1
        Attached = 1
        Bearer = none
        Suspended = 0
        RoamingAllowed = 1
    [ org.ofono.NetworkTime ]
    [ org.ofono.SimManager ]
        Retries =
        MobileCountryCode = 244
        FixedDialing = 0
        SubscriberNumbers = +358447733292
        PreferredLanguages = fi en sv
        BarredDialing = 0
        ServiceNumbers = [Numeropalvelu] = '118' [Asiakaspalvelu] = '+35844144044'
        CardIdentifier = 8935806120724027819
        LockedPins =
        MobileNetworkCode = 12
        SubscriberIdentity = 244121110862781
        Present = 1
        PinRequired = none

Revision history for this message
Tony Espy (awe) wrote :

@Timo

Thanks for the additional information. Also kudos for including the image # and package versions in your description. You wouldn't believe how many bug reports from co-workers none-the-less, that don't include this level of detail!

A couple more question...

1. Does the status bar show "No Signal"?

2. If you disable Wi-Fi, then reboot the phone and let it sit for ~5min, do you eventually see the signal bars show up?

Frankly, there's not much interesting in the syslog, however the output of 'list-modems' clearly shows that the modem has not yet been set online. This is the responsibility of telepathy-ofono. I've added a task for telepathy-ofono and will ping the developers tomorrow.

FYI, there hasn't yet been a new release of ofono since we released 13.10, so pretty sure it's not where the bug lies.

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

1. "No Signal" does not show up in the indicator bar until WiFi is switched on

2. When this started happening the maximum amount I've waited is around 10minutes, no signal

it seems like the modem is not there until WiFi is enabled. For example;

WiFi enabled:

root@ubuntu-phablet:/# /usr/share/ofono/scripts/scan-for-operators
Scanning operators on modem /ril_0...
[ /ril_0/operator/24412 ]
    Status = available
    Technologies = gsm
    MobileNetworkCode = 12
    Name = dna
    MobileCountryCode = 244

[ /ril_0/operator/24405 ]
    Status = forbidden
    Technologies = gsm
    MobileNetworkCode = 05
    Name = FI elisa
    MobileCountryCode = 244

[ /ril_0/operator/24491 ]
    Status = forbidden
    Technologies = gsm
    MobileNetworkCode = 91
    Name = FI SONERA
    MobileCountryCode = 244

Wifi not enabled phone rebooted:

root@ubuntu-phablet:/# /usr/share/ofono/scripts/scan-for-operators
Scanning operators on modem /ril_0...
Traceback (most recent call last):
  File "/usr/share/ofono/scripts/scan-for-operators", line 20, in <module>
    operators = netreg.Scan(timeout=100);
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Scan" with signature "" on interface "org.ofono.NetworkRegistration" doesn't exist

Another thing that resolves the issue is to run /usr/share/ofono/scripts/online-modem, just found out and tried

Revision history for this message
Timo Leppiniemi (timo-leppiniemi-d) wrote :

r25 still suffers from the same issue. Enabling WiFi and connecting to a wireless network or running /usr/share/ofono/scripts/online-modem resolves the issue.

Revision history for this message
Tony Espy (awe) wrote :

@Timo

Thanks, the fact that online-modem works confirms my suspicions that this is a telepathy-ofono problem.

Omer Akram (om26er)
Changed in telepathy-ofono (Ubuntu):
importance: Undecided → Critical
Changed in ofono (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Omer Akram (om26er) wrote :

Also to note is that when this issue happens telepathy-ofono is not running.

Tony Espy (awe)
Changed in telepathy-ofono (Ubuntu):
status: New → Confirmed
Changed in ofono (Ubuntu):
status: New → Invalid
summary: - Ubuntu touch cannot get GSM signal if not joined to a WLAN network
+ telepathy-ofono isn't automatically started, which prevents modem from
+ being onlined
summary: - telepathy-ofono isn't automatically started, which prevents modem from
- being onlined
+ [regression] Ubuntu touch cannot get GSM signal if not joined to a WLAN
+ network
Revision history for this message
Tony Espy (awe) wrote :

According to Tiago, this is due to a gsettings change. He suggests trying the following to resolve:

gsettings set im.telepathy.MissionControl.FromEmpathy use-conn false

Omer Akram (om26er)
no longer affects: ofono (Ubuntu)
Changed in telepathy-ofono (Ubuntu):
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

I debugged this issue a bit with Omer and it turns out the newest telepathy mission-control daemon is not respecting the use-conn key in gsettings.
This key tells mission-control to ignore the connection status from network-manager and load the telepathy connection managers (telepathy-ofono in this case) even if there is no network.

After some tests we found out that if you manually set the gsettings key while mission-control is running [1] you will get telepathy-ofono launched correctly, but if you restart the phone, even if the key is set to the correct value, mission-control will not work, so you have to manually set it again during runtime.

Debugging a bit more, I found out that mission-control reads the correct value during startup and after that the value is set to "true" again (which is the default value). [2]

I am assuming this is the change that actually introduced the bug, but I am not completely sure:
http://cgit.collabora.com/git/freedesktop.org-mirror/telepathy/telepathy-mission-control.git/commit/?id=e6974e3dac274982dedcb5451106473dea3294fd

[1] gsettings set im.telepathy.MissionControl.FromEmpathy use-conn false
[2] MC_DEBUG=all G_MESSAGES_DEBUG=all /usr/lib/telepathy/mission-control-5 2>&1 | grep use_conn

Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

workarounded in telepathy-mission-control 5.16.0-1ubuntu2

Changed in telepathy-mission-control (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Didier Roche (didrocks)
status: New → Fix Committed
Ursula Junque (ursinha)
tags: added: avengers regression
tags: added: r24
Revision history for this message
Tiago Salem Herrmann (tiagosh) wrote :

I can confirm the upstream patch fixes the problem.

https://bugs.freedesktop.org/attachment.cgi?id=89821

Revision history for this message
Ricardo Salveti (rsalveti) wrote :

Fixed in r32 (telepathy-mission-control-5 1:5.16.0-1ubuntu3).

Changed in telepathy-ofono (Ubuntu):
status: Confirmed → Invalid
Changed in telepathy-mission-control (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Sayantan Das (sayantan13) wrote :

Hi there, I am facing a very similar issue in Google Nexus 5 on images starting #50 on the utopic channel. The below output is from image #87.

root@ubuntu-phablet:~# /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
root@ubuntu-phablet:~# /usr/share/ofono/scripts/list-modems
[ /ril_0 ]
    Features = sim
    Revision = M8974A-1.0.25.0.23
    Manufacturer = Fake Manufacturer
    Powered = 1
    Interfaces = org.ofono.SimManager org.ofono.VoiceCallManager
    Lockdown = 0
    Type = hardware
    Online = 1
    Emergency = 0
    Serial = 358240053465159
    Model = Fake Modem Model
    [ org.ofono.SimManager ]
        Present = 0
    [ org.ofono.VoiceCallManager ]
        EmergencyNumbers = 08 000 999 110 112 911 118 119

root@ubuntu-phablet:~# /usr/share/ofono/scripts/scan-for-operators
Scanning operators on modem /ril_0...
Traceback (most recent call last):
  File "/usr/share/ofono/scripts/scan-for-operators", line 20, in <module>
    operators = netreg.Scan(timeout=100);
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Scan" with signature "" on interface "org.ofono.NetworkRegistration" doesn't exist

Revision history for this message
Sayantan Das (sayantan13) wrote :

attaching syslogs for nexus 5

Revision history for this message
Sayantan Das (sayantan13) wrote :

Found the error. It being tracked by another bug.

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.