DevicePolicyResourcesManager.getString() was added in T and called in
many places inside system server. However, it uses
DeviceConfig.getBoolean to determine if a feature is enabled or not. In
the places where it is called from inside system server,
`clearCallingIdentity` was not always called, which can result in
DeviceConfig.getBoolean throwing SecurityException due to mismatched
AttributionSource (calling uid is the caller from the binder client,
while the context is "android" which should have calling uid 0). Context
is "android" because it is inside the system server where the
DevicePolicyManager instance is created. This bug might lead to
unexpected behavior such as packages failing to be uninstalled by admin.
The easiest fix is to place a bypass in SettingsProvider and manually clear
the calling uid there. This fix also allows for the cleanest backporting as
it can be cherry-picked into T without touching all the places where
DevicePolicyResourcesManager.getString() is called in the system server.
BUG: 252663068
Test: manual
Merged-In: I37a6ceb29575593018b93093562c85d49770a43c
Change-Id: I37a6ceb29575593018b93093562c85d49770a43c
(cherry picked from commit b127850fda)
beyond S people can not access the DATA_ROAMING API from Settingss.Ideal
way to use this is from TelephonyManager.
Test: manual.
Bug: 172467621
Change-Id: I5bbdd886599ff0ecf66eb72beb78456adc4d632c
And the related obsolete code.
Test: SystemUITests, framework services tests, NotificationManagerTest
Fixes: 231344755
Change-Id: Id14941f82305b0216f2a12221d4195f8afcc65ab
This reverts commit 321b621ee0.
Reason for revert: Experiment is completed and we do not want to leave the code in place as we would not want to accidentally run it on the public.
Change-Id: I24769b669a38ffafeb10e927e2785caa369faa90
This setting is going to be global across the device rather than per-user.
Bug: 225373531
Test: manual
Change-Id: Ibabad2192e50d8f495f9e9fcbc12ba93156bc3fa
The Settings.Secure string is used for the "review notification permissions" notification that will be shown to users upon upgrade to T, and will track state for whether the user has seen and interacted with the notification yet.
The action is an internal intent to go to the app notification settings page. This intent and activity need to be non-exported to disallow other apps from causing writes to settings.
Bug: 225373531
Test: manual with change to show the notification
Change-Id: I3ad1a3043eb428fab93e15d8f5ae1ada884b010f
Makes sure that third-party apps that target beyond S cannot access the
setting value directly from Settings.
BUG: 177239688
Test: manual with debug app
Change-Id: I2c5faad7f3e334704addc980530aae84c8c13864
This is the minimum time user has to perform the gesture
for it to be considered valid.
Bug: 228395041
Test: atest
Change-Id: I7ce603e5530e13bf3552611c621a8e8b3cf5ab4c
This reverts commit 3048dbaac5.
Reason for revert: abandoning this feature, no longer adding a separate timeout
Change-Id: Ic35b7b94b1e4a49c1fc56f29627577d2d9a40174
Before Android 13, PhoneAccountHandle#getId() returns the ICCID
for Telephony PhoneAccountHandle. Starting from Android 13,
PhoneAccountHandle#getId() returns the on-device Subscription ID
for Telephony PhoneAccountHandle. This need to migrate the
PhoneAccountHandle ID stored in CalllogProvider and ContactsProvider.
Adding these fields to help migrate the ID when it is stored in
the device, and back-up/restored through the cloud.
Bug: 185235527
Test: atest ContactsProvider2Test;
atest CallLogProviderTest
Change-Id: I417f211413cf92a2757899360d6905d0d50064ec
When the experiment flag is flipped to on, toggle the "show system
accesses" setting to on one time and then do not modify the value again
unless the experiment is turned off and then on again.
Bug: 191503437
Test: atest LocationControllerImplTest
Change-Id: I25e647bc3ccfb911719b2047a5096f9a9e62a3ad
This is a cherry-pick of deleteProperty SystemApi that is already added
in internal branches.
Currently there is only a shell command to delete a property.
Adding an API to do the same.
Bug: 184001163
Bug: 226423598
Test: atest android.provider.DeviceConfigTest
Change-Id: I43d7177c509501efd65e32ab3ad000d17d6ffb6c
Merged-In: I43d7177c509501efd65e32ab3ad000d17d6ffb6c
beyond S people can not access the DATA_ROAMING API from Settingss.Ideal
way to use this is from TelephonyManager.
Test: Added CTS Test.
Bug: 172467621
Change-Id: I05cb675231b69f40896007601627e8078e0ecb02
