> Sometimes it is impossible to change sampling frequency, so, developer have only option to use 'reporting' frequency.
This is precisely the distinction I've been trying to convince everyone to make between **periodic reporting mode** sensors and **implementation specific reporting mode** sensors since pretty much forever (I agree the name might have been a misnomer but anyway).
> There might be no way to set '240Hz' sampling frequency, as in your example.
Absolutely, but specifying a **reporting** frequency for a sensor that's operating in low-power mode is sort of absurd.
On the other hand, not being able to set the **sampling** frequency for a gyroscope is going to prevent a whole bunch of use cases from working properly.
Hence you need to be able to handle all these case, deal with sensors that don't support some of them appropriately (e.g. fire an error event when a **sampling** frequency is request on a sensor that only supports low power mode, *as I originally spec'ed*, etc.), and make the interface/option setting intuitive enough that developers actually do the right thing most of the time. :)
--
GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-304226388 using your GitHub account