Used to run stadia smooth via chrome browser on chromebook duet, lenovo.
Suddenly, it's laggy, no idea why. And not on any other device on same wifi network. And it's a consistent issue, not seeming to go away for some reason.
What might've caused this? I don't see any apps running in the background. Not sure if there are any, but i closed all the windows. Background windows. New chromebook, so only installed fl studio and ibis paint on it, that's it. and those apps are closed. Not running as far as I am aware. And stadia ran fine even with those apps installed before. Nothing else has changed. but it's laggy to the point of being unplayable. and very unstable too.
also tried different network on the chromebook. Same result. Only the chromebook lags on any network that any other device doesn't lag on.
Hi @Greenhill, sorry to hear about that. It sounds like the problem is isolated to your device. If there are any system updates that were performed, would you be able to revert back to an older version? Additionally, you could try a factory reset, but that would wipe the data you have on the device. I'm afraid I'm unable to provide additional troubleshooting steps as Chromebooks are not my area of expertise.
Hi @Greenhill,
I tried to help out with a similiar issue with this device HERE.
Did these steps over there help you out? (recieved some kudos from you there, thanks!) Hope so! ![]()
Yeah, thanks for the responses.
I don't know what to say... I realised how complex the issue and involved technology/factors are. So I decided to believe that it can work. And then worked.
Hahaha... Like I don't know what to say. Frequency band issue but specifically on this chromebook? Wild guess.
Something not easily detected and didn't show on speedtests either.
Hello @Greenhill,
So the issue does dissapear ? Everything is right now ?
TBH Chromebooks are mostly low-end machines. Any on-going update / unoptimized addons can cause lags. Have the same problem on my chromebook (asus), sometimes. This is probably what happened : something may had runned in background and use too much ressources.
If the problem does appear again (I do not hope so !), you can use the Chrome built-in Task Manager to see what's happening. ☺
Oh cool ty, Didn't even know chrome had a task manager. I don't even have a del(ete) button on the keyboard. =P
I can't find it tho got the newest chrome os version I think.
Check here. ![]()