Coinciding with the starting signal of a new week is a software update for Chromebooks. A new Chrome OS 101 update is now rolling out to supported devices on the stable Channel. Short of a brief announcement post, Google hasn ’ deoxythymidine monophosphate provided details of what ’ second in this Chrome OS 101 update. I see Lacros mentioned dozens of times in the logarithm I created though.

First things first for Chrome OS 101

It besides appears some devices didn ’ thyroxine receive the initial Chrome OS 101 upgrade earlier this calendar month. Some owners of the Lenovo Chromebook Duet, for exemplar, didn ’ t get their software version flipped to 101. This time about, those small Chrome tablets do get the update. That ’ includes the dark boot screen, productivity catapult and other features we ’ ve been enjoying for a few weeks. Oh, the branding change of ChromeOS is there excessively.

Lacros is everywhere, hinting at a release soon

I besides noticed a swerve of references to work on Lacros, which is the Linux browser that Chromebooks will use rather of the native Chrome OS browser. Google is in the action of uncouple of the browser from the platform for several reasons. Those code changes along with several mentions of Chrome OS 103 hint to me that this passage may be starting in the next 6 to 8 weeks. Of course, I couldn ’ metric ton wait. I ’ ve been running the Lacros browser full time on my Chromebook since Chrome OS 100. I still wouldn ’ t recommend others follow suit barely yet. That ’ second chiefly because I don ’ thyroxine want to be responsible for any issues you might experience.

still, the number of those issues that I ’ ve seen over the past few months has diminished. Suffice it to say, Lacros is coming along nicely !

Other Chrome OS 101 bits

away from the many Lacros changes, there ’ south besides the inclusion of a ” plan B ”. No, it ’ s not a stand-in plan in case the Lacros rollout doesn ’ deoxythymidine monophosphate employment. This has to do with WebRTC, or Web Real Time Communications. According to the WebRTC specification, plan B has been in the works for closely 30 releases. You might not be affected by though, based on the description :

People who use multiple audio tracks or multiple video tracks on a single PeerConnection will have to test their product under Unified Plan, and adjust consequently. In the case where a call is initiated from a non-Chrome end point and replied to by Chrome, the form of the offer may have to change. People who do detailed SDP parse and care about msid attributes will have to check that their parse code picks up the fresh format ( a=msid ). The details on whether changes will be needed and how the apps indigence to change will be application pendent. We think that about all applications that use merely a single audio and a individual television chase per RTCPeerConnection will be unaffected by the change.

Unless you ’ ve been communication over multiple tracks on the lapp connection then, you probably won ’ metric ton notice any changes. This is more of a service provided / developer change. A sub-rosa pay back for the Password Checker feature is besides in Chrome OS 101. apparently, the check would loop endlessly when scouring your passwords against databases with known compromise credentials .

Share this:

Leave a Reply

Your email address will not be published.