Put the background drawable on status_bar_container instead of
status_bar because we always want the status bar background to
fill the entire container.
status_bar receives new margins when corner display cutouts are enabled
which may prevent status_bar from taking up the entire
status_bar_container space.
Test: atest SystemUITests
Fixes: 148355955
Change-Id: Ic7e0c0a79908d2a58d4595d239062435253edfda
This migrates the previous Tron events into Westworld. Now we only log
the spec/package for each tile, not the position.
The position in most cases is not interesting as it can be obtained from
other places (in the future, lift this info from QSTileHost for
example).
Fixes: 147508828
Test: manual using statsd_testdrive
Change-Id: I7b27a31b303d6ebe894041433fbf9d81e57a9f3c
1. Add some checkers and java doc:
- loadHtmlDescription
It filters the <img> tag which do not meet the custom specification and the <a> tag.
- loadAnimatedImage
It checks the resource whether to exceed the screen size.
Bug: 149516547
Test: atest AccessibilityShortcutInfoTest & manual test
Change-Id: I8ecad186fc9e4bb6799ded296805cdc5353c5010
Merged-In: I8ecad186fc9e4bb6799ded296805cdc5353c5010
(cherry picked from commit c6e3836915)
Stub jars should not be in statically linked except for inside
other stub jars.
Bug: 145995723
Test: build, flash and reboot
Test: FrameworksIkeTests, FrameworksNetTests
Change-Id: I503616de0143cc39dd189ae689de3e8d77c345da
Merged-In: I503616de0143cc39dd189ae689de3e8d77c345da
(cherry picked from commit 5fc0bbaae7)
The ActivityTaskManagerTestService has a special method to start a
DreamActivity. This CL adds a verification check before the activity is
started to check that the caller is the currently active dream
component.
Bug: 133216167
Test: atest DreamManagerServiceTest
Merged-In: Id71b4cbc57c6569f58b6d906cc8361c104a507dc
Change-Id: Id71b4cbc57c6569f58b6d906cc8361c104a507dc
(cherry picked from commit 20dc51820a)
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 148478a85e)
* changes:
Fix issues in register/unregister client API implementation
Add a TRM use case priority hints info object
Add requestFrontend implementation in TunerResourceManager
Implement TRM setFrontendInfoList logic with unit tests
Revert "Add tests for start singleTop/singleInstance activity fo..."
Revert submission 10112771-single-for-result
Reason for revert: b/149877125
Reverted Changes:
I923a0d9aa:Avoid creating new instance on top when started fo...
I7d47580f8:Add tests for start singleTop/singleInstance activ...
Change-Id: Ice262d1b8cada3b6c6fe0a5e8000bb59e0536596
(cherry picked from commit e0012bda2a)
It appears that the original reverts missed the master cutover to rvc-dev
for rvc-release builds. b/150138994 tracks this issue
Bug: 149877125
Bug: 150138994
The PackageSetting object is sometimes copied during
scan/install and will not match the reconciledPkg's pkgSetting.
This meant the usesLibrary parsing assigned the values to one
PackageSetting object, but dexopt read from the other, copied
object.
Unfortunately this copy logic leaves the two settings out of
sync and thus the isUpdatedSystemApp flag has to be copied
between them.
All of this would be great to resolve in a future refactor.
Bug: 150142306
Test: adb install -r {out_of_blueline_target}/product/app/CalculatorGooglePrebuilt/CalculatorGooglePrebuilt.apk
installs correctly, with dexopt run with the correct paths
Change-Id: Ifca3bafcea1b8858baf4a22ddd264d5e07a0f1e5
It was being removed from adb_temp_keys.xml but not adb_keys.
Bug: 150138676
Bug: 111434128
Test: atest AdbDebuggingManagerTest
Change-Id: I3c31394e4480e787c771e193b179a472d6ee4a62
Sony introduced some logic that combines devices kernel splits into one
Android device based on identical pid, vid and non-empty uniq. Therefore
populate this field with device ID.
We can change that to a separate uniq attribute in register JSON file if
necessary later.
Bug: 38511270
Test: getevent -li shows that uniq is populated.
Change-Id: Ieca0b826c86e9cad7fa3d3c8f98b9cfd54d20c73
Rename "duration" field to correspond with the
actual time unit.
Bug: 139439353
Test: Successful build
Change-Id: I3e9b3ac5778d6fa4b6de35079743bdf6e85b7560
