ChromeOS

Since the 7C works flawlessly also with smooth stylus input, some more boards could be used to surf the ARM wave.

I Just entered the arm ChromeOS world with a 7c 1 gen and was wondering if there is any chance to get genshin work. ATM it stops after a few secs of the intro.

I'm wondering what repo the Debian instance gets its packages from, more specifically the adb and fastboot binaries.

Thanks in advance to whoever finds this out, you will literally be saving me so much headache!

There might be many cheap Chromebooks for sale in Denmark this summer (article in Danish)

I spent some time installing and configuring Linux (Arch) on pixel slate. Here is what I find.

The good parts.

• Basically everything works out of the box (with one small fixable caveat below). I installed Arch Linux with KDE Plasma.
• Firefox is simply great.
• Battery life is very good. I get very similar battery life compared to Chrome OS. Battery drain in suspend is minimal.
• Screen rotation works pretty well once iio-sensor-proxy is installed.
• virtual keyboard (maliit-keyboard) works well too.

The bad parts

• Stylus works, but lags a lot. Might have something to do with Wayland?
• Gesture navigation can definitely use some improvement.
• The flatpak Plex client appears to lack hardware acceleration and lags a lot with 4k content. I have to rely on the web client at the moment.

Some notes

• My motivation to do this was to completely remove chrome from my devices. I chose Full UEFI boot. There is a very well written tutorial for doing so. For me the only hurdle was to obtain a SuzyQable CCD Debugging cable.
• The default Arch Linux install works well. The only issue was the hid_google_hammer kernel module. It is causing very long delays during the startup and you basically won't be able to properly shutdown or reboot. Fortunately the fix is easy enough. I just had to blacklist the two modules (hid_google_hammer and hid_vivaldi_common). From what I tested, this issue affects many distros, including at least Arch and Void.

Like the title says. Just upgraded my Android phone, got it set up and working like a charm. Went to connect it to my chromebook in the chromebook settings and it won't let me get past the "sign in with your google account" screen.

Keeps saying "wrong password". But not only have I been already using that account/password not only on the new Android Phone, but on my Chromebook for the last year...but I also LITERALLY copied and pasted it from my bitwarden account after it failed to take the typed password three times.

I'm stumped. Help please. Thanks in advance.

When you import a private key for an SSH connection in the Terminal app, where are those stored? Can I access them?

I'm trying out the live USB on a Surface Pro3. I know the wifi chip is supported as I can connect to my phone's hotspot. I was able to connect to my home Wifi with Windows on this laptop, but attempting to connect my home wifi gives this error

The only thing I can think of is WPA vs WPA2 vs WPA3. I've tried changing my wifi between WPA2 and WPA2/WPA3 modes, not going to set it to WPA though.

Any tips?

I have pihole running on my NAS, and my DHCP server is configured to return the NAS IP as the primary DNS server (and 1.1.1.1 as the secondary). From ChromeOS settings I can see the expected DNS servers are being used, and I can reach the NAS using the local DNS records configured in pihole. Earlier this morning I was in a Crostini linux terminal and I could SSH to my NAS by hostname, then all of a sudden it stopped working in the terminal. I can still use the local DNS names in ChromeOS and other devices just fine. Inside the terminal I can see the usual 100.115.92.93 in /etc/resolv.conf, and when I run nslookup nas.lan it's able to resolve the lookup.

Adobe Photoshop on the web launches and works great on Chromebooks Adobe has unveiled the general availability of Photoshop on the web, marking the culmination of nearly two years of beta testing. Beginning Wednesday, September 27th, all users with paid plans can access this simplified-yet-powerful online version of the iconic photo editing app. The biggest highlight of this release is definitely the integration of the Generative …

Chrome Unboxed – The Latest Chrome OS News - Oggi, 22:11

Hey everybody, hope you're all doing well. I usually stream off this laptop about twice a week on Twitch and usually never had a problem until a few days ago. I know both the Twitch app and the laptop's ChomeOS both had an update so I don't know if that's where something went wrong? Anyway, my twitch stream was upside down while my screen was still at the right orientation. I tried doing Shift + CTRL + refresh to change my screen orientation to see if that did anything it didn't. The stream itself was still just upside down. My friend called me on Discord to see if he could help but it was upside down on Discord as well so I don't think it's a Twitch thing. I've streamed problem free for about 2 months so I have no idea why it's doing that now. Any help or suggestions would be very appreciated because I am absolutely baffled on how to fix it.

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

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.

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.