-
Notifications
You must be signed in to change notification settings - Fork 625
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display Vendor Specific Information Elements as possible since API Level 30 #367
Comments
Please use provided feature report template, do not forget to fill all required information in the template. The information provided in the template helps to resolve issues faster. All current contributors are busy with other work. When we don't have an opportunity or time to implement a feature, we encourage developers to fork the project and become a contributor. It would be great to add new contributors to this project. |
I have looked at the issue template. There is no required information in the template that makes sense to answer for this kind of feature request: It asks whether the feature request is related to a problem (it's not), what solution i'd like (i have described it), alternatives i've considered (there are none), how i can help (i probably can't), additional context (there is none), and Device/Android information (irrelevant for a feature request). That's why i didn't use the template. Thanks for the encouragement to submit a pull request. Maybe i will, though probably not soon. |
I think it is related to #365 |
@olekstomek nah, vendor specific information is something completely different :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
It would be nice if the App displayed the vendor specific IEEE 802.11 information elements that were found in the WiFi Beacons. Android's API Level 30 introduced
ScanResult.getInformationElements()
, which can be used to query this information.The text was updated successfully, but these errors were encountered: