Integrate from proto app
* Positioning at the lower end
* Transparency animations
* Show security frame when dragging until it fully settles
Change-Id: Ic5e5b0bbaa50a123c3492b63c15df3ffba37832d
This change also moves to an absolute-distance model of
tracking the panel instead of a delta model; this allows us
to make the decision about the handle size in only one place
(when first detecting the gesture) instead of requiring us
to mix it into the arithmetic everywhere.
Also fixes the drag-too-slowly-and-the-panel-doesn't-move
problem.
Change-Id: I9bdbadd968134ad5ad67eaef9539536fb5cfe1a1
Proto-Id: I0c2f484da89f063995384c263aa9f5f03339ed7c
- Fix crash in CameraWidgetFrame after rotating to landscape
- Fix pages drift to the left bug
- Address Jim's comments on c/245706
- Disable camera widget if landscape
Bug: 7419070
Bug: 7417798
Bug: 7418781
Change-Id: I5c730c7c1baf3c1872367b6392e6786578765298
This new API makes it possible for an application to ask on
which Display it should show a Presentation based on the currently
selected media route.
Also added a new API on DisplayManager to query displays that
support a certain category of uses.
Improved the documentation of the Presentation class to explain
how to choose an appropriate Display for presentation.
Bug: 7409073
Change-Id: Iab451215e570ae55f3718fc228303143c800fe51
Since the code is now very careful about loading layouts, we
sometimes get into a situation where the security view isn't shown.
This CL ensures the security method is shown at least once
when the view is inflated.
Change-Id: If80a46adb868d92194610eccaf9d8d6c2a2c5b3d
- remove redundant signals that were causing keyguard to be rebuilt unnecessarily.
- add a check to ensure we only handle configuration changes if the view is actually showing
- only reconstruct view if screen is turning off or if the configuration changes.
Change-Id: Ia9c7830e370feed6af36cc139d4cd3c5ca0be4fd
This maps activity on the SlidingChallenge to the security
challenge view. Currently it calls onPause() on the SecurityView
if the view is on the move or is hidden.
Change-Id: Ide5f2200e45d8996fa91af06ac2059c3d125ea6f
Integrate changes from prototype app
* Add callbacks for bouncer state changes
* Dismiss the bouncer if focus leaves the challenge area
* Increase edge swipe region, treat this as a slop for
SlidingChallengeLayout's drag handle. (This allows edge swipes in
the drag handle area to still page widgets instead.)
Change-Id: I732de1a8d999a34c7cc8aa8ed99e24b597f3444c
This means the visual glitch is possible again, but reduced since
the layout transitions are disabled.
It's more important to bring back nav buttons for incoming calls
(for the secure, screen off case).
Bug: 7411356
Change-Id: I83005a77930ec7f70a613b3396f85ab1a5fdd96c
Give the GC a chance to collect the current bitmap if it needs to,
as it allocates memory for the next one. This helps avoid OOM situations
that can sometimes occur in extreme circumstances (huge bitmaps)
Also set the default_wallpaper to the right default size.
Issue #7352961 Wallpaper edge is cut-off while scrolling through home page
Change-Id: If76b55061d04b29af7f66a6162e307b8b53bf4ae
* commit '3e297339f8b77d54f520d5471c90c9d04e78400e':
FIx bug #7414801 Should make private and final View.TEXT_DIRECTION_DEFAULT and View.TEXT_ALIGNMENT_DEFAULT constants
We can't make the navbar slippery anymore if lockscreen is
going to intercept all the touches. :)
Bug: 7413021
Change-Id: I1658262e43c37d0b1a554cda434ac43c0a0a86c0
1. The accessibility layer has a back door for a UI test automation code running
from the shell to attach. The unregister code does an incorrect identity check
and as a result the register UI test automation service is not disconnected
until its process is killed. The fix is super safe and simple.
bug:7409261
Change-Id: I4b1da18be6c5619dadd4a58fca6724529bc59dea
