The persistence wrappers are started using the correct file
corresponding to the current user, in case that the controler is created
now in OWNER.
Test: manual, restart sysui on secondary user
Bug: 156758594
Change-Id: I6734817a0368aedf9001009fcf4d124e9239b0c2
Do not allow behaviors to update the status string
directly. Potentially queue up text updates and change it during an
animation.
Bug: 154625942
Test: visual
Change-Id: I916ca083e0b44e01879ba659ac82a3189017631b
targets parking in memory, even if targets are still loading on UI.
Backfill targets of top 8 apps into DS row instead of top 4, if the row
is not full.
Bug: 156470651
Test: atest CtsSharesheetTestCases:android.sharesheet.cts.CtsSharesheetDeviceTest
Test: atest com.android.internal.app.ChooserActivityTest
Change-Id: Idefd6c225fca723d6d266b78ef41a4201483c634
The actual cache clearing is not async anymore, so we can report the
status to the calling app. Here, we just change the documentation to
make the caller aware of the 3rd possible activity result: EIO.
This value is returned if an error happens while MediaProvider is
clearing the cache. In this case, we don't know how much of the cache
was deleted, if at all.
Test: build
Bug: 155290762
Change-Id: I3a04a9b5b6b07c6ec61e97a4cb0d3bc8b10b0370
This would help to debug why MediaSessionService fails to create a new session
without leaving log from the app side.
Bug: 155993197
Test: Build
Change-Id: I8427467d5866a5611d539ec08425be6e948b5540
Otherwise it can happen that we swallow previous printer updates and
never end up getting a valid on-printers-updated call.
Fixes: 156222510
Test: atest PrinterDiscoverySessionLifecycleTest
Change-Id: Idab7399a6ab41ba9051cfcbbeebf4c45d6bfc053
The names of the individual modules do not quite follow the pattern
that java_sdk_library uses so this temporarily sets the following:
naming_scheme: "frameworks-modules"
That causes java_sdk_library to use a naming scheme that matches the
one used by the individual modules of this. It will be cleaned up
later.
Test: m update-api
Bug: 155164730
Change-Id: I56b4db67e919673f353dd2238b63c5bd3e749b05
When the notifications views are filtered out, reset their initialization
time, so now we can rely on the initialization time to determine whether
the notification was recently shown in the shade.
Fixes: 153885122
Test: atest NotificationRankingManagerTest
Test: manual
1. post grouped notifications
2. swipe down notification shade to view notifications
3. toggle on/off DND and see notifications are not ungrouped when
they're unfiltered
Change-Id: Ib9b45cd13ead51d7df2484e91d159cd268799e9a
Add a new priority PRIORITY_DEVICE_PEAK_REFRESH_RATE, and a new config
setting config_defaultRefreshRate which maps to that priority. This
allows an OEM to easily specify a default frame rate different from the
peak frame rate.
Bug: 148978450
Bug: 154648391
Test: - Added new unit tests to verify DisplayModeDirector handles min,
peak, and default refresh rate settings correctly.
- Modified a Pixel 4 to set config_defaultRefreshRate to 60Hz, confirmed
we default to 60, but that an app calling setFrameRate(90) switches us
to 90.
- Confirmed that the "smooth display" and "force 90Hz" options on Pixel
4 work correctly.
Change-Id: I00c82eea39a914b5b38506dd3143feb936749254
Full screenshot UI would expose edit/share actions that are not
appropriate for SUW. ThiS CL removes all the UI in this situation and
just does a haptic with a toast indicating that the screenshot has been
taken.
Bug: 151797808
Test: - Verify behavior unchanged w/ normal screenshots.
- Verify that tooltip UI is used during setup wizard.
- Verify that screenshots taken during SUW are saved.
Change-Id: Id9791265088e34f067cea68fd1eaba597e3c97b0
