diff options
| author | Galia Peycheva <galinap@google.com> | 2019-08-21 10:20:23 +0200 |
|---|---|---|
| committer | Galia Peycheva <galinap@google.com> | 2020-02-25 07:56:28 +0000 |
| commit | 6861e91b84fb444f6a04256bd5d564730660efeb (patch) | |
| tree | 5c55c1f38cd14ac6bedaeb4f526a8d7fc954d9ee /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | a8e46412963a1ba466d1a1f180eef703d262e008 (diff) | |
Make DreamService use an Activity
Currently, the DreamService uses a floating Window to display the
content of the dream on the screen. This introduces difficulties in the
interactions with the Assistant application, which is an activity.
By design, if the Assistant is invoked while the device is dreaming, the
Assistant should be shown on top. However, since floating windows are
always drawn on top of all activities, the Assistant can't be shown on
top of the Dream.
Here, we migrate the implementation of the DreamService to use an
Activity (DreamActivity). Since the screensaver application is not part
of the framework, we can't declare the activity in their AndroidManifest.xml.
Therefore, we start the dream activity with a dedicated method in
ActivityTaskManagerService.
Bug: 133216167
Test: 1. m && ./vendor/google/tools/flashall
2. Go to Settings > Device Preferences > Screensaver > Start now
3. Verify dream appears
4. Click any key to wake up the dream
5. Verify that dream disappears
Merged-In: I8dff0a124cd1b41fb925a73528305431b49ee06d
Change-Id: I8dff0a124cd1b41fb925a73528305431b49ee06d
(cherry picked from commit 148478a85e25c86e4b333295dec03aadedc17e1a)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions