Add a DeviceConfig feature that denotes a list of apps we want to force
into scoped storage. This would allow us to test these apps behaviours
under scoped storage at scale.
Also add the feature to StorageManagerService#dump.
Test: manual:
$ adb shell device_config put storage_native_boot forced_scoped_storage_whitelist <pkg>
$ adb reboot
$ adb shell dumpsys appops --package <pkg> # observe LEGACY_STORAGE
mode=ignored
Test: adb shell dumpsys mount
Bug: 151735608
Change-Id: I6a43e987ebf8d14fb64103a74bafde28f5863ae2
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
Since as of R, apps can no longer query other apps by default,
deprecate the isUserAGoat API's undocumented behavior and
always return false.
Fixes: 156543788
Test: atest CtsMultiUserTestCases
Change-Id: I9743d87b762aabb01dc010ba6d5a6c01643a1f92
Use a scale factor and fixed Stevens' coefficient value for gamma
correction. Scale factors within [0,1) will scale down the effect
intensity/amplitude, and values larger than 1 will scale it up.
The scale up function also makes sure it never scales amplitude
above MAX_AMPLITUDE, or relative intensity value above 1.
New implementation can be visualized here:
https://colab.corp.google.com/drive/1rGCBWXyUe7NePaSLnO-qkeFw8h0DkWJA?usp=sharing
This cl also moves the #resolve and #scale methods to superclass
VibrationEffect (using @hide annotation). This will force every new
effect to also define both behaviors (or explicitly ignore them),
and thus avoid cases where the VibratorService skips scaling new
effects by accident.
Fix: 154712843
Test: atest FrameworksCoreTests:VibrationEffectTest
Change-Id: Ib46e609663aec60a49a8827c90df144caaf7c926
The referenced object could be destroyed and result in native crash when
mCallback is used.
Bug: 156536687
Test: manual test with registering a section from an app
Change-Id: Ie36c0e6e64be1246539f12999f037c24377686dd
Also removes sendPowerHint, setInteractive and setFeature from
PowerManagerService, replacing calls to these methods to existing
setPowerBoost and setPowerMode native methods.
Fix: 150878220
Test: atest FrameworksServicesTests:PowerManagerServiceTest
atest WmTests:SurfaceAnimationRunnerTest
Change-Id: I6c14504650879da6c4d7de4412dc9421fb332f53
When creating admin users, default
UserRestrictions do indeed apply, so updating
the javadoc.
Test: N/A
Bug: 143491938
Change-Id: Id495599abd4ddee100ca2c761d3b420fff315482
Fix a potential race condtion when the same message object
is being enqueued by two threads.
Bug: 150263007
Bug: 154867444
Test: atest android.os.cts.MessageQueueTest
Change-Id: Id79448ba8719479cbdb054f2cdd172fdcbe86d47
(cherry picked from commit 96a6fec4d6)
Background
* Secondary users should be disabled
when the device is an organization-owned
managed profile device.
* This is because supporting secondary
users would complicate the semantics of
user restrictions.
Changes
* Add DISALLOW_ADD_USER as a base restriction
when the device is an organization-owned
managed profile device.
* Handle removal case when the device is no
longer in this mode.
* Remove the ability of other admins to apply
DISALLOW_ADD_USER.
Manual Testing Steps
* Provision an organization-owned managed
profile device.
* Check Settings > System > Multiple users
and verify that a user cannot be added.
* Check WP TestDPC 'Set user restrictions
on parent' and verify 'Disallow add user'
is not present.
Bug: 155281701
Test: Manual testing
atest com.android.server.devicepolicy.DevicePolicyManagerTest
Change-Id: I83348fc8b854cef20383803124000540b5b130cb
