/data is supposed to be inaccessible to begin with, and we don't
want the init sequence tampered with for user builds
Change-Id: If3eb5573248956a14ad56516a9871758f4c00989
(cherry picked from commit a9d772166365a27181a7441c10a6c60a2bab7dab)
this project does not exist in cm12 nor does it have a branch.
For cleanliness remove it
Change-Id: I956cb2e98b4e3fc0184cd614e180451a3d0b23d2
Signed-off-by: Simon Sickle <simon@simonsickle.com>
* Drop DSPManager and libcyanogen-dsp. Devices should switch to
standard Android effects or offload-capable versions.
Change-Id: I4f4eec5747e9073e576fe70e720ac3ffebb3fdd9
The group that maintains and builds the Terminal Emulator
have run into Google Play issues resulting in a package name change.
Update associated libraries for this change as well.
See also:
https://github.com/jackpal/Android-Terminal-Emulator/wiki/Recent-Updates
Change-Id: Ib50a8d8435ea12d2c74ea9a68f5f9ddadc7601a5
* 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
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
