Infeasible
Status Update
No update yet.
Comments
in...@gmail.com
for example, many different devices return the same longitude and latitude.such as : longitude is 121.474000 and latitude is 31.230001.
i donnot understand why is the data the same?
i donnot understand why is the data the same?
ra...@google.com
the fractional part of the location data is exactly the same.
ra...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
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:https://developer.android.com/studio/debug/bug-report#bugreportdevice
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.
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.
ra...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
ro...@gmail.com
I only aply permission android.permission.ACCESS_COARSE_LOCATION.I use android.location.Location in the program.
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
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
Description
This form is only for reporting platform issues and requests related to the Android 16 Developer Preview or Beta. Only report issues that are regressions from the behavior in Android 15. For all other issues that are also reproducible on other versions of Android, please report those issues in the AOSP issue tracker at
If the issue is caused by an app and not a platform issue, we will do our best to route the issue to the app developer. However, note that it is up to the app developer to actually address reported issues.
Before logging your issue, check to see whether it is a known issue described in the current release notes at:
or has already been reported at:
If the issue has already been reported, you can "star" or comment on the existing report if it corresponds to the issue you are seeing.
To expedite resolution of your issue, please provide as much relevant and specific information as possible. This will probably require some work from you. Most reports should include at least the following:
* Are you an Android developer?" (Y/N)
* Which Android Developer Preview build are you using? See Settings > About phone > Build number (for example AP3A.241105.008).
* Is this a regression from Android 15 to 16?
* What device are you using? (for example, Android Emulator, GSI, Pixel 9)
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
* What was the expected result?
* Can you provide the API document where this expected behavior is explained?
* What was the actual result?
* Relevant logcat output.
* Link to captured Android bug report (shared privately in Drive.)
* Optional: Link to any screenshot(s) that demonstrate the issue (shared privately in Drive.)
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Please note, bug report attachments should not be included directly in issue reports.
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes