The restriction is to limit the APIs a financed device owner can
call.
Bug: 215754643
Test: atest com.android.server.devicepolicy.DevicePolicyManagerTest
Change-Id: Ic38b50d7388b277ad74d2c22182bc1e711a1aea4
When "dumpsys activity" is called with special arguments (like
--list-dumpables), dump() should be handled by Activity itself,
not the subclasses, otherwise the end result would be spammed.
This CL fixes that behavior, but only for apps targeting T (so it
maintains backward compatibility for apps that are explicitly
checking for the special values).
Bug: 149254050
Test: m update-api
Test: manual verification with 'adb dumpsys activity ...'
Test: atest CtsAppTestCases:android.app.cts.ActivityDumpTest
Test: adb shell dumpsys platform_compat|grep DUMP_IGNORES_SPECIAL_ARGS||echo NOT_FOUND
Change-Id: I918c9a6649cb66f9e2b6509a643005fac110d152
- SmartspaceDefaultUiTemplateData represents the data of a Smartspace
card with the default UI template;
- Other templates' data classes are all subclasses of
SmartspaceDefaultUiTemplateData;
- SmartspaceIcon and SmartspaceTapAction are the newly-added primitives.
More details in go/ss-launcher-templated-ui.
Test: tested locally
Bug:213926964,212650337
CTS-Coverage-Bug:214471292
Change-Id: I056c49e3db7060697be4a3a8f51358802f2610b0
* changes:
Expose the bg restriction exemption list as an internal API.
Add an action button to the notification for bg battery abusive apps
Exempt certain app behaviors for their background battery usage
Add tracking on abusive broadcast and service binding requests
Add exemption cases for app background restrictions
Monitor long-running foreground services
Post notification on abusive background current drain
Allow limited alarms/jobs when background restricted
Cap the LRU position of broadcast receivers in bg restricted apps
Add a tracker on background current drains for each uid
Add background restriction levels definition and its controller
CTS-Coverage-Bug: 210528288
Bug: 210528288
Test: RBE Built redfin-eng and tested on a physical device
Change-Id: I640be77dbf05633b7a17ada73ea261dbd0027697
Augment the "apparent" display information in configuration
from just the display bounds (maxBounds) to also include the
display rotation and cutout. Like maxBounds, these will be
expected to always be set as basically "the display that this
configuration was built against".
This heavily simplifies fixed-rotation since now we don't
need to deal with the "are we overriding?" question and also
don't need extra activity servertransactions. The configuration
is also in sync (since it is the source of truth used by
resources). Additionally, this means that even the current
legacy fixed-rotation model should work with in any
mixed-rotation situtaion, not just fullscreen.
Bug: 202201326
Test: atest DisplayTest
Change-Id: I6232f74c74324b70b1b0c9f46448c509c2694310
This is so that CTS tests can be run against a test GameService
rather than against whatever GameService a particular device
has set as its default.
Ignore-AOSP-First: GameService incomplete in AOSP
Test: atest CtsGameServiceTestCases GameServiceProviderSelectorImplTest
Bug: 202417555
Bug: 206128693
Change-Id: I5d0d1a4047949117850818c14b5df617314efcf5
Not just moving its services out of the FGS mode.
The shell command for invoking this operation has changed; it is now
adb shell cmd activity stop-app [--user NUM] PACKAGE
Bug: 192504071
Test: manual (Maps nav, YouTube, etc)
Test: atest CtsAppTestCases:android.app.cts.ServiceTest
Test: atest RunningFgsControllerTest
Change-Id: Ic14c1ba557460e25dd1ba2fd79462918e9a47377
Prior to this change, internal components like Settings or
CarUserManager would need to call 3 APIs to logout a managed user:
1. previousUserId = getLogoutUser();
2. switchUser(previousUserId);
3. clearLogoutUser();
This CL encapsulates the whole process into a new DPM.logoutUser(),
but it keeps the getLogoutUser() (as Car need to know which user it
will be switched to in advance, due to the Vehicle HAL integration).
Test: m update-api
Test: atest FrameworksServicesTests:DevicePolicyManagerTest
Test: atest com.android.cts.devicepolicy.DeviceOwnerTest#testCreateAndManageUser_LogoutUser_system
Fixes: 214336184
Change-Id: Ifffc229ecede5d086338e9c7fa08dce0e0de884c
To share the same exemption policy with task manager.
Bug: 200326767
Bug: 203105544
Test: atest FrameworksMockingServicesTests:BackgroundRestrictionTest
Change-Id: I01c70b501e37f13c516d439533e95061ed4a9ebe
In case of excessive amount of outgoing broadcast/service binding
requests from a background app, move the app to restricted bucket.
The exemptions in previous CL still applys here.
Bug: 200326767
Test: atest FrameworksMockingServicesTests:BackgroundRestrictionTest
Change-Id: I2ec82f26bf2a72e2201b140979be09794adedf47
If a certain package has foreground services running for a long time,
say the accumulated durations over last X hours are more than Y hours,
system will post a notification to remind the user.
Some type of apps are subjected to be exempted, i.e. if it's already
in the device idle allowlist. More exemption could be added in
the follow-up CLs.
Bug: 200326767
Bug: 203105544
Test: atest FrameworksMockingServicesTests:BackgroundRestrictionTest
Change-Id: I3a8f34c33e7a533240abc7cf4fa569a0956eec73
