Can't seem to play anything consistently on Galaxy Chromebook. Usually just fails to load game. I've tried in every resolution. But if I try on cheap $150 Samsung Chromebook 3 it works fine on same network. I bought the Galaxy hoping for 4k Stadia play and I can't even play in 720p. Please help I waited thinking update would come and now have a $1000 paper weight.
I would recommend you to try to contact Stadia support and find out if there are any steps you can try for your chromebook or if it might be incompatible, because it's not supported yet.
4K is btw only supported on your chromebook when you have VP9 hardware decoding, 4K display and performance options set up to 4K. You can find this information and some more in this article.
Wont work in any resolution. If I do hard reset it usually will load game and play then 5min later game crashes. Also looks like Galaxy chromebook has the right decoding.
Says has VP9 decoding too.
Then best you can do for the moment would be to contact the Stadia support and check out with them if any more troubleshooting steps are available or if maybe Samsung needs to change something on this chromebook to make it work with Stadia, I am not 100% sure, but I guess it's good if you check out both sides.
Another thing I would recommend is to leave feedback in the Stadia App or on stadia.google.com for this issue as the developers can check this out as well. Even though you would probably not hear back on your feedback, Google can use it to improve Stadia.
I had this problem as well, I lowered the resolution settings from 4K to max out at 1080p and that did the trick.
Same issue. I got Galaxy Chromebook for the hardware and 4k with HDR. I have to lower settings to 1080p and still get some stuttering. My internet is 400 mb download on a wifi 6 network. I can confirm that VP9 is enabled. Also, I have a ton of issues with my different xbox controllers, randomly dropping connection during gameplay. I have not had these issues with any other device, so I am assuming it is a Samsung issue. It is a shame, because the Samsung Galaxy Chromebook is an amazing piece of hardware.
I finally called support. They had me go into chrome flags and turning off the two video acceleration settings then it worked fine, But then couldnt play netflix or other video streaming so I went back into the chrome flags and turned the same two settings back on and still (knock on wood) everything working for stadia. Netflix too.
Running into the exact same issue here. 4k VP9 starts and runs perfect for about 5-10min and then boom, the game pauses and lag increases to about 3-4 seconds and becomes unplayable with the Stadia connection dropping from Excellent to Fair even though speed test confirms bandwidth is over 100Mbps.
Works this way normal chrome, in incognito, with Stadia+ plugin and without. Same experience every single time.
I can absolutely play in 1080p (VP9) just fine, or go play in 4k on my TV with the Chromecast, but the whole point of the Galaxy Chromebook for me was to do Stadia in 4k.
I seem to have localized the issue after some more poking around. It looks to be a spike in CPU utilization that is causing the issue. At launch CPU utilization hovers around 30-60%, however at the ~5 min mark a spike occurs at the same time as the initial freeze of the screen/stadia with the CPU going to 100% for a moment and then hovering around 80% utilization after that, which explains why it never seems to recover properly in the game. See images below:
Seems pretty clear cut that VP9 at 4k is driving the CPU over it's threshold and causing the issue. The question now, is what can be done if anything.
Jumped the gun on that last one, still not resolved. Still crashing at the same time for the same reasons. ![]()
Did you try changing VP9 to H264 in Stadia +?
Yeah, I have tried that and practically everything I and others can think of. No luck. So frustrating on what is supposed to be the top of the line Chromebook. Any way you look at it, the CPU is getting overloaded by 4k Stadia and causing the stream to stutter and lag, and it's only this way on this hardware.
I can vouch for this, plays fine for about five or so minutes then the cpu usage goes crazy and it never recovers after that.