Fixed
Status Update
No update yet.
Comments
mt...@gmail.com
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.
ja...@google.com
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.
mt...@gmail.com
Bug report attached
ja...@google.com
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:
mt...@gmail.com
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.
mt...@gmail.com
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.
ja...@google.com
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.
mt...@gmail.com
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.
mt...@gmail.com
Add Galaxy Tab 8 ultra to the list of devices seeing this. It's an issue with the controller firmware, not the device.
ja...@google.com
On Xiaomi Mi Smart Projector Stadia controller is also have this issue
mt...@gmail.com
Same here. Please fix this.
ja...@google.com
Same issue on philips oled 65 inch 936 srries
ki...@gmail.com
Same here, HP 255 G9 Laptop, Linux OS.
It pairs and works fine, but then next time I want to use it, I need to remove it and pair again.
It pairs and works fine, but then next time I want to use it, I need to remove it and pair again.
ad...@google.com
Please fix this @Google
st...@restena.lu.c-00o5u7nb.appstempdomain.goog
Did anyone have luck with this guy's "fix"? Posting below:
Here is what worked for me:
* forget all Stadia controller in BT settings
* (Re-)Pair stadia controller (make sure that it works fine)
* Restart CCwGTV through settings. Do not turn off the controller. (check that everything works after restart)
* Restart CCwGTV once again. While CC is restarting, power off and power on the controller. (check that everything works)
* Now power off then power on the controller while keeping CC on.
Once those actions are performed, CC should not lose Stadia controller anymore.
Source:https://www.reddit.com/r/Stadia/comments/10g279t/comment/j5oe1j6
Here is what worked for me:
* forget all Stadia controller in BT settings
* (Re-)Pair stadia controller (make sure that it works fine)
* Restart CCwGTV through settings. Do not turn off the controller. (check that everything works after restart)
* Restart CCwGTV once again. While CC is restarting, power off and power on the controller. (check that everything works)
* Now power off then power on the controller while keeping CC on.
Once those actions are performed, CC should not lose Stadia controller anymore.
Source:
am...@stl.tech
I'm having the same problem too, please fix this
am...@stl.tech
Same issue here. Please fix it.
Description
We also referred the google team suggestion provided from below case,
Below is code snippet where we implemented the API to save the App Suggested Network into user saved network list.
List<WifiNetworkSuggestion> suggestionsList = this.parameter.getWifiMgr().getNetworkSuggestions();
Bundle bundle = new Bundle();
bundle.putParcelableArrayList(Settings.EXTRA_WIFI_NETWORK_LIST,(ArrayList<? extends Parcelable>) suggestionsList);
final Intent intent = new Intent(Settings.ACTION_WIFI_ADD_NETWORKS);
intent.putExtras(bundle);
startActivityForResult(intent, SPWConstants.STATEENUM.RETRY_AFTER_DEL_WIFI.ordinal());
And we are getting below FATAL EXCEPTION after implemented the above code.
Below is the exception details,
10-21 15:08:30.554 1000 17170 17170 D AndroidRuntime: Shutting down VM
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: FATAL EXCEPTION: main
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: Process: com.android.settings, PID: 17170
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: java.lang.IllegalStateException: More than one auth type set
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.net.wifi.WifiConfiguration.getAuthType(WifiConfiguration.java:2494)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at com.android.settings.wifi.addappnetworks.AddAppNetworksFragment.isSavedWifiConfiguration(AddAppNetworksFragment.java:334)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at com.android.settings.wifi.addappnetworks.AddAppNetworksFragment.filterSavedNetworks(AddAppNetworksFragment.java:399)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at com.android.settings.wifi.addappnetworks.AddAppNetworksFragment.createContent(AddAppNetworksFragment.java:260)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at com.android.settings.wifi.addappnetworks.AddAppNetworksFragment.onViewCreated(AddAppNetworksFragment.java:230)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.Fragment.performViewCreated(Fragment.java:2921)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentStateManager.createView(FragmentStateManager.java:562)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1324)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1477)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.moveFragmentToExpectedState(FragmentManager.java:1555)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1608)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.BackStackRecord.executeOps(BackStackRecord.java:455)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.executeOps(FragmentManager.java:2333)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.executeOpsTogether(FragmentManager.java:2117)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.removeRedundantOperationsAndExecute(FragmentManager.java:2055)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.execPendingActions(FragmentManager.java:1957)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:3056)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:2990)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:251)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:458)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1435)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:8024)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3475)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-21 15:08:30.557 1000 17170 17170 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
Which breaks the APP functionality. Kindly check the issue and let us know your comments to proceed further.
Below is the code snippet we used to create/add network suggestion.
List<WifiNetworkSuggestion> suggestionsList = new ArrayList<WifiNetworkSuggestion>();;
final WifiNetworkSuggestion suggestion1 =
new WifiNetworkSuggestion.Builder()
.setSsid(SSID)
.setIsAppInteractionRequired(true)
.setIsHiddenSsid(true)
.setPriority(1000)
//.setCredentialSharedWithUser(true)
.setWpa2EnterpriseConfig(wifienterpriseconfig)
.build();
suggestionsList.add(suggestion1);
retcode = parameter.getWifiMgr().addNetworkSuggestions(suggestionsList);
From the above code, we also tried with the option to include/exclude the code ".setCredentialSharedWithUser(true)" while creating wifi suggestion but we got the same error and flow was broken for both scenarios.
Kindly confirm here, whether the option "setCredentialSharedWithUser(true)" should not be used when we try to add the app suggested network into user saved network?
Please Confirm us, to add the app suggested network into user saved network - whether we need to add the network suggestion into wifiManager as per the below line ? or it is not required?
retcode = parameter.getWifiMgr().addNetworkSuggestions(suggestionsList);
Kindly clarify us, the popup to add the App suggestion network into user saved network list should be displayed foreground from Wifi Picker or it can be displayed foreground to the App?
Note : In our scenario, after Suggestion Notification popup for App Suggested network is displayed to user then we are trying to create the popup to add the App suggestion network into user saved network list. Kindly let us know if it is expected case?
We have attached the bug report for your reference.
And below are cases that we already discussed with Google team regarding various issues repoted from saving the App suggested network into user saved network list.
App Suggested Network is not preferred for connecting in Android 11 while saved unmetered network is available
App suggested network is not saved even we implemented the API setCredentialSharedWithUser(boolean) into Android 11(Beta3)