Remove the voltage restriction for haptics since DVL is enabled. This
will allow FW control for exertion protection of the motor, and allow
for stronger output for audio-haptics.
Bug: 318476589
Flag: EXEMPT config json change
Test: dumpsys vibrator_manager and accel measurement
Change-Id: I2263206a423c7731f930c213e68c7fb9fd8d6a3a
Signed-off-by: Zouberou Sayibou <zouberou@google.com>
Bug: 336388573
Change-Id: I1bc1afc1cfeb0cf6f6cce0715b14cedc57895983
Test: atest UnfoldHapticsPlayerTest
Test: manual test that haptics could be disabled
Enable Fold Lock Behavior in config.xml and let it be controlled by sysprop flag 'persist.fold_lock_setting_enabled'.
Bug: 298200843
Test: Flash the device with this build.
* Manually check if the setting accessible.
Change-Id: Ide72528bfd40a6c7460a8ecb0565f1c791d4c8cf
Disable Fold lock behavior setting in UQPR1 as it is supposed to be released in UQPR2.
Bug: 298200843
Test: Flash the device with this build.
* Manually check if the setting accessible.
Change-Id: Iefb62dd1f5249aadd43e308ca3f853cf457193ce
See b/227579876, for P23 and later, we can send null initial attach data profile to modem to clear any previoud data profiles.
Bug: 300203182
Change-Id: I608c7a6a5c6b28874ac69a8989f5c0f23320e5cd
Test: Build pass.
Current fold setting has a toggle button which can enable the “Stay unlocked on fold” setting.
Create a new page for fold setting which will allow us to choose something from three options.(https://screenshot.googleplex.com/6W65aTYtigGpr3v)
*Always - Front display turns on when you fold your device [Currently available setting]
*Only games, videos, and more - Front display turns on for apps that stop your screen going idle [Default]
*Never - Front display locks when you fold your device [New option for user]
Test: atest FoldLockBehaviorSettingsTest FoldLockBehaviorPreferenceControllerTest
*Manual
Flash the build with these changes
Manually select options one by one
Observe the behavior
Fixes: 294194379
Change-Id: I59e8ba653bdac397eec0be60b931dc1c6649843c
Merged-In: I59e8ba653bdac397eec0be60b931dc1c6649843c
button for F10
To configure the power button light reveal’s y-axis offset.
Bug: 291954717
Test: manually test and check the Power button light reveal visually.
Change-Id: I97e6f3c5e30bf421b0cd82c065332765619a38b5
Set the pattern view size to 290dp for F10
Bug: 285290323
Bug: 290721507
Test: manual
Test: Test: m RunSettingsRoboTests -j30 ROBOTEST_FILTER=\
SetupChooseLockPatternTest
Change-Id: I0bd45ad6f793afdec96ffd4a538539d040ad4993
New corner spec imported from design that properly becomes flush with
the vertical and horizontal sides.
Bounding box set based on a 79px size, via a 5.28mm corner and a
conversion of 1px = 66.9um
Test: adb shell setprop debug.screenshot_rounded_corners 1 && <restart sysui>
Fixes: 283827918
Change-Id: I41b976243ac1497e45f74d4172c75093e8334268
This is a temporary measure to decrease the chances of flickers when folding to aod, while we work in parallel to decrease latency.
According to ww metrics, Fold to AoD takes:
p50: 714ms
p89: 1020ms
p95: 1147ms
p99: 1577ms
Once we hit the keyguard drawn timeout, the screen is turned on . However, in some cases sysui and launcher are not ready, and this results with the screen on while showing the unfolded layout, with a rapid transition to the folded one (according to pitot data[1], this happens in 11% of the fold->aod).
This cl sets the timeout to 1700ms (slightly higher than p99). In this way, the chances to have flicker are greatly reduced, but the underlying latency problem remains.
In parallel, we're looking to decrease this latency (see bug).
[1] https://screenshot.googleplex.com/9gV9nEfpstkJmCt
Bug: 243015678
Test: fold->aod many times, no flicker.
Change-Id: I0738901279136dd7577016a3ba46dc4c5b9a86f1
Store the brightness for the default display in nits in persistent data store so that it can be persisted if the device reboots or the display device changes.
Bug: 258455654
Test: adb shell dumpsys display | grep mPersistBrightnessNitsForDefaultDisplay
Change-Id: I20a0a686ee1e4e945fbcd99d5b996534f8ef93b7
Merged-In: I20a0a686ee1e4e945fbcd99d5b996534f8ef93b7
Store the brightness for the default display in nits in persistent data store so that it can be persisted if the device reboots or the display device changes.
Bug: 258455654
Test: adb shell dumpsys display | grep mPersistBrightnessNitsForDefaultDisplay
Change-Id: I20a0a686ee1e4e945fbcd99d5b996534f8ef93b7
This xml maps the devices that can wake the main CPU up to subsystems
that use them.
Test: Builds, boots. Manualy verify the loaded map in the output of
`dumpsys batterystats --wakeups`
Bug: 271922941
Change-Id: I3988cde6d8c5258c1f952ccd8c0a08143998473a
extend lux/brightness mapping table to support 1200nits
Bug: 270673324
Test: brightness level can be 100%
Change-Id: Ie77e797fa5f4a860f8fdd6c84379819dd870192d
We have different settings for inner and outer. So we will use display
config to set them separately.
Bug: 258107876
Test: manual testing
Change-Id: I12ea64b9874ee79eec94c4ede6fa2320b27d0c41
In unfold display, the pattern view UI showing in 2 panes
But the additional horizontal padding make the pattern view
truncate.
Test: build and flash, use demo BP to check the pattern view UI
Test: run CTSVerifier and check the test
Bug: 268276210
Change-Id: Idc040bf7f022c1a282c46d1652a0ce3ca75c1839
Currently, 3P apps could read the system resource
of status bar height for portrait orientation on the
unfolded screen. Updating this value to a correct one.
Bug: 264656380
Change-Id: I859b7c756f1dab88373bf2116cf1638a5faae624
Test: manual
