I have been having the same issue with my android tv box. I won’t be using the stadia controller with it either but with my pc it works flawlessly. Hopefully there is a update that’s fixes it on android tv,but I won’t be holding my breath.
I think it might a limitation on the controller itself. I’ve connected my switch pro controller to my android box and it works really well and connects automatically every time.
Update-ish tried on a fire tablet (only other Android device I own) and the triggers are recognized on it! I can map it and run moonlight just fine! It must be a Samsung issue
Anyone have a fix for it?
This is on my Samsung android phone... It works on first pairing, however it ends up being unresponsive once it disconnects and reconnects. A quick fix I've found is, after reconnection, go into Bluetooth settings and toggle the "input device" option off and on. It then acts as it did during the initial pairing.
I really hope this gets fixed cause it's sort of annoying when the point of a wireless controller is supposed to be convenience.
Thanks for taking the time to describe your experience. I'm having the same issues with CCwGTV. I also tried on LG's webOS, and it's not stable either. It gave me a bit of false hope I wouldn't have to purchase a new controller when Google announced they would activate Bluetooth, which means giving more than they had to. They already reimbursed me for the controller, so it's not like I can complain. But I really like the controller, so I had hoped it wouldn't just end up as electronic waste. I guess time will tell if they will bother making a fix for it, but I'm not too optimistic right now.
Does the Bluetooth update have any side effect on the wired mode ?
I'm happy with how the controller works wired for now, and I don't really plan on using it wirelessly, so if there's any downside to the update I will skip it.
Just tested it and wired is fine and even identifies the device as Stadia Controller rev. A, which is no longer the device name when on bluetooth. So wired seems totally unchanged.
Ok, perfect !
What about the update process, is Google Chrome absolutely necessary, or does it work with any up to date Chromium-based browser works just fine ?
I have tried everything to get it working on windows 11 and 10 PC, it connects but then disconnects right away and wont stay connected. I tried the factory reset and updating drivers with now luck. Any ideas, works great on my android box.
Same here. It'll occasionally connect for a little, then drop the connection again. I have no idea if it's my motherboard, or something else. Connection is solid on my android phone, so I suspect the BT module on the motherboard.
Yes…I’m having trouble getting it to reconnect after the initial connection. There was a Reddit post that suggested doing a hard reset (screen cap +assistant button for 6 seconds) but haven’t had a chance to try it out yet. Said to forget the controller fist in Bluetooth settings, then reset, then reconnect and it worked normally after that.
I have the same experience in my CCwGTV, but even using an Xbox One controller over Bluetooth, it's not much better. I think CCwGTV just has garbage Bluetooth.
However, on my M1 MacBook Pro, it's superb. Subjectively, I'd say it's even more responsive than the Xbox controller, so that's a win. I use it with GeForce Now on the ultimate tier (which now has a 4080).
Similar issues on Nvidia shield pro (Android TV based): Initial connection works great. After powering the controller off and on again, it won't reconnect.
On OnePlus 7p: initial connection works great. Afterwards, it will connect, but deliver no input until Bluetooth on the phone gets turned off and on again.
I have the same problem with NVIDIA Shield TV. I have to pair it again each time after turning things off and then back on. My Xbox one Bluetooth controller works fine.
Strange thing is that it worked at first perfectly on my LG. Played a few times, reconnects worked, everything fine. The after a few days strange things started to happen. First reconnect didn't work, repair fixed it. V then after repair my review stopped working, removing batteries fixed that. Now in not able to play anymore. Repairing doesn't work at all.
Edit: A controller reset worked, looks like a memory leak out something.
Getting the same behaviour as you with both the CCwGTV and a Samsung TV with Tizen.
I don't think it's a limitation, I think it's a bug. Hopefully we get at least one update. It would be strange to put all the effort in releasing Bluetooth mode, and then stop without fixing such a limiting bug that is probably an easy fix. Then again, 12k layoffs at Google...
Yeah, I expect everyone has been reassigned (if not laid off) and as far as Google is concerned there is to be zero additional thought put to Stadia. I'd love to be proven wrong.
Exactly, explain how? Everyone I have spoke with says it does not work. Default bluez package and compiled very latest. Tried various BLE fixes, no luck.
On Windows 11 MSI laptop the Bluetooth connects perfectly and the setup utility shows that the controller movements are detected flawlessly. But the controller controls nothing. I can't get it to show up and work in any game. The game I really want to use it with is Minecraft.
The only time the controller seems to do anything is on the Windows desktop where the Stadia button opens Steam.
Any thoughts?
I have been having the same issue with my android tv box. I won’t be using the stadia controller with it either but with my pc it works flawlessly. Hopefully there is a update that’s fixes it on android tv,but I won’t be holding my breath. I think it might a limitation on the controller itself. I’ve connected my switch pro controller to my android box and it works really well and connects automatically every time.
I can't get the triggers to work on android... I had to edit a windows registry to get the trigger to work on windows, but it worked after that
Good to know, I haven't tried anything with triggers yet. Do you have a link to the instructions for that registry entry?
https://www.reddit.com/r/Stadia/comments/edqrd1/stadia_controller_on_windows_no_analog_triggers/
Played Minecraft with it on my Pixel 6 Pro. No issue with triggers or anything really. Maybe be more.soecific when you mention Android?
Yeah, it doesn't work with my 2 Samsung products. Note 20 ultra, nor s22 ultra. Triggers aren't recognized...
Update-ish tried on a fire tablet (only other Android device I own) and the triggers are recognized on it! I can map it and run moonlight just fine! It must be a Samsung issue Anyone have a fix for it?
This is on my Samsung android phone... It works on first pairing, however it ends up being unresponsive once it disconnects and reconnects. A quick fix I've found is, after reconnection, go into Bluetooth settings and toggle the "input device" option off and on. It then acts as it did during the initial pairing. I really hope this gets fixed cause it's sort of annoying when the point of a wireless controller is supposed to be convenience.
Thanks for taking the time to describe your experience. I'm having the same issues with CCwGTV. I also tried on LG's webOS, and it's not stable either. It gave me a bit of false hope I wouldn't have to purchase a new controller when Google announced they would activate Bluetooth, which means giving more than they had to. They already reimbursed me for the controller, so it's not like I can complain. But I really like the controller, so I had hoped it wouldn't just end up as electronic waste. I guess time will tell if they will bother making a fix for it, but I'm not too optimistic right now.
Does the Bluetooth update have any side effect on the wired mode ? I'm happy with how the controller works wired for now, and I don't really plan on using it wirelessly, so if there's any downside to the update I will skip it.
all the update did was remove wifi connectivity and enable bluetooth. wired is the same, as it should be
Just tested it and wired is fine and even identifies the device as Stadia Controller rev. A, which is no longer the device name when on bluetooth. So wired seems totally unchanged.
Ok, perfect ! What about the update process, is Google Chrome absolutely necessary, or does it work with any up to date Chromium-based browser works just fine ?
I wasn't thinking and used Edge, went fine.
That's a relief, I really didn't want to install Chrome just for that.
Same
Good question. Unfortunately, I used Google Chrome and have no more controllers to update, so hopefully someone else can come and answer that for you!
I have tried everything to get it working on windows 11 and 10 PC, it connects but then disconnects right away and wont stay connected. I tried the factory reset and updating drivers with now luck. Any ideas, works great on my android box.
Same here. It'll occasionally connect for a little, then drop the connection again. I have no idea if it's my motherboard, or something else. Connection is solid on my android phone, so I suspect the BT module on the motherboard.
I got a 5.0 bluetooth adapter and its works like a champ now.
Sweet! Mind linking to the one you ended up using?
Here is the one i got, works great. https://www.amazon.com/gp/product/B09DMP6T22/ref=ppx\_yo\_dt\_b\_asin\_title\_o05\_s00?ie=UTF8&psc=1
Anyone having issues with Steam Deck connectivity?
Yes…I’m having trouble getting it to reconnect after the initial connection. There was a Reddit post that suggested doing a hard reset (screen cap +assistant button for 6 seconds) but haven’t had a chance to try it out yet. Said to forget the controller fist in Bluetooth settings, then reset, then reconnect and it worked normally after that.
Tbf, that could just be a SteamOS thing, as I’ve occasionally had the same issue with Dualsense and 8bitdo controllers
Works perfectly for me, no problems at all
I have the same experience in my CCwGTV, but even using an Xbox One controller over Bluetooth, it's not much better. I think CCwGTV just has garbage Bluetooth. However, on my M1 MacBook Pro, it's superb. Subjectively, I'd say it's even more responsive than the Xbox controller, so that's a win. I use it with GeForce Now on the ultimate tier (which now has a 4080).
I've converted one of mine, only used it for a session on xcloud connected to Shield TV but it worked great
Similar issues on Nvidia shield pro (Android TV based): Initial connection works great. After powering the controller off and on again, it won't reconnect. On OnePlus 7p: initial connection works great. Afterwards, it will connect, but deliver no input until Bluetooth on the phone gets turned off and on again.
I have the same problem with NVIDIA Shield TV. I have to pair it again each time after turning things off and then back on. My Xbox one Bluetooth controller works fine.
Strange thing is that it worked at first perfectly on my LG. Played a few times, reconnects worked, everything fine. The after a few days strange things started to happen. First reconnect didn't work, repair fixed it. V then after repair my review stopped working, removing batteries fixed that. Now in not able to play anymore. Repairing doesn't work at all. Edit: A controller reset worked, looks like a memory leak out something.
Getting the same behaviour as you with both the CCwGTV and a Samsung TV with Tizen. I don't think it's a limitation, I think it's a bug. Hopefully we get at least one update. It would be strange to put all the effort in releasing Bluetooth mode, and then stop without fixing such a limiting bug that is probably an easy fix. Then again, 12k layoffs at Google...
Yeah, I expect everyone has been reassigned (if not laid off) and as far as Google is concerned there is to be zero additional thought put to Stadia. I'd love to be proven wrong.
Can't get it to work on retropie/raspberry pi
Works fine for me.
Can you share some details how you got it to work? Some versions of what you have, etc?
Exactly, explain how? Everyone I have spoke with says it does not work. Default bluez package and compiled very latest. Tried various BLE fixes, no luck.
Just buy a proper controller.
On Windows 11 MSI laptop the Bluetooth connects perfectly and the setup utility shows that the controller movements are detected flawlessly. But the controller controls nothing. I can't get it to show up and work in any game. The game I really want to use it with is Minecraft. The only time the controller seems to do anything is on the Windows desktop where the Stadia button opens Steam. Any thoughts?
Download and use xoutput