So, we have our next speaker and he will present you about the remote operating system, which is like a light.
Hello everyone, I'm Francesco, and I'm the comitter representative of the Honor Project, and I would like to introduce you to Honor
So, what is Honor?
Honor is a project, open source project managed by the Eclipse Foundation.
And when we started on Honor, we wanted to create a truly open and global ecosystem.
And one of our key principles was to not reinvent the wheel, so therefore we built on top of the foundation of Open Harmony,
which is a project incubated by the Open Auto Foundation in China.
Both project share the same goal of building an interoperable operating system, and focusing on respecting privacy to build a platform for smart devices, IoT, and now mobile.
So, this collaboration agreement between the two foundations brings together the expertise of the global open source development.
And the new architecture builds on top of the solid foundation of Open Harmony to enhance and expand its capabilities,
tailoring it for global and market needs while ensuring IP compliance with advanced IP tool chain.
Open Harmony offers a broad range of solutions supporting various form factors from resource constraint, the real-time IoT devices to more powerful devices like phones and tablets.
And this demonstrates its flexibility among different use cases and its scalability.
And the global open Harmony is growing as a platform for smart devices.
It powers projects like Huawei's harmonious next, which demonstrates Open Harmony's scalability.
And Open Harmony's success is reflecting in over 300 products on the market.
And more than 7,000 contributors and over 100 million lines of code.
So, by building on this foundation, a network seeks to be an open and community-driven mobile ecosystem that provides an alternative to platforms that currently dominate the market, like Android for example.
Open Harmony primarily language for developed applications is RTS, which is an extension of TypeScript.
It's a compiled language optimized for open Harmony.
And, yeah, to support developers, we are expanding it to support React Native as well.
And to enable cross-platform development and support existing applications without major rewrites.
And a crucial part of the expansion of the app ecosystem is also the on-year app store, which already offers popular applications like SoundCloud Telegram and Discord.
And our long-term goal is to provide an open-source alternative to existing app stores that currently dominate the market and giving developers more choice in an open and secure ecosystem.
While Open Harmony has demonstrated versatility, we are expanding this by providing dedicated hardware solutions to developers and this initiative focusing on delivering an European phone for a European mobile OS open source.
And which is fully committed to privacy and open source principles.
And the Rear Developer Phone is designed with European regulatory requirements in mind.
And aims to be a developer-friendly device where developers can test and deploy their innovations.
This phone complements already available developer boards, like Raspberry Pi and others, to enhance the ecosystem with more mobile portability.
And our collaboration with Voila has been crucial in the development of this device.
And Voila is known for their contribution in open source hardware.
Like the Voila X-23 and also supported various Linux-based OSes, such as Ubuntu Touch.
And now extends their expertise onto a Neuro.
However, building an open source mobile platform is without any challenges.
Most hardware today depends on close source proprietary Android drivers.
And to overcome this, we use a compatibility layer called the Libpibrs.
I'll further already gave a detailed explanation on which I will be short.
So Libpibrs works by translating function calls from GLIPC-based systems to Android's proprietary libraries that use Vionic.
And it operates key symbols and dynamically links, Android libraries such as libgl and libgleus with a lip dialog, enabling GPU acceleration and other hardware features.
This layer, the approach allows a Neuro to take advantage of hardware features, lock behind proprietary Android drivers, without compromising our open source principles.
Adopting these drivers to a Neuro has required some technical work.
And since libgl is originally designed for GLIPC-based systems, we had to adapt it to work with Mazo, which is a lightweight C library used in a Neuro.
And this involves reworking driver support and update also system dependencies, aligning also with Open Harmony, Clang, LLVM toolchain.
So we can look at this diagram to better understand how it works.
At the top we have Mazo based on Neuro, including applications and render service compositor.
And Libpibrs sits in between this layer and the Android libraries handling symbol of writing.
Dynamically linking and providing wrappers to EGL and Ralllock.
And below that, Android's proprietary libraries handle direct communication with hardware using bionic lipc to facilitate native hardware access.
Now let's talk about what we have achieved so far and what's coming next.
With successfully applied to Neuro patches on top of the Linux kernel, including support for HDF, which is the hardware driver foundations used in Open Harmony, which simplifies drivers development across different hardware platforms.
And another Mazo in Neuro is the system is running now on an LXC container.
And we've successfully enabled this play output using DRM.
We can now render graphics, which is crucial for the functional user interface.
And at the same time, we're working on setting up the system environment and managing library dependencies.
To ensure everything runs smoothly on Mazo.
So next step is to enable other critical subsystems like audio sensors and telephony to make a system usable on mobile hardware.
And we plan to improve compatibility with between Android's proprietary libraries and the Neuro Mazo based environment.
And we also are refining compatibility with the LLVM based tool chain used by Open Harmony and ensure a biocompatibility.
We're also aiming to collaborate more with hardware vendors like VOLINE and other partners to ensure better open source support with devices.
So all these efforts bring us closer to an open source mobile OS.
So we still have work ahead, but progress is steady.
So the Neuro is not just about a phone, but it's a vision of a future of an open source software and mobile.
And it aims to be a fully open and privacy-respecting alternative.
And our collaboration with both Open Harmony and other open source communities such as React Native and Server and More.
Strengthens the ecosystem.
Finally, I invite you to join the project to build this future together for an open secure and adaptable platform.
You can find the repositories on GitHub.
And so anyone can contribute to local projects to create a global impact with an ERO by also upstreaming the innovation to open Harmony.
So thank you.
Are there any questions?
So yes, can you repeat a question please?
Can you repeat a question please?
So the question is that the fact yes is open source.
Yes, it's open source both the developers tools and the runtime that runs on top of open Harmony.
Yes, sorry the time is up.
Let's thank him once again.