* Added a proper API for this thing
* Pass objects around with necessary metadata, pre-filtered and sorted
* Added event log and service dump
* Simplified locking and adjusted for performance / correctness
* Clarified/beautified code where possible
* TODO:
- Write profile descriptions
- Finish the UI
- Clean up javadocs
- Do something with per-app profiles, maybe
Change-Id: Ie2ef84031e81a18e95dcd62392c7e6939860d933
* Allow CMParts to update the summary (or any detail) of a preference
so it can be shown correctly in the UI.
* Also some cleanup and refactoring around the parts list.
Change-Id: Idc16a7eb1a1e4170671fd068bd240b88fadfb577
* Add a new set of attributes which can be declared in the
preference XML which will cause the preference to be
removed from the hierarchy if the constraint is not met.
Currently we can check for installed packages, system
properties, config references, and system features.
* CMPartsPreference is also updated to use similar logic
based on the external XML.
Change-Id: If8fb39cd3312623e38bb3498bfb3f29ed8b444d6
After creating the theme directory it will be labeled as a
system_data_file. By calling SELinux.restorecon() the directory
will be correctly labeled as a themeservice_app_data_file
Change-Id: I73a28da883a467bf8859d879dbe22962424e4a23
TICKET: NIGHTLIES-3349
* Google changed the way TwilightService works in N, which was never
a public API to begin with. Create a local version to avoid this
problem in the future, which also contains the logic we expect
and have tested extensively.
Change-Id: I11098b14fa75664ce8efbc34888c6f97e3af5ca1
As long as the light sensor is providing values, each value change will
enqueue a transition message, which may queue up. Stop doing that and
ensure only one transition message is queued at any given time.
Change-Id: I6e9c5b265066089ff9e0cea7237c2023ed1af30c
As long as the light sensor is providing values, each value change will
enqueue a transition message, which may queue up. Stop doing that and
ensure only one transition message is queued at any given time.
Change-Id: I6e9c5b265066089ff9e0cea7237c2023ed1af30c
* The public SDK build is currently including AIDLs which are
meant to be used for internal purposes only. My assumption
is that this particular implementation was done before we
split off an "internal" SDK, which is used by the platform itself.
* The issue came up when adding an AIDL which has a backing
Java data object which was not included.
* It should be safe to simply hide this interface. All references
to it are hidden already. It is only used for internal purposes
and does not change the API.
* With the internal dependencies removed from the public SDK, we
can completely remove the reference in the makefile.
Change-Id: I0515815543feb077ee5e289b9f900e28758c6e98
* This is used by LiveDisplay, but may be useful for other purposes.
Move it into the internal/common package instead of keeping an
external dependency.
Change-Id: I87c0af11e19ecaea4a1a5b736fc286cd9a8ac55c
* Dexopt is no longer a thing on N.
Revert "You are now a developer!"
This reverts commit 2059ea6908.
Revert "[1/2] cmsdk: cm custom boot dexopt UI"
This reverts commit 6e5ab27fbb.
Change-Id: Ie50e8e6a77172d2b5b0659be831e7dd7a19fee04
* Show alternative brand logo in dexopt screen
when developer options are enabled
* Drawable by Asher
Change-Id: Ie100d7c3e9c96a7ad64c4cd65195d6f531090140
So the implementing service doesn't have to be signed with platform
keys.
Change-Id: I635d79173bf1771b58e1cb2dd333cee091610a48
Signed-off-by: Roman Birg <roman@cyngn.com>
* Pass app info and number of installed packages to boot message UI
* Ui by Asher and Joey, based on Alexander's previous work
Change-Id: I9298d7e2b85a703921abf62f8b91157e6f88803b
Signed-off-by: Joey Rizzoli <joey@cyanogenmoditalia.it>
* Raise the outdoor threshold to 12K lux to more accurately
represent bright sunlight.
* Raise the night color temperature to 4800K to provide a
soft display look at night with less red.
Change-Id: I26bdea7fc97acb2a17944a1f25e5e11866a08e29
* Essentially everything in CMSDK should remain silent when we
are being prompted to enter a passcode for decrypting the
device. Unfortunately, simply shutting off CMSDK entirely
will cause crashes everywhere. We need to be somewhat
selective about it.
* Motivation for this was LiveDisplay kicking into night mode before
decrypted due to location services failing.
Change-Id: I4d745debb2894776258343e8696ce5144f094404
When a theme with more that one wallpaper is installed(Hexo), when
we set the wallpaper in other themes to the second and third wallpapers
of Hexo while using mixnmatch, some other components like icons,ringtones
overlays would also change its Component_id to the corresponding Component_id
of the wallpaper changed.
Change-Id: I16a0b9a69a329308927cecbe2385f51184c8f0ee
TICKET: CYNGNOS-3220
* We currently use the DisplayColorCalibration API for setting display
temperature which makes a lot of guesses about what temperature
the display really is. Some devices will support the new ColorBalance
API (via QDCM or other mechanism), which offers a calibrated
alternative. Add support for this, which will supercede DCC if
available.
* Additionally, define the available color temperature range as a
set of overlayable values so this can be specified per-device.
This range will be mapped to balance values using the power curve
calculations in the new MathUtils class.
Change-Id: I99608c09807b747d962680293c7b0cee8d669003
