Hi Ron, is there any way that I can send you my two same watch faces builded with 1.3.13 and 1.4.20 that you can check them on your watch, then you can see the diferences as on my videos above is not really clear what I meant, just not possible to record properly. Thank you!
@bobota
On your WFS 1.4.20 do you have sweep on for the second hand movement? It doesn’t look like it is on is that what you are seeing? I don’t know how the effects work for you.
If you have sweep on for the 1.4.20 build I’ll contact you for the project and see what I get in Watch5 and Watch6
Ron
Samsung Developer Relations
It is sweep but with 1.4.20 work like inregular tension, not just seconds everything
I can play with it and see what I see.
Ron
Samsung Developer Relations
Can someone that is getting the memory issue give me an idea if their AOD is complex with complications and multiple graphics, etc.
Someone asked me if the AOD was an issue with the memory being over 10MB, if this issue is also with a bland AOD then that isn’t the issue.
I’m just curious.
Ron
Hi Ron,
Usually on my Watch Faces I add an option to get minimal style AOD and full data. The user chooses it from the customization menu. However, I received rejections due to “memory budget” even on watch faces with very essential AOD, with only date and time and totally black background.
Thanks
Hi guys! Maybe that’s important. I updated one of my watch faces to version 1.4.20 and got a Google error of exceeding the memory budget. Then I installed face studio 1.4.13 and compiled the project of this watch face again. Today I also received an error from Google about exceeding the memory budget. And there is no [HR] tag in the watch face, but after installing it on the device in 1.4.13, the watch face asks for permission to the heart rate sensor.
The heart rate does not affect the memory use, it is about the essential size of the watch face app when running on the device.
The issue as I understand it is.
The requirements for a Watch Face App for API 33 takes up so much space that it is almost impossible to create a watch face within the 10 MB Maximum size requirement
On this page see the Performance requirement for memory size.
I was told that a Watch Face App created with Android Studio also has the same issues this is not a WFS issue.
Ron
Samsung Developer Relations
I doubt the 10 MB Maximum size requirement relates to the storage space at all.
I did a test. I put nothing but plain digital time and date text field with default font in a face, 
Then built packages, and unzipped to see how big the resources + bloatware stored there are.
There is still at least 2MB of room for images and what not to fill to 10MB limit, which is plenty. I doubt the custom resources people add in WFS were the problem here. Its the memory budget definition. We have no means to measure the size the face will take in memory with all processes it starts and unfolds there and no warranty that it would still not be all taken without any added stuff.
1 Like
You are right I mistyped thanks for catching it. It is the runtime memory use. It was reported here that you can see the size in a Pixel watch when you check the app it is listed. I don’t know if you can do this on the emulator or not.
Performance Memory Usage - Watch Face Format WO-P8 Assets do not exceed the memory budget of 10 MB.
They are not talking about images and such as assets but the size of the Watch Face app.
I was asked developers to be patient the WFS team is talking with Google
Ron
Samsung Developer Relations
2 Likes
We hope to receive good news soon…
Thanks
I look forward to the good news. Thank you always.
Thanks Ron, we hope the memory issue is resolved soon.
And if Samsung can support developers with a separate channel for early update of wearos 4 as well as other operating system updates in the future, I think it will be much more useful.
Because developers need more time to test and find bugs when releasing watch face on new update, it will be annoying to release it and get bad feedback from customers.
Thank you very much!
Thank you Ron and SDP team. I just want to reinforce one factor, that the same exact app built with WFS1.3.13 and WFS1.4.20 - the latter gets through although it has the exact same specs. Thank you.
Same issue here, using the latest beta 1.5.7, animations aren’t smooth anymore (I am using Gyro to move and scale gradients on the background) and it looks choppy.
1.3.13, background gyro animations looks smooth:
1.5.7, background gyro animations looks choppy:
Sorry it isn’t that obvious here but that’s because I am using gradients and that kinda hides the issue because it fades away, it is more evident in person.
What watch are you running on GW4/GW5 or GW6 or doesn’t it matter
Ron
Samsung Developer Relations
I am using a Pixel Watch
I think you will need to send in an example project that duplicates this behavior. Try to cut it back to the minimum assets that duplicate the issue.
I think it is A Watch Face Studio issue if it happened with the change from 1.3.x to 1.4.x
Ron
Samsung Developer Relations
Ok thanks let me work on that should I send it to you or where is it supposed to be uploaded to?
You can open a developer support request on THIS PAGE
If you let me know the ticket number I’ll follow it.
Thanks for your cooperation.
Ron
Samsung Developer Relations