(This is consistent with Google's APNs config.)
These changes have been thoroughly tested on the Telus mobile network.
More Info...
Telus (from Western Canada) doesn't yet fully support IPV6. As a
result, Telus customers trying to run LineageOS won't have mobile data.
Telus users (including myself) have been running into this
problem for years. For example...
https://www.reddit.com/r/LineageOS/comments/hyg5hw/change_apn_settings/
Change-Id: I5085c9463e26da7101106525550f1efef2474c5b
* Since it's unclear what the numbers are, make it easier to add a new
apn by specifying the possible values in a comment at the top
* Also add missing copyright (verified, first LineageOS commit was
indeed 2016)
Change-Id: Icaf292fd79a903bcf9ef5a3813f6288cffc468ad
* The correct string is "IP", not "IPV4"
* Other possible values are "IPV6" or "IPV4V6"
* Source: prebuilts/sdk/30/public/api/android.txt
Lines: 46832-46834
Change-Id: I3d4729b829f87a4d7ab83584d1aed01d87e10fd2
* The parsing of apns-conf.xml happens in
packages/providers/TelephonyProvider/src/com/android/providers/telephony/
TelephonyProvider.java
* Looking at the code, the only possible occurance of "spn" is as a
value for "mvno_type"
-> Remove all spn="" attributes
Change-Id: Ic7fef88c98ad54ea98d702e028a0455de22e55cd
* We have duplicate entries with one of them having a proxy
* According to the issue, no proxy is required
* Since the one with proxy is selected by default, the user has to change
it manually
-> Remove the wrong one
* Also correct order: Internet, then MMS
* Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/3850
Change-Id: Id3857d74b703b1dd7d16714a3edc6853d4752e64
- FreedomPop UK uses three.co.uk for its APN
- Add missing `type` param that prevents use of data on any Three UK or Three MVNO SIM
Change-Id: I5f0656d95070c312d5d563536909f23722857372
from MIUI v12.0.8.0.QJKCNXM for lmi
The default APN selection for some Chinese carrier SIM cards is
incorrect, resulting in no internet or very slow internet access.
Therefore, replace APN configs from MIUI for all mcc=460 entries.
[TH779] Still keep IPv6 enabled for these APNs.
Signed-off-by: TH779 <i@779.moe>
Change-Id: Id95cbeda2a63764348d07ddcc8caa7b7e49c6f7c
* It's EE now
* Should not be required since 2015:
"In 2010, it merged with Orange UK to form a joint venture,
Everything Everywhere, in 2010, which continued to operate the
T-Mobile and Orange brands until March 2015 and allowed T-Mobile
customers to utilise Orange's 2G signal and vice versa.
In 2012, Everything Everywhere launched a new network, branded EE."
-- https://en.wikipedia.org/wiki/T-Mobile_UK
Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/3069
Change-Id: Id94a6e156f20b484ea3d23cd3a30f5f9e796b117
* PosteMobile is now a full MVNO and it has its own mnc
* Entries extracted from platina-user 10 QKQ1.190910.002 V12.0.3.0.QDTMIXM release-keys
Change-Id: I70d314c558074f2564e88c761c22bc842b973d99
* CoopVoce is now a full MVNO, thus deprecating older ESP entries (still kept here because not all users changed SIM card yet)
* Entries extracted from platina-user 10 QKQ1.190910.002 V12.0.3.0.QDTMIXM release-keys
Change-Id: I9a59ba54926e27ce64d5adbca42fb7b058436e6f
Adding "default" to the type list, will allow to connect to mobile internet via LTE again.
According to the user, even if enforcing LTE here, it won't work unless adding "default".
I couldn't find any official resources, just that this APN seems to relate to CDMA and other people fixed the issue by adding the APN manually:
https://help.ting.com/hc/en-us/community/posts/206433277/comments/216019607
Therefore trusting the reporter in the ticket below that default is enough:
https://gitlab.com/LineageOS/issues/android/-/issues/2819
Change-Id: I931f5355af74e197020032a1581dd11abf84f10c
Extracted from sony stock rom firmware 'H8266_Customized DE_1313-6279_52.1.A.3.49_R3C'
E-Plus got merged into O2
Synced the newest O2 changes
Change-Id: I67e6987769d0bcc271e58e7416468faa902a870b
Add dun apn type to fix hotspot/tethering.
Also update according to https://www.ultramobile.com/data-settings/
BUGBASH-2371
Change-Id: I202cc7be26403d774e8694dd4386391d3576ea66
(cherry picked from commit 367ca28f8206a1e5be8655fb2f1c2e4972d7e8e3
For Example new devices need the new Sprint APNs, so add a new board flag for
them to set that will make the build system add the new APNs to
the APN config XML. If the flag is not set, continue to use the
old APNs.
To add or replace APNs, the custom_apns.py script has been
added. If CUSTOM_APNS_FILE is defined, custom_apns.py
is run and generates a new version of apns-conf.xml.
Change-Id: I7ff12a4342de2a7663b2b66fd627244214a8dc71
Changes:
1. Rename "Internet" to "JIO 4G" per carrier request
2. Make IMS APN invisible per carrier request
3. Remove "carrier_enabled=true" to reduce
redundency as that's default value
Bug: 32935086
Change-Id: Ic7ce9978ed03aa24f116cad3b4fb049277864b89
This fixes BUGBASH-2328 for Portuguese carrier NOS (mcc="268"
mnc="03").
This is an ugly workaround since you can't edit the APN definition
anymore: if you try to save an APN with type dun, you get the error
message: "Carrier does not allow adding APNs of type dun." But it's
working.
Since the preinstalled APNs does not need to be edited and this
doesn't break anything else for this carrier, this is acceptable.
Thanx to tfae@xda.
Change-Id: Ic81a9549bf9610805e68b9be56c811b008cbdacb
* T-Mobile's domestic network is IPv6 only, and T-Mobile
support recommends setting IPv6 only for max compat
* T-Mobile support also recommends IPv4 only for roaming,
however compat issues have been discovered in the past
* Switching to IPv6 only domestically fixes an issue with
literal IPv4 addresses failing to resolve properly on ether
Change-Id: I7e394c6b7eebf9c106eaea5e000fe021adf421e6