New update! (4.4.0)
-
Hi everyone!
Coming week update 4.4.0 will be released to the public!
This update might not have the most spectacular changes but I'm sure you will be happy with it! Why? After a very long time of working together with HERE we identified why some users still experience a massive amount of battery usage. This update is the first in which that is reduced!
The first? Yes! More updates to come for sure regarding issue now that we know where to look. After testing on a lot of different devices we see a relative improvement of ~20%. Note: not all devices had this issue and not all devices will experience the same improvement.
That said, I am confident everyone will have a smoother app experience and less strain on the CPU / GPU leading to better battery life and charging capabilities.
What else is new in this update:
- The route "eat-up" is now seamless meaning that the route line won't have a weird animation anymore where the progress (part you drove) was ahead or far behind your current position
- Fixed an issue where the start page map position would not show your heading correctly
- Fixed issue where tap to recalculate would not trigger
- Support new SilverFox firmware (soon to be released by them, solving issue where long press a button also resulted in short press being triggered)
- Improved contrast in menu's when navigating them with a bluetooth controller
- Minor improvements to waypoint skip algorithm
- Internal updates
Curious to learn your experiences regarding the battery usage! Do know that more improvements will be coming
Cheers,
Corjan -
Thank you!
-
Hi everyone!
Coming week update 4.4.0 will be released to the public!
This update might not have the most spectacular changes but I'm sure you will be happy with it! Why? After a very long time of working together with HERE we identified why some users still experience a massive amount of battery usage. This update is the first in which that is reduced!
The first? Yes! More updates to come for sure regarding issue now that we know where to look. After testing on a lot of different devices we see a relative improvement of ~20%. Note: not all devices had this issue and not all devices will experience the same improvement.
That said, I am confident everyone will have a smoother app experience and less strain on the CPU / GPU leading to better battery life and charging capabilities.
What else is new in this update:
- The route "eat-up" is now seamless meaning that the route line won't have a weird animation anymore where the progress (part you drove) was ahead or far behind your current position
- Fixed an issue where the start page map position would not show your heading correctly
- Fixed issue where tap to recalculate would not trigger
- Support new SilverFox firmware (soon to be released by them, solving issue where long press a button also resulted in short press being triggered)
- Improved contrast in menu's when navigating them with a bluetooth controller
- Minor improvements to waypoint skip algorithm
- Internal updates
Curious to learn your experiences regarding the battery usage! Do know that more improvements will be coming
Cheers,
Corjan@Corjan-Meijerink Today I drove a by MRA generated Roundtrip. Driving 3:15 hours and 115 km. Tour went well. Just one "turn left" had to be "turn right" because after 100 meters I had to make an U-turn. Not dramatic. Recalculation was quick and sufficient when I deliberately left the tour.
"Eat-up" of the route line was OK.
Battery usage is indeed improved. Iphone became, let's say, warmer as handwarm. Display was turned of and phonecover was open. Environment temperature was approx. 24 degrees Celsius in a cabrio with open roof (of course). Sky was cloudy/sunshine. So, not to much direct sunshine on the phone. Loading process wasn't stopped because of temperature.
Very eager to learn next update in this.
Test was done on Carplay with an Iphone 13, MRA 4.4.0 - 404
-
Looking forward to trying it. I had 4 days / 900 miles 1500 km round Scotland last week using Android Auto on my Honda Africa Twin Adventure sports via a Motorola Edge 40 Neo and the (last iteration) of the app was faultless including routes designed with optional loops (no via points only shaping) two of which I skipped and the app continued perfectly after the next waypoint was encountered. I still have a Garmin XT mounted on the bike but its only used for custom proximity shown POI's and I run a confirmation track of the MRA route I'm running. Many thanks. Oh and it was 27C on Mull last Friday. Most unusual!!
-
I use the app every day during my current 4-month trip. Last month in Iraq, I put the phone in the driving wind to cool it down. As soon as I arrived in a city with the usual congested traffic, the phone overheated and started giving a less and less clear picture until it stopped completely. Just when you need it the most. So I am very happy that the problem is found and my phone no longer overheats. To prevent overheating it also helps a little if you stop charging the battery.
-
ik ga morgen gelijk testen, 360km dus dat hoop ik te voltooien met mra
-
Vandaag uitvoerig getest. Mooi op te zien dat de blauwe lijn nu gelijk loopt. Had wel meerdere keren dat de app vastliep rondom stops. Ik maakte gebruik van CarPlay.
-
The battery usage is certainly improved. The phone was cooler today and less trouble to keep the battery charged. Good job.
-
There is an Autozoom in Android Auto. I can clearly see this on my screen. But how it works? I don't know. It looks random.
My setting is "Both" (speed and directions/crossings). Biggest complain. The crossing with a white arrow shows up in the screen only 120-140 meters before you arrive at the crossing. Too late.The blue line and position indicator are looking good. Did not see any strange things. Smooth graphics. Good job.
There is still a clear delay in real position and position on screen. Combine this with the issue of the Auto zoom and you can understand there is an issue.What i noticed about the delay in the position indicator compared to other navigation apps.
Other navigation apps are more on par with the real position. But when you take a wrong turn it takes those other apps a longer time before they noticed you took a wrong turn.
It seems all navigation apps have the same issues but those other apps do a more aggresive correction to keep it the indicator better on par with your real position.
