Android Auto - power consumption - hot phone
-
Majority of battery usage in the app is caused by the map rendering. I am in touch with HERE about this issue.
When using Android Auto + Phone turned on with the app, you are rendering the map twice causing significant battery usage
@Corjan-Meijerink said in Android Auto - power consumption - hot phone:
Majority of battery usage in the app is caused by the map rendering. I am in touch with HERE about this issue.
When using Android Auto + Phone turned on with the app, you are rendering the map twice causing significant battery usage
Thanks for the feedback @Corjan-Meijerink much appreciated - for now for longer runs will run with phone on usb power but will be great not to hammer the phone/battery so much when using it. Keep up the great work. I really want to move your MRA Navigation via AA from using a Zumo XT, just hoping we can get there soon as had lots of great reports from others using MRA Nav with Carplay.
-
@Corjan-Meijerink said in Android Auto - power consumption - hot phone:
Majority of battery usage in the app is caused by the map rendering. I am in touch with HERE about this issue.
When using Android Auto + Phone turned on with the app, you are rendering the map twice causing significant battery usage
Thanks for the feedback @Corjan-Meijerink much appreciated - for now for longer runs will run with phone on usb power but will be great not to hammer the phone/battery so much when using it. Keep up the great work. I really want to move your MRA Navigation via AA from using a Zumo XT, just hoping we can get there soon as had lots of great reports from others using MRA Nav with Carplay.
@Rob-Smith Thanks! Totally understand
-
@Rob-Smith Thanks! Totally understand
@Corjan-Meijerink
I have been running my phone on dark screen mode and after an 8 hr ride using Myroute app it is still showing 95% + charge -
@Corjan-Meijerink
I have been running my phone on dark screen mode and after an 8 hr ride using Myroute app it is still showing 95% + charge@Andrew That is definitely while charging and very likely too.
If the phone itself doesn't have much overhead load and the charger is decent, this is what we expect -
@Andrew That is definitely while charging and very likely too.
If the phone itself doesn't have much overhead load and the charger is decent, this is what we expect@Corjan-Meijerink Yes while charging I have had it in the past when the phone would only last for about 3 hrs while charging think dark mode helps a lot, still having problem with android auto showing roundabouts as left or right turns but phone shows roundabout correctly, very pleased with the way the app is progressing and seems to be improving for me with no drop outs on the last few rides. Keep up the good work.
-
@Andrew said in Android Auto - power consumption - hot phone:
[I] think dark mode helps a lot
Spot on. See here:
"The Purdue study found that switching from light mode to dark mode at 100% brightness [i.e. full sunlight] saves an average of 39%-47% battery power."
-
@Andrew said in Android Auto - power consumption - hot phone:
[I] think dark mode helps a lot
Spot on. See here:
"The Purdue study found that switching from light mode to dark mode at 100% brightness [i.e. full sunlight] saves an average of 39%-47% battery power."
@richtea999 @Andrew Just to confirm dark mode on the phone won't make any difference at all to consumption while using Android Auto? I believe the screen on the phone is normally Off when using Android Auto
-
Android auto in a Ford using their SYNC3, leaves the phone screen on, you have to turn it off manually.
And does then make a difference -
That sounds about right.
There is, of course, some processing power needed for the phone to interact with the Android Auto device, but that power consumption is typically much less than lighting up the screen.
-
The power consumption depends heavily on the mapdetails.
In a urban area the power consumption will be higher compared to the low detail in backroad area's
Many direction changes causes also a higher consumption because more rendering is necessaryThe difference in power consumption with screen on or off is little compared to the consumption when rendering
(I use MRA Next only on Android Auto. Every comment, suggestion, etc will be based on my usage with Android Auto)
-
The power consumption depends heavily on the mapdetails.
In a urban area the power consumption will be higher compared to the low detail in backroad area's
Many direction changes causes also a higher consumption because more rendering is necessaryThe difference in power consumption with screen on or off is little compared to the consumption when rendering
@M-Schrijver Quite true - my mistake.
The phone still needs to do the route calculations, not the Android Auto unit, and that takes reasonable processing power (too much in HERE libraries' case). -
@richtea999 @Andrew Just to confirm dark mode on the phone won't make any difference at all to consumption while using Android Auto? I believe the screen on the phone is normally Off when using Android Auto
@Rob-Smith My phone screen is on maps as well as TFT screen
-
@Rob-Smith My phone screen is on maps as well as TFT screen
@Andrew As I have already stated my phone finishes 250 ml route with a full charge, however lsst night I went into phone settings and found a tab for fast charging ticked this went out today and phone went down to 49% very quickly turned of fast charge and it soon went back up to 100% even using Spotify while using MRA.
Keep up the good work -
@Andrew As I have already stated my phone finishes 250 ml route with a full charge, however lsst night I went into phone settings and found a tab for fast charging ticked this went out today and phone went down to 49% very quickly turned of fast charge and it soon went back up to 100% even using Spotify while using MRA.
Keep up the good workJust an observation - most people when talking about power consumption seem to be basically saying - make sure your phone is plugged into a reasonably meaty charger - that way all is well.
However - something like google maps navigating for you uses significantly less power than MRA. I am hoping that this extra power burn in MRA is due to the MRA dual map render(?) of the Here maps and I have read this is being worked on to reduce this.
To me - running an app that consumes more power than other nav apps (and as such creates device heat from processing and heat from charging) a phone (on power or off power) is not ideal, as having a phone that gets physically hot while navigating is not going to be ideal for the device. Hopefully this will fall as updates come through. Keep up the great work.
p.s. I am talking from my experience while using the MRA navigation via Android Auto.
-
Just an observation - most people when talking about power consumption seem to be basically saying - make sure your phone is plugged into a reasonably meaty charger - that way all is well.
However - something like google maps navigating for you uses significantly less power than MRA. I am hoping that this extra power burn in MRA is due to the MRA dual map render(?) of the Here maps and I have read this is being worked on to reduce this.
To me - running an app that consumes more power than other nav apps (and as such creates device heat from processing and heat from charging) a phone (on power or off power) is not ideal, as having a phone that gets physically hot while navigating is not going to be ideal for the device. Hopefully this will fall as updates come through. Keep up the great work.
p.s. I am talking from my experience while using the MRA navigation via Android Auto.
@Rob-Smith
, 100%...well said. -
Just an observation - most people when talking about power consumption seem to be basically saying - make sure your phone is plugged into a reasonably meaty charger - that way all is well.
However - something like google maps navigating for you uses significantly less power than MRA. I am hoping that this extra power burn in MRA is due to the MRA dual map render(?) of the Here maps and I have read this is being worked on to reduce this.
To me - running an app that consumes more power than other nav apps (and as such creates device heat from processing and heat from charging) a phone (on power or off power) is not ideal, as having a phone that gets physically hot while navigating is not going to be ideal for the device. Hopefully this will fall as updates come through. Keep up the great work.
p.s. I am talking from my experience while using the MRA navigation via Android Auto.
@Rob-Smith said in Android Auto - power consumption - hot phone:
a phone that gets physically hot while navigating is not going to be ideal for the device.
No, it is certainly not ideal!
But keep in mind by far not all phones suffer from that problem.most people when talking about power consumption seem to be basically saying - make sure your phone is plugged into a reasonably meaty charger - that way all is well.
That is not how I intended any of the many comments I made
But truth is that many people use far from ideal charging equipment, but do not realize that. I think at least a significant part of the users that see their phone's charge not keeping up with the battery use can be helped by better charger and better cable, that sustain the charging capabilities of modern phones.That is however by no means an excuse for the high power consumption of the app (or better said: the HERE rendering engine).
