Before the FUL service started, the FUL cancel button was positioned
off of the right side of the window. This was because the
FaceUnlockView (derived from RelativeLayout) was calling
super.onMeasure() incorrectly, preventing it from using the new
'square' size when laying out child views.
Change-Id: I2f1e86617da5c8f37123febab2e433288bdea062
This moves music state management into KeyguardViewStateManager to allow
KeyguardWidgetPager access to it.
Fixes bug 7442977
Change-Id: I113b6d1c8848d60ae53b99e697b33e1e33d67853
This always inserts the music widget to the left of the camera
widget if it exists or as the right-most widget when music is
playing.
Fixes bug 7425361
Change-Id: Ida992fbdde254a2de0ab12c63e003ccfeab7a94a
Sometimes on quickly stopping and starting a user, a race condition
causes the user entry to disappear, causing crashes in Launcher and
SystemUI. Removing this step, since it doesn't really leave much
residue behind.
Bug: 7434849
Change-Id: Ia188602f1a79f75d307397459c2a03fadee4c722
Widgets that did not launch Activitys would not display the unlock
screens when they were tapped. Now any window that is shown with
FLAG_DISMISS_KEYGUARD set while the keyguard is locked will
cause the unlock screen to be displayed.
Bug: 7301530 fixed.
Change-Id: I90d11b52d2b63260bdb5f2b6eb7e98eb7a4d9331
When the referenced bug was filed, face unlock was only showing as a
tiny sliver on tablet layouts. Due to other changes in the lockscreen
branch, it was no longer a sliver, but was still an incorrect layout,
with a width much greater than height. This change makes face unlock
square for all layouts.
The face unlock RelativeLayout was replaced with a custom
FaceUnlockView derived from RelativeLayout. The new view forces a
square layout using the same technique used by LockPatternView.
Note that there is still a bug where the pattern view covers the widget
area on portrait tablet layouts. The face unlock view has this same
issue, but may resolve itself when the pattern bug is fixed.
Also note there are two other Face Unlock tablet bugs that existed
before this change (and therefore are not caused by this change):
- flash during transition from spotlight animation to camera preview
- PIN backup is upper-left instead of centered
Change-Id: I550eccfa3924f230a9dc43f0a9b59f1ea55a9273
Cherry-pick I2ca647595275fde610047f681722b19dc41416da from master:
This commit adds the valid ranges to the latitude/longitude
parameters in Geofence.createCircle()'s javadoc.
Bug: 7172696
Change-Id: Iecef09a5fa11be586b05f9f75107c3e77e637d28
This means that challenges may no longer wrap_content, even
vertically. But it's the only way to rationalize across
different challenges, some of which want to be a fixed size,
some match_parent, and some wrap_content.
This change also fixes some problems with the password view
as well as PIN view (usable again on sw360 devices like
Galaxy Nexus).
Bug: 7427586
Change-Id: I648e68c5159fef7cf594d4bfe8f6d4bdd5da6b6a
Proto-Id: I280b4875a9deee5dfb7409bdfa8ed0b96fbd0cff
This is a cherry-pick of Ieb5ef28ab1e6b4b3c4d2b8ceb3a601083b4f8e2f
from master.
LocationProvider's javadoc suggests using Criteria instead of
LocationProvider, which is deprecated. Criteria is deprecated, too,
now, so we suggest LocationRequest instead.
Bug: 7434865
Change-Id: I00375a419c745bb46ff454bc5e4aa0bfac2b3fc3
