This api is to log BinaryPushStateChanged.
Experiment id is added as a binary blob that is not expected to be
accessed on device side.
This cl is mainly for API.
Will add follow up cls for persisting train info on disk and make puller
for it.
Will address sepolicy in follow up cls.
Bug: 119633962
Bug: 119685453
Test: will add gts
Change-Id: I68b4246cf7e8079155e16121ca37a312b35a5328
Also add a prototype for a future system-api accessible metrics file
that will be auto-generated from atoms.proto
Test: - ./out/host/linux-x86/bin/statsd_testdrive -p com.google.android.permissoncontroller 170
- triggered permission request
Bug: 123594188, 123663448
Change-Id: Icede6ff1f12ca79ebad6267c045a4fb3a9955402
In ag/5859897 we started tracking source styles for each TypedValue.
It is also useful to keep track of source layouts if the attribute
was resolved against a layout (attribute set in XML layout inside
of <View> tag).
Test: atest CtsContentTestCases:android.content.res.cts.TypedArrayTest
Bug: 111439551
Change-Id: Ie6bc6ecd9a22b536a2f3288263b896f9cec67d38
The current implementation of the ProtoOutputStream compresses the
buffer in order to return its correct size.
For some use cases the compression is too expensive and it is more
useful to have a faster but overestimated size to a precise but slower
one.
This implementation adds a `getRawSize` method which returns the buffer
size without compressing it. If the buffer has already been compressed
the returned size is the same as the one from the `getSize`. If the
buffer is not yet compressed the size may diverge.
This implementation will be used to support a ring buffer for window
transitions on the Window Manager.
Bug: 123535780
Test: Check the getSize method from the EncodedBuffer and the getRawSize
from the ProtoOutputStream.
Change-Id: Ied24742a14b76980afdf6d6d22d67ade15ba7aad
Test: Automated tests should pass. Menu should render at correct size, shape, and position for 0-9 action items.
Bug: 121385065
Change-Id: I3448e7e333ea8fdaeb09a241249ce7521920169e
Adding a quota mechanism for deferring alarms based on their standby
buckets.
Number of times an app can receive alarms in an hour is now capped by a
maximum depending on their standby bucket, with the frequency getting
more restricted as the buckets move higher.
Restricting presubmit test to only run when AlarmManagerService changed,
as some tests can take a while to complete.
Test: atest android.util.LongArrayQueueTest
atest CtsAlarmManagerTestCases:AppStandbyTests
atest FrameworksMockingServicesTests:AlarmManagerServiceTest
Bug: 122974477
Change-Id: Icbd5bbb8aeef91b543d09acee553fd0aa3a23f30
- Originally, we had two parameters "total active jobs=6" and "max FG jobs=4",
but because of how we counted jobs against those, sometimes we ran at most 6
jobs and sometimes 10, depending on how pending jobs are queued. Now we made it
consistent.
- The new parameters that control it are:
1. Max total jobs
2. Max BG jobs
3. Min BG jobs
* This is used to ensure a certain number of BG jobs should run
even when the TOP app keeps scheduling new jobs and consume
the max total jobs.
(4. Screen off rampup delay.)
We have these 3 values for each "memory trim level" and "screen on/off".
The intention is that when the screen is off, we should run more jobs. However,
when the screen is off, we don't increase the concurrency right away, but
we'll do so after the rampup delay.
- The current max values are based on the lenient side of the previous values,
but with a slightly lowered the max job count when the screen is on.
Under NOTMAL memory trim level, when the screen is ON:
* 8 total jobs, 6 max BG jbos.
Under NOTMAL memory trim level, when the screen is OFF:
* 10 total jobs, 6 max BG jbos.
Bug: 111360323
Test: Manual test using "adb shell requestsync"
Test: atest JobCountTrackerTest MaxJobCountsTest
Test: atest CtsJobSchedulerTestCases (following failed; all known issues)
android.jobscheduler.cts.BatteryConstraintTest#testBatteryNotLowConstraintFails_withoutPower
android.jobscheduler.cts.BatteryConstraintTest#testChargingConstraintExecutes
android.jobscheduler.cts.ConnectivityConstraintTest#testConnectivityConstraintExecutes_metered
android.jobscheduler.cts.ConnectivityConstraintTest#testConnectivityConstraintExecutes_withMobile
android.jobscheduler.cts.ConnectivityConstraintTest#testUnmeteredConstraintFails_withMobile
android.jobscheduler.cts.JobThrottlingTest#testBackgroundConnectivityJobsThrottled
Change-Id: I0a9de5832b946cb1cac8a69aedbb0cb59251ea47
This API will be used by Android Studio layout inspector to
query where a given resource attribute originated from to allow
developers to have an easier way to find what needs to be changed
to affect a given resource attribute.
Test: CTS added in the topic
Bug: 111439551
Change-Id: Ifbb52b39912ed0444030a86164290a1cd4155250
This includes laying down some groundwork to make the remaining migrations
more straightforward
Bug: 110557011
Test: atest RoleManagerTest && atest SmsManagerTest
Change-Id: Ie96abd73751d10f521756c9dcdab2a5710ca2045
1. Enables image wallpaper in AOD.
2. Enables a mask with 70% black scrim and vignette effects.
3. Add feature flag in developer options which is default disabled.
Bug: 111861907
Bug: 118470430
Test: Manually test the flow
Test: runtest systemui
Test: atest ImageWallpaperTransformerTest
Test: atest AodMaskViewTest
Change-Id: Iff2642d52264e88012f4759842a59aaf5bc45b38
Current description for android.util.Range says ""All ranges are bounded, and the left side of the
range is always {@code >=} * the right side of the range." It should have been "<=" there instead
of ">=". So, corrected that in this CL.
Bug: 122271254
Test: make offline-sdk-docs
Modified description was visible correctly.
Change-Id: I1eaa94210b39813b3e72ac2a0834bc0b466a99a5
Members modified herein are suspected to be false positives: i.e. things
that were added to the greylist in P, but subsequent data analysis
suggests that they are not, in fact, used after all.
Add a maxTargetSdk=P to these APIs. This is lower-risk that simply
removing these things from the greylist, as none of out data sources are
perfect nor complete.
For APIs that are not supported yet by annotations, move them to
hiddenapi-greylist-max-p.txt instead which has the same effect.
Exempted-From-Owner-Approval: Automatic changes to the codebase
affecting only @UnsupportedAppUsage annotations, themselves added
without requiring owners approval earlier.
Bug: 115609023
Test: m
Change-Id: Ia937d8c41512e7f1b6e7f67b9104c1878b5cc3a0
Merged-In: I020a9c09672ebcae64c5357abc4993e07e744687
Members modified herein are suspected to be false positives: i.e. things
that were added to the greylist in P, but subsequent data analysis
suggests that they are not, in fact, used after all.
Add a maxTargetSdk=P to these APIs. This is lower-risk that simply
removing these things from the greylist, as none of out data sources are
perfect nor complete.
For APIs that are not supported yet by annotations, move them to
hiddenapi-greylist-max-p.txt instead which has the same effect.
Exempted-From-Owner-Approval: Automatic changes to the codebase
affecting only @UnsupportedAppUsage annotations, themselves added
without requiring owners approval earlier.
Bug: 115609023
Test: m
Change-Id: I020a9c09672ebcae64c5357abc4993e07e744687
Implement controlWindowInsetsAnimation
Based on the leashes we have on the client, and the insets the
client has requested, we are able to move the surfaces around
such that the resulting insets will match what the client
requested.
Bug: 118118435
Change-Id: I0616e53455a6544aaf374c1b0eb10e258aced21d
We'll use different max numbers for screen on and screen off,
and the semantics will be different from that of P (since the previous
code was broken), so I'm just adding a new set of configs.
Also add wrapper classes for config values.
Bug: 111360323
Test: dumpsys jobscheduler contains the following sections.
max_job_total_on_normal=4
max_job_bg_on_normal=2
max_job_total_on_moderate=4
max_job_bg_on_moderate=1
max_job_total_on_low=4
max_job_bg_on_low=1
max_job_total_on_critical=2
max_job_bg_on_critical=1
max_job_total_off_normal=8
max_job_bg_off_normal=4
max_job_total_off_moderate=6
max_job_bg_off_moderate=4
max_job_total_off_low=4
max_job_bg_off_low=1
max_job_total_off_critical=2
max_job_bg_off_critical=1
Change-Id: I46004a1633494c0498681f4ee1d0045d3c3ab4d7
Some time zone related libcore classes are moving from
libcore.util to libcore.timezone.
Bug: 119026403
Test: build only
Change-Id: Ic807977a85276b888362295d1d305effe33076fc
