32place
WatchMaker Bug Tracking All the ideas and discussions
25 votes Vote

Time zone support is broken

Ever since daylight savings time change in California, times in "other" time zones are wrong. (It's as if the current time zone never changed.) Also, why isn't there India in the list of time zones? Sri Lanka, which has the same UTC offset, is in the list though.

Kannan , 12.03.2015, 01:45
Idea status: rejected

Comments

AlexCurran, 10.06.2015, 10:53
Timezone support in WatchMaker does not take daylight savings into account as there are 100s of variations around the world and it would be a huge job to create a database for all of these.
You need to manually add or subtract an hour in the settings to get the right value.
The country list gives examples of countries in each timezone but does not give a complete list of all countries.
Reply
AlexCurran, 10.06.2015, 10:54
To manually add or subtract an hour, just use the next / previous timezone.
Reply
Kannan, 10.06.2015, 13:53
Indeed, compiling all time zone information is a tedious job. That's why someone else has already done it and it's available as a simple reusable library. Google for Joda time zone. Simply using that library for time zone conversion is the easy and accurate thing to do.

Please reconsider this case.
Reply
Kannan, 10.06.2015, 14:30
Also worth mentioning. Representing time zones as UTC offsets is almost always wrong. Because UTC offsets keep changing all the time. The right way is to use the time zone name (such as Americas/Los_Angeles). If you're storing UTC offsets in your app, you'll have to change it everywhere to use time zone name instead. (This could be more work than using a library only for time zone conversion and leaving everything else unchanged. )

This is why every time zone needs to be listed even when two time zones might have the same UTC offset. Time zones are way more complicated than simple UTC offsets. It's the unfortunate reality we are living in. That's precisely why we need computers to do our time zone conversions.
Reply
Kannan, 13.06.2015, 06:27
So, is this it? You're going to reject this legitimate bug because you don't feel like fixing it?
Reply
Trevor Fenn, 14.06.2016, 15:16
Keep the UTC offsets, but make them actual UTC offsets. Right now they change with local daylight savings time. A UTC offset should never change.


Also, there's a proper time zone API for Android you could be using.
Reply
Rely, 27.10.2018, 21:22
Português (Brazil)
Olá, adquiri a versão premium do WatchMaker (Google Play) e ao importar alguns relógios, o horário no mostrador do Samsung Galaxy Watch BT não é o mesmo do App no celular (1 hora de diferença). O que pode estar errado?
Reply

Leave a comment