* There is still a race condition here.
* Power users can re-enable this by setting
persist.sys.dalvik.multithread to true
Change-Id: I03686bafbac1859695466fcb522bc5436ec82e0d
Mini targets didn't include FFMPEG so far.
I don't see the reason to do this, the plugin takes up minimal space.
Change-Id: I712982c245f9cdb8dd1052a071a7590219b9a9c3
Default recovery flashing on system updates to false. This can be
overridden for specific builds/devices, but the option can be enabled
or disabled on all builds.
Change-Id: Ia1bc94bd1e5f799fc894286a6b2f4f7a8a3816dd
This reverts commit d2d1a7ffb1.
Revert "selinuxrelabel: Remove attempts to relabel /system"
This reverts commit cae5f24530.
Revert "Recheck /data for selinux labeling"
This reverts commit c4dcb16ca9.
Revert "selinuxrelabel: Add a check for dalvik-cache"
This reverts commit c7e9230614.
Revert "selinuxrelabel: Need to check in priv-app now"
This reverts commit 3013c99acb.
Revert "selinux: When adding userdata labels, do cache too"
This reverts commit 8994907baf.
Revert "selinux: Use a more reliable sentinel to flag /data labelling"
This reverts commit b52874de53.
Change-Id: I7779aaca3b0751ed74d525292681817182a0aa7f
This variable is used to build the fingerprint and description on
signed builds, and the dash can't go in there. Add it only when
constructing the final display version variable
Change-Id: I0736d3a88e5f9980c28e6e9afa7e2f9e2d23f815
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
* 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
By defining TARGET_UNOFFICIAL_BUILD_ID in a device's cm.mk, users can
build custom CM builds with their own identifier in place.
This adheres to CM's policy that unofficial builds must be
marked as such, as both the filename and internal version will still
contain the word UNOFFICIAL.
Example:
TARGET_UNOFFICIAL_BUILD_ID := CatEater01
results in
cm-11-20131211-UNOFFICIAL-CatEater01-device(.zip)
Change-Id: I61acdf4698a7fe2b35d3d5315be4b444b1b97987
