Share your experience!
Hello,
I've been using my z3c for two months, without any glitches, with the GPS getting a fix under 20s most of the time, but some time ago, the GPS stopped working.
I am now unable to get a fix in high precision mode.
I've tried the following :
- Factory reset
- Purging assistance data from the service menu
- Removing the sim card
- Using different applications (Waze, Maps, Navigon)
- Clearing and updating A-GPS info (Through "GPS status", and "GPS test"
- Removing the case in hope of a better reception
- Standing outside for extended period of time in order to get a signal
All of the above failed sadly...
The device mode can sometimes get a location, but a very unprecise one (according to "GPS test", I can get a maximum of 3 satellites in use, with a signal to noise ratio that never exceeds 15...).
Build number : 23.0.1.A.5.77
Any input is welcome (the next step will be sending it for repair, but I would prefer to avoid that) !
Thanks in advance
I have the same problem, tried to solve it in the same ways, not solved, I hope in Lollipop, but I begin to lose hopes. In the first month it can fix it so fast...
Hi, I have the same problems. No idea how to fix it, no help from Sony. It's really very frustrating.
Funnily, my GPS stopped working this week aswell 
I am from Hong Kong, got the exact problem as all of you here... I didn't turn on STAMINA mode at all. If I remember correctly, the GPS went crazy after I upgraded the firmware around early Jan... Is there a way I can downgrade the firmware?
Android Lollipop is being rolled out so I'm hoping that my GPS will miraculously come back to life.
It died on Monday with no apparent reason. I tried clearing the cache etc but nothing helps.
I took my z3c to service center yesterday for checking, they said my hardware is fine, reloaded the OS for me, but make no differences... what else can I do?
Mine stopped working over a month ago. I thought it was my fault as I'd dropped my phone pretty badly a few weeks before I noticed this happening. However, seeing as lots of other people are having the same problem, maybe it was not the drop that caused it. Seems like this timing is no coincidence either. The 5.0 update didn't fix it either. Pretty annoying and disappointing.