I've recently observed some really strange behavior on a Samsung Gear S3 device running Tizen 126.96.36.199. I've written both a native service app an web app targetting Tizen 3.0 for wearables but don't see any difference. During launch of these apps, I've used corresponding calls to keep the CPU awake to prevent the sensor acquisition to go to sleep which I had previously experienced. I log the samples in a file stored on the device's local storage (in /opt/usr/media/).
Now the strange thing is, when I force the CPU to stay awake, the log file contains twice as many sensor samples.
To clarify, if I'm logging the acceleromter signal I'm getting: Acc1 - Acc1 - Acc2 - Acc2 - .... - AccN - AccN instead of just Acc1 - Acc2 - Acc3, etc. which I observe when not forcing the CPU to stay awake. So somehow forcing the CPU to stay awake is pushing the system to simply repeat every sample. Even the event time-stamps are the same for every pair of identical samples!!
Has anyone observed this behavior before? Is it a known Tizen bug?
Thanks in advance for your input/comments,