There is no need to save the priority if we're
just hiding the controls.
Change-Id: I96551c5d806d5cc4e01a82a7e010000dff029505
Fixes: 78222122
Test: manual
We had special cases when the bouncer shouldn't be translated but that
doesn't really scale. It's much simpler to just check if it's being
scrimmed - because otherwse it mus be translated.
Change-Id: Ide0af6718f1792ef1a1e16fa39512a2b3a0ba8be
Bug: 78222122
Fixes: 78205990
Fixes: 78140990
Test: atest packages/SystemUI/tests/src/com/android/systemui/statusbar/phone/KeyguardBouncerTest.java
Test: atest packages/SystemUI/tests/src/com/android/systemui/statusbar/phone/StatusBarKeyguardViewManagerTest.java
Test: go/sysui-bouncer-tests
Refactored the state to be more clear and make sure the end runnable is always called.
Fixes: 78861878
Test: have no notification, hide view by scrolling up, get notification, observe
Change-Id: I51b00696f4b2dba565a0213c24a5a67a3c4099e0
Test: adb shell dumpsys activity service com.android.systemui, ensure
the nav bar state shows up.
Fixes: 79881849
Change-Id: I13e6fb4c61c02cbd142e64b7201667e47fe31232
Push over to a standard testable looper, and a testable looper +
setAsMain when needed.
Also make tests more synchronous and single threaded as possible.
This will make them more deterministic and speeds them up noticeably.
Test: runtest systemui
Bug: 79550837
Change-Id: Iab0eb794329d7b1de95aef904ec08ecae7dadc98
Recoloring icons only works for resources in core/res not in SysUI/res.
Bug: 78619585
Test: Manual with dark background.
Change-Id: Ided545abec51bafb0b1963d0a5129066194df61f
Merged-In: Ided545abec51bafb0b1963d0a5129066194df61f
Due to framework side will not callback onScreenTurningOn() when device screen off / on quickly,
So NotificationPanel will not called onScreenTurningOn to update panel position.
There is also a potential issue for cancel touch will be ignored when touch disable
in onFinishedGoingToSleep().
Let ACTION_CANCEL can pass even touch disable to recover Panel position by fling back.
Bug: 79336031
Test: Manual
Change-Id: I45f2fbd8bfef99d86c3d023f07d2fd051d98f083
SysUI status bar updates currently happen upon receiving either the
CONNECTIVITY_ACTION broadcast (which is deprecated) and
INET_CONDITION_ACTION broadcast (which is sent upon validation state
change of networks only).
This leads to status bar showing stale connectivity state. The correct
fix for this is to listen to changes in network state by registering
NetworkCallbacks (see more details in http://b/79286300#comment9).
In the P timeframe, not listening to the broadcasts completely is out of
scope. So this CL just listens for changing network capabilities of the
default data network, which should fix all the cases where the
broadcasts are not getting sent.
Later, when we stop relying on the broadcasts, we will also have to
override onAvailable and onLost (and perhaps the other callbacks too).
Test: runtest --path frameworks/base/packages/SystemUI/tests/src/com/android/systemui/statusbar/policy/
Bug: 71904788
Change-Id: I2e58b9cfceb9937a0b54874dee116ead5339b37b
Previously we mis-count each different activity, regardless of the app
it belongs, as one app launch. We should instead count each different
app open, either created, or brought front as a different app launch,
but different tasks created from the same app is considered one launch.
Fixes: 79885137
Test: Manual test
Change-Id: I5b4b8bee9b0ed4aa23a4ea9eefdfa112b6442455
