Previously called TMN, now called MEO, this operator only has two APNs, one for
Internet and one for MMS.
Change-Id: Iccd17fe50db36db16d105ccada076c3cc6e7c49c
The new version v1.12.25 of repo add a new flas "--force-sync"
This will add the bash completion of the flag
Change-Id: I96700a1f13e6c5e1c361c48a4b778b4e7bc5dfed
Clean up some straggling duplicates
Add Llamaya Int/MMS 21403
Add authtypes to some apns
CYNGNOS-436
Change-Id: I94f47725b72e98f98344792927951d6f06b31eab
With the influx of new APNs and reordering, this broke the vendor/cm
overlay for preferred APN overrides.
Reorder the list to unbreak functionality.
TODO: Make this override more granular as to distinguish between Carrier
and MVNO on carrier APN.
Change-Id: I65b1bf3a54ce76e4cf0b817a1a3cd6f86fe31f6d
* Performance Settings has been removed/refactored so these are no longer neccessary.
Change-Id: I5933700815d0037735fc48f8640b37d1f350ea91
Signed-off-by: Brandon McAnsh <brandon.mcansh@gmail.com>
Dependencies of Maven targets will have to be managed manually. The prebuilt
target that the Maven target is based off of wasn't designed to handle multiple
artifacts per project. Additionally, this target is mainly intended for grabbing
APKs or other standalone blobs, not for pulling in a full jar dependency tree.
If that is your use case, you may want to investigate simply converting your
project to Gradle (or the Maven build system, if you can stomach it).
Change-Id: Iaf48c95c704cfdc85e0074394ff3c7464937e60c
* 21c0d29e00 broke the previous way of adding lunch targets, as it was
adding a 'bacon' target instead of the full lunch-able target (cm_bacon-$variant).
* use printf and format the combo during the parsing
Change-Id: I0d2c4716bf17cb1a85333662f941d454d0b74e6a
Signed-off-by: Brandon McAnsh <brandon.mcansh@gmail.com>
-Move epc.tmobile to type null (deprecated)
-Bring in multiple MVNO's
-Reconcile with external partner lists
Change-Id: I11523b6d207ec33ea501b70eaca533a1cf4f0a00
Removed bearer for Sprint eHRPD and LTE APNs. The eHRPD APN was set
to bearer 13 even though it is valid for all 1x/EVDO/eHRPD connecti
ons. This was causing no APN to be selected when an EVDO connection
was established and radioTech != 13 (eg EVDO_REV_A = 8). The LTE be
arer must also be unspecified so telephony does not then select the
eHRPD APN since any unspecified bearer is potentially valid for bot
h 3G and LTE. Regardless, the bearer does not need to be specified
since the system selects the correct APN for 3G or LTE automaticall
y.
Change-Id: I4ab61625888bf793a774fca2baab8274760452c4
Update based on Ting's guidelines here:
help.ting.com/hc/en-us/articles/205428698-GSM-Android-APN-Settings
Change-Id: I5de6b7a0b0bab9880e02122a7d76b883c2558cec
According to CYAN-6602 this carrier no longer exists. Hence we can safely
remove the associated APN configuration
Change-Id: I984c73a628a4bee0a07dd61fc1dca77fe05da34b