Guessing this is because of the GPS issues with 2.1, but Google Latitude simply DOES NOT update, unless I open Maps manually.
Does 2.2 Fix this? any other phones having this problem in 2.1?
- KrossXC
The Moment had a similar issue. You would think Samsung would have it figured out by now.
May just be me, but I thought it had to be "running" to update the location - at least on my hero I had to open it, and let it load my location before it would update latitude.
Mine updates just fine as long as you have google location services running. Menu/settings/Location & Security/use wireless networks. Make sure user wireless networks is checked. It comes unchecked by default.
FYI: This is not an Android development issue.
Related
For some odd reason my location can never be found. In latitude I have set it manually,as well as automatically using settings and it throws the same error each time. I am running the latest version of maps, so I know it can pull my location from wifi.
Is there a setting I missed somewhere else in the system? It stuck at 1 point but the first time I tried directions, it lost my location on the map.
Any input? is it a bug or just not working w/o GPS?
any help would be appreciated.
The WiFi location doesn't work for some reason -- so GMaps wants to default back to GPS (which the GTablet doesn't have)
Download "Location Spoofer v1.7" or "My Fake Location" from the Market (sometimes they don't show up -- but I posted the APK for Location Spoofer 1.7 in another thread about Google Maps so grab it there if you need it)
I did manage to get my location locked by using latitude from the PC, using IP location look-up. Now my location shows up on maps on the G-tab but still when I click nearest places, (gas, ATM) etc it still throws location not found.
Gonna try location spoofer now.
Ok seems like this issue is gonna go on the back burner for a while. Even running location spoofer, it still gives the message "location temporarily unavailable.
Or...it just be a plain simple issue that Montana is falling behind the times and is on Googles (we'll get around to fixing it) schedule.
It's not that I don't know where everything is in town. it would just be nice to have a functioning tool to show off.
I picked up a Charge last Friday and rooted it the next day. However, both before and after the root (to gummycharged) the network location functionality was broken. Maps would only give me a location if GPS was enabled; trying to get one with GPS off gives a "Please enable a My Location source in system settings" popup even though "VZW Location services" is checked. And nevermind the legal message that comes up every time GPS is enabled...
So the question is, did I break something? I've searched for stuff all day, and though there was some stuff about things being broken with that function on other devices around the end of last year, I haven't seen anything since. I'm wondering if I should just wait for a gingerbread ROM to come along and install that to see if that fixes things...
Update: I have tried copying in a networklocation.apk file from another ROM into my system/app folder, but still no luck. I don't understand why it won't even try to use the network location. I even found the NetWork Location app, which seems to be working just fine and giving me lat/long. It just doesn't work for maps.
VZW Location Services isn't a source that google maps (or pretty much any other program on your phone) can access. That service is only for Verizon Navigator (which is $10/mo and doesn't provide much that Google Maps gives you for free).
So, you have to enable one of the other location services, either the GPS or the google location services.
Google wrote the message that "Please enable a My Location source in system settings" but Verizon added the menu entry for their location services after that. That's why it sounds like checking the Verizon box should make maps work, but it doesn't.
Ah, that makes some sense now. *smacks forehead*
So, I've checked the Google box, and now I don't get the message any more, but it still won't give me a location even after rebooting.
Should I go back and install the regular gummycharged mod? I think my screwing around with networklocation.apk may have actually broken it...
EDIT: IT WORKS!!! Went back, reinstalled gummycharged, and it f'ing works!
You, sir, are The Man. Or The Woman, as the case may be.
Does anyone know if theres a way to prevent latitude from updating on my tablet?
I don't always have it with me, but I always have my phone with me and I do want it updating on there.
The issue I'm running into is if I disable the detecting of my location on the tablet, that setting transfers over to phone as well.
Its akin to leaving my browser open on latitude on my computer when its at home, itll update periodically and show the wrong location. If the browser is closed, it doesnt update but even if maps is closed on the tablet, it still auto updates my location every so often.
Thanks for any help.
I use Google Maps for navigation to and from work, and lately I've been getting a periodic situation where the turn-by-turn directions stop, and all I get is "Turn Right" or "Stay Straight" instead of normal "In 800 feet, turn right on Main Street"...
I've been able to temp fix it by going into Settings, Location, Maps, and toggling Location Services and Location History off and on (with a reboot for good measure), but it's super-annoying and I can't pinpoint when it will work properly and when it won't. Sometimes it works just fine in the morning but quits working properly in the evening of the same day. No changes made in the interim that might cause it.
Anyone see this and know a fix? I'm on Mahdi ROM latest version with latest version of Maps. Maps version doesn't seem to matter, it happened on an older version and then the most recent version again this evening.
ldubs said:
I use Google Maps for navigation to and from work, and lately I've been getting a periodic situation where the turn-by-turn directions stop, and all I get is "Turn Right" or "Stay Straight" instead of normal "In 800 feet, turn right on Main Street"...
I've been able to temp fix it by going into Settings, Location, Maps, and toggling Location Services and Location History off and on (with a reboot for good measure), but it's super-annoying and I can't pinpoint when it will work properly and when it won't. Sometimes it works just fine in the morning but quits working properly in the evening of the same day. No changes made in the interim that might cause it.
Anyone see this and know a fix? I'm on Mahdi ROM latest version with latest version of Maps. Maps version doesn't seem to matter, it happened on an older version and then the most recent version again this evening.
Click to expand...
Click to collapse
Same issue on stock. I searched it up and it seems that you have to reinstall the GoogleTTS.apk. I tried that and have the same issue.
Try a different tts app
Sent from my Nexus 5 using Tapatalk
Suggestions? I don't think its a text to speech issue, it seems maps goes into short mode or dummy mode...
sent from my hammerhead
bump
I have the same issue. On stock Android (4.4.2), intermittent lack of spoken street names. I usually resolve by going in to the text to speech settings and playing the sample. Once I do that, everything seems fine.
Which I had a better idea what was causing TTS to occasionally go sideways so I could fix the root instead of this silly smack-upside-the-head intervention.
This is still happening for me. I'll check the tts settings next time.
sent from my hammerhead
Since a while I'm having big problems with SmartLock Trusted Places. When I'm @ home and having the home address from Google Maps enabled, it almost never works.
If I manually add my neighbors addresses as well it works for the moment but that result does not last.
If I go into the settings and add something it updates my location to the very address that is added automatically by enabling Home from Google Maps.
Location and location history is enabled on the device.
High accuracy, battery saving & device only all get the same result, it does not work.
Running 5.1 with Google Play services 7.0.97 (-438).
Does it work for you?
I actually just logged on to ask the same thing. It's been this way ever since 7.x dropped. It's so frustrating all the issues this new play services has caused.