* commit '31dfff783eeb9ac856bc2fbfa14e7af5190fd717':
Fix content alpha
Removed makeInvisible() function
Making the reordering play nice with the 3D widget carousel
Fixed misplacement of cancel(X) button for Face Unlock
Fill in logic in WidgetPager to ignore music when reordering.
Attempt to fix bug on devices where multi-user support is disabled.
Implement correct music widget positioning in keyguard
Render camera widget correctly after shell restart.
Moving persistence calls to background.
FUL uses square aspect ratio for all layouts fixes b/7426399
Addressing a couple comments on previous CL
Impose a height & width downward on challenge views.
Fixing some regressions in tablet reordering/deleting.
Disable lockscreen window anim when launching camera.
* commit '5c12bc5851056f114893f3d381f9fc8785e2cdb0':
Fix content alpha
Removed makeInvisible() function
Making the reordering play nice with the 3D widget carousel
Fixed misplacement of cancel(X) button for Face Unlock
Fill in logic in WidgetPager to ignore music when reordering.
Attempt to fix bug on devices where multi-user support is disabled.
Implement correct music widget positioning in keyguard
Render camera widget correctly after shell restart.
Moving persistence calls to background.
FUL uses square aspect ratio for all layouts fixes b/7426399
Addressing a couple comments on previous CL
Impose a height & width downward on challenge views.
Fixing some regressions in tablet reordering/deleting.
Disable lockscreen window anim when launching camera.
This is now being done inside stopUI instead of its own separate
call since it needs to be done on the UI thread inside FaceLockService.
Change-Id: Iaf3a203f7f201ba4dde4c878f457e765f11e6c0e
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
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
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 makes it so that the view is hidden immediately when
a call to stop is made. This also changes the call in onPause to
only stop and not go to the backup because we still want Face Unlock
to show as the view is being dragged down.
Change-Id: I66d8fc24e82dc3a0155f7d59d8ced932cb584660
...for lockscreen sometimes and remains black / blank
Add some debug output to try to track down what is going on.
Change-Id: I98a96c5da9c04b988e948f6fc2766d927db49ebf
Integrate from proto app
* New assets
* Layout changes
* Dragging behavior change for sliding challenge
* Realign camera for new padding
Change-Id: Ia177c60f59f1fc74000d95fc39b048321acf1246
Fix for issue found in #7420259
Not sure if this fixes the actual ringtone issue, but it clears the way.
Change-Id: I7fd5584df2dc254ba7281f57e51143c79bfcff63
this would cause the TYPE_ORIENTATION sensor to report NaN after
40 to 800 hours of up-time. this problem only affects the older
and deprecated SensorListener API.
Bug: 7434842
Change-Id: Ie8593cca9c98e4907e417db4106c06151e3ee9a1
