Network Discovery Service browsing lacks api to specify IPv4 or IPv6 services [382215755]

Infeasible

Bug

NeedsInfo

Status Update

No update yet.

Description

jb...@craftsmanshipsoftware.ca

created issue #1

Dec 4, 2024 03:02PM

Both Avahi and Apple's zeroconf apis allow the user to specify if they want to discover IPv4, IPv6 or both services. Android NDS browsing is randomly returning IPv4 or IPv6 services. discoverServices() appears to take "int protocolType" but has no effect.

Comments

ra...@google.com <ra...@google.com> #2Dec 5, 2024 06:39AM

Assigned to ra...@google.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?

ra...@google.com <ra...@google.com> #3Dec 12, 2024 04:42AM

the fractional part of the location data is exactly the same.

jb...@craftsmanshipsoftware.ca <jb...@craftsmanshipsoftware.ca> #4Dec 18, 2024 03:56AM

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.

ra...@google.com <ra...@google.com> #5Dec 20, 2024 09:48AM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

jb...@craftsmanshipsoftware.ca <jb...@craftsmanshipsoftware.ca> #6Dec 21, 2024 07:58PM

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

ra...@google.com <ra...@google.com> #7Dec 24, 2024 12:07PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ra...@google.com <ra...@google.com> #8Dec 31, 2024 07:57AM

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.

ra...@google.com <ra...@google.com> #9Jan 7, 2025 03:10AM

Status: Won't Fix (Infeasible)

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.