Google’s Fuchsia OS is rolling out to every first-gen Nest Hub
source link: https://www.theverge.com/2021/8/18/22630245/google-fuchsia-os-nest-hub-rollout-release-date
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Google’s Fuchsia OS is rolling out to every first-gen Nest HubSkip to main content
clockmenumore-arrownoyes
/cdn.vox-cdn.com/uploads/chorus_image/image/69740372/dseifert_181018_3039_1192.0.jpg)
Photo by Dan Seifert / The Verge
Google has started to push out the silent upgrade to its new Fuchsia operating system on first-gen Nest Hub devices (known as the Google Home Hub on release), meaning the secretive project will be broadly used by consumers after years of opaque development. The OS, which unlike Android isn’t based on Linux and uses a microkernel called Zircon, was previously made available to some devices enrolled in a preview program back in May.
Now, Google has confirmed to 9to5Google that a new firmware update for non-preview Nest Hub devices includes the Fuchsia upgrade, meaning that all first-gen devices should be running Fuschia already or very soon. I just checked the one on my desk — which Google explains how to do here — and sure enough, turns out it’s on Fuchsia right now.
You might’ve thought I’d have noticed that a device that I look at and interact with every day is running an entirely new operating system, but Google is attempting to make the experience as close to identical as possible. Even the pokey performance on the first-gen Nest Hub appears to be very similar, for better or worse. The only way to know you have Fuchsia is by checking the “About device” section of the settings menu, and even then the OS isn’t mentioned by name.
That means that the first widespread Fuchsia deployment isn’t quite as exciting as the possibilities imagined when word of the project first started getting out more than five years ago. At the same time, it’s quite impressive that Google has managed to seamlessly replace the core software of a popular product in a way that most people won’t ever notice.
Sign up for the newsletter Verge Deals
Subscribe to get the best Verge-approved tech deals of the week.
There are 10 comments.
Will Google dare abandon Android, and simply force everyone to Fuchsia? Or maybe just replace the android kernel with the zircon kernel for starters….
Google wants an ecosystem they have full control over, just like Apple.
Posted on Aug 18, 2021 | 4:14 AM
I expect they’re working on building something that looks and feels and runs apps like Android but on top of a Fuchsia base. They may be finding that the Linux kernel and core system is limiting them in various ways they no longer wanted to tolerate.
I don’t think this is about full control, because they can already change anything they want in the software. That would be more about their new Tensor SoC in the Pixel 6, as I suspect Qualcomm have been one of their biggest roadblocks for years now.
Posted on Aug 18, 2021 | 5:06 AM
Oh, there’s no doubt that there are tons of valid technical reasons for making this switch. Like updating properly, or universal app platform etc. But it is always about Control, Google can assert far greater control if they are at the helm, legally, or just dev influence.
Linux kernel is open sourced under a GNU GPL 2.0 license, AOSP uses the Apache 2 license. Zircon and Fuchsia use the MIT and BSD licenses for open sourcing. Not sure what exact differences are in the licensing, but the one in charge of both repositories is Google.
Just like they control the chromium repository, they also control Fuchsia and Zircon repositories. If they manage to pull this off, they will reduce Linux influence and role, and vastly increase their own influence. The world will become dependant on Google even more so than it is now.
Posted on Aug 18, 2021 | 6:29 AM
I don’t think this has anything to do with getting away from Linux or controlling the kernel. They have an insane amount of control over the platform and user base as is. Linux is simply a kernel. It’s not a platform that competes with Google’s business.
My belief is that Fuschia initially became a project to end Android’s reliance on Java APIs, that reliance being what ultimately led to the long legal battle between Google and Oracle.
Of course, this is my speculation as not much is known about Fuschia and its development.
Posted on Aug 18, 2021 | 11:06 AM
Naaah. It has nothing to do with reliance on Java APIs. Kotlin is replacing Java APIs.
The one of the main motivations for Fuschia is a stable ABI interfaces for drivers. Writing drivers for SOC in Linux is notoriously cumbersome and hard to build with modern software engineering practices. One of the thorniest issues is keeping drivers within the Kernel repo for builds which for something like Android means you need to have driver sources or precompiled binaries for various SOC. Unlike desktops, the mobile SOC space moves pretty fast, SOCs becomes outdated the moment they are manufactured (especially Displays and Cameras). It’s not just about Qualcomm, it’s also Broadcom/MediaTek for modem, camera drivers and mainly display drivers. You also have to pray that they play nice with each other and are compiled for the right branch/version of the kernel. This makes CI/CD infeasible (it can take days to build) and each build has a significant chance to brick your phone.
Posted on Aug 18, 2021 | 1:48 PM
Cool. It is not everyday that a brand new OS is distributed to potentially millions of devices.
The fuchsia team must be really excited.
Posted on Aug 18, 2021 | 5:14 AM
My first-gen Nest Hub got bricked overnight because it was on the preview program back in May. Google replaced it for me despite it being out of warranty. I believe it had something to do with the roll-out of Fuchsia.
Posted on Aug 18, 2021 | 5:25 AM
I’ve not been impressed with this update. Been running on it since at least June and now I get random reboots when issuing commands. Will use the wake word then issue the command. The Hub will start to process it then freeze and reboot. Happens at least twice a week whereas I never had that happen before.
Hopefully they get this ironed out. I’m not holding my breath. It always seems like they always find ways to break things that have always worked. Eventually they seem to get them fixed but damn it’s annoying.
Posted on Aug 18, 2021 | 8:36 AM
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK