I'm totally talking out of my butt (have not looked at the relevant code) but I'm guessing that questions 1 and 2 have more to do with driver/hardware limits than Android-imposed limits.
On Monday, October 15, 2012 6:55:47 PM UTC-7, Guillermo Polonsky wrote: > > Did you get a reply on any of these questions? I'm interested too. > BTW, I don't think is would be probably to get more than 3Gs as for > example the accelerometer of the Samsung Galaxy S2 can detect a maximum of > 19m/s^2 which is approx 3.3Gs > Best Regards. Guillermo. > > El lunes, 23 de julio de 2012 14:35:28 UTC-3, JAM escribió: >> >> Hello all. >> >> Hope someone can help. >> >> 1) Is there a way to have a program read higher than 1-2gs? I had a >> beta version built and it doesn't seem to have the ability to read more >> than 1g on some of the phones I've tested it on. >> >> 2) Is there a way to get the phone to receive more samples than the >> 20-40ms it seems to do when set to "fastest"? I need a more accurate >> profile of the accelerometer output than I'm getting. >> >> 3) If I gave someone a specific profile of something I'd like the >> accelerometer to find (a spike that gets above 2g and stays there for a >> duration of 5ms or longer -- like a golf swing), could it be programed to >> "see" such an incident consistantly? >> >> >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
