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?
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ā¦
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.
WFS produces WFF code so this affects all developers. Problem is, users donāt know and tend to blame developer.
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ā¦
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.
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