diff options
| author | 2019-04-22 17:25:49 -0700 | |
|---|---|---|
| committer | 2019-04-22 17:35:35 -0700 | |
| commit | 26029ee232500a3a58464465319e61eb79b79c6f (patch) | |
| tree | 9cedafdbbf75bc2a5c748cce0a6a685c940fdf65 /vulkan/libvulkan/api.cpp | |
| parent | c4f335d6f4b00bac3fde8c439bcc363dff0a77ac (diff) | |
Prevent stale event from being delivered to client
When an on-change sensor is activated, the most recent event is
delivered to the client. A previous change attempted to ensure that
any event that was generated prior to deactivating the sensor would
not be delivered to a client upon activating the sensor. This was to
ensure that an event that was generated in the past, and thus stale,
would not be received by clients. The patch was successful in most
cases, but it did not address the case of a client disabling a sensor
and still maintained a reference to the SensorEventConnection through
the NDK or VNDK.
This patch marks the recent event as stale whenever a sensor
transitions from deactivated to activated. This ensures that the
recent event is always marked as stale, regardless of how the API to
the Sensor Service is utilized.
Bug: 116283108
Test: Verified that stale on-change event is not delivered to a
client.
Change-Id: Iee9a84ec57f5345fb14f0262b492ad100d05c7bb
Diffstat (limited to 'vulkan/libvulkan/api.cpp')
0 files changed, 0 insertions, 0 deletions