search

energyplug / geohashdroid

Automatically exported from code.google.com/p/geohashdroid
0 stars 0 forks source link

Can't determine my current location without GPS #45

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start Geohash Droid
2. Check Today and Use Closest checkboxes
3. Click Go!

What is the expected output?  What happened instead?
This used to show my location and location of the nearest geohash. Now it only 
shows me the Attempting to determine your location box.

What version of Geohash Droid are you using?  On what phone?
0.7.17 on Samsung Galaxy Nexus.

What version of Android is running on that phone, if you know?
4.1.1 (Jelly Bean).

Please provide any additional information below.
This used to work without GPS, has there been a deliberate change? Google Maps 
still gets my location right without GPS, so it's not a system wide problem. 
Although MapQuest seems to have the same problem...

Original issue reported on code.google.com by marko.ha...@gmail.com on 14 Oct 2012 at 6:50

GoogleCodeExporter commented 9 years ago 
I was running into this myself on my Nexus S a while ago, but for me, Google 
Maps actually WAS having a hard time pinning me down very accurately without 
GPS (I think it got a very general match, like my city, but nothing like what 
I'd expect from non-GPS locations).  Plus, any other app that used location 
searching was choking on cell tower/wifi locations, too.  It seems like it 
resolved itself for me, and I haven't heard of any changes to the location API 
that would cause problems like that, so I've got this odd feeling that's an 
intermittent problem with Google's location services.

I'm afraid the only thing I can suggest is to give it more time (on the scale 
of days or weeks, unfortunately) and see if Google sorts it out.  Apart from 
telling it to use cell towers or GPS (which I'm doing), there's nothing more I 
can do on the code side.

Original comment by captains...@gmail.com on 14 Oct 2012 at 7:01

GoogleCodeExporter commented 9 years ago 
Ok, thanks for the quick answer! This has been going on for a couple of weeks, 
so I'm not really hopeful that it'll get resolved soon.

Original comment by marko.ha...@gmail.com on 14 Oct 2012 at 7:20

GoogleCodeExporter commented 9 years ago 
Some additional info: I just installed the Android 4.1.2 update and the problem 
seems to be gone. Might be either the update or the reboot that did the trick.

Original comment by marko.ha...@gmail.com on 18 Oct 2012 at 8:54