Assigned
Status Update
No update yet.
Comments
li...@google.com
Any updates on this? It's been a month already since I reported it, and it seems this crash is occurring quite frequently for my users.
so...@google.com
I am still regularly receiving reports about this issue, and it seems it has not been addressed in the latest 1.4.0-rc01 release.
li...@google.com
Seems like a fairly easy fix on our end. I'll see to that it is fixed in 1.5.
al...@coyote-group.com
Hello,
Thanks for the answer. I will check if I can get a bugreport since it's our clients that have the issue.
However, if the GMS gives the best fused location, in these cases (on Ford and at least this Fiat), shouldn't GMS provide mobile location instead of cars one ?
Best Regards,
Alexis
Thanks for the answer. I will check if I can get a bugreport since it's our clients that have the issue.
However, if the GMS gives the best fused location, in these cases (on Ford and at least this Fiat), shouldn't GMS provide mobile location instead of cars one ?
Best Regards,
Alexis
jy...@coyote-group.com
Hello,
we reproduced the issue on a Ford EcoSport with Sync3, you can find attached two bug reports generated while the bug was happening with inconsistent GPS, wrong location, no speed detected although driving around 50km/h.
We clearly saw that the bug happened when we connect the phone to the car with Android Auto. Like you said it fuses the car's GPS into the location provider.
we reproduced the issue on a Ford EcoSport with Sync3, you can find attached two bug reports generated while the bug was happening with inconsistent GPS, wrong location, no speed detected although driving around 50km/h.
We clearly saw that the bug happened when we connect the phone to the car with Android Auto. Like you said it fuses the car's GPS into the location provider.
jy...@coyote-group.com
Hello, do you have any update regarding this issue ? Thank you
al...@coyote-group.com
Hello,
Any news on this subject ?
Or maybe a workaround or another API to used ?
Best Regards,
Alexis
Any news on this subject ?
Or maybe a workaround or another API to used ?
Best Regards,
Alexis
Description
Devices/Android versions reproduced on: Samsung S20+ / Android 13
Android Auto version reproduced on: 9.1.631044-release
Hello,
We are facing strange behavior on some cars regarding GPS location.
On a Fiat 500X, as soon as we plug our phone to Android Auto, the app receive location with always the same bearing : 81°. When using only on mobile the bearing is correct.
On some Ford cars, we have a different behavior where we do no receive any location when plugged to Android Auto.
We are using the "LocationServices.getFusedLocationProviderClient(context).requestLocationUpdates" API to retrieve the location with this locationRequest parameters :
val locationRequest = LocationRequest.create()
locationRequest.priority = LocationRequest.PRIORITY_HIGH_ACCURACY
locationRequest.fastestInterval = 100
locationRequest.interval = 1000
Can you help us on these issues ?
Moreover, what's the intended behavior when connecting our app to AA, should we receive location from the car's GPS or from the phone ? Because wa are looking to use the CarsData Api to retrieve the car's gps location but regarding thes issues I'm wondering if it's not already the case.
Thanks.
Best Regards,
Alexis