From what i can get from this RFC :

https://fuchsia-review.googlesource.com/c/fuchsia/+/1151293

https://fuchsia.googlesource.com/fuchsia/+/refs/changes/93/1151293/9/docs/contribute/governance/rfcs/0264_running_unmodified_aarch32_linux_programs_on_fuchsia.md

Fucshia is going to new efforts to run arm linux 32bits apps (android?), besides running arm linux 64 bit apps already?

Any idea why?, since arm32 is being deprecated in the following years, why the effort? Is there a new fuchsia product that requires it?

My Hub Max is showing F22. Hopefully, the release notes won't be two months late again.

Edit - Interestingly they just released the F21 release notes but also some of the other odd number ones that weren't previously released. Also of note is that the date for them is very much in the past, e.g., July 21st for F21.

https://fuchsia.dev/whats-new/release-notes/f21

Let's come here and discuss & speculate what Google may have been or want to do in future. This subreddit feeling empty so let's come together and discuss

What's the latest status of Fuchsia

this is not a rant but i just couldn't stop appreciating Huawei from going from using Android AOSP to building their own native OS. i personally like the idea of apps running natively like ios instead of in a Virtual Machine like Android. and with OpenHarmony we could actually see a real competition to Android and maybe it will finally encourage google to take their Fuchsia Project more seriously.

Hi Fellow geeks

I just noticed that the latast branch in the GIT repository appears to be f23 meaning that this is the current WIP release and confirming the release of f22

Sadly, no documentation updates and the latest release notes available are for f18 :(

https://fuchsia.dev/fuchsia-src/contribute/governance/policy/programming_languages

According to this, Rust is permitted to be used throughout Fuchsia, except for the kernel, as it doesn't have an "established industry track records of being used in production operating systems".

With this being several years old now, a lot has changed. Namely, the Linux kernel now has parts written in Rust. Android has also begun using Rust.

I think it's time for Rust to be incorporated in the kernel if this is truly meant to be the OS of the future. I think this project has great potential, but it's greatest enemy is probably Google itself.

https://www.androidauthority.com/microfuchsia-on-android-3457788/

It been a while I never heard about FuchsiaOs.
What is the latest status?
What is the roadmap in the near future?
How the Mobile Phone?

I'm seeing F18 on my Hub Max, straight from F16, skipping F17. I'll update this if Google updates the Fuchsia site with release notes.

Edit - Release notes have been uploaded, https://fuchsia.dev/whats-new/release-notes/f18

Well, to explain what I'm thinking, Smart Watches has healthcare sensors and can send an SOS message when neccessary, so imagine the watch got bugged, malfunctioned and restarted in a completely inappropriate time (another term is "Wrong place and wrong time") causing an unnecessary death that can be avoided

Only one accident of these is enaugh to get the world press is the state of madness and will get both Fuchsia and Google's reputation to insanely go down (just like what happened what Apple watches once but in a completely reversed way when they were praised for saving a life in a place so hard to spot)

Am I wrong?

Fuchsia hardware support matrix (2024)

Hey everyone, it's been a while since I've posted here. Hoping everyone had a great Christmas and a Happy New Year!

You can find my hardware matrix here.

Hardware in 2024:

No new CPU hardware has been added. Two devices have been removed. The Acer Switch Alpha 12 and Google Chromebook Go (atlas).

The Acer Switch Alpha 12 was one of the first devices supported by Fuchsia alongside the original Pixelbook (eve) and has been removed from the documentation.

Additionally, the Chromebook build target and documentation have also been removed. The last supported Chromebook was the Pixelbook Go (atlas) released in 2019.

That leaves two official devices supported by Google. Those being the 7th/8th gen Intel NUCs and the Khadas Vim 3.

Software in 2024:

Due to the layoffs in 2023, the workstation project has been deprecated, Google has canceled bringing Fuchsia to their smart speakers along with the cancellation of the full Chrome browser coming to Fuchsia.

The workstation product is being replaced with workbench which will serve a similar purpose.

We intend that workbench will include graphics, audio, and input support (touch, mouse, and keyboard) in addition to the features included by minimal. This will enable full system validation tests which simulate a graphical product (with the exception of hardware accelerated video decoders and DRM/protected memory)

Ya I know yall will defend mega corps like typical redditors, but ok not straight up stolen but paying pennies? Now the project is downgraded and most likely going to die and still have to use shit Android and shit Linux. Really bummed about this.

I randomly found this new Chromium bug where they plan to remove Chrome on Fuchsia. They mentioned that "Chrome browser on fuchsia won't be maintained due to the cancellation of the workstation program."
https://bugs.chromium.org/p/chromium/issues/detail?id=1509109
What do you think about this? I had very high expectations with Fuchsia and I'm afraid it won't become a general-purpose operating system as many of us hoped for.

https://fuchsia.dev/whats-new/release-notes/f13

Fuchsia F13 release notes Date: August 3, 2023

Version: F13

The following changes have been implemented:

Application Runtimes (Flutter, Starnix, and Web) Starnix The following updates have been made for Starnix:

Added initial support for generic netlink. Added initial support for sysfs. Added initial support for RISC-V. Added fixes to get more LTP tests to pass. Added support for FUSE syscalls. Added support for mounting ext4 from VMO-backed sources. Added support for block read ahead queue. Added support for inotify. Added support for SIOCGIFFLAGS/SIOCSIFFLAGS in ioctl. Added support for InputDevice and keyboard events. Implemented ioctls for LoopDevice (/dev/loopN). Implemented fork() syscall. Implemented vDSO backed clock_getres() syscall. Implemented /proc/<pid>/oom_*. Initial support for Fxfs in Starnix. Fixed issues related to UTC and timer. Fixed issues related to seccomp. Fixed security related issues and performed general cleanups. Refactored and fixed remote_binder. Developer The following updates have been made for Developer workflows:

Added enforcement of FIDL libraries used in host tools that are part of the SDK. Initial support for Fuchsia-controller available in source tree. Removed legacy overnet protocol. Overnet exclusively used a circuit switched connection. Diagnostics The following updates have been made for Diagnostics:

Removed the Dart Inspect library from the Fuchsia source tree. Updated Archivist to write logs to serial instead of the console. Updated Archivist to no longer ingest CFv1 data. Updated the diagnostics tools to accept monikers prefixed with /,, ./, or nothing. FIDL The following updates have been made for FIDL:

Added requirement for explicit unknown interactions keywords. Moved FIDL Dart support out of the Fuchsia source tree. Removed FIDL C bindings. Software Delivery The following updates have been made for Software Delivery:

Added support for fxblob. Deleted fuchsia.pkg/PackageCache.Open. Stopped exposing the pkgfs/versions directory.

Hello fellow redditors,

Do you know if there is something new about Fuchsia? What are they currently working on? Should we expect something new in the near future?

Today I checked fuchsia.dev and saw nothing new, the version control they use looks pretty alive though, with commits around the clock. Checked the Wikipedia page - nothing new there as well, even the latest version hasn't been updated yet. There are no new articles in the "Fuchsia Friday".

Thanks!

F12 released. You might be interested in this: https://fuchsia.dev/whats-new/release-notes/f12

9to5Google post about the release: https://9to5google.com/2023/08/25/fuchsia-12-nest-hub-update/

https://www.osnews.com/story/136593/google-amazon-rebuked-over-unsupported-chromebooks-still-for-sale/

https://9to5google.com/2023/07/25/google-abandons-assistant-speakers-fuchsia/

So many questions? Why does Fuchsia have "strict CPU requirements"? What does this mean for Fuchsia on phones and with ChromeOS?

EDITED: Changed link from OSnews to source link at 9To5Google.

I know that sometime ago their was a YouTube video that showed fuchsia running on a phone and it really looked different than Android for sure.

However since at the heart of the OS is the Zircon kernel I thought I read it somewhere or got the idea that perhaps Google could swap out the Linux kernel and use Zircon and this could help towards Android OS updates lasting longer for phones since Google would now control everything in the OS right down to the kernel itself vs the current situation of them having to align Android OS support to however long a version of Linux is supported.

Has anyone heard any kind of update as to plans that involve it's use in a mobile phone or android?

https://fuchsia.dev/whats-new/release-notes/f11

Looks like some quality updates. Interestingly I was only able to find this on desktop and not through my phone.

I am working on building and running Fuchsia on an internal project at work. I have not been able to find this information anywhere, but maybe I am looking in the wrong place. I am wondering if there is a separate bootfs image that is created and then put into the zbi image. It seems like it should be because the qemu command template shows guest.kernel_image (passed to -kernel for qemu) and guest.zbi_image (passed to -initrd for qemu). Is the guest.kernel_image the kernel.zbi and the guest.zbi_image the normal zedboot.zbi or is another image used there? I haven't been able to find where the guest context is set for that template.

Hey everyone! I'm really fascinated by the Fuchsia operating system, its ongoing development, and its build process.

I've recently set up a developer workstation and have been diving into studying the operating system for about a month now. Since there's limited information and documentation available on this topic, I wanted to reach out here and ask about building everything from scratch without relying on Jiri/Prebuilt CIPD packages.

Typically, when you build the operating system, you start by bootstrapping Fuchsia and fetching all the prebuilt dependencies using Jiri/CIPD. However, I'm curious to know how I can build the entire operating system directly from the source.

Apologies for the somewhat complex/dumb question, but I'm genuinely eager to expand my understanding of how the Fuchsia operating system works.

Thanks, everybody!

So, I finally bit the bullet and built Fuchsia Workstation to run on my ARM MacBook Pro. It's fair to say I'm impressed with the progress: the OS internals appear to be well-built, there's a solid kernel, the typical POSIX utilities work, and so on. Even though I'm not a developer at that fine-grained level (I lean towards systems engineering, so I see black boxes connected to each other), the OS seems to be, for lack of a better word, all there and functional.

I'm wondering, though, about any apps that could make the experience more "livable" for someone who isn't a bare-metal coder. The browser is there, of course, but I'd welcome an e-Mail client built in Dart; an app launcher built in Dart; basically, the full Monty.

So then, there's Dahlia OS. This would seem to be exactly what I'm after, essentially a shell to make Fuchsia "livable", maybe not daily driver standard (of course not, this is a research OS) but definitely able to perform the tasks of quotidian life. But everything that's available from the main site is actually built on a Linux core (the implication being that they'll move it over to Zircon/Fuchsia once Fuchsia is "done"). I did find this, though. Seems to be a build of Fuchsia Workstation built for running on bare metal ARM?

A little bit of hand holding would be appreciated!

Looking a bit inside 9to5google tells something about "undefined android version running VR headsets", "Galaxy Glass" line from Samsung, "Collaboration between Qualcomm, Google and Samsung" "rumored Samsung VR headset [not far away]" and quite much more but knowing android's problems, I have some doubts regarding the android part and that it's not android but an OS that runs android apps which is a reference to starnix since both Linux and Android where mentioned in the "XR OS" job listing from Google which was released right after the "AR OS" list spotted by 9to5google although no idea why this wasn't mentioned (no evidence) so I wanted to ask the experts here

To be fairly honest, this year's Google IO conference might clarify MANY things and I'm looking forward to hear what will happen then