New Beta! (v3.2.15) Android Auto!

[M. Schrijver]

It was just a test route. But maybe i will gonna ride this route today. I need to break-in my front and rear breakpads + the new front tyre.

[Bart De Medts]

I notice that many people chose the red navigation arrow

[Stefan Hummelink]

@Bart-DM said in New Beta! (v3.2.15) Android Auto!:

I notice that many people chose the red navigation arrow

Ya, provides the best contrast imho!

[Corjan Meijerink]

@M-Schrijver looks absolutely amazing

[M. Schrijver]

Ok.
I've done my first ride. Mixed feelings.
It is certainly better than the old app.
I had problems with auto skipping viapoints. But I'll try to focus on Android Auto because this is new for this version.

1. Audio.
   I only have navigation directions when i play audio/music form an other app. When I set the audio/music app on pause, MRA will not give audible directions anymore.

Possible Solution:
Android Auto has a separate channel just for navigation sound.

The volume off the navigation directions is too low.

The sound of the lady who is giving the directions is terrible (just like the one of Google Maps). Please add other voices

2. Routeline and Vehicle arrow.
   Until approx. 40 kph both the routeline and arrow can pretty good follow the movement of the vehicle

Until 60-70 kph. The blue routeline is mostly smooth in it's movement but it is structual 20-100 meter behind the vehicle (sometimes a larger distance). The Arrow is not smooth for a large percentage of the riding times the arrow jump from point to point. It falls behind and then jump suddenly on the blue route line. Sometimes it "overtakes" the blue routeline to my exact location

When i ride like 100 kph. Both the blueline and arrow cannot follow the speed of the vehicle and falls constantly behind. Both needs to jump to the actual almost every kilometer.

B.T.W. My smartphone is mounted in open air for better GPS reception and cooling of the smartphone

3. Enery Consumption.
   The energy consumption is high. Screen stays on many times. The charger cannot deal with the energy consumption. The battery is slowly draining

[Vince Hyde]

@Corjan-Meijerink I have attempted to use Android Auto in my car today Audi on two different phones and I just get a black screen .

[Nick Hodge]

@Vince-Hyde This may not be the issue as I don't have android, but I think a limitation in this first release (i thought I heard on the zoom call last night), is you must have the app loaded and running before connecting to Android Auto??

Don't shoot me but I think that was the case??

[M. Schrijver]

I did get the black screen also while i had the app loaded and active on my smartphone. After a couple attempts, it worked

[Bart De Medts]

@Corjan-Meijerink Can we expect an update this week? I am going to the Ardennes on Friday and wonder if I can expect an update before I leave.

[Con Hennekens]

@Bart-DM, With Corjan OoO until the 29th I would not bet on it. But you never know...

[Bart De Medts]

@Con-Hennekens Ow I thought he was on holiday until today ️

[Corjan Meijerink]

@Bart-DM definitely not I’m returning end of the week. Joost is working hard on the remaining issues!

Scheduled update for June 1st

[Bart De Medts]

@Corjan-Meijerink Still enjoy your vacation!

I would like to see the following things updated:

• be able to plan routes of more than 600 km;
• the delay of the navigation arrow (did I really write that now? ).

Other things are nice, but not a requirement to use the navigation properly

[tuercadura]

@Jörgen

[Bart De Medts]

@Corjan-Meijerink A map update in the app, is that something that is automatically pushed by HERE or does it require intervention from the MRA team?

[flamingm0e]

1. When can we get miles/feet working properly? In the USA, we don't use yards.

• On Android Auto, it shows yds in place of miles, but speaks miles.
• On the dash of my Bronco Sport it has an indicator of the next navigation instruction. It is in miles and feet...

2. Samsung Galaxy S23+. When I just use the main screen to look/follow on the map, it's fine. As soon as I try to navigate somewhere, it's incredibly slow to update the location, it doesn't find me on the road I am on, it sometimes puts me 1 mile away on another road that I'm not on...

3. I haven't been able to use any of the betas. Like any of them. On 4 different Android devices. The constant crashing, and now it can't seem to navigate me anywhere.

[Con Hennekens]

@Matt-Flaming, can you check the settings of the location services in Android? I usually disable what Google calls "enhanced positioning by WiFi" or equivalent. It actually adds nonsense to the GPS stream if you are carrying a hotspot. If your Samsung puts you in a place where you are not, could you check the location in an other app, to see if it is off there too?

The constant crashes of the app seems to be a long gone problem, so I am surprised by your comment. Can you pinpoint under what circumstances, at what actions, or in which screens or menus that happens? maybe a video or screenrecording of when that happens? I can't help you there, but that info will assist the MRA team in assessing what goes wrong.

[flamingm0e]

@Con-Hennekens Location works fine with literally every other app.

I regularly use Waze, TomTom Go/AmiGo/Go Ride, Maps, AutoZen, Locus, Gaia, CalTopo, Kurviger, and Guru. A couple more not worth mentioning as well.

Location works fine when I open MRA. It's only when it starts the "Navigation" is it completely and utterly wrong. If connected to Android Auto, AA is not AS laggy, but still lags behind. Not to mention all the inaccurate distances (yds instead of miles).

This isn't a problem with the device. It's only the navigation in MRA.

[Con Hennekens]

@Matt-Flaming, Okay, I am afraid you need help from someone more technical then me. It is a bit odd though that there are so many Beta testers of which none of them is experiencing these displacements. That's why I was thinking of a phone problem before a app problem. Maybe Corjan has an idea. He will be back from holiday next week.

[flamingm0e]

@Con-Hennekens I've tested with 3 different devices.

My only guess is that it's always related to the unit of measurements, or because I'm in USA.