Energie verbruik hoog

[Drabslab]

@Mopetenpit I use a samsung A32 on Android.

It seems indeed partly dependent on the phone itself. My phone runs hot when using MRA.

One of the reasons why I don't use it for navigation is because I fear it will get dammaged and I don't want to interupt a holiday to go on a phone shopping spree

[Vince Hyde]

@Drabslab I have done a side-by-side test with a friend, we both have Samsung S20FE Mine is wirelessly charged and he was plugged into a USB socket on his bike and he stayed at 100% all day, and mine went below 50% both using Cardo Packtalk and listening to music, but I went for a ride at the weekend and after six hours of riding the charge was at 84% so it is much improved I think.

[Drabslab]

@Vince-Hyde said in Energie verbruik hoog:

so it is much improved I think.

Could be, but Corjan says he is still pushingn HERE to do something, so the real solution is probably not there yet.

Oh well, I hope for a solution by spring next year, until then I don't really need advanced navigation anymore

[Dave J 0]

Navigated with both iPhone 12 Pro and a Google Pixel 6 Pro (my main unit for my bike). On my previous bike using an SP Connect Plus anti-vibration wireless charge mount, both phones would drain battery steadily over a day although the drain was less if I used a wired charge from the auxiliary socket (as would be expected). However, with my new bike and having the power wired into the bike’s dedicated and live switched ‘Nav’ connection (the same setup as with my previous bike) I am now seeing both phones charge to 100% using A-B and route navigation as well as having track recording. Did a 120 mile trip yesterday with phone drain as expected when off the for pictures etc but an effective re-charge back to 100% when back on the bike.

This is a real positive change from previous and much welcome. Not sure what is helping this whether iOS17, Android14 and/or the new bike’s way of handling the wireless mounts charging needs and current draw. More testing needed by me and I am on another trip for a few days later this week. It will be a good check given the on and off requirements of the trip.

[Corjan Meijerink]

All I know at this point is that HERE has implemented small minor improvements in combination with some tweaks from our side.

The true solution is however not yet discovered by HERE.

Due to the nature of the issue, various devices will have various results. The environment in which the phone is operating is also of great impact. Not so much because the app operates differently but the overhead within the phone becomes a greater factor.

[Drabslab]

@Corjan-Meijerink annoying, a problem like that, completely out of your own control

[Corjan Meijerink]

@Drabslab very much I’m calling then twice a week and trust me, I am a pain in their ass.

[Dave J 0]

@Corjan-Meijerink You are doing a brilliant job. Keep doing what you are doing.

[Drabslab]

@Corjan-Meijerink said in Energie verbruik hoog:

@Drabslab very much I’m calling then twice a week and trust me, I am a pain in their ass.

I do trust you but things sometimes take time despite all good intentions

[Axel Härtl]

@Corjan-Meijerink Concerning energy saving: is it possible to let the display being switched off during navigation and automatically switch it on again before an important way change is ahead (komoot can do this 150 m before a turn when using it for bike (Fahrrad) navigation)? For motorbike navigation a wake-up of the display 1 or 1.5 km prior to a turn would be appropriate.

Best, Axel