This CL pins the following make targets to java_version 1.8,
which is currently the default:
framework-protos
repackaged.android.test.base
repackaged.android.test.mock
repackaged.android.test.runner
For consistency, their dependencies,
android.test.base
android.test.mock
android.test.runner
which contain .java source files, are also pinned to 1.8.
This is so that the two steps:
a) update jarjar to support v53 class files
b) support -target 1.9 in the rest of the toolchain
can be completed in any order, in future CLs. Before this CL,
they would have needed to be completed in order a), b).
Bug: 72703434
Test: EXPERIMENTAL_USE_OPENJDK9=true USE_R8=true make checkbuild docs
(in a client where CL http://r.android.com/596874 was reverted)
Change-Id: If78067294ae7ab78997aa109b0e08be427bdf0b8
New metrics constant and usb strings for the new
notification / details page.
Bug: 69333961
Test: Check notification
Change-Id: If9bde7f787e40e42bb991a99b032e1ff968a0a41
- Add an alarm tile to QS
- Add the tile to QS the first time the user creates an alarm
- Tapping on the tile navigates to alarm settings
- Added unit tests for alarm tile
- Updated AutoAddTracker to remove deprecated shared preferences values
so the keys can be removed in a later release
Bug: 70799533
Test: manual testing the alarm QS tile behavior
Change-Id: I2b10468c41b4720b66c9e7bb32e22eb958c199f7
This permission was renamed during the O previews but it was supported on the
final O release, so we need to carry it over.
Test: atest CtsAutoFillServiceTestCases
Bug: 70682223
Change-Id: I2b3d798fe9c09751138f154e6e69e6af6b60dbb1
Adds a separate field in SystemMessage class for Carrier Network
Notification, to be able to differentiate between Carrier and Open
network notifications in case we have both notifications at the same
time.
Bug: 69310016
Test: Builds successfully
Change-Id: I5c4f40640a924e39cf4c6a33825afcc1a5c9d4f9
These metric were using the RESERVED_FOR_LOGBUILDER_COUNTER and hence were not
being picked up.
Bug: 71863561
Test: adb shell logcat -b events | grep sysui | egrep '(1231|1232)'
Change-Id: I34136ac3423e819b37fc3c14c1821171af1868d9
Move resources for ZenModePanel to SettingsLib for new
EnableZenModeDialog in settings
Test: runtest -x /extra/master/frameworks/base/packages/SystemUI/tests/src/com/android/systemui/volume/ZenModePanelTest.java
Bug: 63077372
Change-Id: Iea9060b063ccfb807b39affcdac29d12420bd93b
Now that we have accurate information about a user's carrier data
plan, we can alert them if the current usage patterns would end up
with a nasty surprise towards the end of the current billing cycle.
For example, a single abusive app could use 90% of the user's budget
within the first few days of a billing cycle, leaving the user to
limp along for the remainder of the month.
The simple algorithm here extrapolates to see if the average usage
over the last 4 days would be more than 150% of the data limit for
the full billing cycle. This period is short enough to catch rapid
recent usage, but long enough to smooth over short-term habit
changes, such as a weekend getaway. This was chosen after
backtesting the proposed algorithm against real-world data usage
from a handful of internal users.
Fix NPMS unit tests, and write new ones, but leave the existing
@Ignored annotation intact for now.
Test: bit FrameworksServicesTests:com.android.server.NetworkPolicyManagerServiceTest
Bug: 64133169
Change-Id: I0d394b133257e8569a9aa2631b57638839d870ce
This metric was using the RESERVED_FOR_LOGBUILDER_COUNTER and hence was not
being picked up.
Bug: 71863561
Fixes: 72175011
Test: adb shell logcat -b events | grep sysui | grep 1136
Test: cts-tradefed run commandAndExit cts-dev -m CtsAutoFillServiceTestCases
Change-Id: I34f701ff5336a413477fd14172d16d8d1e5403ad
Refactor TakeScreenshot code out of PhoneWindowManager;
add power menu item for Screenshot.
Test: runtest systemui
Change-Id: Ie8602386cd59f8fd991369d2117f7c4d76f65e41
* Added new metrics:
- AUTOFILL_USERDATA_UPDATED
- AUTOFILL_FIELD_CLASSIFICATION_MATCHES
- FIELD_AUTOFILL_MATCH_SCORE
- FIELD_AUTOFILL_NUM_FIELD_CLASSIFICATION_IDS
* Fixed how FIELD_CLASS_NAME is set for AUTOFILL_SERVICE_DISABLED_ACTIVITY
* Added extra info on some existing metrics:
- FIELD_FLAGS on AUTOFILL_SESSION_STARTED
- TYPE_CLOSE on AUTOFILL_REQUEST to indicate a null response from service
- FIELD_AUTOFILL_NUM_FIELD_CLASSIFICATION_IDS on AUTOFILL_REQUEST to indicate the number of ids in a
field classfification request
Bug: 70241978
Test: verified output of 'adb shell logcat -b events | grep sysui' while
running CTS tests associated with the changes
Change-Id: I05d8d0325e9b338dd3d874e5b95a08cedf4b271c
- Dont create a session if the component is not owned by the calling UID.
- Log metrics for forged attempts.
- Avoid possible NPEs on AutofillManager when context or client is null.
Test: cts-tradefed run commandAndExit cts-dev -m CtsAutoFillServiceTestCases -t android.autofillservice.cts.VirtualContainerActivityTest#testAppCannotFakePackageName
Test: cts-tradefed run commandAndExit cts-dev -m CtsAutoFillServiceTestCases
Bug: 69981710
Change-Id: I9695bc046f3eb8aeecfe44f80fd0366f68b2c635
- Default automatic rules are priority only
- Existing user-created rules will be changed to priority only
- New user-created rules will always be priority only
- Metrics for new dialogs and zen preference controllers
Test: manual
Bug: 63077372
Change-Id: I8694d10ebdfa67ba96f4936c74eae17b450e32af
