Extract non-API changes to make the API change commit smaller / more
focused. These changes are mostly naming, comment and some improved
validation. There's some toString() / parsing toString() changes and
associated tests for manual testing support used in later commits.
Test: atest services/tests/servicestests/src/com/android/server/timezonedetector/location/
Test: atest core/tests/coretests/src/android/service/timezone/
Bug: 236624675
Change-Id: I8f74e4bd0ad1a34b593afdf89b3e4840420a5d10
There are two kinds of detectors, one is AlwaysOnHotwordDetector,
the other is SoftwareHotwordDetector. We don't allow to create
multiple AlwaysOnHotwordDetectors at the same time or create
multiple SoftwareHotwordDetectors at the same time.
Test: atest CtsVoiceInteractionTestCases
Bug: 193232191
Bug: 243598246
Change-Id: I849a2219bba329761f05719307c0a9247026da2a
Test: Built & deployed locally
Bug: 253155340
General TODOs :
- Locking
- Reduce logging post debugging phase
- More generalization/abstraction as create flow is added
Change-Id: Ib35fbe8a9118a62df346ecb19207e5b54f95b019
This change implements a power button behavior that prioritizes entering
a dream on press, rather than turning off the screen.
Bug: 245961904
Test: Manually as follows:
Make sure config_shortPressOnPowerBehavior is set to
SHORT_PRESS_POWER_DREAM_OR_SLEEP.
1. Set screensaver to dock then dock device. Make sure tapping power
button when screen on goes to dream. Make sure tapping power button
when screen off goes to dream. Make sure tapping power button while
dreaming turns display off.
2. Set screensaver to charge then plug in device. Make sure tapping
power button when screen on goes to dream. Make sure tapping power
button when screen off goes to dream. Make sure tapping power button
while dreaming turns display off.
3. Set screensaver to charge or dock and perform the same tests as
above.
4. Set screensaver to dock and then undock device. Make sure tapping
power button does not start dreaming.
Note that the device may charge while docked, so setting screensaver to
charge may act the same when docked or charging.
Change-Id: I9b6859b4933839841b76b832f275dcc14313f192
Add logs to see the whole process of wallpaper set completion.
Bug: 248842910
Test: manually checking logs
Change-Id: I4f68407ee9d20497a748d01efc76ca25c7dbebf9
* changes:
Describe requested visibilities in public types (3/n: server side)
Describe requested visibilities in public types (2/n: client-server)
Describe requested visibilities in public types (1/n: client side)
Because it is not clear to understand what these two methods do,
we rename them.
(1)updateVisibleActivitiesLocked()
(2)updateVisibleActivitiesChangedLocked
Bug: 235296082
Test: atest VoiceInteractionSessionVisibleActivityTest
Change-Id: Id7db3a0dc9c2a17276ae213223fa3dd6ae572b9f
(cherry picked from commit 0d7aa31d35)
Merged-In: Id7db3a0dc9c2a17276ae213223fa3dd6ae572b9f
These changes add a new status (not yet part of the SDK API) that will
enable the time zone detection service to make decisions like telephony
fallback based on information from the provider.
The status will also enable information to ultimately be surfaced to the
user in SettingsUI about the time zone detection being blocked or
running degraded due to settings like the "Google Location Accuracy"
setting on GMS device.
The SDK API changes will be made once the information passed is used and
can actually be detected from tests.
Test: atest core/tests/coretests/src/android/service/timezone/
Test: atest services/tests/servicestests/src/com/android/server/timezonedetector/location/
Bug: 236624675
Change-Id: Ia1a9f9a18454fc087d187289d761d5e3649bbaee
This CL makes the following changes
- instead of stopping any existing dream before starting a new one, now
stop *after* the new dream has been started
- do not reuse the same task for multiple dream activities
This allows a smooth inter-task transition when swiching between dreams,
e.g. between user configured dream and system dream.
Bug: 244315094
Fix: 244315094
Test: atest DreamControllerTest
Test: atest SystemDreamTest
Test: manually on device, see video in linked bug
Change-Id: I9576470ae0f54d553a0db3aee6fb720edaa5d733
Merged-In: I9576470ae0f54d553a0db3aee6fb720edaa5d733
This CL makes the following changes
- instead of stopping any existing dream before starting a new one, now
stop *after* the new dream has been started
- do not reuse the same task for multiple dream activities
This allows a smooth inter-task transition when swiching between dreams,
e.g. between user configured dream and system dream.
Bug: 244315094
Test: atest DreamControllerTest
Test: atest SystemDreamTest
Test: manually on device, see video in linked bug
Change-Id: I9576470ae0f54d553a0db3aee6fb720edaa5d733
A subsequent change will actually move the files to the other git
project.
Bug: 243194720
Test: presubmit
Change-Id: If126bb68f74852528c4da8df79831b49b5129983
If the content of activity is changed, may fill dialog be requested
to show up again. Tracks all fillable views to know the content is
changed, and then reset all flags for the fill dialog.
Bug: 236237955
Test: atest CtsAutoFillServiceTestCases
Change-Id: I58503dd4021021d4bdc8d5114ff7255178fe5408
When a DreamActivity is destroyed, the devices remains in a dream state.
This makes it look like the DreamActivity is stuck in the background but
it is actually destroyed and DreamService does not allow another Dream
to take its place.
Bug: 242368903
Bug: 241569844
Test: Manually tested by checking that when a DreamActivity is destroyed
the device wakes up from dreaming.
Change-Id: Idcb38f2332f3a8dea0add78a4ca506877aeca8f7
This CL makes the client send an integer (instead of InsetsVisibilities)
as the requested visible types to the server.
This CL also removes the usages of InsetsVisibilities from WM shell.
Bug: 253420890
Bug: 234093736
Test: atest ActivityRecordTests DisplayContentTests InsetsPolicyTest
InsetsStateControllerTest WindowContainerInsetsSourceProviderTest
WindowLayoutTests WindowManagerServiceTests WindowStateTests
WindowAddRemovePerfTest StartingSurfaceDrawerTests
TaskSnapshotWindowTest
Change-Id: I29d245e3c36a29f01bdd3347fe858727c3540ff8
Apps did not get the correct transform hint when moving
between displays because the display install orientation
was not updated correctly. Fix by always querying the install
orientation instead of relying on the cached value.
Bug: 251360251
Test: move app between displays, rotate, check final buffer transforms
Change-Id: Icd463de9407b3f22cbea510d65c8d8c1b1c986d6
Adds flag to wallpaper setting methods to allow specifying
home/lock/both. This will be implemented in master.
Bug: 253481667
Test: TreeHugger
Change-Id: I590b2972b102fba672726633a86727b167a4b02b
