Recreating the UMO causes a visual flicker. Since the
theme can be changed from a quick setting, this flicker
may occur while it is onscreen. The UMO now uses it's
own colors and does not need to be recreated for theme
changes.
Test: Manual
Fixes: 232295658
Fixes: 204414378
Change-Id: Ifcdb95e7b783cfe8634c8280ac1aa13f193e04bd
- If carrier Wi-Fi is active then use carrier Wi-Fi level instead of
mobile data level.
- If carrier Wi-Fi level is less than min-level, use min-level instead.
Bug: 222885558
Test: manual test
atest -c InternetDialogControllerTest
Change-Id: If8d2871e61396dd8eb3ebab5eda0906d46a06c33
- In some rare cases, EnhancedEstimates will not provide isHybird as true(means EnhancedEstimates can not provide data to us), it will makes low battery warning logic back to the previous trigger flow, remove isHybird condition to make sure we always use the new trigger condition.
- Although BatteryStateSnapshot will be created by different EnhancedEstimates data, but we already remove the usage of remaining time as our trigger condition(which provided by EnhancedEstimates) so we are safe to always use new trigger condition with or without EnhancedEstimates data. we should think about refactor the class here in the future.
- Use current battery level as notifications string content instead of a fixed value.
Bug: 232663250
Bug: 232686016
Bug: 232712770
Test: atest SystemUITests
Change-Id: I412be50763db39d364757ae3afc2927467451118
This reverts commit fb4a590dbc.
This change brings back the grace period built in VCN because
the carrier privileges grace period is turn off.
Bug: 229418673
Test: atest FrameworksVcnTests CtsVcnTestCases
Change-Id: I85738c969c2bf78da33beaebe5863432948b7735
See b/231339801 for more information.
Fixes: 231339801
Test: Augmented existing tests. Manually reproduced without fix and could not reproduce with it.
Change-Id: I5b365e2064b6680dc136903016ee9ae6b7d3ce7c
TV PiP repositioning in response to keep clear area changes will be
debounced in SystemUI, so the client side delay in setting a keep clear
area with focus becomes obsolete.
Instead the config is turned into a flag for whether focused views
should automatically be marked as keep clear areas.
Bug: 231309309
Test: atest KeepClearRectsTests
Change-Id: I0ac61e671bb75e22a95b400c9bd8d84004379e43
Merged-In: I0ac61e671bb75e22a95b400c9bd8d84004379e43
We start input threads before setting mIsOpen.
This means that sometimes, input threads immediately exit
due to a race condition.
The fix here is to remove the use of mIsOpen and use a new
mechanism with Thread.interrupt() and Thread.interrupted()
to mark a thread to be closed.
Bug: 223316278
Test: MidiScope/MidiKeyboard
Test: CTS Verifier Bluetooth Tests
Change-Id: I7c221504ae8a8814c1aa5598552494c80c202eb2
Only update it when app ops state is changed, as the preference
is possibly disabled by other components already.
Bug: 222677960
Test: "Sensitive Notification" grey out works
Test: Enhanced confirmation flow for accessibility works
Change-Id: I4930ede5de1bfe7594d4f9c6aa5fbd468528a313
While the taskview may embed a showWhenLocked activity, there is no
guarantee that launching the full activity will also have this
property. Instead, prompt for auth before launching the full intent.
Fixes: 232954894
Test: manual - use showWhenLocked activity over lockscreen, then click
top right button to launch full screen
Change-Id: I82857e4cf16b90a2e1a89b61e30aa89948072f87
