Since we don't have a proper proximity sensor, doze is unable to perform a
proximity check thus some xiaomi part features aren't working
Change-Id: Ic7f2dff80b52d32e821b77f2e8c6307f8a8e3d18
* Resolves:
W adsprpcd: vendor/qcom/proprietary/commonsys-intf/adsprpc/src/a
pps_std_imp.c:805: Warning: apps_std_fopen_with_env failed with
0x2 for capi_v2_dap_cpdp.so (No such file or directory)
* Also resolves ADSP_FAILED errors (and audio silence) that occur
during inbound call notification when a BT headset is connected.
Change-Id: Ib73c25c03e89df11b18fedb44631577ab267403f
The FPS deferral property allows deferring clock/bandwidth votes
when switching from high refresh rate to low in case hardware
takes some extra time to change refresh rate.
Bug: 152468927
Bug: 154607334
Test: 60/90 switching, no noise line
Test: systrace to check vsync period
Change-Id: I47284578d13c203b14b3213081faf258dd9a542b
- Setting default peak refresh rate 0 or 120 disables 90Hz.
This makes 90Hz option in min_refresh_rate unusable. Setting
both config_defaultPeakRefreshRate and config_defaultRefreshRate
to 60 allows us to use 90Hz properly
Change-Id: I67eed6191881ba7678065a6840c1d4ed0dea8ed3
- We are no longer using smooth display and using min refresh rate,
So this causes stuck at 120hz all time
Change-Id: Id9661bd4a17a50cf0b1fc132fcd5c84f3e85689c
When markBoolSuccessful is invoked, we update
the partition table. These writes should be
synced before merge operation is resumed post OTA.
If not, any crash before these writes are landed to
backing storage will lead to incorrect switching of
slots.
BUG: 175711601
Test: Verify slot switching correctly after crash when merge in progress
(on redbull)
Signed-off-by: Akilesh Kailash <akailash@google.com>
Change-Id: Icc4987e5e8fb1a4b55a0c8ca74c362c56dd9d0ed
Signed-off-by: Albert I <kras@raphielgang.org>
alioth has a center punchhole camera, so users were still able to
do things like enabling the network traffic monitor or setting the clock
position to center, both of which would not be fully visible due to the
camera.
Change-Id: I2aaa0c06b23b40aac120c325ce15fb0992463520
- 90hz in alioth not calibrated correcly in terms colors (blame xiaomi).
which creates screen flickering while switching between 60<->90<->120hz
- Sometimes low brightness causing flickering between 60<->120hz.
- So we are switching to manually setting refresh rate
Change-Id: I2e16b99318003de819d84cab03f7baa33b9b6f2b
- From LA.UM.9.12.r1-08300-SMxx50.0
- Remove Xiaomi's crap while at it
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5483ae59edd031e381a61619f8f57caaca4cabd6
855 1026 E audio_route_ext: Path name 'audio-record-compress2 bt-sco-wb' already exists
855 1026 E audio_route_ext: start_tag_common_path: fatal err path name already existed in common xml
Change-Id: I93d39add5966dd186fb745cb1222ceecaa63ed48
Signed-off-by: Albert I <kras@raphielgang.org>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
This to allow us to idle to lower refresh rates even if the app is
requesting a higher one if it's idle to save battery life, or boost even on
apps that don't request a certain high refresh rate to get a smoother
experience
Change-Id: Ie611283e1d75a31b218454073e85742be91fdf07
This is to allow refresh rate switching to be truly dynamic based on the refresh rate requested by the app while allowing for us to add boost & idle cases in the future through further properties
Change-Id: I6584ce692d33406e489c82af2ded58af72db5e2d
alioth supports switching between 60,90 and 120 Hz refresh rates, so let's
expose it in Settings -> Display -> Smooth Display for users to save
battery if necessary.
Test: visual confirmation after toggling several times
Change-Id: Ie698ec4d4e738afd2a9055dba2369233103a4f13
Add a new priority PRIORITY_DEVICE_PEAK_REFRESH_RATE, and a new config
setting config_defaultRefreshRate which maps to that priority. This
allows an OEM to easily specify a default frame rate different from the
peak frame rate.
Bug: 148978450
Bug: 154648391
Test: - Added new unit tests to verify DisplayModeDirector handles min,
peak, and default refresh rate settings correctly.
- Modified a POCO F3 to set config_defaultRefreshRate to 120Hz, confirmed
we default to 60, but that an app calling setFrameRate(120) switches us
to 120.
- Confirmed that the "smooth display" and "force 120Hz" options on POCO F3 work correctly.
- While we are at it drop redundant config_defaultMinimumRefreshRate
Signed-off-by: althafvly <althafvly@gmail.com>
Change-Id: I9e5b33ae4d8cb6753b9af70ec5407b3576e75dc3
To allow turning these into errors on other devices, and incrementally
fix these issue, set BUILD_BROKEN_DUP_RULES.
Bug: 77611511
Test: check out/soong.log
Change-Id: I3b8f29f0f9e2ad445e72c65e7688b109817dcff3
