Join now - be part of our community!

xperia z gyroscope problem

gyroscope
Visitor

xperia z gyroscope problem

Hi.please i need help.since the last update to 4.3 my gyroscope and proximity sensor are not working anymore.so the auto rotation and all games and apps that depends on gyroscope are useless.i have done the repair process on pc companion but still not working.note that there is no protective cover over the prox.sensor.
Tags (1)
38 REPLIES 38
yamen123
Visitor

I had the same problem for months, I did a factory reset and the accelerometer and proximity censor worked! After a day and a bunch of updates it broke again. So once again I did a factory reset And it worked. So now I figured the problem is software and not hardware, therefore it was Some driver or update breaking the censors. One of the things that provided a clue to the whole issue was the proximity sensor (brightness adapt to lighting conditions) was also not functioning. So once I did the third factory reset it put the brightness to maximum and selected the adapt to lighting conditions so I can figure out what update or app was breaking the sensors. Since the proximity sensor was also effected so when I broke the brightness would then jump to Max immediately when the sensors got effected. Then voila what's effecting my problem were a few updates and an app. One of them was os monitor and the other was a Google update. So now you know what's breaking your sensor and avoid it or disable it. There is no easy answer but that would help you figure it out.
Dr. Yamen.
Tareq1
Visitor

My Gyroscope was working well last week and now it isn't, what I just did is i turned it off for a few minutes and put it in clean water (since last week I was at the beach and it got some salty water on it) anyway when I turned it on and did the Test again it worked! probably it's just turning the phone off for a few minutes fixed the issue, try it Slightly_smiling_Face good luck 

Ebie
Visitor

Hi, I have done a soft reset hard reset and nothing seems to work, the problem still persists, even tried disabling apps that i have downloaded and upgraded but the problems still persists. I have now decided to send my device in for repairs and have to wait three weeks for my device. Does anyone know what else could cuase this problem or how to prevent it.

torontokid
Visitor

hello

i was wondering if you were able to solve your problem ? beacuause i have the same issue and its killing me

Ebie
Visitor

@torontokid, hi, after trying all of the suggestions everyone helped with, i had to send my phone in for repairs, twice they replaced my device and so far i domt have any problems.
torontokid
Visitor

thanks you for your reply yea i guess i wiill have to send mine in too how long did it take them to send it back ? and why did u have to send it in twice ?

thanks alot for the help 

Ebie
Visitor

Hey torontokid, no probs, the guys here also helped me quite a bit, happy to do the same. At first they did a software update and replaced ambient sensor, but that did not solve my problem, so i had to send it back, on both repairs i waited for three weeks before i got my device back. But my device is good now and i am enjoying it once again.
torontokid
Visitor

thank you very much for taking the time to respond i will probably be sending mine in Thanks again Slightly_smiling_Face 

ThaSoulz
Visitor

Hi there. The problem occured to me a couple of days ago on Z1, I restarted my phone and it works now. I'll update if problem returns but I suggest anyone who encounters the problem tries that first.

XDarkMario
Visitor

wow still now official answer on this pressing matter? my xperia Z1 is also has this issue for the longest. my phone was fine before i updated to android 5.0 LP. the issue never existed on kitkat. rebooting the phone is the only temporary fix for the issue (for about 30 min-2 hr), then after regular use the issue would return. then it happens all sensors go down.

gyroscope down

compass down

light sensor down

proximity sensor down

downgrading back to KK makes the issue take longer to affect but is still there.

leaves me to think its a Firmware kernel issue.