AOD battery drain - how to optimize

[fluxkompensator]

I don't understand how to create energy saving AOD WF in detail. Of course there should be only small areas with information (light), low update frequency (e.g. no seconds) and no data that need to check sensors.
I created those 2 WF and compared the power consumption. With the analogue one I have a power consumption of ~20% per day, with the digital one it's only around 12% on my Amazfit Balance. My usage profile is the same with both WF (almost all sensors on, AOD on, avg. 30-45 GPS/day,....)

https://amazfitwatchfaces.com/balance/view/6522
https://amazfitwatchfaces.com/balance/view/5006

Why is there so a huge difference?
Could anybody please check if this happens on another device as well?
What could be improved to get a low energy AOD?

Thank you for any help

[asoo]

I don't understand how to create energy saving AOD WF in detail. Of course there should be only small areas with information (light), low update frequency (e.g. no seconds) and no data that need to check sensors.
I created those 2 WF and compared the power consumption. With the analogue one I have a power consumption of ~20% per day, with the digital one it's only around 12% on my Amazfit Balance. My usage profile is the same with both WF (almost all sensors on, AOD on, avg. 30-45 GPS/day,....)

https://amazfitwatchfaces.com/balance/view/6522
https://amazfitwatchfaces.com/balance/view/5006

Why is there so a huge difference?
Could anybody please check if this happens on another device as well?
What could be improved to get a low energy AOD?

Thank you for any help

Regarding the watch faces you mentioned, the analog watchface that you said consumes more power, in my opinion, might be because it uses "smooth seconds" on the home screen. This function is similar to displaying an animation, which consumes more power than a analog normal watchface. However, for the AOD , from what I've seen, I think both watchfaces maybe consume similar amounts of power. Therefore, I believe the higher power consumption of the analog watchface is likely due to the home screen display.

However, I haven't tested this; it's just a guess.
If you want to test it, try changing the analog watchface to use
"Normal Analog" for both the home screen and AOD and see if it consumes less power.

[fluxkompensator]

Thanks for your reply. I really appreciate!
You're correct, on analog WF the normal screen is with smooth second, but for the AOD (only minute & hour visible) I used "normal analog", not "Pro analog".
Since I see all my desired information (day, date & time) on the AOD, I do NOT use the normal screen often, sometimes even not for days. That is why I'm very confused about the big difference between the two WFs.

But it's an interesting aspect that not the AOD but the normal screen could be the reason. I will give it a try and change the normal screen to "normal analog" as well.

Thank you!

[MarioLie]

I don't understand how to create energy saving AOD WF in detail. Of course there should be only small areas with information (light), low update frequency (e.g. no seconds) and no data that need to check sensors.
I created those 2 WF and compared the power consumption. With the analogue one I have a power consumption of ~20% per day, with the digital one it's only around 12% on my Amazfit Balance. My usage profile is the same with both WF (almost all sensors on, AOD on, avg. 30-45 GPS/day,....)

https://amazfitwatchfaces.com/balance/view/6522
https://amazfitwatchfaces.com/balance/view/5006

Why is there so a huge difference?
Could anybody please check if this happens on another device as well?
What could be improved to get a low energy AOD?

Thank you for any help

Your problem won't be in the display, but in the background applications running on your watch.

Of course there's a difference in what the always-on display contains compared to the fully active view, and I'll give you a tip - find someone who has Garmin watches and look at the night display of information and I think you'll understand where the problem lies. The white display is only 40% on a black background #000000. White will only show information about sleep, time, alarm settings, and day display, nothing more.

Image AOD

[asoo]

Thanks for your reply. I really appreciate!
You're correct, on analog WF the normal screen is with smooth second, but for the AOD (only minute & hour visible) I used "normal analog", not "Pro analog".
Since I see all my desired information (day, date & time) on the AOD, I do NOT use the normal screen often, sometimes even not for days. That is why I'm very confused about the big difference between the two WFs.

But it's an interesting aspect that not the AOD but the normal screen could be the reason. I will give it a try and change the normal screen to "normal analog" as well.

Thank you!

I'm happy to help.
After you testing finish, Please let we know the results. This will be helpful for others who want to create an AOD similar style to yours, providing them with information to help them make informed decisions about their own AOD creation.

Thank you.

[fluxkompensator]

Your problem won't be in the display, but in the background applications running on your watch.

Of course there's a difference in what the always-on display contains compared to the fully active view, and I'll give you a tip - find someone who has Garmin watches and look at the night display of information and I think you'll understand where the problem lies. The white display is only 40% on a black background #000000. White will only show information about sleep, time, alarm settings, and day display, nothing more.

Image AOD

Thank you!
So you mean that the applications, that run on the normal screen (e.g. steps, weather, compass,...), are also somehow active (in background) when the AOD is on?
For the AOD I generally do not use information that need to be updated regularly, but just minute, hour, date and weekday (so even less than your Garmin example), and mostly with a reduced level (e.g. 127 instead if 255).
But if applications of the "normal screen" are also active during AOD, this could be a reason. I will test it.
Thank you.

[MarioLie]

Your problem won't be in the display, but in the background applications running on your watch.

Of course there's a difference in what the always-on display contains compared to the fully active view, and I'll give you a tip - find someone who has Garmin watches and look at the night display of information and I think you'll understand where the problem lies. The white display is only 40% on a black background #000000. White will only show information about sleep, time, alarm settings, and day display, nothing more.

Image AOD

Thank you!
So you mean that the applications, that run on the normal screen (e.g. steps, weather, compass,...), are also somehow active (in background) when the AOD is on?
For the AOD I generally do not use information that need to be updated regularly, but just minute, hour, date and weekday (so even less than your Garmin example), and mostly with a reduced level (e.g. 127 instead if 255).
But if applications of the "normal screen" are also active during AOD, this could be a reason. I will test it.
Thank you.

You're welcome, and yes, that's the case even when AOD is active, everything continues running in the background. This means step counting, recovery, sleep tracking, etc. Most importantly, the watch constantly verifies if the phone is available and checks for new information. So even though it looks like we have a power-saving mode, the watch is actually running at 80% in the background.

[fluxkompensator]

So in terms of energy it would be better to design normal watch faces with less information panels and AOD faces with little areas an no unnecessary information, right?
I was not aware that applications that are shown in normal screen influence the energy consumption in "AOD mode". I thought that all those services run in background, depending on what is set in settings, independently of what is shown on "normal screen".

[MarioLie]

As I showed in the picture above, simple readable information on the alarm clock - alarm time/no alarm, do not disturb, sleep and info about the day and time, nothing more.

[fluxkompensator]

I'm happy to help.
After you testing finish, Please let we know the results. This will be helpful for others who want to create an AOD similar style to yours, providing them with information to help them make informed decisions about their own AOD creation.

Thank you.

here´s an first update:
I reworked the WF just with "normal" analog hands (no smooth seconds) both for home screen and AOD, additionally I deleted almost all applications from home screen, so that there is just hour, minute, second, day, date, month and battery available.
=> minimalistic version 3.1.3 here: https://amazfitwatchfaces.com/balance/view/6522

Currently the battery drain with my usage profile is around 8.x and 9.x % per day (Sasha´s battery tool), so that´s fantastic for me.

Maybe I will built other test versions with more applications (like steps / HR / ...) on the home screen and test how this will influence the battery drain.

THANK YOU guys for your help!