who knows?! it was my understanding, and perhaps here’s my mistake, my timezone was using DST up until this past saturday nite when we reverted back to standard time. my timezone being Eastern time, we finished Eastern Daylight Time and entered Eastern Standard Time. all across America, when local time hit 2 am on sunday morning, all timezones reverted back to Standard Time. it was just on a set date that this occurred. (plus not to mention some states and other locales here don’t recognize DST within a timezone that does)
for this reason, i thought the preview had it right and my watch was getting it wrong. when i cycled the calendar to the date that daytime savings ended it was turning on and off as expected. but i see where you’re getting at, and if that’s the case i will always show a 1 and the tag is useless for my intentions.
@Knightwing@RickyGrafixWF
spaces do not matter in Tag expressions
In fact when I do complicated tag expressions I user notepad and put them on separate lines for readability.
The [IS_DST] tag is binary there is no need to compare to 0 or 1 it is true or false I’ll try a test on my watch I have both GW5 Pro and GW6 to test on but this does sound like a system bug.
Many countries have DST not just America, but it isn’t useful for countries near the equator.
Do any of your personal complications have a default provider? They do not show on the watch if they don’t have one.
Also when you use the wearable app it comes up with None you have to scroll down to see the others.
My other thought is you have them below some other layer do they show in the WFS emulator window?
so the question i have, am i at least attempting to use the tag correctly? to turn a text box on or off depending on if my timezone is in daylight savings mode or standard time? meaning that it’ll change twice a year? or is it that my timezone in general utilizes it at some point in time so it’ll always return as true?
i always set my comps with a default, and i’m only doing it for myself so the placements are always intentional with a specific comp in mind. and this isn’t happening to just one watch face, it’s every single one downloaded on my watch. for all watch faces and all comp placements, when i try to pick any one, all slots show none. they are just about all small box comps. there is nothing else underneath to scroll or pull down in the wearable app. none is the only option.
everything was fine until i woke up about 2 days ago. i looked and it doesn’t seem i downloaded any updates to change anything. i first tried clearing the cache in both the wearable app and galaxy watch 5 manager. i then uninstalled wear app and reconnected to my phone to my watch. it was like a punch in the gut when none of that made a difference. i really thought deleting and reinstalling the wearable app was going to do the trick.
It almost seems like the same reason the EST is not showing is why the complications are hidden.
I see you have a 24 Hour Copy that is hidden. Using copies of something in your project can cause “register sharing” and hiding one could hide the original as well. If all you are seeing is the clock face then that is probably what happened.
Delete the copy and just hide components in AOD mode not make copies.
Try a very simple digital watch face with a few complications and see if that works.
i imagine the EST issue has been around, it only got noticed because of the changing of the clocks. the app stopped showing the complication options a day later on monday.
i understand what you mean about the hidden copy layers on top of other layers. but i rarely do that, i don’t use AOD so usually just to get it to pass i’ll hide everything under a black tinted circle. only sometimes do i put something a layer over it to make it stand out on the screen in AOD mode. anyway, i’ve since deleted that watch face, along with every watch face i had on the watch when i reinstalled wear app. it must be something with my phone or the app because it’s affecting every watch face. old, new, complicated or simple. watch faces that once worked as intended no longer do.
I did a test on mine and it also has DST as true so I’ll report it to the watch team as a bug and then if it is a wear 4 issue they can report it.
Regarding the complications if reinstalling the watch Faces doesn’t reset them. If you press and hold the power button longer (about 15 seconds) it should reboot a soft reset. If that doesn’t then if you re-pair the watch to the phone it would reset all
so now i’ve tried all of that. even reset the phone about three times now. got so fed up!
i happened to go to the play store to check something and i happened upon the reviews. in that list i did find at least 2 or 3 other people having similar problems in the last day or 2. the only update note is from oct 25 says “-fixed the error” (LOL) however my play store account shows that my wear app hasn’t been updated since jan 4 of this year. when i check the about tab in the galaxy app it says all of my samsung apps are up to date though. is samsung pushing things through in the background with automatic updates that i don’t know about? i would think there would be more people complaining since this update but it’s still kind of suspect i’m not the only one with this problem.
perhaps this is how the wait and see approach was successful in the past? just waiting for a patch?
yes, auto update is enabled, and that’s exactly why this has happened.
the galaxy store put out the update on the 6th. that’s when my problems started. had i known or realized that app had updated itself i could’ve saved myself a couple of resets. and hours of chatting about it here lol
Hi. I’ve already created support request for this. First, it was bugged in Pixel Watch app, then Google fixed it with an update (2 days ago). Then, Samsung issues their own Galaxy Wearable update with really funny changelog for company of this size:
Changelog: fixed the error
Don’t know what was fixed but what I know for sure they introduced same issue which was recently fixed in Pixel Watch app
