Mobile data doesn't automatically connect after leaving wifi

I confirm this behaviour the device frequently doesn't switch to cellular data automatically.

Observed on
current build number: 217
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.en

and previous builds.

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

@Jean-Baptiste

Do you end up with the same network-menu as shown in screenshot included with comment #1?

The network icon shown on the menu indicates that WiFi is off, and no mobile data connection.

If you can reproduce again, can you please include the output of these commands:

% /usr/share/ofono/scripts/list-modems -p

% nmcli d

Also can you please attach the syslog too?

@Dubstar_04

Can you please let us know what device you're using? Also, in addition to the information requested in comment #4, could you please include details about what software you're running on the device? Please either grab a screenshot of Settings::About This Phone::OS, or the output from the command 'system-image-cli -i'.

Yes, exactly same screenshot than comment 1. Here is syslog from when I reproduced, I forgot to save list-modems and nmcli. I'll do next time I've this problem.

@awe

I am currently using an MX4 on OTA8.5. Next time i experience the issue I will try to capture the required logs.

Logs Attached.

I created 2 sets of logs.

- one with wifi on.
- one with wifi off.

Hopefully these will help. if there is anything else I can do to help debug please let me know.

Thanks,

Dan

syslog, list-modems -p and nmcli d when the device didn't reconnect to cellular data and no wifi connection was available.

This happened to me on Bq E4.5 for the first time now after I upgraded from OTA-8.5 to OTA-9.

Silo 032 has long pending networking fixes that now have seen more recent work and the silo might be in shape for landing.

As an interested party in this networking related bug (among many), could you please give 032 a whirl on vivid-overlay (xenial also available) and test your networking in general in addition to this particular bug? If we see no regressions - and we do see fixes - we could try landing the silo.

Upgrade with 'citrain device-upgrade 32 0000'.

I hit the same bug :)
Krillin, rc-proposed, r245

here's list-modems output http://pastebin.ubuntu.com/14866296/

and nmcli d reports
DEVICE TYPE STATE CONNECTION
ril_0 gsm unavailable --
ril_1 gsm unavailable --
ifb0 ifb unmanaged --
ifb1 ifb unmanaged --
lo loopback unmanaged --
ip6tnl0 unknown unmanaged --
sit0 unknown unmanaged --
tunl0 unknown unmanaged --

In all cases list-modems show something similar to:

[ org.ofono.ConnectionManager ]
        RoamingAllowed = 0
        Powered = 1
        Bearer = hspa
        Attached = 0

The modem is not attached, so no connection is possible. But, we are able to detect a bearer, which is suspicious. It might be ofono wrongly reporting a detached state, when connection to cellular might be actually possible.

If there is a Qt side to this bug, the silo 32 has a certain probability of fixing it.

Hmm, nope, I've occasionally seen this both with and without silo 32 on my daily phone.

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

If anybody is able to reproduce this and does not mind making the system image writable, please try downloading and installing

http://people.canonical.com/~abeato/debug/ofono_1.17-debug-attachment.deb

AND modify /etc/init/ofono.override changing line

exec ofonod -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

to

exec ofonod -d -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap

Finally I was able to reproduce this issue with traces. syslog attached.

If anybody else is able to reproduce this, it would be great to have the output of

/usr/share/ofono/scripts/list-contexts

additionally to list-modems and nmcli output.

This is how the bug is apparently produced:

1. NM asks ofono to activate a context
2. Network is gone just a moment after that and modem detaches
3. Attached property is set to FALSE by ofono, then it tries to deactivate activated contexts, but there are none (no response yet from the request sent in step 1)
4. A few seconds later, the context is activated. Obviously the modem has registered again, but no event has triggered for that yet.
5. Modem says it is registered, right AFTER it has activated the context (which is maybe not the most correct sequence of events). Ofono detects that there are active context and it assumes it asked these context to close when it set Attached to FALSE. But that is not true as there were no active context when we did that. We do not change Attached property because ofono waits for old contexts to close before setting Attached to TRUE.
6. We stall until the active context is finally closed by some external event, which might happen hours later. While we are in this situation there is an active context, but probably it is not used by NM as it does nothing with ofono until Attached is TRUE. This last thing needs confirmation.

Fix for this in:

https://github.com/rilmodem/ofono/pull/238

Note: it is possible to still having some issues with connections. see bug #1565717 .

This is still happening for me.

Issue affect data connection if switching from one mobile operator to another. When connected to host network data connection is disabled by setting (to avoid extra charge) but is not reconnected when own network is available. Device Aquaris E5, OTA-11