Incorrect coordinates for weekend at 145E

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set phone to -37,145E
2. On friday (US time) or saturday melbourne/australia time get coordinates
for the weekend and monday
3. Incorrect coordinates will be returned (vs
http://wiki.xkcd.com/geohashing/2010-02-20 )

What is the expected output?  What happened instead?

Expected output for 2010/02/20 is .8360114, .8260195, coordinates returned
are .15201072, .59457521 

What version of Geohash Droid are you using?  On what phone?

0.7.3 on ADP1 running CM-4.2.14.1

Original issue reported on code.google.com by alexofd...@gmail.com on 20 Feb 2010 at 12:45

[GoogleCodeExporter]

I just tried this on my phone for that graticule, and I got the expected result 
(.8360114, .8260195).  Are you sure the date picker on the main screen said it 
was  
Feb 20, 2010?

If it DID say that, can you try going back to the app, adjusting the date, and 
trying 
again?  There's a possibility this may be a different bug I've been wanting to 
chase 
down.

If that doesn't do it, could you try resetting the stock cache (in the settings 
screen)?

Original comment by captains...@gmail.com on 20 Feb 2010 at 12:56

[GoogleCodeExporter]

The date was Feb 20, 2010. I was getting incorrect results for the 20th,21st 
and 22nd.

Clearing the stock cache worked, although I also needed to kill the app (so it 
would
clear the calculated position history) it worked fine.

Thanks very much for your help :)

Original comment by alexofd...@gmail.com on 20 Feb 2010 at 1:02

[GoogleCodeExporter]

Well, you're welcome!  Though I'd still love to know how invalid data got in the
cache in the first place...

If this happens again, file another issue.  Try to remember what dates you 
recently
tried, too, just in case the cache is somehow getting confused under certain
circumstances.

Original comment by captains...@gmail.com on 20 Feb 2010 at 1:46

• Changed state: Done