ChromeOS

Google is pushing a new ChromeOS update that introduces significant upgrades, including a new look, some useful battery charging controls, accent color accessibility settings, and more (via 9to5Google).

ChromeOS, now on stable version 117, adopts Google’s “Material You” design philosophy, the radical new look introduced on Android 12 in 2021. The change is most prominent in the newly redesigned Quick Settings view that now has easier-to-select (and read) rectangular buttons for Wi-Fi, Bluetooth, and other settings compared to the previous small circle icons.

Today, we’re announcing new ways to keep your Chromebooks up and running even longer. All Chromebook platforms will get regular automatic updates for 10 years — more than any other operating system commits to today. We’re also working with partners to build Chromebooks with more post-consumer recycled materials (PCR), and rolling out new, power-efficient features and quicker processes to repair them. And at the end of their usefulness, we continue to help schools, businesses and everyday users find the right recycling option.

Starting in 2024, if you have Chromebooks that were released from 2021 onwards, you’ll automatically get 10 years of updates. For Chromebooks released before 2021 and already in use, users and IT admins will have the option to extend automatic updates to 10 years from the platform’s release (after they receive their last automatic update).

ChromeOS will probably just get lumped into Android at some point.

Every 2017 or newer Chromebook can redeem a no-strings-attached subscription to GeForce Now for three months.

You don’t have to buy a new machine, and there’s no recurring subscription. You don’t have to enter any credit card information, Google spokesperson Peter Du confirms to The Verge. As long as you’ve got a Chromebook from 2017 or newer, you can simply head over to Google’s Chromebook Perks page and hit the “Get perk” button to redeem a three-month subscription to the Priority tier of Nvidia’s GeForce Now.

Some of the new features are:

• Files app now seems to work across local files and those on Google Drive
• Search filters (local or everywhere, time, & and type)
• "Enhanced autocorrect"
• OCR for PDFs (wasn't able to get working - unsure why)
• RGB Keyboard Backlight Control
• Updates to the setup wizard

Seems like the only one I would use is the OCR one but I haven't been able to get it working. Maybe it's an accessibility option?

I have an HP x360 14c running 115.0.5790.160, and Pixel 7 Pro. Phone Hub is connected and the Apps option is enabled. They're on the same wifi, bluetooth is enabled on both. But I just keep getting that apps can't be streamed right now.

The eagle-eyed folks over at About Chromebooks have spotted language in Google’s code indicating that multiple Nvidia Chromebook projects (including the specific models that were rumored last year) have been canceled. Google has not yet responded to a request for comment on this language.

Distrobox as the open-source project allowing easy access to running other distributions/apps via Podman and Docker has merged support for ChromeOS.

ChromeOS has allowed Debian applications to easily run on Google Chromebooks while now with this Distrobox support for ChromeOS, it opens the door for allowing other graphical applications to run from nearly any Linux distribution. This ChromeOS + Distrobox integration was led by Red Hat engineer Eric Curtin.

Archived version: https://archive.ph/vNSJa

It looks like Google's long-running project to split up ChromeOS and its Chrome browser will be shipping out to the masses soon. Kevin Tofel's About Chromebooks has spotted flags that turn on the feature by default for ChromeOS 116 and up. 116 is currently in beta and should be live in the stable channel sometime this month.

The project is called "Lacros" which Google says stands for "Linux And ChRome OS." This will split ChromeOS's Linux OS from the Chrome browser, allowing Google to update each one independently. Google documentation on the project says, "On Chrome OS, the system UI (ash window manager, login screen, etc.) and the web browser are the same binary. Lacros separates this functionality into two binaries, henceforth known as ash-chrome (system UI) and lacros-chrome (web browser)." Part of the project involves sprucing up the ChromeOS OS, and Google's docs say, "Lacros can be imagined as 'Linux chrome with more Wayland support.'"

Previously ChromeOS was using a homemade graphics stack called "Freon," but now with Wayland, it'll be on the new and normal desktop Linux graphic stack. Google's 2016 move to Freon was at a time when it could have moved from X11 (the old, normal desktop Linux graphics stock) directly to Wayland, but it decided to take this custom detour instead. Google says this represents "more Wayland support" because Wayland was previously used for Android and Linux apps, but now it'll be used for the native Chrome OS graphics, too.

On the browser side, ChromeOS would stop using the bespoke Chrome browser for ChromeOS and switch to the Chrome browser for Linux. The same browser you get on Ubuntu would now ship on ChromeOS. In the past, turning on Lacros in ChromeOS would show both Chrome browsers, the outgoing ChromeOS one and the new Linux one.

Lacros has been in development for around two years and can be enabled via a Chrome flag. Tofel says his 116 build no longer has that flag since it's the default now. Google hasn't officially confirmed this is happening, but so far, the code is headed that way.

Users probably won't notice anything, but the feature should make it easier to update Chrome OS and might even extend the lifetime of old ChromeOS devices. This should also let Google more directly roll out changes on ChromeOS. Currently, there can be a delay while Google does the extra build work for ChromeOS, so the standalone browsers get security fixes first.

Archived version: https://archive.ph/EG7nc

Looking at the product page, I would have to conclude they never did. Sure, I can use the One vpn on my phone and USB tether my chromebook. But I'd rather have a native client.

Hey everyone, I recently got a Lenovo Duet to take with me on my travels, and it's my first time trying to be "productive" with ChromeOS.

My photo processing routine is to download photos from my camera by USB and copy them into the android filesystem where I use Lightroom to edit.

However Lightroom can't see the newly copied files until I reboot, and even then I have to restart the app a couple of times before they appear. Anyone know what causes this? is there a way to refresh or flush whatever cache might be causing this manually?

It's a little annoying especially considering they removed (or never had?) the reboot button because "you never need to reboot ChromeOS" 🤔

Update: Figured it out, Android apps can't see FS changes made by Chrome OS. See comment below.

It seems that this update was mostly security fixes and not many new things but I did get a tool tip for this window snapping menu (which seems to be new). Chrome Releases.

I recently used the firmware utility script from mrchromebox.tech to do full ROM on my HP 11 G5 EE Chromebook, and now have nothing but coreboot. I wanted to install a 32 bit OS but the BIOS software that the script installed doesn't support 32 bit software, so I want to install a BIOS(specifically BIOS, no UEFI)that does. is there any way to do this? And if yes, what BIOS software should I use?

Other publications do not count Chrome OS installations as part of the Linux share, but I think that’s nonsense – they’re both clearly Linux desktop operating systems, and should be added up.

Just saw this! I'm curious if it's an Android app or using the Linux subsystem.

It's on the dev channel (116), but it actually works really well!

Already bought a replacement, but issue still present. Is it a problem with the original Lenovo duet screen?

Brunch: a ChromeOS distribution you can install on almost all intel/amd notebooks. Similar to Chrome Flex but including the android subsystem

FydeOS: a ChromiumOS fork, without the need for a google account, with the android subsystem included

OpenFydeOS: the 100% open version

An interesting board with RK3588s

https://www.khadas.com/edge2