Powerconsumption and MRA Next
-
This post is deleted! -
I don't know which HERE app you have been using, and I also don't know since which version exactly the HERE WeGo app uses this specific platform. HERE has multiple apps, not all using the same platform.
I'm using this HERE app
https://play.google.com/store/apps/details?id=com.here.app.mapsAgain, for years I'm using this app. Since 2018 at least. I know this, because I create "collections" as they call it: folders to store places. I create a collection for each holiday. Oldest collection still in my app is that of my 2018 summer holiday.
I've always used Android. On my 3rd phone since 2018, I guess.
Always had a positive charge with this HERE app.
I don't know any other HERE app.Perhaps the above statement is about what you call the "older platform". But again: I tried multiple times with the latest HERE app this week: positive charge.
I never used the old MRA App, so I cannot share my experience of that app.
It also needs to be said that by for NOT everyone experiences a negative charge while navigating with MRA Navigation Next.
I do get the remark of the other MRA member saying that you should not downplay this issue.
Nobody is saying that everybody has this issue. We know that. But a lot of people do have the issue, continously.
I can only speak for myself, but I love MRA. I would love to use it on all my rides and I would love to help. I probably only can help by sharing experiences/information.Hope this helps to improve the product.
-
@Flat-Twin-Therapy yep thats the app that I've been using and that crashed 5 times in 5km
-
@Flat-Twin-Therapy, thanks for the info. I have been test-riding this app this morning to my work, to compare the powerdrain with the MRA app. I see indeed that the drain has gotten less than the MRA app, and I am hopeful that it is a sign for a solution to arrive at MRA also. During my drive, navigating on my Pixel 8 Pro, the HERE WeGo app took about 600mA while the MRA took about 1200mA (both including system overhead). It looks though the 600mA are quite stable and independent of speed, while in the MRA app speed is a large factor. The slower you go the less power it draines. It seems larger movement of the map rises the power consumption for rendering. Sounds logical, but in the end it has to render as many frames a second as always, so I am not sure if I see the logic.
In my case, a power consumption of 1200mA is easily overcome by a decent charger and a compatible USB cable. On wireless charging, that can be a different case, with a lot more heat production. That is why I often explain that it is worth to look at the charging chain, but by no means I am downlplaying the issue.
-
Does it matter if you use offline maps?
-
@Con-Hennekens said in Powerconsumption and MRA Next:
@Flat-Twin-Therapy, thanks for the info. I have been test-riding this app this morning to my work, to compare the powerdrain with the MRA app. I see indeed that the drain has gotten less than the MRA app, and I am hopeful that it is a sign for a solution to arrive at MRA also. During my drive, navigating on my Pixel 8 Pro, the HERE WeGo app took about 600mA while the MRA took about 1200mA (both including system overhead). It looks though the 600mA are quite stable and independent of speed, while in the MRA app speed is a large factor. The slower you go the less power it draines. It seems larger movement of the map rises the power consumption for rendering. Sounds logical, but in the end it has to render as many frames a second as always, so I am not sure if I see the logic.
In my case, a power consumption of 1200mA is easily overcome by a decent charger and a compatible USB cable. On wireless charging, that can be a different case, with a lot more heat production. That is why I often explain that it is worth to look at the charging chain, but by no means I am downlplaying the issue.
Well, this confirms my doubts that Here alone is to blame for the problem. The app would be totally torn apart by users in the app stores if the battery consumption was higher than standard chargers could recharge. As a rule, navigation apps are not used to get cigarettes around the corner, although there are supposed to be
. They tend to be used for longer periods of time and the problem with HereWeGo would have been obvious for a long time.
And 1200 mA vs. 600 mA, this difference is 100%, huge.I can only agree with the other writers, the MRA planner is terrific, the imagined implementation on Next Navigation, with the icons, the selectable colors, the possible additional remarks simply great. Perhaps the team should expand to include Corjan, even the best programmer can't know everything and solve everything at once.
-
@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 -
@Charles-Rijken-0, I doubt it. If anything it will be marginally I think.
-
@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
-
@Con-Hennekens
there was a wrong translation by DeepL.
My proposal was to expand the small team arround Corjan
.
The 8D problem solving recomendation is to collect a team of minimum 5 but not more tha ythan 7 experts, best with a different view and eduacated background to prevent to run in an dead end street.The total team of MRA is just at this size and they I believe are not all IT experts.
My simple logic, working with 8Ds supporting suppliers on problem solving about the last 20 years in my Job is one of the basic questions of the 8D process.
Why do we have this problem here and not somewhere else?
Means here, why do we and perhaps Here have such battery drain and not the competive Apps from Google, Apple TT Sygic and so on?
There must be a reason. Perhaps a program code with copyright, which canβt be use.Again I will not blame somebody, I ask myself these questions.
And I know that IT is somewhat between hell and heaven like my proffession was, heattreatemt. For some Problems, I was affected and supporting too, we donβ t find the cause immediatly. I can tell stories about this in 40 years in my Job in Quality Management.Finally, the last update at the IOS Appstore for HereWeGo is three weeks old.
-
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??
-
@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