Wrong APN selected so MMS stopped working

[Pat McGowan]

On two phones connected to AT&T, got recent rc-proposed updates, at some point between 3/30 and 4/6 the phone started to select the wrong APN, one which did not support MMS only internet. These phones have worked with MMS reliably for over a year.
Rebooting the phone does not fix it.
One phone has been just getting updates for a year the other I had flashed last week.

Explicitly selecting the correct preferred APN makes them work again.

My concern is something changed in the logic or database on the device to change the behavior.

Krillin rc-proposed r306
Arale rc-proposed r299

[Pat McGowan (pat-mcgowan)]

output of list-contexts from the krillin, the sim on ril_1 is not active

http://pastebin.ubuntu.com/15660258/

[Tony Espy (awe)]

Just tested with krillin ( rc/bq-aquaris.en #48 ) plus a single AT&T SIM. Made sure to clear all of the 'Preferred' flags and rebooted. To do this, as root:

# stop network-manager
# stop ofono
# cd /var/lib/ofono/<IMSI>/
# vi gprs

( change any 'Preferred=true' -> 'Preferred=false' )

# reboot

I see in the log that NM finds the three contexts in order, and then tries context3 first always. I rebooted twice and the same thing always happens:

17:16:48 NetworkManager: <info> SCPlugin-Ofono: found internet context 'ATT Nextgenphone' (context1)
17:16:48 NetworkManager: <info> SCPlugin-Ofono: update_connection_setting_from_context: name:ATT Nextgenphone, path:context1, id:/310410833791757/context1, uuid: 71c1fc6d-6992-1120-b348-990f150dae3d
17:16:48 NetworkManager: <info> SCPlugin-Ofono: found internet context 'ATT Phone' (context2)
17:16:48 NetworkManager: <info> SCPlugin-Ofono: update_connection_setting_from_context: name:ATT Phone, path:context2, id:/310410833791757/context2, uuid: fe79bba6-614c-401c-d83b-1e8f52153ed0
17:16:48 NetworkManager: <info> SCPlugin-Ofono: found internet context 'ATT WAP' (context3)
17:16:48 NetworkManager: <info> SCPlugin-Ofono: update_connection_setting_from_context: name:ATT WAP, path:context3, id:/310410833791757/context3, uuid: 499fc259-e7ce-9ecc-bc73-8a4f40d888b6
17:16:48 NetworkManager: <info> SCPlugin-Ofono: found internet context 'T-Mobile GPRS' (context2)
17:16:48 NetworkManager: <info> SCPlugin-Ofono: update_connection_setting_from_context: name:T-Mobile GPRS, path:context2, id:/310260006686790/context2, uuid: 0fc0650f-0763-ee7d-f968-936a08469368
17:17:34 NetworkManager: <info> Auto-activating connection '/310410833791757/context3'.
17:17:34 NetworkManager: <info> Activation (ril_0) starting connection '/310410833791757/context3'
17:17:34 NetworkManager: <info> (/ril_0): activating context /ril_0/context3

It shouldn't be too hard to re-flash a previous rc prior to 48 to see if this is a regression caused by OTA10.

[Tony Espy (awe)]

Re-tested krillin with stable #27 ( OTA-8 ), and got the exact same behavior. Also went much further back to stable #21 ( almost a year-to-the-date ) and same behavior, ATT WAP is chosen yet again.

The only difference between our devices is that you have a non-working T-Mobile SIM present, and I don't, but that really should make no difference in the ordering of NM's connection attempts for a single SIM/modem.

The contexts are read from ofono in order ( context1, context2, context3 ), and then NM always seems to work it's way through the list in reverse order ( ie. it always tries context3 aka ATT WAP first ).

It could be that ATT WAP was always failing to connect for you, thus you were always ending up with context2 ( ATT Phone ) as the working APN, and that for some reason ATT WAP now works? No idea, but the NM still appears to be working the same across multiple versions.

[Launchpad Janitor (janitor)]

[Expired for ofono (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]