Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Operating Systems Google IT

Google's Fuchsia OS is Taking Over Smart Displays, Now on Its Second Device (arstechnica.com) 23

The kingdom of Google's third major operating system, Fuchsia, is growing a little wider today. ArsTechnica: 9to5Google reports Google completed the rollout of Fuchsia to the Google Nest Hub Max. Along with the original Nest Hub/Google Home Hub, that puts two of Google's three smart displays on the new OS, with the one holdout being the 2nd Gen Nest Hub. The Nest Hub Max is the first device running Fuchsia that Google is currently selling -- the Home Hub only got Fuchsia after it had been discontinued. The Google smart display user interface is written in Flutter, a Google programming language designed for portability, which runs on Android, iOS, Fuchsia, and the weird cast platform Nest Hubs typically use. So it's not right to describe the user interface as "similar" after the OS swap -- it's the exact same code because Flutter runs on nearly everything.

You are getting a slightly newer code version, though, and it comes with a Bluetooth menu. If you dive into the settings and hit "about device," you'll see a "Fuchsia Version" field that will say something like "6.20211109.1.3166243." It's a bit weird to do an entire OS switch to the futuristic, secretive Fuchsia project and then have basically nothing to show (or say) for it in terms of obvious improvements in performance or security. You can dive into the minutia of the Fuchsia source code, but it continues to be a mystery in terms of what practical benefits it offers consumers. Google never talks about Fuchsia, so not much is known about what, exactly, Google is accomplishing here.

This discussion has been archived. No new comments can be posted.

Google's Fuchsia OS is Taking Over Smart Displays, Now on Its Second Device

Comments Filter:
  • by Improv ( 2467 ) <pgunn01@gmail.com> on Thursday August 25, 2022 @03:45PM (#62823415) Homepage Journal

    "is taking over" and "now runs on two devices" seem not to fit together that well.

    • And is the Google Home Hub even a 'Smart Display'? Perhaps I'm confusing 'Smart Display' with 'Smart TV'.

      • There also seem to be different versions, Home Hub, Nest Hub, 2nd Gen etc.
        I don't know what any of them are. I did start to do a search to find out but then I realised that I'm never going to buy one so I lost interest.
      • Well, when a display goes to a purplish-red screen of death instead of a BSOD, at least we will know why.
      • That threw me as well. I guess the is googles version of the echo show.

    • by bill_mcgonigle ( 4333 ) * on Thursday August 25, 2022 @04:01PM (#62823483) Homepage Journal

      That's 100% increase overnight!

      And also "secretive". Super impressive.

    • Yeah, those crack (addicted) Slashdot editors are at it again!

    • If you don't hype up and celebrate these early "wins' you'll get no fun out of it at all.

      We've all been there. The company's been using $x technology for years, and it's a bit crusty here and there, but everyone knows how to make it work. Then the young'uns come along and force through making $y. After all that hubris, they'd better make sure $y gets used, so it gets rolled out on their pet project - 100% success, absolutely no problems whatsoever are reported (at least not to the management - the rumour mi

    • I suspect they might intend to refer specifically to Google's smart displays, not smart displays in general. If you look at it that way, two out of three is definitely a takeover.

    • "it continues to be a mystery in terms of what practical benefits it offers consumers" - this is certainly an interesting marketing strategy.

    • "is taking over" and "now runs on two devices" seem not to fit together that well.

      Neither does " will say something like "6.20211109.1.3166243.""

      I'm sure the version field somehow involves urandom and some fancy foot work to arrive at an answer that's "close enough" instead of exactingly correct information we're use to computers calculating.

  • by mtaht ( 603670 ) on Thursday August 25, 2022 @03:58PM (#62823473) Homepage
    This basic exploration of fuschia's basic security [ptsecurity.com] was not promising. The article goes deep into how to build it before diving deep into the security bugs found.

    zx_status_t sys_debuglog_create(zx_handle_t rsrc, uint32_t options, user_out_handle* out) { LTRACEF("options 0x%x\n", options); // TODO(fxbug.dev/32044) Require a non-INVALID handle. if (rsrc != ZX_HANDLE_INVALID) { // TODO(fxbug.dev/30918): finer grained validation zx_status_t status = validate_resource(rsrc, ZX_RSRC_KIND_ROOT); if (status != ZX_OK) return status; }
    • That's a little worrying, considering security was one of the primary reasons for building Fuchsia in the first place.

      • by Teckla ( 630646 )
        A little birdie told me the Fuschia team is made up of geniuses that write very clever and complex code which therefore hides serious bugs very well.
  • No. (Score:5, Funny)

    by backslashdot ( 95548 ) on Thursday August 25, 2022 @04:00PM (#62823481)

    It seems the growth rate slowed down. First, it went from 0 to 1; that's an infinite growth rate. Now it's just 1 to 2, that's a mere doubling.

  • I'd really like to see a performance analysis of Fuchsia. When I looked through the code before, it seemed really inefficient.

  • Looks like the next max is an Amlogic T931. I wonder if they will be able to port it to a current phone processor?

    Because many of the silicon vendors, especially those with names beginning with Q, keep their chips secret. There's no docs. They give you an old kernel that's massively hacked, has a ton of binary firmware blobs, and probably a half dozen or more bootloaders that are binary only too.

    Merely trying to port it to a newer version of the Linux kernel is all but impossible. Do Google's flagship ph

    • by brunes69 ( 86786 )

      I am pretty sure Google just says to Amlogic "give us the docs or we will not use your chip next time".

      It is Google who has the bargaining power here. They can use any chip they want for a device like this and there are tons of options, this is not like a cell phone where you only have a few options.

"Hello again, Peabody here..." -- Mister Peabody

Working...