3 ms·

ChromeOS has gotten progressively worse over the years. I have a Pixelbook and it used to be great, but now I get constant freezes and crashes with android app

ChromeOS has gotten progressively worse over the years. I have a Pixelbook and it used to be great, but now I get constant freezes and crashes with android apps, unresponsive windowing UI and launcher, etc. It's also constantly updating itself, which isn't inherently bad, but it's asking for restarts what feels like twice a week. Linux containers is half-baked (takes >30 sec to launch), the stability of Android apps is questionable.

resoluteteeth 4y ago
I have a cheap chromebook with much worse specs than a pixelbook and it has been extremely reliable. The linux containers are slow to start but that only applies to the first time you run a linux app after restarting the computer or logging out/in. Otherwise they work great. Android apps are more of a mixed bag. The bigger problem is that PWAs don't quite seem ready and Chrome apps are deprecated so there's no good way to make apps that specifically target chrome os right now.
- invisible 4y ago
  I know it's not a requirement, but running docker containers is a nontrivial headache. Additionally, running VSCode resulted in a number of frustrating bugs: - copy+paste not working, or only working on small strings - font size issues and anti-aliasing issues - delays on keystrokes Any type of advanced networking in Linux was also a huge headache (e.g. a wireguard interface) and didn't interop with the browser. So as needed, I was at one point running both the Chrome on ChromeOS and another Chrome in Linux.
jeffbee 4y ago
Are you sure you didn't switch it to dev channel? The last five production ChromeOS releases were on June 23, May 26, April 28, March 31, and March 3, 4 weeks apart as usual.
- turtlebits 4y ago
  Pretty sure im on stable - I guess I'll try a powerwash. The biggest frustration is that all I use it as a glorifed PDF reader for sheet music- I use an Android PDF reader and the Scribd app and it's hit or miss it those work after waking sleep.

resoluteteeth 4y ago

I have a cheap chromebook with much worse specs than a pixelbook and it has been extremely reliable. The linux containers are slow to start but that only applies to the first time you run a linux app after restarting the computer or logging out/in. Otherwise they work great. Android apps are more of a mixed bag. The bigger problem is that PWAs don't quite seem ready and Chrome apps are deprecated so there's no good way to make apps that specifically target chrome os right now.

invisible 4y ago
I know it's not a requirement, but running docker containers is a nontrivial headache. Additionally, running VSCode resulted in a number of frustrating bugs: - copy+paste not working, or only working on small strings - font size issues and anti-aliasing issues - delays on keystrokes Any type of advanced networking in Linux was also a huge headache (e.g. a wireguard interface) and didn't interop with the browser. So as needed, I was at one point running both the Chrome on ChromeOS and another Chrome in Linux.

jeffbee 4y ago

Are you sure you didn't switch it to dev channel? The last five production ChromeOS releases were on June 23, May 26, April 28, March 31, and March 3, 4 weeks apart as usual.

turtlebits 4y ago
Pretty sure im on stable - I guess I'll try a powerwash. The biggest frustration is that all I use it as a glorifed PDF reader for sheet music- I use an Android PDF reader and the Scribd app and it's hit or miss it those work after waking sleep.