Powerconsumption and MRA Next

[Marinus van Deudekom]

@Peter-Schiefer Maybe it's something that @Corjan-Meijerink could use while talking to Here to solve the problem
By the way looking at the reviews of Here WeGo its mainly very negative

[Con Hennekens]

@Charles-Rijken-0, I doubt it. If anything it will be marginally I think.

[Con Hennekens]

@Peter-Schiefer said in Powerconsumption and MRA Next:

Perhaps the team should expand to include Corjan,

I am not sure what you mean by this. Corjan already is head of development.

@Marinus-van-Deudekom said in Powerconsumption and MRA Next:

Maybe it's something that @Corjan-Meijerink could use while talking to Here to solve the problem

The beauty is that Corjan is in close contact with HERE's development department since a few weeks, instead of talking to customer service... It is MRA itself that brought the awareness to HERE that their own app suffers a battery drain problem. The better behaviour I saw in the HERE WeGo app this morning could well be the result of MRA's direct contact with HERE development. Now let us hope the same improvement will be rolled out to the customers SDK soon

[Mzokk]

The issue must be very phone defendant at least in Android. I didn't think that the navigation app was usable on AA until version 4.1.3-312. I use it via Android Auto on an Africa Twin with an old Motorola G7. Its slow to load but once loaded it works fine. I did a 120 mile route last week with it and the phone (cable connected) went from 85% to 100% on my return. For earlier iterations of the App the phone struggled to maintain charge. For speed I generally use my Garmin Zumo XT and I've also been experimenting with the AA version of OSMand+ which does not have power consumption issues. Why can't MRA use the OSM map set if the Here maps are so problematical??

[Con Hennekens]

@Mzokk said in Powerconsumption and MRA Next:

Why can't MRA use the OSM map set if the Here maps are so problematical?

Navigation apps are built around an SDK that is provided by the map provider. Switching to another map provider would basically mean developing a new app. The choice for HERE is partly based previous experience with a pretty good SDK (in the Previous Navigation app) and partly on the Flutter IDE that is compatible with the SDK. Basically that means that the app for IOS and Android can be built simultaneously with the same code. So the choice for HERE was not taken lightly, and in the light of everything getting better, probably the same choice would be made again today