3 ms·

OK, I just busted your theory. Sorry. :) It has 16G The LSM330 has an user-selectable full scale acceleration range of ±2 g/±4 g/±6 g/±8 g/±16 g and angular ra

by X4 13y ago

OK, I just busted your theory. Sorry. :) It has 16G The LSM330 has an user-selectable full scale acceleration range of ±2 g/±4 g/±6 g/±8 g/±16 g and angular rate range of ±250/±500/±2000 d. Samsung Galaxy S4 accelerometers/gyro Datasheet: http://www.st.com/web/en/catalog/sense_power/FM89/SC1448/PF253882 http://www.st.com/web/en/catalog/sense_power/FM89/SC1448/PF2... Here's a FULL Teardown of the insides of the Samsung Galaxy S4. http://www.chipworks.com/blog/recentteardowns/2013/04/25/inside-the-samsung-galaxy-s4/ http://www.chipworks.com/blog/recentteardowns/2013/04/25/ins...

georgemcbay 13y ago
Even if there were a single phone that outperformed the Rift in real world responsiveness (and there isn't), that wouldn't really change anything because the whole value proposition of a generic smartphone printed solution is you use it with whatever phone you already have. If you have some phone other than that super phone, as the majority of smartphone users would, you then have to buy some specific $650 phone for the thing to give you comparable performance to the Rift, and you just spent more than double what a Rift costs.
- X4 13y ago
  Who said that your ordinary iPhone4s or iPhone5 hasn't comparable, equal or better sensors? Am not here to speculate and I know it's tedious to prove everything, but I welcome it in your next post :) Everyone benefits, if one bright mind comes up with a solution or a fact that others have to live with.
snogglethorpe 13y ago
Note that the attributes of the phone hardware sensors are important, but not sufficient—generic "use any phone, no root required!" solutions like you mentioned will have to send the data through a full stack of software layers that are very unlikely to be optimized for high-rate / low-latency uses like this one. You might get lucky and have a phone so incredibly powerful that even non-optimal software stacks are fast/low-latency enough to work well, but I suspect it will be a long time before most people do...
- X4 13y ago
  I risk the dangers of writing to a 10days old post.. You can use LLVM and CLANG to write the sensor tools, bypassing the entire "Stack of Software", could result in sub-millisecond reaction time.

by X4 13y ago

georgemcbay 13y ago

Even if there were a single phone that outperformed the Rift in real world responsiveness (and there isn't), that wouldn't really change anything because the whole value proposition of a generic smartphone printed solution is you use it with whatever phone you already have. If you have some phone other than that super phone, as the majority of smartphone users would, you then have to buy some specific $650 phone for the thing to give you comparable performance to the Rift, and you just spent more than double what a Rift costs.

X4 13y ago
Who said that your ordinary iPhone4s or iPhone5 hasn't comparable, equal or better sensors? Am not here to speculate and I know it's tedious to prove everything, but I welcome it in your next post :) Everyone benefits, if one bright mind comes up with a solution or a fact that others have to live with.

snogglethorpe 13y ago

Note that the attributes of the phone hardware sensors are important, but not sufficient—generic "use any phone, no root required!" solutions like you mentioned will have to send the data through a full stack of software layers that are very unlikely to be optimized for high-rate / low-latency uses like this one. You might get lucky and have a phone so incredibly powerful that even non-optimal software stacks are fast/low-latency enough to work well, but I suspect it will be a long time before most people do...

X4 13y ago
I risk the dangers of writing to a 10days old post.. You can use LLVM and CLANG to write the sensor tools, bypassing the entire "Stack of Software", could result in sub-millisecond reaction time.