- remove unnecessary lock - after statsd added locks for each puller, there
is no need to create additional lock for sampling rate estimation
- adjust sampling target value for AppOps atom based on Beta1 results
- adjust sampling ratio for Dangerous Permission state atom
Test: statds_testdrive 10069, 10075, atest UidAtomTests#testAppOps
--iterations=20, atest UidAtomTests#testDangerousPermissionState
--iterations=20, atest UidAtomTests#testDangerousPermissionStateSampled
--iterations=20
Bug: 143519689
Change-Id: I05fec5f602c7e1c5ba38749147c04aec79da2a46
- The global listener checks mStartingQuickSwitchRotation
before setting the override sampling region, but immediately
after navigation mode switch, this is not set to -1 so we can
end up setting this to the wrong region.
Bug: 158663687
Test: atest android.systemui.cts.LightBarTests#testLightNavigationBar
Change-Id: I332982b5401fa5d4d4af8cd4e4d71ab8beb6cd4d
This fixes use of the autofill SaveUi for secondary users. Without this
change, when running under a secondary user, the PendingIntent is always
sent to U0.
Bug: 159618798
Bug: 155102708
Test: lunch hawk-userdebug && m
run cts --skip-device-info -s emulator-5554 -m CtsAutoFillServiceTestCases -t android.autofillservice.cts.SimpleSaveActivityTest#testTapUrlSpanOnSuccinctDescription_thenTapBack
Change-Id: Ie6deaaaf47a11ae841c183003471d051df2beb90
- In automotive, vold reset / resetIfBootedAndConnected() call can
lose pending unlock request for a user if boot completion and
unlock happens at the same time. In automotive, user unlock
can happen before boot complete.
- After vold reset, check for such lost user (=marked unlocking or
unlocked in UserManager level but is still locked in StorageManager
level) and retry unlocking.
- This also undo previous CL to keep handler messages as that cannot
prevent all the race, especially race of vold reset right after
onUnlockUser call. But handler update is kept inside the service.
- The restoration is done only for automotive device for now as phone
does not have such case.
Bug: 151457974
Test: try reboot in auto devices where this race can happen.
Change-Id: I3b50750f5602c805e79f79f061eed44f880b25bd
Activity was still referred from ImeInsetsSourceConsumer after
ViewRootImpl's mView was destroyed when ViewRoot's surface is cleared
using die signal.
This CL makes sure we still free-up resources at die signal.
Fix: 157955883
Test: atest NexusLauncherTests
Change-Id: Ia48f7b7a8cf6b867ce75b2b7393a60ba73b0c3d0
Add explicit mapping to reduce churn in the logs as notification section list changes.
Fixes: 159568541
Test: statsd_testdrive
Test: atest NotificationLoggerTest
Change-Id: I7f0fe1a4dbed4a4b965154230b937659026b7493
PendingIntent lets SaveImageInBackgroundTask pass the permission
directly to the target. Flow is:
SaveImageInBackgroundTask (current user) ->
ActionProxyReceiver (system user) ->
Share or edit target (current user)
The pending intent created in the first step allows read/write
permission to be passed to the final destination, as ActionProxyReceiver
itself does not have access to the screenshot.
Bug: 159455848
Test: Share and edit a screenshot with the following variations:
- lockscreen on / off
- primary user / secondary user
Verify that full UI flow apperars, final destination can show the
screenshot
Change-Id: Ie92212f2ffc3f8a11c3e5380908460f5f7fbb439
Since rebooting system server requires root, we had to create a new
internal test suite with root access.
Bug: 158283778
Test: StagedInstallInternalTest#
testSystemServerRestartDoesNotEffectStagedSessions
Change-Id: Id37111c0e63025aabe58cc9c8ab39b0362f1aed4
There was some confusion around people seeing all devices with a
status of 'device removed' on timeout. Show the msg instead and not
the favorited controls
Fixes: 159596183
Test: manually set load timeout to 1s
Change-Id: I7cb0f74c2080f3537f8df84ea5eb0fd779285dcf
Start all pending actions after TV allocates logical address. This
ensures DeviceDiscoveryAction is able to run. HdmiControlService
starting its power state in STANDBY prevents all Actions from being run.
Playback and Audio devices perform the same logic upon logical address
allocation.
Bug: 159104739
Test: atest HdmiCecLocalDeviceTvTest
Change-Id: I9a79ee02f5065abbedded26be385115279797977
Merged-In: I9a79ee02f5065abbedded26be385115279797977
Check one more parameter enforceDnsUid in ResolverOptionsParcel in
DnsManagerTest.
Bug: 159587277
Test: atest
com.android.server.connectivity.DnsManagerTest#testSendDnsConfiguration
Change-Id: Ic53f42b968626294c851dac252a70769846ba427
Apply custom icons, if any, during add controls. Edit controls the
issue still exists but will handle separately.
Fixes: 159562131
Test: manual, mock app use TYPE_FAN
Change-Id: Ib75756a8b6fa6e78a678fc8d6ceb3e4cdaafc142
ImageView has state that cannot be reversed regarding tintList, even
if you set it to null. Therefore only clear the tint if we absolutely
need to in order to avoid an override.
Bug: 159559045
Test: manual
Change-Id: Id2223136a76f7e7e3118d95f1ad126f768199d3f
Fixes: 149073538
Test: manually provisioned a work profile on org owned device appears
Test: removed a work profile on org owned device to see disclosure disappears
Test: manually set up device as DO to see disclosure appears
Test: manually created a regular non-organization owned work profile to
see disclosure does not exist
Test: atest KeyguardIndicationControllerTest
Change-Id: I1df774cb4389b64779e7e329c3a1c7ff0b68c3ee
Probe DNS servers to see they support DNS-over-TLS. Use system
CAs to verify whether the certificates sent by DNS servers are
trusted or not. An error is thrown to cause the probe failed if
DNS servers send untrusted certificates.
Unlike the DnsResolver which doesn't verify the certificates
in opportunistic mode, all of the DoT probes from NetworkDiagnostics
check certificates.
DoT probes apply to the DNS servers gotten from LinkProperties
and the DoT servers gotten from PrivateDnsConfig whatever private
DNS mode is.
A common example in DNS strict mode:
. DNS TLS dst{8.8.8.8} hostname{dns.google} src{192.168.43.2:48436} qtype{1} qname{815149-android-ds.metric.gstatic.com}: SUCCEEDED: 1/1 NOERROR (432ms)
F DNS TLS dst{192.168.43.144} hostname{}: FAILED: java.net.ConnectException: failed to connect to /192.168.43.144 (port 853) from /192.168.43.2 (port 41770) after 2500ms: isConnected failed: ECONNREFUSED (Connection refused) (172ms)
. DNS TLS dst{8.8.4.4} hostname{dns.google} src{192.168.43.2:37598} qtype{1} qname{759312-android-ds.metric.gstatic.com}: SUCCEEDED: 1/1 NOERROR (427ms)
An example when the CA is not trusted:
F DNS TLS dst{8.8.8.8} hostname{dns.google}: FAILED: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. (16ms)
An example when TCP/TLS handshake timeout:
F DNS TLS dst{8.8.8.8} hostname{dns.google}: FAILED: java.net.SocketTimeoutException: failed to connect to /8.8.8.8 (port 853) from /192.168.2.108 (port 45680) after 2500ms (2514ms)
Bug: 132925257
Bug: 118369977
Test: atest FrameworksNetTests
Original-Change: https://android-review.googlesource.com/1011670
Merged-In: I1b54abed0e931ca4b8a97149459cde54da1c3d6f
Change-Id: I1b54abed0e931ca4b8a97149459cde54da1c3d6f
