GPS Problems on Nexus 7 (2013)

I wonder why there are so few people getting on this forum about the gps....yes yes, I know it's one of the more active ones, but I would have expected more people to post. People are just not using the gps much yet?
 
I would say that most people don't use the GPS function, especially for an extended period of time. I bet most usage would come from apps getting the location and stopping, not the GPS apps.

I have tethered by Bluetooth everytime I tested the GPS, but today I am going to try connecting via a WiFi hotspot and see if it does the same thing. Doubtful, but we will see.
 
I have seen the gps stop also. Using the "gps test" app, I have seen it happen many times. Usually between 3 to 10 minutes. The tablet then needs to be rebooted to fix it.
 
Well, it seems like a out source service phone line. I need to find a way to talk to the original technical support team. It does not look like a system problem but a hardware problem, since it works fine at the beginning and crashed later. Just like some internet router, which work very well after reboot. Data overload problem? I am just guessing.

Thats a big problem with Google, its seems impossible to contact them. Just like youtube, they give zero ability to contact them. I would bet heavily that their "support" number is just some call center that isn't even connected to google. Probably in another country. They are never any help.
 
I called the google support department.

Their answer is:
GPS must work with Wi-fi, and other funtions. It will not work just by itself for a long period of time.
They suggest me to reset to factory setting.

I mean when I use GPS, I am properly out of Wi-fi environment. Do you agree? Then how can I make GPS to work with Wi-fi while I am on the way since not everyone having 3G cellphone?
I don't really care what outsourced support has to say.

The GPS won't lock after a while problem happens with WiFi turned on.

It is extremely likely if you fix that, GPS will work irrespective of WiFi being on or off. That's how it works with other Android devices.

I remember the Palm Pre GPS nightmare. There you were dealing with a company on its last legs and GPS apps weren't so prevalent back then.

Here you are dealing with the flagship device from a huge company that is pushing mobile services for expansion of their ad service revenue. They need to get GPS working for their own services. 3rd-party apps will just come along for the ride and get support automatically when the Google fixes it for their own apps.

As an aside, someone suggested using a Bluetooth GPS dongle so I broke out my old keychain GPS from windows mobile days. It works great with mock locations and I don't have to see that silly blinking GPS circle anymore. Will use this until Google fixes the problem. I'm pretty confident the GPS on the unit works fine as I can control conditions to have the internal GPS work for long periods of time. This is extremely likely a software issue.
 
I updated (via Google play) to the latest version of play and cleared cash / data. With WiFi connected through my Nexus 4 and WiFi scanning turned off I was able to navigate for 4 hours yesterday with no trouble from the GPS and one map crash which is an improvement from where it was. The maps do not allow navigation without an internet connection and the idea behind this device was to replace our aging Garmin with a more useful device which I am hoping this is.
 
Thats a big problem with Google, its seems impossible to contact them. Just like youtube, they give zero ability to contact them. I would bet heavily that their "support" number is just some call center that isn't even connected to google. Probably in another country. They are never any help.

One of the reasons why some people haven't jumped from Apple to Android. Even though my iOS products are locked down, I'm able to contact someone as long as my Apple Care is up to date.
As for my Android products, I usually hit up forums looking for an answer.
Samsung and HTC do a pretty good job of allowing you to contact them.
If you want a device with pure Android, then not so much.

Sent from my SCH-I605 using Tapatalk 2
 
Has anyone rooted their device? If so, would you be able to drop to terminal, SU, and snag a logcat log of the GPS starting up, running, then dropping out? I think digging into this problem at the core of Android would provide some insight as to what's going on.
 
One of the reasons why some people haven't jumped from Apple to Android. Even though my iOS products are locked down, I'm able to contact someone as long as my Apple Care is up to date.
Being able to contact someone and being able to get a resolution are not necessarily the same thing.

It is nice that someone answered the phone when people complained about Apple maps, but did they resolve the issue?

Personally I don't particularly care what avenue I need to take to get a solution as long as there is a solution.

Sometimes it is quicker to talk to someone and sometimes it is faster to find your own solution.

The worst is when you know that something is wrong and the company refuses to do anything about it.
 
I think your mainly right, however the GPS function IS working with most apps, because most apps only access it for a few seconds at best. So most of the apps that Google makes ad revenue from are already working correctly.

A part of me wonders if the code they used to make the forthcoming LTE model work with Verizon is also in the WIFI only version. The reason I find this interesting is it turned out that the Palm Pre's GPS issues revolved around code that was inserted to make Verizon happy (they wanted customers to pay for their Navigator service). A long shot I know, but never forget your history I say...!:p
 
I think your mainly right, however the GPS function IS working with most apps, because most apps only access it for a few seconds at best. So most of the apps that Google makes ad revenue from are already working correctly.
This isn't a 3rd-party GPS app problem. It happens with just stock Google apps on a bone stock rom with no other GPS apps loaded.

There are 2 ways you can get GPS more stable

1) limit yourself to only 1 GPS app, Google Maps (don't use navigation, don't use Google Earth, etc. etc.)
2) disable Google Play Services

I would submit if these are the available workarounds to get GPS more stable (but still not fixed) then GPS isn't working correctly for Google's services.
 
Today I set out to gather some data about my GPS' failure to reconnect, in order to have solid arguments for an eventual return and refund. It turns out I might not return my Nexus 7-2013 yet; I've never had such good performance since I bought it a week ago! There are three things I observed that might come into play:

1) Some apps seem to close their interface before totally letting go of the GPS resource, which allows you to launch other apps prematurely. I get this impression from Naviator. So, I made a point to count 5 seconds after exiting an app an making sure the top-left GPS Location icon disappears before launching any other GPS-accessing app.

2) Some of you mention disabling Google Play services. For now, I simply disabled auto-updates for apps. There is no mention of this anywhere else in this thread.

3) I also had a suspicion about the auto-sleep feature. I installed Keep Screen On to not let the tablet go to sleep, and to make sure I wouldn't screw up my tests.

I successfully held GPS locks for three periods of more than 1.5 hours today, from my basement with one small window. But, I was not moving much except walking a few times around the house.

A problem with my methodology is that I changes 3 things; now I have to put in more time to identify which is(are) actually responsible in seemingly affecting this issue in a positive way (notice how I'm trying to work around the word "fixed"!). I'm quite sure that quick opening and closing applications is cause for problems which is similar to the simultaneous apps hypothesis raised in this thread.

I'm leaving the tablet on for the night; hopefully tomorrow brings good news: a valid GPS lock!
I will report back after I've had appreciable success on the road and/or in the air.

G*d, this issue has been torturing me! I'm not ready to convert to iPad Mini!
 
Today I set out to gather some data about my GPS' failure to reconnect, in order to have solid arguments for an eventual return and refund. It turns out I might not return my Nexus 7-2013 yet; I've never had such good performance since I bought it a week ago! There are three things I observed that might come into play:

1) Some apps seem to close their interface before totally letting go of the GPS resource, which allows you to launch other apps prematurely. I get this impression from Naviator. So, I made a point to count 5 seconds after exiting an app an making sure the top-left GPS Location icon disappears before launching any other GPS-accessing app.

2) Some of you mention disabling Google Play services. For now, I simply disabled auto-updates for apps. There is no mention of this anywhere else in this thread.

3) I also had a suspicion about the auto-sleep feature. I installed Keep Screen On to not let the tablet go to sleep, and to make sure I wouldn't screw up my tests.

I successfully held GPS locks for three periods of more than 1.5 hours today, from my basement with one small window. But, I was not moving much except walking a few times around the house.

A problem with my methodology is that I changes 3 things; now I have to put in more time to identify which is(are) actually responsible in seemingly affecting this issue in a positive way (notice how I'm trying to work around the word "fixed"!). I'm quite sure that quick opening and closing applications is cause for problems which is similar to the simultaneous apps hypothesis raised in this thread.

I'm leaving the tablet on for the night; hopefully tomorrow brings good news: a valid GPS lock!
I will report back after I've had appreciable success on the road and/or in the air.

G*d, this issue has been torturing me! I'm not ready to convert to iPad Mini!

1) The problem happens even with one single app being open for too long, so this really doesn't have an impact. Driving home with nothing but maps open causes a drop after 30 minutes.

2) I have also done that and that didn't help.

3) When driving, I set mine to never time out and it still drops.

You said 1.5 hours for three periods. Are all three periods 1.5 hours long or is the 1.5 hours an aggregate? The only valid test is to keep it on for 45+ minutes and take a drive. Staying in one location isn't a good enough test because it may be based on transitioning between satellites.

What version of Maps and Google Play Services are you running?

- - - Updated - - -

Now if you do a Google news search for "Nexus 7 GPS" there are several news sites that are reporting on the issue thanks to people sending emails. Let's hope this causes Google to expedite the issue.
 
A part of me wonders if the code they used to make the forthcoming LTE model work with Verizon is also in the WIFI only version. The reason I find this interesting is it turned out that the Palm Pre's GPS issues revolved around code that was inserted to make Verizon happy (they wanted customers to pay for their Navigator service). A long shot I know, but never forget your history I say...!:p

Gawd, I'd forgotten about that can of worms. :p
 
Here's Something To Ponder:

I have both Nexus 7's, the 2012 model and the 2013 model. Well I returned the 2013 model. BUT, all the updates and Android 4.3 etc were loaded onto my "old" 2012 Nexus 7 and it has never had an issue with its GPS. Just makes me wonder if it's more than software. Granted I understand that device drivers and such are different between the two iterations of Nexus 7 models so software is always a possibility, BUT definitely makes one wonder....doesn't it.....?
 
Overnight (6.5 hours), G-Maps stayed connected, and then I switched applications 15-20 times, all stable. But then...

1) The problem happens even with one single app being open for too long, so this really doesn't have an impact. Driving home with nothing but maps open causes a drop after 30 minutes.
I have to agree. Rebooted, just G-Maps, crapped out 3 times on a 6 km drive. Came back home, my original test bed, and had it fail 3 more times at 5-10 minutes intervals. Then went for a walk around my lot and it took some 50 minutes before failing. No discernible pattern...

2) I have also done that and that didn't help.
I guess it didn't help me either! But that was one of the parameters I had changed before getting some glimmer of hope; I had to mention it.

3) When driving, I set mine to never time out and it still drops.

You said 1.5 hours for three periods. Are all three periods 1.5 hours long or is the 1.5 hours an aggregate? The only valid test is to keep it on for 45+ minutes and take a drive. Staying in one location isn't a good enough test because it may be based on transitioning between satellites.
What exactly did you set for "no sleep"? In the system settings, I haven't seen Never; max is 30 minutes, which actually really surprised me. Maybe all that frustration made me partially blind... :mad:

That was 3 x 1.5h = 4.5h.

What version of Maps and Google Play Services are you running?
Somewhat pointless now, but:
Maps 7.0.2
Google Play Services 3.2.25 (761454-36)
Location Access/Location Sources
GPS Satellites: Checked ON
Wi-Fi and Mobile: Unchecked
 
Has Google/Asus recognized this as an issue yet?

I'm loving the tablet in every aspect, except for this GPS issue, and I've tried all the various fixes/workaround.. I either want an ETA on when they plan on addressing it with a software update or it gets returned.
 

Trending Posts

Forum statistics

Threads
956,446
Messages
6,968,293
Members
3,163,548
Latest member
McChin