Hi all,
Just wanted to share my experience with my recently bought Samsung Galaxy SIII. As it turns out, my GSIII was kind of DOA. As soon as it arrived and I tried it, I realized there was something wrong with the gyroscope. Whenever I was looking at a photo, it would flip back and forth between portrait and landscape.
I didn't pay much attention to this and flashed the latest official JellyBean. All was well until I actually wanted to use the gyroscope and realized it simply wasn't working at all. I tried recalibrating to no luck, went back to ICS also with no luck, and using the service menu (*#0*#) gave me very strange values for the gyro sensor.
Today I brought the phone in to an official Samsung repair shop and after trying the same as me, they took it in for RMA. Not sure if anyone else's had the same (trust me, I searched the hell out of the Internet) but just wanted to share in case other people experience the same. Ultimately, *#0*# is your friend in these circumstances.
Cheers,
Espinha
I have problem about the gyroscope too but not that bad as you have. when I re-calibrate it it will not re-calibrate. I tried some apps and through settings > display > gyroscope I can't set it to other angle than default.
I didn't mind this problem for this wasn't causing me trouble about the rotation of the phone.
bordikun said:
I have problem about the gyroscope too but not that bad as you have. when I re-calibrate it it will not re-calibrate. I tried some apps and through settings > display > gyroscope I can't set it to other angle than default.
I didn't mind this problem for this wasn't causing me trouble about the rotation of the phone.
Click to expand...
Click to collapse
Have you tried to go to *#0*# and have a look at the sensors page? Seems like one of your axis might be stuck... if it is, I would definitely get it in for repair.
That command gives me "connection problem or invalid MMI code". I don't really need repairs because the sensors work, it rotates when i turn the phone horizontally. It works for games that need sensors.
Just that I can't "re-calibrate" it.
Related
I tried doing this http://forum.xda-developers.com/showthread.php?t=793441
and my results came up fgets: Unknown Error: 0
msmachdep_SaveGsOffset: failed
Calibration Utilities: failed
Anyone know what all that means lol
Is your horizontal calibration working? If not you have a hardware problem and will probably have to send your phone back to samsung.
^ if I play a game it will go into landscape mode if that is what you are talking about
Try going to settings> display> horizontal calibration. Put your phone on a flat surface and hit calibrate. After it calibrates the ball should stay in the center of the screen. Try that and tell me what happens.
It says that it's calibrated after I calibrate it
The ball doesn't snap to one side after it calibrates? It stays dead center on the screen?
No it just stay dead center the whole time
What exactly is your phone doing that makes you think the accelerometer isn't working. Give as much detail as possible.
I can't go into landscape mode when I look at pictures in my gallery, using the browser, my homescree (using LPP), and I tried taking a screen shot using shootme and it wouldn't recongnize that I was shaking it
This might seem like a stupid question but I have to ask it. In your display settings do you have "Auto rotate screen" checked?
Yeah I made sure it was checked before I tested it
Well I'm stumped. My last suggestion is to try and flash a different ROM and see if that solves the problem. If it doesn't then you may indeed have a hardware issue.
Appreciate the advice, I was thinking about just reflashing the updated version or Axura to see if that worked too
That will work too. Good luck!
I should also mention I have dropped my phone a few times (it fell out of my coat pocket no more then 3 ft.) I have a TPU case and the phone hasn't taken and physical damage, but could the drops throw off the accelerometer?
Sent from my Gangsta Vibrant using XDA App
Dropping your phone can definitely damage the accelerometer but if it's calibrating properly it sounds like an issue with your software and not the hardware itself.
I think it was just a maybe a bad flash or something because I reflashed the same version of Axura and its's working like a charm now
Awesome! Glad to hear you got everything fixed.
Hi there, I have a problem with my S2. It was all fine and dandy (even after several bumps) until last week I dropped it and the screen died. I have had the screen replaced and found that now none of the motion sensors work. I've tried the *#0*# test which sometimes says the gyro passes and sometimes fails. It says the magnetic sensor needs calibration. Is there any way of telling if I've fried the hardware? I have factory reset the phone with no joy.
I have the same problem, I think it's a hardware issue.
I will get mine today to be checked, to be sure.
Great thanks.
Hey, I promised I keep you up to date.
I went to a Samsung service center and it was to expensive just to check for problems, let alone fix them.
And a few days later I restarted the phone and the accelerometer and magnetic sensors were functional again, after a quick calibration everything was fixed for me.
Hope you fix your phone.
Try it to calibrate with GPS ESSENTIALS it's a free app and you find in YouTube videos how to calibrate.
Sent from my GT-I9100 using xda app-developers app
Hi,
My gx2 was running cm10 and everything was working fine up until recently when my lcd screen broke.
So I ordered a new one and replaced the broken one, the repair has gone well , also the screen was good. Except there was a problem with the proximity sensor, when i tried to make a call the screen would go black and not switch on again, the only thing I could do was to take out the battery.
So I thought maybe I damaged the proximity sensor somehow while replacing the screen, so I bought a new sensor. The same Problem.
So I thought maybe it was firmware related even though I did not change the firmware and before the screen broke everything was working fine.
I flashed a stock rom, again everything went well , phone was working except the same problem with the proximity sensor.
Anyone know what that could be? Could I have damaged the motherboard somehow, even if that is unlikely because I was always extra careful and patient.
zsajak said:
Hi,
My gx2 was running cm10 and everything was working fine up until recently when my lcd screen broke.
So I ordered a new one and replaced the broken one, the repair has gone well , also the screen was good. Except there was a problem with the proximity sensor, when i tried to make a call the screen would go black and not switch on again, the only thing I could do was to take out the battery.
So I thought maybe I damaged the proximity sensor somehow while replacing the screen, so I bought a new sensor. The same Problem.
So I thought maybe it was firmware related even though I did not change the firmware and before the screen broke everything was working fine.
I flashed a stock rom, again everything went well , phone was working except the same problem with the proximity sensor.
Anyone know what that could be? Could I have damaged the motherboard somehow, even if that is unlikely because I was always extra careful and patient.
Click to expand...
Click to collapse
1. You should check if the sensor is really damaged. You can use e.g. Android Sensors app from Play store.
2. If it is broken, then try to disable it in ROM settings. I think there is at least an option in phone/dialer settings.
Maybe that can help.
Good luck !
It_ler said:
1. You should check if the sensor is really damaged. You can use e.g. Android Sensors app from Play store.
2. If it is broken, then try to disable it in ROM settings. I think there is at least an option in phone/dialer settings.
Maybe that can help.
Good luck !
Click to expand...
Click to collapse
I know how to disable the sensor, when I disable it calling works, but I want the sensor working . The thing is I thought I damaged it while replacing the screen, so I bought a new sensor, but the problem is still there.
android sensor box shows me a value of 0,0
typing in *#0*# and then "sensors" : the screen is always green an the phone is vibrating PROXIMITY: 13
the phonetester app shows Proximity sensor :near
I just figured something out.
The proximity sensor works when I hold the phone against a light source, when i do the *#0*# test and hold it against the light, the screen turns to white and the sensor works as it should( when i hold my hand near it, screen switches green and phone vibrates) , but only as long as it is near the light source.
Could the sensor just not be calibrated correctly? Is there a way to calibrate it?
than you
Hi everyone,
I am experiencing funny accelerometer issue with autorotation ON.
When I keep my phone straight it flips screen to the left. When I rotate the phone it flips again. Only the home screen works good.
The same is with the games - if I am playing every thing goes to the left because it thinks that the phone is flipped.
I do not know if this could be the issu with the spirit rom but on CM11 there is the same issue and with this rom's there are no calibration tools.
It looks like the start position for the accelerometer is flipped left.
When I test accelerometer with moving the phone up and down it looks like working left and right like the axies being changed.
Do you have any ideas, how could I approach this issue to fix it?
It is just not possible to use autorotation now.
Best regards to you all.
Have the same problem
Yea, it depends on which ROM you installed. Some work some don't. Been looking around, but not much activity for MEGA. Looks like everybody is loosing interest for this phone. I just got mine and love it, have the same problem with screen and camera. Has to do with what it thinks north is.
Hey xda-community,
i've registered, because i have a strange problem with my LG G5 (H850) European Edition. If this is of any use, it's the Vodafone-Edition. Sorry for my language, i'm not a native speaker .
I got my G5 yesterday and was really pleased with the build quality (i was afraid, i was about the get some of those flawed devices as seen on the internet) and the raw power of the whole package. At first i didn't notice but then i realized, that the automatic brightness didn't work. Then i noticed, while having a conversation, that the display was'nt turned down. Up to this point it sounds like the known bug.
What i think (and please, push me into the right direction if i'm wrong - i'd love to take the shame not beeing able to look properly) makes the difference is, that after installing several sensor test apps from playstore, i always got the information, that both sensors are missing.
I took a trip into service menu and tried to calibrate (or better so say, to see if there was any sign of them) those sensors, but nothing happened. No reaction while covering the area where they are supposed to be, nothing.
Firmware is v10c-262-02. Tried to reset the phone and check while having nothing installed - same problem. I tried safe mode - same problem. I can check autobrightness but it doesn't have any effect whatsoever.
What really makes me shake my head is, that when i'm called and i turn the the display downwards to stop the sound, it works after 2 up to 3 times trying to cover the display.
I'd hate to send it in - maybe i'm just too stupid to look for answers, i'd really appreciate any efforts to help.
Thanks in advance and have a nice day.
Nero
Hey there,
short follow up to the problem. Yesterday evening i got a notification about an firmware update and wanted to install it. After hitting the proceed button nothing happened. Nothing. No installation, nada. I shook my head, deceided to return the damn brick and forgot about it. After an hour i noticed that my soft keys had changed their appearance. They got smaller. I asumed a kind of silent update (? nothing is shocking me anymore concerning this phone), checked the brightness control - no change. An hour ago i wanted to unlock my phone and got no reaction. I was about to hard reset it when it unlocked. I scrolled down the notification bar to check something when i noticed that the brightness was different from my setting. I hit the auto brightness button and bazinga. It changed by itself and since then everything works like a charme. The firmware version hasn't changed. I don't have the knowledge to explain anything or to know if something like this is even possibe (something was definitly new because all those vodafone apps where there again - which i deinstalled yesterday). Okay, long story short - either i'm officially going insane or they fixed it. Don't know, don't care.
Have a nice weekend!
Update: And it's gone again. I have no idea what to do anymore. I don't know if anyone is interessted in this, but i share the info anyway...
With Sensors (Umgebungslichtstärkesensor = Ambient light sensor, Näherungssensor = Proximity Sensor)
fs5.directupload.net/images/160508/459jqzhk.png
Without Sensors
fs5.directupload.net/images/160508/wiazcglk.png
nero
It certainly sounds like it *might* be defective, as you say that you have tried a factory reset.
It is a strange problem you have as it only appears to happen occasionally. It also sounds quite annoying. I know it is a pain to have t return it, but it might be better to do that and have a fully functional device, than to keep on facing this problem.
Sorry not to be able to give you a more satisfactory solution.
Good luck.
nobnut said:
Good luck.
Click to expand...
Click to collapse
Hello,
thank your very much for your reply. I agree, i think it'll be the only option i have. I'll try to do return it, it's quite easy in Germany but, nevertheless, connected to some time without a phone.
Have a nice sunday,
Nero
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
jrhlaser said:
I have this same issue with the proximity sensor and in my case it is because of the Lifeproof case is causing this, many others with this case report the same thing. Try taking out of the case and test again - mine works fine with no case; If this still happens, with no case on, then maybe the phone
Click to expand...
Click to collapse
Thank you for trying to help Sensor was damaged, send it in for repair and got it back. One can be sure that it's not a matter of blocked access to the sensors when a sensor test shows, that there are no sensors.
Told about this in so many forums that i forgot to tighten the loose ends. Sorry.
Kind regards