Maemo Leste Wiki - User contributions [en]

Wishlist

2021-01-11T21:33:49Z

Derby: /* Applications */

If there is an application from Maemo Fremantle or even from a standard Linux distribution that you wish to see in Maemo Leste, please add it on this page.

We do not promise that we can port it right away, but we will try, as far as our resources allow.

To make our this easy for our developers, please include links to descriptions of the application, sources, and other useful information.

== Applications ==

{| class="wikitable"http://maemo.org/packages/view/orecchiette/
! Package name
! Done
! Reason
! User
! URL
! Notes
|-
| osso-notes || Yes (quicknote) || a notes application || [[User:Wizzup]] || http://maemo.org/packages/view/osso-notes/ ; http://wiki.maemo.org/Quicknote || Quicknote currently packaged. Usage notes - http://wiki.maemo.org/Quicknote
|-
| pinball || No || fun || Sicelo || https://packages.debian.org/buster/pinball or http://linball.sourceforge.net/|| any implementation.
|-
| scummvm || https://github.com/maemo-leste/bugtracker/issues/269 || fun || [[User:Wizzup]] || http://maemo.org/packages/view/scummvm/ || latest version please
|-
| [[Games/Brainparty|brainparty]] || Yes || for fun || [[User:Wizzup]] || http://maemo.org/downloads/product/Maemo5/brainparty/ ||
|-
| Picodrive || No || Sega emulator, fun || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/p/picodrive/ || http://maemo.org/packages/view/orecchiette/(has also Psycho Pinball installable)
|-
| Internet radio: mSoma || No || media || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/m/msoma/ ||http://maemo.org/packages/view/orecchiette/
|-
| Cutetube2 || No || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cutetube2/0.5.2/ || could change cutetube into a youtube-dl frontend
|-
| PDF reader || Yes || reading || [[User:Wizzup]] || https://github.com/community-ssu/osso-pdf-viewer/ || libhildonfm has bugs regarding file opening dialogs that need to be fixed
|-
| Calendar app || No || orga || [[User:Maemish]] || https://wiki.maemo.org/Qalendar || Probably Qalendar and not fremantle closed. Requires Qt5 port.
|-
| Alarm clock || ? || orga || [[User:Maemish]] || ? || alarmd and alarm UI already works, there might be a FOSS UI
|-
| Word processor / Abiword || Might already be in debian || orga || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/abiword/2.8.1-2maemo4/
|-
| Simple Brightness Applet || Yes, see https://github.com/maemo-leste/simple-brightness-applet || ? || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/simple-brightness-applet/1.1-1maemo0/ || This is not latest build from extras-devel
|-
|Status bar: Load Applet || No || CPU and RAM usage, screenshot and screen record. || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/load-applet/0.4.6-5/ || Needs to be ported to gst1.0
|-
| Camera App: BlessN900|| No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_non-free_armel/blessn900/0.49-3/ ||
|-
| Image viewer/editor || Yes || || [[User:Maemish]] || https://github.com/maemo-leste-extras/mihphoto ||
|-
| Mail with imap support || No || || [[User:Maemish]] || ||
|-
| RSS Feed Reader: Who knows a good one? || No || Reading/Media || [[User:Maemish]] || ||
|-
| Browser: Dooble || No || internet || [[User:Maemish]] || New homepage: https://textbrowser.github.io/dooble/ Not sure if the old package helps porting http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/dooble/1.52-maemo1/ ||
|-
| OpenMediaPlayer || ? || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/openmediaplayer/20161108-1/ Homepage: http://gitorious.org/qt-mediaplayer ||
|-
| SMPlayer || No || media || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/smplayer/0.6.9-1maemo7/ Homepage: http://smplayer.sourceforge.net ||
|-
| Unzip addon for filemanager || No || utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/diablo_extras-devel_free_armel/unzip-fm/0.1.3-3/ ||
|-
| D-Theme SimpleBlackGreen || No || fashion || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle/free/d/d-theme-simple-blackgreen/ ||
|-
| Bootscreen: Don't Panic! || No || fun (but neccessity) || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/dontpanic/1.0/ ||
|-
| MMS: fMMS || No || media || [[User:Maemish]] || https://garage.maemo.org/projects/fmms ||
|-
| Homescreen Dockbar Widget|| No || fashion/utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/homescreen-dockbar/0.0.6/ ||
|-
| Hotspot: MobileHotspot || No. || utility/accessory || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/mobilehotspot/0.3.5/ || Either this or something else. This has only wep encryption which should be changed.
|-
| Firewall || No || || [[User:Maemish]] || || Something with easy configuration.
|-
| Swappolube || No || || [[User:Maemish]] || http://repository.maemo.org/extras/pool/fremantle-1.3/free/s/swappolube/ ||
|-
|bnf- Battery information at glance || No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/bnf/1.2/ ||
|-
| cardioalert || No || || [[User:Maemish]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cardioalert/0.1/ ||
|-
| gnumeric || No || Office || [[User:ric9k]] || http://maemo.org/packages/view/gnumeric/ ||
|-|-
| hamsterfiler || No || utilities/files || [[User:ric9k]] || http://maemo.org/packages/view/hamsterfiler/ ||
|-|-
| alarmed (or cron?) || No || utilities || [[User:ric9k]] || http://maemo.org/packages/view/alarmed/ ||
|-|-
| user friendly tracker || No || utilities? || [[User:ric9k]] || n/a :-) ||
|-|-
| Maps (offline) || No || Navigation || [[User:Sicelo]] || || Ideally something like https://f-droid.org/en/packages/com.github.axet.maps/ from Android, but Modrana, https://github.com/M4rtinK/modrana may be easier as a start. [FoxtrotGPS https://www.foxtrotgps.org] might be the easiest to adapt, it is already packaged in Devuan.
|-
| Orecchiette || No || calls recording || [[User:capitannemo]] || http://maemo.org/packages/view/orecchiette/ ||
|-
| Panucci || No || audiobook || [[User:capitannemo]] || http://maemo.org/packages/view/panucci/ ||
|-
| gPodder || No || podcast || [[User:capitannemo]] || http://maemo.org/packages/view/gpodder/ ||
|-
| Symfonie || No || directory-based audioplayer || [[User:capitannemo]] || http://maemo.org/packages/view/symfonie/ ||
|-
| osso-clock || No || clock and alarms application || pavel || ||
|-
| freecell4maemo || No || freecell game || pavel || ||
|-
| [http://festvox.org/index.html CMU Flite] || ? || Accessibility (TTS) || [[User:Buffer|Buffer]] ([[User talk:Buffer|talk]]) 21:48, 2 March 2020 (UTC) || https://github.com/festvox/flite ||
|-
| Cooktimer || No || feature-rich timers || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/cooktimer/0.0.4-24/ || latest from extras-devel
|-
| OpenSSH Status Widget || No || openSSH monitor and config. || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/openssh-status-widget/2.2-12/ ||
|-
| Recaller || No || record with one tap || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras_free_armel/recaller/2.1.0-5/ ||
|-
| NecroPlayer2 || No || directory-based audioplayer, easy playlist edit, multiple directories, very useful with recaller widget || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/necroplayer2/0.2.3/ ||
|-
| Simpler Brightness Applet || No || simple brightness applet with single tap for backlight and long tap for settings || [[User:Rasmarc]] || http://maemo.org/packages/package_instance/view/fremantle_extras-testing_free_armel/simpler-brightness-applet/1.0/ ||
|)
|-
| telepathy-signal || No || The best open source alternative to WhatsApp should be ready for use with Maemo Leste || [[User:Derby]] || https://github.com/signalapp/Signal-Desktop ; https://github.com/AsamK/signal-cli || This is a suggestion to create a Telepathy connection manager for Signal. Although the Signal [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842943 Desktop] and [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926807 CLI] can be installed, they are not yet available in Debian. In any case, it would be great to have a Telepathy connection manager for Signal to provide seamless integration with Maemo.

Leste FAQ

2020-06-06T17:43:49Z

Derby: /* How about other popular non-Android mobile Linux distributions? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices. It also uses a '''[[#What_is_mainline_Linux.3F|mainline Linux]]''' kernel.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of mainline Linux. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs would be required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], which favours device compatibility and ease of device porting, at the expense of software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve. As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-06-06T17:03:05Z

Derby: /* How does Maemo Leste compare with PureOS? */ Removing link to viedo as it is no longer available

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices. It also uses a '''[[#What_is_mainline_Linux.3F|mainline Linux]]''' kernel.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of mainline Linux. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs would be required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve. As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-06-06T17:01:31Z

Derby: /* Is Maemo Leste completely free? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices. It also uses a '''[[#What_is_mainline_Linux.3F|mainline Linux]]''' kernel.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of mainline Linux. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs would be required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve. As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

X86

2020-06-05T02:23:51Z

Derby:

{{DISPLAYTITLE:x86}}
=== Running on x86/x86_64 ===

The contents of the <code>qcow2</code> file can be extracted and copied into hard drives for bare metal BIOS/Legacy CSM booting.

To extract the contents of the <code>qcow2</code> file, decompress it first and convert it into <code>raw</code> format.

$ xz -d maemo-leste-1.0-amd64-virtual-20180425.qcow2.xz
$ qemu-img convert -f qcow2 -O raw maemo-leste-1.0-amd64-virtual-20180425.qcow2 maemo-leste-1.0-amd64-virtual-20180425.raw

The raw image that it yields, can then be setup as a loopback device, and its partitions mounted.

# losetup --partscan -f maemo-leste-1.0-amd64-virtual-20180425.raw
# mkdir /mnt/maemo-virt
# mount /dev/loop0p1 /mnt/maemo-virt

Setup one <code>Linux</code> partition on the device to be used for booting, format it with a GRUB-compatible filesystem (<i>ext4</i>, for example), then mount it as well.

# cfdisk /dev/sdb
# ...
# mkfs.ext4 /dev/sdb1
# mkdir /mnt/maemo-bare
# mount /dev/sdb1 /mnt/maemo-bare

Change directory to the loop partition, the copy over its contents into the bare metal partition.

# cd /mnt/maemo-virt
# rsync -aAHXv * /mnt/maemo-bare

Once finished copying, bind mount special filesystems into the bare metal Maemo partition, then change root.

# mount --bind /dev /mnt/maemo-bare/dev
# mount --bind /proc /mnt/maemo-bare/proc
# mount --bind /sys /mnt/maemo-bare/sys
# chroot /mnt/maemo-bare /bin/bash

Load the new root's shell profile, install GRUB to the bare metal boot device (<i>/dev/sdb</i>, in this example), then regenerate the GRUB configuration file.

# . /etc/profile
# grub-install /dev/sdb
# grub-mkconfig -o /boot/grub/grub.cfg

After that, you may exit the chroot environment (Ctrl+D), unmount all the filesystems, then reboot the system into your new bare metal Maemo Leste installation.

# umount /mnt/maemo-virt
# umount -AR /mnt/maemo-bare
# reboot

Virtual Machine

2020-05-28T00:08:10Z

Derby: /* Installation */

{{Stub}}

{{Infobox Device
|image=
|manufacturer=Generic
|codename=
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

Generic virtual machine target. This is particularly useful when doing development and testing.

== Installation ==

https://maedevu.maemo.org/images/virtual-machines/

There are three different types of images: VirtualBox (.box), QEMU (.qcow2, .vdi) and Vagrant. The VirtualBox image may be converted to a VMware VMDK image which has been reported to perform better and have good hardware acceleration.
Converting the qcow2 image to raw allows it to be used on real hardware.

=== VirtualBox ===

Download latest .vdi.xz image, unpack it with "xz -d" command.
Create new Virtual Machine, select "Debian (64-bit)" and 1024MB RAM. Use the downloaded file as virtual hard disk.
You are done!

=== QEMU ===

In general something like
qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024
should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].

To set up a port forward for SSH, add:
-nic user,hostfwd=tcp:127.0.0.1:7722-:22
And then log in like this (password: <code>toor</code>):
ssh root@localhost -p 7722

If the mouse pointer is grabbed and no cursor shows, you can add
-usb -device usb-tablet
to the command line

If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:
sudo qemu-system-x86_64 -hda maemo-leste-1.0-amd64-virtual-20200324.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024 \
-nic user,hostfwd=tcp:127.0.0.1:7722-:22 \
-usb -device usb-ehci,id=ehci \
-device usb-host,bus=ehci.0,vendorid=0x0bdb,productid=0x193e

Or you can make a udev rule for your device. For example, with a Lenovo Ericsson N5321 gw you can create "/etc/udev/rules.d/45-n5321.rules" with this in it:
# Lenovo Ericsson N5321 gw simple udev rule
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bdb", ATTRS{idProduct}=="193e", \
MODE:="0666"

And then activate it by running these two commands as root:
# udevadm control --reload-rules
# udevadm trigger

Now you can run QEMU without the need for sudo!

=== virt-manager ===

See [https://github.com/maemo-leste/bugtracker/issues/291#issuecomment-575952497 here].

== Initial configuration ==

On the first run you may want to generate ssh host keys and set the timezone. To do so open the "X Terminal" application and run:
sudo su -
dpkg-reconfigure openssh-server
dpkg-reconfigure tzdata

Make the system up-to-date:
apt update
apt upgrade
apt install linux-image-amd64
reboot

To get networking to work (at least in virtualbox), launch a shell and do
sudo ifconfig eth0 up
sudo dhclient eth0

== Connectivity ==

If you have a modem exposed to QEMU, you still need to do some steps manually to get connectivity.

First off you need to add the development APT repository to your APT sources:
# echo 'deb https://maedevu.maemo.org/leste beowulf-devel main contrib non-free' >> /etc/apt/sources.list

Now update and upgrade:
# apt update && apt upgrade

Then you can install these things:
# apt install ofono libicd-network-ofono connui-iapsettings-gprs connui-statusbar-cellular connui-home-cellular connui-cellular-settings connui-conndlgs-cellular

We need mdbus2 to manipulate oFono:
# wget http://ftp.nl.debian.org/debian/pool/main/m/mdbus/mdbus2_2.3.3-2_amd64.deb
# dpkg -i mdbus2_2.3.3-2_amd64.deb

Then we can check if oFono finds our modem:
# mdbus2 -s org.ofono
/
/bluetooth
/bluetooth/profile
/bluetooth/profile/dun_gw
/bluetooth/profile/hfp_ag
/bluetooth/profile/hfp_hf
/mbm_0

Then can check our mbm_0 modem:
# mdbus2 -s org.ofono /mbm_0
[METHOD] org.freedesktop.DBus.Introspectable.Introspect() -> (s:xml)
[METHOD] org.ofono.Modem.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.Modem.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.Modem.PropertyChanged(s:name, v:value)

# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.GetProperties
({'Online': <false>, 'Powered': <false>, 'Lockdown': <false>, 'Emergency': <false>, 'SystemPath': <'/sys/devices/pci0000:00/0000:00:04.0/usb1/1-1'>, 'Interfaces': <@as []>, 'Features': <@as []>, 'Type': <'hardware'>},)

Power on the modem:
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.SetProperty Powered true
()
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.GetProperties
({'Online': <false>, 'Powered': <true>, 'Lockdown': <false>, 'Emergency': <false>, 'Manufacturer': <'Lenovo'>, 'Model': <'N5321 gw'>, 'Revision': <'R3C11'>, 'Serial': <'xxxxxxxxxxxx'>, 'SystemPath': <'/sys/devices/pci0000:00/0000:00:04.0/usb1/1-1'>, 'Interfaces': <['org.ofono.SimManager']>, 'Features': <['sim']>, 'Type': <'hardware'>},)

Check if we need to enter a pin:
# mdbus2 -s org.ofono /mbm_0 org.ofono.SimManager.GetProperties
({'Present': <true>, 'CardIdentifier': <'xxxxxx'>, 'FixedDialing': <false>, 'BarredDialing': <false>, 'SubscriberNumbers': <@as []>, 'LockedPins': <['pin']>, 'PreferredLanguages': <['de', 'en', 'fr']>, 'PinRequired': <'pin'>, 'Retries': <{'pin': byte 0x03, 'pin2': 0x03, 'puk': 0x0a, 'puk2': 0x0a}>, 'CardSlotCount': <uint32 1>, 'ActiveCardSlot': <uint32 1>},)

If PinRequired is 'pin' we need to enter a pin to unlock the sim:
# mdbus2 -s org.ofono /mbm_0 org.ofono.SimManager.EnterPin pin 1234
()

Then we can bring the modem online:
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.SetProperty Online true
()

If we now redo the first mdbus2 command on /mbm_0:
# mdbus2 -s org.ofono /mbm_0
[METHOD] org.freedesktop.DBus.Introspectable.Introspect() -> (s:xml)
[METHOD] org.ofono.Modem.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.Modem.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.Modem.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.SimManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.SimManager.ChangePin(s:type, s:oldpin, s:newpin) -> ()
[METHOD] org.ofono.SimManager.EnterPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.ResetPin(s:type, s:puk, s:newpin) -> ()
[METHOD] org.ofono.SimManager.LockPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.UnlockPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.GetIcon(y:id) -> (ay:icon)
[SIGNAL] org.ofono.SimManager.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.AllowedAccessPoints.GetAllowedAccessPoints() -> (as:apnlist)
[METHOD] org.ofono.SimAuthentication.GetApplications() -> (a{oa{sv}}:applications)
[METHOD] org.ofono.SimAuthentication.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimToolkit.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimToolkit.SelectItem(y:item, o:agent) -> ()
[METHOD] org.ofono.SimToolkit.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.SimToolkit.UnregisterAgent(o:path) -> ()
[SIGNAL] org.ofono.SimToolkit.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.RadioSettings.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.RadioSettings.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.RadioSettings.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.MessageManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.MessageManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.MessageManager.SendMessage(s:to, s:text) -> (o:path)
[METHOD] org.ofono.MessageManager.GetMessages() -> (a(oa{sv}):messages)
[SIGNAL] org.ofono.MessageManager.PropertyChanged(s:name, v:value)
[SIGNAL] org.ofono.MessageManager.IncomingMessage(s:message, a{sv}:info)
[SIGNAL] org.ofono.MessageManager.ImmediateMessage(s:message, a{sv}:info)
[SIGNAL] org.ofono.MessageManager.MessageAdded(o:path, a{sv}:properties)
[SIGNAL] org.ofono.MessageManager.MessageRemoved(o:path)
[METHOD] org.ofono.PushNotification.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.PushNotification.UnregisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.UnregisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.SendBusinessCard(s:to, ay:card) -> (o:path)
[METHOD] org.ofono.SmartMessaging.SendAppointment(s:to, ay:appointment) -> (o:path)
[METHOD] org.ofono.LocationReporting.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.LocationReporting.Request() -> (h:fd)
[METHOD] org.ofono.LocationReporting.Release() -> ()
[SIGNAL] org.ofono.LocationReporting.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.SupplementaryServices.Initiate(s:command) -> (s:result_name, v:value)
[METHOD] org.ofono.SupplementaryServices.Respond(s:reply) -> (s:result)
[METHOD] org.ofono.SupplementaryServices.Cancel() -> ()
[METHOD] org.ofono.SupplementaryServices.GetProperties() -> (a{sv}:properties)
[SIGNAL] org.ofono.SupplementaryServices.NotificationReceived(s:message)
[SIGNAL] org.ofono.SupplementaryServices.RequestReceived(s:message)
[SIGNAL] org.ofono.SupplementaryServices.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.CellBroadcast.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.CellBroadcast.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.CellBroadcast.PropertyChanged(s:property, v:value)
[SIGNAL] org.ofono.CellBroadcast.IncomingBroadcast(s:message, q:channel)
[SIGNAL] org.ofono.CellBroadcast.EmergencyBroadcast(s:message, a{sv}:dict)
[METHOD] org.ofono.ConnectionManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.ConnectionManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.ConnectionManager.AddContext(s:type) -> (o:path)
[METHOD] org.ofono.ConnectionManager.RemoveContext(o:path) -> ()
[METHOD] org.ofono.ConnectionManager.DeactivateAll() -> ()
[METHOD] org.ofono.ConnectionManager.GetContexts() -> (a(oa{sv}):contexts_with_properties)
[METHOD] org.ofono.ConnectionManager.ResetContexts() -> ()
[SIGNAL] org.ofono.ConnectionManager.PropertyChanged(s:name, v:value)
[SIGNAL] org.ofono.ConnectionManager.ContextAdded(o:path, a{sv}:properties)
[SIGNAL] org.ofono.ConnectionManager.ContextRemoved(o:path)
[METHOD] org.ofono.NetworkRegistration.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.NetworkRegistration.Register() -> ()
[METHOD] org.ofono.NetworkRegistration.GetOperators() -> (a(oa{sv}):operators_with_properties)
[METHOD] org.ofono.NetworkRegistration.Scan() -> (a(oa{sv}):operators_with_properties)
[SIGNAL] org.ofono.NetworkRegistration.PropertyChanged(s:name, v:value)

[[Category:Device]]

Leste FAQ

2020-05-22T19:35:37Z

Derby: State that Maemo Leste uses mainline Linux in the description under "What is Maemo Leste?"

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices. It also uses a '''[[#What_is_mainline_Linux.3F|mainline Linux]]''' kernel.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of mainline Linux. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve. As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-20T02:44:22Z

Derby: /* What devices does Maemo Leste work on? */ Fix punctuation

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve. As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-19T13:20:13Z

Derby: /* Does Maemo Leste run with pure mainline Linux? */ Improve wording as "running" is already possible.

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to switch to using a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-17T13:35:21Z

Derby: /* How about other popular non-Android mobile Linux distributions? */ Fix broken link

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Talks

2020-02-03T19:23:13Z

Derby: /* FOSDEM 2020 - Freedom Main Track - 2nd February 2020 */ FOSDEM 2020 videos are now up

== FOSDEM 2020 - Freedom Main Track - 2nd February 2020 ==

'''Regaining control of your smartphone with postmarketOS and Maemo Leste - Status of Linux on the smartphone''' - ''Merlijn Wajer (Wizzup), Bart Ribbers (PureTryOut)''

[https://fosdem.org/2020/schedule/event/smartphones/ Event info]

Video: [https://video.fosdem.org/2020/Janson/smartphones.webm WebM/VP9], [https://video.fosdem.org/2020/Janson/smartphones.mp4 MP4]

== OpenFest 2019 - 2nd November 2019==

'''GNU/Linux: coming to a phone near you''' - ''Merlijn Wajer (Wizzup)''

[https://www.openfest.org/2019/en/full-schedule/#lecture-471 Event info]

Video: [https://www.youtube.com/watch?v=heQmjP5tQn0 YouTube] (via [https://invidio.us/watch?v=heQmjP5tQn0 Invidious])

== OpenAlt 2019 - 2nd November 2019 ==

'''Debian v kapse''' - ''Pavel Machek''

[https://openalt.cz/2019/program_detail.php#event_32 Event info]

== Devuan Conference #1: “THE POWER OF CHOICE” - 7th April 2019 ==

'''Maemo Leste: Mobile Hacker OS''' - ''Ivan Jelincic (parazyd)''

Video: [https://www.youtube.com/watch?v=_ULy7jBnXdo&t=12304 YouTube] (via [https://invidio.us/watch?v=_ULy7jBnXdo&t=12304 Invidious])

== FOSDEM 2019 - Lightning Talk - 2nd February 2019 ==

'''Maemo Leste - A Debian/Devuan based mobile hacker OS''' - ''Merlijn Wajer (Wizzup)''

[https://archive.fosdem.org/2019/schedule/event/maemo_leste_mobile Event info]

Video: [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.webm WebM/VP9], [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.mp4 MP4]

[https://maedevu.maemo.org/media/fosdem-2019-maemo-leste.pdf Slides]

== OpenFest 2018 - 4th November 2018 ==

'''Maemo Leste''' - ''Merlijn Wajer (Wizzup), Ivan Jelincic (parazyd)''

[https://www.openfest.org/2018/en/full-schedule/#lecture-360 Event info]

Video: [https://maedevu.maemo.org/media/openfest-2018-maemo-leste-wizzup-parazyd.webm WebM]

[https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf Slides]

== OpenAlt 2018 - 3rd November 2018 ==

'''Maemo Leste - Debian do kapsy''' - ''Pavel Machek''

[https://openalt.cz/2018/program_detail.php#event_14 Event info]

Video: [https://www.youtube.com/watch?v=9C0j4M_AQ2I YouTube] (via [https://invidio.us/watch?v=9C0j4M_AQ2I Invidious])

[https://openalt.cz/2018/avatars/d96c9c95348879e4e6e2c27f665ca2b3-nokia_n900.pdf Slides]

Leste FAQ

2020-02-02T16:01:38Z

Derby: /* Does Maemo Leste use Halium? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Talks

2020-02-02T15:01:52Z

Derby: /* FOSDEM 2020 - Freedom Main Track - 2nd February 2020 */ Live stream is over

== FOSDEM 2020 - Freedom Main Track - 2nd February 2020 ==

'''Regaining control of your smartphone with postmarketOS and Maemo Leste - Status of Linux on the smartphone''' - ''Merlijn Wajer (Wizzup), Bart Ribbers (PureTryOut)''

[https://fosdem.org/2020/schedule/event/smartphones/ Event info]

Video: Coming soon

== OpenFest 2019 - 2nd November 2019==

'''GNU/Linux: coming to a phone near you''' - ''Merlijn Wajer (Wizzup)''

[https://www.openfest.org/2019/en/full-schedule/#lecture-471 Event info]

Video: [https://www.youtube.com/watch?v=heQmjP5tQn0 YouTube] (via [https://invidio.us/watch?v=heQmjP5tQn0 Invidious])

== OpenAlt 2019 - 2nd November 2019 ==

'''Debian v kapse''' - ''Pavel Machek''

[https://openalt.cz/2019/program_detail.php#event_32 Event info]

== Devuan Conference #1: “THE POWER OF CHOICE” - 7th April 2019 ==

'''Maemo Leste: Mobile Hacker OS''' - ''Ivan Jelincic (parazyd)''

Video: [https://www.youtube.com/watch?v=_ULy7jBnXdo&t=12304 YouTube] (via [https://invidio.us/watch?v=_ULy7jBnXdo&t=12304 Invidious])

== FOSDEM 2019 - Lightning Talk - 2nd February 2019 ==

'''Maemo Leste - A Debian/Devuan based mobile hacker OS''' - ''Merlijn Wajer (Wizzup)''

[https://archive.fosdem.org/2019/schedule/event/maemo_leste_mobile Event info]

Video: [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.webm WebM/VP9], [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.mp4 MP4]

[https://maedevu.maemo.org/media/fosdem-2019-maemo-leste.pdf Slides]

== OpenFest 2018 - 4th November 2018 ==

'''Maemo Leste''' - ''Merlijn Wajer (Wizzup), Ivan Jelincic (parazyd)''

[https://www.openfest.org/2018/en/full-schedule/#lecture-360 Event info]

Video: [https://maedevu.maemo.org/media/openfest-2018-maemo-leste-wizzup-parazyd.webm WebM]

[https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf Slides]

== OpenAlt 2018 - 3rd November 2018 ==

'''Maemo Leste - Debian do kapsy''' - ''Pavel Machek''

[https://openalt.cz/2018/program_detail.php#event_14 Event info]

Video: [https://www.youtube.com/watch?v=9C0j4M_AQ2I YouTube] (via [https://invidio.us/watch?v=9C0j4M_AQ2I Invidious])

[https://openalt.cz/2018/avatars/d96c9c95348879e4e6e2c27f665ca2b3-nokia_n900.pdf Slides]

Leste FAQ

2020-02-02T14:55:00Z

Derby: /* What is Maemo Leste? */ Add comment on available upstream packages

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages. This also gives us the benefit of having access to over 20,000 packages from upstream, immediately available for installation in Maemo Leste.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T14:45:36Z

Derby: /* Is Maemo Leste completely free? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed user space drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T06:19:18Z

Derby: Add "Can I use Maemo Leste with musl?" question

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== musl libc kicks arse. Can I use Maemo Leste with musl? ===

We love musl libc too. musl provides a lean, efficient and standards-compliant implementation of libc. What's not to like? Well unfortunately a lot of software built for Linux is glibc-dependent and is not standards-compliant. Rebuilding this software with musl can result in unexpected runtime behaviour or bugs. musl would be an extra hurdle that we don't really need right now. Still, it would be nice to one day see Maemo Leste rebuilt against musl and might make for an interesting future project, but until then, make sure you check out postmarketOS.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T05:29:57Z

Derby: /* What is Maemo Leste? */ Add paragragh explaining the benefits of building on top of Devuan compared to Fremantle

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Building on top an actively developed Linux distribution makes Maemo Leste maintenance sustainable. Fremantle was built on top of Debian packages forked from several versions of Debian, leaving the onus on Nokia to maintain every single package. Leste however, utilises Devuan's package repositories meaning that much of the heavy lifting is already done by upstream; we only have to manage and maintain a limited set of packages.

All in all, Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T04:28:49Z

Derby: /* Does Maemo Leste run with pure mainline Linux? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be, thus the additional patches help to achieve this. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T03:50:42Z

Derby: Paragraph consistency

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===

No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===

Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===

The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===

Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===

The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===

Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===

postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===

Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===

The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===

Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===

Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T03:47:52Z

Derby: Add "Is Maemo Leste completely free?" question

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===
The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== Is Maemo Leste completely free? ===
Unfortunately not. There is still no smartphone available that is fully functional without the use of [https://en.wikipedia.org/wiki/Proprietary_device_driver binary blobs]. Our primary supported devices currently require closed firmware to be able to use Wi-Fi and Bluetooth, and the TI OMAP-based devices have integrated PowerVR video hardware which require closed drivers for video acceleration. It's an unfortunate state of affairs, however progress is being made, and the PinePhone is a great example of this as it can have video acceleration with the Lima driver which is 100% free software.

Our current goal is to provide full functionality for our supported devices, however there are plans to additionally provide a blob-free, libre version of Maemo Leste with missing functionality where blobs are required.

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T03:00:55Z

Derby: Add "Does Maemo Leste run with pure mainline Linux?" question

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== Does Maemo Leste run with pure mainline Linux? ===
The primary devices that we support can run with a pure mainline Linux kernel, however right now our images use mainline plus a few patches. As we are still in the early phases of development, our current priority is to ensure that our supported devices are as fully functional as they can possibly be. We have already upstreamed some of our patches and our goal is to upstream the remaining ones to be able to run a 100% mainline kernel on our devices.

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T02:07:06Z

Derby: /* What is mainline Linux? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long-term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T02:05:41Z

Derby: /* What's wrong with Android (vendor) kernels? */ Improve wording

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained by vendors with almost no effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T02:03:08Z

Derby: /* Does Maemo Leste use Halium? */ Fix link

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-02-02T02:01:22Z

Derby: /* Why do we need another mobile operating system? */ Improve answer

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

Today's smartphone industry is dominated by the duopoly of Apple and Google with their iOS and Android operating systems. This leaves those of us who value information privacy and software freedoms with virtually no options when it comes to choosing a smartphone. Some pretenders have tried to change this but have ultimately [[#How_about_other_popular_non-Android_mobile_Linux_distributions.3F|fallen short in some areas]]. Maemo Leste aims to put an end to this dire situation. We provide a ''true'' GNU/Linux experience which evolves along with the base Linux distribution from which it is built on top of. Maemo Leste is the only multi-device mobile Linux distribution that prioritises the use of [[#What_is_mainline_Linux.3F|mainline Linux]]. We hope that Maemo Leste will help to raise awareness of the [[#Why_is_it_important_to_run_mainline_Linux.3F|importance of running mainline Linux]] which may eventually lead to increased consumer demand for devices that are compatible with mainline Linux, leading to improved options when choosing a smartphone.

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Main Page

2020-02-01T16:30:47Z

Derby: Give the FAQ a heading

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

= Frequently Asked Questions =

See [[Leste_FAQ|FAQ]]

= Supported Devices =

See [[:Category:Device]]

= Development =

See [[Development]]

= Roadmap =

== Project milestones ==
https://github.com/maemo-leste/bugtracker/milestones

== Wishlist ==

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

= Talks =

See [[Talks]]

= Links =
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Main Page

2020-02-01T16:28:08Z

Derby: Add link to new Talks page

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

Also see our [[Leste_FAQ|FAQ]].

= Supported Devices =

See [[:Category:Device]]

= Development =

See [[Development]]

= Roadmap =

== Project milestones ==
https://github.com/maemo-leste/bugtracker/milestones

== Wishlist ==

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

= Talks =

See [[Talks]]

= Links =
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Talks

2020-02-01T16:25:43Z

Derby: Maemo Leste talks at various events

== FOSDEM 2020 - Freedom Main Track - 2nd February 2020 ==

'''Regaining control of your smartphone with postmarketOS and Maemo Leste - Status of Linux on the smartphone''' - ''Merlijn Wajer (Wizzup), Bart Ribbers (PureTryOut)''

[https://fosdem.org/2020/schedule/event/smartphones/ Event info]

Video: [https://live.fosdem.org/watch/janson Live stream at 15:00 CET]

== OpenFest 2019 - 2nd November 2019==

'''GNU/Linux: coming to a phone near you''' - ''Merlijn Wajer (Wizzup)''

[https://www.openfest.org/2019/en/full-schedule/#lecture-471 Event info]

Video: [https://www.youtube.com/watch?v=heQmjP5tQn0 YouTube] (via [https://invidio.us/watch?v=heQmjP5tQn0 Invidious])

== OpenAlt 2019 - 2nd November 2019 ==

'''Debian v kapse''' - ''Pavel Machek''

[https://openalt.cz/2019/program_detail.php#event_32 Event info]

== Devuan Conference #1: “THE POWER OF CHOICE” - 7th April 2019 ==

'''Maemo Leste: Mobile Hacker OS''' - ''Ivan Jelincic (parazyd)''

Video: [https://www.youtube.com/watch?v=_ULy7jBnXdo&t=12304 YouTube] (via [https://invidio.us/watch?v=_ULy7jBnXdo&t=12304 Invidious])

== FOSDEM 2019 - Lightning Talk - 2nd February 2019 ==

'''Maemo Leste - A Debian/Devuan based mobile hacker OS''' - ''Merlijn Wajer (Wizzup)''

[https://archive.fosdem.org/2019/schedule/event/maemo_leste_mobile Event info]

Video: [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.webm WebM/VP9], [https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.mp4 MP4]

[https://maedevu.maemo.org/media/fosdem-2019-maemo-leste.pdf Slides]

== OpenFest 2018 - 4th November 2018 ==

'''Maemo Leste''' - ''Merlijn Wajer (Wizzup), Ivan Jelincic (parazyd)''

[https://www.openfest.org/2018/en/full-schedule/#lecture-360 Event info]

Video: [https://maedevu.maemo.org/media/openfest-2018-maemo-leste-wizzup-parazyd.webm WebM]

[https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf Slides]

== OpenAlt 2018 - 3rd November 2018 ==

'''Maemo Leste - Debian do kapsy''' - ''Pavel Machek''

[https://openalt.cz/2018/program_detail.php#event_14 Event info]

Video: [https://www.youtube.com/watch?v=9C0j4M_AQ2I YouTube] (via [https://invidio.us/watch?v=9C0j4M_AQ2I Invidious])

[https://openalt.cz/2018/avatars/d96c9c95348879e4e6e2c27f665ca2b3-nokia_n900.pdf Slides]

Main Page

2020-02-01T07:11:52Z

Derby: /* Links */ Add YouTube channel

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

Also see our [[Leste_FAQ|FAQ]].

= Supported Devices =

See [[:Category:Device]]

= Development =

See [[Development]]

= Roadmap =

== Project milestones ==
https://github.com/maemo-leste/bugtracker/milestones

== Wishlist ==

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

= Links =
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Main Page

2020-02-01T04:49:15Z

Derby: /* Project milestones */ The wishlist already has it's own section

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

Also see our [[Leste_FAQ|FAQ]].

= Supported Devices =

See [[:Category:Device]]

= Development =

See [[Development]]

= Roadmap =

== Project milestones ==
https://github.com/maemo-leste/bugtracker/milestones

== Wishlist ==

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

= Links =
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Development/Porting Packages

2020-01-28T03:12:29Z

Derby: Add a placeholder that will be used to describe the procedure for forking a Debian/Devuan package

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

Leste FAQ

2020-01-26T22:57:45Z

Derby: /* Why is Maemo Leste based on Devuan rather than Debian? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (although we ended up rewriting them anyway as Maemo Leste now uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T22:55:19Z

Derby: /* Why is Maemo Leste based on Devuan rather than Debian? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the ''upstart'' init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (we ended up rewriting them anyway as now Maemo Leste uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T22:32:13Z

Derby: /* What is Maemo Leste? */ Fix typo

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it is a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the upstart init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (we ended up rewriting them anyway as now Maemo Leste uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T22:31:47Z

Derby: /* What is Maemo Leste? */ Improve wording; add hyperlinks.

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is an operating system based on GNU/Linux that is currently in development. It is aimed at mobile devices with touch screens such as smartphones, tablets and PDAs.

It is built on top of '''[https://devuan.org/ Devuan]''', and thus indirectly based on [https://www.debian.org/ Debian]. Essentially, it a modernised and liberated version of '''[https://en.wikipedia.org/wiki/Maemo#Maemo_5 Maemo 5/Fremantle]'''; the last version of the mobile Linux OS from Nokia that was released in 2009 for the [https://en.wikipedia.org/wiki/Nokia_N900 Nokia N900] internet tablet/smartphone. Unlike its predecessor which only ran on a single device, Maemo Leste runs on a variety of devices.

In Maemo Leste, closed-source packages that originate from Fremantle have been reversed engineered, liberated, updated and rebuilt; whilst open-source Fremantle packages have been updated to newer libraries and APIs, including [https://en.wikipedia.org/wiki/Hildon Hildon], the mobile user interface from Fremantle.

Maemo Leste aims to provide an unconstrained and free mobile Linux distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the upstart init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (we ended up rewriting them anyway as now Maemo Leste uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T20:34:56Z

Derby: /* How about other popular non-Android mobile Linux distributions? */ Rephrase

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]], preferring to prioritise device compatibility and ease of device porting, instead of prioritising software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the upstart init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (we ended up rewriting them anyway as now Maemo Leste uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T20:24:44Z

Derby: /* Why is Maemo Leste based on Devuan rather than Debian? */ Fix typo; rephrase; Devuan upstart support was dropped in ascii.

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticeable in the project).

Maemo Fremantle uses the upstart init system. We initially chose Devuan because we figured Devuan might support upstart to some degree as well, so we would not have to deal with rewriting the init scripts (we ended up rewriting them anyway as now Maemo Leste uses OpenRC). Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T20:11:36Z

Derby: /* Are packages (for N900 especially) Thumb-compiled? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are ARM packages Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T20:09:44Z

Derby: /* What's wrong with Android (vendor) kernels? */ Rephrase

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices on the market, all with kernels based on Linux; yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T20:08:08Z

Derby: /* What's wrong with Android (vendor) kernels? */ Android kernels diverge so much (breaking compatibility), that it is incorrect to call them Linux

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T19:58:35Z

Derby: /* Are there any technical merits in using System V init with OpenRC instead of systemd? */

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) Linux kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate; there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T19:47:57Z

Derby: /* Are there any technical merits in using System V init with OpenRC instead of systemd? */ Reinforce the importance of choosing Devuan over Debian.

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) Linux kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate, there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. systemd now has [https://www.phoronix.com/scan.php?page=news_item&px=systemd-2019-stats over 1.2 million lines of code]; this complexity increases the [https://2h73ayp5jhv44aq9p3zmp9gd-wpengine.netdna-ssl.com/wp-content/uploads/2017/08/GaugingSoftwareReadinessWithDefectTracking.pdf defect density] and [https://docs.microsoft.com/en-us/archive/msdn-magazine/2004/november/security-tips-minimizing-the-code-you-expose-to-untrusted-users attack surface]. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T18:55:56Z

Derby: Added question on Debian/systemd compatibility

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) Linux kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate, there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== Can Maemo Leste work with a Debian/systemd base? ===

Several users and developers have expressed interest in using Maemo Leste with Debian and systemd. Work has begun to make this possible. We do not want to restrict the reach of Maemo Leste, therefore we welcome contributions for Debian/systemd compatibility and provide assistance with it. It is hoped that eventually we will be able to provide users with a choice of Devuan and Debian bases for Maemo Leste.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T18:34:39Z

Derby: /* Does Maemo Leste use Halium? */ Fix typo

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) Linux kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate, there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Leste FAQ

2020-01-26T18:31:44Z

Derby: /* How does Maemo Leste compare with PureOS? */ Update info on Librem 5

{{Stub}}

=== What is Maemo Leste? ===

Maemo Leste is a GNU/Linux distribution aimed at mobile devices with touch screens: smartphones, tablets and PDAs.
Maemo Leste is based on Devuan (and thus indirectly based on Debian), while it inherits a lot of packages from (the now very old) "Maemo Fremantle", the Nokia OS for the Nokia N900 internet tablet/phone.
The mobile user interface is based on "Hildon" from Fremantle, as are various other packages (from Fremantle) -- some have been reversed engineered, others which were already open source have been updated to newer libraries and APIs.

Maemo Leste aims to provide an unconstrained and free mobile distribution for hackers, developers and even just casual users.

=== Why do we need another mobile operating system? ===

What Maemo Leste hopes to bring to the table is a streamlined but otherwise unrestrained mobile OS. User freedom and hackability of the devices, while still having a usable OS.

We aim to provide a "true" GNU/Linux experience by providing up to date packages, do not use vendor Linux kernels (only "vanilla").

=== Why not add/extend new packages to Fremantle instead? ===

Fremantle is ancient, and quite a few packages are [https://wiki.maemo.org/Fremantle_closed_packages closed source] and also outdated.
Many are in dire need of a replacement, either for interoperability sake (browser, closed wifi stack, closed phone stack) or need a lot of updates to be even reasonably secure: ancient (vulnerable) browser, unsupported crypto libraries, ancient Linux kernel are just a few.

Beyond that, Fremantle was never truly "Debian" -- although it used a lot of the Debian ecosystem. We realise that we do not have the time to maintain all kinds of core packages, so it made a lot of sense to base Maemo Leste on a modern and community-run distribution. We can't run an entire distribution without a good base distribution like Debian.

Furthermore, adding lots of updated and new packages mixed together with the old Fremantle packages is likely to become a big hell. Old packages need an older glibc (even though it claims to be backwards compatible, it isn't always), other libraries might depend on other specific libraries). That will also make it very hard to keep track of what old and new packages are in place, we would still be stuck with many other outdated packages - permanently frozen kernel interface, and so forth. This only gets more complicated with the new C++ ABI with newer GCC, and so on. We'd also ideally have all packages be Position Independent Executables (PIE), further complicating mixing with Fremantle.

We went for a distribution based on Debian because it would provide a clean base; and Fremantle already used a large part of the Debian ecosystem. Right now it is very easy to figure out what packages Maemo Leste adds on top of Devuan/Debian, which also makes the life of developers (and even users) easier.

=== Does Maemo Leste use Halium? ===
No. Halium aims to build a common base for mobile GNU/Linux distributions. This is great idea in principle but their choice of components leaves a lot to be desired.

Halium uses Linux kernels from Android. See [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|below]] for a description of some of the problems of Android kernels. By embracing the use of Android kernels, Halium can provide a working device ports fairly quickly but this may have a negative effect in the long run. A developer who has a fully working device running GNU/Linux with an Android kernel, may be less inclined to help get that device running on mainline Linux, thus the reliance on Android continues. The shortage of mainline Linux kernel contributions from the developers of Halium and other libhybris-based Linux distributions is evident.

=== What is mainline Linux? ===
Mainline Linux is pure Linux, taken and built from Linus Torvalds' Git tree (kernel.org). It has an organic development model which provides new releases every two to three months and also less frequent long term supported stable releases.

=== What's wrong with Android (vendor) Linux kernels? ===
The Android Open Source Project (AOSP) leeches off Linux. Hundreds, if not thousands, of out-of-tree kernel forks are maintained with very little effort to contribute back to mainline Linux. This not only hurts the Linux development ecosystem but we as users also suffer as a consequence of this. There are thousands of different Android devices with kernels based on Linux on the market, yet only a handful of those devices are able to run on mainline Linux, and most of those that do, have very limited hardware support. Linux kernels are [https://source.android.com/devices/architecture/kernel/android-common#branch-hierarchy forked up to five times by AOSP, before finally being forked once more by the device manufacturer]. This results in kernels that have diverged significantly from mainline. This means that it is not possible to install an up-to-date mainline kernel on any given Android device. Also, it often means that kernel updates are not timely, nor frequent. When the device manufacturer decides to stop supporting the device, no further kernel updates are provided. This allow the manufacturers of Android devices to practise [https://en.wikipedia.org/wiki/Planned_obsolescence planned obsolescence]. This practice is a huge contributor to our society's [https://en.wikipedia.org/wiki/Throw-away_society throw-away culture], forcing consumers to replace their devices every year or two and has a [https://www.fastcodesign.com/90165365/smartphones-are-wrecking-the-planet-faster-than-anyone-expected big impact on our planet]. The vast majority of users of Android devices are not even made aware when their kernel has reached end-of-life, leaving them vulnerable to known exploits.

=== Why is it important to run mainline Linux? ===
Using mainline Linux keeps us in touch with [https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git cutting-edge kernel development], allows us to provide [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git normal stable releases] which helps to accelerate development, whilst also giving us the option of providing [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git long-term supported stable releases]. Mainline Linux does not suffer from any of the problems associated with Android kernels listed above. The first rule of Linux kernel development is [https://felipec.wordpress.com/2013/10/07/the-linux-way/ "don't break userspace"]. Regressions are not allowed and this ensures kernel-to-userspace API and ABI stability. By running mainline Linux, once a device is supported, we can be sure that it will continue to work and we will receive regular kernel updates for decades to come, just like running Linux on your PC. See also the official explanation on [https://www.kernel.org/doc/html/latest/process/1.Intro.html#the-importance-of-getting-code-into-the-mainline the importance of getting code into the mainline].

=== How does Maemo Leste compare with postmarketOS? ===
postmarketOS is mobile GNU/Linux distribution which runs Android kernels but also mainline Linux kernels. We share several goals in common with postmarketOS, particularly the use of mainline Linux. This presents a great opportunity for collaboration. Both Maemo Leste and postmarketOS have great working relationship and have already benefited from each other's work.

=== How does Maemo Leste compare with PureOS? ===
Purism's PureOS is currently in development for the Librem 5 phone. Purism have stated their plans to upstream all work to parent projects. This naturally presents another opportunity for collaboration, especially with PureOS also being based on Debian. We would welcome any collaborations with Purism. Work on a Maemo Leste port for the Librem 5 phone is in progress ([https://github.com/Daniel-Abrecht/image-builder image-builder], [https://github.com/Daniel-Abrecht/arm-sdk arm-sdk], [https://dpa.li/temp/l5-maemo.mp4 video]).

=== How about other popular non-Android mobile Linux distributions? ===
The majority of initiatives to create a mobile Linux distribution as an alternative to Android have often made questionable decisions on the components they have chosen to include in their distributions. Some of these distributions are built for profit which means they often do not have the best interests of the end-user at heart. This has resulted in the inclusion of closed source components where they could have been avoided.

One of the most popular alternatives is the worst offender. It includes a proprietary GUI and a proprietary application framework which means that apps developed for that platform will run only on that platform and nowhere else. Its base distribution, which is actually open source, deliberately uses unsupported/unmaintained GNU General Public License (GPL) version 2 licensed packages (even though they have long since been superseded by newer versions relicensed as GPL v3) for the purpose of [https://en.wikipedia.org/wiki/Tivoization Tivoisation]. This allows a vendor to use hardware restrictions to prevent users from running modified versions of the software on their hardware. This distribution has a counterpart distribution which is open source, however it is unfortunately also based on the same Tivoised base distribution.

Another popular alternative distribution decided that instead of working together with the community on a common display manager, Wayland, to replace X11, they would develop their own. In the process, they heavily criticised Wayland. Some of the criticism was unfounded, and even though other points may have been fair, Wayland could have been adapted to suit their needs. They since retracted that criticism, nevertheless they continue to work on their own display manager in preference of working with the greater community on Wayland.

Finally, the vast majority of alternative distributions have decided to go the route of using [[#What.27s_wrong_with_Android_.28vendor.29_Linux_kernels.3F|Android kernels]] in order to prioritise device compatibility and ease of ports over software freedoms.

=== Why is Maemo Leste based on Devuan rather than Debian? ===

Convenience for developers, and a little bit of politics (but this is not really noticable in the project).

Fremantle used the (now abandoned) upstart init system. We initially chose Devuan because we figured Devuan might (and it does, afaik) support upstart to some degree as well, so we would not have to deal with rewriting the init scripts.
But we ended up doing it anyway, and now Maemo Leste uses OpenRC. Another reason is that some people who initiated the project are either working on Devuan or are close with people who work on Devuan.

As you may know, the Devuan project focuses on providing a Debian alternative that can be used without systemd. Although Debian can be installed without systemd, Devuan provides a much more stable and tested system in this regard. Key system components such as PolicyKit, UPower and udisks2 have been known to be broken in Debian when it is used without systemd, whereas Devuan provides working replacements.

=== Are there any technical merits in using System V init with OpenRC instead of systemd? ===
Not wanting to turn this into a systemd debate, there are already plenty of places on the internet where you can read up on the pros and cons of systemd. Both init systems have their merits. System V init with OpenRC does not provide as many features as systemd, but perhaps its main advantage is architectural. Although traditional init is flawed in several aspects, we believe that its loose coupling of components help to provide better reliability, stability and security.

=== What devices does Maemo Leste work on? ===

Our currently list of (semi) supported devices can be found here: [[:Category:Device]]

Maemo Leste could work on your device, and we'd like to link you to a porting guide here, but we don't have one yet.

Maemo Leste focuses on providing support for devices that can run on mainline Linux, with an emphasis on supporting mobile/cellular phones. There are a limited number of mobile phones supported by mainline Linux at present, all with varying degrees of hardware support. Although you may be disappointed by the lack of devices currently supported by Maemo Leste, we hope this will expand and we strongly believe that running on top of mainline Linux is the right way forward for building a mobile OS that respects software freedoms.

Maemo Leste has also been shown to run on the Gemini PDA which uses an Android kernel with libhybris. It should be possible to run Maemo Leste on other Android devices using this method, however this falls outside of the scope of this project and what we are trying to achieve, As such, only limited support would be provided.

=== Can I run an alternative desktop environment or window manager instead of Hildon? ===
The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. There are plans to make this process easier, however don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

=== Are packages (for N900 especially) Thumb-compiled? ===
Yes. This is very useful for N900 since it only has 256MB RAM. https://www.embedded.com/electronics-blogs/beginner-s-corner/4024632/Introduction-to-ARM-thumb

Motorola Droid 4

2020-01-22T13:50:44Z

Derby: /* Status */ Compass

{{Stub}}

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Not yet || PowerVR SGX540 (closed driver) - see [[Motorola Droid 4/PowerVR]]
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes ||
|-
| 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || WIP || Reported to work, no UI yet
|-
| Phone calls || WIP || Reported to work, no UI yet
|-
| Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.
|-
| FM Transmitter || N/A ||
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || ? || Available as input device, needs MCE work
|-
| Proximity sensor || ? ||
|-
| HDMI-out || WIP || works, but not with hildon-desktop
|-
| TV-out || N/A ||
|-
| Vibration Motor || Yes ||
|-
|Compass || No || Mainline supports it, so Leste needs to add config - see https://github.com/maemo-leste/bugtracker/issues/294
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Now go to the working directory and run:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.

== Postinstall notes for 20200112 image ==

=== Wifi ===

Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)

deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free

apt install -t ascii-backports wpasupplicant
apt install -t ascii-backports firmware-ti-connectivity

=== Bluetooth ===

Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/

=== Sound ===

This needs to be executed after each boot by hand ;

modprobe snd-soc-cpcap
modprobe snd-soc-motmdm
modprobe snd-soc-audio-graph-card

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

[[Category:Device]]

Motorola Droid 4

2020-01-22T13:40:13Z

Derby: Bluetooth info

{{Stub}}

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Not yet || PowerVR SGX540 (closed driver) - see [[Motorola Droid 4/PowerVR]]
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes ||
|-
| 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || WIP || Reported to work, no UI yet
|-
| Phone calls || WIP || Reported to work, no UI yet
|-
| Bluetooth || Yes || Needs firmware - see [[#Bluetooth|below]]. See also https://github.com/maemo-leste/bugtracker/issues/290.
|-
| FM Transmitter || N/A ||
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || ? || Available as input device, needs MCE work
|-
| Proximity sensor || ? ||
|-
| HDMI-out || WIP || works, but not with hildon-desktop
|-
| TV-out || N/A ||
|-
| Vibration Motor || Yes ||
|-
|Compass || No || Mainline supports it, so Leste needs to add config
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Now go to the working directory and run:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.

== Postinstall notes for 20200112 image ==

=== Wifi ===

Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)

deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free

apt install -t ascii-backports wpasupplicant
apt install -t ascii-backports firmware-ti-connectivity

=== Bluetooth ===

Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/

=== Sound ===

This needs to be executed after each boot by hand ;

modprobe snd-soc-cpcap
modprobe snd-soc-motmdm
modprobe snd-soc-audio-graph-card

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

[[Category:Device]]

Motorola Droid 4

2020-01-22T13:28:23Z

Derby: /* Status */ SGX info

{{Stub}}

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Not yet || PowerVR SGX540 (closed driver) - see [[Motorola Droid 4/PowerVR]]
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes ||
|-
| 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || WIP || Reported to work, no UI yet
|-
| Phone calls || WIP || Reported to work, no UI yet
|-
| Bluetooth || Not yet || Needs firmware. Download https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts and save it in <code>/lib/firmware/ti-connectivity/</code>
|-
| FM Transmitter || N/A ||
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || ? || Available as input device, needs MCE work
|-
| Proximity sensor || ? ||
|-
| HDMI-out || WIP || works, but not with hildon-desktop
|-
| TV-out || N/A ||
|-
| Vibration Motor || Yes ||
|-
|Compass || No || Mainline supports it, so Leste needs to add config
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Now go to the working directory and run:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.

== Postinstall notes for 20200112 image ==

=== Wifi ===

Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)

deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free

apt install -t ascii-backports wpasupplicant
apt install -t ascii-backports firmware-ti-connectivity

=== BT ===

Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/

=== Sound ===

This needs to be executed after each boot by hand ;

modprobe snd-soc-cpcap
modprobe snd-soc-motmdm
modprobe snd-soc-audio-graph-card

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

[[Category:Device]]

Motorola Droid 4

2020-01-22T13:17:52Z

Derby: /* Status */ Add link to Serial Cable section

{{Stub}}

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Not yet || Also PowerVR - see [[Motorola Droid 4/PowerVR]]
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes ||
|-
| 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || WIP || Reported to work, no UI yet
|-
| Phone calls || WIP || Reported to work, no UI yet
|-
| Bluetooth || Not yet || Needs firmware. Download https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts and save it in <code>/lib/firmware/ti-connectivity/</code>
|-
| FM Transmitter || N/A ||
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || ? || Available as input device, needs MCE work
|-
| Proximity sensor || ? ||
|-
| HDMI-out || WIP || works, but not with hildon-desktop
|-
| TV-out || N/A ||
|-
| Vibration Motor || Yes ||
|-
|Compass || No || Mainline supports it, so Leste needs to add config
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Now go to the working directory and run:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.

== Postinstall notes for 20200112 image ==

=== Wifi ===

Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)

deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free

apt install -t ascii-backports wpasupplicant
apt install -t ascii-backports firmware-ti-connectivity

=== BT ===

Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/

=== Sound ===

This needs to be executed after each boot by hand ;

modprobe snd-soc-cpcap
modprobe snd-soc-motmdm
modprobe snd-soc-audio-graph-card

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

[[Category:Device]]

Motorola Droid 4

2020-01-22T13:14:23Z

Derby: Move sections to a more logical order

{{Stub}}

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=
|release_date=
|soc=
|dram=
|power=
|lcd=
|video=
|audio=
|network=
|storage=
|usb=
|camera=
|sensors=
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.4 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux/tree/maemo-5.4
|-
| Serial || Yes || On MicroUSB port, requires special cable
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Not yet || Also PowerVR - see [[Motorola Droid 4/PowerVR]]
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes ||
|-
| 2G/3G data || WIP || Reported to work, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| SMS || WIP || Reported to work, no UI yet
|-
| Phone calls || WIP || Reported to work, no UI yet
|-
| Bluetooth || Not yet || Needs firmware. Download https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts and save it in <code>/lib/firmware/ti-connectivity/</code>
|-
| FM Transmitter || N/A ||
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || ? || Available as input device, needs MCE work
|-
| Proximity sensor || ? ||
|-
| HDMI-out || WIP || works, but not with hildon-desktop
|-
| TV-out || N/A ||
|-
| Vibration Motor || Yes ||
|-
|Compass || No || Mainline supports it, so Leste needs to add config
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz (NOTE: 20200112 image may have issues with WiFi)

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

Now go to the working directory and run:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you unaccelerated hildon-desktop after a minute.

== Postinstall notes for 20200112 image ==

=== Wifi ===

Requires wpasupplicant and firmware-ti-connectivity from ascii-backports (needs to get added to sources.list)

deb http://pkgmaster.devuan.org/merged ascii-backports main contrib non-free

apt install -t ascii-backports wpasupplicant
apt install -t ascii-backports firmware-ti-connectivity

=== BT ===

Requires https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts to go in /lib/firmware/ti-connectivity/

=== Sound ===

This needs to be executed after each boot by hand ;

modprobe snd-soc-cpcap
modprobe snd-soc-motmdm
modprobe snd-soc-audio-graph-card

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

[[Category:Device]]