With my previous CL [1], we can override
rounded_corner_content_padding
at the Framework resource layer rather than the SysUI resource layer.
No matter whether
persist.sys.ime.can_render_gestural_nav_buttons
is enabled or not, there should be no observable behavior change in
this CL.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: Manually verified as follows.
1. Build aosp_coral-userdebug and flash it
2. adb shell cmd overlay lookup android \
android:dimen/rounded_corner_content_padding
-> 70.0px
3. adb shell cmd overlay lookup com.android.systemui \
com.android.systemui:dimen/rounded_corner_content_padding
-> 70.0px
Change-Id: I391a504482f25c17f9b67f7eb8f56f362da71ae0
Signed-off-by: pix106 <sbordenave@gmail.com>
Signed-off-by: Nidhun Balaji T R <nidhunbalaji@gmail.com>
Signed-off-by: Sebastian <kjjjnob.seba@gmail.com>
Signed-off-by: Sebita <kjjjnob.seba@gmail.com>
Signed-off-by: pix106 <sbordenave@gmail.com>
When being in dark environments, turning screen off, then moving to
bright environments and turning screen on, sometimes it happens that the
light sensor emits an initial light sample of 1 lux, which causes the
automatic brightness controller to ramp down the brightness even though
the ambient brightness is high. Avoid the controller using those samples
by giving the light sensor some time to warm up.
Change-Id: I81dcb41a25ff0c9f0cf3265da7054ac7ebcbcc34
