Allows the multiple audio focus that requested with AUDIOFOCUS_GAIN.
Test: atest SettingsProviderTest
Test: Manual - play music on A app
Test: play music on B app // play music on A app and B app
Test: receive a call // stop music
Test: end a call // play music on A app and B app
Test: receive a notification // ducking all music
Bug: b/135749683
Change-Id: I4bdd2cdc5e543674f331fc000bd24fd30499bdc3
There are chances that innocent namespaces got banned with actually
harmful namespace, and since innocent namespaces' flags may not be
changed for a long time, they are getting banned on the devices for a
long time even though they are not problematic.
Thus we want to do: When a namespace's configuration got successfully updated, unban ALL the
banned namespaces(by clearing the hashcode map) if the updated namespace was banned before updated.
Bug: 153010388
Test: atest DeviceConfigTest & local device with Mob Dog
Change-Id: I61b92a09d77ef1e1b7bc9c86f6655ba62a8a3d89
So we can show it in developer options. Also fix a bug
where the setting wasn't being respected in systemui.
Test: atest
Bug: 152907434
Change-Id: I1eaed93a0c8a1ec4486c7072972e2f924402bb94
-Add a new app ops helper to make testing easier.
-Consolidate app identity within CallerIdentity class.
-Remove location age restriction for coarse locations, was a bit
arbitrary.
-Remove listener identifiers from LM. These were not being properly
propagated and add a lot of binder overhead with what appears to be
little benefit since we have featureIds, which contain much better
information.
-Remove appops checks from some GNSS APIs that shouldn't require it.
-Move location fudger into location providers and reset them after mock
providers are used so that offset information cannot be leaked.
Bug: 149375028
Test: presubmits + manual
(cherry picked from commit 6033344baa)
Change-Id: I18e2cf3c39836f31d28180e1a4613df4ad675ab7
A new value in global settings for the adb to determine if the
device allows using incremental installations by default.
Bug: 150183149
Test: builds
Change-Id: I64e8fafcacbb790fa469629136a7dacbfd34e800
Roll back the changes of ACCESSIBILITY_BUTTON_TARGET_COMPONENT to
support previous behavior of the a11y button. Also, create another
setting key to hold shortcut targets of the a11y button which is
assigned by the user from the settings app.
Bug: 152263232
Test: atest SettingsProviderTest
Change-Id: I7a70e8c8495cefe6632efddbb322a323aa1168c7
Merged-in: I7a70e8c8495cefe6632efddbb322a323aa1168c7
- Target to fix migration issue to support a user revoked the accessibility shortcut before upgrading to R, but wants to to apply new hardware shortcut design in R.
- The switchbar of accessibility_shortcut_enabled was removed in (1/n), so we should also remove related checker in controller.
Bug: 142529032
Test: atest AccessibilityShortcutControllerTest
Change-Id: I48f8d88c4192e894b9e210221e5dc7e701344623
Bug: 151888061
Test: Manual verification (ensured that this method returns null after
first reboot)
Change-Id: Ie8ad397c7b68e35cfa7b696ef22d84f376cf3fe7
* changes:
[SM08] Add NetworkTemplate unit test for fetching mobile data usage
[SM07] Make combine subtype configurable from Settings
[SM05] Enable record mobile network stats by collapsed rat type
[SM04] Support fetching data with NetworkTemplate with subType
[SM02] Support record mobile network stats by collapsed rat type
Note that enabling/disabling would not take effect until device
reboot. This will be addressed in follow-up patch.
Test: 1. atest NetworkStatsServieTest SettingsBackupTest
2. adb shell settings put global netstats_combine_subtype_enabled 1|0
Bug: 146415925
Change-Id: Ic94da540afa479ed18f1b6fbda4ae3216c37476b
Merged-In: Ic94da540afa479ed18f1b6fbda4ae3216c37476b
(cherry picked from commit c4f77ac90b)
Bug: 144838882
Test: atest SettingsProviderTest:SettingsStateTest
System reinitialises some settings to the same value after reboot (e.g.
bluetooth_on, accessibility_enabled, font_scale). Such modifications
shouldn't set isPreserved flag.
Change-Id: Ib929bf7d544b78202691eff3ae2ac75f2c209aa2
When restoring settings from a different phone,
UiModeManager did not update the new settings.
Now, the settings are loaded from local storage and changes applied
when the SettingsHelper restores a value of interest
Bug: 138671559
Test: manual test: reset phone1, setup, used data transfer tool to restore from phone2, check dark mode is the same as phone 2
Change-Id: I861bec342b3284e0f398c8610fcc6881c27601a5
Per API review feedback, global settings are discouraged in favour
of fine-grained getter APIs.
Bug: 149999040
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testCommonCriteriaMode
Test: atest com.android.cts.devicepolicy.OrgOwnedProfileOwnerTest#testCommonCriteriaMode
Test: atest FrameworksServicesTests:DevicePolicyManagerTest
Change-Id: Ia810f67409ce2b482bca06f1e21df2f98d12ccfd
Bug: 150842661
Test: 1. atest SettingsStateTest
2. atest PreservedSettingsRestoreHostSideTest
Reset operation brings a setting to its default state. This should
include isValuePreservedInRestore which is false for a newly initialized
setting.
Change-Id: Ife317e2ac9dbaae9d3f2abe770407558e7bdd775
