This allows applying only those values provided. Since NULL can
be passed for several of these params, the builder keeps
track of fields that have been specified using flags instead.
Test: nope
Change-Id: I1483df7f796d11f1ebb5eda57d4aa10787cfb5de
Current retry for notifying cameraserver is 20ms * 30 = 600ms. Double it
to 1.2 seconds to give cameraserver enough time to start up.
Test: Build
Bug: 140414594
Change-Id: I5726212d81bb595a99c9137e073f0da022d0779c
am: 97b5991f24 -s ours
am skip reason: change_id Idbff4fbabca962c632ff5d78b25418c0502db9a7 with SHA1 d2eb34b689 is in history
Change-Id: I2869d08fb1bf9b878f5acea1e3e05a1de892edf7
am: 803f3e0a6f -s ours
am skip reason: change_id Idbff4fbabca962c632ff5d78b25418c0502db9a7 with SHA1 d2eb34b689 is in history
Change-Id: Ie8e9917a797a56e5bb9a498f0c2f7f49ab52ed36
am: 941d439465 -s ours
am skip reason: change_id Idbff4fbabca962c632ff5d78b25418c0502db9a7 with SHA1 d2eb34b689 is in history
Change-Id: I7081d25eb3e16e25cf36dab3d2f44ab820d44bcd
Also, if session is aborted before the pre-reboot verification is
complete, we now stop the verification process.
Bug: 140233823
Test: StagedInstallTest#testFailInstallAnotherSessionAlreadyInProgress_MultiPackageSinglePackage
Test: StagedInstallTest
Change-Id: I4cff8060aa1600c505531f00986ebbeb523c07c8
Removed guards for most of the logging. Still guarded for tiles that are
added, as it goes through all the tiles every time something changes and
it's pretty verbose.
Also added log for destroyed tiles due to not being available.
These logs are not too frequent, happening only when a user is started
on the device and when the tiles are customized.
Test: adb logcat
Bug: 138848764
Change-Id: Ica203a6611d54ce22c9d426b0413e8b543ba41b3
It's not possible for the device to go to SHADE_LOCKED after you're
already unlocked, still it's possible that it would happen.
Added an extra condition to avoid it, and logs to catch the regression
if it happens again.
Fixes: 139259891
Test: pull down notification while authenticating
Change-Id: I5c2b81906fa444dfd07d040b81a527245d4130e6
Smart reply updates are not visually interruptive and bubbles should not
show flyout for them, since flyout text remains the same.
1) Modify NoMan.isVisuallyInterruptive to skip evaluation of fields
irrelevant to bubbles
2) Modify NotificationComparator to rank interruptive notifs higher
3) Pipe bool (isInterruptive) from system_process to SysUI
NoMan --- set bool on notif record and ranking
Ranking --- parcel bool for cross-process transport
SysUI notif entry --- get bool from ranking
SysUI bubble data --- on notif entry update, suppress flyout if isInterruptive=false
Considered adding "isInterruptive" bool to StatusBarNotification.
Did not because "visually-interruptive" is additional information that the
system figured out and SBNs should be limited to info from the app.
4) NoMan --- schedule ranking update if interruptive changes for bubble
Fixes: 138755533
Test: manual - send one sms => flyout appears once
Test: manual - send multiple sms in a row => flyout appears for each one
Test: atest FrameworksUiServicesTests
Test: atest NotificationComparatorTest
Test: atest SystemUITests
Change-Id: Id4b855054689ee73a109bb7cd18004531b41f28c
(cherry picked from commit 0dddc61824d091e48962e36939828cae3cde2aa9)
