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
On low-end devices, the current 48 fps boot animation can use more than
50% of CPU time, and if the texture cache is enabled, a majority of main
memory as well. For these devices, add half-resolution variants of the
lower-resolution boot animations which display 2x upscaled -- this
greatly speeds the boot process and makes the boot animation run more
smoothly.
Change-Id: I0140616ca38c52a06dd4622f1c20a9ca0da95f4b
The variable used does not exist at this stage of the build. Switch
to PRODUCT_DEFAULT_DEV_CERTIFICATE, which does exist when in use.
Change-Id: Icb3bbaa437e68b96e1ce05a09f6525cd1ddb9a6a
Per https://jira.cyanogenmod.org/browse/CYAN-2183 the previous ones
were all incorrect/broken and replaced by the new addition.
Needs testing
Change-Id: Ic6781e9d75da61f8ff2c84de13c3235ee97a029b
PS2: Adjust mnc on coop mobil MMS to be '##' format
Signed-off-by: Henning Nielsen Lund <hnl_dk@amigaos.dk>
Change-Id: I4cd0e838ca274440a56678252c8ad1f209da5a7d
* patch set 1 to 7 doesn't fix the problem, it bruce forces the spn
list to ALL DEVICES.
* this change and http://review.cyanogenmod.org/#/c/57393/
will attack the problem at lowest level, customized it for speed
and memory.
* the best part is that it handles letters and exit the
function when it find a letter in the response from ril.
Change-Id: Ia63309acf38617e68b98ff1068463a942fa793df
Don't assume the path to the signing key is the default, it can
be empty and have the same meaning...
Change-Id: Id545d6436e9f21d6b62eec5a317ea7665190f104
Similar to the ro.build.id/ro.build.display.id distinction, and with
the same rationale; signed builds are intended to be stable by
definition, the release types have different meanings (user vs
userdebug), and the full CM version has too much duplicated information:
the device's name and build date are already present elsewhere in the
same information screen.
For signed builds, remove the duplicated information and the type,
leaving only the actual numeric version and the verbose build identifier,
turning for example "11-20140109-SNAPSHOT-HappyPonies-device" into just
"11.0-HappyPonies". If a simplified display version can't be built,
it'll be the same as the full ro.cm.version
Change-Id: I7d8cccbb3205bde710f0004df0a6bd12c39693f1
* Remove all this stuff. If a device wants ZRAM, it should be
enabled by the maintainer and properly configured and tuned.
* This stuff currently causes a conflict with the ZRAM support
added in Kitkat. Kill it.
Change-Id: Ib2488ea4463e32ec44b65fe786f732145b5b6e23
These are a no-op due to the additional block-device protection from
e18c0d508a
so get rid of them entirely. Any installing recovery (or equivalent
installation process) should handle the labeling of system components
on its own.
Change-Id: I14c50f08efa6f05b03fad4fbc404219cc504e1ff
TBD: Do we still want to label unlabeled files?
