It's now enabled by default

Change-Id: I57f059c872fc2ad2fd15e788b1391eeebaff9bde

Change-Id: If17503f2dd4bd4d6e333891f9649a7db8d809852

 * These are moved to sysprops in Android 13.

   https://android.googlesource.com/platform/system/libsysprop/+/976d33062b51e77edde44faad1a6e801c5dc0188%5E%21/#F0

Change-Id: I5bff67a15c537e8a47a19f30776fca6bf2c9fbe5

This ensures that the device doesn't switch to hrr while
doze mode is active.

Change-Id: I8488e86e56a46aea95f2835d8667c23401625f0b

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>

Support has landed in WebView, so time to turn it on in framework!

Change-Id: I064cf3512928637895932b3405adaec74b1ceed2

Bug: 214499288
Test: Presubmit
Change-Id: I83757ae6a053ec6b10b08322c4e76d988f1a4a48

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

This reverts commit 4372eed4.

Change-Id: Icd049f2e874d7044e7a156eac7d3f1d4e16460f1

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

These are not pinned on stock.

This reverts commit 98c9d2a9.

Change-Id: I69b906fbc0ae18c4d5832fc642beaae38ff6d392

Change-Id: I0ab13fb86b352680439198058b615f29f76f0165

* Activates some options on Settings>accessibility>vibration

Change-Id: I00e20f0d607736c04d5c2a0bd9c513c7f5fd8b41

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

Change-Id: Ia57acd244608848f70fdcc30d5694c919db60671

Change-Id: I274cd7c5e5e47b2e86dbc733b37960e1a5993e7a

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

Change-Id: If96bb13d6cc2c2156d8df111a1037247c96c6e0f

Remove or update paths that don't exist.

Bug: 119800099
Test: boots
Change-Id: Idd0066e2ab737c9edcf9a745a19aca7421f62575

The app is moving to /product

Test: m
Test: check if it can boot
Bug: 137908189
Change-Id: Ifd73ba03884543e33d61c74d933ad8171dd3b259

Test: Presubmits
Bug: 135753770
Change-Id: If522ab29b6c4e9aab91f5ba41e10947799315f33

Bug: 130103428
Test: verified with dumpsys pinner
Change-Id: I8ffe5eee1d40a5ac6be2112621ccda4b4dd5be1a

This reverts commit 51e488c63c0e15aac8deb4ac3892ee0ca5b2bffc.

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>

Bug: 147569830
Test: atest TeleServiceTests:PhoneGlobalsTest
Change-Id: I57d80bbf17fafdc87ba04c6e7f7ab9573482e395

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