Actual driving speed is WAY off
-
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?
@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.I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@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.@Con-Hennekens I have a Jeep Wrangler. The speed is wrong even without using Android Auto. It had been correct before the last update.
-
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, 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.@Con-Hennekens yes it is a Ford with SYNC 3. I will try that, thank you
-
@Con-Hennekens I have a Jeep Wrangler. The speed is wrong even without using Android Auto. It had been correct before the last update.
@Donald-LaRue, In that case I can only advise to submit a support ticket at https://www.myrouteapp.com/support
-
@Con-Hennekens yes it is a Ford with SYNC 3. I will try that, thank you
@Tony-13, I love to hear about it
-
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
-
The GPS information that Ford sends to the phone is really corrupted
-
The GPS information that Ford sends to the phone is really corrupted
@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? -
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?
-
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?
@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
