RomManager hasn't been properly updated in years.
Is this still even a reliable ROM updater anymore?
Change-Id: I3ea57ec0121e6d6f933dd80031bb53514a44e362
These service providers no longer exist.
https://en.wikipedia.org/wiki/Loop_Mobile
Change-Id: Ic6263b6e8721ee81d902e0bd42553749411d8860
(cherry picked from commit 11af61ac83c15b9943c4b70f463748ebca003f16)
Vodafone Live is TV service for Vodafone TR,
but is getting chosen after full wipe and needs to be toggled everytime.
Change-Id: Id0db8a433d3e2cff0f893913dcd8361f51f72817
Do not prepend app or priv-app to the src when a path is explicitly
given as an argument. This fixes the SRC path in such conditions.
Change-Id: I43370f17fe224df323fcfa9b0d5eae4ee2996524
* Move extra tools to common.mk. These are needed for CMFM, and should
be included for all.
* Move LiveWallpapersPicker, SoundRecorder and Screencast
to common.mk. These apps are extremely small, and only takes up
less than 1 MB combined.
* 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
On a fresh install the theme service broker creates the initial
theme directory which needs to be relabeled to a themeservice_app_data_File
in order for the brokered theme service to write to this directory
Change-Id: Ifd689a0c619c0e954192749b83a0cacaa945468f
TICKET: NIGHTLIES-3349
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
