© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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.