Battery drain when navigating
-
No, also noticed with iPhone X.
The little 12-5Volt converter plug does not supply enough power to compensate for the consumption, the iPhone was empty after 1 hour (start at 45% battery charge).
But because this is known, I'm sure it will be solved soon. -
I will add my findings to this debate. Yesterday I used the app to navigate and track a route of about 120 miles. I stopped several times and paused the tracking. The original route was 66 miles and when I reached the destination I chose to edit the route and I added several route points to take me back home. The first of these new route points was RP7 so when I opened the newly edited route I gave a long press on RP7 to set as the start point. Everything worked perfectly as it should have.
My phone is an iPhone 11 and it's mounted on a Quadlock handlebar mount. I had it plugged into a 12v supply via a usb cable. My phone had about 80% battery when I started and when I got home the battery was at 100%. I also noticed that there was no significant heat despite the phone being within the Quadlock case. I had no other apps open while navigating. -
I also find battery usage to be excessive - Older Samsung Galaxy S7 - MRA Mobile Next app 3.2.9. Battery usage was so bad during one hour of navigating I had to stop it. The phone was connected for fast charging. The phone was hot. I'm hoping that once I can download maps to my SD Card and run offline that battery usage will be significantly reduced. That is how I currently run with MRA Navigation - GPS and WIFI only. No cellular service.
-
My contribution to the topic "battery charging". I drove a short distance today with the bike and Navigation Next. At the start I had a battery charge of 73%, at the finish was 64%. The route is 3.4 km long and of course only takes a few minutes. Equipment: iPhone 13 pro, iOS version 16.3.
@Mopetenpit said in Battery drain when navigating:
My contribution to the topic "battery charging". I drove a short distance today with the bike and Navigation Next. At the start I had a battery charge of 73%, at the finish was 64%. The route is 3.4 km long and of course only takes a few minutes. Equipment: iPhone 13 pro, iOS version 16.3.
Ook de batterij op mijn iPhone 13 Pro, iOS 16.3.1 loopt snel leeg. Tijdens een rit van een uur verloor de accu 2% aan volume, terwijl hij aan de USB-oplader 12V van de auto was aangesloten. De iPhone werd ook erg warm. Zo durf ik geen gebruik te maken van de app tijdens de lange ritten in de vakantie.
-
@Mopetenpit said in Battery drain when navigating:
My contribution to the topic "battery charging". I drove a short distance today with the bike and Navigation Next. At the start I had a battery charge of 73%, at the finish was 64%. The route is 3.4 km long and of course only takes a few minutes. Equipment: iPhone 13 pro, iOS version 16.3.
Ook de batterij op mijn iPhone 13 Pro, iOS 16.3.1 loopt snel leeg. Tijdens een rit van een uur verloor de accu 2% aan volume, terwijl hij aan de USB-oplader 12V van de auto was aangesloten. De iPhone werd ook erg warm. Zo durf ik geen gebruik te maken van de app tijdens de lange ritten in de vakantie.
@Corjan-Meijerink
Can you give a status update on the battery performance while navigating on Android? Has that been fixed?
Thanks! -
@Corjan-Meijerink
Can you give a status update on the battery performance while navigating on Android? Has that been fixed?
Thanks!@Rolf-Aalders actively in progress. We are working closely with HERE to improve the performance.
-
@Mopetenpit said in Battery drain when navigating:
My contribution to the topic "battery charging". I drove a short distance today with the bike and Navigation Next. At the start I had a battery charge of 73%, at the finish was 64%. The route is 3.4 km long and of course only takes a few minutes. Equipment: iPhone 13 pro, iOS version 16.3.
Ook de batterij op mijn iPhone 13 Pro, iOS 16.3.1 loopt snel leeg. Tijdens een rit van een uur verloor de accu 2% aan volume, terwijl hij aan de USB-oplader 12V van de auto was aangesloten. De iPhone werd ook erg warm. Zo durf ik geen gebruik te maken van de app tijdens de lange ritten in de vakantie.
This post is deleted! -
@Rolf-Aalders actively in progress. We are working closely with HERE to improve the performance.
@Corjan-Meijerink
Oh that is really good to hear. Thanks!
This is the only issue preventing me from actively using it. -
Today I took a drive with connected iPhone 13 to the USB port via cable. I have no idea if the phone became too hot (you can't feel it with gloves on
), but the battery logging indicates that charging stopped at 85%. The iPhone has an internal safeguard to protect the battery. I have complete confidence that everything will be fine.
-
I have just returned from a trip to Ireland where I tried to use the new MyRoute app to navigate with my Android 10 Ulefone Armour X7 Pro. I found that even with the phone on charge with a 1.5A charger it was draining the battery enough to not be able to last the day.
I switched back to using the MRA Navigator stand-alone app because that is able to allow the phone to charge up even when in use.
MyRoute app version 4.0.1 - 194
MRA Navigation version v1.6.12 -
I have just returned from a trip to Ireland where I tried to use the new MyRoute app to navigate with my Android 10 Ulefone Armour X7 Pro. I found that even with the phone on charge with a 1.5A charger it was draining the battery enough to not be able to last the day.
I switched back to using the MRA Navigator stand-alone app because that is able to allow the phone to charge up even when in use.
MyRoute app version 4.0.1 - 194
MRA Navigation version v1.6.12@Karl-Mumford are you able to try a 2.4A or 3.0A charger? The 3.0A charger works fine with my iPhone 12.
-
I have just returned from a trip to Ireland where I tried to use the new MyRoute app to navigate with my Android 10 Ulefone Armour X7 Pro. I found that even with the phone on charge with a 1.5A charger it was draining the battery enough to not be able to last the day.
I switched back to using the MRA Navigator stand-alone app because that is able to allow the phone to charge up even when in use.
MyRoute app version 4.0.1 - 194
MRA Navigation version v1.6.12@Karl-Mumford I have just see that MyRoute-app on my phone updated itself automatically yesterday so I would have been using the previous version while in Ireland
-
@Karl-Mumford are you able to try a 2.4A or 3.0A charger? The 3.0A charger works fine with my iPhone 12.
@CD130 my charger is hard wired into my bike but I could replace it, yes. However the face that the MRA navigation app uses much less power hints that MyRoute-app could probably do so too.
-
I encountered the problem after updating my Samsung 32A. What also was in a change with 'normal' working was that the connection with the phone function didn't work anymore. I can see someone was calling me but there was no sound and it wasn't possible to pick up.
Maybe this last one was the origin of battery drain, constant seeking to connect with my bleu tooth device???
Battery drain from +- 85% to 10% in 51 minutes. The Phone was very hot. -
I also have this issue, latest version installed from App Store. Just back from a 9 day tour of Europe and using my phone (iPhone 14 Pro Max) on a QuadLock wireless charger head.
With MRA running all day (regardless of the temperature) I was barely getting to the end of a days ride as the phone was sub-20% battery. For one of those days I switched to Calimoto and experienced no such issues and on the last day I had Waze running all day long, also no issues so it's definitely an MRA app problem.
On my iPhone though, switching into Low Power mode instantly fixed the issue, so I wonder if MRA is using the full 120hz screen refresh and battery saver reducing this is the key? Anyway, that solves it for me when using MRA. Like I said, all other nav apps are not a problem.
-
You might want to consider using Dark Mode next time, although judging by that screenshot, you may already be there!
Change both Map layer and App theme in the Navigation Settings. The Map layer one doesn't kick in until you actually start navigating, so ignore the default map view being, confusingly, light mode!
-
You might want to consider using Dark Mode next time, although judging by that screenshot, you may already be there!
Change both Map layer and App theme in the Navigation Settings. The Map layer one doesn't kick in until you actually start navigating, so ignore the default map view being, confusingly, light mode!
@richtea999 I’ll try that, although using Low Power mode solved the issue. I wish I knew what MRA was doing to consume so much battery though.
-
@richtea999 I’ll try that, although using Low Power mode solved the issue. I wish I knew what MRA was doing to consume so much battery though.
@Paul-41 a lot of battery drain is due to the rendering the maps on your device when online navigating. I guess the rendering remains although you've downloaded maps. The mapsupplier (Here) has to do (also) something to solve this. Google for 'battery drain' on this forum and you'll find more topics. It's under the attention of the MRA-team.
-
@Paul-41 said in Battery drain when navigating:
@richtea999 I’ll try that, although using Low Power mode solved the issue. I wish I knew what MRA was doing to consume so much battery though.
Probably redrawing the screen too often is my guess. However, that's easily written in a glib message like this, and a nightmare to fix as a developer!
One setting that might be useful would be a choice to decrease the app's screen refresh rate, so 1/5th second, 1/10th second, etc, so users could feed back on their findings. Maybe just in the beta.
I have to say I couldn't use my iPhone because it overheats and dims the screen, so I'll also be trying low battery mode this afternoon/evening. I had the same problem on a new Samsung Galaxy A54 this past weekend, so I'll also be experimenting that one too, at some point.
-
@Paul-41 said in Battery drain when navigating:
@richtea999 I’ll try that, although using Low Power mode solved the issue. I wish I knew what MRA was doing to consume so much battery though.
Probably redrawing the screen too often is my guess. However, that's easily written in a glib message like this, and a nightmare to fix as a developer!
One setting that might be useful would be a choice to decrease the app's screen refresh rate, so 1/5th second, 1/10th second, etc, so users could feed back on their findings. Maybe just in the beta.
I have to say I couldn't use my iPhone because it overheats and dims the screen, so I'll also be trying low battery mode this afternoon/evening. I had the same problem on a new Samsung Galaxy A54 this past weekend, so I'll also be experimenting that one too, at some point.
@richtea999, I happen to know that this has been tried, to as low as 40fps. It did not make any significant difference for the battery drain. It looks like something in the SDK is maxing out the processor. Slower phones seems to have less problems with battery drain, but that too is not always fully true.





















