Make sure that opening the notification panel doesn't result in a "blip"
in the nav bar visibility
Bug: 147427386
Bug: 149021759
Bug: 149115608
Test: on hawk
adb shell settings put global policy_control "immersive.navigation=*"
swipe up from bottom of screen - make sure it autohides
pull down notification panel - make sure the panel doesn't blip
on sdk_gphone_x86 - atest SystemUITests
Change-Id: I4b5244e5ff26fb23e687cd46bc105d4fb8251bc6
Register a receiver that listens for Intent.ACTION_CLOSE_SYSTEM_DIALOGS
and dismisses the volume UI when such an intent is received.
Bug: 149228466
Test: Manual
Change-Id: Iabb706b1d4cc54cb84f228aad95bfdb7e6f75851
This fixed the keypad remains ON when switch facet issue.
BUG: 130573446, 149228466
Test: Manual
Change-Id: Ia449fb41a03bc02498471ded660d573d5b1ad141
(cherry picked from commit 82298783683ebe82a5847dfd35fc8b3528709930)
(cherry picked from commit ebff32a5d6)
Previously, while restarting the Navigation Bar, we omitted the step where we
apply the selection state that reflects the current task stack.
This omission caused CarFacetButtons to lose their selection state on
certain events, such as the day/night toggle.
Bug: 148211695
Test: Manual -- Verify that the selection state is preserved between
day/night toggle.
adb shell dumpsys activity service com.android.car/.CarService day-night-mode day
adb shell dumpsys activity service com.android.car/.CarService day-night-mode night
Change-Id: Ic07b8b66aa531436ce4f23d56bb3c11a79b7cb46
If the Keyboard is shown, then margin bottom is 0.
Otherwise, the margin is the height of the NavBar.
Bug: 149022190
Test: Manual. Verify that NotificationView's margin adjusts based on
whether keyboard or IME is shown.
Change-Id: I96c50a4d773dfac9b57ab1c15cfc59d315da4605
Refreshing all of status bar causes issues with some listeners being
triggered before it is ready to be called.
Bug: 145946470
Bug: 146163621
Bug: 146521766
Test: manual (flash + change language + watch logcat for sysui crash)
Change-Id: If9b2d0fd81698aba21ed3d5708ac68d09bdba0a7
Use a controller to monitor KEY_SETUP_WIZARD_IN_PROGRESS and USER_SETUP_COMPLETE
flags to know when to set CarSysUI bars in an unprovisioned state and prevent
interactions with notification shade.
Bug: 145616123
Test: Manual
Change-Id: Ie035f049e3e9e7cb411fc9553a20e4c09078c121
Only show unlock dialog when the foreground user has screenlock and trusted device.
Bug:144590810
Test: Manually on IHU
Change-Id: I2585ec33391aec9f3cd71f03507e863cbd5d4e76
Merged-in: I08c7aa677150ca950785428580eee6a39ffadd37
Only show volume dialog on first volume change event if the flags
related to the event are set to show UI.
For example, this allows us to not show the volume dialog if the volume
is changed from sound settings as the first volume change event.
Bug: 145134692
Bug: 145094923
Test: Manual
Change-Id: I9bf7eeb009a792e7205265add2cc6b1b0d542168
are recreated when the device changes density.
Also resolves issue where on restart, user cannot pull down
notification shade.
Bug: 144940266
Test: Manual
Change-Id: I29a9b9c3d6ee13cd9e1c415ebd6c0177d4c2cf26
The only times the keyguard is shown are:
1. To display unlock dialog when the initial user has a trusted device.
2. To display user switcher if the user clicks "Cancel" on the bouncer and
wants to switch to a different user.
Fixes: 140766764
Test: manual
Change-Id: I9e3c1138813ba40f0c6b2e8cba057b99ff6fb040
Merged-in: I9e3c1138813ba40f0c6b2e8cba057b99ff6fb040
We can reduce boot time, by having CarStatusBar listen for Volume change events and have it initialize VolumeUI when the first of such an event is received.
Bug: 143107490
Test: Manual
Change-Id: Iee8a68197bbb40b8d93d2cf4cfd3e8a1f41d2212
(cherry picked from commit 4d45b5557929b1390d75c9b1c3ee8622b18023a7)
ready.
Also moved the listener to be added at the end of connectNotificationsUI
when all other variables have been initialized.
Bug: 144583077
Test: Manual
Change-Id: I281fbdd833c23d8dc9d2430d8a6eaad7e4577c53
Merged-In: I281fbdd833c23d8dc9d2430d8a6eaad7e4577c53
Test: Robolectric -- Robolectric results are identical before and after this change.
Test: Manual -- Hawk is booting successfully and interacting with different
parts of CarStatusBar is not failing.
Test: Manual -- Pixel 2 is booting successfully and interacting with different
parts of StatusBar is not failing.
Bug: 142342652
Bug: 140999054
Change-Id: Idf5e152aa661f06b7a041d39d759595636807dce
If volume dialog is not expanded, then we just replace the old default
CarVolumeItem with the new group.
Bug: 141752233
Fixes: 141752233
Test: Manual
Change-Id: Idfa6ad3a1129e069a297f1c1cfd47b40a61773cc
to be configurable.
Bug: 143372960
Test: manual - took before and after videos
Merged-In: Ia0b6a56859889d538e21f807a88bc5217d89e64a
Change-Id: Ia0b6a56859889d538e21f807a88bc5217d89e64a
- createCar(context) will lead into crash when car service is crashed.
- Migrate all createCar to new style which can handle car service crash
while removing unnecessary delay for connect.
Bug: 142543455
Test: kill car service and check if systemui survives
Change-Id: I69298f763a2a2e63c0cf8deae13f747ea19bbf9d
Merged-In: I69298f763a2a2e63c0cf8deae13f747ea19bbf9d
(cherry picked from commit c83d7b93ae0620bac34af2a937d5855b05058213)
A burst of ACTION_OUTSIDE events would cause the dialog
dismiss animation to repeatedly cancel and restart before
it could finish.
Add a flag to keep track of the dismissing state, and let
the animation finish once it has started.
Change made based on proposal from partner.
Bug: 142877093
Test: manual
Change-Id: I16a76bd7a65313027751f8f0e223d0346626c37b
(cherry picked from commit c8d3ef17af781731b558302efada5c1e7bebd096)
of removing/adding the view.
Adding/removing the car status bar via window manager causes issues if
trying to do too quickly since the calls are asynchronous. So if the
status bar is under the process of being removed when we want to show
the status bar, it will throw a BadTokenException because not all of the
references have been cleaned up.
Bug: 142272085
Test: manual
Change-Id: Ia0f46ba4f7582aaadd24dd885788609f027fa156
