It isn't an evening without ChromeOS crashing to login at least once.

@ratamacue The v1 of the Samsung Chromebook Plus.

The touchscreen stopped working a couple of weeks ago, its Linux App support is basically unusable, and it becomes very unstable when it becomes memory-constrained while the Android subsystem is running.

My best guess is that ChromeOS ARM support is just plain buggy.

@baldur Plausible. I've owned 3 different Chromebook models and all have been extremely stable. All Intel though. Haven't tried the Linux container support yet, but Android apps are great. I even used an old c720 with chrouton/Kali Linux to compete in openctf at defcon this year and loved it.

@ratamacue Yeah, I keep hearing such nice things so I'm guessing either it's buggy ARM support or I got a lemon.

@baldur @ratamacue Lots of tabs (50+) open in sessions lasting several days?

@ondra @ratamacue I do have a bunch of tabs open, yes. But like I said, if I'm running an Android app with a bunch of tabs open then sessions barely last more than a day without crashing to login. Often it crashes several times each evening. So no to the lasting several days.

Everything is basically fine if I avoid using Android apps.


@baldur @ratamacue I've used dozens of different and they are usually pretty stable unless I have tens of resource-intensive tabs (Gmail, Google Docs...) opened for ~week.
Though I usually have Play Store completely disabled since its implementation is still a joke. Plus it's a proprietary platform, clutters the UX...

But I haven't heard of this from deployments I've worked on nor community discussion on Reddit etc. Maybe it's a specific Android app? Have you tried powerwash?

@ondra Tried it once. Didn't fix it.

Things are fine if I either don't use Android apps or just use an Android app with very, very few tabs open.

The more heavy-weight the Android app, the fewer tabs I can use before everything freezes and then crashes.

My device handles being memory-constrained fine if there aren't any Android apps running, but as soon as an Android app is running, then being memory-constrained causes instability: it locks up up and is unresponsive until it crashes to login.

@baldur You might try resetting the hardware as well. It may help with the touchscreen issue. (

Plus Android apps are apparently crashing when accessibility options are enabled.

Closest thing I've found in the issue tracker is ... You may want to create a new issue on there and upload crash logs for developers to investigate.

Sorry I can't help any better than that.

@ondra Thanks, wasn't expecting this to be solved TBH, but I'll try the hardware reset to see if that at least solves the touchscreen problem.

That issue you linked to describes my problem _exactly_. My guess is that the graphics hardware of this Samsung Plus is just underspecced for anything but trivial Android app use.

I guess the smart thing for me to do would be to just disable the Play Store and give up on trying to use Android Apps on this thing 😝

@baldur Well, the least you can do is star the issue and wait. :)

The board used in Samsung Chromebook Plus (codename kevin) is gru, which is running OP1 ARM SoC designed by Google specifically for Chrome devices. It should be more powerful than most Android devices on the market, AFAIK. It was even among the first 3 devices officially supporting Play Store on Chrome OS. The same board is used in the recently introduced Acer Chromebook Tab 10 tablet, BTW. The HW spec shouldn't be an issue.

@baldur Then again, as I've mentioned before, the implementation is still far from perfect after all these years in development. I don't want to discourage you from using apps on since there is obviously demand for that and I'm obviously biased, but I live happily without them and only thing I need from time to time is VLC. :)

Sign in to participate in the conversation

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!