WAI
Status Update
No update yet.
Comments
se...@gmail.com
Checking for bugs. Mobile isn't working properly
ve...@google.com
ve...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
lb...@gmail.com
Still exists even on Q beta 6
ar...@google.com
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
[Deleted User] <[Deleted User]>
I am also facing the same problem. @google why you guys don't allow to use internet in Networkspecifier api. It is working fine without any issue except we are unable to connect to access point or use any internet. If you allow this it will resolve many such issue. Thanks
[Deleted User] <[Deleted User]>
Add wifi networks is also not working properly. Here it is creating alone issue in user experience as many people even don't know what to do with the local hotspot connection
sa...@google.com
a) After an provides network suggestions to the platform, the platform will post a notification asking user for approval of the app when the platform sees one of the network suggestions in the scan results for the first time. If there are no scans happening in the platform, the approval will get delayed. Note: We are thinking of changing this approval mechanism to behave similar to run time permissions in a future release (i.e the app can ask the user to grant the permission when the app is opened the first time).
b) App provided network suggestions are always in a different database than user saved networks. So, even if an app provides a suggestion for a network, the wifi picker will not have that credentials because wifi picker only displays user's saved networks.
c) User's saved networks always take preference over app provided network suggestions. In the bugreport attached to the public bug, I see a saved network on the device: "TP-LINK_E406" which will always be preferred over the app provided suggestions. The API makes this clear, the app can only provide suggestions to the platform, the platform provides no guarantees on when the device will connect to these networks. If there is no other saved networks or other app provided suggestions in the scan results, then your app provided suggestion will be connected. But, when there are other candidates, the platform chooses the best candidate to connect to.
b) App provided network suggestions are always in a different database than user saved networks. So, even if an app provides a suggestion for a network, the wifi picker will not have that credentials because wifi picker only displays user's saved networks.
c) User's saved networks always take preference over app provided network suggestions. In the bugreport attached to the public bug, I see a saved network on the device: "TP-LINK_E406" which will always be preferred over the app provided suggestions. The API makes this clear, the app can only provide suggestions to the platform, the platform provides no guarantees on when the device will connect to these networks. If there is no other saved networks or other app provided suggestions in the scan results, then your app provided suggestion will be connected. But, when there are other candidates, the platform chooses the best candidate to connect to.
lb...@gmail.com
@8
a) Why the terrible UX of a notification? Why not a dialog/Activity like the rest of the framework?
This makes the user lose the context of the app.
The notifications also appear after quite a long time.
b) There should be a way for developers and/or users to add the network to the list of networks, so that it will be saved the same way, being backed-up by Google or whatever that can do it.
c) But if the saved network is wrong (incorrect password/setting), what will happen?
All I want is a way to add networks.
I also wish we could load the networks, so that we could have a proper backup&restore solution, and not the one of Google, which might fail (it failed for me just this month, when going back from Android 12 to 11, not restoring even a single network).
a) Why the terrible UX of a notification? Why not a dialog/Activity like the rest of the framework?
This makes the user lose the context of the app.
The notifications also appear after quite a long time.
b) There should be a way for developers and/or users to add the network to the list of networks, so that it will be saved the same way, being backed-up by Google or whatever that can do it.
c) But if the saved network is wrong (incorrect password/setting), what will happen?
All I want is a way to add networks.
I also wish we could load the networks, so that we could have a proper backup&restore solution, and not the one of Google, which might fail (it failed for me just this month, when going back from Android 12 to 11, not restoring even a single network).
lb...@gmail.com
@8 Also why did you remove my files? I wanted to try it out..
Description
- Steps to reproduce the problem (including sample code if appropriate).
1. Have a Wifi network around. Don't have configuration for it set on the device, so if you try to connect to it, it should ask for password.
2. Instead of using the UI of the OS, make an app that will suggest the network to be available for you. Attached sample project to do it. Basically it's based on:
fun addNetworkAndroidQ(context: Context, networkName: String, networkPassword: String? = null) {
val wifiManager = context.getSystemService(Context.WIFI_SERVICE) as WifiManager
val list = ArrayList<WifiNetworkSuggestion>()
val builder = WifiNetworkSuggestion.Builder().setSsid(networkName)
if (!networkPassword.isNullOrEmpty()) {
builder.setWpa2Passphrase(networkPassword)
}
list.add(builder.build())
val result = wifiManager.addNetworkSuggestions(list)
if (result == WifiManager.STATUS_NETWORK_SUGGESTIONS_SUCCESS)
Log.d("AppLog", "success")
else Log.d("AppLog", "failed")
}
3. Launch your app, and make it offer the new network.
- What happened.
First, nothing happens for a few seconds.
Then a notification might appear (usually it doesn't appear), asking if it's ok to use the networks.
If you choose that it's ok, still nothing occurs. The network isn't added, and you can't connect to it because it still requests for a password from you.
- What you think the correct behavior should be.
Various things:
1. Instead of a notification that appears after so long, it should show a normal screen asking if it's ok to add the network/s.
2. When choosing to accept the networks, it should allow us to connect to them. Currently it seems it doesn't do anything at all.
3. Instead of rarely asking the user, it should always ask the user.
Attached bug report too.