Age | Commit message (Collapse) | Author |
|
Caused by AOSP new refactor and it keeps the string in
a view of the notification panel.Furthermore, the unlock
string is not kindly design to 2 SIMs with PIN enabled.
Fix it by setting the string to null under kinds of SIM
state change event,even with 2 SIM PIN lock enabled.
Change-Id: Ia0c5db950575cf78eb6dfbb85f9f090739c2298e
CRs-Fixed:2947841
|
|
Change-Id: Ic23aece12c3bbd2b4dcf3205fdbcdd1601deabec
|
|
Had to support both old/new UX for PIN for a while. Cleanup the
unneeded code and simply the ripple.
Fixes: 187340770
Test: atest KeyguardPinBasedInputViewControllerTest and visual check
Change-Id: Ie12cd93c7aaba5a3ef172792a5dd2a41f2196447
|
|
Change-Id: I1e21c5890b5b2e2f2855f09960bc8eec8aa922bf
|
|
f23acf33ff3684586b7dc66026b518ada77eed84
Change-Id: Id555c35af9a5ed2570504cd6b4e3ca3b5892c340
|
|
With this change, taps outside of the bouncer inputs increase the
FalsingManager's belief that erroneous taps are happening. If the
belief becomes strong enough, the bouncer will be retracted.
Special attention is given to ensure that actual password inputs
are not recorded by the falsing manager. Valid button and pattern
inputs do not have their motion events recorded, but do _decrease_
the FalsingManager's belief in pocket dialing. Thus, a few bad taps
mixed with good taps will not retract the bouncer.
Test: atest SystemUITests && manual
Bug: 172655679
Change-Id: Iac8d2a2f41764f3c1cccb66b9d332c489cabca77
|
|
This uses the HistoryTracker on pin-based input to determine if a
tap outside of an intended region is a false touch, retracting the
pin input if we believe pocket dialing is occuring.
To do this, the cl properly integrates the HistoryTracker into
falsing, at least for single taps.
Most importantly, HistoryTracker#falsingBelief now return 0.5 when
it is unsure if a tap is false or not, and tends towards 0 when it
believes it's valid and 1 when it believes it's false.
HistoryTracker#falsingConfidence remains unchanged.
Test: atest SystemUITests && manual
Bug: 172655679
Change-Id: Ie771b1bf8ac564af7ffb68e190772fff5c562e89
|
|
Change-Id: If3509f3a660e820f4c8c0b29e007faa868e1f089
|
|
Revert submission 13536242-b179775696-depenency-get-keyguard
Reason for revert: Candidate reversion for broken tests: b/180440298
Reverted Changes:
I6d0271692:Add ViewController to CarrierText.
I4d9a4a21f:Add Controller for Emergency Button.
I4c76d99f9:Remove Dependency.get from KeyguardSliceTextView.
I730593fcf:Add injection to ClockProvider.
Ifbb93e624:Remove Dependency.get from KeyguardStatusView.
I237215456:Remove final calls to Dependency.get from keyguard...
Change-Id: I7b46dbad24050cfe6a363131549169602fda1f13
|
|
Support both the old-style PIN views and the new ones behind the
keyguard layout flag.
Fixes: 179121004
Test: adb shell cmd overlay disable com.google.android.systemui.gxoverlay
Change-Id: If588df2503d9337fe63b300fb24da09ef0a6d1e9
|
|
This removes all the calls to Dependency.get from EmergencyButton.
Bug: 179775696
Test: atest SystemUITests && manual
Change-Id: I4d9a4a21fe8a8a0306b110a2fbaaa3ea91507d05
|
|
Bug: 178561525
Change-Id: Ifb7c4a1c94e1f4cab710826d57282b981a46e990
|
|
This gives other parts of the system the ability to temporarily
override the falsing manager, telling it to ignore a given gesture.
The intent is to give other parts of the system a chance to include
their own falsing information (such as whether a button was tapped or
not), giving the FalsingManager more context about what is going on.
As of right now, their is no way to feedback this context-aware
falsing information back to the FalsingManager. An API for this is
still being explored.
Bug: 172655679
Test: atest SystemUITests && manual
Change-Id: I87ee94a2386622ebff7580346325ae07e3bb5f5d
|
|
Change-Id: I1cca277b923fed07896ee2e268c8da7df72eedce
|
|
Styling bouncer and shade so they have solid backgrounds and read colors
from themes instead of named resources.
Scrim now fetches colorBackgroundFloating, and views get their background
from colorBackground.
Switching from light to dark theme will make bouncer colors update without
re-inflating any views.
Bug: 173561906
Bug: 173561901
Test: atest ScrimControllerTest
Test: atest KeyguardSecurityContainerControllerTest
Test: manual, switching to dark theme annd showing notif guts
Change-Id: I372e8b688d7bbddd698381accd074b7655788cd0
|
|
Change-Id: I51f7864ca57206ba4034be7db7ae9f36d5c53f59
|
|
Test: atest TelephonyManagerTest
Fix: 171884262
Change-Id: I9cdc11c49e4ca602cfa1464e5f424c4a96798cfe
|
|
Change-Id: I6a8d7215f874fed05e9fec71b17c8a3d1e2c94e0
|
|
b00c929394cb6bce158265af9606a8eb5a79e47a
Change-Id: I42d17262a789d2eb106a924b442a9d3debcc35e4
|
|
Revert submission 12656261-revert-12585643-b166448040-keyguard-message-area-NUUJOVRYJS
This also fixes the original issue introduced in this CL.
KeyguardAbsKeyInputViewController#reset would call mView#resetState
instead of its own internal resetState method. However, all the logic
from the various resetState methods had been moved from the views to
their controllers. Simply calling resetState direclty resolves the
issue (line 105 of KeyguardAbsKeyInputViewController).
Reason for revert: Fixing http://b/169231892 and http://b/169145796
Reverted Changes:
I7683b2234:Revert "4/N Setup Controller fo KeyguardSecurityCo...
I5cbe04c0c:Revert "5/N Add KeyguardSecurityViewFlipperControl...
I11dff38ad:Revert "6/N Add Controller for KeyguardPatternView...
I55c250121:Revert "7/N controllers for remaining Keyguard Pas...
Ie84234cb8:Revert "8/N Remove View Injection from KeyguardMes...
Ic62f199a5:Revert "9/N Clean Up Keyguard Class Structure"
Change-Id: Ie3669e0c9a23ffd4443ced0fb08ec754f1df55db
Fixes: 169145796
|
|
Revert submission 12585643-b166448040-keyguard-message-area
Reason for revert: http://b/169081305 & http://b/169020145
Reverted Changes:
I6fa05012c:4/N Setup Controller fo KeyguardSecurityContainer....
Iecf265744:5/N Add KeyguardSecurityViewFlipperController.
I90ab99b2f:6/N Add Controller for KeyguardPatternView
I4b74eddd1:7/N controllers for remaining Keyguard Password Vi...
I805286374:8/N Remove View Injection from KeyguardMessageArea...
I362755980:9/N Clean Up Keyguard Class Structure
Change-Id: I55c250121c2e234a41b30f2d647c44f6cb631028
Fixes: 169081305
Fixes: 169020145
|
|
Revert submission 12585643-b166448040-keyguard-message-area
Reason for revert: http://b/169081305 & http://b/169020145
Reverted Changes:
I6fa05012c:4/N Setup Controller fo KeyguardSecurityContainer....
Iecf265744:5/N Add KeyguardSecurityViewFlipperController.
I90ab99b2f:6/N Add Controller for KeyguardPatternView
I4b74eddd1:7/N controllers for remaining Keyguard Password Vi...
I805286374:8/N Remove View Injection from KeyguardMessageArea...
I362755980:9/N Clean Up Keyguard Class Structure
Change-Id: Ic62f199a51a15d8384450b8f181f3c5a0b988d7f
Fixes: 169081305
Fixes: 169020145
|
|
KeyguardInputView no longer implements KeyguardSecurityView.
This cl seeks to clean up some of the lingering vestiges from this
large chain of refactors.
I have manually tested none, swipe, pattern, pin, and password views
for successfully unlocking, as well as multiple failed attempts
resulting in temporary lock outs.
Fixes: 166448040
Test: atest SystemUITests && manual
Change-Id: I36275598001184e774677cf2dbb16dec8dc7ab5b
|
|
No real functionality changes (hopefully). Just moving
objects into controllers.
Test: manual
Bug: 166448040
Change-Id: I4b74eddd18d29dd8966caa32c5960ff8be2e6f43
|