Actual driving speed is WAY off

[Donald LaRue]

@Con-Hennekens yes. The actual speed is off with or without the android auto.

[Tony 13]

On mine Adroid Auto makes all the difference. Correct speed is shown on the app if Android Auto is not used. Should I raise a ticket to get this looked at?

[Donald LaRue]

@Tony-13 yes, please. Speed is incorrect on my phone even when phone is not connected to android auto.

[Con Hennekens]

@Tony-13, Do you by any chance own a Ford?
I use Ford Sync3 and experienced very strange behaviours concerning the speed indication... Corjan pointed me to the Android Auto setting on the phone and asked me to disable the right on location services (for the Android Auto app). As contra-productive as that seems, the app falls back to its own location service, instead of that from your AA device. That, for me, solved my problem.

[Donald LaRue]

@Con-Hennekens I have a Jeep Wrangler. The speed is wrong even without using Android Auto. It had been correct before the last update.

[M. Schrijver]

In my case the actual driving speed fluctuate enormous from time to time.
From -- to 180 km/u and back in less than than a second. This causes also strange visual behaviour on the screen. The navigation arrow jumps over the screen in this situation.

MRA Next is the only navigation app which has this behaviour.
Never saw this with: Google Map, Waze, TomTom Go, Amigo and Flitsmeister.

[Tony 13]

@Con-Hennekens yes it is a Ford with SYNC 3. I will try that, thank you

[Con Hennekens]

@Donald-LaRue, In that case I can only advise to submit a support ticket at https://www.myrouteapp.com/support

[Con Hennekens]

@Tony-13, I love to hear about it

[Tony 13]

Finallly checked. As suggested I turned off location permissions in the Android App. Now MRA displays the correct speed on my phone and on the Android App screen in my car. Thank you

[Corjan Meijerink]

The GPS information that Ford sends to the phone is really corrupted

[Con Hennekens]

@Corjan-Meijerink, seemingly yes. I don't mean to be overly critical (you know me ) but it is funny to see that MRA app and HERE WeGo (based on the same HERE SDK) are suffering from it, while other apps like gMaps and FlitsMeister seem not to suffer from it. There seems to be a link to the HERE SDK?

[BJ]

I am also suffering from this bug.

Speed in app and with Android Auto is not correct, seems to be freezing at the speed that I drive when I opend the app.

Any chance that this bug is being solved?

[Con Hennekens]

@BJ, could well be but I really don't know. Corjan has just released a new public version, as far as I know it contains also an SDK update. Please try and let us know

[BJ]

I tried this morning. Unfortunately the actual speed is still not shown correctly.

Speed is toggling between 7 and 14 km/h, also when standing still...

Issue occurs in Android Auto, and in the app on my Samsung A36 telephone.

[Con Hennekens]

@BJ said in Actual driving speed is WAY off:

Speed is toggling between 7 and 14 km/h, also when standing still...
Issue occurs in Android Auto, and in the app on my Samsung A36 telephone.

Am I correct when I assume that it happens on the phone ONLY when connected to Android Auto in your Ford?
I had the exact same thing. I disabled the permission for location services on the Android Auto app in the Android Settings. That way the MRA app falls back to using the phones GPS data, that solved it for me.

[BJ]

Correct. When I disconnect my phone from Android Auto the actual speed is showing correctly on my phone in MRA.

I also issued a ticket at MRA today, and their advise is to disable location access for Android Auto on my phone. Seems to be an issue with Ford automobiles.

Bit strange though, Google Maps and TomTom both work fine with location access for AA enabled.

[Con Hennekens]

@BJ, yes that is strange. Obviously there is a workaround, and some big 1000+ developer teams found it.