Constructor of JobStatus may update the network request in the
JobInfo parameter. NetworkRequest is moving into the incoming
connectivity module. The hidden methods and members usage will
not allowed anymore, so it requires to rebuild the network
request for any update in the network request. Expose a new
Builder constructor as a helper method to construct from an
existing JobInfo instance which will helpful for such cases
that need to clone the JobInfo and update only specific items.
Also, JobStatus which is inside the platform could not refer
to the hidden members or methods of classes in the connectivity
mainline module. Callers who want to construct a network
request should use the formal NetworkRequest.Builder. Update
the usage accordingly to resolve the hidden usage.
Bug: 172183305
Test: atest JobInfoTest
Test: atest com.android.server.job.controllers.JobStatusTest
Change-Id: Ifb74d44e29e13f0e3b995be638c5bfe435a09106
Minor cleanup that allows us to restrict access/usage of the scheduler
itself for cleaner and more robust future work. For example, if we
want to abstract the scheduler away from the AIDL provider.
Bug: 181984005
Test: atest CtsBiometricsTestCases
Change-Id: I5850cae1f30f9479a29565b7b7c0d43108d0f7bd
Split it up into more generic and useable components that are not as
location specific.
Bug: 182491144
Bug: 181665909
Test: presubmits
Change-Id: I2d6d5e70328657a7430e170531402cb3acbed028
* changes:
Add trace for tracking the performance of new starting window
Force enable hardware accelerated for starting window
Pre-draw AdaptiveIconDrawable and cache it before doFrame
The connection service will become the mainline module.
Remove the hidden API usage of NetworkAgent.
Bug: 170598012
CTS-Coverage-Bug: 170598012
Test: atest FrameworksNetTests FrameworksTelephonyTests
atest FrameworksWifiTests
Change-Id: I4e4040ae7f94bdf479c7df9ec2ffabafbe06331c
+ simplify adding new callbacks on storage state
+ streamline lock story for ifs members
Bug: 183101753
Fixes: 183101753
Test: atest PackageManagerShellCommandTest PackageManagerShellCommandIncrementalTest IncrementalServiceTest PackageManagerServiceTest ChecksumsTest
Change-Id: I86fffa7101eeb42ebccca67ae7f5d133c1ab9dfa
This CL reworks our previous CL [1], which enabled "adb bugreport" to
include ime-tracing files into bugreport with some unpleasant
side-effect described in Bug 177462676.
Basically what this CL aims to do is to mirror my CL [2] for
InputMethodManagerService. Instead of relying on heuristics, this CL
introduces a clear and dedicated command
adb shell cmd input_method tracing save-for-bugreport
so that "adb bugreport" can explicitly tell IMMS to dump the tracing
files.
See the corresponding CL for frameworks/native [3] about how it's
triggered from "adb bugreport".
[1]: Ie87eb8423e2bb70f28c330983d45b95e2e07062d
ac24994aaa
[2]: I887ae6941b4844a606675b447f67ecee88d7f192
96a51f9971
[3]: I62105334e4efbb4514390ffa8be5416482ca3b29
02b1d2c70b2f4703a9dd51ba69d78604d66916e1
Bug: 177462676
Test: Manually done as follows.
1. adb shell cmd input_method tracing start
2. adb logcat -d -s imeTracing:*
Make sure ime tracing is running
3. adb shell dumpsys input_method \
--dump-priority CRITICAL --proto > /dev/null
4. adb logcat -d -s imeTracing:*
Make sure ime tracing has not been stopped.
5. adb shell cmd input_method tracing save-for-bugreport
6. adb logcat -d -s imeTracing:*
Make sure ime-tracing was dumped and is still running.
7. adb root && adb shell ls /data/misc/wmtrace/ -al
Make sure ime tracing files are saved.
Test: Manually done as follows.
1. adb shell cmd input_method tracing start
2. adb logcat -d -s imeTracing:*
Make sure ime tracing is running
3. adb bugreport bugreport.zip
4. adb logcat -d -s imeTracing:*
Make sure ime-tracing was dumped and is still running.
5. unzip -v bugreport.zip | grep ime_trace_
Make sure ime_trace_{clients,service,managerservice}.pb are
included.
Change-Id: Ib106e077a10eb6a4f37b38aa9172e7c99a81f898
This is a safe no-op CL that removes mis-specified
@GuardedBy("mMethodMap")
annotations from InputMethodManagerService, which was added while we
were trying to introduce proto-based event logging [1]. Otherwise our
lint would keep false-alarming even if those methods were correctly
used.
Anyway, this CL should have zero impact on generated code since
@GuardedBy annotation is used only for static code analysis.
[1]: Icbfb8c11e882f29eb45dea9d4c23315c48e9d619
5e68eeac86
Bug: 154348613
Bug: 177462676
Test: presubmit
Change-Id: I92fb0f9f8957ad0649bfad6196356bb3f9698e04
Android Framework needs to know for each RestoreSet provided by
BackupTransport the properties of the transport (e.g. device-to-device
transport, encryption) that was used to obtain the data in the restore
set in question.
Bug: 182986784
CTS-Coverage-Bug: 183441953
Test: atest FullBackupRulesHostSideTest
Change-Id: I07bc2d4eb3837390ea3b0aee769d143ab153335d
Adds additional logging around user switches, and fixes a bug where
location toggle changes were not logged correctly.
Bug: 183409327
Test: manual
Change-Id: I36fdef5c3eddd3db70d7c18506f82bb687677120
Now it does the same as TimeZoneIdValidator, but in upcoming CLs
it will map time zone IDs in suggestion to canonical ones.
Bug: 173787057
Test: atest com.android.server.timezonedetector.location
Change-Id: I61fe69c537ea10cde649454646329ee4d99dd69a
