Commit 49895bb361e74ffe92a3c0b76f988c8e4697b5c1 in device/google/gs101
failed to remove these overlays. Since this tree was created from
device/google/gs101, this results in the following issue on pantah:
* Pull down status bar
* Try to adjust brightness, network settings open instead
This is caused by the 171px offset that causes the status bar
to overlap the brightness slider.
Test: Reliably adjust brightness, confirm with "Show layout bounds"
from developer settings.
Change-Id: I1b97a28c257cb5b0faba830f29e9058d2dbe50fa
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 6 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
Use runtime resource overlay instead of build time
config overlay so that P21 and later devices are covered
automatically
Bug: 274172776
Test: Manual testing with Messenger app video call
Change-Id: I0ade7915271a3de67a3dcf8815b4dba1b16900a0
Turn off the large JPEG stream on camera1 apps
that experience high power consumption during
video call
Bug: 254350466
Test: Manual testing with Messenger app video call
Change-Id: Ib5012a39caffc1a135b9e2a7a2ef9ed2df064b2e
Remove boosted mode from the available modes list. Also remove boosted
color data from display_colordata_cal0.pb
Bug: 226204397
Change-Id: I5d889f6aff8dc0c5ac745087a639bb85b04a3fe5
config_gnss_supl_requires_default_data_for_emergency removed. Use default value of "false".
Bug: 211060538
Change-Id: Iaec1924d4bda5cdcb4ee427bfe3a12ef7e0fd420
Test: TAM help to verify
Add /system/bin/surfaceflinger to the pinner service default pin list
Bug: 207573339
Test: by 'dumpsys pinner' command
Change-Id: If29333eb06f2aaaf88fdfbad27fe9de4258c5b27
This CL updates resource overlay of
rounded_corner_content_padding
so that the same device-specific value can be seen from both the
Framework code and the SysUI.
With my previous CL [1], the SysUI continues to see the same value
even after this migration.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: presubmit
Change-Id: I3edd624ce3ae7db479f58d1e8a4ccc4dc3edc3b3