[WearOSApp] Huge Energy Consumption when using Complications

[Rhabarbara745]

AAPS 2.6.1 full release Watch: Fossil Gen 5

Using a simple WatchMaker Watchface with AAPS "Full Status" Complication leads to massive energy consumption of the AAPS wear app -> 40 % shorter battery life

Watchmaker Watchface "Full Status" Complication	AAPS NoChart Watchface

Is there a workaround or anything i can try?

[gregorybel]

I have same issue with a Huawei watch. I tried a lot of things but no solution. I use now complication from xdrip.

[dlvoy]

@Rhabarbara745 please try:

• watchface without AAPS complications (but with other frequently refreshed ones) - to exclude watchface-complication-os interactions
• does usage is the same with other complication-enabled watchfaces

Unfortunately, it seems very device & watchface dependent, and SDK gives little-to-none control over refresh.

On Huawei Watch 2 i have 8% consumption, which is not stellar but tolerable:

[Rhabarbara745]

Further tests: Another watchface with aaps complication, battery life seems to be pretty similar:

Same Watchface with step counter and 3rd party weather app complication: (+ ~10 hours)

Can't say how often step counter does update data, I hope it is comparable to aaps. If I can help with further information, logfiles etc please let me know.

[rICTx-T1D]

Iam so worry about this high baterie consuming. Iam very happy to leave the original dexcom watchface and switch to manufacture-watchface with aaps-Complication. But now, my watch lifetime is the halft. :(

Please build a patch for this problem. (I have a fossil gen5 too with last os-update)

[dlvoy]

I will work on rewriting complications refresh algorithm, but it is quite complex topic

[rICTx-T1D]

I will work on rewriting complications refresh algorithm, but it is quite complex topic

Thanks for reviewing this annoying bug. I hope you can find a solution. Many thanks in advance.