-
All replies
-
Helpful answers
-
Jun 19, 2015 8:58 AM in response to bdpspby léonie,It is wrong for Hamburg, Germany as well.
Sunset will be later in two hours, but the watch face is showing Hamburg right on the terminator already.
-
Jun 19, 2015 11:17 AM in response to bdpspby LarryHN,Tell Apple - https://www.apple.com/feedback/watch.html
LN
-
Jul 1, 2015 4:31 AM in response to léonieby Roger Fischer,The astronomy face has its seasons upside down, backwards or dyslexic, however you wish to term it. It's showing the northern hemisphere in its winter in July.
-
Jul 3, 2015 3:54 AM in response to bdpspby Roger Fischer,the display is backwards. It's showing the northern hemisphere in its winter, when it should be showing summer. Yesterday (July 2) it was correct for a brief time. Then this morning (July 3), it reverted. Not sure if these algorithms reside within each watch or are transmitted from some dyslexic cloud.
-
-
Jul 4, 2015 6:33 AM in response to léonieby Roger Fischer,Here's what appears to be going on -- and it's worse than dyslexia; it's insanity. In the morning it's backwards, but sometime toward the evening it corrects itself, then returns to backwards sometime over night.
-
Jul 4, 2015 6:57 AM in response to Roger Fischerby léonie,I never noticed how unstable the axis of the Earth is. Now we finally know that Apple is causing the climate change .
-
Sep 18, 2015 11:57 AM in response to bdpspby bennyjlava,I diagnosed this problem shortly after the Apple Watch came out. There is one time of day when the shadow is accurate. Then, as the day progresses, the shadow rotates about an axis defined by the points on the terminator that are closest to the two poles. This is wrong. It is the Earth that rotates about its axis, defined by the North and South Poles. On the Apple Watch, in summer or winter each Polar Region is in sunlight at one time of day and in darkness 12 hours later. In reality, it takes 6 months for that to happen. Right now it is close to the equinox, so the problem is less apparent. I hope this gets fixed in WatchKit 2.0!
