07-22-2012 02:40 PM - last edited on 07-22-2012 05:14 PM by coreno
hi. i have 9780. my phone version 184.108.40.2068. i open options>device>location settings>refresh location = locacion update failed. what can i do?
[personal information removed]
08-03-2012 02:29 PM
Welcome to the BlackBerry Support Community.
The following article will provide you with more information on the issue you are experiencing with location services on your BlackBerry® Bold™ 9780 smartphone:
How to troubleshoot built-in GPS issues on a BlackBerry smartphone - http://www.blackberry.com/btsc/KB11950
We hope this helps.
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Click "Accept as a Solution" for posts that have solved your issue(s)!
08-26-2012 11:23 PM
In case the subject line didn't explain enough...here.....
I had a 8900 and was happy but it used to freeze up....so Tmobile did warranty replacement and sent us (wife and me) 2 new phones. 9780's. Nice but GPS never worked....unless you do a battery pull and restart. Then it might find your location about 5 times....and then it goes out. It gives a general location(from cell tower) with the 3.2 kilometer radius....hahhahahahah like that **bleep** helps!
Wife's phone got white screen that would not go away, took it in and they ordered her a new 9780, new one's GPS does the same thing. I took mine in to Tmobile after getting really pissed the other day driving out of town and having to restart phone(battery pull) while looking for the place I was going to. They sent me another 9780 and guess what? SAME!
Dude, I called RIM's 800 line and this lady pretty much gave me the finger over the phone....told me I could pay $49 to get Tmobile's tech support guy to help me....hahhahaha
ended up transfering the call and guy on Tmobile tech support asked the same questions: Is the GPS on? have you tried updating the phone's software from the phone? Have you updated the phone using desktop software?
And last but not least my favorite: Have you tried doing a hard reset?
Guys, time to accept some responsibility here and tell people no fix for this bug has been developed!
I've read posts about this very issue from 2011 and 2012. this is ridiculous.