Share your experience!
Hey there.
It's working perfectly fine on my phone running 4.3
Lol you put your username as gyroscope. Ok do this to check if your sensor is normal or not.
Download this app https://play.google.com/store/apps/details?id=com.sonymobile.androidapp.functiontester and test all the sensors using it.
Or you can try it like this > dial *#*#7378423#*#* in phonepad/ dialpad > service tests > gyroscope > see if the values change if you shake your phone.
eljay Try a software repair to see if that helps you with the problem
Backup everything as it will erase all data on phone (sms, contacts,apps)
Update/Repair your phone via SUS
SUS ( Sony Update Service) ... download and install it on pc and follow the on-screen instructions
http://www.sonymobile.com/global-en/tools/update-service/
Yes its happening in 101 only. so its not software issue. As i triedthe same in previous version.i didnt had that problem. to test . just use photosphere app from google. check if you can align to it accordingly
Okay - it's a little late for me to join the party - however - "me too"!!
I've googled and better googled this, and found that there are similar problems with other Android devices (Nexus 7 particularly) - but thought I must be the only one with this issue on my trusty Xperia Z.
HOWEVER
Mine won't even calibrate!!
Gyroscope calibration - "FAILED! Please retry with following a product instruction - Error code = -1"
Accel calibration - "FAILED! Please retry with following a product instruction - Error code = -1"
Proximity calibration - FAILED! Please retry or your phone may not support this function - Error code = -98"
Further info - worked fine on the latest firmware - 10.4.1.B.0.101 for a few months - decided to wipe and re-install as phone was running sluggish (due to amount of installed junk!!) - after the re-install, this is what I get.
Other sensor apps say "waiting for device" on the sensors.
So - having previously run custom ROMs on other devices, decided to have a look at the system logs.
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable accel
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable gyro
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable compass
A whole bunch of:
E/Sensors ( 851): HAL: ERR open file " " to read with error 2 (I added the quotes here for ease of reading)
E/Sensors ( 851): HAL:ERR can't read chip_enable
and....
E/Sensors ( 774): HAL:unknown compass id ©@@ÉÄDr@/─p☻ -- params default to ak8975 and might be wrong.
(this is just using USB debugging, and looking at logcat)
Re-installation of firmware has NOT fixed the issue, and the device will NOT re-calibrate. From the research I've done, and from the info I've read - it's because a small part of the filesystem (which is used to reference the sensors) is now corrupted - so it doesn't know what the sensors (or WHERE the sensors) are at.
So what IS wrong? How do we fix? With full access to the filesystem (i.e. root) I'm confident it'd be doable, but my linux knowledge lies more with basic admin than something like this!
Can I also please urge anyone with this, or who has previously had this, to comment, or at least 'me too' the post? I suspect it's probably wider-spread than we'd think...
Last week, all my sensors were still working, but this week, possibly after an update to Android 4.4.4, my gyroscope and proximity sensor are not working on my Sony Xperia Z1 Compact.
I dialed *#*#7378423#*#* and went to the Gyroscope service test, the one with the green cube. There I can confirm that my gyroscope is not working, everthing stays zero. However, I do not see any 'calibrate' button. Am I looking in the right menu? How can I recalibrate my gyroscope?
after updating the phone to jelly bean last time the gyro, accelerometer, compass all have stopped working. i have downloaded the function tester. And NO it still does not work.
Went into the service menu to test. Did NOt work also.
tried backup and factory reset via PC Companion. Still NO GO.
Updated to the new Kit Kat. STILL NO GO. FYI NO GO means the gyroscope, accellerometer and compass is not working after applying fix. All this happened during my phone is still withing the warranty period. Although I did report the issue in March 25 2014. i have a service request number 1-1151375485. honestly there have been several cases in which your support team is still unable to provide a fix in relation to this issue.
==================================================
Here is one of the link and the details given prior to the issue is well put. Such a shame to SONY.
/t5/Xperia-Z-ZL-ZR/xperia-z-gyroscope-problem/td-p/559629.
HERE IS THE ISSUE COPIED FROM THE USER's WRITINGS:
Re: xperia z gyroscope problem
Options
May
Okay - it's a little late for me to join the party - however - "me too"!!
I've googled and better googled this, and found that there are similar problems with other Android devices (Nexus 7 particularly) - but thought I must be the only one with this issue on my trusty Xperia Z.
HOWEVER
Mine won't even calibrate!!
Gyroscope calibration - "FAILED! Please retry with following a product instruction - Error code = -1"
Accel calibration - "FAILED! Please retry with following a product instruction - Error code = -1"
Proximity calibration - FAILED! Please retry or your phone may not support this function - Error code = -98"
Further info - worked fine on the latest firmware - 10.4.1.B.0.101 for a few months - decided to wipe and re-install as phone was running sluggish (due to amount of installed junk!!) - after the re-install, this is what I get.
Other sensor apps say "waiting for device" on the sensors.
So - having previously run custom ROMs on other devices, decided to have a look at the system logs.
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable accel
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable gyro
E/cal_data_manager(27964): Self-Test:ERR-Failed to enable compass
A whole bunch of:
E/Sensors ( 851): HAL: ERR open file " " to read with error 2 (I added the quotes here for ease of reading)
E/Sensors ( 851): HAL:ERR can't read chip_enable
and....
E/Sensors ( 774): HAL:unknown compass id ©@@ÉÄDr@/─p☻ -- params default to ak8975 and might be wrong.
(this is just using USB debugging, and looking at logcat)
Re-installation of firmware has NOT fixed the issue, and the device will NOT re-calibrate. From the research I've done, and from the info I've read - it's because a small part of the filesystem (which is used to reference the sensors) is now corrupted - so it doesn't know what the sensors (or WHERE the sensors) are at.
So what IS wrong? How do we fix? With full access to the filesystem (i.e. root) I'm confident it'd be doable, but my linux knowledge lies more with basic admin than something like this!
Can I also please urge anyone with this, or who has previously had this, to comment, or at least 'me too' the post? I suspect it's probably wider-spread than we'd think...
===================================================
My problem is exactly the same. unless SONY provides an explanation or a fix. I have to say. I will do everything in my power to influence people around me (to say the very least) that your product is no good. I mean if we have access to Google then its not a problem to convince people. All the phones problems is being addressed online and most of the fix is provided NOT by your technicians. And I am very dissatisfied with your customer service. Such bad service. Left me hanging because i could not get my phone fix within the warranty period.
This specific phone problem has never been addressed and rectified properly. NOT even your support staff can provide a solution via an internet fix. you can Google it. I mean the 3 main sensor (gyroscope,accelerometer, compass) defect issue is well known and you did not even try to have a fix for it? So yes. I hope that having me wasting my precious time writing this heart-aching dissatisfaction for purchasing the SONY XPERIA Z phone MAC 2013 with an issue that no solution is provided will produce a much better brain fart for you guys to have a fix for me and other people with good customer service. I mean. I will post this on every android community forum with print screen. SO yes. Please adhere to our request. Addressing it as it was your CEO's personal phone and rectifying it if not you should come up with a better solution. So **bleep** YOU SONY FOR MAKING MY LIFE MISERABLE. I have copied this complaint and will definitely post this on android community forum.
Sincerely,
Mokhzane Mohamed Ramly
I mentioned two weeks ago that I experienced the same problems, but when I a few days later tried it again, it worked out of the blue. I am not sure if another software upgrade had occurred in the meantime, but I didn't do anything manual. Strange business... In any case, it seems to be software-related.