WEBVTT 00:00.000 --> 00:19.000 So, we have our next speaker and he will present you about the remote operating system, which is like a light. 00:19.000 --> 00:29.000 Hello everyone, I'm Francesco, and I'm the comitter representative of the Honor Project, and I would like to introduce you to Honor 00:30.000 --> 00:32.000 So, what is Honor? 00:32.000 --> 00:37.000 Honor is a project, open source project managed by the Eclipse Foundation. 00:37.000 --> 00:42.000 And when we started on Honor, we wanted to create a truly open and global ecosystem. 00:42.000 --> 00:51.000 And one of our key principles was to not reinvent the wheel, so therefore we built on top of the foundation of Open Harmony, 00:51.000 --> 00:56.000 which is a project incubated by the Open Auto Foundation in China. 00:57.000 --> 01:11.000 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. 01:11.000 --> 01:23.000 So, this collaboration agreement between the two foundations brings together the expertise of the global open source development. 01:23.000 --> 01:32.000 And the new architecture builds on top of the solid foundation of Open Harmony to enhance and expand its capabilities, 01:32.000 --> 01:43.000 tailoring it for global and market needs while ensuring IP compliance with advanced IP tool chain. 01:44.000 --> 01:57.000 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. 01:57.000 --> 02:04.000 And this demonstrates its flexibility among different use cases and its scalability. 02:04.000 --> 02:08.000 And the global open Harmony is growing as a platform for smart devices. 02:08.000 --> 02:16.000 It powers projects like Huawei's harmonious next, which demonstrates Open Harmony's scalability. 02:16.000 --> 02:22.000 And Open Harmony's success is reflecting in over 300 products on the market. 02:22.000 --> 02:28.000 And more than 7,000 contributors and over 100 million lines of code. 02:28.000 --> 02:46.000 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. 02:46.000 --> 02:54.000 Open Harmony primarily language for developed applications is RTS, which is an extension of TypeScript. 02:54.000 --> 02:58.000 It's a compiled language optimized for open Harmony. 02:58.000 --> 03:08.000 And, yeah, to support developers, we are expanding it to support React Native as well. 03:08.000 --> 03:17.000 And to enable cross-platform development and support existing applications without major rewrites. 03:17.000 --> 03:30.000 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. 03:30.000 --> 03:45.000 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. 03:46.000 --> 04:08.000 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. 04:08.000 --> 04:12.000 And which is fully committed to privacy and open source principles. 04:12.000 --> 04:19.000 And the Rear Developer Phone is designed with European regulatory requirements in mind. 04:19.000 --> 04:30.000 And aims to be a developer-friendly device where developers can test and deploy their innovations. 04:31.000 --> 04:44.000 This phone complements already available developer boards, like Raspberry Pi and others, to enhance the ecosystem with more mobile portability. 04:44.000 --> 04:49.000 And our collaboration with Voila has been crucial in the development of this device. 04:49.000 --> 04:54.000 And Voila is known for their contribution in open source hardware. 04:54.000 --> 05:02.000 Like the Voila X-23 and also supported various Linux-based OSes, such as Ubuntu Touch. 05:02.000 --> 05:08.000 And now extends their expertise onto a Neuro. 05:08.000 --> 05:14.000 However, building an open source mobile platform is without any challenges. 05:14.000 --> 05:19.000 Most hardware today depends on close source proprietary Android drivers. 05:19.000 --> 05:24.000 And to overcome this, we use a compatibility layer called the Libpibrs. 05:24.000 --> 05:29.000 I'll further already gave a detailed explanation on which I will be short. 05:30.000 --> 05:39.000 So Libpibrs works by translating function calls from GLIPC-based systems to Android's proprietary libraries that use Vionic. 05:39.000 --> 05:53.000 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. 05:54.000 --> 06:09.000 This layer, the approach allows a Neuro to take advantage of hardware features, lock behind proprietary Android drivers, without compromising our open source principles. 06:09.000 --> 06:14.000 Adopting these drivers to a Neuro has required some technical work. 06:14.000 --> 06:26.000 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. 06:26.000 --> 06:37.000 And this involves reworking driver support and update also system dependencies, aligning also with Open Harmony, Clang, LLVM toolchain. 06:37.000 --> 06:42.000 So we can look at this diagram to better understand how it works. 06:42.000 --> 06:50.000 At the top we have Mazo based on Neuro, including applications and render service compositor. 06:50.000 --> 06:57.000 And Libpibrs sits in between this layer and the Android libraries handling symbol of writing. 06:57.000 --> 07:04.000 Dynamically linking and providing wrappers to EGL and Ralllock. 07:04.000 --> 07:19.000 And below that, Android's proprietary libraries handle direct communication with hardware using bionic lipc to facilitate native hardware access. 07:19.000 --> 07:24.000 Now let's talk about what we have achieved so far and what's coming next. 07:24.000 --> 07:40.000 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. 07:40.000 --> 07:48.000 And another Mazo in Neuro is the system is running now on an LXC container. 07:48.000 --> 07:54.000 And we've successfully enabled this play output using DRM. 07:54.000 --> 08:01.000 We can now render graphics, which is crucial for the functional user interface. 08:01.000 --> 08:09.000 And at the same time, we're working on setting up the system environment and managing library dependencies. 08:09.000 --> 08:13.000 To ensure everything runs smoothly on Mazo. 08:13.000 --> 08:25.000 So next step is to enable other critical subsystems like audio sensors and telephony to make a system usable on mobile hardware. 08:25.000 --> 08:34.000 And we plan to improve compatibility with between Android's proprietary libraries and the Neuro Mazo based environment. 08:34.000 --> 08:45.000 And we also are refining compatibility with the LLVM based tool chain used by Open Harmony and ensure a biocompatibility. 08:45.000 --> 08:57.000 We're also aiming to collaborate more with hardware vendors like VOLINE and other partners to ensure better open source support with devices. 08:57.000 --> 09:03.000 So all these efforts bring us closer to an open source mobile OS. 09:03.000 --> 09:08.000 So we still have work ahead, but progress is steady. 09:08.000 --> 09:17.000 So the Neuro is not just about a phone, but it's a vision of a future of an open source software and mobile. 09:17.000 --> 09:21.000 And it aims to be a fully open and privacy-respecting alternative. 09:21.000 --> 09:30.000 And our collaboration with both Open Harmony and other open source communities such as React Native and Server and More. 09:30.000 --> 09:34.000 Strengthens the ecosystem. 09:34.000 --> 09:45.000 Finally, I invite you to join the project to build this future together for an open secure and adaptable platform. 09:45.000 --> 09:48.000 You can find the repositories on GitHub. 09:48.000 --> 10:00.000 And so anyone can contribute to local projects to create a global impact with an ERO by also upstreaming the innovation to open Harmony. 10:00.000 --> 10:03.000 So thank you. 10:03.000 --> 10:23.000 Are there any questions? 10:23.000 --> 10:27.000 So yes, can you repeat a question please? 10:27.000 --> 10:34.000 Can you repeat a question please? 10:34.000 --> 10:39.000 So the question is that the fact yes is open source. 10:39.000 --> 10:52.000 Yes, it's open source both the developers tools and the runtime that runs on top of open Harmony. 10:52.000 --> 10:55.000 Yes, sorry the time is up. 10:55.000 --> 10:58.000 Let's thank him once again.