Assigned
Status Update
Comments
lb...@gmail.com <lb...@gmail.com> #2
If it's all about security/privacy, please consider other ways to still let it be possible somehow, just in a different way.
For example, instead of "addNetwork", make an Intent that will be sent to the system, which includes all of the networks that need to be added, and then when we send the Intent, the OS will show a a screen showing all of the networks that are going to be added, and allow the user to confirm all or specific ones.
It's unfair that such an API that existed for a very long time and was used well by various apps is now completely gone, without any alternative.
For example, instead of "addNetwork", make an Intent that will be sent to the system, which includes all of the networks that need to be added, and then when we send the Intent, the OS will show a a screen showing all of the networks that are going to be added, and allow the user to confirm all or specific ones.
It's unfair that such an API that existed for a very long time and was used well by various apps is now completely gone, without any alternative.
lb...@gmail.com <lb...@gmail.com> #3
The new screen should also have a checkbox "keep added networks even after removal of app", as I've found that if you remove the app, it's planned to also remove the networks :
https://issuetracker.google.com/issues/136806098
lb...@gmail.com <lb...@gmail.com> #4
And there shouldn't be a restriction of number of added networks, as this can ruin the whole point of restoring list of saved networks:
https://issuetracker.google.com/issues/136787273
lb...@gmail.com <lb...@gmail.com> #5
Oh , and it seems that even though it's possible to add an open network to connect to (no password), it isn't possible to add WEP one?
https://issuetracker.google.com/issues/136600127
How could that be?
What should apps behave when they are in a place that has WEP protected Wifi network ?
How could that be?
What should apps behave when they are in a place that has WEP protected Wifi network ?
ve...@google.com <ve...@google.com>
ve...@google.com <ve...@google.com> #6
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ar...@google.com <ar...@google.com> #7
We've deferred this issue for consideration in a future release. Thank you for your time to make Android better. In case you want to provide more information with respect to this bug, please file a bug in AOSP via "https://goo.gl/TbMiIO
ad...@google.com <ad...@google.com>
bn...@google.com <bn...@google.com>
lb...@gmail.com <lb...@gmail.com> #8
@7 Fixed how? Added something in android-x ? Added something on Android S ?
Description
"This method was deprecated in API level 29.
a) See WifiNetworkSpecifier.Builder#build() for new mechanism to trigger connection to a Wi-Fi network. b) See addNetworkSuggestions(java.util.List), removeNetworkSuggestions(java.util.List) for new API to add Wi-Fi networks for consideration when auto-connecting to wifi. Compatibility Note: For applications targeting Build.VERSION_CODES.Q or above, this API will always return -1.
"
I don't seem to be able to add a network anymore because of this.
Is it really a better API for adding a network?
Suppose I have SSID, password and type of network (open, WEP, WPA...), is it still possible to add a network?
If not, please bring it back.
I've succeeded so far using addNetwork function, but I don't seem to find how to do it otherwise.
It is useful in various apps. Wifi backup apps, sharing, batch restore...