I'm in the Cevennes with my motorbike and test the different Navi-App with my iPhone.
1 Point is notable: The power consumption of the myRoute App with Apple Car-Play is much higher than the other Navi-Apps like Calimoto, Scenic, TomTom, or Google Maps.
Any plan to optimize? Otherwise I need a charging device for a whole day on my bike 
@Joro I see the same here on iPhone even without Apple Car-Play, just using the app and my iPhone in my car. Sometimes even having the iPhone at the charger my battery capacity is used faster than recharged
@Joro said in Power consumption:
Any plan to optimize? Otherwise I need a charging device for a whole day on my bike
There was a message about this last year saying they were working on it but I don't recall seeing a further update from MRA.
https://forum.myrouteapp.com/topic/4062/battery-usage-high?_=1726158954609
Andy
@Joro well known issue, and reported many, many times. The unfortunate part is that it is a HERE issue, and the developers don't seem to be able to garner much attention with them - so it appears we are stuck until they do. The issue has been around for over a year now.
Hi All,
Even in my car with CarPlay, and iPhone connected through cable (and charging by this cable) device alerts that Charging facility is disabled by high temperatutre on device.
iPhone really gets too much heated and I must put it in front of air conditioned air flow.
This does not happens if I do not use Car Play.
Best regards
Lluis Arasanz
F750GS
@Joro my bike charger stopped working due to rain and my battery went from 100 to 10 in under an hour... Luckily I have my sat nav.
@Lluis-Arasanz I have the same but without using Apple Car Play, but when I use wireless fast charging, powered by cable I don't have it.
Thank for your feedback.
Also the heat with the high power consumption will be a problem if you are on the road in warmer areas
Without fixing this issue the usage of the App wouldn't make sense for me as my trips are to long for the power consumption. It’s a pity because the App has potential...
@Joro said in Power consumption:
Thank for your feedback.
Also the heat with the high power consumption will be a problem if you are on the road in warmer areas
Without fixing this issue the usage of the App wouldn't make sense for me as my trips are to long for the power consumption. It’s a pity because the App has potential...
I see it the same way 
Hello,
I've noticed that my old Nokia 7.2 has never had any problems with excessive power consumption or overheating. No problems even on a 3 hour trip last weekend. Nor on a 5-hour tour at an air temperature of 25-27° beforehand.
All new smartphones have fantastically good graphics.
These are then sent to the display at very high refresh rates of up to 120Hz.
In addition, the entire display is constantly moving while driving, unlike with videos, where only the changed areas are displayed. And then at 24 - 60 Hz.
Perhaps it makes sense to set the refresh rate to the minimum and the resolution as well.
Both are possible on my Pixel 9, which I don't currently use for motorbike navigation.
I'm curious to see if this eases the situation.
Hallo,
es fällt mir auf, dass mein altes Nokia 7.2 noch niemals Probleme mit zu hohem Stromverbrauch oder Überhitzung gezeigt hat. Auch auf einer 3 Stunden Tour am letzten Wochenende keine Probleme. Ebenso nicht auf einer 5 Stunden Tour bei 25-27° Lufttemperatur davor.
Alle neuen Smartphones haben eine traumhaft gute Grafik.
Die dann noch mit sehr hohen Refresh-Raten bis zu 120Hz aufs Display gesendet werden.
Dazu wird das gesamte Display beim Fahren ständig bewegt, anders als bei Videos, bei denen immer nur die geänderten Bereiche dargestellt werden. Und dann mit 24 - 60 Hz.
Vielleicht ist es sinnvoll, die Refresh-Rate aufs Minimum einzustellen und die Auflösung ebenfalls.
Beides ist auf meinem Pixel 9 möglich. das ich aktuell nicht für die Motorradnavigation nutze.
Ich bin gespannt, ob dies die Situation entspannt.
Hallo,
Ik heb gemerkt dat mijn oude Nokia 7.2 nooit problemen heeft gehad met overmatig stroomverbruik of oververhitting. Geen problemen, zelfs niet tijdens een 3 uur durende trip afgelopen weekend. Ook niet tijdens een tocht van 5 uur bij een luchttemperatuur van 25-27° vooraf.
Alle nieuwe smartphones hebben fantastisch goede graphics.
Deze worden vervolgens naar het beeldscherm gestuurd met zeer hoge verversingsfrequenties tot 120 Hz.
Bovendien beweegt het hele scherm constant tijdens het rijden, in tegenstelling tot video's, waar alleen de veranderde gebieden worden weergegeven. En dan met 24-60 Hz.
Misschien is het zinvol om de verversingssnelheid op het minimum in te stellen en de resolutie ook.
Beide zijn mogelijk op mijn Pixel 9, die ik momenteel niet gebruik voor motornavigatie.
Ik ben benieuwd of dit de situatie verlicht.
@Rainer-Treichel said in Power consumption:
Perhaps it makes sense to set the refresh rate to the minimum and the resolution as well.
Both are possible on my Pixel 9, which I don't currently use for motorbike navigation.
These things have been been extensively tested at the beginning of the app project, and it made (almost) no difference, to everybody's surprise. My guess at the time was that the rendering engine does not honour the refresh rate setting of the device it runs on, but goes max capacity all the time. But if it was that simple, they would have found it by now... 
I also noticed a power consumption issue, but only when I am navigating online. If I set to offline navigation (all the rest unchanged) the consumption falls a lot, to a very reasonable level.
Hi,
as I wrote it is tested with a iPhone and compared with the other Navi App in the Apple Universe. In this framework the power consumption is very high. In the Android Universe it's might be different but that not the point for this post.
It doesn't make sense to optimize a iPhone for a single App. It should work out of the box on a similar level.
As a toureguide I don't have time to fiddle arround with the navi. It must function reliably.
@Joro well known issue, and reported many, many times. The unfortunate part is that it is a HERE issue, and the developers don't seem to be able to garner much attention with them - so it appears we are stuck until they do. The issue has been around for over a year now.
