Age | Commit message (Collapse) | Author |
|
Change-Id: I6a8d7215f874fed05e9fec71b17c8a3d1e2c94e0
|
|
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
|
|
am: e211918c69 am: ff0a6eab18 am: 9ab827cc25 am: 2020cf0234 am: d40a4d4fc1
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1373837
Change-Id: I2fffd61e227a00df07b3219f4ba9c81181cd1faa
|
|
am: e211918c69 am: ff0a6eab18
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1373837
Change-Id: Ic52b887978dca4791d2d80ace3473a26141f0cc3
|
|
See https://source.android.com/setup/contribute/respectful-code for reference
Test: Presubmit
Bug: 161896447
Change-Id: I7fb8abdb8e3ca65d29a40bd7f6f090aefaa0765f
|
|
The PUK state is DONE in StateMachine after PUK is unlocked.
If two sim cards are both locked by PUK, the PUK state should
be ENTER_PUK after SIM1 PUK is unlocked.
Bug: 155135725
Test: manual
Change-Id: I0261d8be913a878e65c5240d4d39b248c2e3a5d5
|
|
The PUK state is DONE in StateMachine after PUK is unlocked.
If two sim cards are both locked by PUK, the PUK state should
be ENTER_PUK after SIM1 PUK is unlocked.
CRs-Fixed: 2675202
Change-Id: I0261d8be913a878e65c5240d4d39b248c2e3a5d5
|
|
There is a time delay that the SystemUI get
READY state from telephony,and the SystemUI
think it's PIN_REQUIRED state when check state
from telephony api. That will cause the internal status
be in a wrong state and make the screen locked.
Use new api check the SIM state.
Change-Id: Iede5925c5af2a70cc15451f8560e31f76da64caa
CRs-Fixed: 2663732
|
|
The initial goal was to remove PhoneConstants. But in doing so, it made sense to replace
an int[] array as a return type with a strongly typed class called PinResult.
Bug: 147774309
Test: SystemUITests
Merged-In: I42f2141f9378fc4f7a6f11af6073d38f917528bc
Change-Id: I42f2141f9378fc4f7a6f11af6073d38f917528bc
|
|
To customize the last puk prompt, add a new string array
Change-Id: Idbf8d36f1ca807f4c232e85621d47e48eca6c1e2
CRs-Fixed: 2614468
|
|
Change-Id: I16a4437d9876db7a6a2b07231b4584df4564bee4
|
|
Change-Id: I321486af27bd4665b73da2c51d88e293b54f3a4c
|
|
The initial goal was to remove PhoneConstants. But in doing so, it made sense to replace
an int[] array as a return type with a strongly typed class called PinResult.
Bug: 147774309
Test: SystemUITests
Change-Id: I42f2141f9378fc4f7a6f11af6073d38f917528bc
|
|
Bug: 146593004
Test: manual - pin and puk
Change-Id: Ic64cc8a48c6e28f3ac8a013cbb4c15e7e58f7f4d
Merged-In: Ic64cc8a48c6e28f3ac8a013cbb4c15e7e58f7f4d
|
|
Bug: 146593004
Test: manual - pin and puk
Change-Id: Ic64cc8a48c6e28f3ac8a013cbb4c15e7e58f7f4d
|
|
Change-Id: I30dd2dce3b0c2fcd635381413a213fe3e97be97b
|
|
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
|
|
TelephonyManager.getSimCount()
TelephonyManager.getDefault()
TelephonyManager.from()
Bug: 111498835
Test: Manual DSDS test cases
atest com.android.systemui.statusbar.policy
Change-Id: I676a70a5dbd2dcbdbbee6cd889ffd614dc42fb9d
|
|
Change-Id: I293059a06fd09d0377ea06c58cf62eeb31d4668e
|
|
Test: presubmit setup on source branch
Bug: 130289146 Create a Gradle build for SystemUI
Bug: 136279712 Daggerize FalsingManager
Bug: 137324767 "Unable to instantiate service com.android.systemui.doze.DozeService" exception breaks launcher tests
Bug: 137563419 Remove Bouncer reveal delay from bypass flow
Bug: 138787339 Allow Services and Activities to be injected into directly.
Bug: 139128921 [AS 3.5 RC2, SDK API 29 rev 2] Overload resolution ambiguity: while removing element from HashMap
Bug: 64712476 Import translations for dev branches
Change-Id: Ib7fd4706c070907fd556c3532957f3b1b046de6d
|
|
Bug: 139051615
Test: atest SystemUITests && atest SystemUIGoogleTests
Change-Id: Ic4dd5978001c208504c137cee41f363d7e70b1b5
|
|
After device's pattern lock and SIM Card's PIN lock are settled,
reboot and we can see screen keeps showing "Phone is starting".
During the process of showing SIM Pin lock, SIM Pin class handle
"Absent" event and dismiss keyguard. That keyguard has been hidden
will trigger system resume the FallbackHome activity. The FallbackHome
activity will show "Phone is starting" and leads to this issue.
Remove the code for ABSENT in KeyguardSimPin/Puk class to fix it.
Change-Id: I55e41f2d79fe057e413dd2724f504be8867040e5
CRs-Fixed: 2503092
|
|
setup simpler
Removed:
com.android.settingslib.restrictedlockutils
com.android.settingslib.helputils
com.android.keyguard
Moving sysui settings to use sysui settings resource package name
Test: Everything compiles / presubmit
Bug: 130289146
Change-Id: I5d760fa2f04439d24b455839f7bdd5cc499e840f
|
|
Change-Id: I0f9f887d6a33702a6988709d8296731cfdb8f73d
|
|
Test: tap on notification on lock screen
Test: tap on notification on shade locked
Test: swipe down from the top expanding QS
Test: swipe up from LS
Test: switch between pin, pattern and password
Test: add and remove locked sim card
Test: atest KeyguardBottomAreaTest
Test: atest KeyguardClockPositionAlgorithmTest
Test: atest KeyguardMessageAreaTest
Test: atest KeyguardIndicationControllerTest
Test: atest StatusBarKeyguardViewManagerTest
Test: atest KeyguardBouncerTest
Test: atest KeyguardPatternViewTest
Fixes: 130398499
Fixes: 130298363
Fixes: 129784068
Fixes: 130223966
Change-Id: Ib1706de259fa4b1f4ef13f654cbd931457733d82
|
|
Change-Id: Ife0402f9f6166a53c75fa57f80dee0b442ce6d28
|
|
1) Remove old bypass code for ABSENT in KeyguardPin/Puk class
and move it into KeyguardViewMediator where it belongs.
2) Fix issue where pulling out sim and then putting it back in
doesnt trigger PIN/PUK screen until turn off->on screen by clearing
SimData state for the slot that became ABSENT.
Bug: 119560495
Test: Move across eSIM and pSIM as well as manually remove PIN/PUK'ed SIMs
Change-Id: Iebf2cb046b1a1d7e0689a2329a9f78e1cbb6aca4
|
|
Change-Id: Ieb6ae3730e8b01f867f9b5120de1ab3067653d21
|
|
Test: n/a
Change-Id: I432e11b52deb7974e50f62076af3b7aa07e364b6
|
|
RootCase:SimPinView is unlocked by incorrect subId
Change-Id: I7c2b24e9c8d791d9c4f619d659e0f66e68bd3f01
CRs-Fixed: 2208323
|
|
Using the new accessibility pane title API
to identify the pattern, pin, and password unlock
screens.
Bug: 73131182
Test: Verified that accessibility events are properly
sent when unlocking the phone with each of the lock
methods.
Change-Id: I32594f4736b503e7f9e3be96e9f77a84ffcadc54
|
|
This CL add an alert dialog under SIM PIN/PUK screen when users try to
disable current eSIM profile and failed.
Bug: 62680294
Test: E2E
Change-Id: I97d8cf1ae8fb30ece48c4731e72bfdfedf69d49a
|
|
Adds the possibility of presenting a custom message on
the keyboard if you're trying to dismiss the keyguard.
This is particularly useful when you're showing the
bouncer because custom authentication (SmarLock)
failed.
Test: launch FLAG_SHOW_WHEN_LOCKED activity and
call KeyguardManager#requestDismissKeyguard
Fixes: 63940122
Change-Id: I0d88c0e59521887efa56d74874062b2b14970e4e
|
|
* Fix to properly display attempts remaining for PIN/PUK.
* On bootup show the available PIN/PUK attempts if sim
is locked on PIN/PUK.
* Show incorrect password message on entering wrong PIN/PUK
password.
In KeyGuardSimPinView and KeyGuardSimPukView, check for sim locked on
PIN and reset the flags to show the default message.
Bug: 37782683
Change-Id: I46d7d5dd86977cddecf3147add73ef6ccc64b257
|
|
am: b7dc3a3b21
Change-Id: I16555b53bbf9c743921cbd36578af3550705a242
|
|
There is the possibility of mCallback being null while
the Keyguard still has a PhoneStateListener registered
for onSimStateChanged callback. This can cause a NPE.
Bug: 66986066
Test: Manual, PIN/PUK locked SIM
Change-Id: I799c9521f787e800e259c3bdce9edee3f844f5f3
|
|
am: 43f9f0290c
Change-Id: I9e28e3975331a7af11747065761632a0566deb56
|
|
1) If the PIN/PUK keyguard comes up for a locked
SIM, it can not be removed by removing the
affected SIM. It can only be removed by
rebooting the device or entering a bogus PIN.
This change automatically clears the keyguard
when when the locked SIM is removed. It will
be shown again if the locked SIM is re-entered.
2) If the device is PUK locked and the code
**05*PUK*new pin* new Pin# is entered in the
emergency dialer, it will unlock the SIM.
By listening to the READY state, we can remove
the keyguard when the SIM is unlocked by
other means.
Bug: 64469515
Bug: 64044132
Test: Manual
Merged-In: I7b576ee7e38f141075cae094e3d1f74b7145d53f
Change-Id: I9507f80edcd4c04dfa0cc3b48a25e619aafa9eb3
|
|
Before this CL, we always show "Disable eSIM" button in SIM lock screen
if the device has eSIM chip. This may make the user who has never used
eSIM or currently is not activated the eSIM Profile confused. This CL
makes the "Disable eSIM" button only be shown iff the device has eSIM
chip and the current activated Profile is eSIM profile.
Bug: 37518023
Test: E2E
Change-Id: Id5a1325f49733528a370ec7145fe49731243bcf7
|
|
|
|
This button is used for eSIM devices. For the phone without eSIM, when
the SIM is lock, the user can remove the SIM card to unlock the phone.
This button is used to let the user disable the current carrier to
unlock the phone (the same as removing SIM card for non-eSIM devices).
Bug: 37275510
Test: manual test
Change-Id: I7e648e4bb5033c1ab3bfdfea9513e65632c49f2a
|
|
Just frameworks/ this time. More paths to come.
Bug: 24137209
Test: make -j32
Change-Id: Iff27abd26fa43296ac2fff8f534fc6742d2ae80c
|
|
Test: make
Change-Id: I3abb67e2b022737d2aa0226bb07f3966ad68fff7
|