11-18-2013 8:12 PM
Anyone else having issues with their Note 3 GPS? I'm having an issue were every time I plug or unplug the charger from my phone the GPS drops out. I have to then toggle the GPS on/off in my quick settings to get it working again while navigating. It also seems to drop the signal when I get an incoming phone call while using the navigation app. I have confirmed this same behavior on 2 other friends Note 3's. I'm hoping this is just a software issue that will be fixed in a future os update.
Solved! Go to Solution.
03-25-2014 12:22 AM
I paid full retail price $724.99 plus tax only to find out 5 days after the buyers remorse period that the gps didn't work. Talk about feeling ripped off.
03-25-2014 4:11 AM
The fact that it will work on some days on a previously traveled route which had griss errors before, with seemingly no correlation to weather, time of day.. Or anything else that is apparent.. Really makes me scratch my head
Read through the details in this thread. It's related mainly to the changing of signals from LTE/4G such as when changing towers/coverage areas and inbound calls or emails. You can also get it to drop if you plug it in to a car charger while navigating. Usually for me it's an inbound call or email.
03-25-2014 7:23 AM - edited 03-25-2014 7:26 AM
I understand the theoretical "reported isues", but LTE/4G changeover, /Chargers & all that is simply the observations that other users have made or speculated. No one has actually confirmed the actual issue from AT&T other than "We're working on it" or equivalent... But as I state.. I may travel the same route one day and not drop GPS and have it drop insanely the next over the exact same route on a subsequent day. It may also suggest a tower traffic/congestion issue or a device receiver sensitivity issue. I am usually cycling when I see it most so i am never on a charger so if I am to assume that it is a LTE/4G switching error, I would think that the error would be more repeatable. I have indeed had it error at the same location as it may have before on occasion but then I've had it work like a charm through the same location with no apparent correlation such as weather, temp, time of day, etc.. It may work one day under cloudy skies and misty weather then fail under clear skies the next day or vice versa..
03-25-2014 7:30 AM
WAAAAAAAAA!!! I really hope this is fixed prior to the MS150 on Apr 12-13. This is a 180 mile cycling even from Houston to Austin that I will be participating in to support The Multiple Sclirosis Foundation. It is my first time riding it and I would love to be able to do real time tracking for some friends and family. Please release a fix soon.
03-25-2014 7:44 AM - edited 03-25-2014 7:46 AM
I understand the theoretical "reported isues", but LTE/4G changeover, /Chargers & all that is simply the observations that other users have made or speculated. No one has actually confirmed the actual issue from AT&T other than "We're working on it" or equivalent.
If you're waiting on AT&T to admit there's an issue, that's not going to happen. That would open them up to way too costly of an issue. Not going to happen for many reasons.
If you're als dismissing pretty basic testing and observations then you're selling yourself short. I for one have an exact area that I travel 3 times per week that see's a switch from LTE to 4G so i can 100% confidently show repeatadly that it causes a GPS Drop. If i turn off the cell portion of the phone and leave the GPS on and of course in turn run Sygic or TomTom GPS with locally stored maps, it's just fine and works perfectly...outside when you plug the phone in to charge...which I don't quite understand, but don't care about as I tend to plug it in all the time when in the car and I do so right away.
I also have access to any number of Verizon Note 3's that do NOT exhibit ANY GPS issues under simliar circumstances. I've tested both extensively when traveling with my coworkers. I've also seen AT&T Phones rooted with non AT&T GPS files on them that are 100% fine after the root. Those points noted, I'm confident it's 100% an AT&T Issue.
03-25-2014 8:23 AM
03-25-2014 8:34 AM
Wow. I just chatted with an AT&T tech support rep and he said that they are aware of the issue but he doesn't know when they will fix it. When I complained about safety issues he was like 'well, I'm just relaying the info I've been given.' They were NOT sorry at all about this serious problem. When I finally said that I am leaving AT&T, he said that he hates to see me leaving. Oh well, I guess they don't care at all. Great.
03-25-2014 8:38 AM
If the GPS fix exists and we know that it exists on XDA, why ATT does not implement it on the current Android 4.3 firmware. Why we have to wait for "fix" in KitKat? We do not even know if "att gps fix" will work in the new firmware.
At least now we can root our phones and repair GPS. After upgrade to Android 4.4 this option will not be possible.
03-25-2014 10:32 AM
a. The fix works most of the time but in x number of phones doesn't or even makes it worse.
b. There is something in the file that ATT desperately wants on the phone and is involved in the issue.
c. Replacing the file is an accidental fix, the real problem is elsewhere.
Remember that ATT did send out a small update trying to fix the phone, I imagine they tried tweaking the file and it didn't work.
03-25-2014 11:20 AM
You could still return it. The way things are going, Note 4 will be out before the fix is released anyway.
This is what I did. Even though I wasn't seeing any GPS issues after the first 10 days with the Note 3, I returned to AT&T while I could still get a full refund as I didn't what to keep it and then start having the problems that I've read about too many others having with it, only to be told by AT&T that there is nothing they could do about it. I paid over $700 for it at retail so it wasn't worth it to take a chance on something with as many GPS problems as I heard about it having. I'll stick with my iPhone 5S for now as the GPS on this is always spot on accurate.
03-25-2014 1:16 PM
I have it on good authority that build NC2 passed technical acceptance today and will begin rolling out in one week. Normally I would not bother posting this information on an AT&T forum, but both my wife's Note 3 and my Note 3 are exhibiting this problem and the complete lack of ownership and communication by AT&T has driven me to submit this to hopefully give hope to those on this forum desperate for an answer. The Note 3 is a really great device and it's a shame so many people's experience with it has been marred by such a completely avoidable bug.