Mobile Phone Battery usage - Any News??
-
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?
-
Not every one has this issue.
My personal preference is not to use the voice prompts as I prefer to visually focus on the route line.
It is mentioned by the Dev's that having Voice Notifications enabled can be the cause of the battery drain.You don’t stop riding when you get old, you get old when you stop riding.
-
Not every one has this issue.
My personal preference is not to use the voice prompts as I prefer to visually focus on the route line.
It is mentioned by the Dev's that having Voice Notifications enabled can be the cause of the battery drain.@Lynchy67 but I'm comparing like for like, I use both voice and visual, online navigation and online maps - in both apps, and Scenic doesn't drain battery half as much as MRA.
The issue exists for everyone, just because you disable some features doesn't mean the issue isn't there, you're just not being impacted by it
-
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?
@Rajp said in Mobile Phone Battery usage - Any News??:
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?
Merely a theory, but MRA uses Flutter rather than native code which I've noticed isn't necessarily as quick/efficient. That's because there's an extra layer of code to 'detach' the Flutter code from the native UI elements.
The second possible reason is that Flutter tries to redraw only the parts of the screen that have changed (as does any decent OS/library), but it's very easy to code that poorly and end up redrawing stuff that doesn't need to be refreshed. Been there, done that! If the HERE API hasn't finely tuned the redraw logic (which admittedly takes time, skill, and a sh*tload of testing), then there will be CPU cycles and battery being used unnecessarly.
Pure guesswork, though, that theory.
-
@Lynchy67 but I'm comparing like for like, I use both voice and visual, online navigation and online maps - in both apps, and Scenic doesn't drain battery half as much as MRA.
The issue exists for everyone, just because you disable some features doesn't mean the issue isn't there, you're just not being impacted by it
@Rajp said in Mobile Phone Battery usage - Any News??:
The issue exists for everyone, just because you disable some features doesn't mean the issue isn't there, you're just not being impacted by it
I can assure you that I do not have this issue at all. My iPhone 11 charges on my Quadlock wireless charger whilst navigating with MRA.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox B8J bar buttons.
Quadlock wireless mount for IPhone 11.
Cardo Scala Packtalk Bold.
TomTom Rider 500. (In the cupboard now) -
@Rajp said in Mobile Phone Battery usage - Any News??:
The issue exists for everyone, just because you disable some features doesn't mean the issue isn't there, you're just not being impacted by it
I can assure you that I do not have this issue at all. My iPhone 11 charges on my Quadlock wireless charger whilst navigating with MRA.
@Nick-Carthew Lol - that's because you're charging the phone - try without
-
@Nick-Carthew Lol - that's because you're charging the phone - try without
@Rajp I wouldn’t expect to use any navigation app or device for any length of time without it being connected to a power supply.
Always willing to help if I can.
Triumph Tiger 1200 XRT called Tina.
MRA Navigation Next and SilverFox B8J bar buttons.
Quadlock wireless mount for IPhone 11.
Cardo Scala Packtalk Bold.
TomTom Rider 500. (In the cupboard now) -
@Rajp said in Mobile Phone Battery usage - Any News??:
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?
Merely a theory, but MRA uses Flutter rather than native code which I've noticed isn't necessarily as quick/efficient. That's because there's an extra layer of code to 'detach' the Flutter code from the native UI elements.
The second possible reason is that Flutter tries to redraw only the parts of the screen that have changed (as does any decent OS/library), but it's very easy to code that poorly and end up redrawing stuff that doesn't need to be refreshed. Been there, done that! If the HERE API hasn't finely tuned the redraw logic (which admittedly takes time, skill, and a sh*tload of testing), then there will be CPU cycles and battery being used unnecessarly.
Pure guesswork, though, that theory.
Cheers,
quick and dirty solution: get one of those rugged phones with huge battery. I´m using a Fossibot F101 Pro for approx. 14k km now since I switched to NN this March. It´s not connected to any network the whole day (except when I have to load the route in the morning or make adjustements during the day), functions as media player for my headset and of course tracks the route I´m riding. Nothing else. The battery will hold for 11 to 12 hours of riding (breaks included, during longer breaks the screen is turned off to save some battery life) with screen set to max. brightnes.
I´m prepared to have it loading while riding, because sometimes I just can´t get enough, though and 11 hours or so may not be enough. But that´s another story.^^
The complete solution cost me €150,-- for the phone, €20,-- for SP Connect Mount and another €21,35 for 10 pcs. of 3M 4936 adhesive strips (2 pcs. where acctually needed - that´s what they´re using to glue the windows into the skyscrapers in Dubai etc. and you´ll need something strong like that because original adhesive from SP connect etc. will not be able to hold that weight of the mobile^^).
Just my 2 cents.
Regards from Austria,
André -
@Nick-Carthew Lol - that's because you're charging the phone - try without
@Rajp
Charging when in use will make you phone more hot than without charging(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Rajp I wouldn’t expect to use any navigation app or device for any length of time without it being connected to a power supply.
@Nick-Carthew Why not? I want to converse my battery health and not degrade it by constantly charging it.
I did 8 hours riding using Scenic navigation with the phone without charging and battery had just over 60% left from 90% charge. Tried to do the same with MRA and was down to 5% by hour 5. Same background apps running, same route.
-
@Rajp
Charging when in use will make you phone more hot than without charging@M-Schrijver and constantly charging will degrade your battery health
-
Heavy usage were phone gets hots also.
Often little amount charging do not degrade more quick than less but longer.
A Li-ion has a max. amount of cycles. 1 cycles is from 100% to 0% and then charging back to 100%. How you divide those charges does not matter for the degradation.
A few things which speed up the degradation.- Keep the battery for a long time at 100% without using it
- Heavy usage. Drain the battery faster than you should be considering the health of the battery. Temperature of the battery is your instrument for measurement.
- Drain your battery to 0% or almost 0% before charging.
Best way to keep your battery at good health as long as possible
- Always keep your battery between 10% and 80%. Especially when not using it for a long time.
- Keep the temperature of your Li-ion battery at ALL time at room-temperature. Even when charging.
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?
@Rajp said in Mobile Phone Battery usage - Any News??:
Curious why Scenic.app doesn't suffer from this excessive battery drain whilst MRA does - both apps use HERE maps
Thoughts?Maps having the same HERE badge do not mean they come from the same source, let alone the same SDK is used. I believe HERE offers multiple SDK environments. The one MRA uses is the latest one, and that's probably why some child diseases occur. HERE's own WeGo app is built on the same SDK and shows the same problem concerning battery drain.
@Lynchy67 said in Mobile Phone Battery usage - Any News??:
My personal preference is not to use the voice prompts as I prefer to visually focus on the route line.
It is mentioned by the Dev's that having Voice Notifications enabled can be the cause of the battery drain.I cannot remember this statement, and I would be surprised if it works that way, since the problem is confirmed to be related to the rendering of the map. Are you by any chance navigating without the sound by tapping "Open route" instead of "Navigate"? If that is the case, you are actually not using the HERE map, nor the Next navigation module based on the HERE SDK
-
Heavy usage were phone gets hots also.
Often little amount charging do not degrade more quick than less but longer.
A Li-ion has a max. amount of cycles. 1 cycles is from 100% to 0% and then charging back to 100%. How you divide those charges does not matter for the degradation.
A few things which speed up the degradation.- Keep the battery for a long time at 100% without using it
- Heavy usage. Drain the battery faster than you should be considering the health of the battery. Temperature of the battery is your instrument for measurement.
- Drain your battery to 0% or almost 0% before charging.
Best way to keep your battery at good health as long as possible
- Always keep your battery between 10% and 80%. Especially when not using it for a long time.
- Keep the temperature of your Li-ion battery at ALL time at room-temperature. Even when charging.
@M-Schrijver @NICK CARTHEW impossible to charge at room temperature all the time. Just finished a 10 day, 4000mi bike trip, where ambient temps were in excess of 90degF (12degC = 54degF....at those temps, I also do not have issues) for 6 of those days. With the combination of excessive battery drain by the app, and the added heat of the charging, combined with the ambient temp rendered MRA nav 100% useless, as the phone also goes into protect mode and dims the screen and it cannot be seen. It got shelved on day 3, and Scenic app took over....flawlessly, I might add.
So as @Rajp mentions, I too, am curious as to why Scenic (and Google, and Apple to name a few others), do not have such a severe issue?
And for the critics out there that will see this as negative, perahps it is, however, the only way to improve is to know the issues. As mentioned many times, this has been a known issue for over a year, no matter if it is a HERE problem or not, it is MRA's name on the app, therefore, the critique must go there. It's like having issues with a vehicle purchased at a dealership - it is the dealership that you deal with when issues arrive, not directly with the manufacturer.
-
@M-Schrijver @NICK CARTHEW impossible to charge at room temperature all the time. Just finished a 10 day, 4000mi bike trip, where ambient temps were in excess of 90degF (12degC = 54degF....at those temps, I also do not have issues) for 6 of those days. With the combination of excessive battery drain by the app, and the added heat of the charging, combined with the ambient temp rendered MRA nav 100% useless, as the phone also goes into protect mode and dims the screen and it cannot be seen. It got shelved on day 3, and Scenic app took over....flawlessly, I might add.
So as @Rajp mentions, I too, am curious as to why Scenic (and Google, and Apple to name a few others), do not have such a severe issue?
And for the critics out there that will see this as negative, perahps it is, however, the only way to improve is to know the issues. As mentioned many times, this has been a known issue for over a year, no matter if it is a HERE problem or not, it is MRA's name on the app, therefore, the critique must go there. It's like having issues with a vehicle purchased at a dealership - it is the dealership that you deal with when issues arrive, not directly with the manufacturer.
@GT-JWR just back from a 8 days tour in Luxemburg. I found out that when navigating offline the battery drain was less
I was surprised myself. My quadlock could keep up and most of the days I ended with more than 20% power leftHonda Goldwing GL1500,
Honda Silverwing GL 650
DMD2 T865X 8 inch Android tablet using MRA next for navigation
Garmin XT (almost in the cupboard)
Samsung S20FE mounted on a Quadlock and using Android Auto in my car -
@GT-JWR just back from a 8 days tour in Luxemburg. I found out that when navigating offline the battery drain was less
I was surprised myself. My quadlock could keep up and most of the days I ended with more than 20% power left@Marinus-van-Deudekom I did notice that in offline mode, it was better - however, when ambient temp got up there, the comibination of battery drain and temp just didn't work, unfortunately...
-
@M-Schrijver @NICK CARTHEW impossible to charge at room temperature all the time. Just finished a 10 day, 4000mi bike trip, where ambient temps were in excess of 90degF (12degC = 54degF....at those temps, I also do not have issues) for 6 of those days. With the combination of excessive battery drain by the app, and the added heat of the charging, combined with the ambient temp rendered MRA nav 100% useless, as the phone also goes into protect mode and dims the screen and it cannot be seen. It got shelved on day 3, and Scenic app took over....flawlessly, I might add.
So as @Rajp mentions, I too, am curious as to why Scenic (and Google, and Apple to name a few others), do not have such a severe issue?
And for the critics out there that will see this as negative, perahps it is, however, the only way to improve is to know the issues. As mentioned many times, this has been a known issue for over a year, no matter if it is a HERE problem or not, it is MRA's name on the app, therefore, the critique must go there. It's like having issues with a vehicle purchased at a dealership - it is the dealership that you deal with when issues arrive, not directly with the manufacturer.
@GT-JWR perfectly said, of course the fan boys on here will completely disagree and say the app is perfect in every way
-
@M-Schrijver @NICK CARTHEW impossible to charge at room temperature all the time. Just finished a 10 day, 4000mi bike trip, where ambient temps were in excess of 90degF (12degC = 54degF....at those temps, I also do not have issues) for 6 of those days. With the combination of excessive battery drain by the app, and the added heat of the charging, combined with the ambient temp rendered MRA nav 100% useless, as the phone also goes into protect mode and dims the screen and it cannot be seen. It got shelved on day 3, and Scenic app took over....flawlessly, I might add.
So as @Rajp mentions, I too, am curious as to why Scenic (and Google, and Apple to name a few others), do not have such a severe issue?
And for the critics out there that will see this as negative, perahps it is, however, the only way to improve is to know the issues. As mentioned many times, this has been a known issue for over a year, no matter if it is a HERE problem or not, it is MRA's name on the app, therefore, the critique must go there. It's like having issues with a vehicle purchased at a dealership - it is the dealership that you deal with when issues arrive, not directly with the manufacturer.
@GT-JWR
I know it is not possible to keep your phone battery at room temperature. You need an Airco systeem for your battery for it. Just like an EV has.
It was a reaction to an argument where was said that some things will degrade your battery faster.In Scotland at low temperatures (8-16 degrees celcius) MRA worked flawless on part of battery usage.
Next weekend i will go to Germany with temperatures just above 20 degrees (Celcius). Let see how MRA wil perform there. -
@GT-JWR perfectly said, of course the fan boys on here will completely disagree and say the app is perfect in every way
@Rajp The app isn't perfect because of this.
I do believe that it nice to see how well people enjoy the app regardless of this significant flaw.The core of this issue is out of our power. We know HERE is working on significant improvements but due to the nature of the issue and the complexity of it, it takes longer than any of us hope.
Why does one app using HERE maps show this issue and others not? This has to do with the underlying development platform. Native vs cross-platform (we do the latter). Their own cross-platform demo app and HERE WeGo also show similar (terrible) battery usage.
I was in Amsterdam last week and spoke to some board members of HERE about the issue. They are very aware of this issue, unfortunately that is all I can do.
-
@GT-JWR perfectly said, of course the fan boys on here will completely disagree and say the app is perfect in every way
@Rajp said in Mobile Phone Battery usage - Any News??:
fan boys
I think sensible people can do without such terms easily. Save those for your facebook quarrels please.
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
undefined
