AOSP doesn't mount cgroups in /sys/fs/cgroups anymore.
Follow the convention and mount BFQIO cgroups in /dev/bfqio.
Also, remove the ioprio write as we only need ioprio_class
when dealing with 2 different priorities.
Change-Id: I8ff6c601547c445368e80832e736bb926d86b4d1
The global init.rc no longer creates this for us in N,
but we still need it for BFQ cgroups.
Thus, create the mount point in the CM vendor init.rc.
Change-Id: Ice5ff15737329aefd1dad2401bb530a18008fc4d
* We might want to disable pinning entirely for an extract run.
* Set DISABLE_PINNING=1 to turn it off and override everything.
Change-Id: I1be90dda68f0de1c5f5a70c946052d70bfaab7ed
* No need to look for /sbin/recovery as adbd will report
the device as being in recovery mode already. Also, this
check appears to hang on N.
Change-Id: I3bcb427835ae3cd37c7ea56cbc57bba0d18fcc04
Since mainline devices will always identify as a latest
release api level (due to userbase volume), make sure
we check against the current api vs api -1.
Change-Id: I9e9b41a1af5d3a93f58b2e0e0545b979d1cef978
* The maintenance version should not be set optionally
to its official value status, but only be used when needed
* Use the TARGET_VENDOR_SHOW_MAINTENANCE_VERSION := true
introduced in I77c924a13122c8e1d9af14501e46bc532f7aefbd
to show the value of the maintenance version in releases,
with an intermediary CM_VERSION_MAINTENANCE variable
Change-Id: I22b944a1d2d8586e5f3c75e19ca1c53aa3b22b59
* Gives easy access to the RTC values in order to verify or debug
the current status of the RTC clock and alarm, for example
if a user says powered-off alarm doesn't work
Change-Id: I47e71433a53a25fe9880e7be6a1f5bdb1105ef78
* Some devices using AMS AS36xx LEDs controllers
are using 2 backlight paths to light the display,
mostly on Sony Huashan and Sony Blue board devices
* Although most of the displays have interlaced backlights
and the half dark path can be hard to see, other displays
have a top / bottom path that make half the screen on / off
* Control the backlight level of both path if the device does have
BACKLIGHT_PATH set, and if present, SECONDARY_BACKLIGHT_PATH
* Leave the HEALTD_BACKLIGHT_LEVEL config accessible
to override the default 100 / 255 brightness used in healthd
Change-Id: If774c3e66acedddf7ba676581e7c88b7e83a66b6
Signed-off-by: Adrian DC <radian.dc@gmail.com>
* Moving this to open-source from CyanogenOS :)
* Thanks to Chao Chen, Ethan Chen, Pat Erley, Scott Mertz,
and Keith Mok for various contributions to this.
Change-Id: If79f9c279668d14ee0cde62889bb09e7185ef08c
* In many cases, we would like to keep certain files which do not
exactly match what might be extracted from a factory ROM. This
becomes extremely annoying over time to manually reconstruct,
and it's easy to miss these special cases when updating to a
new vendor release. It's also useful to flag additions which
aren't found in the upstream release at all.
* To solve this, we can now "pin" files to a specific sha1 hash.
Simply append the sha1sum of the file to the appropriate line
in your bloblist, prepended by a | delimiter.
* This works by backing up the current files first, running the
extraction, then checking if any pinned files need to be
restored.
* Also add an exit trap to clean up all of our tempfiles
Change-Id: I2010b5175b5701e19a3efb112e8907062ca37d66
* Don't wanna break the build for anyone again :( The
native stuff is very QCOM specific and won't work elsewhere.
Change-Id: Id5dbba1a46dc12cbd5914cf3072ed92a72039b31
* LiveDisplay needs to store the user-selected default mode somewhere
in the case where we are mixing local sysfs-style modes with QDCM
modes. Add a rule for this.
Change-Id: I42b80df7c0ee3c2815594c8a6feea3dc078c6ae2
CyanogenMod builds shouldn't show maintenance versions. Allow the
environment to override this behavior instead
Change-Id: I77c924a13122c8e1d9af14501e46bc532f7aefbd
Zhao Wei Liew
Caio Oliveira
Steve Kondik
Adrian DC
Dan Pasanen
Hashbang173
Luca Stefani
Brandon McAnsh
Abhisek Devkota
Adnan Begovic
dzadzev
Luis Vidal
Ziyan
Scott Mertz
Louis Popi
vm03
Jessica Wagantall
DodoGTA GT