ubuntu-phonedations-bugs team mailing list archive
-
ubuntu-phonedations-bugs team
-
Mailing list archive
-
Message #00381
[Bug 1437200] [NEW] In case there is no type field in APN, we should provision for all types
Public bug reported:
In case there there is no "type" field for an entry in the Android APN
DB, we should provision all possible types for that entry. In those
cases, the type is set to PhoneConstants.APN_TYPE_ALL in the Android
code. See:
http://androidxref.com/4.4.2_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcTracker.java#844
http://androidxref.com/4.4.2_r1/xref/frameworks/base/telephony/java/com/android/internal/telephony/PhoneConstants.java#110
http://androidxref.com/5.1.0_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/ApnSetting.java#307
As PhoneConstants.APN_TYPE_ALL="*", in case we find a type="*" in the DB
we must treat it also as an entry valid for all types (I have actually
seen type="*" in a Moto G APN DB).
** Affects: ofono (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In case there there is no "type" field for an entry in the Android APN
DB, we should provision all possible types for that entry. In those
cases, the type is set to PhoneConstants.APN_TYPE_ALL in the Android
code. See:
http://androidxref.com/4.4.2_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcTracker.java#844
http://androidxref.com/4.4.2_r1/xref/frameworks/base/telephony/java/com/android/internal/telephony/PhoneConstants.java#110
- As PhoneConstants.APN_TYPE_ALL="*", in case we find a type="*" filed in
- the DB we must treat it also as an entry valid for all types (I have
- actually seen type="*" in a Moto G APN DB).
+ As PhoneConstants.APN_TYPE_ALL="*", in case we find a type="*" in the DB
+ we must treat it also as an entry valid for all types (I have actually
+ seen type="*" in a Moto G APN DB).
** Description changed:
In case there there is no "type" field for an entry in the Android APN
DB, we should provision all possible types for that entry. In those
cases, the type is set to PhoneConstants.APN_TYPE_ALL in the Android
code. See:
http://androidxref.com/4.4.2_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcTracker.java#844
http://androidxref.com/4.4.2_r1/xref/frameworks/base/telephony/java/com/android/internal/telephony/PhoneConstants.java#110
+ http://androidxref.com/5.1.0_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/ApnSetting.java#307
+
As PhoneConstants.APN_TYPE_ALL="*", in case we find a type="*" in the DB
we must treat it also as an entry valid for all types (I have actually
seen type="*" in a Moto G APN DB).
--
You received this bug notification because you are a member of Ubuntu
Phonedations bugs, which is subscribed to ofono in Ubuntu.
https://bugs.launchpad.net/bugs/1437200
Title:
In case there is no type field in APN, we should provision for all
types
Status in ofono package in Ubuntu:
New
Bug description:
In case there there is no "type" field for an entry in the Android APN
DB, we should provision all possible types for that entry. In those
cases, the type is set to PhoneConstants.APN_TYPE_ALL in the Android
code. See:
http://androidxref.com/4.4.2_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/DcTracker.java#844
http://androidxref.com/4.4.2_r1/xref/frameworks/base/telephony/java/com/android/internal/telephony/PhoneConstants.java#110
http://androidxref.com/5.1.0_r1/xref/frameworks/opt/telephony/src/java/com/android/internal/telephony/dataconnection/ApnSetting.java#307
As PhoneConstants.APN_TYPE_ALL="*", in case we find a type="*" in the
DB we must treat it also as an entry valid for all types (I have
actually seen type="*" in a Moto G APN DB).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1437200/+subscriptions
Follow ups
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Pat McGowan, 2015-06-11
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Launchpad Bug Tracker, 2015-04-14
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Launchpad Bug Tracker, 2015-04-13
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Launchpad Bug Tracker, 2015-04-01
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Tony Espy, 2015-04-01
-
[Bug 1437200] Re: In case there is no type field in APN, we should provision for all types
From: Alfonso Sanchez-Beato, 2015-03-27
-
[Bug 1437200] [NEW] In case there is no type field in APN, we should provision for all types
From: Alfonso Sanchez-Beato, 2015-03-27
References