- required after LineageOS/android_packages_apps_Settings@af35c7c

Change-Id: I79ecd91513df0d195e1d15d20b4438d1b283743f
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>

Phasing out config_roundedCornerMultipleRadius config from device
overlay package.

Bug: 224688507

Test: Build ROM and pass presubmit test
Change-Id: I5cb7efdde8b03f89b74d775612b20e78c6e4d89d

Change-Id: I6b68ead715e6c1506cbedac568c9a53db2f944b7

Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.

Bug: 162195999
Test: verify values still overlaid correctly
Change-Id: I017491fd383551c5aadf8648edb900e0c12a27b8

Added a device specific overlay that changes the default name
from "AndroidAp" to customized name

Test: Builds, manually verified name change
Bug: 36368950
Change-Id: I38a5f6fb950d6a45342080bae186a8ed276d94bf

* From https://github.com/xiaomi-mars-devs/android_hardware_xiaomi

Change-Id: I3bd89bd602dab01fd214b55cc98c8e91ca5060f7

Change-Id: Ie173a8deca131ef595429d2162f656196aabfbe2

Change-Id: Iae000afede3985a99b72b7985092bcdaf1abfa22

Change-Id: I7196dce967c9adbc62bb5156ade749c92c7780a1

Change-Id: I80da2eaf2d4aba55edf3e08de13dfa4fbdb531b2

Change-Id: I0f8674fb15c50c7c89e93916faf8bfb14193a4f6

The PowerManagerService reads config_screenBrightnessDozeFloat first
and later falls back to config_screenBrightnessDim if the float
value is INVALID_BRIGHTNESS_IN_CONFIG [1]. The problem is that
config_screenBrightnessDozeFloat is set to 0.0 by default on the
frameworks side [2], so it will never be INVALID_BRIGHTNESS_IN_CONFIG.

As a result, mScreenBrightnessDoze is always initialized to 0.0f
if the device does not set config_screenBrightnessDozeFloat in an
overlay, which then causes BRIGHTNESS_CONSTRAINT_TYPE_DOZE to
always return 0.0f.

To prevent other framework components from getting an incorrect
doze config value, set this float in overlay as well.

[1] https://android.googlesource.com/platform/frameworks/base/+/refs/tags/android-12.1.0_r10/services/core/java/com/android/server/power/PowerManagerService.java#991
[2] https://android.googlesource.com/platform/frameworks/base/+/refs/tags/android-12.1.0_r10/core/res/res/values/config.xml#1333



Change-Id: If79a05c167aff39b38e234fea906cb7bbeed6381
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>

Change-Id: I8feacfc23b7e697653c1be29346361e35de5586d
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>

Change-Id: I02496a99f54b00718303e24e0f0dcc252492b910

The modified library NOPs out the instruction to change binder
threadpool, allowing the library to load and camera to work on S.

Extend the pattern for cameraperf since "7c 00 00 94" occurs twice
to only NOP the configureRpcThreadpool call.
Output of llvm-objdump:
```
    3ad0: 7c 00 00 94  	bl	0x3cc0 <_ZdlPv@plt>
    3b10: 7c 00 00 94  	bl	0x3d00 <_ZN7android8hardware22configureRpcThreadpoolEmb@plt>
```

Change-Id: I1ef0ed29e4a2eb820826e5d7df1fa53c9e3df584

Change-Id: Ifbde2b5cae85084d524de6a96883c9f04ad63a51

The current vector drawable was generated from an auto-traced svg
that was based on screen_round_corner_{top,bottom}.png in MIUI's
product/overlay/DevicesOverlay.apk. The problem is that the curve
edge in the png file is rasterized, which results in a vector asset
with jagged edges.

Here is what I did to re-draw the curve in native vectorized format:
- Open the png in PhotoShop and crop a corner with 1:1 square ratio
- Use the pen tool in shape mode to trace the black mask
- The corners on Mi 11 series are not perfect arcs. I had to add at
  least two adjust points to fit the original curve of the png file
- Fill the path with black
- Export as .svg. I had to convert the color mode to RGB without
  merging layers because PhotoShop wouldn't let me export svg in
  grayscale
- Import the svg in Android Studio as a vector asset
- Grab the content of the drawable .xml

Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I2b5e8257e0987f6a975a4bf4cc7d971587510c08

Set 120Hz as default refresh rate in the blocking zone

Bug: 156462520
Test: no fps transition in the blocking zone
Change-Id: Iac4c8ef6a36e4d3a108bb9a17716c7c729e513db

When the proximity sensor is in use, the smp2p_sleepstate
IRQ is fired multiple times a second, with each one
holding a 200ms wakelock. This is probably a bug in the
DSP firmware. To fix this, avoid using the proximity sensor
in doze mode, because sleep is preferred to turning off the
screen.

Change-Id: I5c54643b3d6d6ea4e5f847870a5266bb96342583

Change-Id: I8fe0edfb3a0e7af750202afd1fd4f39434820123

Change-Id: If1a8026941df9108655843c6302ff5c5f44cd88a

Change-Id: I543f078dd4dba30e1b22737d5c22d591e3fb34e6

Change-Id: I2c90efac01e61500eb1be23bb0ae6f96c2acdc53

MIUI uses ro.product.vendor.marketname for default device name.

Change-Id: I310c1ffc581b72653783d1093d9e7ebde544bb16

Change-Id: Iaaaabd13de384a0ebfff9f527fcdd0338c3f99bc

Change-Id: I2f8841ea74c9ca0981a7c0a7cfeafe2b27a56d3f

Change-Id: I7b3ed2c217c7f84107257eaf0e577dc2c4d7bef7

Change-Id: Ib40dd59a0e8e4df6ade54a6a7a7434bfb7a06409

These targets are using prebuilt audio HAL and for some reason,
using the source-built liba2dpoffload breaks A2DP. Just use
prebuilt HAL extensions to avoid mismatches.

Change-Id: I37a5601afdbfdcb81a1053b366fad79fadf4eaa7

* Nuke Megvii proprietary files and build stub ones from hardware/xiaomi

Change-Id: I53f8f0897b25517741a06c5962c02fe8fda61072

Change-Id: I3b13a18ed7bc02bd1691318d300c64219a6cf103

Change-Id: I373e94cd8212514a1121a259642448a84215135b

Since msm_drm driver is created as a module by default for
all the build configurations, it has to explicitly moved to
first stage (vendor) ramdisk as the recovery menu needs the
driver to display the UI. Hence, package this as a part of
vendor ramdisk for QGKI configurations only as GKI doesn't
have this requirement.

Change-Id: Ic3d5f5a4a1d3b32de7ec4dfe9ef03bf9b8204068

Change-Id: I9f9463a1ebdfc37486e9a8c81328a421694bda9c

Change-Id: Iec2ad2d4d8cb009c2ca9cd5a9f4a991eb0f45ff2

Change-Id: I6c52e9cb623e8dcc3eb1262af949cbaeeb8aa565

Bug: 183746553
Test: verify default haptic levels set to high on r4
Change-Id: Ie6489be8375ddc01aeb3f227f86e98785232e52a

Change-Id: I72ae3bd68f6dd5154fb7f8101e634c78c4f0c3ee

 * fod radius = miui radius value / 2
 * fod x position = miui x position value + (miui radius value / 2)
 * fod y position = miui y position value + (miui radius value / 2)
 * fod enroll progress radius = (miui radius value / 2) + 5

Change-Id: I487e3a16fec8a7f9760a100606e7081aec5f7581

Change-Id: I3853ae6aada0e97ddf197bb10d7cdbe6499eee1e