Thanks Joshua, that’s a very “can-do” offer and much appreciated.
However, not an immediate issue for me now as I am well into porting my code into a different Lua development package which provides the raw data already. In some ways it is more difficult to use than Corona and not as polished, but it filled the immediate need…
I do think adding the raw data to your accelerometer API is a good idea though, and perhaps this discussion may be of benefit to others.
For example, from what you’ve said, adjusting the frame rate in Corona may change the frequency cutoffs of the accelerometer filtering, perhaps resulting in (apparently inexplicable until you understand the filtering) changes in accelerometer behaviour (e.g. response time, lag, jitter etc.). With a user provides the filtering themselves, a change in frame rate could be compensated by different filter values to provide a similar response from the accelerometers.
Best regards,
Doug