Battery drain issue

[ESpmdark]

Recently bought a new phone, so I went from an old Samsung A71 running version 3.3.2.0 to a Pixel 10.

Build: 05a3433-2026.06.04

Ever since the swap, the phone has had approximately 45-50% of its batterydrain due to AAPS background proccesses.
Ironicly, my ancient phone had more batterylife than this, so something cant be working as intended.

Not sure if you needed all the files, so I just zip'ed them up just incase.
Let me know if theres something I should check that the logfiles wont cover.

files.zip

[MilosKozak]

there is nothing special in logs. you may try to unpair watch and test

[ESpmdark]

Ill run a test without the watch connected (aswell as it being disabled within the AAPS settings).

Just a question ahead of time:
Might there have been an issue since I installed a new version on the watch, without uninstalling the old version first?
I just assumed it would overwrite it, but might there be some duplicate calls coming from the watch?

[daniilaursulesei]

I confirm that AndroidAPS drains a lot of battery, without having a watch (I use a Pixel Watch 2 only a couple of days in a month). Together with Medtronic Guardian app for sensor (the other app that really steals energy), I get less than a half of day of battery (in days when even I have one or two hours of screen time). So I can give some rough numbers from today - I use Pixel 7 Pro:

battery from 100% to 93% (screen time 12 min):
Medtronic Guardian 13% (background use 1h)
Google Play services 12% (background use 1h)
Android APS 8% (background use 1h 12 min)
xDrip 5%
...
system apps 45%

I don't have any hopes from Medtronic to optimize their app (they never consider users feedback), would be awesome if anything can be done to reduce the battery usage. I am glad to help with testing, I am not that familiar with coding Android applications, but I can catch up, so far I have experience in C; or at least collect logs or anything that might help.

Many thanks!

[ESpmdark]

On my old phone the AAPS accounted for 10-20% of the total drain (I dont activly use the phone much)
But on the new phone (same level of usage from my part), its in the range of 45-50%. Thats a extreme level of battery usage.

After I've tested without the watch, I'll roll AAPS back to the version I was using on my old phone to see if there's a difference.

I dont have the insight to judge where the majority of the battery usage from AAPS comes from. For all I know, there might be phone settings thats off on the new phone that allows AAPS to run spesific tasks more frequently on my new phone compared to the old one.

[MilosKozak]

you can also test v4 (dev branch)
it may spend more CPU when open = better UI, but it's more optimized on background

[ESpmdark]

After 2 cycles of full -> needs to be charged, without watch connected.
the range of usage ended up being 39-42%

so about a 5% drop from not using a watch, but not the main culprit.

I also realised I probably should'nt roll back to the old version, seing as that lacks the Android 16 connectivity fixes.

But I'm at a loss at what I can do here.
Fresh new phone. That lasts 9 hours on a full charge if I only ever touch my phone to give myself bolus injections.

Edit: I'm sure I could try the dev branch, but this cant be how others experience the current version?
There has to be something wrong spesificly on my phone's environment?

[vanelsberg]

After 2 cycles of full -> needs to be charged, without watch connected. the range of usage ended up being 39-42%

To rule out any other causes that drain the battery (including a bad preforming battery), you may consider installing the Accu​Battery app to see live details on battery usage?