Status Update
No update yet.
Comments
vi...@google.com
i donnot understand why is the data the same?
vi...@google.com
hw...@kentech.ac.kr
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.
vi...@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.
vi...@google.com
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
hw...@kentech.ac.kr
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
hw...@kentech.ac.kr
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.
hw...@kentech.ac.kr
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.
Description
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
=====
Dear,
I am Hyunwoo Lee, an assistant professor at KENTECH in South Korea.
I was a postdoc at Purdue from 2020-2022 and I and my colleagues at Purdue developed the security testing framework for the VoWiFi smartphones.
With it, we have analyzed security of VoWiFi android phones and have found some issues.
We want to share the result with you. Most of the issues are not directly related to the Android framework, but we are reporting the results because those phones are running over Android and just in case there is something that we have missed.
I have shared the report with android-bugreport@google.com through Google Drive.
Please let me know if it does not work or if you have any question.
Sincerely,
Hyunwoo Lee.
Security_Issues_of_VoWiFi_Android_Smartphones.pdf -