Maemo Leste - First update (March 2018)

Merlijn Wajer, Fri 02 March 2018, News

battery, droid4, kernel, n900, networking, ofono

It's been a month since our first post and there's a lot of stuff to talk about!

First of all, someone added us to Wikipedia, cool!

Devuan, the distribution that Maemo Leste is based on, has released a beta version of "Devuan ASCII" (Devuan 2.0): Maemo Leste uses Devuan Ascii, so we're happy to see ASCII being close to a release.

On the software side

We have imported various new packages, added new device images, and have been working on fixing and enhancing existing packages.

More work has been done behind the scenes, so if you're excited, please do follow our github issue tracker and/or the IRC channel. We also have logs of the channel history now:

What is next?

We have started to use the Github 'Milestones' feature to sort tickets by order of importance and feasibility, and you can see the ticket that we deem necessary for an Alpha releases here: Alpha release milestone.

A lot of major things are still missing. A few obvious ones are phone calls, UI and daemons for conversations, integration for wifi connectivity, integration for 3g data, 3d acceleration for various supported platforms, support for Qt applications and some sort of Android application support. We will try to cover what we're going to work on for the next month, to give you an indication on where we are, where we are going, and where you can help.


The first big thing that we want to attempt to get into a working state is connui, icd2 and wpa_supplicant integration for icd2. In layman terms: we want wifi to work with the Maemo Fremantle UIs. To do this, we need to finish reverse engineering the last bits of connui, and then we need to write a plugin for icd2 that communicates with wpa_supplicant, the de-facto wifi daemon. (See #73 and #42) We will need someone to finish the icd2 documentation in doxygen format: #28

Similarly, we would also need someone to take a look at what the best way would be to integrate ofono into our networking stack. One method to do that would be to integrate it into icd2, but perhaps there are also alternatives, by using NetworkManager or connui, and somehow hooking those up to icd2.

Having working phone calls with audio (even with perhaps not too great audio quality) would be a huge win and might not be too far out, we're hoping someone will pick this up, see #27.

Android in a box

The best way to run Android applications on GNU/Linux seems to be Anbox, which is in the process in being packaged for Debian (and Devuan): We have a ticket for anbox support, #9.

We do not yet know how much RAM anbox would use and if it is feasible for all our supported devices, but devices such as the LIME2 and the Motorola Droid 4 might have enough RAM to spare to run Android applications using Anbox.

Drivers and packaging

Having 3D acceleration work on the LIME2 devices would be quite nice, since they can output to high resolution screens, in which case 3D acceleration is really a must-have #43.

The Droid 4 also currently has no 3D acceleration. We hope that a more lightweight version of hildon-desktop can provide some solace here #51.

Finishing the USB gadget code is definitely a short term goal, but that depends on how fast we can get the kernel bugs resolved.

Another thing we want to wrap up soon is importing the Maemo Qt patches ( #53), since that will allow us (and hopefully, others) to import many more packages from Maemo Fremantle. Examples of such packages are clockui (#55), osso-calculator (#54) and open media player (#25).

Packaging pulseaudio is also somewhere on the road map, which might be required for better call quality on the N900 and also to protect the N900 speakers from being irrepairably damaged #62.

Platform support

We might look at supporting arm64 in the near future, if we have a (virtual) device that we can test our builds on.


If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our bugtracker.

Join us! We really need more people helping out. At this point, we specifically need developers who can work on porting packages, help out with reverse engineering, and debug driver issues.

We're currently on in #maemo-leste, but also hang out in #maemo. We also monitor the github issues closely.