The code use to always announce for accessibility when resetting the
password field, which results in announcing "Four characters replaced
with zero characters."
The fix is to only announce this message when the user needs to try
again.
Fixes bug 24331841
Change-Id: Icc9450d37b9338a39709f50666829d4a007b2b65
Tracks why trust agents are disabled and shows
a generic message on the keyguard. Dedicated strings
in follow-up.
Bug: 22704995
Change-Id: Ibb4fd9c9386c4dc12f0734004502b9a9cc6ded79
If you tap the enter key twice on the keyguard PIN entry
screen, the second tap can sometimes register because keyguard
hasn't been dismissed yet. The fix is to ignore a second attempt
after the PIN has already been verified.
Fixes bug 19216025
Change-Id: I73a004e91e43f3da65ec84f90de6943e717d737f
A message can now be shown on the keyguard bouncer
explaining why the bouncer is being shown.
Bug: 21618072
Change-Id: I25aea9cc242abbf6a133fb42cc4407f5c2f3f688
- Split password entry enabled and input enabled into two states;
- Disable input during lock check;
- Disable password entry when locked out;
- Don't show soft keyboard if password entry is disabled on resume;
- Auto show soft keyboard when password entry becomes enabled;
Bug:20542149
Change-Id: Iffe3f205776143ac21e25e337d5b7a0e6994ebf2
Also removes the Klondike from the content description.
This reverts commit c199ef3759
from change I3dd05fa1714da36795f448718fd70f1cdbfe2584
Bug: 18528774
Change-Id: I8a85076f939a8b78075b5a6322009ebfd78bf8d3
- Only call userActivity in down touch event
- Use normal timeout when QS is open
- Clean up old code regarding user activity in Keyguard
Change-Id: I968eeed33fef44def37b68eb1ddc63f1a531ab35
The pin unlock design was changed according to the spec
and new animations where introduced for the password field.
Bug: 13735707
Change-Id: I76f5e873bd0ea4f34ca3d2cd971223f0a83e2f28
