Galaxy Wearable / Watch - watch face loading issues

[amoledwatchfaces]

This is mostly from users using Galaxy Watches. When will Samsung finally fix WFF watchface.xml loading issues in their Galaxy Wearable app and on watch directly? How long will it take?

1. watchface.xml is passes XSD and memory-footprint validation
2. watch face does not throw any errors in logcat
3. watch face works fine on watch but also fails to load customization from time to time.

As a developer with no chance of solving this on my own, these are the only options available to me:

1. recommend user to configure watch face on watch (unacceptable to some users) or where it works and try and try again
2. explain to user that this is not watch face fault and recommend to contact Samsung
3. recommend user buying some other device where the wearable companion app is not bugged every then and now.

Tomas

[dect]

I might have gotten it wrong, but I believe you are not developing using WFS… Well, when I developed some watchfaces using the Jetpack API (the one google killed) the galaxy wearable app didn’t used to load when I used lots of “icons” for the settings even though it passed the memory test… I don’t know much about WFF but do a test, try to remove the icons for each style or add one file only, just to check if thats what causing the issue…

[Osman]

Nope he is 100 percent correct.

Any watchface made in Samsung Watch Face Studio which has many styles lets say exceeding 5 options and each option has more than 5 choices.

The Galaxy Wearabale App customization lags and forcecloses. This has been going on for last 4 years.
Neither Samsung Watchface Studio Team , Samsung have been able to do any thing to fix it.

It is such a nonsense issue of Galaxy Wearable app that should not exist. And it is beyond any watchface developers control who makes watchfaces in Samsung Watchface Studio.

Making watchfaces dumber with less options and by removing options is just not the solution. Some one should fix that damn Galaxy Wearable bug that is still present even on wear os 5 and latest Galaxy Wearable app.

[SMZ]

This issue has been around for a long time.

[amoledwatchfaces]

WFS produces WFF code so this affects all developers. Problem is, users don’t know and tend to blame developer.

@dect

lots of “icons” for the settings

You mean customization previews?

If Pixel Watch (1,2,3) can handle customization properly on both watch & wearable app then why Samsung Watch (4,5,6,7) cannot? I was hoping that Wear OS 5 will improve things. It seems that users now have more luck customizing complex watch faces with Galaxy Wearable but still, this shouldn’t be a lottery…

@sinjae @Boshra @Shamima

[dect]

Yes, customization preview.

[matze_styles4you]

Here we are again. It’s Christmas time. Many new Smartwatch users and many have no idea how to customize the watch face as the wearable app is not able to handle highly customizable watch faces.

1 star ratings incoming

It’s such a shame. Honestly.

[amoledwatchfaces]

Hi @matze_styles4you, I’ve raised the issue at Samsung Developers Support. Ticket #00029595.

If you can, please create new ticket and mention same issue (maybe also my ticket no.) I’ve uploaded apk, galaxy wearable video recordings and log files.

Google was able to fix those issues promptly so I believe Samsung is capable of fixing those too. We just need to make this "priority“.

For the logs, Support wants:

*First, make sure the Developer Option of your device is “ON” before applying the following steps.

a) Dial *#9900#, Delete Dumstate/logcat
b) Dial *#9900#, Select Debug Level to MID. This restarts the device.
c) Reproduce the issue
d) Again dial *#9900# and press “Run Dumpstate/logcat”
e) When it is finished press “Copy To SD Card (include CP Ramdump)
f) In the main (root) directory of the device file system, please look for the directory ‘log’. That directory would contain the dumpstate log file generated, having the name format: dumpstate__
g) Compress the “log” folder and share it with us

I hope Samsung can fix this.

@Shamima