This will allow us to remove the overlay in vendor/cm so devices
with no battery, aka fugu, can override this to none.
Change-Id: I80c0cc06d3aed344c7c705d420af297c96baf706
Added SecretCodeReceiver to locked components
Added list of components that need to be forced enabled
(because they've been previously disabled)
Change-Id: I7cc0efc1830b45bc5384ff421b829e0be0d955d8
Settings resources states that this should be overlayed in product config.
Due to lack of another central source for info (note: need wiki page), point
to Google Support page.
Change-Id: Ic472951b98a409583571442909a638991396d538
This forces set UA string to Nexus5 for SoftBank MCC:440 MCN:20.
Tested send/receive & confirmed working by yours truly.
Change-Id: I1831c329eb38507a957111052bb5f56350c49361
In theory, could have been a good idea, but ultimately just leads to
headaches for device maintainers that need to overlay any of these.
Revert "overlay: remove Verizon specific eri.xml"
This reverts commit 5f92da62c6.
Revert "Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank"
This reverts commit eeeb0888d4.
Revert "Add apns/eri for Boost Mobile"
This reverts commit b207e2eda3.
Revert "add more vzw eri's"
This reverts commit 82e10af192.
Revert "multi-carrier overlays: Add eri and config for US Cellular"
This reverts commit 1af75f1ba7.
Revert "Multi-carrier overlays: Fix Mms"
This reverts commit f8b0737a43.
Revert "Generic multi-carrier overlays based on hammerhead"
This reverts commit 6f5758c9c3.
Change-Id: I3495a89ce405362dc558f7ec7f0e61adea9fa507
Restore order to the universe by removing that which is evil.
For some strange reason, Verizon devices do not agree on the eri.xml to
use, even on the same spn. Since it is not universal, it does not belong
in vendor/cm (at least while there is no automatic method to check which
eri.xml should be used). Remove these so that we don't end up with
strange double-overlay issues for devices.
Change-Id: If5a28ed03c8cc6b145c151c7ebf95fabdf81f434
Companion change to I8a648014873319ea0d0f1089495d6777b8a1b8bf,
config_mms_user_agent_profile_url can't be empty either
Change-Id: Ib6b34972439818da47c389377664e75263dfd21b
The default user-agent isn't set, which makes
TelephonyManager.getMmsUserAgent() return an empty string when a
device doesn't have one in its own overlays. Every hardware should
set its own unique name for this, but add a default value for cases
in which is is forgotten.
Fixes android.telephony.cts.TelephonyManagerTest#testTelephonyManager
Change-Id: I8a648014873319ea0d0f1089495d6777b8a1b8bf
Add a separate list of default lockscreen unlock targets for devices
without voice capability.
http://review.cyanogenmod.org/#/c/52966/1
Change-Id: Ifbb066faade39b1cd98a6d1bfb7b5021eb51ab95
