Status Update
No update yet.
Comments
us...@adixor.ro
i donnot understand why is the data the same?
ki...@google.com
us...@adixor.ro
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
us...@adixor.ro
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
us...@adixor.ro
for example,we hava 100 users.
20 users returned the same location information, longitude is 121.474000 and latitude is 31.230001。
30 users returned the same location information, longitude is 122.474000 and latitude is 32.230001。
15 users returned the same location information, longitude is 120.474000 and latitude is 30.230001。
as for Android build,all versions have it.
I dont reprodouce this issue.
what may be the cause of this issue?please
ki...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
us...@adixor.ro
Thanks for reporting this issue.
COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.
Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.
us...@adixor.ro
We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.
ki...@google.com
us...@adixor.ro
ki...@google.com
Hi, the engineering team updated that the version 9.5 has the fix, though it's not at 100% prod yet
us...@adixor.ro
There must be something wrong here ... the issue is not fixed even now, with the latest update I just got yesterday (Android Auto 10.0.632824). Is this expected and if so, when do you think we could expect the fix to reach prod? We're almost 2 months after the fix was implemented per the notes above.
Thank you!
ki...@google.com
Thanks for the update.
I have let the engineering team know this and I’ll share an update as soon as I learn more.
Description
- OS version - Android 13 March 5 patch
- Android Auto 9.0.630834
- Google play services - 23.09.14 (190400-515650844)
- all play store packages updated, car's entertainment system fully updated.
The issue below only present after Coolwalk got enabled. I only use wired Android Auto, same cable that worked for years and that works just fine with Coolwalk is not enabled.
High impact for using the navigation/AA when replicated - which is pretty quick-: the driver needs to switch his attention from driving to reconnecting the phone to the car.
Problem description
____________________
In a few minutes (between "a couple" and "several") after connecting the phone to my Renault Captur 2 2020 - using the car display - the AA taskbar becomes "frozen" in that it does not accept ANY touch input. Waze -or whatever app was in foreground at the moment- continues to work fine, but I cannot switch to any other app or doing anything that involves using the taskbar. Physically disconnecting and reconnecting the phone fixes the issue temporarily until it freezes again randomly in the future, but eventually it does happen anytime I use Android Auto. There is no other error message, on the car screen or on the phone.
The taskbar _display_ itself is not frozen, for instance the clock continues to show the right time and gets updated, it just does not accept any touch input. Only the active foreground app part of the screen accepts touch inputs.
After playing a bit more playing with it I can confirm some of the things others have mentioned (see references):
- sometimes the taskbar freezes after I use the reverse camera (thus the car head display switches to the reverse camera and when back to Android Auto the taskbar is frozen, no touch input works)
- sometimes the taskbar freezes and I also see all sorts of weirdness when I switch to the car's multimedia system and then back to Android Auto. I've seen not only taskbar freezes, but also sometimes Waze doesn't show anything (the waze section of the display is completely black), or it does show the map but the image is frozen, or the image moves very slowly, or the map is weird - does not have all the normal details on it.
- restarting the car's multimedia system does not fix the issue, it reconnects to AA but the taskbar is still frozen which points to a bug in the Android server/mobile side of things. Only fix is physically disconnecting/reconnecting the phone to the car.
Please let me know what other info I can provide to help here, though unfortunately there is no error message of any kind. I can try to take a video of this issue happening, as it is replicable in minutes.
References: