Age | Commit message (Collapse) | Author |
|
Change-Id: I1e21c5890b5b2e2f2855f09960bc8eec8aa922bf
|
|
Change-Id: Id1a205bf3f0609c0b13e4bea377056c3b06299fa
|
|
bfec35b4f4e7fc70cfa2c4c209c9edf3cacb7f95
Change-Id: I423b0aa056a5f6ad601874f4bff41299b35f0a7f
|
|
Change-Id: If3509f3a660e820f4c8c0b29e007faa868e1f089
|
|
This reverts commit 0f53fd20d5f5a986f6140de89d7d5623466d847b.
The previous version of this didn't account for padding in onMeasure
(I'd taken this out when copying from FrameLayout, as I didn't think we
used padding), which is applied based on window insets. Tests also added
to check this case.
Forwards we go again :)
Bug: 170858298
Test: Included. Manually tested on phone, with feature enabled too; PIN/Pattern/Password all render correctly.
Change-Id: I7b1f35a185214ffdd2187f1c059f77535197a215
|
|
This reverts commit 868e770b824b5d776d64fd9364f24a6aa1ed5ab5.
Reason for revert: Breaks password entry - b/180993584
Change-Id: I9a1771b795c90b1cfe6c2457d390ac53235c6c94
|
|
I'd like to test other things (like tap makes the IME move), but to do
that means replacing the mock with a proper fake. That can come later,
but this at least tests that the flagging works correctly.
The changes between this and
commit cae34b8e22f8a7baa845bfd31f472ed728c67a89 is the bouncer height is
now measured using wrap_content, so the placement can be controlled
properly by the outer View (as the position of the bouncer changes
depending on the size of the screen).
This reverts commit cae34b8e22f8a7baa845bfd31f472ed728c67a89.
Test: Included
Bug: 170858298
Change-Id: I18428a6df9abf0e8e37c1c179be6843e4eee793c
|
|
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: I7ae9d1441579068a17fc6cf013176fd291de004a
|
|
Change-Id: I7d4929024872b369444e276a60ded06e37b1fefb
|
|
Fixes: 179775696
Test: atest SystemUITests && manual
Change-Id: I23721545632093850182416ae8a6213662b04e6b
|
|
This reverts commit 6c5bfcb40fdcf2499098daad37577e7ead67699a.
Reason for revert: Bug: 179493042
Test: Manually verified
Change-Id: Iebcaa9e92a2f83419c07936aa5aa3c81970da34a
|
|
This is currently enabled by settings
persist.sysui.keyguard.one_handed_keyguard_enabled to true. If enabled,
this will cause "one-handed able" security modes to be measured with
half of the width of the SecurityViewContainer. Tapping either side of
the screen will then move the keyguard by changing the margins.
There's some flaws here, but it's a start. There's a frame of the
bouncer being on the wrong side of the screen if the keyguard is on the
right, and it doesn't respond to opening/closing the device properly yet.
Bug: b/170858298
Change-Id: Ib997b9b3cb4ca7a069c805c7a8f3a79434eebd4c
Test: Incoming :)
|
|
Change-Id: I6a8d7215f874fed05e9fec71b17c8a3d1e2c94e0
|
|
0d6a9012a73a2d999d52aaefca0a6ad52322db31
Change-Id: I881bbcdc63fcbafa8966064cccb7ce1edc710062
|
|
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: I7683b2234b601032ee606fbaabd474c5e2f6e989
Fixes: 169081305
Fixes: 169020145
|
|
Move the guts of KeyguardSecurityContainer into
KeyguardSecurityContainerController. This removes a lot of
Dependency#get calls, and is another step towards simplifying our
view inflation process.
CustomViews that previously implemented KeyguardSecurityView now
all extend KeyguardInputView, allowing them to be simultaneously
treated as one while also being recognized as a View (the interface
required a lot of casting back and forth to a View).
LockscreenUtil is made a Singleton in this CL.
Bug: 166448040
Test: atest SystemUITests && manual
Change-Id: I6fa05012c55f5e003ab551d2f8360891a62fa2a7
|
|
It is far easier to move _everything_ into SysUIComponent, and then
selectively promote things back to GlobalScope and/or WMScope than
it is to try to do it one at a time. With this change, though lots
of files are touched, very little actually changes structurally.
After this change goes in, folks should stop using @Singleton quite
so freely. Most things should live in @SysuiSingleton. @Singleton
is due to quickly be replaced by @GlobalScope.
Bug: 162923491
Test: atest SystemUITests && manual
Change-Id: Idc31d3d83b030581fb1fa869f7fafc4f2d3a8828
|
|
Caused by new SIM state check logic. It thinks when
the SIM state is READY, it will not handle PIN/PUK
lock event from telephony to avoid multi lock screen
and other issues.
Fixed by not dealing with the puk lock procedure
in such method.
Change-Id: Icbd237b60550c097eecd87da6a16a74e33595622
CRs-Fixed: 2718677
|
|
There is unexpected input dialog for SIM PIN.
Because the SystemUI set it sim state to ready after
verified the PIN lock, but the sim state in the
telephony is in PIN_REQUIRED.So the SystemUI will get
another security screen.
Do no act to PIN_REQUIRED after in READY state.
Change-Id: Ibaeec117cc67002e96d6125347f7694af59a7a0b
CRs-Fixed: 2669805
|
|
This CL replaces all the reference of IccCardConstants.State
with TelephonyManager SIM card state values.
Bug: 111498835
Test: Manual
atest com.android.systemui.statusbar.policy
Change-Id: I810cce9ff418e34a8dbea06e91fa25b2300647e0
|
|
Test: make
Change-Id: Ifbe07dad012b863a5f99c443db6de66aaacc4b82
Fixs: 140034863
|
|
KeyguardBouncer.needsFullscreenBouncer.
The view is just proxying to an underyling object. Query the object directly.
Bug: 140059518
Test: atest SystemUITests.
Change-Id: I797f7c6a3d8734795d8a34a3709eaeed2e571dfa
|
|
Bug: 139051615
Test: atest SystemUITests && atest SystemUIGoogleTests
Change-Id: Ic4dd5978001c208504c137cee41f363d7e70b1b5
|
|
This CL introduces a way of blocking IPCs on the main thread.
This is enforced by StrictMode, and enabled on tests and eng
builds.
All current blocking IPCs were whitelisted and bugs will be
filed, in order to fix them for R.
Bug: 139360025
Test: adb logcat
Test: atest SystemUITests
Change-Id: I45af2619605ee36b6bae83ef080272c62754b654
|
|
Currently when both sims are locked on PIN, upon exhausting
PIN attempts for SIM1 PIN, SIM1 PUK view is not displayed
and the user is not able to unlock the PUK.
This is due to while fetching the getSecurityMode in Key
-GuardSecurityModel, the ordering of checking the security
mode is PIN first and PUK later.So when one sim is locked
on PUK and the other is locked on PIN the ordering of checking
the PIN first is causing to return PIN as security mode in place
of PUK. This will lead to PUK lock screen not been shown to user.
Fix: In KeyGuardSecurityModel.java, while querying the security Mode
modify the order to check for security mode i.e PUK locked state first
and then PIN locked state.
In KeyGuardSimPinView and KeyGuardSimPukView, check for sim locked on
PIN and reset the flags to show the default message.
Test: manually test
Bug: 34796244
Change-Id: I157959d9eb313b9d3af84f86e1429448a0f7f065
|
|
Test: make
Change-Id: I3abb67e2b022737d2aa0226bb07f3966ad68fff7
|