Update PrivateDnsMode from StringDef to IntDef because IntDef is
the normal way of representing multiple choices in public API.
Also update other related files.
Bug: 185311744
Test: 1. make update-api
2. atest FrameworksNetTests CtsNetTestCases CtsNetTestCasesLatestSdk
3. atest FrameworksServicesTests:DevicePolicyManagerTest
Change-Id: I23e7ec140066979726d769cabc5f7057bb2167e6
Merged-In: I23e7ec140066979726d769cabc5f7057bb2167e6
(Cherry-picked from ag/14227609)
- Removing fuzz in the absence of an alarm clock alarm.
- Adding a minimum duration that the alarm should be fuzzed before an
alarm clock - currently 2 minutes.
- The maximum fuzz is now a linear function of futurity of the alarm
with the maximum capped at 15 minutes.
- If the futurity is less than the minimum fuzz, the alarm goes off
immediately, bringing the device out of idle.
Also, fixing a bug with re-evaluating alarm deliverability in doze and
battery saver.
Test: atest FrameworksMockingServicesTests:com.android.server.alarm
Bug: 170279979
Bug: 166693547
Change-Id: Ia8c656a0336cc0b72f0b3901de96d4aa440186d4
If the screen is off, but the CPU is awake and epoll_wait returns for a
non-wakeup alarm, sending any wakeup alarm within its eligibility window
would cause all the held non-wakeup alarms to also fire, which could:
1. Elongate the length of the time the CPU is awake.
2. Cause apps to wake up and perform work.
This change defers sending any wakeup alarm as long as it is possible to
defer all such eligible alarms to later.
Also, fixed a bug in sorting after adding multiple alarms to the store.
Test: atest CtsAlarmManagerTestCases
atest FrameworksMockingServicesTests:com.android.server.alarm
Bug: 161497385
Change-Id: I01f98255091baddf4e7529f88733776e27d090d7
1. Remove extra space before "EJ" in the timer dump.
2. Actually print out the list of system installers. SparseSetArray
doesn't have toString() implemented.
Bug: 141645789
Bug: 141495777
Test: adb shell dumpsys jobscheduler
Change-Id: Ia6e88b0b1177dc585fcca4a29d658b5a9370b60b
This CL updates VcnManagementService to set the NOT_VCN_MANAGED bit for
Networks that are not VCN-managed. This ensures that Networks correctly
regain the NOT_VCN_MANAGED bit after leaving a VCN.
Bug:
Test: atest FrameworksVcnTests CtsVcnTestCases
Change-Id: I01ffdde246e602296673675add58c47c92b15994
If the user beings using a new privacy item while the chip is showing,
display the new item on the chip
Fixes: 187219110
Test: go to camera, start playing video while the chip is showing. It
should update to show the mic icon
Change-Id: I4e98375c70cb25e110824901e8738eab83564b3c
The NPE here would catch in the outer try-catch causing the end object
token to not be written by ProtoOutputStream
Bug: 187098431
Test: atest IncidentdTest#testIncidentReportDumpLocal
Change-Id: I65fb92c077e246aaf2ae902b545fea38dd667e25
This CL updates VcnManagementService to notify policy listeners
when the subIds for any VCN instances change. This is necessary to
ensure that NetworkFactories properly update their Networks in the
event that a Network comes up under an existing VCN are properly
marked as VCN-managed.
Bug: 187112989
Test: atest FrameworksVcnTests CtsVcnTestCases
Change-Id: Iecab1226119c8fd876131c381647267f18339db2
For incremental hardening, our primary focus is to ensure the system
does not crash. Rather than throw new exceptions when querying from
incrementally installed packages we should return null values and not
subvert API expectations by throwing exceptions in places that
normally cannot fail.
This may cause UI issues when an app loads the resources of a
different, incrementally installed package. We can introduce new APIs
to allow system apps to determine when a package not being fully
present would cause issues on a case-by-case basis.
We will be able to tell from logcat and bugreports where the failed
read occurred in the resources.arsc.
Bug: 169167078
Test: builds
Change-Id: Idfd9ad11b64fc9e8dce9d0fa7ab9b6e4f6083d41
This ensures that adapters have their caches filles and other benefits
such as lists maintaining their scroll positions
Bug: 183503469
Test: validated with local app that service is not called on drag for
colors changing and that flicker is removed
Change-Id: I043d1d7a547b012f7a12eb555b35854a9bb7109b
1. Only downgrade an EJ that doesn't have the IGNORE_BACKOFF extra when
we are actually attempting to back off the job.
2. Allow EJs to have the FLAG_EXEMPT_FROM_APP_STANDBY flag since that
can only be set by the system and won't cause issues.
Also propagate the scheduleEjAsRegularJob bit through the job extras to
help with debugging.
Bug: 178852366
Test: atest ContentResolverTest (all)
Test: atest CtsJobSchedulerTestCases:JobInfoTest
Test: atest CtsSyncManagerTest
Test: atest SyncOperationTest
Test: atest SyncManagerTest
Test: atest SyncRequestTest
Change-Id: I133d089a4d770a3cc37df72f8b38d234b24077df
This CL is part of the effort of removing ActivityView.
Test: m frameworks/base/tests
Bug: 179161778
Change-Id: I613107bbdde17b0d1cd2bb920d35953198a3195d
An NPE could happen, related to falsing, if the very
first gesture to happen is a tap on an ExpandableNotificationRow.
Fixes: 187196123
Test: atest SystemUITests
Change-Id: I8a82fc4d85ba5676a6c198a0b6ddb67009c8ad8e
Mainline modules seem to be metalava'd differently, causing the CREATOR,
describeContents(), and other parcelling methods to become part of the
public API.
Additionally, AppSearchResult and AppSearchBatchResult were forked from
Jetpack with parcelling added, and manually maintained.
Additionally, the parcelling wouldn't work properly if the keys and
values are not themselves parcelable, but this was not clearly
documented or called out.
This CL fixes these problems by creating parcelable wrappers around the
upstream Jetpack AppSearchResult and AppSearchBatchResult, usable only
when they contain parcelable keys and values.
Bug: 146218515
Test: Presubmit
Change-Id: I828a22dc6dae3e46f5d167f1a9d12627ba15d9fd
If alarms with long timeouts are created, there is a risk of a
crash in system_server because of alarm creation limit is reached:
java.lang.IllegalStateException: Maximum limit of concurrent alarms 500
reached for uid: 1000, callingPackage: android
To avoid this cancel alarms if Notifications are canceled.
Suggested-by: Snild Dolkow <snild@sony.com>
Bug: 186456631
Change-Id: I63343b9450fc817ec6a2f46329de346320463c46
