Status Update
Comments
vi...@google.com <vi...@google.com>
su...@google.com <su...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Please provide sample apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample apk.
Android full bug report capturing
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
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.
Screen record of the issue, for clarity
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Note: Please upload the files to google drive and share the folder to
te...@gmail.com <te...@gmail.com> #3
su...@google.com <su...@google.com> #4
We have shared this with our product and engineering team and will update this issue with more information as it becomes available
su...@google.com <su...@google.com> #5
This is work as expected. As Pixel 6 support STA+STA feature, please check:
And the network callback receives OnAvailable means the connection is success. But as it's connected using the secondary STA, the Wifi settings will not display as connected.
On Pixel 4A, the secondary STA is not supported. Also if you target less than S(31), device will using the primary STA to connect, which will display in the Wifi settings.
iw...@mail.canon <iw...@mail.canon> #6
su...@mail.canon <su...@mail.canon> #7
How can the app communicate with secondary WiFi?
The app is always communicating with the primary WiFi and cannot seem to communicate with the secondary WiFi.
Is it possible to disable the STA+STA feature from the app?
We would prefer to always use the primary WiFi as we have done with previous Android devices.
su...@google.com <su...@google.com> #8
The network callback will return the actual network which is using for connecting to the requested peer, no matter primary or secondary. This is the way app use secondary Wifi to do the communication.
This not way to disable STA+STA from the App. The only way to do that is keep the app's target level less than S(31)
te...@gmail.com <te...@gmail.com> #9
su...@google.com <su...@google.com> #10
As indicated above "The network callback will return the actual network" -> any time you use ConnectivityManager to request/create a network the callbacks will return a Network object. You must use this Network object to create a socket to communicate over that specific network. If you do not then you will simply get the default network. If you're using a library to create a connection than you may be limited by the available APIs of that library.
su...@google.com <su...@google.com> #11
We are closing this issue as we don't have enough actionable information. If you are still facing this problem, please open a new issue and add the relevant information along with reference to earlier issue.
Description
val specifier = WifiNetworkSpecifier.Builder()
.setSsid(wifiName)
.setWpa2Passphrase(wifiPassword)
.build()
val request = NetworkRequest.Builder()
.addTransportType(NetworkCapabilities.TRANSPORT_WIFI)
.removeCapability(NetworkCapabilities.NET_CAPABILITY_INTERNET)
.setNetworkSpecifier(specifier)
.build()
val connectivityManager = context.getSystemService(Context.CONNECTIVITY_SERVICE) as
ConnectivityManager
connectivityManager.requestNetwork(request, networkCallback)
The dialog from the system appears correctly stating the name of the network, but when I press "Connect", it does not connect to the new network. The network callback however receives "OnAvailable" with the correct network instance.
I could not reproduce the issue on other devices (On Pixel 5 it connects properly).
Current target sdk is 31. If I change it to 30, the connection works properly.