During VTS testing, when many sensors are quickly enabled, the load on the Sensorhub side will be too heavy, and then continue to send sensor enable instructions and Sensor Flush instructions. These instructions sent by the Kernel driver to the Sensorhub through inter-core communication cannot be responded to in a timely manner. After the Kernel side judges the timeout, it will determine that the enable fails; after the enable fails, it cannot continue to test the flush or return the expected flush data.
ten sensors is tested as a group
Bug: 339763843
Test: run vts -m VtsHalSensorsV2_0TargetTest
(cherry picked from https://android-review.googlesource.com/q/commit:09952885e441bcf0d8f0bf0834ff46608b07e0d0)
Change-Id: I6f6d36d1e3c98b85b412189c3f97163c0945a7ab
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
go/new-android-ownership-model
Bug: 304529413
Test: N/A
Change-Id: Ic8c4bd6ac246e7efa98bbdaf822d12ae8e1230a5
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: I3322344f595f974f730dc824af0110388076d838
Just found that each device wants to install a different set of sensors
via LOCAL_SENSOR_FILE_OVERRIDES. Instead of providing a default list in
the apex, which would make things difficult to configure, let's not
hard-code the list in the apex.
Bug: 315089092
Test: cvd start && dumpsys sensorservice
Change-Id: Ie7ddbe6657d5afc06ca009ac37e3a54a5b26ad7d
- move apex definition near to the binary
- make the binary use static linking (for smaller size of apex)
- remove unused keys
Bug: n/a
Test: cvd start
Test: dumpsys sensorservice # available sensors
Change-Id: I07734c5a5b1ade542c669155dd96176f912629ac
If the payload of additionalInfo event isn't initialized, system will
crash when execute to the function of convertToHidlEvent in
HalProxyAidl::injectSensorData. Because there is an operation to get
the payload in the function of convertToHidlEvent.
Bug:306109770
Test:VtsAidlHalSensorsTargetTest.Sensors/SensorsAidlTest #InjectSensorEventData
Change-Id:I649de10451914ddfdb9d735ca1359521bf810bca
There is a new graphics.mapper HAL and instead of adding yet another
combination of mapper/allocator, use libui that handles all of that for
us.
Test: VtsAidlHalSensorsTargetTest
Bug: 304843606
Change-Id: Icf4a218de6afe0ae77a4520a6f78a4f7da9bedd4
This CL fixes an issue where a sensor may not generate any events
and the processing code calls .front() on an empty std::vector.
Bug: 291779133
Test: Presubmits
Change-Id: Ibb118f239ce9ea42fc25d1d05ba6bd46a60231f0
Upload files to /data/local/tests/unrestricted instead to improve data
collection in the event of a crash.
Bug: 284307085
Bug: 258819618
Bug: 199904562
Test: atest :kernel-presubmit
Change-Id: I14b8bdeec300e94c7796e8dfe644b644b4d96ba3
Signed-off-by: André Draszik <draszik@google.com>
Upload files to /data/local/tests/unrestricted instead to improve data
collection in the event of a crash.
Bug: 284307085
Bug: 258819618
Bug: 199904562
Test: atest :kernel-presubmit
Change-Id: Id4f73972910525dc4de6c19755d19a38092ae03b
Signed-off-by: André Draszik <draszik@google.com>
commit bde01c60fa
moved this APEX from the HIDL to AIDL impl, but accidentally
left out the rename of the binary in the file_contexts
Also deletes unused .rc file here; the APEX already reuses the
.rc file from outside the APEX dir.
Bug: 222579208
Test: Build cf_x86_64_phone using sensors APEX: http://ab/P33964358
Boot the device, use accel sensor to rotate the screen.
Change-Id: Ib107770312bb80b67364c855efd2df3a9bc52b9a
(cherry picked from commit 80e55dabf3)
Allow sensor hal to send SW_LID event through HID transport
drivers when hall_effect event is detected.
Bug: 262056923
Bug: 274537630
Test: Build pass.
Change-Id: Iddbb4b83f20955d7c316d0eee391effcf30f5b4f
Function assertTypeMatchStringType does not match the sensor type
HINGE_ANGLE that only exists on folding screen phones. When testing the
VtsAidlHalSensorsTargetTest on a folding screen mobile phone,
it will fail.
So we need add CHECK_TYPE_STRING_FOR_SENSOR_TYPE(HINGE_ANGLE) to
the function assertTypeMatchStringType.
Bug: 270831199
Change-Id: Ib82a1168ff90d851eee6ce025464b11bcda7d5ca
