Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
I have the same issue.
pub00515 said:
Hi,
I'm a proud S2 owner but I'm note sure for how long. It seems the gyro in my device is very unstable. For example, if I use Google Maps and I turn on the sensor, the map will rotate if I only the tilt the device upwards (and this shouldn't cause a map rotation).
I've also tested some other apps using the gyro (STLView by ModuleWorks https://market.android.com/details?id=moduleWorks.STLView or some artificial horizon apps) and they all share this instability.
I have an EEE-Pad as well, and there those apps are really great.
So the question really is, is it just my device or can anyone else reproduce these issues?
Thanks,
Mark
Click to expand...
Click to collapse
I tested it on my sgs2 with maps and I don't seem to have the issues that you are experiencing. I even downloaded STLView and did not have this "instability" problem. Perhaps your handset is faulty?
Another possible reason is that you might have been trying to use your sgs2 in the bermuda triangle. It has been documented that the bermuda triangle wrecks havoc on electronics.
Are you sure maps use gyro ? I guess they use primarily compass and G-sensor, while of course, gyros can help too.
Did you try to calibrate the gyro sensor?
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
pub00515 said:
Yupp, tried calibration, didn't help.
@info5i2002
Pretty far from bermuda
In STLView, did you enable the gyro button (the button on the left side)? What happens if you tilt the phone by 90° (hold it over your head facing towards you) - does the heading swing around?
When I hold the phone level (in landscape orientation), and I tilt the phone up and down, I can clearly see the axis swing from left to right.
Click to expand...
Click to collapse
Yeap, tried it in landscape and tilted it up and down and it seems to move only up and down only.
If the device is in a case/cover which has Magnetic Lock then the issue is normal.
issue is NOT gyro related, what's described here is unstable accelerometer and/or compass readout. i guess it's mainly due to missing magnetic calibration (try to do the "8" pattern with the phone, AND turn the phone twice around each axis). if the problem persists, than it's maybe within technological limits (and everyone faces it, although the people here are more upset about it). also possible is magnetic interference due to huge amounts metal etc...
Yes .. people often confuse accelerometer (G-sensor), electronic gyroscopes, and compass. All do different things, but all can be used in applications like maps.
I also noticed that the magnetometer of my s2 is kind of imprecise.
I have continuously swinging head indication, of about +/- 15 degrees. Moreover, the correspondance from phone orientation and indication is not linear. I get higher sensitivity towards one direction and lower towards the opposite direction...
However what I did notice, is that the magnetometer, responsible for the compass, is very sensitive not only to nearby magnets, but even to metal objects at considerable distance. So perhaps it is all just this sensor beind a tad too sensitive.
Sent from my GT-I9100 using XDA App
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Yes, there definitely must be something wrong with the gyro and/or the magnetometer.
Some time ago I opened a specific thread on this subject in this forum, got many "reads" but no replies whatsoever...
So strange nobody did actually notice it so far.
pub00515 said:
Hi,
I've done a few more tests - I placed a strong magnet next to my Eee-pad and I had no deflection when I moved the magnet. So in this case, the app is correctly using the device's gyro and accelerometer. I then performed te same test with my S2 and bingo, I had a strong deflection as I moved the magnet. This is plain silly, as the sensor I'm using in my own app doesn't rely on the compass, instead it relies on the rotation vector sensor as provided by the SDK. Now the question is, who was sloppy? Does Gingerbread perhaps not support the gyro fully or did Samsung not implement the sensor correctly? As I wrote, the same code works perfectly on my Honeycomb tablet so it's not a programming error per se.
Regards
Mark
Click to expand...
Click to collapse
Now that's interesting. Could be !
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Btw. it's common that that electronic compasses are much more sensitive to metal objects, that's not Samsung's mistake. But the sensors should not be linked.
Edit: I downloaded some sensors monitoring application. And gyroscopic sensor itself for sure is not sensitive to magnetic fields and works as it should, same for accelerometer. But then there are some IMHO virtual sensors: linear acceleration and rotation. They seem to be synthesized from more sensors, and the rotation does react on magnet.
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Dr.Sid said:
My compass works a bit weird. I put it on table, let it show the north. Then I rotate the device 180 degrees .. and the north shifts like 5 degrees. It can be worse, but calibrating (waving the 8 pattern) helps .. but I can't get the error under 5 degrees no matter what.
Click to expand...
Click to collapse
Mine does the same. Actually I can get even 15 degrees deviation. I noticed that it seems to depend on the location I am, despite apparently there should be no magnetic objects nearby. I am pretty sure that if if you try rotaring your phone at constant angular speed in the horizontal plane (with it horizontal on a table for instance) with a "compass" app running you will notice that the indicaton on the screen speeds up considerably when the phone is pointing to the north, and slows down when is pointing to the south.
Which Gingerbread version are you guys running?
I'm still waiting for the 2.3.4 update.
It would be interesting if someone could try this with 2.3.4, perhaps it works with the update?
Thanks...
Mark
pub00515 said:
So perhaps if someone has a different phone running Gingerbread with a gyro on board, we can see if the issue exists there as well (best would be to try it with STLView, as I know what API calls are made)
Thanks,
Mark
Click to expand...
Click to collapse
hi mark,
again, what you (we) experience here has nothing, i repeat nothing, to do with the GYRO. what you mean is the accelero- and magnetometer! a gyro knows nothing about it's current position (it only detects deviations, read about a coriolis vibratory gyro for more details about the mems gyro the sgs2 is using)
most programs i know are not using the gyro for positional information, for example google maps, google sky... they are all using the magnetometer in combination with the accelerometer ONLY!
regards,
markus
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
pub00515 said:
Hi Markus,
thanks for the heads-up, but I think I have a pretty good idea of what's going on:
Why?
Well, for starters, I'm a software developer in a technical field and I'm also the author of STLView mentioned above. Secondly, the same app running under Honeycomb with an Asus EeePad is working perfectly, and it is using the gyro there. Yes gyro and no, not magnetometer.
The problem with the S2 as I see it, is:
either Gingerbread or Samsung have failed to implement the rotation_vector sensor, as provided by the official API, correctly. On the S2, it is using the acceleration sensor combined with the magnetometer, which is just plain silly, as the magnetometer is too unstable for correct rotation rate measurement. On the EeePad, the same virtual sensor is using the accelerometer and the gyro in combination (gyro for rotation rate and the accelerometer to eliminate gyro drift). What you get is a very accurate sensor reading, which is just not possible on the S2 as of now.
Hopefully, either Samsung or Google are going to fix this flaw, but I think the problem is more on Samsung's side as they are the ones who actually know what physical sensors are available. That's also why it would be interesting to find out if other devices running Gingerbread that have a gyro on board are also experiencing the same problems.
By the way, I'm also a pilot so I think I have a pretty good understanding of what a gyro is and what it measures, thank you very much. Next time, remember: "Halbwissen ist gefährlich"
Regards
Mark
Click to expand...
Click to collapse
hi mark,
sorry - i didn't meant to be rude...
nor did i know your background; the thing nowadays is, a hell lot of people are talking technical nonsense all the time, which is quite frustrating...
i have to admit as i'm no software developer i didn't know the thing with the rotation_vector, what's sure for me was that the actual situation is caused from the accel/mag sensor, simply because of its behavior. that it would be way better to use the gyro as well for all this applications is absolutely true.
so let's hope either samsung or google will provide a fix, as you said!
glück ab, gut land!
markus
Hello.
I have thought that Le Pro 3 has a hall sensor. If it does. Mine is not working. I have x720 phone. with 19s version. I don't think is original. It has Google Store and not a single chinese sign or bloatware. I think is a vendor rom.
I tried with a lot of magnets and and there is no hall sensor. I ordered a flip case that was supposed to work with that sensor and open/close phone when you open the cover.
I checked the Accessibility/hall sensor option to On but nothing works.
Did anyone checked his phone for hall sensor?
Thanks
Lastest for x720 is 18s...
Mine eui version is 5.8.019s (Stable)
I testet on my device and there is a Hall sensor and its working well.
I am on the s18 on x720
You have test it with a magnet?
I don't know if mine is not working hardware or maybe is the vendor ROM to blame.
I have installed Sensor Test and at the magnetic field it says uncalibrated. I don't know how to fix it
When I aproach a magnet to the phone in sensor test it detect it and it show it works. So I think is the software to blame.
I tried again with cydras rom. And somehow it works sometime. When I try with a magnet, close to the buttons it works but only sometimes. Not allways.
I received the original flip cover and it works. It must have a special magnet or something.
The phone works and close screen when I flip it.
hi guys, did anyone have a problem with your sensor??? via test * # 0 * # (sensors) Inside the test area all sensors are apparently off , iris sensor, light sensor, proximity sensor, heart rate sensor, magnetic sensor, accelerometer sensor and barometer. all the numbers are 0. and I do think the sensor is not broken,but they do not work. My phone is G950FD,
and after updating (about half years ago) all the sensors are borken, what can i do.
Hey, I have the same phone SM-G900FD and my sensors are dead... all of them. It happened a year ago (give or take). One morning I turned it on and first the screen rotation and then every other sensor went dead. I couldn't fix it... My service man said that it was due to the bent motherboard on my phone, but I doubt it since I didn't bent it at all and many other people have the same issue with their S8 plus like you. We now have bootloader U3 and we can't downgrade it to Nougat from Oreo (many have said that this solves the issue). I don't know, you'll just have to live with it like me, 'till you buy a new phone...