There's no point to keep using custom pref to set minimum refresh rate
when AOSP smooth display feature behaves in the exact same way in
our case.
Change-Id: I497918a9c9687443a9438fb6291769f6e51d9379
Signed-off-by: Francescodario Cuzzocrea <bosconovic@gmail.com>
- after updating rounded corner masks, the adjustment no longer matches screen
- users can see that the radius of the fancy clipping path is slightly too high
and thus causes visible pixel bleed in the top corners at mQsExpansion progress = 0.
- Reduce the radius by 3px to fix clipping issue.
- this is rather obvious after light qs
Signed-off-by: Omkar Chandorkar <gotenksIN@aospa.co>
Change-Id: I09593708bfd95af106d538832727a3ffe98d0a02
Add power consumed by audio and video hardware to power profile.
Attribute these power to specific app.
Bug: 70531798
Test: PowerProfileTest
Test: BatteryStatsHelperTest
Test: PowerCalculatorTest
Change-Id: I4811efa14ce97983258cd59bfd328181fe95baf4
This CL updates resource overlay of
rounded_corner_content_padding
for alioth 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: I0464cd8cd08a26381a026497fb5ee332842b1d96
Bring back old usage of status_bar_height, status_bar_height_portrait,
and status_bar_height_landscape by set the size containing cutout size.
Bug: 216782082
Test: make
Change-Id: I0bf97352bc07e45d7694f9512266f08e7139c103
With the new added APIs, we don't need to overlay status_bar_height that
contains cutout size and quick_qs_offset_height anymore.
Bug: 186604541
Test: make
Change-Id: I36d869866ed03d3996b7b0d8cc6d3f6bb6ab624d
* Extra padding for front facing camera cutout when camera is in use
* Remove flares on high brightness while using front camera
Change-Id: I68acb0deecbecd916be90de0a9043ea4703553df
* also add config_mainBuiltInDisplayCutoutRectApproximation for cutout
* Previous one was a notch bar, thats not what we have
* draw correct punchhole camera cover
Change-Id: I67b8775ca88a6091ead2468dfe351ab7dbee9219
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
- 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
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
