Statement regarding battery usage

[Corjan Meijerink]

@richtea999 Just improving Very curious about what they come up with.

Hahaha, and why that?

[richtea999]

@Corjan-Meijerink said in Statement regarding battery usage:

@richtea999 Just improving Very curious about what they come up with.

Hahaha, and why that?

setState() forces a stateful widget to redraw, and if HERE have them all over their code, it may cause many unneeded redraws of the screen. It's quite hard work to keep those calls to the absolute minimum.

You may request or define a 40 frames/second, but if they're calling setState() 100/second, it's going to be doing the 100 regardless of your requested setting.

But I'm teaching Grandma to suck eggs, as they say!

Well done for twisting their arm. Fingers crossed it gets properly fixed.

[Corjan Meijerink]

@richtea999 ah like that

[Flat Twin Therapy]

Thanks Corjan!! Really looking forward to that fix!! It really prevents me from using MRA for navigation. Tracking is fine. Navigating drains my Android phone.

[paul69]

excellent news thanks

[Lynchy67]

@Corjan-Meijerink

Personally, I have no battery issues!

I set the display Brightness to 50% in Android.
Using a 2.1 Amp Din Plug the Battery is always showing an increasing percentage.
I never use any Voice commands in the app.
And only use the following settings in the app.

Phone is Samsung S21+

[Rob Verhoeff]

Today, during a ride of over 2 hours, I didn't experience any battery issues. I started with a capacity of only 25%. By the end of the ride, it charged up to over 80%. I didn't have any other apps running in the background, only the Bluetooth connection with the Sena was active.

[Herman 1b]

@Rolf-Aalders said in Statement regarding battery usage:

Thanks Corjan!! Really looking forward to that fix!! It really prevents me from using MRA for navigation. Tracking is fine. Navigating drains my Android phone.

Likewise. On a recent trip I was forced to switch back to the old Navigation app as my battery was going down too fast (despite charging).

I thought the old Navigation app also used HERE. Is that not the case?

[Corjan Meijerink]

@Herman-1b yes, correct. But a very different version / platform than it is now so they cannot be compared.

[Fred Gilbert]

@Lynchy67

I used your settings and it seemed to work. The charge state held more or less steady.

[Drabslab]

Yesterday, on samsung A32, and with phone on the charger all the time, the battery went empty in 2 hours with only navigation running.

OK, it was only 50% charged to start with but nevertheless...

Travelling to Austria on thursday will be with TomTom, I am affraid.

I hope HERE comes with a good solution soon.

[Marinus van Deudekom]

@Corjan-Meijerink today Another test. This time with my Samsung S20FE in the car with Android radio. I started the trip with 90% Battery and after a 2 hours drive it ended with 73% battery. All the time the phone was hooked up with a usb cable to a 2 amp socket. The phone was quite warm but not steamy hot.
So its better than it was before the update but still the battery gets drained
Hopefully it will be better in the near future

[richtea999]

@Drabslab said in Statement regarding battery usage:

OK, it was only 50% charged to start with but nevertheless...

Not a solution, but a work-around might be to investigate your charger current output, and consider a more powerful one if it's less than say 2A.

The A32 can manage a max input wattage of 15W, so that's a current of around 3A max.

[Con Hennekens]

@richtea999, good suggestion!

[martin-phogel.de]

I did my first lap with the app today. I use a Samsung S8+, the power comes from a BAAS mini-USB, which only supplies 1A.
The brightness was permanently set to max, besides MRA I was running the Garmin Drive app (with Bluetooth connection to my Zumo XT) and an app to monitor the battery charge.

On the MRA app, route navigation and tracking were on all the time. The map settings were Theme=Light, Type=Normal, Building=Off.

I started with a battery charge of 80%, after two hours the battery was fully charged. So no problems with battery capacity at all.

Maybe the power consumption depends a lot on the smartphone model?

[Con Hennekens]

@Martin-Wilcke said in Statement regarding battery usage:

Maybe the power consumption depends a lot on the smartphone model?

For sure, and probably mainly on the internal graphics engine. It feels like the graphics engine is used 100% whatever settings are used. Less capable graphical logic leads to less problem with drainage. Therefore the problem is likely more eminent on high(er)-end phones.

[Shawn Graham]

@Corjan-Meijerink this issue appears unresolved. I'm still having an issue.

How do we fix it. I can't use if battery runs out before I get where I'm going

[Corjan Meijerink]

@Shawn-Graham well that’s correct
They have made minor improvements but yet the real fix still needs to be found!

[TomOnTour]

Hi @Corjan-Meijerink!

Many hanks for the update.

Thomas

[Adventurer86276]

I been using Scenic app and it used HERE maps in Version 3 and did not have any battery drain issues. I tried MRA because Scenic changed to OSM in V4 and currently has too many bugs from the switch. MRA does have a real problem with battery usage, I could easily use Scenic (V3=HERE maps) while running waze and spotify in the background and my phone would be charged to 100% very often by the time I reach stops or even at the end of the ride, I went on a very short ride the other day with MRA and spotify/waze in the background and by the time I got home my battery was at 69%... So a real problem given it's always charging and despite the thread here talking about HERE being the culprit, Scenic did not have this problem. Very unfortunate as I liked MRA but can't use it for long rides because of the very high battery usage.