After this cl, it could guarantee that device list always has
saved devices:
1. Even though in onCreate(Fix flaky UI)
2. Even though there is no other bluetooth event to trigger it
(e.g. no device is connecting)
Fixes: 70934171
Fixes: 63910184
Test: Build
Change-Id: Iec628d455690a68d92f201f6eac9cd97b555b2b4
Suggested language list alignment should be as per the default locale.
Test: 1. RTL language
2. Settings>System>Languages & input>Languages>Add a language>English
3. Check the alignment
Bug: 70360392
Change-Id: I934b1061fb897ac69270a493562defba4a5a1a35
Signed-off-by: susanta.patra <susanta.patra@lge.com>
Migrate transport initialization task to binding on-demand. Added
Robolectric tests for the task as well.
Bug: 17140907
Test: m -j RunFrameworksServicesRoboTest
Test: adb shell bmgr init <transport>, observed logs & transport dir
Change-Id: I2d6c1acd31741169080edef2f938fabf43b0649a
Log WorkChains associated with a given WorkSource to statsd whenever
a wakelock is acquired / released or changes.
Test: WorkSourceTest, manual.
Bug: 62390666
Change-Id: I1720ba8b1778d38067398caac7cf92c4d375f816
For now just returns raw key material. In the future we will need to
change this to use the KeyStore move api. (Once that has been
implemented.)
Test: adb shell am instrument -w -e package com.android.server.locksettings.recoverablekeystore com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I8aee4da81f0f853503f570dae8d74e1d29f124cc
This mostly completes the task. Still some TODOs around constructing
the vault metadata correctly, and exactly what the Intent should look
like.
Test: adb shell am instrument -w -e package com.android.server.locksettings.recoverablekeystore com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: Ibf5705830f577597f0cc2afdd906f6517e426d01
This is a temporary solution, while the KeyStore team works on adding a
move API to KeyStore. (At which point this will be updated to instead
return 'move tokens', allowing the user to move the key from the system's
keystore to their own, without ever seeing the raw material.)
Test: adb shell am instrument -w -e package com.android.server.locksettings.recoverablekeystore com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I2241a6da15d50c26a7b384d4e5b6f78366fb9300
What's the problem is:
1. Work profile is not running (work mode is OFF)
2. Uninstall an app
3. ACTION_PACKAGE_REMOVED is sent to work profile
4. AMS skipped the broadcast as the target user of the broadcast is
not running, but LauncherAppsService is indeed listening to .
5. LauncherAppsService failed to notify Launcher the package change.
Proposed solution:
Not skipping broadcast if its parent user is running. Please also note that
since ag/2325045, BroadcastQueue won't deliever broadcast to
receiver running in stopped users.
Test: Turn off work, remove/ Install any app in work profile, observe
that Launcher reloads accordingly.
Test: Install an app in work profile, turn off work mode, switch
to secondary user, adb uninstall that app. Switch back to user 0,
observe Launcher reloads accordingly.
Test: Reboot the device, didn't see any "Skipping broadcast of" log.
BUG: 70503418
Change-Id: I35a269b09ab83a32a13cc7bc2066c8f71ba9f960
Currently recovery agents can set/get statuses only for their own keys.
Bug: 66499222
Test: adb shell am instrument -w -e package \
com.android.server.locksettings.recoverablekeystore \
com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I5cb70ce139ca29c066d46d0bd4d2967bd3c30843
Use the same method applied for StaticLayout.testFallbackLineSpacing
and set the text size in pixels.
Test: bit FrameworksCoreTests:android.widget.TextViewTest#testFallbackLineSpacing
Tested on Pixel and Pixel XL
Bug: 68385045
Change-Id: Ib3fd29882551444d4e6e36f820dc547b22c7edbd
...so it does not block showSaveUi.
Bug: 70939974
Test: atest CtsAutoFillServiceTestCases:FieldsClassificationTest
Change-Id: I64bb20c1c617790e7281f287c567cb5c13178a6e
This implements all of recoverKeys, except for loading keys into the
AndroidKeyStore. Also omitting re-enrolling keys into the recoverable
store for now, as it is not clear whether the user will have a lock
screen set at this point. If they do not have a lock screen set, we
cannot re-enroll keys, as the platform-decrypt key is bound to the
lock screen. Also modifies SecureBox to throw AEADBadTagException for
any issues with the encrypted payload. IllegalArgumentException is
a runtime exception, so would be unexpected, but might occur if the
encrypted payload is for some reason garbage. Also, throw NPE if the
payload is null, as that is a programmer error - not something that
should ever occur at runtime.
Test: adb shell am instrument -w -e package com.android.server.locksettings.recoverablekeystore com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I4f0be412c3044f3472a6aed514f1caf54b7ee41f
In anticipation of the availability of Keymaster implementations with
multiple security levels this patch adds the additional
keystore flags FLAG_SOFTWARE and FLAG_STROGBOX.
Also, the IKeystore method addRngEntropy got a new flags parameter
for the caller to express which implementation shall be awarded the
precious entropy.
Test: Keystore CTS tests
Bug: 63931634
Change-Id: I4a4eafbdbe1290f0c7bd2bfa2ce3e5fbb06c2dd8
