@Matthew
Now for your comment #6.
The initial design looks good, although as there's been a recent push to
implement MMS, I think there are some adjustments needed.
1. Each APN has a defined "Name", which would be helpful to display to
the user. For instance, the default APN for my T-Mobile account in the
US is:
"Name" - "T-Mobile US"
"APN" - epc.tmobile.com
Also, it might be helpful to include the MCC ( mobile country code ) and
MNC ( mobile network code ).
2. Currently the only protocol that's supported for Mobile data
connections is IPv4. This will change, but I wonder if we should either
hide this field for now, or make it read-only until the underlying
support changes?
3. The MMS fields are close, but not quite accurate. The attribute in
apns-conf.xml are: mmsc, mmsproxy, and mmsport. oFono exposes two
properties: "MessageCenter" and "MessageProxy" ( which combines mmsproxy
and mmsport ).
4. We're still trying to determine how we rectify the difference between
ofono contexts and Android's APN db. First, the apns-conf.xml file
allows multiple types ( eg. "default,supl,mms" ), however there's no way
to express this via the current ofono properties exposed for contexts.
The current idea is that a context that supports multiple types in apns-
conf.xml will be created with TYPE_ANY in ofono, and if it happens to
support MMS, then the requisite MessageCenter and MessageProxy
properties will also be set.
5. Turns out that there are ~100 or so APNs defined with "proxy" and
"port" attributes that are used to configure what I'm guessing is a
required HTTP proxy. Again, we have no way currently to expose these
attributes via ofono properties.
6. Some APNs also expose an "authentication-type" attribute that can be:
"None", "PAP", "CHAP", or "PAP or CHAP". It appears that this is only
used by four APNs ( in Argentina ).
7. Although we currently only provision a single Internet context/APN
for a specific SIM, we've decided that it'd be best to provision all of
the possible APNs for the given SPN/MNC/MCC combination, pick a default
( which is the first that supports Internet in the list ), and then
allow the user to select any of the APNs that have been provisioned.
This will require us to add an additional "Selected" property. The AOSP
Settings dialog for "Access Point Names" uses a radio-button style
interface.
8. AOSP allows a user to manually create a new APN.
9. AOSP also allows a user to reset their APN configuration to it's
default ( ie. undo any changes made ).
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1225174
Title:
Cellular Settings -- No way to edit APN
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1225174/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
