Adds a new setting key to support long press accessibility
button.
Bug: 150587818
Test: atest SettingsProviderTest
Change-Id: I1ca1e01867a937690f7a5e5b27d595cd0a83e395
Adds a new capability discovery opt-in intent,
which an application can use to prompt the user
to enable contact discovery.
Bug: 111305845
Test: atest CtsTelephonyTestCases; telecom test app
Change-Id: I42b9d7226a1296bc7e4e86a5ff6448bc8f23d3c0
When switching dark mode, the dark mode override should only apply when
the dark theme is in auto or custom mode. The solution is
to set the override to the same value as night mode
Test: UiModeManagerTest
Fixes: 150567159
Change-Id: Ib10b73e747a53669de0babc9b44d373b47bfc0fb
+ Allow this limit to be modified using DeviceConfig properties.
+ Support DeviceConfig.getProperties() in TestableDeviceConfig.
Bug: 144155182
Test: atest --test-mapping apex/blobstore
Test: atest services/tests/mockingservicestests/src/com/android/server/testables/TestableDeviceConfigTest.java
Test: atest services/tests/mockingservicestests/src/com/android/server/am/CachedAppOptimizerTest.java
Change-Id: I28e67a27771be04ed1d37f367abd392505adc5c4
-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.
Test: presubmits + manual
Change-Id: I0ab6318093b1a7c7210ce9e39ccccf75d4f2eb66
ADB_ENABLED historically meant the state for USB debugging. Since
wireless debugging can be enabled separately, define another setting
for it.
BUG: b/111434128
Test: make
Exempt-From-Owner-Approval: approved in aosp_master
Change-Id: If3abca8e77381d6832f55d55a43c52ee1a1267d1
Cross profile connected apps can provide the functionality of multiple
app from just one of the apps. If the user uses only one of the apps to
interact with all of the connected apps, the connected apps will fall
into low standby buckets. Cross profile connecting apps and using the
conncted apps is the clear signal of usage for both apps, so this
change treats all usage of one app to be equal to the other.
Fixes: 140808123
Test: atest com.android.server.usage.AppStandbyControllerTests
Change-Id: I9e3bd71c7b486417b3943778edece4ab29d4c41d
* changes:
WifiOemMigrationHook: Migrate Settings global values
WifiManager: Add API for scan always available toggle
SoftApConfiguration: Add shutdown enabled method
Add "AUTO_REVOKE_DISABLED" systemApi constant to Settings, which
will be used to read the global state of the auto revoke system.
Test: None
Bug: 146513245
Change-Id: I8072d124adf2808493f2eb4de5e52d87bef57508
and from MONITOR_DEVICE_CONFIG_ACCESS permission declaration.
Test: no need, just removing annotation.
Bug: 149487442
Change-Id: I73bbe9672eb5c8c0fd043c07a5e27463f0f14e5c
Changes:
a) Add a method to migrate Settings values from platform.
b) Marked all of those settings back to @hide.
c) Also, deprecated couple of public Settings keys which are no longer
used in the wifi stack.
Bug: 148514485
Test: Compiles
Test: TBD: Add unit tests for this class.
Change-Id: I3566cdb53fc997fbb2cc5bceadd865ff8b01539b
Add Enhanced Connectivity Developer option switch. This switch will
allow the connectivity thermal power manager to actively shutoff 5G in
order to save power when cellular throughput is below the set threshold.
ScreenShots: https://drive.google.com/drive/folders/109VTTXqIn5Teg6daHpNHV7z13MmEEb7Q?usp=sharing
Bug: 147305171
Test: On-device using developer option menu
Change-Id: Ia990db0fe8a8cea47b12b570c46c10a5ab558a27
There were a couple problems with work profile state in location. First,
we assumed that notifications sent to parent users would also be sent to
profiles but this is not true. Second we had assumed location status in
profiles was always identical to the parent user, but work profiles may
have user restrictions applied which are not present on the parent user.
The easiest way to handle these issues seems to be to expand LMS user
handling to deal with all users, rather than making various assumptions
which may or may not be true.
This also means we need to store last locations on a per profile basis.
Since we're refactoring how last location works completely, we also
removed the special NO_GPS handling for last locations. With the new
permission strings we now no longer have to exclude gnss based location
from coarsening. This lets us:
1) deprecate and remove various constants and methods use for storing
coarse locations tied to fine locations
2) substantially simplify code that calculated coarse location
This also exposed numerous bugs in the location service where we were
using the current user's state instead of the calling user's state,
which could have exposed the current user's location to other users
inappropriately.
Bug: 148798374
Bug: 146071833
Test: presubmits + manual
Change-Id: I2d3216a9fb58b73d0124d563b05de8870b70b716
