AoaHID: Use 1-based IDs for virtual devices A recent kernel security hardening patch restricts virtual HID device registration to IDs greater than 0. The aoa-helper library assigned 0-based IDs to virtual devices based on the enum ordinal() value (e.g. touch screen was ID 0). When attempting to connect to a device running the updated kernel, the kernel rejects the ID 0 registration causing a pipe error on the host side. Shift the virtual device IDs to be 1-based (ordinal() + 1) to satisfy the kernel's id > 0 validation check. Bug: 531673909 Test: atest aoa-helper-test Flag: EXEMPT BUGFIX Cherrypick-From: https://googleplex-android-review.googlesource.com/q/commit:549ba4077992aeb9084cb939d903f47ea59e412c Merged-In: Ib35a0230a7459a1bf52d3be90902b77fd7d7444d Change-Id: Ib35a0230a7459a1bf52d3be90902b77fd7d7444d
TF is a test harness used to drive Android automated testing. It runs on test hosts and monitors the connected devices, handling test scheduling & execution and device management.
Other test harnesses like Compatibility Test Suite (CTS) and Vendor Test Suite (VTS) use TF as a basis and extend it for their particular needs.
1. Create your change in Gerrit 2. Add the reviewer named "Tradefed Codereview" (email: tradefed-codereview@tradefederation.google.com.iam.gserviceaccount.com) 3. Review the code review guidance at go/tf-guidelines and go/tradefed-code-reviews 4. GWSQ should add a couple of people from the team to review your code and give feedback.
More information at: https://source.android.com/docs/core/tests/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/docs/core/tests/tradefed/architecture
If you are a tests writer you should start looking in the test_framework/ component which contains everything needed to write a tests in Tradefed.