Adding the mvno_* fields is certainly recommended if possible, as I have seen instances where there were multiple APNs that were provisioned that could be used to provide a mobile data connection, but had differing MMS attributes, which left MMS broken if the wrong was activated by NM.
Also, it's interesting that APN mentioned in comment #3 works, as it specifies a 'Password', whereas the official settings from giffgaff specify that the password should be blank. See the related bug #1435776 which describes a NM regression in Vivid where APNs that specify a 'Username' without a corresponding 'Password' cause NM to throw a 'no- secrets' error and fail to be activated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434605 Title: [APN] giffgaff APNs don't have the proper 'mvno' fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1434605/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
