Battery drain
-
Yes, i know.
But i've noticed something.
When you follow the route exactly as planned in advance. And because of this no recalculation are needed. The battery usage is almost on par with other apps like Google maps, Waze or TomTom Go.But when you have a bad route which needs multiple recalculations especially within in few kilometers. The juice is sucked out of the battery very quickly.
The other day i went from 90 to 80% in two hours. I had 2 recalculations in this time. Then i went from 80 to 50% in 30 min. In this period i had multiple recalculations in a small area (roads closed, wrong roads, etc).
The last part was 1 hour with one recalculation and went from 50 to 44%My first route this year was a very well known route (for me). The route was therefore exact. It is a 4 hour ride. No recalculations needed. I went from 100% to 95% in 4 hours. Still a bit high consumption but no problem for a riding a whole day.
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
Yes, i know.
But i've noticed something.
When you follow the route exactly as planned in advance. And because of this no recalculation are needed. The battery usage is almost on par with other apps like Google maps, Waze or TomTom Go.But when you have a bad route which needs multiple recalculations especially within in few kilometers. The juice is sucked out of the battery very quickly.
The other day i went from 90 to 80% in two hours. I had 2 recalculations in this time. Then i went from 80 to 50% in 30 min. In this period i had multiple recalculations in a small area (roads closed, wrong roads, etc).
The last part was 1 hour with one recalculation and went from 50 to 44%My first route this year was a very well known route (for me). The route was therefore exact. It is a 4 hour ride. No recalculations needed. I went from 100% to 95% in 4 hours. Still a bit high consumption but no problem for a riding a whole day.
@M-Schrijver I more or less stopped using Next because of this battery issue. I don't plan burning my phone with this tool, and I don't like ariving somewhere with an empty battery, or riding fearing that my phone will shutdown.
Still strange that this is caused by Here. Are there massive complaints on the net about the Here apps as well?
-
I don't know. I want to try the Here app also. Just for A to B and see what it does
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
I don't know. I want to try the Here app also. Just for A to B and see what it does
@M-Schrijver said in Battery drain:
I want to try the Here app also
I'm curious about your experiences if you start using it.
I use it regularly and have no problems with battery drain or a warm iPhone. -
@M-Schrijver said in Battery drain:
I want to try the Here app also
I'm curious about your experiences if you start using it.
I use it regularly and have no problems with battery drain or a warm iPhone.@Jack-van-Tilburg it is for sure better than before but as you can see there are still some issues. I hope that @Corjan-Meijerink van solve it with Here. Still hopeful
-
Yes, i know.
But i've noticed something.
When you follow the route exactly as planned in advance. And because of this no recalculation are needed. The battery usage is almost on par with other apps like Google maps, Waze or TomTom Go.But when you have a bad route which needs multiple recalculations especially within in few kilometers. The juice is sucked out of the battery very quickly.
The other day i went from 90 to 80% in two hours. I had 2 recalculations in this time. Then i went from 80 to 50% in 30 min. In this period i had multiple recalculations in a small area (roads closed, wrong roads, etc).
The last part was 1 hour with one recalculation and went from 50 to 44%My first route this year was a very well known route (for me). The route was therefore exact. It is a 4 hour ride. No recalculations needed. I went from 100% to 95% in 4 hours. Still a bit high consumption but no problem for a riding a whole day.
@M-Schrijver said in Battery drain:
Personally is suspect recalculation while riding is the main cause of the battery drain.
It is not the recalculation, it is the rendering of the map, that already has been established. Is far as I know there have not been any claims before that indicate that recalculation has an influence. Recalculations are usually very short, so I don't think that is it.
@Drabslab said in Battery drain:
I more or less stopped using Next because of this battery issue.
Some phones suffer more from it than others. I suspect mainly higher-end phones suffer more. My daily Pixel 8Pro can keeps up with cable-charging, but not with wireless charging. On my Bike I use a CAT S52 and that one has no problem at all, charges almost as fast as always on the bike. Using the app "G-CPU" is saw that the cpu cores get maxed out while dragging the map on the screen. The rendering of the map is done by functions of the HERE SDK the app makes use of.
Saillant detail: HERE's own Here WeGo app suffers from the same problem (is built on the same SDK)...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@M-Schrijver said in Battery drain:
Personally is suspect recalculation while riding is the main cause of the battery drain.
It is not the recalculation, it is the rendering of the map, that already has been established. Is far as I know there have not been any claims before that indicate that recalculation has an influence. Recalculations are usually very short, so I don't think that is it.
@Drabslab said in Battery drain:
I more or less stopped using Next because of this battery issue.
Some phones suffer more from it than others. I suspect mainly higher-end phones suffer more. My daily Pixel 8Pro can keeps up with cable-charging, but not with wireless charging. On my Bike I use a CAT S52 and that one has no problem at all, charges almost as fast as always on the bike. Using the app "G-CPU" is saw that the cpu cores get maxed out while dragging the map on the screen. The rendering of the map is done by functions of the HERE SDK the app makes use of.
Saillant detail: HERE's own Here WeGo app suffers from the same problem (is built on the same SDK)...
@Con-Hennekens said in Battery drain:
@M-Schrijver said in Battery drain:
Personally is suspect recalculation while riding is the main cause of the battery drain.
It is not the recalculation, it is the rendering of the map, that already has been established. Is far as I know there have not been any claims before that indicate that recalculation has an influence. Recalculations are usually very short, so I don't think that is it.
I did not know that.
But why is the battery usage a lot higher when there are many recalcultions in a route compare to no or nearly no recalculations.
Map renderings are not that different for a whole day/tripA little sidenote. The day i had a high battery usage. The Data usage was also enormous. Almost 500 MB for a 180 km ride. That's idiot. This means a 10 day holiday could cost me 4-5 GB's
The day with a low battery usage had also a lower data usage. Around 80 MB for also a 180 km ride. Still a high usage to my opinion. TomTom Go uses around 10 MB for the same route. But data usage is a different topic.(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
@Con-Hennekens said in Battery drain:
@M-Schrijver said in Battery drain:
Personally is suspect recalculation while riding is the main cause of the battery drain.
It is not the recalculation, it is the rendering of the map, that already has been established. Is far as I know there have not been any claims before that indicate that recalculation has an influence. Recalculations are usually very short, so I don't think that is it.
I did not know that.
But why is the battery usage a lot higher when there are many recalcultions in a route compare to no or nearly no recalculations.
Map renderings are not that different for a whole day/tripA little sidenote. The day i had a high battery usage. The Data usage was also enormous. Almost 500 MB for a 180 km ride. That's idiot. This means a 10 day holiday could cost me 4-5 GB's
The day with a low battery usage had also a lower data usage. Around 80 MB for also a 180 km ride. Still a high usage to my opinion. TomTom Go uses around 10 MB for the same route. But data usage is a different topic.@M-Schrijver said in Battery drain:
But why is the battery usage a lot higher when there are many recalcultions in a route compare to no or nearly no recalculations.
I have never noticed that, nor have there been others that mentioned that as far as I remember. You must consider that a recalculations take place in a second. How much energy would that consume in such a short time?
Map renderings are not that different for a whole day/trip
Rendering a map which continuously moves draws power continuously. Albeit in the HERE SDK too much.
The Data usage was also enormous. Almost 500 MB for a 180 km ride.
I have not been paying a lot of attention to data consumption lately. But I know from a 6 day trip last year that it was almost negligible as long as you have downloaded your maps for offline use. If you have not done that, 500MB for live caching of map data sounds like a lot, but not impossible I think. I think if you keep driving in the same areas, the data comes out of cache. Therefore you will likely not need 4 GB of mapdata for a 10 days holiday. But I can't be sure of that.
-
Yes, i know.
But i've noticed something.
When you follow the route exactly as planned in advance. And because of this no recalculation are needed. The battery usage is almost on par with other apps like Google maps, Waze or TomTom Go.But when you have a bad route which needs multiple recalculations especially within in few kilometers. The juice is sucked out of the battery very quickly.
The other day i went from 90 to 80% in two hours. I had 2 recalculations in this time. Then i went from 80 to 50% in 30 min. In this period i had multiple recalculations in a small area (roads closed, wrong roads, etc).
The last part was 1 hour with one recalculation and went from 50 to 44%My first route this year was a very well known route (for me). The route was therefore exact. It is a 4 hour ride. No recalculations needed. I went from 100% to 95% in 4 hours. Still a bit high consumption but no problem for a riding a whole day.
@M-Schrijver Good for you if that seems to work for you! That most definitely has not been my experience at all. Once I have a pre planned route before hand, I typically follow it to a tee....battery drain is crazy nuts....
-
@M-Schrijver Good for you if that seems to work for you! That most definitely has not been my experience at all. Once I have a pre planned route before hand, I typically follow it to a tee....battery drain is crazy nuts....
@GT-JWR Had the same problem yesterday with a 300ml route phone was on 100%Charge at start plugged into power on the bike, only lasted for about 130mls before it switched itself of as it was flat.
-
@GT-JWR Had the same problem yesterday with a 300ml route phone was on 100%Charge at start plugged into power on the bike, only lasted for about 130mls before it switched itself of as it was flat.
@Andrew yep...my iphone hasn't actually turned off, but it goes into a power safe type mode where the screen goes so dim, I might as well just turn it off.....for 'critical' bike trips (where I am leading), it means I have to download the routes to my XT and use it. Really hope this issue gets resolved soon.
-
@M-Schrijver said in Battery drain:
Personally is suspect recalculation while riding is the main cause of the battery drain.
It is not the recalculation, it is the rendering of the map, that already has been established. Is far as I know there have not been any claims before that indicate that recalculation has an influence. Recalculations are usually very short, so I don't think that is it.
@Drabslab said in Battery drain:
I more or less stopped using Next because of this battery issue.
Some phones suffer more from it than others. I suspect mainly higher-end phones suffer more. My daily Pixel 8Pro can keeps up with cable-charging, but not with wireless charging. On my Bike I use a CAT S52 and that one has no problem at all, charges almost as fast as always on the bike. Using the app "G-CPU" is saw that the cpu cores get maxed out while dragging the map on the screen. The rendering of the map is done by functions of the HERE SDK the app makes use of.
Saillant detail: HERE's own Here WeGo app suffers from the same problem (is built on the same SDK)...
@Con-Hennekens said in Battery drain:
I suspect mainly higher-end phones suffer more
Hai Con,
My phone is not a high end phone. Its a simple Samsung A-32.
It is not difficult, it is easy, it's a hobby
-
@Con-Hennekens said in Battery drain:
I suspect mainly higher-end phones suffer more
Hai Con,
My phone is not a high end phone. Its a simple Samsung A-32.
@Drabslab, Okay, good to know. So there must be other factors in play.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Drabslab, Okay, good to know. So there must be other factors in play.
I might be wrong but understand that a few weeks ago there were a number of days planned together with Here people to invest and hopefully solve the battery drain issue. Does anybody know the results because I haven't seen any information yet.
-
I might be wrong but understand that a few weeks ago there were a number of days planned together with Here people to invest and hopefully solve the battery drain issue. Does anybody know the results because I haven't seen any information yet.
@Arno-0 they are working on it and we have reported further feedback and provided more information. Is it painstaking? Yes. Am I doing everything in my power? Yes.
-
@Arno-0 they are working on it and we have reported further feedback and provided more information. Is it painstaking? Yes. Am I doing everything in my power? Yes.
@Corjan-Meijerink Thanks for the update. I'm convinced that you do everything that is possible to solve this issue but waiting is always difficult
-
@GT-JWR Had the same problem yesterday with a 300ml route phone was on 100%Charge at start plugged into power on the bike, only lasted for about 130mls before it switched itself of as it was flat.
@Andrew Have found information on line when a phone gets down to a certain cold temperature it will stop charging to protect the Battery. Here in England I was out in 8 deg Celsius so the wind chill factor would of been a lot colder as phone is out in the open on a mount, am wondering if this is some of the problem along with excessive Battery Drain.
-
@Andrew Have found information on line when a phone gets down to a certain cold temperature it will stop charging to protect the Battery. Here in England I was out in 8 deg Celsius so the wind chill factor would of been a lot colder as phone is out in the open on a mount, am wondering if this is some of the problem along with excessive Battery Drain.
@Andrew, I cannot speak from experience, but I think that chance is very small. For most people the heat due to the drain alone would be enough to keep the battery temperature in the charging window.
Is that really a thing for phones? I heard likewise for electric vehicle below minus 20 degrees Celsius, but never for a phone...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Andrew, I cannot speak from experience, but I think that chance is very small. For most people the heat due to the drain alone would be enough to keep the battery temperature in the charging window.
Is that really a thing for phones? I heard likewise for electric vehicle below minus 20 degrees Celsius, but never for a phone...
@Con-Hennekens said in Battery drain:
I heard likewise for electric vehicle below minus 20 degrees Celsius, but never for a phone
A battery does not know where it is installed, but does in all cases react to temperature. For phones this is usually not a problem because we usually carry it in our pocket and we act as heating system.
It also depends on the chemical composition of the battery, some are more impacted by cold or heat than other types.
It is not difficult, it is easy, it's a hobby
-
@Con-Hennekens said in Battery drain:
I heard likewise for electric vehicle below minus 20 degrees Celsius, but never for a phone
A battery does not know where it is installed, but does in all cases react to temperature. For phones this is usually not a problem because we usually carry it in our pocket and we act as heating system.
It also depends on the chemical composition of the battery, some are more impacted by cold or heat than other types.
@Drabslab, True of course, but also dependant on the implemented systems. For an EV in northern Norway it can be meaningful to limit chargeing below certain temperatures. Also they can have electrical warming available for rising the temperature of the battery before charging. For a phone battery it seems not very likely to have implemented lower temperature limits.
Anyway, if my car refuses to charge underway, I would very much like to be able to call someone...
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app
