* ChangeId DROP_CLOSE_SYSTEM_DIALOGS doesn't need to be @TestApi.
* BROADCAST_CLOSE_SYSTEM_DIALOGS permission needs to be @SystemApi given
its protectionLevel
Bug: 181593849
Test: Builds
Test: atest CloseSystemDialogsTest
Change-Id: I6cbbc4a396f920e6cc60299ba827c76158e2e7cf
Remove the internal timeout to clean up the starting window, for now on
the developers are responsible for removing it.
- Also clean up some redundant members.
Bug: 181838419
Test: atest SplashscreenTests
Change-Id: Iebcccbca454eb7fda4bed637cb5866deec36cf6b
- Added the following testAPIs to replace the usage
of adb shell commands in tests:
* stopUser and ACTION_USER_STOPPED
* waitForBroadcastIdle
- Changed the documentation for switchUser to correctly
reflect that it accepts CREATE_USERS
Test: verfied that tests can access the APIs
Bug: 181030374
Change-Id: I92b92471a18cf97a118d3f1946d6e06c277a76f1
Some apps, such as the shell, do not seem to be able to always access
the DeviceConfig, and get an NPE. Fail gracefully when this happens.
Test: manual
Fixes: 182907280
Change-Id: If4de34f2022c165ad8bf5a950c8a04cfd5abacc9
Back when we added Intent.ACSD to publicAlternatives of collapsePanels()
in ag/13035420, we didn't have the complete picture of which use-cases
the Intent.ACSD would remain valid for and I thought there might still
be 3p valid use-cases. Turns out cinek@ was right in that CL.
After finished implementation, there are not 3p valid use-cases for
Intent.ACSD anymore - this is explained in detail in ag/13331897 but
TL;DR; for security reasons we're deprecating the intent and in S the
platform will automatically be responsible for collapsing the shade
where applicable. So, the result is that there are no public
alternatives to collapsePanels() anymore and this is on purpose since
having this capability lead to abuse.
Test: Builds
Bug: 159105552
Change-Id: I5ead6f83d19b00a27498a0ef42b6957667964644
We define three change ids in this change:
OVERRIDE_MIN_ASPECT_RATIO
OVERRIDE_MIN_ASPECT_RATIO_MEDIUM
OVERRIDE_MIN_ASPECT_RATIO_LARGE
Depending on which change ids are enabled, we override the minimum
aspect ratio of a given app to the value corresponding to the treatment.
Bug: 174042980
Test: atest WmTests:SizeCompatTests
Change-Id: I2db2a3acbd051b651b7ab0dc4c51c38a0276430b
Otherwise they get out-of-sync and sometimes AR will not relaunch
the app, but the app client will think it needs to be relaunched
Bug: 181697795
Test: app configuration tests pass.
With 3-button nav, open app in split and observe launcher
reconfigure properly.
Change-Id: Idc8d71d92d9ae107e3adb949a2137de6c08908e9
Created a new metrics called mLastTimeComponentUsed in UsageStats.
It is persisted and loaded as other metrics.
Bug: 175829712
Test: core/tests/coretests/src/android/app/usage/UsageStatsTest
Test: cts/UsageStatsTest
Test: UsageStatsDatabaseTest
Test: UsageStatsServiceTest
Test: UsageStatsPersistenceTest
Change-Id: I10cf5c40cf5955246a6a04e96ac0352b4ed29acd
* changes:
Hide app name from collapsed CallStyle.
CallStyle now supports contextual actions (e.g. smart replies)
Fix the layout issue with the expand button of the CallStyle
PacProxyInstaller class is running a thread all the time and is
listening to intent ACTION_PAC_REFRESH so it would be better to
make it be a system service with a manager class PacProxyManager
which is obtained with getSystemService(PacProxyManager.class).
Besides, rename PacProxyInstaller to PacProxyService will
be easier to know it's the service for PacProxyManager.
ConnectivityService is going to be a mainline module and it
needs constructor of PacProxyService to be SystemApi.
However, in current design, it needs to pass a handler and
an int arguments to the constructor which would be difficult
to maintain if just expose the constructor directly.
So, define a listener for the event that the current PAC
proxy has been installed so that the handler and the int
arguments can be removed from the constructor.
Bug: 177035719
Test: FrameworksNetTests
Change-Id: I2abff75ec59a17628ef006aad348c53fadbed076
* This prevents the color change problem when expanding minimized notifications.
* The expander for minimized groups will use the non-highlight colors.
Fixes: 176899982
Test: manual
Change-Id: I592ebc1edc18075537c81bfa8d36dee9b6d011d1
Before, LegacySplitScreen is not allowing non-resizable to enter split
screen. Now, it also checks supportsNonResizableMultiWindow.
Fix: 181377395
Bug: 176061101
Test: manual
Change-Id: Iae4c65b5c8b0a139dbf8af55caba9f6c99d1f470
It copies time zone API to keep in consistent.
Bug: 172891783
Test: atest services/tests/servicestests/src/com/android/server/timedetector/*
Change-Id: Id32745540483eafe8292a0de2221e6a7ff22cc84
Load default wallpaper by device's CMF color in WallpaperManager. The
fallback is to use default wallpaper if no matching wallpaper with
corresponding CMF color.
Bug: 178161042
Test: Build ROM and manual test
Change-Id: Iea818784f05f730e3cde79e95771a84db1b39225
Also some small fixes:
* Bind the title in the CallStyle builder.
* Remove an unnecessary findViewById.
* Rename a method overload for clarity.
Bug: 179178086
Test: manual inspection
Change-Id: I6e96864c17718b9729b108e4db82534aad33675f
* This required that call style also has a collapsed state which has no actions. Removing actions from the collapsed state resolves a bunch of bugs that were being introduced. There's just too much of SystemUI that assumes collapsed notifications don't have actions to fix this right now.
* To make the collapsed state match stylistically, I also had to remove the progress bar from that state for vertical space reasons.
Bug: 179178086
Test: atest NotificationTemplateTests
Test: visual inspection ; expand/collapse
Change-Id: I6bc865d5fca8459ffaa6031d220d8bfa08545d89
