Lines Matching full:sensor
46 latest event from each on-change sensor: the last event <a href="batching.html#precautions_to_take_when_batching_non-wake-up_on-change_sensors">must be saved </a>outside of the FIFO so it cannot be lost.</p>
58 reported. That is, the sensor must wake the SoC up and deliver the events
68 <p>Up to KitKat, whether a sensor was a wake-up or a non-wake-up sensor was
69 dictated by the sensor type: most were non-wake-up sensors, with the exception
70 of the <a href="sensor-types.html#proximity">proximity</a> sensor and the <a href="sensor-types.html#significant_motion">significant motion detector</a>.</p>
71 <p>Starting in L, whether a given sensor is a wake-up sensor or not is specified
72 by a flag in the sensor definition. Most sensors can be defined by pairs of
73 wake-up and non-wake-up variants of the same sensor, in which case they must
76 <p>Unless specified otherwise in the sensor type definition, it is recommended to
77 implement one wake-up sensor and one non-wake-up sensor for each sensor type
78 listed in <a href="sensor-types.html">Sensor types</a>. In each sensor type
79 definition, see what sensor (wake-up or non-wake-up) will be returned by
80 <code>SensorManager.getDefaultSensor(sensorType)</code>. It is the sensor
