Fact-checked by Grok 2 weeks ago

libhybris

libhybris is an open-source designed to enable the loading and execution of Android's Bionic-compiled layer () libraries and drivers within glibc-based or other libc environments on systems. Developed initially by Stskeeps as part of the project, it acts as a libdl-like interface that overrides Bionic symbols with equivalents, bridging the gap between Android's userspace hardware adaptations and standard applications. This facilitates the use of proprietary Android drivers for components such as GPUs, cameras, audio, sensors, and on devices lacking open-source alternatives. Primarily utilized in mobile Linux distributions, libhybris has been integral to projects like , where it integrates Android Board Support Packages (BSPs) into the operating system's architecture, allowing hardware access through middleware components such as pulseaudio-modules-droid and gst-droid for audio and multimedia. It supports a wide range of ARM-based devices from manufacturers including HTC, , , , , , and , with adaptations covering smartphones and tablets running kernels from 2.6 to 4.9. Historically, it powered ports for , enabling Mir display server compatibility with Android GPU drivers, and was employed in to containerize Android components on downstream kernels for devices without mainline support. The library requires ARMv7 or architectures and 3.17 or later, often in conjunction with frameworks like Halium or Project Treble for 9 compatibility. While effective for accelerating development on hardware, libhybris has seen reduced adoption in some ecosystems, such as its deprecation in in favor of native drivers, though it remains active in adaptations via repositories like mer-hybris. Licensed under the 2.0, libhybris continues to support in Wayland-based environments and custom plugins for multimedia on libhybris-enabled devices.

Overview

Definition and Purpose

Libhybris is an open-source compatibility layer designed to enable the loading and execution of libraries compiled against Android's bionic libc—such as hardware abstraction layers (HALs)—within systems that use or libc implementations. This bridging mechanism translates bionic-specific calls into equivalents compatible with standard C libraries, allowing Android-compiled binaries to function in non-Android environments without extensive recompilation. The primary purpose of libhybris is to permit distributions to access and utilize proprietary or vendor-optimized hardware drivers on devices originally engineered for platforms, all while avoiding the overhead of a complete stack. By providing a lightweight interface for hardware interactions, it supports the integration of 's userspace components into glibc-based systems, particularly for mobile and embedded applications. Key benefits include enabling for critical components like (via EGL/GLES), audio, sensors, and (through the Radio Interface Layer or RIL), which enhances performance in mobile operating systems without requiring full driver reverse-engineering. This approach significantly lowers the barrier for environments to locked-down mobile hardware. Developed within the Mer project in the early amid Android's growing dominance in the market, libhybris emerged to facilitate software stacks on devices reliant on Android-specific drivers.

Relation to Android Ecosystem

Libhybris serves as a that enables the integration of 's bionic libc-compiled libraries into environments utilizing or libc implementations. By acting as a wrapper, it translates calls from the lightweight bionic C library—developed by for —to equivalent functions in , while also providing a custom implementation of libdl for dynamic linking of binaries. This layer depends heavily on vendor-supplied Android Layers () to facilitate hardware interactions, bridging the gap between non-Android user-space applications and device-specific drivers. For instance, it relies on the Gralloc HAL module for allocating and managing graphics memory buffers essential for rendering operations, and on AudioFlinger for routing and processing audio streams through the device's sound hardware. In the overall software stack, libhybris occupies a pivotal position between user-space applications and kernel-level drivers, many of which are derived from sources, thereby allowing accelerated features such as without requiring a complete . This setup supports the reuse of proprietary hardware blobs on standard distributions. To achieve this , libhybris employs mechanisms like LD_PRELOAD, which intercepts and redirects calls to libraries at runtime, ensuring binary compatibility for closed-source components that would otherwise be incompatible with glibc-based systems.

History

Origins in Mer Project

libhybris originated in 2012 within the Project, an open-source initiative launched by the company as a community-driven successor to the operating system. Mer aimed to establish a robust, middleware-agnostic foundation for mobile distributions, addressing the challenges posed by Android's growing lock-in on hardware ecosystems, where proprietary drivers and adaptations were predominantly tailored for Android's Bionic libc rather than standard glibc-based systems. This context was critical for projects like , Jolla's mobile platform, which sought to leverage existing hardware without the need for extensive proprietary reinvestments. The library was primarily developed by engineers, with Carsten Munk, then Chief Research Engineer at , serving as the key initiator. Munk released an initial prototype in August 2012, driven by the need to port to devices originally designed for , thereby enabling broader hardware compatibility for Mer-based systems. Early contributions also came from community members associated with the Open webOS project, including developers like Florian Haenel, Thomas Perl, and Simon Busch, who collaborated on integrating Android components into glibc environments. The core motivation behind libhybris was to facilitate the reuse of Android's mature Layer (HAL) ecosystem—encompassing drivers for sensors, cameras, and processing units (GPUs)—directly within -based Linux distributions. By providing a translation layer between Android's Bionic libc and , it allowed developers to avoid the costly and time-intensive task of reimplementing hardware drivers from scratch, particularly for GPU acceleration via . This approach enabled efficient hardware access for non-Android systems like and , focusing initially on and input handling to support Qt-based applications. The first public prototype appeared on in August 2012 under Munk's personal repository (stskeeps/libhybris), with a commit demonstrating basic Bionic-to-glibc translation for shared libraries. By early , the project gained visibility through Mer Project announcements, leading to a cleaned-up version released under the 2.0 and hosted in the mer-hybris organization on , where it focused on foundational compatibility for hardware adaptations.

Evolution and Key Milestones

In 2014, libhybris saw initial integration into , enabling ports to Android-based devices such as the Google Nexus 4 (codenamed ""). This marked a significant step in utilizing libhybris as a to leverage hardware abstraction layers () within a glibc-based environment, allowing to access proprietary drivers for graphics and other hardware without full dependency. By 2016, detailed installation guides for on the Nexus 4 further solidified this integration, demonstrating libhybris's role in facilitating multi-boot setups alongside . The period from 2017 to 2019 brought expanded adoption through forks and collaborative efforts. In April 2017, the Halium project was announced, uniting developers from (via UBports), , communities, and others to standardize support using libhybris as the core compatibility mechanism. forked and adapted libhybris to work with libc, enabling compatibility with bionic-compiled libraries on musl-based systems, while extending support to ARM64 () architectures for devices running Halium 9 (targeting Android 9). similarly incorporated these forks via Halium, broadening libhybris's applicability to diverse Linux mobile distributions. Between 2020 and 2023, libhybris underwent enhancements to support newer HALs, including compatibility with and 11 through Halium branches like halium-10.0, which addressed evolving vendor interfaces for . Graphics improvements focused on integrating support via Android's graphics HAL, allowing better rendering performance in environments without native Vulkan drivers. In 2022, maintenance of the original Project's libhybris repository shifted toward community-driven forks, such as the libhybris/libhybris repository, as upstream activity waned. From 2024 to 2025, updates emphasized compatibility with via Halium 14, incorporating branches like halium-14.0 to handle updated requirements for modern devices. Recent discussions in the UBports forum in October 2025 highlighted versioning challenges with libhybris and Halium, particularly around aligning Android base versions with ongoing ports. The libhybris/libhybris repository remains active, with over 70 open issues as of late 2025 focused on bug fixes for stability and device-specific integrations. Key milestones include the release of libhybris 0.1.0+git within layers, which standardized packaging for embedded Linux builds and facilitated broader adoption. Additionally, libhybris's integration into Nemo Mobile, a Mer-based distribution continuing MeeGo's legacy, enabled hardware adaptations for mobile devices using the Nemo stack alongside drivers.

Technical Architecture

Compatibility Layer Mechanics

Libhybris operates as a shim that provides compatibility between Android's Bionic libc and glibc-based systems by implementing a libdl-API-like . This core mechanism includes a fake libdl.so, which loads Bionic-compiled libraries and resolves their symbols through a dedicated translation table. Wrappers for standard functions like dlopen and dlsym facilitate and symbol lookup, allowing Android hardware adaptations to function without full dependencies. The symbol translation process maps Android-specific functions—for instance, those defined in libhardware.so—to equivalent glibc implementations, ensuring seamless interoperability. This mapping addresses key differences between Bionic and glibc, particularly in threading models where pthreads are wrapped and sanity-checked for compatibility, and in memory management routines that require adjustments to avoid conflicts. By overriding Bionic symbols with glibc-based alternatives during resolution, libhybris enables applications to invoke Android APIs as if running in a native environment. During the loading process, applications link directly against libhybris, which intercepts calls directed at binary blobs, such as GPU or telephony drivers. These intercepted calls are then forwarded to the underlying via interfaces, bypassing the need for 's full user-space stack while maintaining hardware access. This interception occurs at the level, ensuring that Bionic-linked code executes correctly on hosts. To build libhybris, developers compile it using the , which provides the necessary Bionic headers and toolchain for compatibility. Integration into Linux distributions, such as those using Yocto or , relies on files generated during the build to handle library paths and dependencies. The process typically involves cloning the source repository, running autogen.sh for configuration, and executing make for compilation and installation.

Integration with Hardware Abstraction Layers

Libhybris facilitates hardware access in non- Linux environments by wrapping and adapting Android's Hardware Abstraction Layers (s), enabling glibc-based systems to utilize bionic-compiled drivers originally designed for devices. This is central to projects like Halium, which standardize usage across mobile distributions, allowing seamless bridging between Android's hardware interfaces and userland applications. Supported s include components such as Gralloc for buffer allocation and HWComposer for layer composition, AudioHAL for sound processing, Sensors HAL for device sensors, and telephony via with the RIL (Radio Interface Layer) daemon. The adaptation process involves libhybris providing specialized wrappers to intercept and translate Android HAL calls into compatible Linux operations. For instance, the hybris_gralloc wrapper manages graphics buffer allocation by handling Android's memory requirements, such as shared memory mechanisms, and mapping them to Linux-native equivalents to ensure efficient resource use without direct bionic dependency. Similarly, for audio, libhybris employs dlopen to load the AudioHAL directly, while middleware like pulseaudio-module-droid routes audio streams through the HAL. Sensors HAL integration follows a comparable pattern, with wrappers exposing sensor data to Linux frameworks, and telephony relies on socket-based communication with the RIL daemon to handle modem interactions. These wrappers minimize the need for deep Android code modifications, prioritizing compatibility layers for C++ interfaces where necessary. Libhybris supports HAL versions spanning Android 4.x through 10 (as of 2025), aligning with Halium versions from 6 to 10; for deprecated components like the legacy Camera HAL, it includes shims to maintain without requiring full driver rewrites. This version handling ensures ports remain viable on devices with varying Android firmware ages. At the kernel level, libhybris depends on Android-derived modules—such as kgsl for GPUs—to expose hardware functionality, with ioctls passed through directly from user space to kernel drivers, avoiding unnecessary abstraction overhead. A representative workflow for GPU rendering illustrates this integration: libhybris loads Android's libEGL.so library, which interfaces with the graphics HAL, and maps the resulting calls to open-source drivers like Mesa or freedreno for GPUs, enabling hardware-accelerated rendering in applications such as compositors. This approach leverages existing Android blobs where full open-source kernel support is unavailable, providing a practical path to hardware utilization in distributions like and .

Implementations and Usage

Adoption in Linux Distributions

Libhybris has been a core component of , developed by , since its initial release in 2013, facilitating ports to devices by enabling the use of proprietary drivers within Sailfish OS's gesture-based . This integration allows , built on the project, to leverage 's layers () through libhybris's compatibility mechanism, supporting a wide range of smartphones without requiring fully open-source drivers. In , an Linux-based for mobile devices, libhybris was adopted starting in 2017 to enable and proprietary driver support on devices with Android-derived kernels. Developers utilized pmbootstrap, postmarketOS's build tool, to create libhybris-enabled images via the hybrisaports , allowing the to run on lacking mainline compatibility. However, as of late 2024, libhybris support has been discontinued in , with the project shifting focus away from hybris-based adaptations. Halium, a libhybris-based , has been to Ubuntu Touch since 2017, providing a standardized interface that bridges Android's proprietary drivers with the Lomiri . This setup enables ports on devices running 9 through 13 by translating bionic-compiled libraries for glibc-based systems, simplifying hardware integration for cameras, sensors, and other peripherals. Beyond these, libhybris has seen adoption in other Linux distributions for mobile and embedded use cases. Nemo Mobile, a continuation of the project, integrates libhybris through Halium compatibility, with ports to various devices including the Xiaomi 7 and Poco series via Halium. , KDE's mobile interface, initially relied on libhybris within Halium for on devices like the , though support is being phased out in favor of mainline kernel devices. Additionally, libhybris is integrated into and build systems through dedicated recipes in layers like meta-android, enabling its use in custom embedded Linux images for hardware adaptations. Distributions typically track libhybris via Git snapshots rather than stable releases, with Halium versions (e.g., 7.1 through 14) aligning to corresponding versions 7 through 14, including Halium 14 for as of October 2025, to ensure compatibility with evolving APIs. This versioning approach allows projects like and to maintain support for newer Android hardware ecosystems.

Supported Hardware Platforms

Libhybris has been implemented on a wide range of Snapdragon-based devices, leveraging the compatibility layer to interface with GPUs through binary blobs or the open-source Freedreno driver stack. Notable examples include the MSM8916 SoC in the 5 (hammerhead), where libhybris enables for graphics and multimedia in non-Android environments. Support extends to the SDM845 SoC in devices like the , facilitating ports to distributions such as and . More recent implementations cover up to the SM8350 (Snapdragon 888) in 2021-era smartphones, with ongoing community efforts integrating Freedreno for improved open-source compatibility. For Samsung Exynos platforms, libhybris supports ports on S series devices, particularly those with GPUs. The 7420 SoC in the S6 (zeroltexx) utilizes libhybris to bridge hardware abstractions, enabling features like GPU rendering in Linux-based systems such as community adaptations. Similar support exists for earlier models like the S4 (jfltexx) with 4412, where the layer handles display and sensor integration. Sony Xperia devices receive extensive libhybris support, especially in community ports, due to their hardware and active developer involvement. The Xperia Z3 (), equipped with the 400 GPU on a , demonstrates robust compatibility for camera, audio, and graphics acceleration. This extends to variants like the Xperia Z3 Compact (), integral to early Mer Project adaptations and ongoing maintenance in projects like Halium. Other vendors feature targeted libhybris implementations through community efforts. HTC's One M7 (m7) with Snapdragon 600 benefits from established ports for and . Huawei's P8 Lite uses libhybris for integration in . Motorola's (shamu) on Snapdragon 805 supports full hardware access in . Xiaomi's Mi A1 (tissot) with Snapdragon 625 enables Android 7.1-based ports via Halium. Limited community-driven support exists for NXP processors in select tablets and for SoCs in devices like certain Volla handsets, though these remain experimental and less mature. As of 2025, over 50 devices are documented in the wiki (though libhybris support has been discontinued there), with Halium accelerating new ports based on hardware abstraction layers for enhanced compatibility on Treble-enabled smartphones.

Limitations and Alternatives

Known Challenges and Limitations

Libhybris, as a bridging Android's Bionic-based hardware adaptations with systems, introduces challenges due to the translation of API calls between the two environments. Compatibility gaps persist with evolving Android hardware abstraction layers (HALs), as libhybris was primarily developed around older Android versions and may not fully support newer interfaces. For instance, support for advanced HALs such as for acceleration remains incomplete, limiting workloads. Additionally, changes in newer Android versions, including updates to the Vendor Interface Object (VINTF), can cause integration issues, requiring custom patches that are not always available or stable across devices. As of November 2025, libhybris support remains limited to Android versions up to 12 in projects like Halium, with community efforts for versions 14 and 15 requiring unofficial patches. Security concerns arise from libhybris's reliance on vendor blobs, which are closed-source drivers extracted from Android . These blobs often contain unpatched vulnerabilities, as vendors prioritize their own ecosystems over third-party updates, leading to potential exploits in outdated . Sandboxing mechanisms in libhybris implementations vary by distribution and may not always include equivalents to Android's SELinux, such as in some setups, potentially exposing the system to broader risks from unverified interactions. The maintenance burden is significant due to the dependency on stagnant Android vendor blobs, which frequently break during kernel updates or hardware revisions. Porting libhybris to new devices requires extracting and adapting these blobs, a process that demands device-specific tweaks and can fail with upstream changes, increasing the effort for maintainers. Persistent issues stemming from mismatched implementations continue to challenge adaptations. Licensing for libhybris itself follows the Apache 2.0 license, promoting open reuse, but its integration with proprietary code—often under restrictive vendor terms—complicates redistribution and modification. This mix can conflict with GPL-licensed components in distributions, as the closed blobs cannot be freely altered or shared, hindering full open-source compliance in deployments.

Comparison with Other Solutions

Libhybris provides a lightweight for integrating Android's hardware abstraction layer (HAL) into glibc-based systems on devices, contrasting with full solutions like Anbox, which run a complete in a on desktops. Anbox, developed in 2017, leverages containers to boot a full system for app execution but requires significant overhead for the entire , whereas libhybris avoids this by directly wrapping only the necessary bionic-based hardware adaptations without emulating a full Android userspace. This makes libhybris more resource-efficient for hardware access on resource-constrained , though it demands device-specific efforts tied to the original Android vendor blobs, unlike Anbox's more generic focus on x86 architectures for desktop integration. In comparison to native Linux drivers such as freedreno for GPUs or i915 for graphics, libhybris offers broader support for Android hardware components like cameras and sensors where open-source alternatives remain incomplete. Native drivers provide a purer (FOSS) implementation with lower overhead and better integration into mainline kernels, but they often lack full functionality for non-graphics peripherals on older or vendor-specific mobile SoCs. Libhybris, by contrast, incurs some performance overhead from the compatibility shim but enables functionality on devices without mature native driver support, prioritizing practicality over ideological purity. Halium extends libhybris by standardizing the HAL middleware for /Linux distributions on Android-based mobile devices, facilitating projects like and through unified interfaces for services such as telephony and audio. While Halium builds directly on libhybris for hardware bridging, alternatives like custom modifications maintain an Android-like user interface and app ecosystem without incorporating a full userspace, avoiding the need for HAL translation layers altogether. These Android-centric hacks emphasize continuity of proprietary app compatibility over the desktop-oriented environments enabled by libhybris and Halium. Waydroid, introduced around 2020, represents a more recent approach that runs a full system within a host for seamless app integration, often outperforming libhybris in Android app compatibility due to its complete runtime support. Unlike libhybris's HAL-only focus, which targets Linux userspace on mobile hardware with minimal Android components, Waydroid demands higher resource usage for the containerized environment but provides better isolation and broader desktop applicability, including sessions. Overall, libhybris excels in reviving legacy devices from around 2015, such as older Qualcomm-based smartphones lacking mainline support, by leveraging existing drivers without requiring full OS overhauls. However, it trades off against modern features like advanced acceleration, where vendor-locked solutions or native drivers offer superior performance and future-proofing on newer hardware.

Development Status

Current Maintenance and Updates

Libhybris is primarily maintained through the libhybris/libhybris repository on GitHub, a fork of the original mer-hybris/libhybris project, with the upstream mer-hybris seeing its last significant activity in 2024 before maintenance shifted to community forks. Halium, a related hardware abstraction layer project, continues to integrate libhybris patches, particularly for Ubuntu Touch and similar mobile Linux initiatives, ensuring compatibility with evolving Android hardware interfaces. The project lacks formal versioning beyond its initial 0.1.0 release from 2013 and does not use release tags, though commits provide support for as of 2024-2025. Recent commits in 2025 have addressed compatibility issues, including a merge in June 2025. The last confirmed commit was on June 30, 2025. Activity in the original Project has declined, with efforts increasingly led by communities around and Halium, though dropped libhybris support on November 17, 2024, in favor of mainline kernel approaches. As of November 2025, the primary repository reports 71 open issues and ongoing contributions, indicating sustained but modest involvement.

Community and Contributions

The libhybris project is primarily driven by open-source communities focused on mobile distributions, with key discussion hubs including the wiki for technical documentation and the IRC channel #postmarketos on for real-time collaboration. UBports maintains dedicated forums for Halium-related discussions, where libhybris integration in ports is frequently addressed by developers tackling hardware compatibility issues. Additionally, Jolla's Together platform serves as a forum for community ports of , often involving libhybris adaptations for non-official devices. Contributions to libhybris follow standard open-source practices on its GitHub repository, where developers fork the project, implement changes, and submit pull requests through the issue tracker for review. Testing is essential and typically requires deploying builds on target hardware, using tools like the Android Debug Bridge (adb) logcat to capture and analyze runtime logs for hardware abstraction layer (HAL) functionality. Prominent individual contributors include Oliver Smith, a lead developer in who has advanced libhybris support for newer Android versions and device ports. UBports teams have extended libhybris through Halium, enabling ports for devices like the S10. while corporate involvement from has diminished following its strategic pivot away from broad hardware support. Essential resources for engagement include the Mer Wiki's Adaptations/libhybris page, which provides porting guides and was last updated on June 23, 2025. Build instructions are available for integrating libhybris into Yocto-based systems via layers and for environments through APKBUILD recipes. Community efforts face challenges such as relatively low barriers to initial porting but significant hurdles in updating vendor blobs across versions, which often require device-specific tweaks. There are ongoing calls within these communities to transition toward more () drivers to reduce reliance on closed blobs and improve long-term maintainability.

References

  1. [1]
    libhybris/libhybris: Hybris is a solution that commits hybris ... - GitHub
    Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems.Libhybris · Issues 71 · Actions · Activity
  2. [2]
    Libhybris: Load Android Libraries, Override Bionic Symbols - Phoronix
    Sep 25, 2012 · A libdl-API-like implementation that happens to be able to load Android libraries, and overrides some symbols from bionic with glibc based ones.
  3. [3]
    Libhybris Let You Use Android Drivers & HW Libraries in Linux
    Apr 8, 2013 · Libhybris Let You Use Android Drivers & HW Libraries in Linux · Open Source GPU drivers. This would be the ideal solution, as you would just be ...
  4. [4]
    Architecture - Sailfish OS Documentation
    Sailfish OS can run on top of standard Linux hardware with native drivers, or one can utilize the drivers for an Android-compatible hardware via libhybris, ...Middleware layer · Application and UI layer · Call chains
  5. [5]
    Adaptations/libhybris - Mer Wiki
    Jun 23, 2025 · libhybris adaptations include smartphones from HTC, Huawei, Motorola, Nexus, Oneplus, Samsung, Sony, Xiaomi, and others, and tablets.
  6. [6]
    Hybris - postmarketOS Wiki
    Nov 17, 2024 · Libhybris is an Android compatibility layer, allowing libraries compiled with bionic (Android) libc to be loaded by applications built with different libc.Missing: open | Show results with:open
  7. [7]
    mer-hybris - Sailfish OS Adaptation Repositories - GitHub
    Sailfish OS Adaptation Repositories. Repositories related to hardware adaptations of Sailfish OS. 39 followers; Finland; https://docs.sailfishos.org/Tools ...
  8. [8]
    Multimedia - Sailfish OS Documentation
    On libhybris devices, hardware codecs, camera support and hardware video buffers from the Android HAL are exposed in a custom open source GStreamer plugin ...
  9. [9]
    Libhybris Proposed For Wayland's Weston - Phoronix
    Sep 6, 2013 · Libhybris is a compatibility layer for allowing Bionic-based Android libraries/drivers to be loaded by glibc-based Linux systems.
  10. [10]
    A look at Mer - LWN.net
    Jul 24, 2013 · The Mer project was born out of the ashes of the MeeGo mobile-oriented distribution in 2011. In an admittedly provocatively titled talk ...
  11. [11]
    Adaptations/libhybris/gpu - Mer Wiki
    Apr 24, 2015 · A page to track graphics adaptions to various devices. Qualcomm. MSM8960 - Adreno 225. Motorola Photon Q. With EGL_PLATFORM=fbdev seems to ...
  12. [12]
    mer-hybris/audioflingerglue - GitHub
    Contribute to mer-hybris ... Simple service that replaces AudioFlinger and library for forwarding calls made to custom AudioFlinger to client.Missing: libhybris | Show results with:libhybris
  13. [13]
    Wayland utilizing Android GPU drivers on glibc based systems, Part 1
    ### Summary of libhybris from http://mer-project.blogspot.com/2013/04/wayland-utilizing-android-gpu-drivers.html
  14. [14]
    How to Use Libhybris and Android GPU Libraries with Mer (Linux ...
    Apr 21, 2013 · I've found a faster and easier way to play with libhybris thanks to Martin Brook (vgrade) who wrote a tutorial on how to use libhybris with Mer on the ...
  15. [15]
    First Sailfish OS build for Nexus 4 released - OSnews
    Mar 27, 2014 · This Nexus 4 release isn't using native glibc drivers – it uses libhybris with Android drivers. I guess same can be done for Nexus 7 (and ...Missing: integration | Show results with:integration
  16. [16]
    Adaptations/libhybris/Install SailfishOS for mako - Mer Wiki
    Dec 29, 2016 · Installation steps · Install Android base zip by following instructions: CyanogenMod website · Install the Sailfish OS zip on top of that Android ...Missing: 2014-2016 | Show results with:2014-2016
  17. [17]
    Halium is in the air!
    Apr 24, 2017 · Project Halium is the effort by the community which aims to bring the common grounds for different distributions and have a common base.Missing: history timeline
  18. [18]
    Activity · Halium/android - GitHub
    halium: switch to halium-13.0 branch of libhybris fork. NotKitpushed 1 commit to halium-14.0 • 077495d…b3bc388 •. on Apr 23. More activity actions. More ...
  19. [19]
    Implement Vulkan | Android Open Source Project
    Devices that launch through Android 10 must support Vulkan 1.1. Other devices can optionally support Vulkan 1.3, 1.2, and 1.1. Support a Vulkan version. An ...
  20. [20]
    Android version and Libhybris | UBports Forum
    Oct 13, 2025 · So I am a bit confused in regards to Android versions and Libhybris/Halium these days. I was a regular UT user a few years back and then the ...Missing: Jolla engineers 2012
  21. [21]
    Issues · libhybris/libhybris - GitHub
    Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems - libhybris/libhybris.Missing: Gralloc LD_PRELOAD
  22. [22]
    libhybris 0.1.0+git - OpenEmbedded Layer Index
    Name, libhybris. Version, 0.1.0+git (c3a76b4a32c19812c3eebd41d34dfed2430e6d7d). Summary. Description, Hybris is a solution that commits hybris, ...Missing: Nemo | Show results with:Nemo
  23. [23]
    Nemo Mobile - Mer Wiki
    Oct 25, 2018 · Nemo Mobile is a Linux distribution for mobile, which continues MeeGo Community Edition project. One of the main goals of Nemo is to replace closed source ...Missing: adoption | Show results with:adoption
  24. [24]
    Scope of Halium
    ... HAL (a standard libhybris wrapper). Libhybris ... This will contain more than a compat layer and may have quite deep integration within Android code.
  25. [25]
    https://github.com/mer-hybris/pulseaudio-modules-droid
  26. [26]
    https://github.com/libhybris/libhybris/tree/master/compat/camera
  27. [27]
    Hardware Adaptation Development Kit - Sailfish OS Documentation
    Sailfish OS then uses the libhybris layer to connect the linux system into the vendor's BSP. ... This is possible since there is a large degree of ...
  28. [28]
    Halium | Ubports
    Libhybris serves as the bridge between the Android hardware drivers and the distribution, enabling compatibility. The Android container uses chroot to ...
  29. [29]
    Nemomobile in May 2023
    May 26, 2023 · The development efforts have been focused on two key areas: porting Nemomobile to Qt6 and extending compatibility with Halium devices. Towards ...
  30. [30]
    Plasma Mobile: Technical debt and moving forward
    Dec 14, 2020 · In 2017, several of communities working on bringing GNU/Linux to mobile devices came together and introduced Project Halium. This was ...Missing: musl ARM64<|separator|>
  31. [31]
    Halium - Manjaro Wiki
    Dec 16, 2021 · It is possible to install Manjaro on some Android phone using Project Halium and libhybris. Currently, only Halium 9 is supported but the plan is to add ...
  32. [32]
    libhybris - OpenEmbedded Layer Index
    Other branches ; pyro (Yocto Project 2.3), libhybris 0.1.0+gitrX ; morty (Yocto Project 2.2), libhybris 0.1.0+gitrX ; krogoth (Yocto Project 2.1), libhybris 0.1.0+ ...
  33. [33]
    Halium Project
    Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.Missing: 2017 postmarketOS musl libc ARM64
  34. [34]
    Device Overview — Halium documentation
    Device Overview¶. These pages detail devices that. ( A ) have a running Halium Image; ( B ) had a Halium image in the past; ( C ) users want to see ported.
  35. [35]
    Devices - postmarketOS Wiki
    This page contains a list of devices supported by postmarketOS. There are currently 703 devices supported by postmarketOS, and 1,420 devices ...All devices · Renamed Devices · Xiaomi POCO X3 NFC (xiaomi... · CategoryMissing: libhybris | Show results with:libhybris
  36. [36]
    [PDF] IPDPS RADR22 - Operating System Convergence
    Advantages: ▸. Only one codebase maintained. ▸. Better performance because there is no virtualization overhead. Disadvantages: ▸. UI redesign typically required ...
  37. [37]
    [PDF] Porting mainline Linux to mobile phones
    “security fixes”. ○ Lots of out-of-tree code. ○ Questionable code quality ... ○ Ubuntu Touch reuses Android binaries through libhybris. ○ Unless you ...<|control11|><|separator|>
  38. [38]
    [PDF] Halium Documentation
    Feb 15, 2023 · • [ ] Build and integrate the libhybris (upstream) to the base rootfs. 112. Chapter 2. Contents. Page 117. Halium Documentation. • [ ] Create ...
  39. [39]
    Match rules | Android Open Source Project
    Oct 9, 2025 · Thus, a device with a HAL at version 10 in its manifest file remains compatible with a framework that states 5-7 in its compatibility matrix.Missing: libhybris | Show results with:libhybris
  40. [40]
    [PDF] An Empirical Study of Proprietary Vendor Blobs in Android Firmware
    Oct 14, 2024 · This work underscores the critical security concerns associated with vulnerable vendor blobs and emphasizes the urgent need for timely updates ...Missing: libhybris | Show results with:libhybris
  41. [41]
    [PDF] Release v2.17.2 Canonical Group Ltd. - Mir documentation
    Sep 10, 2024 · 3rd party (UBports) works with a libhybris container for Android drivers. ... There are even security concerns about placing windows to ...
  42. [42]
    Porting Mobian to New Devices
    Mar 7, 2023 · In addition, many kernels are device specific, which in turn creates a higher maintenance burden for every phone added. Adding the ...
  43. [43]
    Anbox
    ### Summary of Anbox
  44. [44]
    Jolla and Mer - LWN.net
    May 7, 2014 · Greaves said that the project(s) will be trying to make libhybris work for any device that has a CyanogenMod build. The rest of the phone is a " ...
  45. [45]
    Waydroid - ArchWiki
    Nov 2, 2025 · Waydroid is a container-based approach to boot a full Android system on a regular Linux system. Prerequisites CPU Requirements
  46. [46]
    GitHub - mer-hybris/libhybris
    Contribute to mer-hybris/libhybris development by creating an account on GitHub ... The ReadME Project. GitHub community articles. Repositories.
  47. [47]
    Releases · libhybris/libhybris
    **Summary of Releases for libhybris/libhybris:**
  48. [48]
    Commits · libhybris/libhybris
    **Summary of Commits from https://github.com/libhybris/libhybris/commits/master:**
  49. [49]
    Jolla C2 Halium Version - Devices - Sailfish OS Forum
    Oct 11, 2025 · Jolla uses a special compatibility layer (libhybris) that makes the Android-only driver usable in the classic Linux distro such as SailfishOS.
  50. [50]
    Libera Chat | A next-generation IRC network for FOSS projects ...
    Oct 25, 2025 · Providing a community platform for free and open-source software and peer directed projects. Connect by pointing your IRC client to irc.libera.chat:6697 (TLS)About Libera Chat · Sponsoring Libera Chat · Contributing to Libera Chat · FAQMissing: postmarketOS libhybris
  51. [51]
    UBports Forum: Home
    Discuss news updates from Ubuntu Touch and its related projects. about 8 hours ago Support Discuss and solve problems with other users.Recent Topics · Devices · Categories · Asus Zenfone Max Pro (M1)
  52. [52]
    Build hybris with Android 9 support - Merge requests - GitLab
    Oct 6, 2019 · This PR includes initial changes to make libhybris-based adaptation work for newer Android 8/9 devices. Tested to run Xorg on Fxtec pro1 and ...
  53. [53]
    libhybris - OpenEmbedded Layer Index
    libhybris 0.1.0+gitrX ; libhybris · 0.1.0+gitrX · Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems.
  54. [54]
    hybris/libhybris/APKBUILD ... - postmarketOS · GitLab
    Open in Web IDE . Quickly and easily edit multiple files in your project. Edit single file Edit this file only. File actions. Find file t