Categories
Mobile Syrup

It’s officially ChromeOS, stop writing Chrome OS

Google’s Chrome OS is no longer Chrome OS. Now it’s ChromeOS. Yes, ChromeOS.

While such a dramatic branding change may be a head-scratcher for some, this one makes a lot of sense to me and will hopefully bring some consistency to coverage of Google’s Linux-based Chromebook operating system.

The Verge reported on the change, noting that Google’s senior director of marketing for ChromeOS, James Croom, confirmed the change. However, Croom also acknowledged the company hasn’t finished converting every instance of Chrome OS to ChromeOS, so don’t be surprised if you see the occasional Chrome OS out in the wild.

Oh, and in some official branding, Google stylized the name as chromeOS instead of ChromeOS, but that appears to be only a stylistic choice. The correct term is ChromeOS.

The Verge highlights several places where the new ChromeOS brand is on display and a few places where it isn’t if you want to go looking.

For a product that’s been around over a decade, removing a space from the name hardly counts as a major rebranding. Still, it’s nice to have it officially confirmed as the way to go considering people have been all over the place with it for years. Looking back at MobileSyrup’s coverage, over the last couple years we’ve written both ChromeOS and Chrome OS.

Finally, we can have unity.

Source: The Verge

Categories
Mobile Syrup

Chromebooks could save you some battery life when charging

Chromes OS will bring a new upgrade to Chromebook users to save battery life when browsing the web, courtesy of Chrome OS 105.

With Chrome OS 105, there will be a battery-saving optimization to prevent websites from draining your battery in the background. This typically happens when websites use your CPU while unopened, which puts your battery to work.

About Chromebooks discovered something within the Chrome OS 105 developer beta through a flag, showing that JavaScript activities from inactive websites will be deprioritized while limiting the time they can run the script.

As a result, Google has noted to expect up to 10 percent in battery life improvements, but these aren’t guaranteed, depending on the website running in the background.

Chrome OS 86 originally included background throttling for JavaScript but did not conserve as much battery life as Chrome OS 105.

Chrome OS 105 continues to work with a shorter window, which benefits battery optimization, but only time will tell whether changes will need to be made.

Source: Google Via: Android Police

Categories
Mobile Syrup

Google’s ‘Material You’ design language could come to Chrome OS

Google’s new design language known as ‘Material You’ appears to be coming to Chrome OS.

‘Material You’ will likely make its way to Chome OS following its introduction alongside Android 12 back in 2021. The change, which was first spotted in a Chromium Gerrit by 9to5Google, notes a flag that says, “When enabled, runs ChromeOS in Material Next MVP mode.”

The codename “Material Next MVP” seems to be an internal Google reference to ‘Material You.’ Further, ‘MVP’ is the term used by developers for “minimum viable product.”

‘Material You’ will likely enable anyone using Chrome OS to customize the colour schemes used in app wallpapers.

In addition, colour is referenced in the discussion on the Chromium Gerrit, describing options regarding how hues can be changed. However, it looks like the wallpaper will not determine the colours and that instead, you’ll select them through a mixer.

As always, this isn’t confirmation Google will add ‘Material You’ to Chrome OS, though it looks that’s likely the case.

Image credit: Google

Sources: Chromium Gerrit Via: 9to5Google, Android Police

Categories
Mobile Syrup

Steam finally arrives on Chrome OS in alpha, only for select Chromebooks

After a long wait and a premature announcement, Chromebook owners can finally install Steam on their devices.

Well, some Chromebook users. Those with a specific and short list of devices. Moreover, the version of Steam on Chrome OS is in alpha, and it requires running a beta version of Chrome OS (specifically, the ‘Dev’ channel of Google’s operating system).

In other words, if you’ve eagerly awaited the arrival of Steam on Chrome OS, you likely will have to wait a little longer unless you have a supported device and are willing to deal with bugs, glitches, and tons of other potential problems running beta software.

According to a Google blog post, the supported Chromebooks include:

  • Acer Chromebook 514 and 515
  • Acer Chromebook Spin 713
  • Asus Chromebook Flip CX5
  • Asus Chromebook CX9
  • HP Pro c640 G2
  • Lenovo 5i Chromebook

Moreover, you’ll need to have one of the above Chromebooks with Intel Xe graphics, an 11th Gen Intel i5 or i7 processor, and at least 8GB of RAM. Plus, the company notes that games that require a lot of RAM — for example, 6GB — may not work well on Chromebooks with 8GB of RAM. Finally, Google warned of performance and scaling issues on devices with screens with resolutions higher than 1080p (the company is working on a fix).

Google also has a list of recommended games that people can try with Steam on Chrome OS, some of which come with caveats. Further, the company says that Chrome OS will “typically” play the Linux version of a game, but there is Proton support for running Windows games too. Proton, for those unfamiliar, is a compatibility layer developed by Valve to help run Windows games on Linux.

As for the install process is that users need first to switch their Chromebook to the Chrome OS Dev channel, then change a flag in ‘chrome://flags.’ After that, rebooting and punching in a terminal command will start the Steam install process. Once installed, users should be able to install games through Steam as they would on Windows. You can find more details on the process here.

It’s great to see Steam finally arriving on Chrome OS, even in such an early state. However, I wouldn’t recommend trying it to anyone not comfortable with using alpha software and contending with bugs. Still, now that it’s actually available, it hopefully won’t be much longer before Steam moves from alpha to beta, and then to full release.

Source: Google, (2) Via: The Verge

Categories
Mobile Syrup

Upcoming Chrome OS update could bring support for variable refresh rate displays

With Steam support on the horizon (but still vaguely distant), now seems like a great time for Chrome OS to get variable refresh rate (VRR) support.

First spotted by About Chromebooks, Chrome OS 101 is now hitting the Dev Channel with VRR support. The functionality isn’t enabled by default — instead, it appears to be hidden behind a flag (on of Chrome’s semi-hidden settings available by typing ‘chrome://flags’ in the URL bar).

The feature boasts the following description:

“Enable Variable Refresh Rate

Enable the variable refresh rate (Adaptive Sync) setting for capable displays”

9to5Google suggests the feature might only work with external displays rather than Chromeboooks’ built-in screens. Still, if the support is there, it opens the door for Chromebooks with built-in VRR-capable displays down the road.

For those not familiar with VRR, it allows displays to adapt the refresh rate (the number of times the screen refreshes each second) to match the frames per second (fps) of content. VRR is particularly useful for games, where the framerate can vary depending on what’s happening.

For example, a pre-rendered cutscene might run at 30fps, while a walking section of the game could run at 70fps. When a more intense encounter happens — say, an explosion — the framerate could drop suddenly. VRR enables the display to match, reducing screen tear and making things feel smooth.

Typically, displays run at a set refresh rate (most run at 60Hz, or 60 refreshes per second). If content doesn’t sync with that, you can see tears (where the screen refreshes mid-frame, splitting the image) or other artifacts.

9to5 also points out the VRR will be a bigger deal when Chromebook hardware catches up. Most Chromebooks use integrated GPUs that aren’t as powerful as, say, discrete AMD or Nvidia GPUs popular among PC gamers. VRR could still be helpful, but may not be as significant a factor on lower-end hardware.

Either way, it’s good to see the feature make its way to Chromebooks as Google prepares to push the platform into gaming.

Source: About Chromebooks Via: 9to5Google

Categories
Mobile Syrup

Google announces Steam for Chrome OS, but you can’t get it yet

Google officially announced the Steam for Chrome OS alpha, but it seems like it isn’t quite available yet.

As reported by Android Police, a presenter at Google’s Games Developer Summit offhandedly announced the program, saying it “just launched.” However, it doesn’t appear to be available on the web yet, with Ars Technica’s Ron Amadeo tweeting that Google said people can learn more on the Chromebook community forum, but that there doesn’t appear to be anything on the forum about Steam yet.

That information should arrive eventually (hopefully). You can check for that here.

Until more official info becomes available, all we have to go on is what we’ve learned before. That includes an initial list of Chromebooks that will support Steam (you can check that out here), and general requirements of an 11th Gen Intel Core i5 or i7 and at least 8GB of RAM.

Although the requirements will likely rule out many lower-end Chromebooks, they could change going forward. Aside from the requirements, Steam for Chrome OS will likely be available for Chrome OS Dev or Canary builds to start before it moves into a beta and eventually stable release down the road.

Source: Android Police

Categories
Mobile Syrup

Dirty Pipe exploit could let someone take over your phone, fix is on the way

There’s a new Linux vulnerability out there that could give attackers full of control of your Android smartphone.

However, the exploit goes beyond just Android phones — it potentially impacts anything running Linux, including Android phones, Chromebooks, smart home devices, and more.

Although it sounds dire, it’s worth keeping in mind that most people don’t need to panic. For one, the issue has already been patched (although the fix may not have reached your devices yet). The exploit also only impacts some newer Android phones, such as the Pixel 6 series and the Galaxy S22 series (more on that below, along with a way to check if your device is affected).

The exploit, dubbed ‘Dirty Pipe,’ impacts the Linux kernel. The kernel is the core of an operating system and typically acts as an interface between apps and hardware. Because of that, any app that can read files on your device can potentially use the exploit to mess around with files, run malicious code, or gain administrator privileges. Ultimately, attackers could use the exploit to take over a device.

Max Kellermann discovered Dirty Pipe, but also found a way to fix it and already submitted the fix to the Linux kernel project. Additionally, Dirty Pipe was reported to Google’s Android Security team, who introduced the fix to the Android source code. Similarly, the Chrome OS team seems to have a patch poised to roll out in a mid-cycle update to Chrome OS 99. In other words, the Dirty Pipe fix is ready, it just might not have hit your phone or laptop yet.

How to check if my phone/laptop is at risk

Thankfully, checking whether your device could be exploited using Dirty Pipe is fairly easy. We’ve included instructions below:

  • Android: Open Settings > About phone > Android version > Look for Kernel version. If the number is 5.8 or higher, your device is potentially at risk.
  • Chrome OS: Open a new tab > Type ‘chrome://system’ in the address bar > Scroll to ‘uname’ > Look for the ‘Linux localhost’ text and check if the number is higher than 5.8.

In both cases, the number represents the Linux kernel version. Dirty Pipe was introduced in Linux kernel version 5.8 back in 2020, but the exploit wasn’t found until recently. If your device has kernel version 5.8 or higher, it’s potentially at risk for Dirty Pipe (unless you’ve received a patch for it already).

Most Android phones use an older version of the Linux kernel and likely won’t be impacted. However, as mentioned above, the Pixel 6 series and the Galaxy S22 series are impacted. 9to5Google noted that Android devices that launched with Android 12 have a chance of being impacted.

How to protect yourself from Dirty Pipe

Although there are no known instances of attackers using Dirty Pipe to gain control of phones or computers yet, it’s likely only a matter of time before it starts to happen. The best thing you can do to protect yourself is to make sure your devices are up to date.

As mentioned up top, there are already Android and Chrome OS patches, but they haven’t rolled out yet. Hopefully, they roll out soon — keep an eye out for new security patches and make sure to install them right away.

In the meantime, 9to5 suggests only running apps that you trust on your device. Moreover, it may be a good idea to avoid installing new apps until the patch is made available.

Source: Max Kellermann Via: 9to5Google

Categories
Mobile Syrup

What to expect from Apple’s March event [SyrupCast 253]

On this week’s SyrupCast, Patrick O’Rourke and Brad Bennett take a look at Chrome OS coming to Mac and PC and then unpack all of the major rumours surrounding Apple’s upcoming March event, including the iPhone SE (2022), iPad Air and more.

As always, you can listen to the show on your favourite podcast platform or watch the video version on our YouTube channel. This week, we split our two-topic podcast conversation into individual episodes on YouTube. Let us know what you think of the new format!

Subscribe on Apple Podcasts

Direct download link

Categories
Mobile Syrup

Chrome OS code change reveals initial list of Chromebooks getting Steam

Google is closer than ever to rolling out support for Steam on Chrome OS. Now, a newly uncovered list details which Chromebooks will initially support Steam.

Spotted by 9to5Google, the list was included in a recent code change submitted to the Chromium Gerrit, an online collaborative tool for reviewing code. The list mostly contains devices from Acer and Asus:

  • Volta – Acer Chromebook 514 (CB514-1H)
  • Volet – Acer Chromebook 515
  • Voxel – Acer Chromebook Spin 713 (CP713-3W)
  • Delbin – Asus Chromebook Flip CX5 (CX5500)
  • Drobit – Asus Chromebook CX9 (CX9400)
  • Lindar – an unknown/unreleased Chromebook from Lenovo

Moreover, 9to5 discovered that there will be other requirements for Steam. Chromebooks will also need, at minimum, an 11th Gen Intel Core i5 or i7 CPU, and at least 7GB of RAM.

It’s worth noting, however, that these are initial requirements and they could change. For example, 9to5 notes it’s seen evidence of Google testing Steam on Chromebooks with 10th Gen Intel CPUs and with AMD chips.

Another interesting tidbit of information is that Nvidia appears to be directly involved with developing Steam support for Chrome OS. The graphics card maker submitted several code changes, according to 9to5, and has also worked on making Chromebooks capable of using a discrete graphics card specifically for Steam.

Considering there aren’t any Chromebooks on the current list that have discrete GPUs, that suggests there will be more Chromebooks coming to the list in the future.

This all marks fairly strong ambition from Google to enable gaming on Chrome OS. We’ve tracked the company’s efforts for a while now, and it may not be much longer until Chrome OS is a potential alternative for PC gaming. That said, Steam support on Chrome OS seems at odds with Google’s struggling Stadia platform — maybe it’s another sign that Google’s moving away from Stadia.

Source: 9to5Google

Categories
Mobile Syrup

Google’s Chrome OS Flex could breath new life into old computer hardware

Google’s Chrome OS will soon be available to old PCs and Macs through the new ‘Chrome OS Flex’ variant, currently available in early access mode.

Chrome OS Flex looks and feels identical to Chrome OS according to details the company shared with The Verge. Moreover, Google said that Flex is built from the same codebase and follows the same “release cadence.” However, some features may be missing depending on the hardware in the device you’re using.

The Verge notes that when it asked about specific features, including always-on Google Assistant and Android phone syncing, Google said they were hardware dependant. Ultimately, it sounds like many Chrome OS features will depend on hardware, so it’s worth keeping that in mind.

The ability to easily install Chrome OS on old computer hardware has been a long time coming. Google purchased Neverware back in 2020 — the company made software called ‘CloudReady’ that could help convert computers into Chromebooks.

At the time, speculation indicated Google would leverage the Neverware purchase to put out its own take on CloudReady — this appears to be Google doing just that.

The move is arguably a smart one. Many people trade up old computers when old hardware struggles to run new software. Some people choose to install lightweight software that lets them squeeze more life out of old hardware, but that can often be a tricky process, especially for people unfamiliar with Linux.

At the moment, Google is targeting businesses and schools with Chrome OS Flex, which makes sense — it could be a great way to convert existing computer fleets to Chrome OS without needing to purchase new devices. However, Flex could eventually become another option for people to extend the life of ageing computer hardware.

Those interested can learn more about Chrome OS Flex here.

Source: The Verge