Bug: Image opacity doesn’t work on actual watch (Watch4 Classic)
It’s working on my end with GW4 classic using a full black image dropped to 40%. It’s a bug even in the older version of WFS. You just have to remove it and reupload it again.
1 Like
how about to use numberFormat(“00.0”, [SEC_MSEC]) ? The text format string such as “0.00” or “#.##” needs to be wrapped by double quatation. It seems work well on my end.
Thank you, those quotation marks plus outer pair of brackets made it work the way I intended.
(numberFormat("00.000",[SEC_MSEC]))
Now can the MSEC part be somehow reset in the preview? I mean with moving the time slider I can only adjust the MIN or SEC part of time, but the decimals do not change at all. When I hit the play button, only the tenths change like 00.200, 00.400, 00.600, 00.800, 00.001, 00.201, 00.401, 00.601, 00.801, 01.002, 01.202, 01.402, 01.602, 01.802, 02.003, 02.203… It would take 100s of running preview to let the thousands to get to .000 again.
Complications Settings - Default Provider:
Please update the “Sunset / Sunrise” complication ID app to those released on ONE UI 4.5. The current one, under default provider, no longer works.
I had already reported this issue on September 15th.
Thank you.
Customizations:
When we set customizations such as background, graphic elements, etc. on WFS 1.2.7, we can give a name to those customizations such as “Hands”, “Time Color”, “Date”, “Stripes” etc …
Now, on WFS 1.3.8, it is set as “SET 1”, “SET 2”, “SET 3” etc …
Is there a chance to still get the custom names?
Thank you.
You can rename them in the Customisation Editor
I hadn’t noticed it. Thank you.
Galaxy Wearable App
Version 2.2.53.22101061
Galaxy Watch5 Manager
Version 2.2.12.22101351
WFS 1.3.8 Beta
Hi All,
looks like that the customizations menu doesn’t work from the Wearable app on the phone.
When we try to customize the Watch Face it freezes and returns to the previous screen.
This issue occasionally also happened with watch faces created with previous versions of WFS, but with this latest version I have never been able to access the customization menu from the phone.
Examples:
Here it gets stuck and does not apply the desired option:
**
UPDATE:
After many attempts, I was able to access the customizations from the phone. Either way it looks very unstable on this side.
Hello Matteo. I have the same versions from the Galaxy Watch5 Manager and Galaxy Wearable app. I tried watch faces that were created with WFS 1.3.8 beta and earlier. I have no problems. No freezing and I was able to access every area in customization menu from the phone. I use a Galaxy Watch 5 and Galaxy S 10 with Android 12 OneUi 4.1
Hi Silvio,
thank you.
As I had already written, it does not always happen. I also tried very simple test watch faces. Sometimes I get reports from users who encounter this issue.
With WFS 1.3.8 it looks like more unstable.
However, I repeat, it does not always happen.
(Phone Galaxy Fold 4 - Android 12 - One UI 4.1.1)
1 Like
I’m trying a face on the Pixel Watch and the screen turns off even with Always on Display. Looking at reports online it appears that this is a problem with the faces and not with the OS/Device.
I asked support but they don’t have a pixel watch to try on. And technically this would be a Pixel support issue. But giving the inconsistency of Android switches it may be that what you think is on is off.
Having said that we’d need more information about this other than the screen turns off.
Ron
Samsung Developer Relations
On the watch I have Always on Display set to on. If I use one of the faces that came on the watch then it always stays on. Using a face from this app it stays on for about 15 minutes and then the screen goes black until I tap on it. I believe the issue is due to some change in the way the Pixel Watch works however other 3rd party watch face makers that had this issue have been able to change it without a change to the OS. Since this app compiles faces for all brands of Watches I figured I’d point out the issue. It’s a minor issue but something I noticed. There is a bit more information here: https://www.reddit.com/r/PixelWatch/comments/y7n85z/custom_watch_faces_sometimes_turn_off_even_with/
The reddit article you cited has one user saying it was fixed in a pixel update but someone after that said he had the issue. Did you apply a recent update?
Since it was reported with Watchmaker watch faces also it may not be a WFS issue. Is this happening to the Watch Face you created with WFS or is it a 3rd party app. Not all 3rd party watch faces are created with WFS.
Ron
Samsung Developer Relations
The update mentioned in that thread was about the Pixel Minimalist Watchface. It’s a 3rd party watch face that had the issue and they fixed it without an OS update. The watch is on the latest firmware. There are a few other 3rd party watch faces that also have in their latest update that they’ve fixed the issue where the screen turns off with AOD turned on.
Thanks,
Pixel MInimal Watch Face was not made using Watch Face Studio it is an older wear OS watch face and may not have used the AndroidX library that were introduced this summer.
Same thing with the Watchmaker 3rd party watch that was mentioned in the reddit thread.
I’m not saying there may not be an issue with WFS designed watch faces just that I don’t know and they do use the latest AndoirdX library
Ron
Samsung Developer Relations
I am having an issue with my WFS where I only have access to like 5 complications for the small square ones, and like 10 for the big rectangle one. I tried the language thing that someone mentioned a while ago, but nothing changed. In WFS when I go to set a complication to fixed, I can only change it to watch battery. On the watch, I can also do steps, chance of rain, and UV index. Any help would be appreciated.
I have the same issue too but I don’t believe it is related to WFS 1.3.8 Beta because it is the same for watch faces I downloaded from Play Store in August. The Wearable app doesn’t have the complications but when I try on my watch itself they are there.
Weirdly I was down to just the Heart complication and rebooting and restarting watch and Wearable App and anything else a few more came back. Then overnight more appeared. I will play with it some more try that language change and factory reset it and then report it as a bug.
Thanks for pointing this out.
Ron
Samsung Developer Relations
Currently, rotate tag [SEC_MSEC]*6 is very choppy in the Preview but it’s quite smooth on actual watch. Please improve Preview’s playback mode, so we can screen recording it for marketing materials.