WAI
Status Update
Comments
am...@google.com <am...@google.com>
am...@google.com <am...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
From the provided description it seems you are reporting this bug from an end user's perspective. Kindly confirm the same.
Could you please share a bugreport.
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
From the provided description it seems you are reporting this bug from an end user's perspective. Kindly confirm the same.
Could you please share a bugreport.
ki...@gmail.com <ki...@gmail.com> #3
The devices I have experienced this on are:
Samsung Galaxy S22+
Android 13
Build number TP1A.220624.014.S906USQ2BWA2
Hisense 65U6H TV with Google TV
Android 11
Build number RTT2.220118.001
I understand you are primarily looking for Pixel or AOSP specific bugs, but the problems are discussed affecting multiple Android products and if the problem is with the firmware update to the controller, I'd like to at least draw attention to it in hopes it reaches the correct people to address.
Yes, I am reporting from an end user's perspective.
I had tried to include a bug report numerous times prior to submitting this issue, but my phone would not generate it. I never received a notification that it had been generated. I will continue to try and attach it.
Samsung Galaxy S22+
Android 13
Build number TP1A.220624.014.S906USQ2BWA2
Hisense 65U6H TV with Google TV
Android 11
Build number RTT2.220118.001
I understand you are primarily looking for Pixel or AOSP specific bugs, but the problems are discussed affecting multiple Android products and if the problem is with the firmware update to the controller, I'd like to at least draw attention to it in hopes it reaches the correct people to address.
Yes, I am reporting from an end user's perspective.
I had tried to include a bug report numerous times prior to submitting this issue, but my phone would not generate it. I never received a notification that it had been generated. I will continue to try and attach it.
am...@google.com <am...@google.com> #4
Bug report attached
am...@google.com <am...@google.com> #5
It looks like you are raising this request as an Android user, rather than an Android Open Source Developer. Our Android Support team will be in contact with you shortly.
In the meantime, here are helpful resources:
am...@google.com <am...@google.com> #6
Please visit the Stadia community forum where Product Experts may be able to assist you further: https://community.stadia.com/t5/Community/ct-p/en_community . We are marking this public bug status as "Duplicate" as it will be duplicative of the feedback you provide via the suggested channel. We will no longer provide responses or updates on this bug, but rather will investigate further based on the feedback you submit.
ki...@gmail.com <ki...@gmail.com> #7
I appreciate looking into this. Stadia is completely shut down. From my understanding, they will no longer provide support. Thus why I looked for help here.
ki...@gmail.com <ki...@gmail.com> #8
The Stadia forums have been locked in read-only mode die to the shutting down of the Stadia service also. This is a widespread problem which I hope Google will fix for all former-Stadia clients.
am...@google.com <am...@google.com>
rp...@google.com <rp...@google.com>
am...@google.com <am...@google.com> #9
I'll also double up on what the original poster said, the Stadia forums are indeed in archive mode and cannot be posted to. Unfortunately they've also shut down their other social media outlets already as well. Also, I guess Google probably won't see this since they're trying to direct to that 'duplicate' but I'll post it for posterity anyway, but it doesn't matter that they linked a post saying this is a duplicate issue, as that issue number they shared is not open to the public to post on or read, so we aren't really able to even read what's going on there.
That aside, as they said, many, many, people in the community are very happy to get this bluetooth update, but there is definitely a connection issue, I'm on a Moto G Stylus (nearly stock android) on Android 11 and similarly also have the issue, apparently it's also happening on other platforms as well, but something is wrong there and it is still a Google thing.
One thing I will add however, is that on Android if you go into the device's bluetooth settings and toggle it's Input permission off and on, it will suddenly start working again. Also, the issue you marked as a duplicate above doesn't seem to be open as far into the public as this post is, I can't read it and I doubt the original reporter of this issue can either.
That aside, as they said, many, many, people in the community are very happy to get this bluetooth update, but there is definitely a connection issue, I'm on a Moto G Stylus (nearly stock android) on Android 11 and similarly also have the issue, apparently it's also happening on other platforms as well, but something is wrong there and it is still a Google thing.
One thing I will add however, is that on Android if you go into the device's bluetooth settings and toggle it's Input permission off and on, it will suddenly start working again. Also, the issue you marked as a duplicate above doesn't seem to be open as far into the public as this post is, I can't read it and I doubt the original reporter of this issue can either.
ki...@gmail.com <ki...@gmail.com> #10
Add Galaxy Tab 8 ultra to the list of devices seeing this. It's an issue with the controller firmware, not the device.
am...@google.com <am...@google.com>
rp...@google.com <rp...@google.com>
am...@google.com <am...@google.com> #11
On Xiaomi Mi Smart Projector Stadia controller is also have this issue
ki...@gmail.com <ki...@gmail.com> #12
Same issue on other devices like SteamDeck
Description
* What was the expected result?
Notification should come every time the app is running.
Note : Disconnect the wifi which previously connected using wifiNetworkSuggestion api.
* What was the actual result?
Sometimes(very occasionally) notification is prompting to connect suggested wifi. After approved to that wifi suggestion notification then the suggested wifi is connected successfully.
* Which Android Beta build are you using?
Android Q Beta 3
* What device are you using?
Pixel
* Can you provide the API document where this expected behavior is explained?
Here is the sample code I have:
-----------------------------------------
final WifiNetworkSuggestion suggestion =
new WifiNetworkSuggestion.Builder()
.setSsid("SSID_NAME")
.setWpa2Passphrase("PASSWORD")
.build();
final List<WifiNetworkSuggestion> suggestionsList = new ArrayList<WifiNetworkSuggestion>();
suggestionsList.add(suggestion);
final WifiManager wifiManager = (WifiManager) getApplicationContext().getSystemService(Context.WIFI_SERVICE);
final int status = wifiManager.addNetworkSuggestions(suggestionsList);
if (status == WifiManager.STATUS_NETWORK_SUGGESTIONS_SUCCESS) {
Log.i("Main","Success");
}else {
Log.i("Main", "Not Success");
}
-----------------------------------------
Permission that i have:
------------------------------
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
------------------------------