KeyguardUpdateMonitor onFingerprintAuthenticated currently doesn't
immediately update the trust state. TrustManager.isDeviceLocked()
should return "unlocked" after FP is authenticated.
Fixes: 37963501
Test: Two tests as follows
1) use custom app that polls isDeviceLocked(), make sure
it returns "unlocked" after FP is authenticated but keyguard is showing.
To get that state, slide keyguard up slightly and touch FP sensor
without letting go of the other finger.
2) with at least 2 accounts, run the app on both accounts.
when switching users, the app should show that the "inactive/underneath"
user is locked. the app should report that the current user is locked
before touching fp, and unlocked after touching fp
Change-Id: I2a11411deebf369d85dee62cffdcd631bd99649f
we have a link to the client which is enough to find the views.
Also there was some cases where the windowToken was not updated
properly. This is moot now.
Also: Read a array of views from the client to speed up the
client<->AutofillManager communication.
Fixes: 38070352
Test: CtsAutoFillServiceTestCases
1 Started autofill, saw fill UI
2 Home button
3 Kill activity in background
4 Recents -> back to activity
5 Saw fill UI restored
Change-Id: I7c2c9411204fa5d65867efae9b7296399121c3a2
Instead of relaunching activity in-process, ask ActivityManager.
requestActivityRelaunch to relaunch it. It can make the correct
decision when activity needs to be relaunched.
Test: manual - switch between users to trigger ActivityThread.handleApplicationInfoChanged
Bug: 37992833
Bug: 37412579
Change-Id: I662a04e3cd82115a6008cef9308a2cf1038d51e1
ForegroundToken is now ImportanceToken, and doesn't actually
cause an app to become foreground (that is not needed for
toasts anyway).
Also improved output and logging -- new logs for changing
in key uid stats, and when force stopping services after a
uid goes idle.
Test: manual
Change-Id: I44dd391bb8d37857be1359f4b7021dc8d2cd0285
Otherwise it may cause a deadlock due to reversed lock ordering.
Test: create guest/switch/remove
Change-Id: Id11263ee2d358ab97b212477f896db7313605448
Fixes: 37347817
We've seen evidence of lab devices racing with other apps that are
using cache space immediately after tests wipe it clean, which can
cause test failures. To mitigate this, try our best to wait for the
device to go "idle" by watching for broadcast queues to fully drain.
Also improve javadocs along the way.
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest
Bug: 37486230, 37566983, 37913442, 37914374
Change-Id: I4d430db443b6fa6d33a625fe07b90279b5d51c12
This commit builds on top of prior API commits. It
adds code to the system server, but in a disabled way.
The system server is responsible for monitoring two
(configured) package names: one for the "updater app"
(provided by the platform) and one for the "data app"
(provided by the OEM). When either package changes
the updater app is triggered via a privileged
intent.
The updater is then required to communicate with the
data app and report back to the system server.
Unit tests are included for the major components.
To run:
make -j30 FrameworksServicesTests
adb install -r -g "out/target/product/angler/data/app/FrameworksServicesTests/FrameworksServicesTests.apk"
adb shell am instrument -e package com.android.server.timezone -w com.android.frameworks.servicestests \
"com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner"
This contains a cherry-pick / conflict resolution of
commit 68f666693a after an automerger skip.
(cherry picked from commit 68f666693a)
Test: See above.
Bug: 31008728
Merged-In: I8f82cdcc2b574778a7e0d0184270f305b69ee17b
Change-Id: I8f82cdcc2b574778a7e0d0184270f305b69ee17b
The PopupWindow anchoring offset should be based on the bottom of the anchor
view, but we were using top. Hence, the PopupWindow.tryFitVertical() was
failing to place it above the view in some cases, even when there was plenty
of space.
Fixes: 37991460
Test: manual verification with virtual view sample
Test: CtsAutoFillServiceTestCases pass
Change-Id: Iffdfe0d7858e865192338184d63bf5b93ba7108f
- Better explanations of some strings.
- Fix to use the right package when an item is pressed in
the foreground services dialog.
- Improve java docs on Service.startForeground().
Bug: 37925387
735566 lv - Android - [Source] Context unclear or missing:
Apps running in background
Bug: 37925888
735566 lv - Android - [Source] Context unclear or missing:
Tap for details on battery and data usage
Bug: 37897953
735566 gl - Android - [Source] Context unclear or missing:
LEFT_SIDE, RIGHT_SIDE
Bug: 37943079
Music is dying mid playback
Test: manual
Change-Id: Ied41932c61f59335bd18dfba3fcb13af28a0bddd
The low priority notifications had their contrast calculated
against the white background and weren't satisfying
our contrast requirements.
This also aligns the case where the app had no colors better,
and ensures that it's actually using the secondary text
color there.
Test: existing tests pass
Change-Id: Ic11e9d06783e60998f35e0eb7f6f29fb1d86c7df
Fixes: 37444266
