In order to completely mute the ringer (no vibrate), introduce an extra
state beyond mute, which mutes the vibrator as well, if it was enabled.
Bug: 5530217
Change-Id: Ib1f299ee6bbca56c1aa7e1100662591362d08307
Note that this will currently get rid of the Tethering option as
DUN tethering is broken, but that should get fixed shortly.
bug:5495862
Change-Id: I3a45529649bf05e1e6631069fc830b4051da4fd3
1. Now the NumberPicker has a max height and width for which is looks
good but can still shrink if there is not enough available space.
bug:5512787
Change-Id: Ieea88cafa8408e1d4160bab4bfe2b771bd79f7f8
Saves 270dp^2 of pixel memory: 290K on mdpi, 650K on hdpi,
1.2MB on xhdpi. Multilockwave is still 60fps on crespo.
Bug: 5497875
Cherry pick 2f4207086e2177f8970538a3d8e921eb13c14b00 to MR1
Change-Id: Ib77695cb4256a484f5c61af1159e5e3df8cce9ba
1. Added handling for hover events that are transformed into
touch events and given to the touch event handling code
if accessibility is enabled.
2. Now swiping across the handle unlocks the device for both
cases - accessibility enabled or disabled.
bug:5513324
Change-Id: I7031690d69b1a2737e2ce4d1871d69d7dfbf3006
Only Latin-1 based passwords are supported on the system at
this point. As such, we need a way to show a Latin-1-compliant
keyboard when unlocking the device.
It is expected that 3rd party IMEs honor this mode for Latin-1
password dialogs. If not, this change will cause lockscreen to
revert to using the Android system IME for entering the password.
Change-Id: I59bb56f6f5968b5abc50cf1b9b26c19ca4f183e4
This fixes three issues;
- Make the background black while the transport is showing.
- Show scrim sandwiched between artwork and overlapping UI.
- Remove gaps in sides of background assets.
Change-Id: I563fc680c4c042d8b25ec37332aeab528cf838ca
If you turn the device from portrait to landscape mode and immediately
invoke the lockscreen, it will come up in landscape mode and switch to
the desired portrait mode within a couple of seconds. Previously,
Face Unlock would come up in landscape mode, but its position would
not change once lockscreen corrected itself, causing Face Unlock to be
partly off the screen.
This has been fixed by checking if we are already bound to Face Unlock
when the layout is created. If this is true, then the layout is being
created due to a change in orientation, and we stop Face Unlock, and
restart it at the new position.
This commit also adds a fix where we now use INVISIBLE for the Face
Unlock area when it is not showing instead of using GONE. The
dimensions of the Face Unlock area is 0-by-0 when set to GONE, and we
want to avoid the possibility for the Face Unlock service being
assigned a zero area. I'm not sure if this was ever causing problems,
but it certainly is not the intended behavior.
Also cleaned up some comments and logging.
Change-Id: I68deb49cb26dafb5c238167d0c23f0eed2cfb75a
