Jump to content

Recommended Posts

I didn't know this at first, but the galaxy s features a 6 axis gyroscope! This means great opportunities for games/apps, developers :)

Does anyone know if there is an app to test it? if not, can someone pls hint a developer :D

Share this post


Link to post
Share on other sites
is there anyone know whether non-US version has gyroscope?

I have the European Version (bught by Amazon Germany) wich has a SMB380 Acceleration, an MS-3C Orientation, and a MS-3C Magnetic Sensors. There is no 6-Axis Gyroscope in the Eruropean Samsung Galaxy S I9000.

But the combination of this sensors is also very good for gaming.

Only thing the Sensor has an factory offset wich must be recalibrated and that can be done with on board Software but not without Super User Rights.

Regards

Christopher

Share this post


Link to post
Share on other sites
I have the European Version (bught by Amazon Germany) wich has a SMB380 Acceleration, an MS-3C Orientation, and a MS-3C Magnetic Sensors. There is no 6-Axis Gyroscope in the Eruropean Samsung Galaxy S I9000.

But the combination of this sensors is also very good for gaming.

Only thing the Sensor has an factory offset wich must be recalibrated and that can be done with on board Software but not without Super User Rights.

Regards

Christopher

Can you explain how to do this on a rooted phone?

Tankyou

Share this post


Link to post
Share on other sites
Does anyone know if there is an app to test it? if not, can someone pls hint a developer :)

Checkout the compass app (free in market). Change the compass type to GPS. In this mode it will show you the pitch and roll of your phone as well as the compass direction and also the GPS data.

Share this post


Link to post
Share on other sites
I have the European Version (bught by Amazon Germany) wich has a SMB380 Acceleration, an MS-3C Orientation, and a MS-3C Magnetic Sensors. There is no 6-Axis Gyroscope in the Eruropean Samsung Galaxy S I9000.

But the combination of this sensors is also very good for gaming.

Only thing the Sensor has an factory offset wich must be recalibrated and that can be done with on board Software but not without Super User Rights.

Regards

Christopher

Sorry to pull up an old thread but how did you recalibrate the sensor , i just got this phone and i am dead worried of the offset.

Thanks , i am looking forward to your reply

Share this post


Link to post
Share on other sites
Sorry to pull up an old thread but how did you recalibrate the sensor , i just got this phone and i am dead worried of the offset.

Thanks , i am looking forward to your reply

Phone must be rooted

STOP before pressing enter read the rest of this post!

Code:

adb shell

su

/system/bin/sensorcalibutil_yamaha

(can also be done from the phone with a terminal software like better terminal)

place the Phone horizontally on a table or somerhing flat, from which you knmow it is a correct horizontal area.

keep in mind that the phones back isn't flat so lay it on the edge of that table.

keep still in this position

Press Enter

after this reboot or restart the phone.

Thats all

regards Christopher

Edited by Tanis64

Share this post


Link to post
Share on other sites
I have the European Version (bught by Amazon Germany) wich has a SMB380 Acceleration, an MS-3C Orientation, and a MS-3C Magnetic Sensors. There is no 6-Axis Gyroscope in the Eruropean Samsung Galaxy S I9000.

But the combination of this sensors is also very good for gaming.

Only thing the Sensor has an factory offset wich must be recalibrated and that can be done with on board Software but not without Super User Rights.

Regards

Christopher

I'm pretty sure there are now 6-axis gyroscopes at all. There are only three rotational axis in a 3d world. At least as far as I know.

It is the combination of gyroscope and accelerometer that makes it a 6 axis device.

Share this post


Link to post
Share on other sites

Hi ,

As you know, all of the 4 american versions of Galaxy S have 6 axis accelerometer which is a combination of traditional 3 axis accelerometer and a 3 axis gyroscope like iPhone 4. but what about the international version of Galaxy S ? I thought the international version has only 3 axis accelerometer but today Omar Khan in MobileBeat 2010 conference shows a slide with international version of Galaxy S and there is a sentence above it:

image-0216_4C3E07BF.jpg

What do you think?

source:

http://mobile.venturebeat.com/2010/07/12/m...-with-galaxy-s/

Share this post


Link to post
Share on other sites
6 Axis.. wow thats 6-D!!!! perceive dimensions in gaming not yet available in reality!

I kid i kid. on a more serious note, watch this: http://www.youtube.com/watch?v=8SvXljHGcH4...eos=gRe4WCgyhig

Omar Khan claims that the european version of the galaxy S has 6 axis gaming. Much alike the iphone 4.

Well in that video he says it's a 3 axis accelerometer X 2 axis geo-magnetic (i.e. compass) = 6D so that doesn't sound much like a gyroscope unfortunatly.

Share this post


Link to post
Share on other sites

Great to find this and other threads like it i thought, i run the tool, and i get this:

# sensorcalibutil_yamaha

=====================================

Sensor Calibration Utilities

Copyright © 2009 Yamaha Corporation

=====================================

Starting calibration utilities...

access: Stale NFS file handle

msmachdep_Init failed

calibration utilities failed

When i try to use a compass app, or the *#0*# sensors app, i always see this in logcat:

I/ActivityManager( 2255): Starting activity: Intent { cmp=com.mictale.gpsessentials/.compass.CompassActivity }

E/SensorManager( 3332): registerListener 1:MS-3C Magnetic Sensor delay:120

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. giving up...

E/SensorManager( 3332): =======>>>Sensor Thread RUNNING <<<========

E/SensorManager( 3332): registerListener: [email protected]

E/SensorManager( 3332): registerListener 0:SMB380 delay:120

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. retrying...

E/Ms3CSensor( 3567): Ms3CSensor::initialize() failed. giving up...

E/SensorManager( 3332): registerListener: [email protected]

D/dalvikvm( 3332): GC freed 1200 objects / 63336 bytes in 40ms

I/ActivityManager( 2255): Displayed activity com.mictale.gpsessentials/.compass.CompassActivity: 2603 ms (total 4577 ms)

W/PowerManagerService( 2255): Timer 0x7->0x3|0x3

I/PowerManagerService( 2255): ULight 7->3 f0

D/dalvikvm( 2707): GC freed 1085 objects / 49960 bytes in 119ms

the yamaha sensor server is running

logcat has this when booting the machine:

D/SensorManager( 2256): ====>>>>>Num Sensor: 1

D/SensorManager( 2256): found sensor: SMB380, handle=0

D/SensorManager( 2256): ====>>>>>Num Sensor: 2

D/SensorManager( 2256): found sensor: MS-3C Magnetic Sensor, handle=1

D/SensorManager( 2256): ====>>>>>Num Sensor: 3

D/SensorManager( 2256): found sensor: MS-3C Orientation Sensor, handle=2

D/SensorManager( 2256): ====>>>>>Num Sensor: 4

D/SensorManager( 2256): found sensor: gp2a Proximity Sensor, handle=7

D/SensorManager( 2256): ====>>>>>Num Sensor: 0

D/SensorManager( 2256): found sensor: gp2a Light Sensor, handle=4

E/SensorManager( 2256): ####### akmd2 started!!!

using *#0*# the proximity sensor works

then later:

D/NetworkConnectivityListener( 2340): onReceive(): mNetworkInfo=NetworkInfo: type: WIFI[], state: CONNECTED/CONNECTED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true mOtherNetworkInfo = [none] m$

I/LogsProvider( 2466): onAccountsUpdated: Delete SNS log : spType = 0

D/PowerManagerService( 2256): bootCompleted

E/SensorManager( 2256): registerListener 0:SMB380 delay:240

E/Ms3CSensor( 2219): msmachdep_LoadGsOffset failed[-1]

W/Ms3CSensor( 2219): Ms3CSensor::initialize() failed. retrying...

I/LogsProvider( 2466): onAccountsUpdated: Delete SNS log : spType = 1

I can't help but wonder if the sensor calibration tool would fix this if it ran, but i have no idea, what stale "NFS" file it complains about.

so it looks like it should work, but then it just doesn't.

I wiped earlier today then did a nandroid restore when nothing changed after wiping.

If noone has a "dude, you suck googling, follow this [link], it's tell you" i might have to go request Vibrant #3.....

Thanks in advance for looking,

Daniel

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.