AIDL interfaces which are vintf-stable have to be frozen in release.
But these interfaces have been never frozen, so freeze them.
- android.hardware.power
- android.hardware.identity
- android.hardware.keymaster
- android.hardware.vibrator
- android.hardware.light
- android.hardware.tests.extension.vibrator
Bug: 153500421
Bug: 153500550
Bug: 153511407
Bug: 153500549
Bug: 153501107
Bug: 153501202
Test: m
Change-Id: I643c25fc695f9d1e874dcceb327d465c49e9cab6
Merged-In: I643c25fc695f9d1e874dcceb327d465c49e9cab6
Dumping android.hardware.tests.extension.vibrator was ommited
because of difference of module name across branch.
Bug: 153501107
Bug: 152655547
Test: m
Change-Id: Ia272ffa77add9ef0b02ee0a23fc2389ac69fa9aa
Merged-In: Ia272ffa77add9ef0b02ee0a23fc2389ac69fa9aa
All aidl_interface modules should by default considered as stable, in
case it is used across system and vendor partitions, or across modules.
Like other API surfaces, we need to have a dump for the current
(yet-to-be-released) version and update it when there is an API change.
This is done via .
Then the owner of the interface can freeze the current version as a
numbered version via .
This change shal be rejected only when the owner is certain that the
interface is not used across the updatable boundaries.
Bug: 152655547
Test: m
Change-Id: I93fba2721695a14e0eb4a2173066ce132228b895
In order to provide a more descriptive name, and to be consistent
with HIDL, the stable AIDL package names are switching from
vintf-vibrator format to the package format
(android.hardware.vibrator).
Bug: N/A
Test: all build time
Change-Id: I52959482898f329ad1b3a3a5b345a0c6dc72197d
This CL shows an example of how to use and retrieve a HAL extension.
Bug: 136027762
Test: run HAL and:
- use "dumpsys --pid android.hardware.vibrator.IVibrator/default" to
make sure that the HAL I'm running is the binary being added.
- VtsHalVibratorTargetTest
- test-vintf-vibrator-ext-client
Change-Id: I8614007a727e8e05ba4667c2cd1623ce936a1609
Packages which contain some non-supported Java types can still have
their Java-supported types used in Java.
Bug: 143566068
Test: mma
Change-Id: I2afc5cc8d0a1bd981108ee2b87d6033fd48bdb37
Since it is accidentally installed on some devices, although it is a
test.
Bug: 123878766
Test: atest hwbinderThroughputTest
Change-Id: Id43aa7e9ca3152c35bb2dac84d7386c9d7a5e0aa
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: I075670b64eebbbbd6a6ae0e84ad51bf1c6f5ba36
These are not used anywhere in the tree and are hence not supported.
These are being removed from hidl-gen so this code is being removed.
Bug: N/A
Test: hidl-gen -Lcheck android.hardware.tests.expression@1.0
Change-Id: Ia19746da8ba361c7f29cc8732058a27cdc7a1bfe
So that the test doesn't require modifying the system partition.
Still creating a shared version of this library since some things
downstream still depend on this.
Bug: 136111641
Test: libbinder_benchmark
Change-Id: I636f53c2a2bc4705804ca36d124102eba55c23e6
This type is unused and some parts of it has bitrot. In order to reduce
the complexity of new features, removing this.
Fixes: 131616631
Test: HIDL's test/run_all_device_tests.sh
Test: HIDL's test/run_all_host_tests.sh
Change-Id: Ib7f94053ab987ccb6858eec1cfd7e53fd7320ba3
hidl-generated makefiles are now generated such that bpfmt(file) == file.
Bug: 67417008
Test: enable bpfmt hook
Change-Id: I1f69d292bc23a7cc293a66110cb02d597e1019ad
So that it can be included in tests.
Bug: 122456128
Test: libhwbinder_benchmark, hwbinderThroughputTest, libhwbinder_latency
Change-Id: I4c77c04252c7d6f0c2215ee052d747561db181e0
toString is broken in some cases because of recursive definitions. This
exercises that case.
Bug: 117342189
Test: hidl_test
Test: m android.hardware.tests.baz@1.0 android.hardware.tests.baz-V1.0-java
(this runs hidl-gen on this for both Java and C++ output)
Test: manually inspected output
Change-Id: Ic09ac133345f2d83d6f83d3d0af1f63e7e3250ee
pointer needs a fixup (to abort) since they can't be used in remote
transactions, so removing it from the union here.
Bug: 117322722
Test: hidl_test
Change-Id: Ie582f6b79a8176ca1585bf4b1f43ae9d5d97fa92
This change adds HIDL handle types to the baz@1.0 and safeunion@1.0 test
HALs to exercise native handles in Java.
Bug: 35098567
Test: Ran the hidl_test (C++ and Java) suites
Change-Id: Iddf1c269cbdc68ce337f1e787570f3810f7baad2
Test: make vts -j; fmq_test
Changes:
* Modified method that configures the synchronized queue. Now this method takes in a descriptor of an existing queue and creates a queue on the HAL server side.
Change-Id: I395d6311f3580af6a87556849b3e921fa9eaf097
This change removes Java-incompatible types (memory, handle) from the
safeunion@1.0 test HAL. Moving forward, the idea is to keep this HAL
Java & C++-friendly, and create another version (likely safeunion@2.0)
to regress on C++-only types; tracked by b/110269925.
Bug: n/a
Test: Ran the existing hidl_test suite
Change-Id: Ic7458c3f5b571e77e5f894a9854a2b201f53fe18
This change adds a new HIDL safe union, InterfaceTypeSafeUnion
(containing an interface+array) to the safeunion test HAL.
Bug: 79878527
Bug: 110269925
Test: Existing hidl_test suite passes successfully. Added more test-
cases to hidl_test_client.cpp to exercise InterfaceTypeSafeUnion
(included in a separate CL).
Change-Id: I04ffeeeabccc1dc2651aac9371569c36d37f4f87
This change implements a basic HAL and server-side functionality to test
the HIDL implementation of safe unions.
Bug: 79878527
Test: Ran make, new tests in hidl_test/ pass successfully (included in a
separate CL).
Change-Id: Ia420137bc1dc0a188e04176081c7f5418e74449c
