Samsung Galaxy Note 3 GPS Issue

I wonder why this page http://m.samsung.com/us/mobile/cell-phones/SM-N900AZKEATT

clearly says AT&T Galaxy Note 3 , and under specs lists the OS as Android 4.4 KitKat

This just changed recently!

Att has forgotten about us and started working on blocking this

http://www.pcmag.com/article2/0,2817,2455011,00.asp

That changed at least 2 or 3 weeks ago.  If you pull up a Samsung chat window the agents will tell you all N900A devices being manufactured right now have 4.4 on them.  If that were true I guarantee you someone would have found one and extracted the contents of the stock ROM and put it on any one of the many Android forums.

So basically its more smoke and mirrors.  Even Bell in Canada, who's N3 is essentially the same as the N900A, is releasing 4.4 this coming week.  When the Canadians get it before US users you know its reached a new low point.

Before you update to KitKat read this and protect your SD card

http://www.androidcentral.com/kitkat-sdcard-changes

I tried the above tactic of turning off " use wireless networks " again while I was on mini roadtrip just little while ago . Wanted to see if anything changed since last time tried it months ago and didn't work then. Not only still not working but it made things worse! My arrow on navigation was flying around everywhere on screen, jumping to nearby streets and going nuts with dropped" GPS signal lost" msg. GPS locked back on twice for like 1 minute went back to trying find a lock . After awhile though  I think my phone had an anxiety attack ...GPS symbol dissapered,  map frozed up,  and it was over for my phone trying to find my location . My phone again let me down, mentally wanted to go back home to rest ,and said F.U . I'm out and find your way home ! AT&T  Galaxy Note 3 ..... There aint no "I" in TEAM and there aint no "WE " either.  🙂

@Eileen89 wrote:

I ran GM app again, plugging it into my car and unplugging it while the App was giving me directions. I had no loss of the White GPS icon at all and the App kept right on working. I've done everything I could to create the GPS issue on my new Note 3 and yet each time it keeps right on working as it should. I'm not going to run anymore tests as it is obvious to me at this point that for what ever reason my Note 3 is not having the GPS issue that others are complaining about. I would love for other new Note owners to post whether or not they are having this same issue but not everyone with an AT&T Note 3 takes the time to visit this site so I doubt that's going to happen. 

---

I've been fighting this as a cyclist using apps like MapmyRide and Strava.  The issue is more pronounced when using these types of tracking apps because you can easily see when tracking is lost due to straight line interpolations on the map.  I rode nearly error free from last spring until last fall, using a Note 1.  I then began having these GPS problems that everyone speaks of and I wrongly assumed the App.  After a couple of months of back-n-forth with the App developer, and reading up on the issues described here and other forums, it's clearly the GPS interaction and not the app.  I am convinced it is not solely the fault of the Note 3 but seems to be the interaction of the device with either GPS or nearby cell towers.  When I upgraded from my Note 1 to Note 3, I expected the problem to go away but it was exactly the same and has been since I got the Note 3 on release day.  Maybe the note 3 is just more sensitive to the issue.  

The kicker is that on some days, with no correleation to weather, trees, etc.. On the same routes where it errored before,  It will run error free.  Sometimes in clear weather, sometimes with thick overcast and it will error in equally bad or good conditions.  My suspicion tells me that it is perhaps, tower congestion or as some stated LTE to 4G switching.  Regardless,  there are multiple reportings of a Note 3 failing in a given region only to stop failing after being rooted.  

Perhaps you, and the people that QC'ed this current version of firmware live in an enviroment,toweres, signal strength, etc.., that is condusive to not reproducing this error, but clearly, there are many of us that have real issues with this.