HIDL libs are not necessarily part of VNDK now. Because some are
used by VNDK libs, they are still VNDK. But rest are now just
vendor-available.
.hidl_for_test files are also removed because they are used to exclude
test-purpose hidl libs from VNDK libs.
Instead, .hidl_for_system_ext files are added to tests/lazy to
distinguish them from others which are installed /system.
Bug: 143933769
Test: update-makefiles.sh && m com.android.vndk.current
Merged-In: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
Change-Id: Ia81312dda340b6b5cbdd7a3c21e1d323bda39a4a
(cherry picked from commit b0907a6bb8)
Bug: 151896491
Test: local build
Exempt-From-Owner-Approval: This CL update suite name vts-core to vts as
the suite name is updated. This CL won't change test logic or behavior.
Change-Id: I562b4dc50765e953800a814a8fd84a01c1b9352b
Merged-In: I562b4dc50765e953800a814a8fd84a01c1b9352b
We separate out per-mode tests into a separate test suite for better
extensibility. If a new DumpstateMode value is added to 1.1, it will no
longer require updating a macro in the test.
All tests still run the same and if they're per-mode, still include the
actual mode string in their final name. No material behavior changes.
Test: atest VtsHalDumpstateV1_1TargetTest on cuttlefish
Change-Id: Ifefae981705e564c10ee450851d3d2320f8206f3
Pixel has been dumping some non-sensitive information in bug reports
using IDumpstateDevice for a long time, and requiring nothing to be
dumped on user builds by default suddenly changes behavior.
To account for this use case, we instead change the meaning of the
toggle to control *verbose* logging, specifically anything with privacy,
storage, or battery impact.
VTS tests are updated appropriately.
Bug: 143183758
Bug: 143184495
Test: atest VtsHalDumpstateV1_1TargetTest
Change-Id: Ib71ce43e9168d82fd9ee0564db813c5a3538c459
Merged-In: Ib71ce43e9168d82fd9ee0564db813c5a3538c459
(cherry picked from commit 09c8b5ba59)
Add a "PROTO" dumpstate mode to request a protobuf dump from
IDumpstateDevice HAL, primarily used by incidentd to get
device-specific state as a proto for automated issue reporting and
debugging.
Since the format of these states can vary across vendors and devices,
the proto schema will not be defined in AOSP.
Bug: 140521164
Test: VtsHalDumpstateV1_1TargetTest
Change-Id: I1d586c99b654471db5028039792c3d9e6e2184bb
Merged-In: I1d586c99b654471db5028039792c3d9e6e2184bb
Add dumpstateBoard_1_1 to accept a mode parameter (e.g. for limiting
vendor logs to the right bug reports).
Add setDeviceLoggingEnabled for the user to toggle vendor logging on and
off.
Bug: 143183758
Bug: 143184495
Test: atest VtsHalDumpstateV1_1TargetTest
Change-Id: I5420e5e4ce88619c7e40cf967382f98babc3c3d5
Merged-In: I5420e5e4ce88619c7e40cf967382f98babc3c3d5
(cherry picked from commit c9e2c6d319)
Convert VtsHalDumpstateV1_0TargetTest to be parameterized test
and add it to vts-core.
Bug: 142397658
Test: $atest VtsHalDumpstateV1_0TargetTest
Change-Id: Ifba3b6dac6f7f4e153f50d521e6d2e07f599cf7e
hwservicemanager will now shutdown the service when it is not in use.
This puts less restrictions on clients.
Bug: N/A
Test: build only (this is an example implementation not used on any
device)
Change-Id: I4641e727f6e4c3ca5d97d53a66b3cc0fee6f12f3
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: I075670b64eebbbbd6a6ae0e84ad51bf1c6f5ba36
Since it only prints a date.
Bug: 140115084
Test: boot device and check that this can run (as I've also had to
update file contexts for it)
Change-Id: Id22452cec4f32c2bbfa07065cb5e9c5d2b9936bf
hidl-generated makefiles are now generated such that bpfmt(file) == file.
Bug: 67417008
Test: enable bpfmt hook
Change-Id: I1f69d292bc23a7cc293a66110cb02d597e1019ad
HIDL_FETCH_IDumpstateDevice isn't defined simply
because this is a binderized service and this function
would be called (to no great use) if it was installed
to a device.
Bug: N/A
Test: N/A
Change-Id: I9b660af3fe329977cdcd0c3f485af651c34416cb
Bug: 78509314
Test: HAL isn't running
Test: adb bugreport HAL runs
Test: HAL isn't running after bugreport finishes
Test: manually inspect state using `lshal` and logs
using `adb logcat | grep android.hardware.dump`
(cherry picked from commit 711b806727c85d91cf805db4f78b4a9609e2bf43)
Change-Id: Ic97516a4297e7933430fb4fa3fd0109f8c1b1d0a
Removing whenever I see these in code reviews.
Test: none
Merged-In: I4322f533a837d55618ec2ed2125e8966ace9d61d
Change-Id: I4322f533a837d55618ec2ed2125e8966ace9d61d
Removing whenever I see these in code reviews.
Test: none
Merged-In: I4322f533a837d55618ec2ed2125e8966ace9d61d
Change-Id: I4322f533a837d55618ec2ed2125e8966ace9d61d
Dumpstate hal does not have selinux permissions to files under
/data/local/tmp. So we pass fds to pipes to the hal for testing, which
works out because of this selinux rule:
allow domain su:fifo_file { write getattr };
Bug: 67648445
Test: VtsHalDumpstateV1_0Target
Change-Id: I804ef03250f18d3aa34393297e8ac9725e437dbb
