** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
--
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 'mvn
No, it hasn't landed in RTM due to bug #1481456.
That said, it did land in wily, so I've updated the Ubuntu task to
FixReleased.
** Changed in: android (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Can we confirm if this has landed?
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Fix Committed
** Changed in: canonical-devices-system-image
Milestone: None => ww34-2015
** Changed in: canon
Testing Status visibility changes... please ignore.
--
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 abo
Changed both android tasks to FixCommited, as it's still not clear that
this fix was released a new android package for the vivid overlay PPA or
wily.
** Changed in: android (Ubuntu RTM)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member
** Changed in: android (Ubuntu)
Status: Fix Released => Fix Committed
--
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
** Changed in: android (Ubuntu)
Status: Fix Committed => Fix Released
--
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
** Also affects: android (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: android (Ubuntu RTM)
Status: New => Fix Released
** Changed in: android (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: canonical-devices-system-image
Importance: Unde
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
The AOSP apns file we used as reference:
https://android.googlesource.com/device/sample/+/master/etc/apns-full-
conf.xml
And as I talked on IRC, when updating the PR you can simply cherry-pick
and push a new version (as long it has the same change-id, it will just
create another patch revision).
Change submitted to gerrit with the APN checked by joc:
https://code-review.phablet.ubuntu.com/#/c/362/
--
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 t
Seems that the APN entry in comment #7 is fine, from joc's log:
Provisioning for MCC 234, MNC 10, SPN 'giffgaff',...
and he was able to start a data connection:
[ /ril_0/context1 ]
Active = 1
Name = giffgaff
Type = internet
MessageProxy = 82.132.254.1:8080
Finally, there is a
preloaded="true"
line in the giffgaff entry that I have no idea what is for. I have not
seen any reference to it in the AOSP code. Qualcomm specific maybe?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I think the right APN should be:
http://mmsc.mediamessaging.co.uk:8002";
mmsproxy="82.132.254.1"
mmsport="8080"
type="default,mms"
mvno_type="spn"
mvno_match_data="giffgaff"
/>
There are discrepancies between what we see in the DB and the setti
Alright, noticed AOSP had the same entry described by Alfonso here, so
just did a pull request to get that in sync.
Please review https://code-review.phablet.ubuntu.com/#/c/361/
Would be nice if we could get someone to test this.
** Changed in: android (Ubuntu)
Status: Incomplete => In Pr
On Thu, Mar 26, 2015 at 8:03 AM, Alfonso Sanchez-Beato
wrote:
> 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 ev
Another comment: it will be difficult to get somebody in an operator
that can answer the question about how to detect if it is the owner of
the SIM, unless the phone is sold directly by them.
One thing that should be pretty safe for MVNOs is to check the content
of EF_SPN SIM file and set:
mvno_t
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, al
Some points:
" This means that a user's device when initially provisioned ends up with all
five APNs."
Will this at least make it work for the user? Besides having extra APNs
that are not needed.
"What should have happened is that we should've discussed the details of
giffgaff's MVNO arrangement
Changing to incomplete because it's not clear what is the side effect of
having that entry in our database, and because we don't yet have the
values for the mnvo fields (atm we can either leave it this way or
remove it completely).
--
You received this bug notification because you are a member of
** Tags added: apn connectivity
--
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:
ht
** Changed in: android (Ubuntu)
Assignee: (unassigned) => Ricardo Salveti (rsalveti)
** Changed in: android (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
22 matches
Mail list logo
