Adding HAL changes for the following
i) a method to place the HAL in a special mode.
Expect to use this method for data-injection.
ii) a method to inject sensor data into the sensors subsystem.
iii) New sensor type for a SYNC event (google custom sensor).
iv) New sensor type for a nudge gesture (google custom sensor).
Change-Id: Idf0479b6301c5363cf51938e23aabc790b69fa96
Adds a new sensor type for converting the Android Wear defined wrist
tilt sensor type into an official android sensor type.
Change-Id: If6357aeb463a556a68a19b28931edec04f99a952
i) on-change sensors should set maxDelay.
ii) Drivers should hold a wake_lock till poll() is called
the next time when delivering events from wake-up sensors.
Change-Id: I4b137843d5c857f04601618548306a710fbfbe5c
Merged and resolved conflicts with Ic66b792c8229867fa5ff760cdde3d7c6f3360296
Conflicts:
include/hardware/sensors.h
Change-Id: I47b7e5f16b50fd5272590f6daba4a9d6833b3afb
Step count can reset when android restarts
When calling activate() without calling setDelay() before, use a default rate
Uncalibrated magnetometer should not be low pass filtered
The accelerometer can be used for the geomagnetic rotation vector
When batching call retuns an error, it shouldn't change the state. In particular, it shouldn't change the rate.
batch(timeout=0) must always return success
Wake upon fifo full will never be specified when timeout=0
setDelay is not called when in batch mode
Change-Id: I8a437eeedbdc54e5f1f3e644a92e9f781d7add0d
Improve explanation of Batch mode
Put the 4th component of the unit quaternion back in the rotation vector
Modify rotation vector description
Modify definition of uncalibrated sensor event
Remove query()
Change-Id: I7564073fac0e2467bcfca040b259d9d20e2688c5
Specified more precisely what the uncalibrated magnetometer should be
Added uncalibrated sensors event struct
Specified that rotation vector and game rotation vector have to use gyroscopes
Added magnetic field rotation vector
Added accuracy field to rotation vector and magnetometer rotation vector
Added section on comparative importance of batching different sensors
Specified that one-shot sensors must deactivate themselves before sending an event.
Change-Id: Ibc30ce6fc30e698af49a91930bd5a8316b6568b9
mainly update the documentation, add new sensor types
and add a batch mode.
- TYPE_PEDOMETER, defines a pedometer sensor
- TYPE_SIGNIFICANT_MOTION, defines a sensor that triggers an
event when the device is moving "enough". This sensor must allow
the SoC to go into suspend, while it is enabled.
- TYPE_STEP_COUNTER, defines a pedometer but returns a step count
(and looses precise timestamps, per step).
Change-Id: I3e20ff165851b7cb318f3c6637a6580de156b8fe
- add support for SENSOR_TYPE_MAGNETIC_FIELD_UNCALIBRATED
- add support for SENSOR_TYPE_GAME_ROTATION_VECTOR
- add support for SENSOR_TYPE_GYROSCOPE_UNCALIBRATED
Change-Id: I83048eb239d2123b5ec1f411b99f1883080a646f
the current API / Documentation would not allow to set the
rate of "non continuous" sensors.
Most sensors HAL implementation already support changing the rate
(technically they're not compliant with the doc), so it's easier
to change the doc (and also allows more control).
Change-Id: I4ad324ddc3b569ec61770b3cf927c06f8ff4af4e
