Don't use the timestamp channel in any-motion mode
Don't use the timestamp channel in any-motion mode

That seems to create out of order timestamps issues in the
CTS Verifier Single Sensor Tests, and as it's a degraded, low
accuracy mode anyway, we are probably perfectly fine with the
usermode, HAL-level, timestamp.

Change-Id: I771c7e81916ae8ccf207ba3b213f9bc7525de362
Signed-off-by: Patrick Porlan <6b7a5b9114e07d350ffba0c179039885a7e82794@intel.com>

01org/android-iio-sensors-hal,01org/android-iio-sensors-hal