Amazfit Watch faces

... cause the variables you get from the buttons to disappear. Therefore, you must store the values ​​in the System property instead, which is
"SysProSetInt" "SysProGetInt" .

I haven't created a watch face that affects AOD selections, so I can't provide accurate recommendations.
This is all I can ...

... cause the variables you get from the buttons to disappear. Therefore, you must store the values ​​in the System property instead, which is
"SysProSetInt" "SysProGetInt" .

I haven't created a watch face that affects AOD selections, so I can't provide accurate recommendations.
This is all I can ...

... cause the variables you get from the buttons to disappear. Therefore, you must store the values ​​in the System property instead, which is
"SysProSetInt" "SysProGetInt" .

I haven't created a watch face that affects AOD selections, so I can't provide accurate recommendations.
This is all I can ...

... on my bip6.
I can't test it on the balance because now I am on my work out of my province I hope I understand correctly and it's useful for you.
Note : use SysProSetInt
https://i.postimg.cc/wT7tmFwB/Animationtest2.gif

Project open on Watch face editor for Amazfit watch on ZeppOS
aod.rar

SysProSetInt works fine.
I have never used SysProSetInt64.

... AOD background?


if you want to change the AOD background together with the normal watchface. , you must to use something like this
hmFS.SysProSetInt('js_test_int', 123)

Variables for the home screen and AOD are separate, so data must be manually saved to memory. hmFS.SysProSetInt. to use ...

... to change settings related to the AOD screen. In other cases it is not necessary. To save a setting, you usually use something like this
hmFS.SysProSetInt('js_test_int', 100)
You can read in the documentation how to use this function correctly and how to read the data afterwards
https://docs ...