setDarmAmount implementations provided by clock plugins
should use the dark amount to transition into and out
of the doze state on AOD. For example, the size of the
clock could shrink in the Y direction when leaving doze
to make room for the notification stack scroller.
Bug: 119035943
Test: KeyguardClockSwitchTest passes locally.
Change-Id: I9968dc2cc5ab8000ff525f3d1d06ffbf73359086
- indicate if an entry is a bubble
- indicate if an entry is a bubble that has been dismissed
Test: none
Bug: 111236845
Change-Id: I81a3ed92d438eb849995f80ed2ef2a3995c1cefe
This change modifies the UI that appears when a notification is
long-pressed to include a third option when the notification could
potentially buzz or make sound, allowing the user to promote or demote
the notification's channel such that it will not alert (or will start
alerting) for future notifications.
Test: atest SystemUITests
Bug: 116622974
Change-Id: Ia070d0ef1b181b4de8b3d49ace9ff2a65fed8deb
To add test testHeaderReadFromOldController into
HeadsUpAppearanceControllerTest.java and conflict with
testOperatorNameViewUpdated.
Bug: None
Test: I solemnly swear I tested this conflict resolution.
Change-Id: If7d7961dbc12346484f3d139bdc808a53abc6c46
This causes it to be consistently picked up for grantPermissions.
Test: Manual - share to Gmail from screenshot notification.
Change-Id: I194526db97eed4af78d35ef3070eb89c4d5d57d7
Previously reverted due to b/72554856, fix for that in topic.
Original commit message:
Security model for moving sharesheet to systemui
ResolverActivity (still in frameworks) now requests a "permission token"
that it hands to a stubbed system ui activity ChooserActivity.
This permission token allows an app (SysUI) with the signed permission
"START_ACTIVITY_AS_CALLER" to call
ActivityManagerService#startActivityAsCaller. Permission tokens are a
one-time use, limited-time offer.
Test: runtest systemui && manual testing
Bug: 69850752
Change-Id: Ia50e21e2f8c6b6d0ed7207625e3b5aef214396bb
dozeTimeTick implementations provided by clock plugins
should update the time of the clock while the device
is dozing and deal with burn-in related issues.
Bug: 119035943
Test: KeyguardClockSwitchTest passes locally.
Test: Custom clock updates with time on AOD screen.
Change-Id: I5c31e6d856c5a80dc3e501831dda5a62c0be5ba0
After typing a wrong PIN, the EditText view will be disabled and lose the focus,
as a result, inputs from hardware keyboard won't be sent to PIN EditText.
Test: 1. Enable PIN lock
Test: 2. Lock the device with Power key
Test: 3. Enter wrong PIN from a physical keyboard
Test: 4. Try to enter PIN again with physical keyboard
Bug: 119287260
Change-Id: I04df523c19c99bef75ea481b44154f7ba2270689
Signed-off-by: Wang, ArvinX <arvinx.wang@intel.com>
Signed-off-by: Guobin Zhang <guobin.zhang@intel.com>
DisplayNavigationBarController is a class to control everything related
to external navigation bars. Belows are its tasks:
1. create external nav bars when:
a. StatusBar.createNavigationBar()
b. A system decoration supported display added
2. remove external nav bars when display is removed.
3. remove all external nav bars when StatusBar.destroy()
(Following Tasks)
1. Support SystemUiVisualibility for external nav bars
(corresponding to b/117478341#3)
2. A design doc for refactor
Bug: 115978725
Bug: 117478341
Test: atest SystemUITests
Test: Manual - external nav bars still works
Change-Id: I17084c1be287ae7ccfb94b2d1302072a5d620e29
This change modifies NotificationMenuRow such that it is now able to
display a different set of icons depending on whether the user swipes
left or right.
No change is made to the current set of icons - all current icons are
still displayed on both sides - but this will enable a followup CL to
replace the buttons to the right of the notification with block and
silence buttons per the designs for the new interruption model.
Bug: 116622974
Test: atest NotificationMenuRowTest
Change-Id: I459441353099d45f348b8299a1fb140790b0697e
After showing the heads up for the fullscreen notification, to
change the density by user will have the status bar icons
not show normally. It will the only one icon overlay on the
clock but actually there are more than one icons. And, it can't
back to normal after expandable notification and collapse the
notification panel.
The root cause is that all of instances of PhoneStatusBarView,
Clock, HeadsUpStatusBarView, and HeadsUpAppearanceController are
recreated by FragmentManager after configuration density and
font changing. The new HeadsUpAppearanceController status is
neither consistent with HeadsUpManager's status nor the state of
the previous instances.
The solution is that to apply the onSaveInstanceState and
onRestoreInstanceState in PhoneStatusBarView, Clock, PanelBar, and
HeadsUpStatusBarView. To make sure that the values of the fields
in the new instance, which are set by other source, have the
consistence with the state of the old instances.
HeadsUpAppearanceController's Constructor.
To hook onLayoutChangedListener to sync the status with
HeadsUpManager's status to HeadsUpStatusBarView if there is a
pinnded heads up notification.
In original, PanelBar.mState is the only one state to save. Instead
of only saving one, to save the view tree state in
CollapsedStatusBarFragment.onSaveInstanceState and restore the view
state in CollapsedStatusBarFragment.onViewCreated.
CollapsedStatusBarFragment.mDisabled1 doesn't need to save and
restore because CommandQueue.recomputeDisableFlags will give it
the correct value.
After density changed, RemoteViews will reinflate the instances of
NotificationHeaderView and the wrapper instances of
NoticationContentView will also recreated in
NotificationContentView.setAmbientChild. The recreated instance
should synchronized with the ExpandableNotificationRow intance.
Bug: 80224819
Fixes: 111996469
Fixes: 117818441
Test: atest SystemUITests
Change-Id: Ia3f8a0f138f403c8e0c74c00d56bd93baf604d3a
Merged-In: Ia3f8a0f138f403c8e0c74c00d56bd93baf604d3a
This system service will listen to ThermalHAL for throttling events and
take actions accordingly, e.g. shutdown device and/or sending
notification to registered listeners to IThermalSerivce.
Bug: 79443945
Bug: 118510237
Bug: 111086696
Bug: 116541003
Test: Boot and test callback on ThermalHAL 1.1
Test: Boot and test callback on ThermalHAL 2.0
Test: Kill ThermalHAL process
Test: Change device threshold to trigger shutdown
Change-Id: I1f4066c9f1cf9ab46c1738a0a4435802512e4339
This works on AOD since notification icons were moved to
the status bar. For the lock screen, the clock is made
transparent due to the height of the clock. This prevents
the clock from interfering with the notifs in stack scroller.
Bug: b119103421
Test: KeyguardClockPositionAlgorithmTest updated.
Change-Id: Ife2de31ae6d55effced99c6d419c794ac57c8522
Add phone navigation bar in 2 situations:
1. When status bar is created and external
displays,which supports system decorations exist.
2. When new displays are added and the displays supports system
decorations
TODO: 1. Support nav bar logic in WM code.
2. Add lightController and more for external nav bars
3. Move the logic to DisplayNavigationController
Bug: 115978725
Test: Manual
Test: atest SystemUITests
Test: atest ActivityManagerMultiDisplayTests
Test: atest ActivityManagerMultiDisplayTests#testNavBarShowingOnDisplayWithDecor
Test: atest ActivityManagerMultiDisplayTests#testNavBarNotShowingOnDisplayWithoutDecor
Test: atest ActivityManagerMultiDisplayTests#testNavBarNotShowingOnPrivateDisplay
Change-Id: Ibf7c548d911ec2aca213b5ac0ecbd67f5f9fbeb5
This change modifies SwipeHelper to pass the direction of a swipe to the
provided callback when determining whether the swipe represents a valid
dismiss gesture, and modifies the callback defined by
NotificationStackScrollLayout to allow dismiss gestures only to the
right.
Test: manually
Change-Id: I7ff1e8f92e7da9ed36520195d823f9a62f9a64ba
In landscape and largest density, the area that could show the heads
up notification is smaller than normal density. To handle the heads
up notification should be different with the normal notification in
both of targetScrollForView and getScrollRange because
StackScrollAlgorithm translation heads up notification as
mHeadsUpInset but neither targetScrollForView nor getScrollRange has
have the same consideration.
The solution make the StackScrollAlgorithm to considerate scroll
value to move up the heads up notification.
The getScrollRange need to consider more about the difference
between heads up showing and non-heads up showing. The top padding
and the total content height are the major considerations.
Test: manual test
Test: atest SystemUITests
Change-Id: I46bb960a81f6ab5be4d8e39738e8fb64245dd4eb
Merged-In: I46bb960a81f6ab5be4d8e39738e8fb64245dd4eb
Fixes: 110388615
(cherry picked from commit 529bfe6f0a)
