| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| | |
Android 6.0.1 Release 72 (M4B30X)
# gpg: Signature made Tue 04 Oct 2016 09:47:40 AM PDT using DSA key ID 9AB10E78
# gpg: Can't check signature: public key not found
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a bug where it was possible to authenticate the wrong user.
We now bind the userId when we start authentication and confirm it when
authentication completes.
Fixes bug 30744668
Change-Id: I346d92c301414ed81e11fa9c171584c7ae4341c2
(cherry picked from commit b6f4b48df273d210d13631b4c2426482feb40c97)
|
|\ \
| | |
| | |
| | |
| | |
| | | |
Android 6.0.1 Release 61 (MOB30Z)
Change-Id: Ib003ccb606e0d77209291b757ea36399d3b65814
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Also disables app pinning when the "return to call" button is pressed
and brings up the in-call screen when app pinning is stopped if there is
an existing call.
Combination of ag/1091397 and ag/1085584 adapted for MNC.
Bug: 28558307
Bug: 28761672
Change-Id: I82ec4042bff387c845ce571b197a4a86e1dd5ec8
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- For a multisim device, when only one sim is inserted
that is pin locked, the carrier text only shows
'SIM CARD IS LOCKED - NO SERVICE' even though the
voice registration state for one of the phones is 12,
where emergency calls are allowed
- This occurs when the state above is reported for the
slot where a sim card is not inserted. We only check for
active subscriptions when creating the display text
- Add a check for when only one sim card is inserted. If
the voice registration state is out of service for both
slots, with at least one as 12 (emergency allowed)
show 'Emergency calls only' instead of 'No service'
Change-Id: Ib58b6b7431d7b29c770287037cbf07c8df101ae3
CRs-Fixed: 985955
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the font size is set to Huge, and pin lockscreen + sim unlock screen
is showing, the text for the pinpad overlaps. Reason is we enforce the smallest
maxHeight on all children, and this breaks certain screens. Just let each child
use its own maxHeight that it set to begin with.
FEIJ-184
Change-Id: I3b461f6f75a3f541281fb32efc83a891ca7b65f0
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In devices with more than one SIM, keyguard visually distinguishes each SIM
card by showing its color and its name.
This patch introduces now a configuration item that lets you choose wether or
not show the SIM display name on those cases.
Issue: PAELLA-224
Change-Id: I8fb019d4fa534b2ca2f047083c27aa9cf8b7b39c
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add sanitizePassword call after the verification is success so
that the password/pin/pattern goes to default_password. This
will avoid security vulnerability.
Change-Id: I711b9e38e1812bad9fa7ab8d0ab9e35963138a69
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In MSIM case, with two sims being locked on pin,
the second sim pin unlock screen does not get closed
even with the correct password.This is due to the
showDefaultMessage flag not being set to true after
sim pin is verified successfully.
Fix: In KeyGuardSimPinView, set the showDefaultMessage
flag to true after SIM PIN is verified successfully.
CRs-Fixed: 949288.
TICKET: CYNGNOS-2766
Change-Id: Ie31ee9fb009314555c81f3787d0ef3af4aad74c7
|
| |
| |
| |
| |
| |
| |
| |
| | |
* When the fingerprint sensor is embedded in the power key,
wake-and-unlock is total chaos. Add an option to disable it.
* The default behavior is unchanged.
Change-Id: I50c0a857daba92c17470d8089aca94099c792956
|
| |
| |
| |
| |
| | |
Change-Id: Ia9adc5b1cc3fead1203422ef51af87084b9fd3dc
TICKET: CYNGNOS-2673
|
| |
| |
| |
| |
| |
| |
| | |
Ticket: CYNGNOS-2431
Change-Id: I2f47031f9fb2cc40e61a5f57d49e985104b14024
Signed-off-by: Roman Birg <roman@cyngn.com>
|
| |
| |
| |
| |
| | |
Ticket: CYNGNOS-2462
Change-Id: Ia68e26ec2dfc23317135d933bc25204c1380bb02
|
| |
| |
| |
| |
| |
| | |
Allows user to left swipe to live lockscreen and back.
Change-Id: Ia94d735695b77a091a240e13858641cf95ac0647
|
| |
| |
| |
| | |
Change-Id: Ic627953c5df854c442671a98b5da539b994da18b
|
| |
| |
| |
| |
| |
| | |
Restore the pre-M behavior, set the separator to " | ".
Change-Id: I91a3ccfc9013269d2e14e6835e322f84b05c3eb4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the input is shorter than the minimum requirement for
PUK, then we need to alert the user with a more clarified
error rather than simple text.
TICKET: SAMBAR-587
Change-Id: I6bcf932b735891d763db54d6ba53ab7b538de720
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-Customize default Date&Time display format.
-Customize mock and Dock on or off for carrier.
-Customize accessibility on or off for carrier.
-Customize default input method.
-Customize default enable data roaming or not.
-Customize default enable mobile data or not.
-Customize default network.
TICKET: CYNGNOS-1473
Change-Id: I3a74d0113d6b730c4d7935aaa2da307ebe500566
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(At least) Qualcomm RILs report SIM unlock success as result=0,
attemptsRemaining=0. As reportSimUnlocked() causes showDefaultMessage()
to be called (via reportSimUnlocked -> handleSimStateChange ->
onSimStateChanged -> resetState -> showDefaultMessage), which accesses
mRemainingAttempts to determine the message to show, set
mRemainingAttempts before calling reportSimUnlocked().
This resets that code sequence back to AOSP; it got broken in commit
18281968a799556a68abbb992adfd04c4cc754ff.
Change-Id: Icf7b15f1bf55bb32c8b58bd6c77109971cbc463b
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I'm not sure of the behavior on QCOM RILs, but on Broadcom RIL
(and probably other RILs), this will eat into the user's PIN
remaining tries. Given that the user is only given ~3 tries, this
is a very bad idea.
In addition, if onAttachedToWindow is called multiple times before
the RIL replies, this can completely delete the retry quota leading
straight to the PUK screen.
Change-Id: I339f1b6d79d543ae8930a7bb95acf823fd5ae20e
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Revert "SystemUI: Support display for radio tech"
This reverts commit 598421095aacb599d4bc8e8fcea20734d7847d0c.
Revert "SystemUI: Customize StatusBar for Chinese carrier"
This reverts commit d473d0b22ac8704c39d5eedd0d7b12f60a2fa215.
Revert "Statusbar: Add customized icons for Chinese carrier"
This reverts commit a6324c7293bebeff4c6ccee8c2a8af38b7a150a8.
Change-Id: Ib03c7455a04bd7d63a8c0a7d238040099e94e89c
|
| |
| |
| |
| |
| |
| |
| | |
* Variable size pattern lockscreen
* Toggle dots/error pattern visibility
Change-Id: Ie109e82c1fb2fd96b07e977e1cd76ae3acb865ff
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Revert "Hide emergency button when OOS"
This reverts commit 5ccaaff4818af8d48e072cbd2b8b784e5cd0c593.
* Buggy on MSIM, making the button perma enable.
Revert "EmergencyCall Button on Swipe Lock Screen"
This reverts commit 5f712cc90ebb11a04e72ab6b04a1229eeddef9fc.
* Introduces some ugly padding to make room for a button we have
disabled by default since forever.
Revert "Emergency call button on Swipe lock Screen."
This reverts commit f17cb289ae5f760a51b8463fe270b336d1e3b408.
* See above, adds the option to enable the button itself.
Conflicts:
packages/SystemUI/src/com/android/systemui/statusbar/phone/KeyguardBottomAreaView.java
Change-Id: Ie95f0b075e25b625298eac3c06d278e6cb1e7b17
|
|\ \
| | |
| | |
| | |
| | |
| | | |
git://codeaurora.org/platform/frameworks/base into cm-13.0
Change-Id: I008f052e4e27b44457c8343d20f6e1ba943c8e1f
|
| | |
| | |
| | |
| | |
| | |
| | | |
Hide emergency button when OOS in lock screen
Change-Id: Ia3c360755ab74b2c688833f9972710304a195f65
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When SIM state is changed to ABSENT/NOT READY, Closing Keygaurd
is not required Explicitely in M as it is handled by default.
Hence re designed the logic to avoid exceptions.
Change-Id: I8024b6ddd75c2630734e8d750d83f88c994e165a
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Support monitor locale change and display for radio tech.
CRs-Fixed: 653747
Change-Id: I66d0bb29d0121a19ada0c1ad03ceeec9a03243df
|
| | |
| | |
| | |
| | | |
Change-Id: I4e9fb06db7b9ba05e4a7bbe11916bb2271af4727
|
|\ \ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Android 6.0.0 release 26
Conflicts:
cmds/bootanimation/BootAnimation.cpp
core/java/android/accounts/AccountManager.java
core/java/android/app/AppOpsManager.java
core/java/android/os/PowerManagerInternal.java
core/java/android/os/storage/IMountService.java
core/java/android/provider/Settings.java
core/java/com/android/internal/widget/ILockSettings.aidl
core/res/res/values-mcc204-mnc12/config.xml
core/res/res/values-mcc219-mnc02/config.xml
core/res/res/values-mcc730-mnc07/config.xml
core/res/res/values/config.xml
core/res/res/values/symbols.xml
packages/SystemUI/res/values/config.xml
packages/SystemUI/src/com/android/systemui/doze/DozeService.java
packages/SystemUI/src/com/android/systemui/statusbar/CommandQueue.java
packages/SystemUI/src/com/android/systemui/statusbar/ExpandableOutlineView.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/DozeParameters.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/DozeScrimController.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/NavigationBarView.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/NotificationPanelView.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/StatusBarHeaderView.java
packages/SystemUI/src/com/android/systemui/statusbar/phone/StatusBarKeyguardViewManager.java
packages/SystemUI/src/com/android/systemui/statusbar/stack/StackScrollAlgorithm.java
services/core/java/com/android/server/LocationManagerService.java
services/core/java/com/android/server/am/ActivityManagerService.java
services/core/java/com/android/server/pm/PackageManagerService.java
services/core/java/com/android/server/power/PowerManagerService.java
telecomm/java/android/telecom/Phone.java
telephony/java/android/telephony/CarrierConfigManager.java
telephony/java/android/telephony/RadioAccessFamily.java
telephony/java/android/telephony/ServiceState.java
telephony/java/android/telephony/SignalStrength.java
telephony/java/android/telephony/TelephonyManager.java
telephony/java/com/android/ims/ImsCallProfile.java
telephony/java/com/android/ims/ImsReasonInfo.java
telephony/java/com/android/ims/ImsSuppServiceNotification.aidl
telephony/java/com/android/ims/ImsSuppServiceNotification.java
telephony/java/com/android/ims/internal/IImsRegistrationListener.aidl
telephony/java/com/android/internal/telephony/RILConstants.java
Change-Id: I99c6edb8e25a77145b5adef97d0d55bfbe676959
|
| |\ \
| | | |
| | | |
| | | | |
mnc-dr-dev
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 24273807
Change-Id: I497fcd2ee527ec22d14ff1b6c30be4ef9a878980
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When going over the handler, it could happen with a bad interleaving
we thought that Keyguard was not showing when getting the
onFinishedGoingToSleep message, so we stopped fingerprint
authentication. For some reason our state machine for canceling
/restarting authentication didn't work correctly so the fingerprint
listening state was not correct.
Bug: 24178814
Change-Id: I2a4731f195982395244c12e4d33b2b7d561c5671
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We used to start fingerprint authentication in onFinishedGoingToSleep.
This was a UX issue because then users couldn't place the finger on
the sensor immediately after pressing the power button because
onFinishedGoingToSleep is significantly delayed (around 900ms after
pressing the power button).
Bug: 23570959
Change-Id: I0bf557ebd10e6a8b033ab98a78aa338bf6538dcc
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To make unlocking work if keyguard is in occluded state and user
taps on a notification.
Bug: 22855718
Change-Id: Ide632f524a635e3e37741abaa77e258394c9a6e2
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 23718313
Change-Id: I6c88fbba9ae460594b8e2f1a77c6545b305e5813
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixes bug 23699953
Change-Id: Id099443b830f5608c0bf955075c3407b401f3d53
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
SystemUI uses it to start authentication again after lockout reset
expired.
Bug: 22846755
Change-Id: I90a987c6aa4ac52cc7e7aff1bce262d1db3f12ee
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 23214670
Change-Id: I8192ded696c1908871b2578194e2a226bb51b1e9
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Split off from I0af11da1b7cd7c8d837bc5ba3a62ef2ffca74b1b.
The initial value did not matter previously because
a SystemUI crash triggered the boot logic and forced
a manual entry before fingerprint works.
Long term the timeout logic should be moved to StrongAuthTracker
so it can be shared with the trust agent implementation (currently
implemented by the trust agents themeselfes)
Bug: 22846469
Bug: 22115393
Change-Id: I0af11da1b7cd7c8d837bc5ba3a62ef2ffca74b1b
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 22846469
Bug: 22115393
Change-Id: I6ef5322d02e540fc043e7f20d3aabf595ce7c224
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When calling cancel() on the cancellation signal, it doesn't happen
immediately. Now, because of a state messup during boot, we go
through the sequence
startListeningForFingerprint
stopListeningForFingerprint
startListeningForFingerprint
However, the cancellation callback from stopListeningForFingeprint
happened AFTER the second startListeningForFingerprint, so we assumed
that fingerprint detection was not running anymore but in reality it
was - leading to weird states and all kinds of small state messups.
Introduce a state machine to track when we we called cancel but
waiting for the confirmation of FingerprintService in order to track
this properly.
Bug: 23380500
Change-Id: I403479fb749cf7c22b73611b69698e8b771777d0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
After gettin a callback onAuthenticationSucceded we set the
fingerprint listening state to false. However, when waking up, we
immediately started listening again because the state was false.
Protect against that by only calling authenticate only once, except
when the unlock doesn't go through because unlocking with fingerprint
is not allowed.
Also fixes some animation "jank" because of the state messup.
Bug: 23304421
Change-Id: Ic83ac0f1590dd4f8017bb55dca9e19a60cfdf99f
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Move all fingerprint related to logic in on central class in
SystemUI that knows all the state of the UI so there is exactly ONE
place in which we decide what to do when we acquire a fingerprint.
- When pulsing and we get a valid finger, we fade the contents of the
Keyguard out and fade the scrim out almost the same way as we would do
in a normal wake-and-unlock sequence.
- Hide shadows while dozing, so we don't see the artifacts when we fade
the dozed Keyguard out.
Bug: 23225107
Change-Id: I82f78e61f2530cf7d507ade80f6f0a340c082567
|
| |\ \ \
| | |/ / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When pulse was about to turn on and at the same time we were starting
a wake-and-unlock sequence, there was jank because the scrim handling
was not correct anymore. Now, abort the pulse when we are wake-and-
unlocking so we don't see flickering with the scrims anymore.
Bug: 23217476
Change-Id: I331f513b68fb1832b4372d3e2e518b31b556a43c
|