IssueTracker

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.

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.

Bug report attached

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.

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.

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.

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.

Add Galaxy Tab 8 ultra to the list of devices seeing this.  It's an issue with the controller firmware, not the device.

On Xiaomi Mi Smart Projector Stadia controller is also have this issue

Same issue on other devices like SteamDeck

Same here. Please fix this.

Same issue on philips oled 65 inch 936 srries

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.

Please fix this @Google

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

I'm having the same problem too, please fix this

Same issue here. Please fix it.

Same problem here, both with my Pixel 7, google tv (SONY) and Steam Link.

Same problem here with two different controller, both with my Pixel 7,

An issue on raspberry pi and Nvidia shield .
This is producing an enormous e waste problem.
Countless controllers going to waste.
A really poor Bluetooth implementation.

Shame on Google.

What is stadia controller? Help please

On Mon, Sep 30, 2024, 7:07 PM <buganizer-system@google.com> wrote:

Works fine on windows.

My stadia controller never wants to reconnect once powered off, need to re-pair it each time.

When I pair the stadia controller to my LG TV, all works fine until controller is powered off and on again, then the controller connects to my TV but pressing any button on the controller, freezes all inout on the TV (including remote control)

I strongly suspect there some general BT compability issue with the current Stadia Bluetooth firmware, it would be very nice if Google could get this resolved before they stop supporting updates.

As I cant edit: Won't reconnect issue is persitant on: Windows, Mac and Ubuntu. Re-pairing fixes it. (temporarly)

Issue my TV shows is super irritating, and it seems to be somewhat persistant, re-paring does not fix the issue. (Seems something is remembered on one of the ends)

I have encountered this issue with my users twice now. Has this been resolved yet?

I've also seen a lot more of these errors in the last few days.

I am using getScriptLock(). I get this error constantly, on both tryLock() and releaseLock(), even if there is only one instance of my script running. Why is it infeasible to fix this?

Also experienced this for the first time today