Statement regarding battery usage

[RetiredWingMan]

@Marinus-van-Deudekom out of interest, do you use the direct wired charger or the one that plugs into a USB port? The direct wired charger is supposed to put out a much higher charging current.

[Marinus van Deudekom]

@RetiredWingMan I recently changed it to a usb Port with quick charging. Tomorrow I'll find out if that will be a difference

[richtea999]

@Nick-Carthew said in Statement regarding battery usage:

@Corjan-Meijerink Would it be useful to compile a list of phones that are and are not affected by excessive battery drain?

It would be good, but I can see why Corjan says 'Nah!'. There are so many variables at play that it may be quite difficult to pin it down. Some factors:

• the device
• the OS version
• the battery (is it new, is it 5 years old?)
• the charger (low power, high power, wireless, closeness to wireless charger)
• the charging cable
• the actual route
• the route options (traffic updates, offline, etc)
• the display intensity (often driven by the strength of sunlight hitting it)
• light/dark display mode
• other apps running

That's just the ones I can think of in 3 minutes. There will be others.

To pin it down, you need to restrict all but one of the variables, and then run a lot of live tests. And repeat. On several devices.

I've done such testing, and if you can test on a bench then you can pin it down a bit better. You need something called a 'dummy battery' which allows you to dynamically measure the current being taken from the battery (now a measurable power source inserted instead of the battery). But this is an app to be used on the road too, for confirmation of test results. Nightmare.

[Marinus van Deudekom]

@Marinus-van-Deudekom did a test today result
2 times 105 km drive starting with 100% battery after the trip it took 20% battery and 25% battery on the trip home so its better but still need improvement. Since 355 is not yet out for Android it was version 348

[Corjan Meijerink]

@Marinus-van-Deudekom 4.3.3 (355) is available for Android beta testers.
Version 348 is 4.3.2 and has no changes at all regarding battery usage (this is the current public release)

[Marinus van Deudekom]

@Corjan-Meijerink hi Corjan. Yesterday when I left home in the morning I looked for the 355 update and at that time it was not available. Somewhere Yesterday my phone did an auto update so I don't when that happened. So maybe in the way back home it was already updated to 355. Is there a possibility to check when the update was installed

[RetiredWingMan]

@Marinus-van-Deudekom in Android, go to the play store, account, manage apps & device, manage and it will, display the last time it was updated.

[Marinus van Deudekom]

@RetiredWingMan Sorry my friend that will only tell you when the app was last created. In this case october 28th. Since it was installed somewhere yesterday during the afternoon this will only say when the Devs created it.

[richtea999]

@Marinus-van-Deudekom said in Statement regarding battery usage:

@RetiredWingMan Sorry my friend that will only tell you when the app was last created. In this case october 28th. Since it was installed somewhere yesterday during the afternoon this will only say when the Devs created it.

This app will tell you when an app was last updated:
https://play.google.com/store/apps/details?id=com.bluckapps.appinfomanager

I'm sure there are others, but this one has minimal permissions & can be used offline if you're worried about nefarious data collection.
The only permission it requires is to read info about other apps on your device.

[RetiredWingMan]

@Marinus-van-Deudekom it works on my tablet and phone ....

[dave99]

I saw these threads on high battery usage and wanted to chime in. I'm trialling MRA and just got back from my first ride with navigation. It used 70% of my phone's battery in about 90 minutes - still extremely high.

I'm using MRA 4.3.4 on a Samsung A52S running Android 14.