request at max
To simplify orchestration around handling multiple override
requests, we are reducing the OverrideRequestController to
only having one override request at a time. If a new request
is added, the previous request will be cancelled and removed.
This change also means that we can remove the SUSPENDED status
of a request and the accompanying callbacks
Bug: 216495664, Bug: 207686851
Test: OverrideRequestControllerTest
Change-Id: I787f2ce8567812a633c0afdd5b3f684da4508249
With this CL, the back and IME switcher buttons on the navigation bar
have the same color transition even when they are rendered by the IME.
Note that the behavior is still behind a flag
persist.sys.ime.can_render_gestural_nav_buttons,
which is still off by default. There should be no observable changes
no matter whether the flag is enabled or disabled though.
Fix: 215549533
Test: Manually tested with ThemedNavBarKeyboard sample
1. Build aosp_coral-userdebug and flash it
2. adb root
3. adb shell setprop \
persist.sys.ime.can_render_gestural_nav_buttons true
4. adb reboot
5. make -j ThemedNavBarKeyboard
6. adb install -r \
$OUT/system/app/ThemedNavBarKeyboard/ThemedNavBarKeyboard.apk
7. adb shell ime enable \
com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard
8. adb shell ime set \
com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard
9. Open the Dialer app
10. Focus in the top edit field.
11. Tap "EXTENDED LIGHT NAVIGARION BAR" mode
12. Make sure that the navigation button color changes from light
to dark with animation.
13. Tap "EXTENDED DARK NAVIGARION BAR" mode
12. Make sure that the navigation button color changes from dark
to light with animation.
Change-Id: I41a3478a97d67b238c4424d93acbcad646aee0d2
* changes:
Add API to configure LPS maintenance mode behavior
Add TestApi to force Low Power Standby to be active
Add TestApi wakelock flag to have system acquire wakelock
Allowlist active voice interaction session from Low Power Standby
Introduce Low Power Standby API and wakelock restrictions
The current RecentTasks fetches the recents app (based on
config_recentsComponentName). However, it does so for user 0. In some
cases, the recents app might not be installed in user 0 (even though it
is installed in other users). We need to fetch it even in that case, so
that recents can work on those other users. (Otherwise, the attempting
app will not only not do recents, it'll probably crash.)
Bug: 216636343
Test: manual confirmation on a headless user 0 device where launcher is
uninstalled on user 0
Change-Id: Ib2b536e997d58f8fb34c75e92a1cdd843b4b04fa
When "dumpsys activity" is called with special arguments (like
--list-dumpables), dump() should be handled by Activity itself,
not the subclasses, otherwise the end result would be spammed.
This CL fixes that behavior, but only for apps targeting T (so it
maintains backward compatibility for apps that are explicitly
checking for the special values).
Bug: 149254050
Test: m update-api
Test: manual verification with 'adb dumpsys activity ...'
Test: atest CtsAppTestCases:android.app.cts.ActivityDumpTest
Test: adb shell dumpsys platform_compat|grep DUMP_IGNORES_SPECIAL_ARGS||echo NOT_FOUND
Change-Id: I918c9a6649cb66f9e2b6509a643005fac110d152
* changes:
Add bottom sheet fill UI for Autofill
Implement actions on client and service for bottom sheet
Notify Autofill while activity started
Adds APIs for Autofill bottom sheet UI
