app gave wrong location

[GoogleCodeExporter]

I have not run the app for a few days (if that matters).
I ran the app today (Saturday), and also went to the website (peeron.com) on my 
PC to compare, and they have different results.
No, not rounding error.
No, not "next graticule was closer", I mean actually different decimal numbers 
(something like X.282 vs X.405).

I changed both to Friday, and they gave the same results as each other.
I changed back to today, and this time the app was correct.

What version of Geohash Droid are you using?  On what phone?
0.7.10 on Samsung Fascinate (Verizon)

What version of Android is running on that phone, if you know?
firmware 2.2.1
kernel 2.6.32.9
build sch-1500-ed04

(m5) Rammy (at gmail)

Original issue reported on code.google.com by m5ra...@gmail.com on 18 Jun 2011 at 2:52

[GoogleCodeExporter]

Hm... this is sounding familiar...

Going through the lookups at irc.peeron.com's maps, the closest hashpoint with 
a .282 latitude was June 16, 2011 (two days ago).  This is sounding eerily like 
a bug that came up before, where what the date picker showed wasn't in sync 
with what it was reporting back in code.  A bug which I thought I fixed on 
Android's side itself.

As a quick suggestion, can you try getting today's (June 18, 2011) hashpoint 
again, but adjust the date back a day first before trying (i.e. just click the 
minus and plus arrows so that the date changes before going back to June 18)?  
I just tried it on my phone and I got the correct point, so I have this feeling 
that bug with DatePicker is creeping back in again.

Original comment by captains...@gmail.com on 18 Jun 2011 at 5:00

[GoogleCodeExporter]

First of all let me say I really do like the app.

I hope this is what you mean:
I made sure the app wasn't running in the background
I started the app
I changed to yesterday's date
I changed back to today
I went to the map (options set to "Use Closest")
The coordinates were good

I will wait to test it again in a few days.

R

Original comment by m5ra...@gmail.com on 18 Jun 2011 at 5:42

[GoogleCodeExporter]

Yep, that's starting to sound a lot like an old bug.  Cripes.

I've got a couple ideas of how to fix this (up to and including just dragging 
in the small-screen version of the date picker, which doesn't have this 
problem), but in the meantime, the only workaround I've got is to either 
twiddle the date when you're on the main screen, or press the Back button to 
back out of the app (not the Home button; it seems that's what's saving the 
state and triggering the bug).

But, I'll give it some thought.  Thanks for the bug report!

Original comment by captains...@gmail.com on 18 Jun 2011 at 5:56

• Changed state: Accepted
• Added labels: Component-UI, Type-Defect, Usability

[GoogleCodeExporter]

ok, I can repeat the error now, based on what you said.

Set the date to the 16th
go to map
go "back" to date (still shows the 16th)
go "home" to exit the program

kill all running programs

start the app
(shows today's date, the 18th)
go to map
(shows coordinates from the 16th)

R

Original comment by m5ra...@gmail.com on 18 Jun 2011 at 6:06

[GoogleCodeExporter]

All righty.  I've got a new version in the Downloads area (0.7.11-pre1).  I 
changed the main date picker on the large/medium screens to the same 
space-saving date button I use in the small screens, since the DatePicker 
widget seems to have a bug in it that isn't going to be fixed in the main SDK 
releases.  DateButton, on the other hand, I know that one works, at least.

So, give it a shot, and if that all looks well, I'll make a new update in the 
Marketplace.  Thanks!

Original comment by captains...@gmail.com on 23 Jun 2011 at 3:08

• Changed state: Fixed

[GoogleCodeExporter]

indeed it looks good, thanks

Original comment by m5ra...@gmail.com on 23 Jun 2011 at 3:52