Anyone noticing or dealing with a bug in their Android handset (mine is an EVO 4G) in which the time and/or location changes. While there have been a few settings and network variables that make diagnosis difficult, here's what I'm noticing.
At 8:46pm on 01/11/11 I noticed my handset was showing the time as 1:46am and the location as Reykjavik, Iceland. I am on the East Coast of the US, in New England.
I did a soft reset and the time corrected itself. I thought nothing further.
This morning after my clock alarm (that goodness for that!), I noticed the time was again showing incorrectly; this time it was off by about 4 hours so the 6:10am time was displaying as 11:10am, but the location was correct (at least in Beautiful Widgets).
Further exploration found that the "automatic settings" were showing the time zone as GMT 0:00 when it should be reading Eastern +5:00. Each time I disable automatic settings and manually set the time zone everything returns to normal. The first time the phone was on Sprint's 3G network and the second time on my wi-fi using Charter Communication's internet.
I've checked a few other settings. If I re-enable the automatic settings, the time zone will continue to default to GMT, so there is something wrong there, but more interesting is when navigating to the Google search page in the DOLPHIN HD browser, I was asked to share my location with Google; when I did it popped up as Reykjavik, Iceland. When I opened the stock Android browser, the previous and correct location (my real location) was displaying.
So now I am completely lost as to what could be causing this, what the solution might be, if my phone is defective, if Sprint's time server is messed-up or if it's a particular application.
Just don't know....
Birds falling dead from the sky....
Fish dying by the hundreds Southeastern US....
And now a smartphone that has suddenly become stupid....
HELP!
***UPDATE*** I checked my work phone - which is also on Sprint's network - and noticed that the time was correct on that device (I failed to mention this earlier). That phone is not a smartphone and not running Android OS. This would seem to remove Sprint's information serving from the possible list of sources for the problem.
At 8:46pm on 01/11/11 I noticed my handset was showing the time as 1:46am and the location as Reykjavik, Iceland. I am on the East Coast of the US, in New England.
I did a soft reset and the time corrected itself. I thought nothing further.
This morning after my clock alarm (that goodness for that!), I noticed the time was again showing incorrectly; this time it was off by about 4 hours so the 6:10am time was displaying as 11:10am, but the location was correct (at least in Beautiful Widgets).
Further exploration found that the "automatic settings" were showing the time zone as GMT 0:00 when it should be reading Eastern +5:00. Each time I disable automatic settings and manually set the time zone everything returns to normal. The first time the phone was on Sprint's 3G network and the second time on my wi-fi using Charter Communication's internet.
I've checked a few other settings. If I re-enable the automatic settings, the time zone will continue to default to GMT, so there is something wrong there, but more interesting is when navigating to the Google search page in the DOLPHIN HD browser, I was asked to share my location with Google; when I did it popped up as Reykjavik, Iceland. When I opened the stock Android browser, the previous and correct location (my real location) was displaying.
So now I am completely lost as to what could be causing this, what the solution might be, if my phone is defective, if Sprint's time server is messed-up or if it's a particular application.
Just don't know....
Birds falling dead from the sky....
Fish dying by the hundreds Southeastern US....
And now a smartphone that has suddenly become stupid....
HELP!
***UPDATE*** I checked my work phone - which is also on Sprint's network - and noticed that the time was correct on that device (I failed to mention this earlier). That phone is not a smartphone and not running Android OS. This would seem to remove Sprint's information serving from the possible list of sources for the problem.
Last edited: