![]() Any idea why this causes the controller to turn off? :(Īh gotcha, sounds like a big issue on Google's end. I suspect there's not an easy fix for it. I suspect this might be part of why it reports Chromebooks aren't officially/formally supported. It seems to happen consistently when switching activities (as happens with going from the shell to the streaming client). but there's a bug in the Android Runtime for Chrome where it says it's lost the Context for the connection ID - as a result, it looks like the underlying Bluetooth never reports back that the connection succeeded. ![]() Opprinnelig skrevet av Packetdancer:When I try on my Pixelbook, if I use adb to view the logs, I see that the connection to the Steam Controller is made.
0 Comments
Leave a Reply. |