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
Runtime Resource Overlays (RROs) can no longer change the value of
resources in manifest when read during PackagerParser.
This change uses component-override to enable the service by default
on sunfish devices.
Remove usages of profile_supported_* from overlays as they no
longer configure the enable state of Bluetooth componenets.
Bug: 135048762
Test:
adb shell pm query-services \
com.android.bluetooth/.a2dpsink.A2dpSinkService
adb shell pm query-services \
com.android.bluetooth/.avrcp.AvrcpTargetService
adb shell pm query-services \
com.android.bluetooth/.avrcpcontroller.AvrcpControllerService
adb shell pm query-services \
com.android.bluetooth/.ba.BATService
adb shell pm query-services \
com.android.bluetooth/.hfpclient.HeadsetClientService
adb shell pm query-services \
com.android.bluetooth/.hid.HidDeviceService
adb shell pm query-services \
com.android.bluetooth/.sap.SapService
Change-Id: If41df9fdefbcd952f8387451dc137565343e3d75
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
