UBports Ubuntu Touch
UBports Ubuntu Touch

Ubuntu Touch: The History of an Open Mobile Operating System

Ubuntu Touch emerged as a response to the growing demand for an open, flexible mobile operating system capable of competing with dominant platforms like Android and iOS.

The idea was born at Canonical, the company behind the Ubuntu Linux distribution, which had long sought to expand its ecosystem beyond traditional desktops and servers.

Inspirations and Project Goals

The core vision was to create a unified operating system that could run seamlessly across devices—from smartphones and tablets to desktop computers. This concept, known as convergence, aimed to eliminate barriers between devices, allowing users to access the same interface, apps, and data regardless of hardware.

Unlike closed mobile systems, Ubuntu Touch was designed to be fully open-source, giving users complete control over their devices. Canonical also sought to diversify the mobile market, which in 2013 was dominated by Android (~80%) and iOS (~15%).

First Release and Early Development (2013–2014)

Announcement and Initial Steps

Ubuntu Touch was officially announced on January 2, 2013, by Mark Shuttleworth, Canonical’s founder. Originally codenamed “Ubuntu for Phones”, it was intended as an extension of Ubuntu for mobile devices. The first developer preview (Ubuntu Touch 1.0) was released on October 17, 2013, based on Ubuntu 13.10 (Saucy Salamander). Initial support covered the Samsung Galaxy Nexus and LG Nexus 4, popular devices among developers due to their openness and ease of modification.

Technical Foundations

Ubuntu Touch was not a typical Android-based mobile OS. Instead, it used:

  • A Linux kernel (with modifications from CyanogenMod for hardware support).
  • The Mir display server (later replaced by Wayland) for rendering the interface.
  • The Unity 8 desktop environment, designed for touchscreen devices.
  • Qt and QML libraries for mobile app development.
  • A dedicated Click package format, which isolated apps in a sandbox and protected the read-only system filesystem.

RTM Release and First Commercial Devices

In 2014, the RTM (Release To Manufacturing) version was released, marking its readiness for commercial use. Canonical partnered with hardware manufacturers, leading to the first devices pre-installed with Ubuntu Touch:

  • BQ Aquaris E4.5 Ubuntu Edition (February 2015) – The first commercial Ubuntu Touch smartphone, made by Spanish manufacturer BQ.
  • BQ Aquaris E5 Ubuntu Edition (June 2015) – The second BQ smartphone.
  • Meizu MX4 Ubuntu Edition (mid-2015).
  • BQ Aquaris M10 Ubuntu Edition (March 2016) – The first Ubuntu Touch tablet.

These devices were primarily sold in Europe and Asia, but their reach was limited due to a lack of carrier support and low brand awareness among average users.

Architecture and Key Features

Ubuntu Touch stood out with its innovative architecture and unique features, designed to appeal to both developers and everyday users.

Convergence: One System for All Devices

The most significant feature was convergence—the ability to use the same OS across smartphones, tablets, and desktops. With desktop mode, users could connect their phone to a monitor, keyboard, and mouse, turning it into a full-fledged computer. This was enabled by:

  • An adaptive interface – Unity 8 automatically adjusted to screen size and input methods (touch vs. mouse/keyboard).
  • Windowed interface support – In desktop mode, apps could run in windows, similar to traditional Ubuntu.
  • Full Linux access – Users had access to a terminal, file manager, and all Ubuntu tools.

Android App Support

To address the lack of popular apps, the UBports community (which later took over development) attempted to integrate Anbox (Android in a Box), a container that allowed running Android apps directly on the Linux kernel without full system emulation. However, Anbox had limitations:

  • Performance issues and lack of Google Play Services support.
  • Compatibility problems with many popular apps.
    In newer versions, Anbox was replaced by Waydroid, a more modern solution.

Openness and Privacy

Ubuntu Touch was a fully open system, meaning:

  • Open-source code – The entire system (except some hardware drivers) was available under the GPL license.
  • No user tracking – Unlike Android and iOS, Ubuntu Touch did not collect telemetry data or display ads.
  • Full user control – Users could modify the system, install custom ROMs, and manage app permissions.
  • Security – The system used process isolation mechanisms (e.g., AppArmor) and regular security updates.

User Interface

Ubuntu Touch introduced a gesture-based interface, eliminating the need for physical or on-screen navigation buttons. Key features included:

  • Edge-based gestures:
    • Left edge swipe – Opens the app launcher and shortcuts.
    • Right edge swipe – Switches between open apps and manages multitasking.
    • Top edge swipe – Opens notifications and quick settings (Indicators).
    • Bottom edge swipe – Reveals context menus and additional options within apps.
  • HUD (Head-Up Display) – A text-driven menu system allowing users to quickly search and execute complex commands within apps via typed input.
  • Scopes – Instead of traditional icons, the home screen consisted of dynamic dashboards that aggregated live content (e.g., news, social media, local music, weather) in a unified view.

Development Under Canonical (2014–2017)

Releases and Updates

After the commercial debut of the first devices in early 2015, Canonical adopted a regular over-the-air (OTA) update cycle. By the time the project was discontinued in 2017, Canonical had released OTA-1 to OTA-15. Key milestones included:

  • OTA-1 to OTA-3 (2015) – Initial stability fixes and battery life optimizations.
  • App ecosystem growth – Gradual expansion of core apps (e.g., Calendar, Contacts, a new web browser).
  • OTA-10 (2016) – Official tablet support (coinciding with the BQ Aquaris M10 launch) and key convergence features, such as windowed mode on external monitors.

Hardware Partnerships

Canonical’s official hardware partnerships were limited to BQ (Spain) and Meizu (China). Optimized versions of Ubuntu Touch were released only for select models from these brands.

Other devices gained support through community efforts:

  • Google Nexus reference devices – Models like the Nexus 4, Nexus 7, and Nexus 10 were officially used by Canonical as developer test platforms. The Nexus 5, though unsupported by Canonical, became a favorite among the developer community, which created a near-perfect port for it.
  • Fairphone 2 (2016) – This modular, eco-friendly smartphone received Ubuntu Touch solely through the UBports community, without Canonical’s involvement.

Challenges and Setbacks

Despite its ambitious goals, Ubuntu Touch faced several major challenges:

  1. Limited hardware support – Canonical struggled to secure partnerships with leading smartphone manufacturers, who preferred the safety and established ecosystem of Android.
  2. Lack of key apps – The Ubuntu Store suffered from a shortage of popular apps (e.g., WhatsApp, banking apps, games). Most available software consisted of simple web apps, and the independent OpenStore only emerged after Canonical’s withdrawal.
  3. Fierce competition – Android and iOS dominated the market (~98%), effectively eliminating not only Ubuntu Touch but also other alternatives like Windows Phone and Firefox OS.
  4. Technical issues – The Mir display server and Unity 8 were resource-intensive, leading to instability, occasional slowdowns, and high battery consumption.

UBports Takes Over (2017–Present)

End of Canonical’s Support

In April 2017, Canonical announced the end of active development for Ubuntu Touch, shifting its focus to cloud and IoT projects. This decision disappointed users and developers, but the community refused to let the project die.

The Rise of UBports

Founded in 2015 by a group of enthusiasts, UBports—a non-profit organization—took over full responsibility for Ubuntu Touch after Canonical’s withdrawal. Its primary goals were:

  1. Maintaining and developing Ubuntu Touch as a fully open system.
  2. Porting to new devices – Supporting newer smartphones and tablets.
  3. Improving stability and performance – Fixing bugs and optimizing battery life.
  4. Expanding the app ecosystem – Encouraging developers to create software for Ubuntu Touch.

Transition to a New System Base

In March 2023, UBports achieved a major milestone with the release of OTA-1 Focal, which migrated the system to Ubuntu 20.04 LTS (Focal Fossa), replacing the long-standing Ubuntu 16.04 base. This update brought:

  • Support for newer smartphones – An updated Halium layer enabled stable ports for devices originally released with Android 9 and newer.
  • Graphical modernization – A deep update to the Mir display server, which became a full-fledged Wayland compositor for mobile devices.
  • New hardware compatibility – Strengthened the system’s position on modern devices, such as PinePhone, Fairphone 3/4, and privacy-focused Volla Phone models. Older 64-bit devices (e.g., Sony Xperia X, OnePlus 3/3T) retained compatibility through backward architecture unification.

New Update Release Model

UBports reorganized its release model, adopting a structure based on Long-Term Support (LTS) releases and smaller maintenance updates:

  • Major releases (LTS base) – The system is ported to a new, stable architecture every few years, following Canonical’s official Ubuntu releases (e.g., the 20.04 transition in 2023 and the 24.04 stable line debut in late 2025).
  • Point updates (Maintenance) – Between major updates, the system receives regular, smaller bug-fix releases (e.g., 24.04-1.3 in May 2026). These are not tied to a strict schedule but are rolled out every few weeks or months after thorough stability testing.

App Ecosystem Development

UBports continues to expand its software ecosystem, focusing on security and process isolation:

  • OpenStore – The official app store for Ubuntu Touch, offering hundreds of apps (browsers, games, tools) packaged in the Click format, ensuring they cannot damage system files.
  • Popular messengers – Thanks to developer efforts, users have access to native, unofficial clients for services like Teleports (Telegram) and Axolotl (Signal).
  • Desktop apps (Convergence) – While Ubuntu Touch does not use Snap or Flatpak by default, advanced users can run traditional Linux programs (e.g., Firefox, LibreOffice) inside Libertine containers, primarily useful when the phone is connected to a monitor and keyboard.

Improved Hardware Compatibility

With community engagement and regular updates to the 24.04 LTS line, Ubuntu Touch now officially and stably supports over 30 selected device models, completely phasing out old 32-bit platforms. Supported devices include:

  • Reference and partner devices – Devices shipped with Ubuntu Touch pre-installed or with full technical support, such as:
    • Fairphone 3, 4, and 5 (eco-friendly modular smartphones).
    • Volla Phone 22, Quintus (privacy-focused devices).
    • PinePhone / PinePhone Pro (fully open-source smartphones).
  • Popular community ports – Older Android smartphones with high stability, including:
    • Google Pixel 3a.
    • OnePlus 3/3T.
    • Sony Xperia X.
  • Tablets – Open-source touch devices like PineTab / PineTab2 and Volla Tablet.

Collaboration with Other Projects

UBports actively supports the mobile Linux ecosystem, collaborating with other open-source initiatives:

  • postmarketOS – A mobile OS based on Alpine Linux. Both projects closely cooperate on Halium, which adapts Android hardware drivers for Linux distributions, making it easier to port systems to new smartphones.
  • Plasma Mobile – The mobile version of KDE’s environment, developed in cooperation with UBports to unify graphic server protocols (Mir/Wayland). This allows mutual testing of Plasma Mobile and Lomiri (formerly Unity 8) interfaces across different system bases.
  • Waydroid – A modern container project that replaced the abandoned Anbox. UBports collaborates with Waydroid’s developers to enable smooth and efficient Android app execution within an isolated environment on Ubuntu Touch.

Current State of Ubuntu Touch (May 2026)

Latest Version and Support

As of May 2026, the latest stable version is 24.04-1.3, released in the same month. The system is actively developed by the UBports community, with future updates planned according to the new release model.

Impact on the Mobile Market

Ubuntu Touch has had a significant influence on the development of alternative mobile systems, proving that:

  • Linux can be a viable mobile OS – Despite technical challenges, the project demonstrated that mobile Linux is a real alternative.
  • Convergence is possible – The idea of a single OS across devices was later adopted by Microsoft (Continuum) and Samsung (DeX).
  • Community can sustain a system without corporate backing – UBports shows that open-source projects can survive through user engagement.

Future of Ubuntu Touch

The UBports Foundation focuses its plans on stabilizing the newly released Ubuntu 24.04 LTS base and facilitating system adaptation on modern hardware:

  1. Lomiri environment development – Further modernizing the Lomiri interface (formerly Unity 8), fully integrating it with the latest Wayland protocols, and making it easier to run on other Linux distributions (e.g., Debian, Fedora).
  2. Waydroid improvements – Intensive work on performance, graphical acceleration, and notification integration for Android apps running in containers.
  3. Battery optimization – Continuous improvements to background process sleep mechanisms to extend battery life on modern multi-core smartphones.
  4. Strengthening partnerships – Expanding the range of factory-supported devices in collaboration with key hardware partners: Volla, Fairphone, and Pine64.
  5. Easier porting process – Developing the Halium tool and UBports Installer to reduce the time needed to port Ubuntu Touch to the latest smartphones debuting with Android 13 and newer.

Challenges

Despite progress, Ubuntu Touch still faces several challenges:

  1. Limited hardware support – Most smartphone manufacturers are not interested in collaborating with UBports.
  2. Smaller app ecosystem – The software ecosystem is less attractive to average users.
  3. Competition from Android and iOS – Their dominance (~98% market share) makes it difficult to gain a wider audience.
  4. Lack of carrier support – Most mobile operators do not support Ubuntu Touch (e.g., no VoLTE/5G certification).

Possible Development Scenarios

  1. Optimistic – Ubuntu Touch gains a niche but stable market position, especially among open-source enthusiasts and privacy-conscious users. Collaboration with open-source hardware manufacturers (Pine64, Fairphone) allows for an expanded list of supported devices.
  2. Realistic – The system remains a hobbyist project, developed primarily by the community without broad commercial support. Users mainly run it on secondary devices (e.g., old smartphones).
  3. Pessimistic – Lack of progress in hardware support and app ecosystem leads to a gradual decline in interest. UBports may shift focus to other projects (e.g., postmarketOS).

Conclusion

Ubuntu Touch is a unique project that broke barriers in the world of mobile operating systems. It began as an ambitious initiative by Canonical to create an open, convergent system capable of competing with Android and iOS. While it never achieved mass popularity, it revolutionized the perception of mobile Linux and proved that alternatives to closed systems are possible.

After Canonical’s withdrawal in 2017, the project was taken over by the UBports community, which continues its development to this day. Thanks to the dedication of volunteers, Ubuntu Touch has survived and evolved, gaining support for new devices, improved stability, and new features.

As of May 2026, it remains a stable, albeit niche alternative to Android and iOS, primarily targeting open-source enthusiasts, developers, and privacy-conscious users. Its future depends on community activity, hardware manufacturer support, and the ability to compete with dominant platforms.


Discover more from FOSS2go

Subscribe to get the latest posts sent to your email.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *