@Selene Have you tried the same SIM in an Android or iOS device? If so, was it automatically provisioned?
Unfortunately, handling of MVNOs is tricky business. The apn database does have a way of handling MVNOs, but utilizing this support may require technical assistance from StraightTalk and/or the carriers that they have agreements with. Here's a quick re-cap of how things works... When we initially provision for GPRS/MMS, we call a plugin with the following pieces of information: - Mobile Country Code ( MCC ) - Mobile Network Code ( MNC ) - Service Provider Name ( SPN ) - Subscriber Identity ( IMSI ) - Group ID ( GID ) All of the above values are read from the SIM and passed into the provisioning plugin. The first two attributes ( MCC/MNC ) are used for normal matching. The latter three are matched against MVNO-specific attributes in the apns-conf.xml file. So if we could determine whether or not Straightalk programs their SIMs with a valid SPN or GID, then we could potentially create records for Straightalk. That said... Straightalk's own documentation is pretty clear that a user needs to update their phones settings manually in order for GPRS to work. They also are pretty clear that MMS might now work even after doing so... http://www.straighttalkbyop.com/program.php ** Changed in: android-src-vendor (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351434 Title: APN info for Straight Talk via AT&T To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-src-vendor/+bug/1351434/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
