Took me quite some time to figure this one out, thought I should post it here in case anyone else has a similar problem.
When I updated to Android 4.1.2, I noticed that my Google Navigation stopped working. It would simply sit there endlessly "Waiting for location..." Fortunately, there's a simple fix:
1. Go to "Settings > Accounts > Google > Location Settings".
2. Flip the switch to "On" (I found this was off in my case).
3. Try Google Navigation again, it should work fine.
I'm not sure why Google decided to break up the location settings into two different places like this, but it's a bit silly IMO as it's definitely going to catch some people out.
You probably cleared the Google Services Framework at some point. When you do that, it disables location services.
Makes sense. It's still a good thing to let people know about it.
It's good to know that I wasn't the only one with this issue factory reset did the thing for me.
I have a different issue
hi
My issue is different.
After the update I am not able to download updates from Google play.
It tells me that the connection to the server has been timed out.
|I cleared the Cache of Google play, but did not helped.
Any ideas?
The issue with GPS was present on update from ics to jb as well and also on 4.0 to 4.0.x and fix was the same as you described it switch on and off location service
Sent from my Galaxy Nexus using xda premium
MattSkeet said:
The issue with GPS was present on update from ics to jb as well and also on 4.0 to 4.0.x and fix was the same as you described it switch on and off location service
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
In my case it was actually that the location service for Google apps was switched off by default after the update. I didn't need to cycle it or anything, just simply switch it on.
Vilcek said:
hi
My issue is different.
After the update I am not able to download updates from Google play.
It tells me that the connection to the server has been timed out.
|I cleared the Cache of Google play, but did not helped.
Any ideas?
Click to expand...
Click to collapse
Not sure how to fix that. Are you sure you have an internet connection on your phone? You might need to use the "Clear Data" option, rather than just "Clear Cache".
Hey, man, thanks a lot, I've been banging my head for 6 hours until I found your post. I was minutes away from resetting my phone to factory defaults. You saved me a lot of trouble. Kudos to you!
Thanks for the heads up on this!
Thanks
I too had emptied the google apps framework for the update to 4.2.1 on the galaxy nexus, this helped me out. Thanks!
Awesome
It worked for me in a Galaxy S3 i9300. Thank you so much!
Related
Does anybodies Google places work? I hit the search button when I want to find something and nothing ever happens.
Sent from my Galaxy Nexus using Tapatalk
Mine is working fine. I am on a custom rom though. I'm pretty sure it was working before rooting too.
The exact same thing has happened to me since ive owned the galaxy nexus. I have been holding out and hoping that one of those maps updates will fix our problem. A good work around is if you go to maps and type in the search bar what you are looking for and select it from the map or if you go to google places on your web browser it works ok. Not really a good solution but its worked for me.
Are you sure you guys are allowing access? When you first run it you have to grant it access. Could be in the background when you pull the drop down.
blacknsb said:
The exact same thing has happened to me since ive owned the galaxy nexus. I have been holding out and hoping that one of those maps updates will fix our problem. A good work around is if you go to maps and type in the search bar what you are looking for and select it from the map or if you go to google places on your web browser it works ok. Not really a good solution but its worked for me.
Click to expand...
Click to collapse
Yeah when I search in maps it works but in the places app no dice. Kinda sucks. I wonder if I uninstall it and reinstall will fix it.
Sent from my Galaxy Nexus using Tapatalk
Worth a try for sure. I use that app all the time if I'm out of town.
I checked and I had the same problem. I resolved it by going to:
Settings>apps>Maps> then I cleared the cache and uninstalled the updates. I went to the market and updated back to the current version and everything works fine now.
Oh how I love Android and all of it's little glitches. I see them as an opportunity to figure things out.
bmolloy said:
I checked and I had the same problem. I resolved it by going to:
Settings>apps>Maps> then I cleared the cache and uninstalled the updates. I went to the market and updated back to the current version and everything works fine now.
Oh how I love Android and all of it's little glitches. I see them as an opportunity to figure things out.
Click to expand...
Click to collapse
Glad it worked for you but it didn't work for me.
Sent from my Galaxy Nexus using Tapatalk
Anyone else seeing Google Maps FC a lot lately? It seems to be related to finding my location (either in Latitude or Maps itself). Sometimes the map tiles won't get drawn, other times it just force closes.
Seeing this on mine (GSM) and my GF's VZW version.
Nop but have you tried clearing the app cache?
Galaxy Nexus Stock + Franco m3
YES! this happens with me too lately! dunno why!
SOLVED for me!
Had the same issue, and this worked for me:
http://forum.xda-developers.com/show....php?t=1467313
I was experiencing the same thing and chalked it up to a bug so I uninstalled Maps updates and have been refusing to update until a new version comes out.
The fix permissions thing, I feel like that could be risky... I guess I could take a nandroid backup first and then try it.
I am having this problem and I just bought my GSM Nexus from Play Store... Whats wrong with Maps app? Keeps force closing...
STOCK. Not rooted.
Cleared cache and settings in Settings > Apps > Clear.
Still force closing.. What the ??
Steve Jobs® said:
I am having this problem and I just bought my GSM Nexus from Play Store... Whats wrong with Maps app? Keeps force closing...
STOCK. Not rooted.
Cleared cache and settings in Settings > Apps > Clear.
Still force closing.. What the ??
Click to expand...
Click to collapse
And the problem continues to this day. I almost wanted to start a new thread, until I stumbled upon this one.
Stock Jellybean JRO03C, rooted, slightly themed (to get rid of gradient background). Maps is at 6.9.2 as shipped with the image, and have not had an update since.
Maps keeps force closing every few hours even when I'm in other apps and have not started Maps myself. FC reports says it's an out of memory exception. This only started after I upgraded to JB; it was fine on all versions of ICS, even when rooted.
I had this issue upgrading from 4.2 to .4 uninstalling the map updates did the trick
Sent from my Galaxy Nexus using xda app-developers app
skye206 said:
I had this issue upgrading from 4.2 to .4 uninstalling the map updates did the trick
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Unfortunately I don't have an update I can uninstall.
I have for now restricted it from doing background data and see what happens. Next - block it off using Droidwall; still next - disable it outright...
motopig said:
Unfortunately I don't have an update I can uninstall.
I have for now restricted it from doing background data and see what happens. Next - block it off using Droidwall; still next - disable it outright...
Click to expand...
Click to collapse
No one?
DIsabling Maps still doesn't stop it from crashing behind the scenes. :crying:
Sorry this problem is months old. Haven't had it since the update that fixed it.
Sent from my Galaxy Nexus using Tapatalk 2
Hi guys,
I think I've found a possible workaround for forcing Nexus Update without breaking Google Services Framework. I did this procedure on three Nexus and got the same result, so I think it's safe (or I'm lucky as hell).
Step by step:
Settings->Apps->All->Google Services Framework
Click on Force Stop and Clear Data after.
Go check your System Updates on "Settings->About". If it works and your phone starts downloading the update, reboot your phone immediately. When it's back on, Google Services will ask your permission to get your location and anonymous data, click Agree and open some google app, like Maps. Go back to your System Updates on About menu and proceed as usual.
I think the trick here is to allow Google Service Framework to rebuild its data before the update run itself.
Well, it worked for me and worth a try
Breaking google services framework? I've never heard of that.
supernova_00 said:
Breaking google services framework? I've never heard of that.
Click to expand...
Click to collapse
When you clear the data of Google Framework, some stuff breaks, but after awhile it will go back to normal.
supernova_00 said:
Breaking google services framework? I've never heard of that.
Click to expand...
Click to collapse
It happens a lot when you clear it to force the update. Search the forum and you'll see a lot of reports about that.
danielms said:
It happens a lot when you clear it to force the update. Search the forum and you'll see a lot of reports about that.
Click to expand...
Click to collapse
I clear it all the time and never have any issues and have never seen any mentioned.
supernova_00 said:
I clear it all the time and never have any issues and have never seen any mentioned.
Click to expand...
Click to collapse
One issue is your phone can disappear from the Play Store "devices" list. This happened to me but eventually it will come back, just takes time.
Great!
danielms said:
Hi guys,
I think I've found a possible workaround for forcing Nexus Update without breaking Google Services Framework. I did this procedure on three Nexus and got the same result, so I think it's safe (or I'm lucky as hell).
Step by step:
Settings->Apps->All->Google Services Framework
Click on Force Stop and Clear Data after.
Go check your System Updates on "Settings->About". If it works and your phone starts downloading the update, reboot your phone immediately. When it's back on, Google Services will ask your permission to get your location and anonymous data, click Agree and open some google app, like Maps. Go back to your System Updates on About menu and proceed as usual.
I think the trick here is to allow Google Service Framework to rebuild its data before the update run itself.
Well, it worked for me and worth a try
Click to expand...
Click to collapse
Worked perfectly on Nexus 7, thanks.
Worked when updated to 4.2. But this time still get no notification when try to update to 4.2.1
Sent from my Galaxy Nexus using xda premium
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
What color are you signal bars? Grey = No connection to Google, Blue = Connection to Google
Try clearing data for the Google Framework
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Galloway said:
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Click to expand...
Click to collapse
And which ROM is this?
DirtyOldMan said:
And which ROM is this?
Click to expand...
Click to collapse
He's running Liquid Smooth 2.5 as stated in the first sentence.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Galloway said:
Signal bars are blue both on wifi and on data with good signal. I just tried clearing Google Services Framework... No go still unfortunately. Thanks for the suggestion however.
Click to expand...
Click to collapse
Reflash the gapps/addons
KorGuy123 said:
He's running Liquid Smooth 2.5 as stated in the first sentence.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks
I will try refreshing Gapps when I get a chance but the thing that has me puzzled is why my stock rooted N7 is doing the same thing. I can't help but think it is an issue with my account or something. I haven't changed any settings recently that I know of. if it was just a Gapps issue I would have thought it would be isolated to just my SGS3. It isn't likely a location issue as my Wife's tablet is working fine.... Definitely confused...
Again thanks for any and all suggestions
Galloway said:
I will try refreshing Gapps when I get a chance but the thing that has me puzzled is why my stock rooted N7 is doing the same thing. I can't help but think it is an issue with my account or something. I haven't changed any settings recently that I know of. if it was just a Gapps issue I would have thought it would be isolated to just my SGS3. It isn't likely a location issue as my Wife's tablet is working fine.... Definitely confused...
Again thanks for any and all suggestions
Click to expand...
Click to collapse
And all of these are connected to your WiFi?
Remove and Re-add your google account on the affected devices.
Just to try I added my wife's account into Google now and tried voice searching with her account from my N7 and it didn't work either. It works from her tablet. I think this means it is not a ROM issue but rather a settings or similar issue. I will try a Gapps refresh later to see what happens. If anyone else has experienced this regardless of whether there is a fix I'd be curious to know. if others have I may submit it to Google. if it is just a weird issue for me I'd rather try working through it.
Galloway said:
Just to try I added my wife's account into Google now and tried voice searching with her account from my N7 and it didn't work either. It works from her tablet. I think this means it is not a ROM issue but rather a settings or similar issue. I will try a Gapps refresh later to see what happens. If anyone else has experienced this regardless of whether there is a fix I'd be curious to know. if others have I may submit it to Google. if it is just a weird issue for me I'd rather try working through it.
Click to expand...
Click to collapse
Gapps won't fix it... it's 2 devices... bear with me I need to narrow it down....
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
Check PM, sending you my GTalk, add me, so we can chat.
SGS3 wifi or data (LTE mainly) the N7 and TF300T are wifi only...
Galloway said:
SGS3 wifi or data (LTE mainly) the N7 and TF300T are wife only...
Click to expand...
Click to collapse
Check you PM... I sent you my gtalk... add me... you can chat at gmail.com
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
I've been having this problem too with an HTC One on a Sense-based custom ROM, and a HTC Evo 4G LTE both stock and custom. I've found better success uninstalling the updates to the Google Search app though it's still slower than it used to be. Some more people have talked about it here... http://forums.androidcentral.com/go...-google-moment-while-online-voice-typing.html
Doesn't seem like there's much of a solution or acknowledgment by Google that there's a problem.
I fixed the issue!! On a hunch I decided to delete my Google account from the phone completely. I then booted to recovery and cleared cache and dalvik. Rebooted and added my Google account back in... it is now working as it used to. If anyone else is having the issue I would recommend trying this and see if it helps you as well.
Almost forgot but I'd really like to thank everyone who contributed ideas and thoughts!
I just verified this fixed my N7 as well!
Thanks
Galloway said:
I fixed the issue!! On a hunch I decided to delete my Google account from the phone completely. I then booted to recovery and cleared cache and dalvik. Rebooted and added my Google account back in... it is now working as it used to. If anyone else is having the issue I would recommend trying this and see if it helps you as well.
Click to expand...
Click to collapse
thanks it worked for me.....
Easier solution
Galloway said:
I'm running Liquid Smooth 2.5 and have just found that anytime I try and use voice search the microphone icon glows as if it is recognizing but as soon as it goes to search it just errors out with "Cannot reach Google at the moment". Has anyone else encountered this and are there any suggested fixes? I found some threads of making sure the device date and time is correct. It is. Interestingly I just tried on my rooted stock N7 and same thing... Yet I also just tried on my wife's Asus TF300t and it is working properly... I've checked all google account settings I can think of and can't see anything abnormal.
Thanks in advance for any help.
Click to expand...
Click to collapse
My impression from searches on Google's forums is that this is a fairly prevalent problem. I don't know what causes it, but I've seen it on S4s, too. I just wanted to add that, anecdotally, I tried clearing the cache (though not dalvik) and removing the Google account, to no avail; however, I found a much simpler solution:
Settings, My Device, Language and input
Change Voice recognizer from Google to something else (in my case Samsung powered by Vlingo)
(Optional) Change Voice recognizer back to Google
This resolved the issue for me, please let me know if it works for others (I don't need a thumbs-up or anything, I'm honestly just curious if it's that simple and we're making it out to be more difficult.)
jacksonpeebles said:
My impression from searches on Google's forums is that this is a fairly prevalent problem. I don't know what causes it, but I've seen it on S4s, too. I just wanted to add that, anecdotally, I tried clearing the cache (though not dalvik) and removing the Google account, to no avail; however, I found a much simpler solution:
Settings, My Device, Language and input
Change Voice recognizer from Google to something else (in my case Samsung powered by Vlingo)
(Optional) Change Voice recognizer back to Google
This resolved the issue for me, please let me know if it works for others (I don't need a thumbs-up or anything, I'm honestly just curious if it's that simple and we're making it out to be more difficult.)
Click to expand...
Click to collapse
This solution didn't work for me...but I solved the problem by cleaning cache / data and doing a "force stop" of Google Search :laugh:
tia08 said:
This solution didn't work for me...but I solved the problem by cleaning cache / data and doing a "force stop" of Google Search :laugh:
Click to expand...
Click to collapse
Whatever works, I guess!
Does anyone have this issue? After about 60hrs of reboot Google Now just stops to display any cards and it is just blank with the google searchbar on top...
I have Google Now enabled and never had this issue before. Tried clearing cache and app data and that doesn't fix the issue. Only reboot helps. This is annoying. Any help is appreciated. I am running stock Android 4.3 (no root).
Thank you!
Sent from my Galaxy Nexus using xda premium
Ive had this happen before. I dont really know what causes it, it just fixes itself usually. I did, however, find that at one point I had both of my devices with Google Now and they had different settings enabled and it was messing up what was shown. That was a while ago and I think the settings sync now. But you never know. If you have two devices, try that. Also, you can try to clear the data for the app and see if it fixes it.
I have tried clearing the app data and that didn't do much. Still having the issue. I will check the settings on my tablet for Google Now, maybe you are right and this is what causes my problems. Thanks for the idea-will give it a try.
It's generally "normal" I think.
I really wish Google would give us more control over Now... Soon?
Sent from my Galaxy Nexus using xda app-developers app
I'm also experiencing this "issue". I use Galaxy Note II and CarbonRom 1.8 here. Decided to search Google for this and found this thread.
I thought it was due to a lot of ROM flashing I was doing here, so maybe it eventually messed up my Google account info on servers and made my Google Now became empty some times, but I realized that probably it's some technical difficulties on Google Now server itself, since it's happening with more people.
Let's hope for an update to solve this. It's pretty annoying!
viniciusrsouza said:
I'm also experiencing this "issue". I use Galaxy Note II and CarbonRom 1.8 here. Decided to search Google for this and found this thread.
I thought it was due to a lot of ROM flashing I was doing here, so maybe it eventually messed up my Google account info on servers and made my Google Now became empty some times, but I realized that probably it's some technical difficulties on Google Now server itself, since it's happening with more people.
Let's hope for an update to solve this. It's pretty annoying!
Click to expand...
Click to collapse
Did this issue get resolved for you? I have found the problem and I temporary fix.
The issue is related to the new Google play services 3.2..they changed location to use wifi as Android 4.3 has it on at all times.. This is to save power from using GpS.. Anyway if your not running 4.3 and have wifi on all the time your location based cards will not work...
The solution, downgrade to Google play services 3.1 Everything works great on 3.1..
Sent from my SGH-T889 using xda app-developers app
luv4greenleaves said:
Did this issue get resolved for you? I have found the problem and I temporary fix.
The issue is related to the new Google play services 3.2..they changed location to use wifi as Android 4.3 has it on at all times.. This is to save power from using GpS.. Anyway if your not running 4.3 and have wifi on all the time your location based cards will not work...
The solution, downgrade to Google play services 3.1 Everything works great on 3.1..
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
This issue got solved by itself here, but thanks for the tip anyway!
By the way, I'm using 4.2 here and in fact I don't have wifi enabled all the time. Need to say also that Google Now in Brazil is not sooo much great, it does not have so many services, only the basic ones, so maybe it had something to do with Brazilian Google servers issues on that time.