Based on observing it's values, xiaomi.sensor.aod reports
the following events:
4.0: Bright environment
5.0: Dark environment
Change-Id: Ie589066bd860a7fed3989092c21aee73686ecea4
Signed-off-by: Arian <arian.kulmer@web.de>
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the 8 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
Enable Adaptive color mode setting.
Bug: 143513730
Test: Boot test and measure the adaptive color value
Change-Id: I969ec6c3cb1d092a33c0e3a028ff38ad7115dfe2
This fixes deep sleep on AOD. The values are from stock,
note that xiaomi did not use RRO for these values, hence
the values are changed in framework-res.apk directly.
Change-Id: I9c4ea935e7a7df4bd85e1884f91ab25805fe8959
Tethering package is APEX and we need to create a RRO to overwrite
the values for config_tether_wifi_regexs and config_tether_wifi_p2p_regexs.
BUG: 163800715
Signed-off-by: Weilun Du <wdu@google.com>
Change-Id: Ia0834f5215ff8c3b13effa591bd2f84d93419a06
Test: manual testing - ensure that the brightness value in
Settings>Display>Brightness Level can go the full range from 0% to 100%.
[wight554: adapted for our value]
Change-Id: Ife1f2796bb3b8ec5f508903afd30a31556b49cbe
Signed-off-by: Volodymyr Zhdanov <wight554@gmail.com>
Remove the old config_ims_package device config and configure the
new MMTEL and RCS configurations in Telephony instead. Also,
configure the RcsService to be the default RCS service.
Bug: 111305845
Test: make checkbuild
Change-Id: I0d709b8248f1c40f0a5b50ec799396706eeadd65
* This is only available on Nexus/Pixel devices, and we have our own
implementation in livedisplay.
Change-Id: I8343e4986d7dd8413bd8d36dfad0309a4c08026e
