In some circumstances we might want to set a custom vendor.mk
filename. If not set, then just default to the current device name
Change-Id: Icb59ebee67ce17b41ac613020685773efb01103d
In Nougat, CAF removed Helium as it is a duplicate of Hassium.
Switch back to choosing Hassium as the default alarm tone.
This essentially reverts commit 2b999181c8.
Change-Id: I62ff1565c76fddf2f744c26c44f30e940cf25b7b
* androidkernel is a set of toolchain symlinks for kernel builds that
point to the regular toolchain binaries, except with ld pointing to bfd
instead of gold.
Change-Id: Id1e2d3b1c50db581bff13cfa00b5b35d5badb8ed
Include the telephony-ext jar library in PRODUCT_PACKAGES
and in boot jar path.
The telephony-ext jar is needed for MSIM manual provisioning
and other telephony related functionalities to work.
Change-Id: I049ec39e88ec734e3770a9439d4c7ba8949b4357
* Move extra tools to common.mk. These are needed for CMFM, and should
be included for all.
* Move PhotoTable, LiveWallpapersPicker, SoundRecorder and Screencast
to common.mk. These apps are extremely small, and only takes up
less than 1 MB combined.
* Remove obsolete live wallpapers.
* Move sound property overrides to common.mk. There's no need
to have them spread across several files.
* Include CM audio files from common.mk
Change-Id: If308506cd9cd0a75014de988c242d700db5d16f3
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>