Clean up Japanese APNs

 * Rename and rearrange Japanese APNs to make intelligible.

Change-Id: I628012eb5a2cdc1b4e95ca9a6cf1eaa88eb88b31
Allow reading of cpufreq attributes

 * Various tools might want to use these values without writing to
   them. Set world readable for all nodes.

Change-Id: I5521ca0104e9f21b2e3fdb3469485f887ee50f28
Merge "Clean up Japanese APNs" into cm-11.0
Add apns/eri for Boost Mobile

Change-Id: I01bb82afe9a7a35d0a309491fe96da34655ec9c3
Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank

* APN information *
au: http://b00111.blogspot.jp/2013/04/sim-apn-au-ltesim-3gsim-lte-net-au-net.html
SoftBank: http://b00111.blogspot.jp/2011/07/simapnsimsimsim.html
EMOBILE: https://android.googlesource.com/device/sample/+/master/etc/apns-full-conf.xml
b-mobile: http://www.bmobile.ne.jp/devices/apn_data.html

* authtype *
0 is for no authentication
1 is for PAP authentication
2 is for CHAP authentication
3 is for CHAP or PAP, whatever is available

Change-Id: Ib76ced71fa0efe3125db7f97271a6cdf979dbf90
cm: Move default ringtone override to telephony.mk

Change-Id: If5bf8f72f9b07271145d910ba5c44dc73748ae27
overlay: add tmo and att default LTE apns

Change-Id: Ic243e0f9a37bbb50fb8d3b4c598f7e6e7e663fce
overlay: remove Verizon specific eri.xml

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
Merge "overlay: remove Verizon specific eri.xml" into cm-11.0
Merge "overlay: add tmo and att default LTE apns" into cm-11.0
vendor/cm: We are at CM11 now

Change-Id: I0a4b4319506043cae16ad9b6ad360c06961d0fb2
Merge "vendor/cm: We are at CM11 now" into cm-11.0
apns: Add type default for Sprint.

Change-Id: I9e5c5702a47a1497120bb808b2d1c6585dde538b
Squashed revert of mms and spn-specific overlays

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 5f92da62c686c12c00fc9f7948654816c586f838.

Revert "Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank"

This reverts commit eeeb0888d437ac0147cfe4b81aba264cf0d00b70.

Revert "Add apns/eri for Boost Mobile"

This reverts commit b207e2eda31e10a45a20774c61dc350975095d1b.

Revert "add more vzw eri's"

This reverts commit 82e10af192daaacf9e819253264a09a7051d0e06.

Revert "multi-carrier overlays: Add eri and config for US Cellular"

This reverts commit 1af75f1ba7abb351ec1113eeceaa00389a119e3b.

Revert "Multi-carrier overlays: Fix Mms"

This reverts commit f8b0737a435d211b01baf5df3feb9f98039884e2.

Revert "Generic multi-carrier overlays based on hammerhead"

This reverts commit 6f5758c9c33d1be82f76e32a8d83b427204436d1.

Change-Id: I3495a89ce405362dc558f7ec7f0e61adea9fa507
Re-add apns from squashed revert

apns re-added from:
- Add apns/eri for Boost Mobile
- Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank

Change-Id: I2e0091cc4ed1a5c6957792940aba13b801bf7335
VendorCM : Add density bucket for xhdpi

Add missing density buckets for devices such
as the nexus 5.

Change-Id: If759e5f061fe7f199db0688889db9559538dad84