• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Weather Widget not showing correct time (DST changes)

Sindian

Lurker
This is really annoying, I have deleted my City and cleared data and cache on App. It will show the correct time but when I add City time is a hour behind after last night. Anybody else had this problem or know how to fix it? Time on Phone is correct and on the weather app if I press Refresh it shows the correct time but the display is wrong.
 
The time on my phone is fine, it's reading 5:00pm. However the weather widget is not showing the correct time.

You can see in the picture, underlined in red, that the time shows 4:00pm, it even shows updating the weather at the correct time (5:00pm), when in actuality the time is 5:00pm, not 4:00pm. We did move the clocks forward yesterday (or really today because it was 2:00am), and phones do it automatically, but there is no setting for this in the weather widget settings and it hasn't done it automatically.

Does anyone know a solution?
 

Attachments

  • Screenshot_20180311-171929.jpg
    Screenshot_20180311-171929.jpg
    209.5 KB · Views: 692
Maybe removing the widget and then putting it back, will refresh the issue?

Unfortunately I've tried that and it didn't work. I've reset my phone. I really don't know why it's not working

Maybe removing the widget and then putting it back, will refresh the issue?

I believe it is something with the city. I cleared the cache and data it changed the time to 5:44pm. But when I added the city back, it changed back to 4:44pm.
 
I found this reply over in the S3 forums when doing a Google search for the problem:

I had the same issue, so I tested a theory. It has to do with the city. I tried to turn the location off and then back on to reset the app like I read here prior and it didn't work, so instead I turned off the location and added another city close by and the time was Accurate! Then I manually added my city with the location turned off and the time was wrong like before. My guess is the city hasn't been updated yet and we will need to just wait. My location for reference is Concord, NH the city I tested was Manchester, NH.

So it seems to be an issue with one's local area not updating their time, and should be fixed within a day or two.
 
I found this reply over in the S3 forums when doing a Google search for the problem:



So it seems to be an issue with one's local area not updating their time, and should be fixed within a day or two.

Yeah I saw that and was hoping that was it but I've added quite a few cities just to test and time is always wrong
 
Back
Top Bottom