News for hackers. Stuff that matters.
Re:Recognizing Speech from Smartphone Gyroscopes (2014) by leni536 on Monday January 18, 2016 @03:07AM (#10923186)
Solution: low pass filter gyroscope sensor data before the application can access it. Is there a legitimate reason for an application to need gyroscope data in the range of ~200Hz?
Re:Recognizing Speech from Smartphone Gyroscopes (2014) by wallacoloo on Monday January 18, 2016 @03:23AM (#10923237)
I think this is a legitimate usage for some games, for example, racing games in which you steer via tilt. The bigger issue in this case is not the frequencies visible to the application (the relevant hand motion is much below 200 Hz), but rather the latency of these movements. If possible, a game should be able to respond to a tilt action within the duration of a single frame.

But it's impossible to filter a signal in the time domain without introducing a phase shift (i.e. a delay). As a result, you cannot remove that extra frequency information before sending the data to an application without making sacrifices on latency.

Re:Recognizing Speech from Smartphone Gyroscopes (2014) by leni536 on Monday January 18, 2016 @06:27AM (#10923770)
Alternative solution: make the unfiltered gyro data available through an explicit permission.
Re:Recognizing Speech from Smartphone Gyroscopes (2014) by wallacoloo on Monday January 18, 2016 @05:35PM (#10927515)
Perhaps it's possible to use some sort of active cancellation - like what noise-cancelling headphones do - only in this case you would be trying to minimize the correlation between gyroscopic data & microphone data.