Reports a stationary state event when the device is at absolute
rest. For example, the device is placed on a stationary object, such as desk or table.
Reports a moving state event when the device transitions from absolute rest to moving state.
For example, the device is lifted from a desk or table.
Uses the accelerometer motion detect interrupt to reduce
the power.
Triggers when detecting a significant motion—a motion
that might lead to a change in the user location. For
example, walking, biking, or sitting in a moving car,
coach, or train.
The following examples don’t trigger a significant
motion:
The device is in a pocket and the person isn’t
moving.
The device is on a table and the table shakes a bit.
Reporting mode: Single response, after the notification
sensor automatically disables itself.
A low-power dynamic calibration algorithm for gyroscopes.
Validated across multiple gyroscope parts from different
vendors.
A low-power dynamic calibration algorithm for the magnetometer sensor.
Validated across multiple magnetometer parts from
different vendors.
Reports the orientation of the device that is relative to
an unspecified coordinate frame.
Obtains the orientation through integration of
accelerometer and gyroscope readings. Therefore, the
y-axis doesn’t point north; instead, it points to an arbitrary
reference.
Provides a three-dimensional vector indicating the
direction and magnitude of gravity.
Determines the relative orientation of the device in space.
Reports the orientation of the device relative to the ENU coordinates frame.
Unlike geomagnetic rotation vector, this sensor uses gyroscope.
Obtains orientation through the integration of accelerometer, gyroscope, and magnetometer readings.
Tracks the distance in meters, and reports to the client when the requested distance is completed.
The client can query the accumulated distance any time before the final distance is reached.
Reduces the development time.
Plug and play of QSH-compliant sensors across the platforms.
QSH drivers or algorithms are compliant across Qualcomm® Snapdragon platforms.
Generic APIs.
Saves power by enabling the local memory.
Due to the limited local memory, only a finite number of sensors can fit in here.
Enables QSH to operate in ultralow power mode, meeting the low-power requirements of the industry.
Suitable for background use cases, such as proximity detection and gesture recognition.
More memory and more on-chip resources are available, as compared to the Island mode.
Higher power consumption due to more on-chip resources being active.
Access to the larger main memory allows integration of more sensors.
Supports cycle-intensive operations.
Improves sensor accuracy.
By default, this feature is available.
QSH supports calibration for hardware-based sensors.
Calibration standardizes equipment for precise results, which ensures that the sensor values match the baseline.
Recalibration maintains sensor accuracy and adjusts for sensitivity changes over time.
For more information, see Calibrate sensors.
Configure the buses, power rails, GPIOs, and Interrupt/Polling modes, for physical sensors.
By default, this feature is available.
Change sensors configuration, such as Serial Bus type, GPIOs, and Interrupt/Polling mode.
Sensors are configured using the Registry files parsed during QSH framework initialization.
For more information, see Configure sensors.
Includes device motion, activity, and device physical position sensors.
Gathers data from one or more physical sensors and generates the intended output.
These sensors are a set of software algorithms.
Enables device motion using significant motion.
Supports device positioning and direction using linear acceleration, gravity, geomagnetic rotation vector, and rotation vector sensor.
Step counter, step detector, and activity recognition help to identify user activities.
For more information, see Software-based sensors.
Low latency and improved performance, as compared to the Qualcomm messaging interface (QMI).
The QSH direct channel is an interface designed for high-speed applications. It ensures that sensor data is transmitted with minimal delay, which is crucial for high-rate applications, such as optical image stabilization (OIS) and other camera sensor use cases that require real-time or near-real-time data processing.
The overall system performance is enhanced due to the efficient handling and quick access to sensor data, making it suitable for applications that demand high-speed data processing.
For more information, see QSH direct channel APIs.