I think it is perfectly fine to add operators that use the same MCC/MNC
code even if we cannot discriminate with the mvno_* fields. The list of
APN choices will grow, but NetworkManager is supposed to handle that
properly and eventually will get to the right one.

About the position in the file, although I understand that putting it at
the end might resolve more easily conflicts, I think it is better to
order by MCC/MNC, because that is the convention followed by all DBs.
Note that when we merge operators from an updated DB, we might found
that an operator we added at the end of the file might have already been
added to the DB we are updating from, and in fact putting them in order
would be the way to detect that and avoid duplicates. Besides, afaik we
do not have a "master" upstream DB, instead we have merged from
different DBs, so there will be always conflicts.

For the concrete case of giffgaff, I've found in my Moto G DB:

    <apn carrier="giffgaff"
         mcc="234"
         mnc="10"
         apn="giffgaff.com"
         authtype="1"
         user="giffgaff"
         password="password"
         mmsc="http://mmsc.mediamessaging.co.uk:8002";
         mmsproxy="193.113.200.195"
         mmsport="8080"
         mvno_type="spn"
         mvno_match_data="giffgaff"
         preloaded="true"
    />

We can take mvno_type and mvno_match_data from here.

However, this entry has a different MMS proxy to the one specified in
http://community.giffgaff.com/t5/Settings-for-your-device/Internet-and-
MMS-settings-APN-guide/ta-p/3489121#faq_no_6 . This is the problem with
these DBs, none of them seem to be in a completely sane state :-/.
After seeing that, can we trust the mvno_* values for giffgaff?
Probably, but...

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to