| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
If MDTP is activated the device will be wiped, instead of recovery.
Change-Id: I6ab1b82841e4d6e90a8d156dea03448674f64446
|
|
|
|
|
|
|
|
|
|
|
| |
The back button cannot do anything from this activity as it is
only ever launched first thing at boot. So do not permit going back.
Note that screens launched from here (emergency dialer, keyboard config)
still work and their back buttons still work.
Bug: 20730074
Change-Id: I939e05450e5fbd61d12890325c4afe9dcad35c1e
|
|
|
|
|
|
|
|
| |
Requires matching framework change:
https://googleplex-android-review.git.corp.google.com/#/c/692822/
Bug: 20184626
Change-Id: I04bfb9ed61a7b40fbc28fbc0b4b10bf848b34a2c
|
|
|
|
|
|
|
|
|
|
| |
In the language & input settings, the auxiliary IME subtypes have been
hidden since they should not be a default. With Id156c85535a22, now we
can explicitly control the behavior of input method picker.
Note the this CL should not change any user visible behaviors.
Bug: 20763994
Change-Id: I9f797d07ba02363fab58ceb9aecb3cc11fbc407e
|
|
|
|
|
|
|
|
| |
CryptKeeper activity is now disabled by using primaryUserOnly, instead of
broadcast receiver. This allows to avoid bringing up the process, when it
is not necessary.
Change-Id: I5d1f979b96093c6769f6c920b18517971835a7ad
|
|
|
|
|
|
|
|
|
|
|
| |
For secondary users, disable CryptKeeper activity in a broadcast receiver of
USER_INITIALIZE intent. This change has the following benefits for guest
user switching:
- The code will be executed earlier in the user switching flow, when the
screen is frozen by WindowManager.
- Initialization of CryptKeeperActivity is skipped
Bug:18670536
Change-Id: I60300198b605c26ad15afe2c874d5f1be7da5087
|
|
|
|
|
|
| |
Bug: 18292029
Change-Id: I2a78775d0505a3064838443ea631fee0ad612e5c
|
|
|
|
|
| |
Bug: 18292029
Change-Id: I02b6eff56902859ae3aba4909656553f4b322b0c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since patterns and passwords can't be shorter than 4
elements, we shouldn't count them against attempts to unlock
the device. If we do, we risk resetting the device
due to stray input.
Bug: 18211475
Bug: 18273380
Change-Id: Ib329cd3383471483cda68bfac4278b17d0c09c57
Conflicts:
src/com/android/settings/CryptKeeper.java
|
|
|
|
|
| |
Bug: 17875087
Change-Id: I7729a4fcb993def912e950ad0ea59fd64bfc34d3
|
|
|
|
|
|
| |
Bug: 17875087
Change-Id: I78ba98901bc74ae654414c0a4a303b104a629965
|
|
|
|
|
| |
Bug: 17659622
Change-Id: Ibd44f5c619f61764ef4e4a3447f241e2f73339b5
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This will help us track down who requested a data wipe.
Bug: 17412160
Change-Id: I46b3f12a661a406450d23a7974513f40beb23c8d
|
|/
|
|
|
| |
Bug: 17551103
Change-Id: I4fd182b7ac7a9ad7c1483979d4510b50b52e520f
|
|
|
|
|
|
|
|
|
| |
Otherwise, the lockscreen can be shown during the decryption
challenge, which hides the challenge activity window until
the next reboot.
Bug:17512377
Change-Id: Idb6b5b3dddb3cf2dc70b784413ea310c401880af
|
|
|
|
|
|
|
|
|
|
| |
- Changing package from android.telecomm to android.telecom
- Changing package from com.android.telecomm to
com.android.server.telecomm.
- Renaming TelecommManager to TelecomManager.
Bug: 17364651
Change-Id: Ia6e2d082eac1c1f306da691e95dd9bfb9afd37eb
|
|
|
|
|
|
|
|
| |
Requires matching framework change
https://googleplex-android-review.git.corp.google.com/#/c/535832/
Bug: 17213613
Change-Id: Ia8006f4a9cb5909d83f1848d9acfbc3f1e0ab5fb
|
|\
| |
| |
| | |
into lmp-dev
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
PhoneManager
- handlePinMMI docs should explain what a Pin is and what MMI is
- rename isInAPhoneCall to isInCall
- rename showCallScreen to showInCallScreen
- merge this class into TelecommManager, we don't need both
Bug: 16960458
Change-Id: I8285f15747b66fdfad93d203d848d4a62c0f9b2a
|
|/
|
|
|
|
|
|
|
|
| |
Also clear pattern a little more quickly, and show owner info
even from before encrypting (since we're fixing pattern visible,
we should fix owner info too in the same way)
Bug: 17059314
Change-Id: Ie9ccd4a892a1dec32ebe60567d3b72dd6fe25060
|
|
|
|
|
|
|
| |
Needs string change
Bug: 11477689
Change-Id: I1dcca59483bff32a939b8a7d052eafebd8a1eef0
|
|
|
|
|
| |
Bug: 16496992
Change-Id: Ibdd4bbbf9a9eeafee5e0e5ed48464d524628cf12
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tablets may be used in docking stations thus need to support landscape mode.
Phones will not be, and having them rotate is both ugly and annoying.
Also this matches lock screen behavior.
The attribute screenOrientation is not themeable, so the only way of doing
this is programmatic.
Test for truth of bool which is only set for sw600dp devices and
clear the nosensor setting from the manifest if set.
Bug: 16405551
Change-Id: I5b3f945b89402e5aa39642c2c06e98f9ca1ce298
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
White on black material theme
Center text
Remove fade to black task
Fix emergency call button
Note - does not implement all requirements of frames in the defect. More
to follow.
Bug: 15328359
Change-Id: I878e59dccffff366ba2484bb77482e168cbd2b81
|
|
|
|
| |
Change-Id: Ie0ba36ef55869f2d7cfd3e460541c6f3bd08da55
|
|
|
|
|
|
|
| |
Did not reenable after entering wrong password.
Bug: 12434219
Change-Id: If8b0c22213a345b3dd0f92e02710c155c7adcd1c
|
|
|
|
|
|
|
|
|
|
| |
Show keyboard on retry with PIN or password
Show correct message on cooldown
On return from emergency call, don't override cooldown
Don't show keyboard on return from emergency call if in cooldown
Show back functionality on emergency call
Change-Id: I5cc93cb09ad758b72521bd43cfad1040be2e5f8d
|
|
|
|
|
|
| |
Currently pattern is left on after a failed attempt. This change removes
it after a timeout.
Change-Id: I77830510b17396f6e64a482816f6041af0fdc166
|
|
|
|
| |
Bug: 15159008
Change-Id: I9bb6f86c2941cbd93572c25716d21691a4fefbef
|
|
|
|
|
|
|
|
| |
To enable marquee'ing, you have to call setSelected on the relevant control.
Comment added to explain this. Also see defect 15327172 filed against
SDK documentation to properly explain this.
Change-Id: If8f70baa1b682070b312fa689b2edd77b50d2d6e
|
|\
| |
| |
| |
| | |
* commit '3afbdf006057c93f930694e26306a3cc9cea34e4':
Update showCallScreen to use Telecomm (6/6)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Use TelephonyManager instead of ITelephony for showCallScreen so that
the invocation routed to telecomm instead.
Bug: 15008165
Change-Id: Ib674e2e48efaa1cc97d1513dc2c2b27fdb343657
|
|/
|
|
|
|
| |
Have to call setSelected to make marqueeing work.
Change-Id: Ic00012c150a9cacfff2b11f2938ea0674a1f45e9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On power fail/reset, an encrypted device will sit at the enter password screen
indefinitely, chirping. This is designed to attract the attention of the user.
However, it also flattens the battery, and the user who's attention is not
drawn will discover a discharged phone the next morning. We have had many
complaints about this.
Keep current functionality, but power down after 10 minutes. It's a compromise,
but seems reasonable.
@bug 12582489
Change-Id: I895c0147bed978ecf6984af2c748f971dfa0d221
|
|/
|
|
|
|
|
|
|
|
|
| |
Messaging currently implies encryption only works with PIN or password
(K functionality). Now that in L we support encryption with PIN, pattern,
password or swipe/none, we need to update the strings accordingly.
@bug 14257692
@bug 13674657
Change-Id: I055db1289c2c2750d217b50b653a7f36ff304aca
|
|
|
|
|
|
|
|
|
| |
Depends on framework change from
https://googleplex-android-review.git.corp.google.com/#/c/435138/
Bug 13526708
Change-Id: I16189b629b5515ec5175e05155ba4ec0c27d22fb
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need to disable pattern control when in cooldown. We also need
to hide the back button completely in pattern mode.
Bug: 13329798
Change-Id: Idefea60d95db1810d340c69cc730a286011363db
|
|/
|
|
|
| |
Bug: 13327729
Change-Id: Ie83dda98558b66c824c15975310a8fb1835e900f
|
|
|
|
|
|
|
|
|
|
|
| |
Use plumbing provided by dependant change to bring up correct dialog
at boot time.
Needs matching framework changes from
https://googleplex-android-review.googlesource.com/#/c/412885/
Bug: 8769627
Change-Id: Ib04a2875e051a7cccca035fadb25978dfec22491
|
|
|
|
|
|
|
|
|
|
|
| |
The fix in Change Ifbe4cdf40e3b76d2069ecace940f85fa58f31187 causes
keyguard to be more aggressive about showing itself.
CryptKeeper itself should explicitly dismiss keyguard.
Fixes bug 11680832
Change-Id: I87287762b73bdffc6f1800379f02f70f4bd873a8
|
|
|
|
|
|
| |
Bug: 10993393
Change-Id: Idaddd01f099ae40283eb86fd92232845f9d436b8
|
|
|
|
|
| |
Bug: 7480506 Encryption screen shows back button
Change-Id: Iba2706fd6b61303178b472071f32d65bdf72e50d
|
|
|
|
|
|
| |
Bug: 7302014 CryptKeeper logs PII data
Change-Id: Ifb18c428c70e97f28ceeced2fa0aa6e9247a5372
|
|
|
|
|
|
| |
Bug: 7302014 CryptKeeper logs PII data
Change-Id: I4dec3a827a5b6880b1c0995b8adebf34315c4773
|
|
|
|
|
|
| |
Bug 7132230
Change-Id: I0253637e6d464afc229cf11ffe69852bf44fe261
|
|
|
|
| |
Change-Id: Ic95136fd5934afdd53a08bfd640d40add67fdb44
|
|
|
|
|
|
|
|
|
|
| |
Fix b/6531158 (Stop showing the keyboard)
Fix b/6532201 (Stop removing the text view, and prompt the user with a message)
Fix b/6155075 (Stop listening to MCC/MNC changes)
Change-Id: Ibf8414fe57bdd0acf6c20f3194c52b168b9292c6
|