- Added support for SensorHeadTrackerTest. This does not affect other tests used by Hid Command tool.
- Added two new functions setGetReportResponse() and
sendSetReportReply()
Bug: 228319672
Test: atest android.hardware.cts.SensorHeadTrackerTest
Change-Id: I83cfe1f71df57584dac7288ab092164a5c5dea3c
Bazel doesn't allow a module and file with the same name.
These are some extra modules I missed in aosp/2201115
Bug: 198619163
Test: m am, verified it was still installed to out/target/product/emulator64_x86_64/system/bin/am and not am.sh
Change-Id: I763a938918854541ec5b0bcf740b1b6cf0fce771
Bazel doesn't allow a module and file with the same name.
Bug: 198619163
Test: m ime, verified it was still installed to out/target/product/emulator64_x86_64/system/bin/ime and not ime.sh
Change-Id: I214e190e159a7aff9149e77146d1a493992e885d
Split SysTrace.h into SysTrace.cpp to avoid defining ATRACE_TAG
in the clients of SysTrace.h
This is in preparation to land aosp/2190022
Test: m
Bug: 161393989
Change-Id: I0ed94c9f66043aa83a59e8042ec9e61ee47db0f2
Emptyness of a String8 variable was not checked correctly.
As a result, even when no arguments were provided,
`app_process` was still launching runtime.
Test: adb shell app_process64
Change-Id: Ia303edb5a74b61efad24b475008a3642a07ab789
The fix is taken from AOSP patch aosp/2154236.
This will make sure the UI Automator always has the entire display to
interact with. Otherwise, in multi-windowing mode or on devices with
task bar, it will only be able to interact with the current focused
window, the default launch bounds, or the display excluding task bar,
depends on the actual scenario.
Test: PlatformSenarioTests
Bug: 238981445
Bug: 238985243
Bug: 238581838
Bug: 233945217
Change-Id: I9223ef5552ddb081e75de1242670862f2813e56d
This change adds all dumpsys sections defined in incident.proto from
being included when incident is called from dumpstate, since these
sections are already included elsewhere in bug reports. This reduces the
time taken in the INCIDENT REPORT section by ~6.8s (18.64s -> 11.83s).
Test: - atest incidentd_test
Test: - Took a bug report and verified that the incident report in bug
reports no longer contained dumpsys sections.
- atest incident_d test
Bug: 239444802
Change-Id: Ia090131687401fcbfea9708e80fd02899a8fb643
Since pids can belong to non hal processes as well, in theory.
Bug: 233130219
Test: build
Merged-In: I8ef6b2aaa871f6a8f992887a394d81c544e9cba4
Change-Id: I8ef6b2aaa871f6a8f992887a394d81c544e9cba4
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
(cherry picked from commit d1ce457da1)
Emulated FBE was a developer-mode feature intended to allow developers
to add Direct Boot support to apps before native FBE devices became
widely available. Since all devices running the latest version of
Android now use native FBE (except for a couple edge cases not relevant
here, like in-development devices on which encryption hasn't been
enabled yet), and emulated FBE doesn't work on native FBE devices
anyway, there's no longer any need to carry the code for emulated FBE.
Bug: 232458753
Change-Id: I2ab35472c872b19b2bf64aa99424b5ccd9f6170f
Since pids can belong to non hal processes as well, in theory.
Bug: 233130219
Test: build
Change-Id: I8ef6b2aaa871f6a8f992887a394d81c544e9cba4
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
During OTA, sysprops aren't available as early in the boot process.
This causes the boot animation to not have dynamic colors.
This CL tries to load the colors more frequently, at every part loop.
Before we'd only try on the first frame of each animation part.
Test: adb shell bootanimation
Fixes: 229029861
Change-Id: I1bbebf93b4fbc31d945c4181472576cf29f13bc7
The resolution may be changed while the boot animation is playing.
mInitWidth and mInitHeight store the original resolution, and then the
animation coordinate and size are recalculated according to the ratio
(mWidth/mInitWidth and mHeight/mInitHeight).
Bug: 228605923
Test: change resolution and then reboot to check the animation
Change-Id: Id09490ecf7fc4b3e1a6baf073c134f357e9b327f
(cherry picked from commit 764ea04421)
Merged-In: Id09490ecf7fc4b3e1a6baf073c134f357e9b327f
We often get bugs where testers have executed a LONG list of test steps.
It becomes extremely difficult to know where in the logs corresponds to
which test script step.
This adds a new telecom shell command:
adb shell telecom log-mark Testing 1 2 3
This command adds a USER_LOG_MARK event log item to all ongoing calls and
to the general telecom logs with the specified message.
Test: Tested using the new shell command to mark the telecom logs in and out of calls.
Fixes: 228895073
Change-Id: Ic11edc777e57a4fc8748a42c931379faf7cea671
"locksettings help".
This removes the duplication and also fixes the
current behavior showing the incorrect documentation for "locksettings
verify" which does *not* log in the user.
Test: adb shell locksettings
Test: adb shell locksettings clear --old 0000 (to verify other commands
still work)
Change-Id: I429288a9e4280d41213e1c0fd8234d3666888abc
Because the resetUsbPort API modified to Asynchronous,
related function need to be modified.
Bug: 217369748
Signed-off-by: Ricky Niu <rickyniu@google.com>
Change-Id: Ieef549736532688ff356b4bb8fa790fb10403300
Implement resetUsbPort to support manual testing on
real device to verify feature functionality from App layer
and VTS test.
Bug: 216387845
Test: Manual test with "svc usb reset UsbPort" correctly
Signed-off-by: Ricky Niu <rickyniu@google.com>
Change-Id: Ieb29de3dd398859607490548a1f3a16f8359ae8f
(cherry picked from commit 519062eabd)
Merged-In: Ieb29de3dd398859607490548a1f3a16f8359ae8f
During OTA, sysprops aren't load as fast as during regular boot.
This causes the animation to not be able to pick up the dynamic colors.
We can mitigate this issue by trying to reload the sysprops at the
beginning of each animation part.
Test: manual
Bug: 227381265
Change-Id: I4397079aacc52acb5cda54a925f70e4f5c745b3f
The following restrictions applies to the instrumentation of the sdk
sandbox processes:
* Instrumentation must be signed with the same certificate as the client
app the instrumented sdk sandbox belongs to.
* If there is a running instance of to-be-instrumented sdk sandbox
process, then it will be killed before the instrumentation starts.
* While instrumentation is running the client app won't be allowed to
connect to the instrumented sdk sandbox process.
* The --no-restart instrumentation of the sdk sandbox processes is not
supported.
Bug: 209061624
Test: atest SdkSandboxInprocessTests
Change-Id: Ia4b145c091bf8da600a77ea82fc9e3cd97757275
Revert "Disable pointer authentication in app processes."
Revert submission 1954983-master-I3030c47be9d02a27505bd4775c1982a20755758c
Reason for revert: PAC has shipped with S, and we're going with app compat outreach rather than regressing security.
Reverted Changes:
I3030c47be:Disable pointer authentication in app processes.
I3030c47be:Disable pointer authentication in app processes.
Change-Id: I75c4d2d3cf59aecf99d9c9d37c6750f999e74de8
The information will be printed
- Message if no animation file
- File name when it's loaded
- Image name and path, loop information when playing
- Play time at the end
Bug: 220161782
Test: Manual, check logcat with and without bootanimation.zip
Change-Id: I0e16bdeb4456a423649a27f7ae88f256e3fa3d19
