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.
I don't really care what outsourced support has to say.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?
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.
Being able to contact someone and being able to get a resolution are not necessarily the same thing.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.
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.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.
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!
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...!![]()
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...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 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.2) I have also done that and that didn't help.
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...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.
Somewhat pointless now, but:What version of Maps and Google Play Services are you running?