I don’t yet see the experimental flag to start Lacros upon bootup on my Chromebook with the ChromeOS 105 Dev Channel. Google resolved that by lowering the priority for the Android container startup process unless you actively try to open an Android app. In fact, that caused some issues for people who don’t use Android apps. This approach is actually no different from how Google enables Android apps upon bootup. You’d then just click your Chrome browser icon and be none the wiser. And during that time, if you don’t have Lacros enabled on your device, the container will simply shut down, hopefully before the login process completes. Of course, there will be a transition from Chromebooks using the Chrome browser to using Lacros. The idea is that in the few seconds it takes you to type your password on PIN, the Lacros startup on Chromebooks will already be happening. As soon as you boot up your Chromebook and the login screen appears, Google will start the Lacros container in the background. The solution is quite simple, even if the coding to make it happen isn’t. So how is Google going to fix this and speed up Lacros? Chrome browser on the left, Lacros browser on the right When I open the Lacros browser on my Chromebook, it take a few seconds before I can actually see or use it. Even on that device, though, it’s an issue. More so on entry-level hardware than on the wicked fast HP Elite Dragonfly Chromebook with its 12th gen Intel CPU. Here’s the problem: It takes time for a Chromebook to fire up that container. This is the exact same approach Google uses to enable Linux on Chromebooks.

And Google is beefing up the security of this browser by running it in a container, or a separate sandbox, from all other apps. Lacros is, as mentioned, written to run on native Linux. Unlike the native browser in ChromeOS that we’ve had since the first Chromebooks in 2010. Why is this a pain point for me? To understand that, you need to understand how Google is implementing the Linux version of Chrome on Chromebooks. Google intends to speed up the Lacros browser on Chromebooks so it starts quicker. Today I found code that will eliminate one of my pain points using Lacros. Lacos is essentially the Linux version of the Chrome browser and is part of Google’s effort to decouple Chrome from ChromeOS.

A few months back, I mentioned that I’m using the Lacros browser full-time.

Google chrome browser for chromebook