In current desgin, the confgis for cutout and rounded corner are based
on the original display size. If the display resolution is overridden,
cutous and rounded corners will be drawn in incorrect places with
incorrect size.
We should load the cutout & rounded corners with the orignal display
size and then scale the results with the display ratio which is
calculated by dividing current size with original size.
Bug: 209592558
Test: manual:
1. Go Settings-> Display-> Screen Resolution
2. Switch between FHD+ and QHD+
3. Check if the cutout and rounded corner looks the same as they
are in the original display size.
Test: manual:
1. adb shell wm size 1080x2340
2. Check if the cutout and rounded corner looks the same as they
are in the original display size.
Test: atest DisplayCutoutTest LocalDisplayAdapterTest
ScreenDecorationsTest RoundedCornerResDelegateTest
Change-Id: Iea42b73c0276b82983c1ddbce9455355afdc164d
enabled status changes.
See b/228414210#comment4 for an in-depth explanation.
Fixes: 228414210
Test: manual: Start a media session then update the display size
or font size; verify that the seekbar still shows up.
Test: MediaControlPanelTest
Change-Id: I37ec1149ce24b81ca7f545ee524df68173b3c943
According to the motion spec for split-shade, there should be no depth effect.
Fixes: 228022043
Test: Manually + NotificationShadeDepthControllerTest.kt
Change-Id: I1b908e17b3084f94578973d53993b47d9ad22ebb
In ScreenDecorations.onConfigurationChanged(), only redraw OverlayWindow
views when rotation is changed
Bug: 229549809
Test: atest ScreenDecorationsTest
Change-Id: Ic596c065ac9f962de94277be858fdb2ab96bc833
The CountDownLatch should be put at the last line to avoid making
CountDownLatch#await passed without updating values.
Bug: 224717753
Test: atest WindowMagnificationControllerTest
Change-Id: I29530a02780291d684a30e31b4811f2b95fe0faf
Dragging a notification into split screen would fail if bubbles
were expanded while performing this action. I think it makes sense
to collapse the stack if its open when drag and drop for an app
starts.
Bug: 223909931
Test: atest DragAndDropControllerTest
Test: manual - have bubbles expanded
- swipe down the shade, long press on a notification
and drag it
=> bubbles are collapsed and the notif is able to be
put into split screen.
Change-Id: Ib5160b3d772452f1cdd704926887bd38a5fd1ef1
We just keep notif scrim alpha to 0 when we are on keyguard and we are
not transitioning to full shade. This will prevent the notification
shade from showing when tracking on the lockscreen.
Bug: 201040592
Test: Manual on devices of multiple form factors:
Launch notif from LS - portrait and landscape
Launch UserSwitcher From LS - portrait and landscape
Show pin bouncer in LS
Swipe to unlock - portrait and landscape
Change-Id: I0cfa7cd40b69c5c9ea7eeb708f1a073f307918cb
LargeScreenHeader should respect the disable flag and not show its
contents when QS is disabled.
Test: manual in landscape and split shade.
Fixes: 218873788
Change-Id: I085f36a30dd654cd49a35b3b3f3dfd71745226cb
Use the QS expansion amount to fade out the UDFPS
affordance instead of blinking out when qs starts
being expanded.
Also, don't immediately hide the lock icon affordance
when qs is expanded. Instead, we rely on the alpha
set by NotificationPanelViewController. It's the same
alpha used to fade out the keyguard bottom area.
Tidy up the UdfpsKeyguardView alpha updating.
Fixes: 228897571
Test: atest LockIconViewControllerTest UdfpsKeyguardViewControllerTest
Change-Id: I23e716261d2d8881fab3b4b420e2080ff5a4cb28
We don't want the brightness to change right before
the display goes off
Fixes: 228285716
Test: manually cover proximity sensor and wait
Test: atest DozeScreenBrightnessTest
for the display to turn off
Change-Id: I0980f223e7ae86afcc0d3a3a8c93e57d8883e281
Instead, allow the face-auth help messages to be shown
to the user.
Test: manual, atest KeyguardIndicationControllerTest
Bug: 227545287
Change-Id: I3cfd99af941053e9da28ac4454c022f255e3eac4
Root Cause: From ag/17686873, we remove the protect mechanism that
AccessibilityManagerService might not ready to retrieve information when
the phone get booted without keyguard lock, but it will still happen if
the sequence of the object created got change, just like b/184272107 in android sc-dev.
Solution: Change to check target is empty first before showing it, this
way, we can show a11y FAB both in onUserUnlocked() and
onKeyguardVisibilityChanged(false) stage without showing empty content
a11y FAB.
Bug: 192635136
Fix: 184272107
Test: atest AccessibilityFloatingMenuTest
Change-Id: Icca1c2bbae3f0bf6cad4fb28c53b5a9e6cd9b271
- Disable Wi-Fi toggle when user is not allowed to change Wi-Fi state.
- Show restriction message in Wi-Fi toggle summary.
Bug: 203168097
Test: manual test
atest -c InternetDialogTest
Change-Id: I9e637a1f782997de1486921f5eb0093f59ecb02f
Move fractionToShade to AmbientState so it's accessible from both
StackScrollAlgorithm and NotificationShelf.
Fixes: 229112693
Test: StackScrollAlgorithmTest
Test: swipe down on lockscreen to go to shade
=> section gap widens smoothly
Change-Id: I860d250986fd77643e67947e4b642e5bccf1dc29
This avoids showing double status bars when the system status bar
appears in certain situations.
Test: atest DreamOverlayStatusBarControllerTest
Bug: 223641960, 224775246
Change-Id: Id7e23fe8d763f931c39bd5c2866a310fdaf785fa
