https://maemo-leste.github.io/2025-11-08T23:00:00+01:002025-11-08T23:00:00+01:002025-11-08T23:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2025-11-08:/maemo-leste-2025-daedalus-release.html

<p>It's been way too long since our last update, but many things have changed in the meantime. We've:</p> <ul class="simple"> <li>released Maemo Leste for Devuan Daedalus (Debian Bookworm);</li> <li>received funding from NLnet (through the <tt class="docutils literal">NGI0 Commons Fund</tt>)</li> <li>added support for Qt6;</li> <li>added more extras packages;</li> <li>improved the chat and browser application significantly …</li></ul>

<p>It's been way too long since our last update, but many things have changed in the meantime. We've:</p> <ul class="simple"> <li>released Maemo Leste for Devuan Daedalus (Debian Bookworm);</li> <li>received funding from NLnet (through the <tt class="docutils literal">NGI0 Commons Fund</tt>)</li> <li>added support for Qt6;</li> <li>added more extras packages;</li> <li>improved the chat and browser application significantly;</li> <li>added a CI/CD to our Forgejo instance;</li> <li>improved the Nokia N900 support;</li> <li>improved ofono (modem) support for the mapphones (Motorola Droids) and Nokia N900</li> </ul> <p>and much more...</p> <div class="section" id="funding"> <h2>Funding</h2> <p>Maemo Leste <a class="reference external" href="https://nlnet.nl/project/MaemoLeste-AppArmour/">has received funding from NLNet</a> as part of the <tt class="docutils literal">NGI0 Commons Fund</tt> to continue improving our system!</p> <p>In particular, the following tasks have received funding:</p> <ul class="simple"> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/41?state=all">Conversations improvements</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/751">Porting extras packages to Daedalus</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/42?state=all">Support Qt6 next to Qt5</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/43?state=all">Forgejo CI/CD with extras integration in particular</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/37?state=all">Porting Maemo Leste to Excalibur/Trixie</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/39?state=all">AppArmor support in Maemo</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/38?state=all">Integrate and switch to Geoclue in Maemo Leste</a></li> <li><a class="reference external" href="https://git.maemo.org/leste/bugtracker/milestone/40?state=all">Port Maemo Leste to additional devices</a></li> </ul> </div> <div class="section" id="daedalus"> <h2>Daedalus</h2> <p>We ported Maemo Leste to Devuan Daedalus (Debian bookworm) some time ago (see <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/751">issue #571</a>) and silently switched our images over to this release. At the time we were caught up on Debian stable, but as of writing of this post, Debian bookworm is now old stable again. One of our priorities is to switch to Devuan Excalibur (Debian Trixie) soon, so that we are on Debian stable.</p> <p>It has taken us while but we are slowly catching up to the Debian release cycles - these things take time because we have to port our packages to newer libraries and code, and when we started Maemo Leste we were targetting a distribution that was then already olstable.</p> <p>As part of the upgrade to Daedalus, we:</p> <ul class="simple"> <li>ported our media application framework <a class="reference external" href="https://git.maemo.org/leste/mafw-tracker-source/commit/c0e38e4eb46e2aa2492bfedb983956bb50c4b79d">to use Tracker 3</a></li> <li>rebased our Xorg patches on the debian xorg</li> <li><a class="reference external" href="https://git.maemo.org/leste/dependency-resolver">wrote a piece of software</a> to figure out in what order to build our packages in Jenkins, as this historically has been somewhat of a challenge</li> <li>Decreased the number of upstream software that we had to fork, as our patches made it upstream in some cases</li> <li>migrate away from python2 in <a class="reference external" href="https://git.maemo.org/leste/maemo-system-services/commit/4fc8f17d9dfb55eacc573be856054f18e3e08961">icd2 module management</a>.</li> <li>Switched to a newer upstream upower version which contains <a class="reference external" href="https://git.maemo.org/leste-upstream-forks/upower/commit/1df483b7608fcdd8e69b9968fe85b42a112cab18">most of our patches</a>;</li> </ul> <p>The actual set of changes is much larger and can be seen in <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/751">issue #571</a>.</p> <div class="section" id="jenkins-and-versioning"> <h3>Jenkins and Versioning</h3> <p>When we first made the <tt class="docutils literal">chimaera</tt> release, we made a mistake in how we version the packages, normally our packages end in something like: <tt class="docutils literal">+4m7</tt> - which means &quot;distribution release 4, Maemo 7&quot;. In the <tt class="docutils literal">chimaera</tt> case, the <tt class="docutils literal">4</tt> felloff. Unfortunately in Debian packaging versioning this means that the <tt class="docutils literal">chimaera</tt> versions without this one-digit prefix always take precendence over the packages with this additional prefix. In an attempt to make dist-upgrading possible, we <a class="reference external" href="https://git.maemo.org/leste/leste-config/commit/4c4de8c405f3ce5a10e35d1d16b5f76de9f7215e">added a file to apt.preferences.d</a> that gives the packages <tt class="docutils literal">daedalus</tt> release repository a higher priority than the <tt class="docutils literal">chimaera</tt> ones. We <a class="reference external" href="https://git.maemo.org/leste/jenkins-integration/commit/8e6c21127e46c9975ab985dab699f50b3dc50027">also fixed the problem in Jenkins</a> although this doesn't really matter at this point, as the chimaera versions are already problematic.</p> <p>This <a class="reference external" href="https://git.maemo.org/leste/jenkins-integration/commit/9802ed8e969ac209f2358d1f04683556423fb5eb">commit to jenkins-integration</a> adds the proper versioning for Daedalus and we also fixed some IRC integration script for packages that are only built for one architecture in <a class="reference external" href="https://git.maemo.org/leste/jenkins-integration/commit/b00ad4d9070861413fcc5f915272ebd58157dd4f">commit b00ad4d9</a>.</p> </div> <div class="section" id="dist-upgrading"> <h3>dist-upgrading</h3> <p>As always, installing a <tt class="docutils literal">daedalus</tt> image is the easiest way to get up to date, but it is possible to dist-upgrade from <tt class="docutils literal">chimaera</tt> to <tt class="docutils literal">daedalus</tt>, but one has to ensure that the repositories in <tt class="docutils literal">/etc/apt/sources.list</tt> and <tt class="docutils literal">/etc/apt/sources.list.d/*</tt> have their <tt class="docutils literal">chimaera</tt> references removed. Make sure you're fully up to date on <tt class="docutils literal">chimaera</tt> first.</p> </div> </div> <div class="section" id="core"> <h2>Core</h2> <p>Various core applications and daemons have seen improvements and fixes.</p> <div class="section" id="browser-jib"> <h3>Browser (jib)</h3> <p>Jib now has full-support for the virtual keyboard, so that this browser is also usable from devices with no hardware keyboard. In addition, we've improved the built-in adblocker, so it does not block benign resources.</p> </div> <div class="section" id="calendar"> <h3>Calendar</h3> <p>We've fixed the vertical alignment in the month display for the calendar, see <a class="reference external" href="https://git.maemo.org/leste/qalendar/pulls/1">qalendar/pulls/1</a>.</p> <img alt="" src="/images/qalendar-vertical-alignment.png" style="width: 531px; height: 407px;" /> </div> <div class="section" id="ntp"> <h3>ntp</h3> <p><tt class="docutils literal">sicelo</tt> made it such that we when we fetch the time over NTP, we also synchronise it to our hardware clock, see <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/61">leste-config/pulls/61</a></p> </div> <div class="section" id="conversations"> <h3>Conversations</h3> <p>Conversations has received a lot of attention - bringing you new, and exciting features for our Daedalus release.</p> <div class="section" id="maemo-fi-cation"> <h4>Maemo-fi-cation</h4> <p>Conversations now uses more UI components (and paradigms) from Fremantle.</p> <p>The settings and about page were moved to a popup.</p> <img alt="" src="/images/conv_settings.png" style="width: 576px; height: 324px;" /> <p>We are now also using a dialog for the contact picker (Compose new message).</p> <p>The maemo-fi-cation of our UI is still on-going, and will be expanded with more Maemo components in the future.</p> </div> <div class="section" id="improved-tableview"> <h4>Improved tableview</h4> <p>We have various places where messages are listed: the overview (the first screen), search window, and the groupchat memberlist window. Code-wise, we are now using the same table everywhere.</p> <p>In addition, we improved this table's sorting, avatar/presence visualization, , and made table updates more performant.</p> </div> <div class="section" id="ux-improvements"> <h4>UX improvements</h4> <p>When writing a long message, the input box now dynamically grows according to input.</p> <img alt="" src="/images/conv_expand.png" style="width: 576px; height: 324px;" /> <p>The QML interface has been reworked to be more responsive. This was already the case, but there was still the occasional clipping bug.</p> <p>In portrait, everything now properly scales, and adjusts:</p> <img alt="" src="/images/conv_responsive.png" style="width: 324px; height: 576px;" /> <p>Some other improvements related to the chat window are:</p> <ul class="simple"> <li>Improved 'bottom pinning' on incoming messages</li> <li>Support key combination shift+enter to introduce a newline whilst 'auto-send on ENTER' is enabled</li> <li>Set focus directly after sending a message</li> <li>Optional shader for chat bubble backgrounds, similar to a well-known chat application</li> <li>Optional shader for the background: matrix falling rain</li> </ul> <img alt="" src="/images/conv_matrix.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="slim-mode"> <h4>Slim mode</h4> <p>Conversations is designed to run on low-powered devices, with possibly old(er) hardware. As such, conversations is written in C++, and leverages various tricks to keep memory usage low, and performance fast.</p> <p>While the regular QML interface is already minimal in terms of resource usage, we have introduced 'slim' mode for a minimalistic, alternative QtWidgets based interface. This can be enabled in the settings.</p> <p>Since Conversation's core logic was already separate from presentation, supporting this alternative interface required minimal changes.</p> </div> <div class="section" id="attachments"> <h4>Attachments</h4> <p>We now parse incoming and outgoing links, and render these links depending on their content type. In the case of XMPP, when someone sends a picture - this is generally just a link to a <tt class="docutils literal">.jpg</tt>. Conversations now renders them inline.</p> <p>Additionally there is also an image viewer that supports gestures like panning, and zooming to further inspect incoming media.</p> <p>By default, this feature is off for privacy reasons (as to prevent auto-visiting weblinks sent by a counterparty), but can be turned on in the settings.</p> <img alt="" src="/images/conv_attachment2.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="address-book-integration"> <h4>Address book integration</h4> <p>Our initial address book integration introduced features like avatars and display names. We've now expanded this to also support 'master contacts'.</p> <p>Master contacts unify contacts from multiple sources such as XMPP, Matrix, and SMS into a single contact.</p> <p>By keeping contact management (osso-abook) and messaging (Conversations) separate, Maemo ensures that the address book integrates across the entire system. This allows applications to share a consistent, unified view of contacts while keeping the messaging layer focused on communication.</p> <p>Additionally, the code responsible for interacting with the address book has seen major improvements, resulting in better performance.</p> </div> <div class="section" id="channel-member-list"> <h4>Channel member list</h4> <p>Groupchats now expose a memberlist, from which you can start a private conversation with a contact.</p> <img alt="" src="/images/conv_memberlist.png" style="width: 324px; height: 576px;" /> <p>Since the memberlist could be quite long, it has the ability to filter for specific names.</p> </div> </div> <div class="section" id="qt5"> <h3>Qt5</h3> <p><tt class="docutils literal">Sander</tt> has made it so that the Hildon Input Method (HIM) now works well in Qt, which means that devices without keyboard have access to a usable virtual keyboard. This work can be found in <a class="reference external" href="https://git.maemo.org/leste/qt-input-maemo">leste/qt-input-maemo</a> and is very exciting.</p> <p>Additionally, the qt menu is now always shown properly (see <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/563">issue #563</a>).</p> </div> <div class="section" id="qt6-platform-plugins"> <h3>Qt6 platform plugins</h3> <p>Leste has various Qt plugins to make Qt applications integrate with the operating system. These change the look, and behavior of Qt applications, and make them more suitable for e.g. touchscreen devices.</p> <p>Qt6 is the new Qt version, so the various plugins needed a migration to this new version.</p> <ul class="simple"> <li>Each had their qmake converted to CMake, in order for better integration with existing IDEs</li> <li>Each are now separate repositories to make development more focussed, and accessible</li> <li>Each now have a Qt GUI example application - handy for testing any changes made to the plugin in question</li> </ul> <p>We are happy to report Qt6 applications now also integrate into Maemo, just like our Qt5 applications do.</p> <div class="section" id="qt6-input-maemo"> <h4>qt6-input-maemo</h4> <p>This the keyboard integration, including the virtual keyboard. Since our Qt5 version was already using modern Qt (having been ported from Qt4 only recently), minimal changes where needed to get this working on Qt6, see <a class="reference external" href="https://git.maemo.org/leste/qt6-input-maemo">qt6-input-maemo</a>.</p> </div> <div class="section" id="qt6-qpa-maemo"> <h4>qt6-qpa-maemo</h4> <p>This plugin is responsible for integrating with xcb/x11, and offers glx (opengl) and egl (opengles) backends for hardware acceleration. It also deals with things like drag &amp; drop, and clipboard. Porting this was somewhat challenging due to Qt plugin infrastructure changes, as well as debugging hardware acceleration on the various devices we support, see <a class="reference external" href="https://git.maemo.org/leste/qt6-qpa-maemo/">qt6-qpa-maemo</a>.</p> </div> <div class="section" id="qt6-maemo-widgets"> <h4>qt6-maemo-widgets</h4> <p>This plugin provides additional Maemo components (widgets) for Qt, like <cite>QMaemo5InformationBox</cite>, <cite>QMaemo5DatePickSelector</cite>, see <a class="reference external" href="https://git.maemo.org/leste/qt6-maemo-widgets">qt6-maemo-widgets</a>.</p> <p>Previously part of the plugin, this is now a shared library that produces a pkgconfig, and CMake config for other Qt apps to consume.</p> </div> <div class="section" id="qt6-style-maemo"> <h4>qt6-style-maemo</h4> <p>This plugin deals with how Qt applications look. For example, when this plugin is active, a <cite>QButton</cite> is replaced by a GTK button at runtime. It does so by painting GTK widgets off screen and use that to figure out what the Qt widgets should look like. This plugin also handles spacing, size hints, and color palettes. Due to Qt plugin infrastructure changes, this was somewhat time consuming to migrate, see <a class="reference external" href="https://git.maemo.org/leste/qt6-style-maemo/">qt6-style-maemo</a>.</p> </div> </div> <div class="section" id="sphone"> <h3>sphone</h3> <p>Our dialer software has also seen some improvements:</p> <ul class="simple"> <li>The default ringtones are now ogg files (<a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/767">issue #767</a>)</li> <li>There is a more clear indication when a call has ended (<a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/727">issue #727</a></li> </ul> </div> <div class="section" id="osso-xterm"> <h3>osso-xterm</h3> <p><tt class="docutils literal">thp</tt> contributed a bunch of changes to the terminal application:</p> <p><a class="reference external" href="https://git.maemo.org/leste/osso-xterm/pulls/5">osso-xterm/pulls/5</a> tidies up the preference UI. As mentioned in the pull request:</p> <ul class="simple"> <li>Preview prominently visible at the top</li> <li>Font selection hidden behind a button/dialog</li> <li>Color scheme presets (Black-on-white, White-on-black, ...)</li> <li>Custom color scheme with working preview buttons</li> <li>Use color picker from Hildon Extras</li> <li>Remove &quot;Reverse&quot; option (it just swaps fg/bg color)</li> <li>Make scrollback a picker instead of a text field</li> <li>Make it clearer what the hardware keys option does</li> </ul> <p><a class="reference external" href="https://git.maemo.org/leste/osso-xterm/pulls/6">osso-xterm/pulls/6</a> removes some obsolete code and <a class="reference external" href="https://git.maemo.org/leste/osso-xterm/pulls/7shlibdepsusage">osso-xterm/pulls/7</a> fixes a typo in the debian control file.</p> <p><a class="reference external" href="https://git.maemo.org/leste/osso-xterm/pulls/8">osso-xterm/pulls/8</a> re-organises the toolbar buttons and moves the fullscreen button all the way to the right, which is more consistent with other Maemo applications.</p> <p><a class="reference external" href="https://git.maemo.org/leste/osso-xterm/pulls/9">osso-xterm/pulls/9</a> fixes behaviour where menu buttons would sometimes move around, by placing the &quot;Copy&quot; and &quot;Paste&quot; buttons after the &quot;Reset&quot; and &quot;Reset and Clear&quot; buttons.</p> </div> <div class="section" id="connui-cellular"> <h3>connui-cellular</h3> <p>We have made it such that the icons for 2.5G and 3.5G now show up correctly, see <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/745">issue 745</a> and <a class="reference external" href="https://git.maemo.org/leste/connui-cellular/pulls/3">connui-cellular/pulls/3</a>.</p> </div> <div class="section" id="hildon-input-method"> <h3>hildon input method</h3> <p>User <tt class="docutils literal">thp</tt> has improving the settings for the hildon input method in <a class="reference external" href="https://git.maemo.org/leste/hildon-input-method-plugins/pulls/5">hildon-input-method-plugins/pulls/5</a> by making it possible to configure the hardware key long press action: so that one can either have keys repeat or change the key to the special symbol of said key.</p> <div class="section" id="theming-for-programs-started-over-ssh"> <h4>Theming for programs started over ssh</h4> <p>In <a class="reference external" href="https://git.maemo.org/leste/osso-af-startup/issues/3">osso-af-startup/issues/3</a> user <tt class="docutils literal">thp</tt> documented why the theming did not work well when starting programs over <tt class="docutils literal">ssh</tt>, and this has now been fixed.</p> </div> </div> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>The Nokia N900 has seen a fair number of changes:</p> <ul class="simple"> <li>the proximity sensor is now exposed over IIO, see <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/134">issue #134</a> and <a class="reference external" href="https://git.maemo.org/leste/hildon-meta-core/pulls/1">hildon-meta-core/pulls/1</a></li> <li>The headset microphone has been added in the HiFi profile, see <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/51">leste-config/pulls/51</a></li> <li>The module blacklist has been updated, see <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/58">leste-config/pulls/58</a></li> <li>The wifi mac address is now properly read from libcal, see <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/56">leste-config/pulls/56</a> and <a class="reference external" href="https://git.maemo.org/leste/wl1251-cal/pulls/1">wl1251-cal/pulls/1</a></li> </ul> </div> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>The mapphones (Motorola Droid 4, Motorola Bionic, Motorola Droid RAZR, Motorola Droid 3, Motorola Atrix 2, various xoom/xyboard tablets), received significant improvements. In particular, the cellular stack (in the form of ofono) has seen various improvements, improving the stability of the cellular stack and reducing the amount of custom code by <a class="reference external" href="https://git.maemo.org/leste-upstream-forks/ofono/commit/058db24b7201ce7f087d5c4ea38937d28d52c999">migrating to QMI from custom AT commands</a> and moving to ofono 2.12.</p> <p>In <a class="reference external" href="https://git.maemo.org/leste-upstream-forks/droid4-linux/pulls/12">droid4-linux/pulls/12</a> and <a class="reference external" href="https://git.maemo.org/leste-upstream-forks/droid4-linux/pulls/13">droid4-linux/pulls/13</a> <tt class="docutils literal">uvos</tt> and <tt class="docutils literal">sicelo</tt> improved the bq2415x charger event reporting from the kernel to userspace.</p> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>Display brightness now correctly adjusts according to the user setting. Previously, devices with large ranges of brightness values (like the Pinephone) did not quite work well with our existing brightness adjusting logic.</p> <p>We're also working on updating our pinephone kernel to a more recent version with better support, performance and power management user <tt class="docutils literal">norayr</tt> has been working on this.</p> </div> <div class="section" id="mz617-tablet"> <h3>MZ617 tablet</h3> <p>The Motorola MZ617 tablet also saw improvements to its audio in <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/54">leste-config/pulls/54</a> and <a class="reference external" href="https://git.maemo.org/leste/leste-config/pulls/55">leste-config/pulls/55</a>.</p> </div> </div> <div class="section" id="extras"> <h2>Extras</h2> <div class="section" id="hamsterfiler"> <h3>hamsterfiler</h3> <p>Hamsterfiler, a file browser, now adjusts to varying resolutions, making the interface more responsive.</p> <img alt="" src="/images/hamsterfiler.png" style="width: 324px; height: 576px;" /> </div> <div class="section" id="crazyparking"> <h3>crazyparking</h3> <p><tt class="docutils literal">thp</tt> helped us bring crazyparking to Leste - a top-down puzzle game that challenges players to navigate interesting parking scenarios.</p> <img alt="" src="/images/parking.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="forgejo"> <h2>Forgejo</h2> <p>We <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-forgejo-migration.html">migrated away from Github to Forgejo</a> and now run our own Git forge on <tt class="docutils literal">git.maemo.org</tt>. This in turn has made it easier for us customise our Git forge.</p> <div class="section" id="code-search"> <h3>Code search</h3> <p>Full text code search is enabled on <tt class="docutils literal">git.maemo.org</tt>, which makes it very easy to quickly search our entire codebase.</p> <p>We have been working with the Forgejo developers to add the option to enable and disable the code indexer per repository, as we want to avoid indexing our various Linux repositories, you can track this work on <a class="reference external" href="https://codeberg.org/forgejo/forgejo/pulls/8106">forgejo/pulls/8106</a>.</p> </div> <div class="section" id="translations-with-weblate"> <h3>Translations with weblate</h3> <p>Pushing updates from weblate to our <tt class="docutils literal">l10n</tt> repositories was broken after the migration from Forgejo to Github - this has now been resolved with translations being pushed directly to our <tt class="docutils literal"><span class="pre">git.maemo.org/leste-translations</span></tt> repositories.</p> </div> <div class="section" id="continous-integration"> <h3>Continous integration</h3> <p>Historically Maemo Leste has used Jenkins for all its package building, which has been a bit complex to manage permissions on and add packages to. So we have been working on adding a CI system using Forgejo which allows us to automatically. The Forgejo CI system is similar to 'Github Actions', and we currently:</p> <ul class="simple"> <li>build a package for every commit that gets pushed;</li> <li>deploy extras packages to the <a class="reference external" href="https://git.maemo.org/leste-extras/-/packages">extras-testing</a> repository on Forgejo. This repository is present on the devices but disabled by default.</li> </ul> <p>As a result, community members can now push out updates of their own software more easily - and even automatically to the <a class="reference external" href="https://git.maemo.org/leste-extras/-/packages">extras-testing</a> repository. The <a class="reference external" href="https://git.maemo.org/leste-extras/-/packages">extras-testing</a> repository is available in the Hildon Application Manager, but disabled by default.</p> <p>We have set up runners for <tt class="docutils literal">amd64</tt>, <tt class="docutils literal">armhf</tt> and <tt class="docutils literal">arm64</tt>, so these runners are all available to the CI/CD. Below is an example page of actions ran on the <tt class="docutils literal">maemo/daedalus</tt> branch, which will build packages automatically for the daedalus testing repository.</p> <img alt="" src="/images/actions.png" /> <p>The screenshot below shows the build status of various packages on the <a class="reference external" href="https://git.maemo.org/org/leste-extras/dashboard">Forgejo extras dashboard</a>.</p> <img alt="" src="/images/issue-897-screenshot.png" /> <div class="section" id="workflows"> <h4>Workflows</h4> <p>The CI mentioned just above is powered by our newly developed <a class="reference external" href="https://git.maemo.org/leste-cicd/forgejo-workflows">leste-cicd/forgejo-workflows</a> repository, which contains two actions:</p> <ul class="simple"> <li><a class="reference external" href="https://git.maemo.org/leste-cicd/forgejo-workflows/src/branch/master/.forgejo/workflows/maemo-entry.yml">maemo-entry.yml</a>: a resuable action which builds a package for each architecture and uploads them if they are in <tt class="docutils literal"><span class="pre">leste-extras</span></tt></li> <li><a class="reference external" href="https://git.maemo.org/leste-cicd/forgejo-workflows/src/branch/master/maemo-build/action.yml">maemo-build/action.yml</a>: composite action that builds a package</li> </ul> <p>The uploading of the packages into our Forgejo extras debian registry is done using our custom <a class="reference external" href="https://git.maemo.org/leste-cicd/include-artifact">leste-cicd/include-artifact</a> action.</p> <p>Further details on the extras workflow can be found in <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/798">issue #798</a>.</p> </div> <div class="section" id="container-base-images"> <h4>Container base images</h4> <p>Forgejo actions typically suggest using a specific runner, which come preinstalled with Node.js and a bunch of other programs. We opted instead to build our own base devuan images with our <a class="reference external" href="https://git.maemo.org/leste-cicd/devuan-base-containers">leste-cicd/devuan-base-containers</a> repository. We've built images for <tt class="docutils literal">chimaera</tt>, <tt class="docutils literal">daedalus</tt> and the freshly released <tt class="docutils literal">excalibur</tt> release.</p> <img alt="" src="/images/leste-cicd-container-registry.png" /> <p>Certain Forgejo actions normally require Node.js, but we decided not to leverage that and instead using a Forgejo action written in shell, see <a class="reference external" href="https://git.maemo.org/leste-cicd/checkout-action-nojs">leste-cicd/checkout-action-nojs</a> (forked from <a class="reference external" href="https://github.com/taiki-e/checkout-action">taiki-e/checkout-action</a>.</p> <p>We created a custom action that uploads artifacts without requiring Node.js in this repository: <a class="reference external" href="https://git.maemo.org/leste-cicd/upload-artifact-nojs">leste-cicd/upload-artifact-nojs</a>.</p> </div> <div class="section" id="future-work"> <h4>Future work</h4> <p>We will continue to develop our CI/CD system to make it easier to contribute to Maemo Leste. In particular, we're looking to:</p> <ul class="simple"> <li>ensure that our CI/CD deals better with packages that are meant only to be built for a specific architecture</li> <li>contribute to Forgejo to make it easier for other projects to set up similar CI/CD setups</li> <li>ensure our CI/CD build-on-commit coverage extends to all our core packages</li> <li>we can build device images in our CI/CD as opposed to in Jenkins by leveraging debos</li> <li>Provide better integration with our Weblate translation setup</li> </ul> </div> </div> <div class="section" id="bugtracker-issues"> <h3>Bugtracker / issues</h3> <p><tt class="docutils literal">Sander</tt> utilised a <a class="reference external" href="https://git.maemo.org/sanderfoobar/LesteIssueLabels#mass-label-leste-bugtracker-issues">local LLM</a> to tag all of the issues in our bugtracker.</p> </div> </div> <div class="section" id="website-redesign"> <h2>Website redesign</h2> <p>Our website has a fresh new look. The homepage is now clean, concise, and clearly communicates our mission: provide a FOSS Linux distribution for mobile devices.</p> <p>We've kept it lightweight, no fancy CMS, no cookies, just statically generated content.</p> <p>See <a class="reference external" href="https://git.maemo.org/leste/maemo-leste.github.io/pulls/23">maemo-leste.github.io/pulls/23</a></p> </div> <div class="section" id="image-building"> <h2>Image building</h2> <div class="section" id="debos"> <h3>Debos</h3> <p>We're looking to modernise our image building process to make it easier to port Maemo Leste to other devices. <tt class="docutils literal">erebion</tt> has made a start on utiling the debos recipies as used to Mobian and adopting them for Maemo. We've been building on his work and almost have bootable images for the Droid 4, which would be a great milestone. The current changeset can be found in <a class="reference external" href="https://git.maemo.org/MerlijnWajer/mobian-recipes">MerlijnWajer/mobian-recipes</a></p> </div> <div class="section" id="raspberry-pi-images"> <h3>Raspberry Pi images</h3> <p>We're working in getting the Raspberry Pi images to build again. Currently minor manual modifications are required to get the latest raspberry images to boot, as documented in <a class="reference external" href="https://git.maemo.org/leste/bugtracker/issues/758">issue #758</a></p> </div> </div> <div class="section" id="what-s-next"> <h2>What's next</h2> <p>Devuan recently released their version of Debian Trixie coined <a class="reference external" href="https://www.devuan.org/os/announce/excalibur-release-announce-2025-11-02">Excalibur</a> and we are looking to rebase Maemo Leste onto this release soon. Moving to Excalibur will probably mean we will move to Qt6 and towards Pipewire - away from Pulseaudio.</p> <p>Adding support for more devices is something we're also aiming to do soon - both in terms of developer single board computers (like the Raspberry Pi and Olimex OLinuXino devices) as well as actual phones and tablets. The developer single board computers will make it easier for folks to develop and contribute (phones do not always make for nice development devices)</p> <p>We're also looking to seriously improve our developer documentation - how to port and/or contribute packages, how to port Maemo Leste to new devices, how to debug problems and so forth.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join our effort!</p> </div> 2025-07-29T00:00:00+02:002025-07-29T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2025-07-29:/a-deep-dive-into-building-maemo-leste-packages-on-forgejo.html

<p>labels = for arch and default images jobs.*.container.image = for chimaera/daedalus/excalibur, etc</p> <p>misschien is er met strategy en matrix nog iets te doen</p> <p>01:35 &lt;Wizzup&gt; ik denk dat we idd wel onze eigen docker registry willen uiteindelijk 01:40 &lt;Wizzup&gt; om een paar redenen: 01:41 &lt;Wizzup …</p>

<p>labels = for arch and default images jobs.*.container.image = for chimaera/daedalus/excalibur, etc</p> <p>misschien is er met strategy en matrix nog iets te doen</p> <p>01:35 &lt;Wizzup&gt; ik denk dat we idd wel onze eigen docker registry willen uiteindelijk 01:40 &lt;Wizzup&gt; om een paar redenen: 01:41 &lt;Wizzup&gt; we willen armhf, arm64 en amd64 images die allemaal hetzelfde hebben 01:41 &lt;Wizzup&gt; we willen images die onze repos er ook in hebben 01:41 &lt;Wizzup&gt; we willen images die ook onze verschillende cpu flags en andere flags aan hebben</p> <p>git clone <a class="reference external" href="https://code.forgejo.org/forgejo/runner">https://code.forgejo.org/forgejo/runner</a> GOOS=linux GOARCH=arm make</p> <dl class="docutils"> <dt>Idee:</dt> <dd><p class="first">Forgejo experimental repository, die ook onze stable en devel repository pulled, en dan kunnen we met een tooltje forgejo pkgs importeren in onze main repo. Moeten we alleen de versie selection fixen, maar dat kan best redelijk gedaan worden volgens mij.</p> <p class="last"><a class="reference external" href="https://forgejo.org/docs/v1.20/user/packages/debian/">https://forgejo.org/docs/v1.20/user/packages/debian/</a></p> </dd> </dl> <p><a class="reference external" href="https://git.maemo.org/leste-cicd/-/packages">https://git.maemo.org/leste-cicd/-/packages</a></p> <p>Docker base images:</p> <blockquote> <p><a class="reference external" href="https://git.devuan.org/paddy-hack/container-images">https://git.devuan.org/paddy-hack/container-images</a> <a class="reference external" href="https://docs.docker.com/build/building/base-images/#create-a-full-image-using-tar">https://docs.docker.com/build/building/base-images/#create-a-full-image-using-tar</a> <a class="reference external" href="https://forgejo.org/docs/latest/user/packages/container/">https://forgejo.org/docs/latest/user/packages/container/</a></p> <p>SEE <a class="reference external" href="https://git.maemo.org/leste-cicd/devuan-base-containers">https://git.maemo.org/leste-cicd/devuan-base-containers</a> FOR DEBOOTSTRAP AND DOCKER</p> <p>RESULT: <a class="reference external" href="https://git.maemo.org/leste-cicd/-/packages">https://git.maemo.org/leste-cicd/-/packages</a></p> <p>En dan hebben we een base-base, die kunnen we dan aanpassen met onze changes in een Dockerfile: * dpkg-buildflags * onze repos * onze repo key * etc</p> <ul class="simple"> <li>en die dan gebruiken voor bouwen</li> </ul> </blockquote> <dl class="docutils"> <dt>Secrets management:</dt> <dd><a class="reference external" href="https://forgejo.org/docs/v1.21/user/actions/#secrets">https://forgejo.org/docs/v1.21/user/actions/#secrets</a></dd> </dl> <p><a class="reference external" href="https://forgejo.org/docs/latest/user/packages/debian/#configuring-the-package-registry">https://forgejo.org/docs/latest/user/packages/debian/#configuring-the-package-registry</a> <a class="reference external" href="https://forgejo.org/docs/latest/user/packages/debian/#configuring-the-package-registry">https://forgejo.org/docs/latest/user/packages/debian/#configuring-the-package-registry</a></p> <dl class="docutils"> <dt>Forgejo issues:</dt> <dd><a class="reference external" href="https://codeberg.org/forgejo/forgejo/issues/8780">https://codeberg.org/forgejo/forgejo/issues/8780</a></dd> </dl> <p>Does not need node (yay)</p> <blockquote> <p><a class="reference external" href="https://github.com/taiki-e/checkout-action">https://github.com/taiki-e/checkout-action</a></p> <p><a class="reference external" href="https://git.maemo.org/MerlijnWajer/upload-artifact/">https://git.maemo.org/MerlijnWajer/upload-artifact/</a></p> </blockquote> <p><a class="reference external" href="https://git.maemo.org/leste-cicd/-/packages/container/daedalus-maemo-amd64/latest">https://git.maemo.org/leste-cicd/-/packages/container/daedalus-maemo-amd64/latest</a></p> <p><a class="reference external" href="https://git.maemo.org/leste-extras/-/packages">https://git.maemo.org/leste-extras/-/packages</a></p> <p><a class="reference external" href="https://wizzup.org/protected-branches.png">https://wizzup.org/protected-branches.png</a></p> <p><a class="reference external" href="https://git.maemo.org/org/leste-extras/teams/extras-team">https://git.maemo.org/org/leste-extras/teams/extras-team</a></p> <p>Template repos <a class="reference external" href="https://git.maemo.org/leste-extras/template">https://git.maemo.org/leste-extras/template</a></p> <dl class="docutils"> <dt>TODO:</dt> <dd><p class="first">lowered polling rates in the runner</p> <p class="last">Maybe re-enable cache when we have versioned our composite actions</p> </dd> </dl> 2025-06-22T00:00:00+02:002025-06-22T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2025-06-22:/maemo-leste-forgejo-migration.html

<p>With the next release of Maemo Leste imminent, we have some additional information to share: we have moved all of our repositories from Github to Forgejo, self hosted on <a class="reference external" href="https://git.maemo.org">https://git.maemo.org</a>. Our website (<a class="reference external" href="https://maemo-leste.github.io">https://maemo-leste.github.io</a>) will remain hosted on Github for now.</p> <p>This article will discuss …</p>

<p>With the next release of Maemo Leste imminent, we have some additional information to share: we have moved all of our repositories from Github to Forgejo, self hosted on <a class="reference external" href="https://git.maemo.org">https://git.maemo.org</a>. Our website (<a class="reference external" href="https://maemo-leste.github.io">https://maemo-leste.github.io</a>) will remain hosted on Github for now.</p> <p>This article will discuss the changes and the motivations that lead to this migration.</p> <div class="section" id="github-values-and-forgejo"> <h2>Github, values and Forgejo</h2> <p>Maemo Leste as a project initially used Github for our code hosting. We chose to host our code there because we believed that the 'network effect' of Github would lower the barriers for contributions from outsiders.</p> <p>Since then, years have passed and we're not sure if this 'network effect' really is that visible and important to us. Github is not open source, not self-hostable and owned by big corporations - none of these points align with our values. Additionally, making backups of our project on Github is a bit of a pain.</p> <p>We don't know if we can rely on Github in the long term, so we have always kept backups of our project, but Github doesn't make this very easy.</p> <p>We've also been trying to switch from our <a class="reference external" href="https://phoenix.maemo.org">Jenkins instance</a> to something more modern - and Github actions aren't something we want to trust to build our software, for the same reason that we don't host most of our content on the cloud.</p> <p>So we set out to find an alternative and we ended up choosing Forgejo.</p> <div class="section" id="forgejo"> <h3>Forgejo</h3> <p>Forgejo offers just about everything that we want: it is open source and self hosted with minimal resource requirements. Their values and goals align with ours more so <a class="reference external" href="https://forgejo.org/compare/">than the alternatives</a>.</p> <p>Forgejo also has a great migration path with support for importing repositories from Github (including issues, milestones, open and closed pull requests) as well as an API that makes it easy to automate the tasks.</p> <p>Furthermore, we are planning to try out <a class="reference external" href="https://forgejo.org/docs/latest/user/actions/">Forgejo Actions</a> as an alternative method to build our packages and additionally offer continous integration services to our developers.</p> </div> <div class="section" id="status"> <h3>Status</h3> <p>Our instance is live at <a class="reference external" href="https://git.maemo.org">https://git.maemo.org</a></p> <p>We've currently migrated all our repositories from Github to Forgejo - and our Forgejo is set up to push an changes to Forgejo back to Github for the forseeable future.</p> <p>All our packages now pull in sources from our Forgejo rather than from Github.</p> <p>Account creation and login is facilitated by Oauth2 - allowing previous Github users to easily migrate. Accounts free from Github can also be requested, but public registration is disabled to limit the potential for abuse.</p> <p>Forgejo is also configured with full text code search and we're actively <a class="reference external" href="https://codeberg.org/forgejo/forgejo/pulls/8106">contributing to Forgejo</a> to further enhance this functionality.</p> <p>Weblate integration is still lacking, as we have not figured out how to use the hosted weblate instance to communicate directly with our Forgejo instance. We are working on addressing this. In the meantime we will not pull in new translations.</p> <p>Happy hacking!</p> </div> </div> 2024-08-27T00:00:00+02:002024-08-27T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2024-08-27:/maemo-leste-2024-telepathy-update.html

<p>It's been a good while since our last update, but not for the lack of changes - indeed, we've been busy bees. Some of the highlights:</p> <ul class="simple"> <li>Big communication (Telepathy) upgrade;</li> <li>Graphics rendering artifacts fixed on all mapphones;</li> <li>Much improved phone calls on several devices;</li> <li>Integration of Gnome Tracker and the Open …</li></ul>

<p>It's been a good while since our last update, but not for the lack of changes - indeed, we've been busy bees. Some of the highlights:</p> <ul class="simple"> <li>Big communication (Telepathy) upgrade;</li> <li>Graphics rendering artifacts fixed on all mapphones;</li> <li>Much improved phone calls on several devices;</li> <li>Integration of Gnome Tracker and the Open Media Player;</li> <li>Support for more devices;</li> <li>Improvements to our user guide and documentation;</li> <li>Significant changes to our browser (Jib);</li> </ul> <p>(Also check out our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-five-year-anniversary-and-chimaera-release.html">previous update</a> in case you missed it).</p> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <p>We have moved to a new Linux LTS release - 6.6.x and after fixing various regressions (no call audio at all, cpu frequency issues and other instabilities) are now in an even better spot when it comes to hardware support through the new features brought by this Linux release - in particular for call audio.</p> <div class="section" id="graphics"> <h3>Graphics</h3> <p>We have had minor rendering bugs on the mapphone phones (Droid 4, Droid Bionic, Droid Razr, etc) which were mostly prevalent in font rendering. This problem has been fixed in <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/9acc40b173ba4ede851f83f127e6e5c50306573b">leste-config version 1.103</a>!</p> <p>Additionally, we have improved the 16-bit mode of xf86-video-omap so that the xv video scaling works properly. This is helpful because the Nokia N900 uses 16 bit Xorg. We've also improved the <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/commit/4e5aead5403f4c9e594fc9c1e3b9ac5afae182ad">compositing</a> as well as <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/commit/92eb692c2d1f8b743b7b56c88616f0f2e41b822d">two</a> <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/commit/ace9cda2a22a4b032ff82cc6761485945fffd55c">other</a> stability fixes.</p> <p>hildon-desktop (the Maemo window manager) also has a 30% speed improvement in the application launcher by <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/commit/51b5a4b0cbe046bfc7cd5d4b028676344ad92bb8">calculating the saturation in the shader just once</a>.</p> </div> <div class="section" id="connectivity"> <h3>Connectivity</h3> <p>The cellular data code has improved, particularly in the provisioning (<a class="reference external" href="https://github.com/maemo-leste/libicd-network-ofono/commit/920429ada67a8ffe7a5384169a8a9ab3c28fa5a8">commit 920429ad</a> and <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ofono/commit/ffa7b91ce39fd9e35fbf8db715ff">commit ffa7b91c</a> which fix <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/555">issue #555</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/585">issue #585</a>), <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ofono/pull/1">handling a missing gateway</a> and <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ipv4/pull/7">moving the stack to use iproute2</a>.</p> <p><tt class="docutils literal"><span class="pre">libicd-network-wpasupplicant</span></tt> now properly updates the wireless signal strength with <a class="reference external" href="https://github.com/maemo-leste/libicd-network-wpasupplicant/pull/2">libicd-network-wpasupplicant pull request #2</a>.</p> <p>We have also packaged the latest wpa_supplicant version, which would allow using hostapd for mobile hotspots, but unfortunately this doesn't work currently with Linux 6.6, only with Linux 6.1.</p> </div> <div class="section" id="audio-and-call-audio"> <h3>Audio and Call Audio</h3> <p>The call audio has improved a bunch both for all the mapphones and the Nokia N900. We have also made some general audio improvements.</p> <p><a class="reference external" href="https://github.com/maemo-leste/maemo-audio/commit/ecbae1b12cfdfe10b3e144536a1294e534b266c1">Pulseaudio was switched to a user daemon</a> instead of a system daemon, as recommended by pulseaudio upstream.</p> <p>Regular audio would sometimes stop working after a phone call was made using the device, this has now been resolved by <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/1febfa7d6f7373150afad5785103734f99439ab4">reducing the shared memory of each pulseaudio connection</a>.</p> <p>On the mapphone devices the call audio has become a lot more stable by removing some of the hacks we've had in the kernel previously and using the new <tt class="docutils literal"><span class="pre">audio-graph-card2</span></tt> framework in the kernel, which allows defining audio routes in a way that we couldn't before. (The Droid 4 and other devices rely on cpcap to manage the audio routes and requires not active ALSA connection, and we could not express that before.). For more details check the following commits: <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/efca4073912c3051e495f3afe40225f74a0c2dc0">commit efca4073</a>, <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/21f8cb5ab78ece3abbfeeeb4ffcea028e9dc9dbe">commit 21f8cb5a</a>, <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/80b50f94a11a016d9d33a8280640de4297717602">commit 80b50f94</a>, <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/4246f219e152042d83fb008103904ebd827ec0cb">commit 4246f219</a>, <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/8a0687ee846b311d9aca2f0065d3a34750c0b3e2">commit 8a0687ee</a>.</p> <p>On the Nokia N900 side, voice calls were finally integrated, and call audio has also been incrementally improved thanks to work by <tt class="docutils literal">arno11</tt>, with <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/48">support for headsets</a>, <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/11f11dac690ee752900f144ecff809a8991d14c3">support for the earpiece</a>, which is connected on a completely separate part of the N900's codec, <a class="reference external" href="https://github.com/maemo-leste/libcmtspeechdata/pull/6">8000Hz audio</a>, <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/39">better resampling</a> and <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/41">setting the proper group for the cmt_speech node</a>. In addition, further N900 call quality audio improvements were made to libcmtspeechdata in <a class="reference external" href="https://github.com/maemo-leste/libcmtspeechdata/pull/1">libcmtspeechdata PR #1</a>, <a class="reference external" href="https://github.com/maemo-leste/libcmtspeechdata/pull/2">libcmtspeechdata PR #2</a>, <a class="reference external" href="https://github.com/maemo-leste/libcmtspeechdata/pull/4">libcmtspeechdata PR #4</a> and <a class="reference external" href="https://github.com/maemo-leste/libcmtspeechdata/pull/5">libcmtspeechdata PR #5</a>.</p> </div> <div class="section" id="miscellaneous-updates"> <h3>Miscellaneous updates</h3> <p>After moving to Linux 6.6, the cpu frequency options disappeared. We traced it down to a regression which we have reported upstream and temporarily worked around by making the <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/20d360a9da5a5450117ca9bcae436352c1e81bd6">cpufreq device tree platform device built in</a> (as opposed to a kernel module).</p> <p>Maemo Fremantle supported the feature where you could silence audible notifications such as incoming calls, or alarms, by turning the device face-down. This feature is now supported in Maemo Leste as well, through <a class="reference external" href="https://github.com/maemo-leste/mce/pull/61">https://github.com/maemo-leste/mce/pull/61</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/62">https://github.com/maemo-leste/mce/pull/62</a>, and <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/iio-sensor-proxy/pull/2">https://github.com/maemo-leste-upstream-forks/iio-sensor-proxy/pull/2</a>. The face-down reporting feature has also been submitted to upstream <tt class="docutils literal"><span class="pre">iio-sensor-proxy</span></tt> and could be used for other Linux mobile distros in future.</p> </div> </div> <div class="section" id="devices"> <h2>Devices</h2> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>We have been working hard on improving the performance on the Nokia N900 and <tt class="docutils literal">sicelo</tt> and <tt class="docutils literal">arno11</tt> in particular have contributed many fixes.</p> <p>The N900 now runs in <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/44">16bit Xorg mode</a> to improve the performance of the X server. <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/pull/6">Turbo mode and overclock frequencies</a> have been added as well, allowing for a much more smooth experience. We're still trying to find the best scheduler, as the default ondemand scheduler doesn't perform particularly well when it comes to having a responsive device.</p> <p>We've also been toying with <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/50">tweaking the default hildon transitions file</a> which controls what the window manager transitions look like, which effects are used and so on. In particular we're trying to see what the best settings will be for a responsive device. In the process we've also been further improving the performance of hildon-desktop.</p> <p><tt class="docutils literal">sicelo</tt> has added support for Nokia N900's ofono to fetch <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/ofono/pull/4">extra details about the operator</a>, such as the name. He has also fixed the issue where the N900 battery icon never hit the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/167">fully charged state</a>, which affects both the status icon as well as the LED behaviour. This is now fixed in mce and our kernel in <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/pull/9/commits">droid4-linux PR #9</a>, and are already upstreamed to mainline linux.</p> <p><tt class="docutils literal">sicelo</tt> has also fixed a potential crash in <a class="reference external" href="https://github.com/maemo-leste/gps-nokia-n900/pull/1">gps-nokia-n900 PR #1</a> and also ensured that the GPS date is correct since the epoch rollover in 2019 in <a class="reference external" href="https://github.com/maemo-leste/gps-nokia-n900/pull/2">gps-nokia-n900 PR #2</a>.</p> <p>Furthermore, <tt class="docutils literal">sicelo</tt> has also added support for the <a class="reference external" href="https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/375">N900 'switch-type' proximity sensor in iio-sensor-proxy</a>. To top it off, he has also corrected the accelerometer orientation to correctly report face up and face down in <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/pull/11">droid-linux PR #4</a>.</p> <p><tt class="docutils literal">arno11</tt> and <tt class="docutils literal">freemangordon</tt> have also been working on infra red support, have been ensuring that the Linux kernel wide is working and reportedly have the <a class="reference external" href="https://github.com/maemo-leste-extras/pierogi">pierogi GUI</a> working on the N900. The necessary patches will have landed in Linux 6.8, so when we move to the next Linux LTS kernel we will have working infra red.</p> <p>We've also ensured that the microphone works for regular (non-call) audio in <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/51">leste-config PR #51</a>.</p> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>We ensured that the earpiece in calls isn't too loud in <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/37">leste-config PR #37</a>. Otherwise, there haven't been that many updates to the Pinephone this time around -- but it works well for phone calls and SMS, runs pretty stable and is fun to use with the physical keyboard.</p> </div> <div class="section" id="mapphones"> <h3>Mapphones</h3> <p>Most of the improvements to the mapphones have been in the form of making the audio calls work better and fixing the graphical glitches as well as by adding new mapphone devices. One other change however is fixing the 'hidden caller id' feature being inverted (so when one would request to be hidden it wouldn't be, and vice versa) - this was solved in <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/ofono/pull/2">maemo-leste-upstream-forks/ofono PR #12</a>.</p> </div> <div class="section" id="new-devices"> <h3>New devices</h3> <p>We have added images for a lot of new devices, the Motorola <em>RAZR XT910 and XT912</em>, the Motorola <em>Atrix 2</em> and the XYBoard <em>MZ609/MZ617</em> <strong>tablet</strong>.</p> <div class="section" id="razr-xt910-xt912"> <h4>RAZR XT910 / XT912</h4> <p>We now support the Motorola RAZR XT910 and XT912. Most features should just work and the battery life is pretty decent. There is still a screen corruption bug that we have to investigate.</p> <p>The relevant <a class="reference external" href="https://github.com/maemo-leste/arm-sdk/commit/ae9f3c25d269a1521c670373a3a6fd88cdb14f11">arm-sdk change</a> can be found here and the <a class="reference external" href="https://github.com/maemo-leste/hildon-meta/commit/00e744a25d8e2da0aafa81087a2d71561184233e">hildon-meta change</a> can be found here. The kernel changes are more complicated and spread out over several commits, so we would encourage interested users to look directly at our <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/tree/maemo-6.6.y">maemo-6.6.y Linux branch</a>.</p> <p>Download the <a class="reference external" href="https://maedevu.maemo.org/images/xt912/">XT912 images</a> and <a class="reference external" href="https://maedevu.maemo.org/images/xt910/">XT910 images</a> now and give it a try if you own a device!</p> </div> <div class="section" id="droid-3"> <h4>Droid 3</h4> <p><a class="reference external" href="https://maedevu.maemo.org/images/droid3/">Droid 3 images</a> are now available. See the <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_3">Droid 3 wiki page</a> for more information. There seems to be some instability when the GPU is clocked too high, so we're looking into lowering the GPU clock speed and voltage to see if that will get rid of the instability problems.</p> <p>The <tt class="docutils literal">solana</tt> branch of <a class="reference external" href="https://github.com/MerlijnWajer/bionic-clown-boot">this bionic-clown-boot fork</a> works for the Droid 3.</p> </div> <div class="section" id="atrix-2"> <h4>Atrix 2</h4> <p><a class="reference external" href="https://maedevu.maemo.org/images/bionic/">Atrix 2 images</a> are now available in the form of Bionic images - there is a lot of overlap between the two phones which means that these images should mostly just work.</p> <p>The Atrix 2 seems to be the AT&amp;T version of the Bionic (which used the Verizon network). The modem seems to be on SPI instead of USB, which provides additional challenges.</p> <p>We will provide more specialised images (and a wiki page with instructions) in the near future. Make sure to downgrade to this <a class="reference external" href="https://maedevu.maemo.org/images/atrix2/">Android (InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip) release</a> before flashing bionic-clown-boot, and change the installation script to store the installation not on the <tt class="docutils literal">/sdcard</tt> but on <tt class="docutils literal">/data/clown</tt> (and create said directory). If you're worried you might make a mistake - just wait for the wiki page to surface in the coming weeks!</p> <img alt="" src="/images/atrix2-1.jpg" style="width: 666px; height: 375px;" /> <img alt="" src="/images/atrix2-2.jpg" style="width: 666px; height: 375px;" /> </div> <div class="section" id="xyboard-tablets"> <h4>xyboard tablets</h4> <p>One of the more exciting device ports is the MZ608/MZ609/MZ615/MZ616/MZ617 (or just commonly known as xoom2/xyboard tablets) port. Most of these tablets do not come with a micro SD card slot, which posed some additional challenges to us, since most of our device installs have always been to (micro) SD cards.</p> <p>The xyboard tablets come in different variants with either 16GB of storage of 32GB of storage. However, there is no way to flash Maemo Leste directly to the data partition, so one has to install the right version of the droid4-kexecboot and then flash the special <strong>mz617-tiny-bootstrap</strong> image to a flashable partition (like <tt class="docutils literal">cdrom</tt>) which will then boot to a minimal Maemo. Using this minimal Maemo, one can then flash (using rsync) the Leste image root partition to the /data/ partition. The process is rather involved, but a wiki page will follow this news announcement in the coming weeks with detailed installation instructions.</p> <p>The tiny image was created specifically for the xyboard tablet and this required quite some changes. We introduced a new meta package called <a class="reference external" href="https://github.com/maemo-leste/hildon-meta/commit/657045b6d5e5a50c7566dd6232663a9ca5c1163e">hildon-meta-core</a> which contained only the bare minimal required for Maemo Leste to function. We then <a class="reference external" href="https://github.com/maemo-leste/hildon-meta/commit/f49d49bdcbd8b2ac46c341a0039597d799e76a9f">trimmed it some more</a> to further reduce the required disk space.</p> <p>Then we added a special flag to the image-builder to <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/566a74d48b6fb19c9545322f4052072428022f76">build tiny images</a> which will remove manual pages and other unnecessary files that are hard to prune otherwise and set <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/34a747a1b55631403b66a3f538601f6b89b5909c">only one locale</a>. The end result is that we end up with an image that is about ~700MB, which fits in one of the smaller but flashable partitions of Android on the xyboards.</p> <p>We, of course, also <a class="reference external" href="https://github.com/maemo-leste/hildon-meta/commit/10123d888eac654e6374f45b04accc383e942a98">added a meta package</a>.</p> <p>It is worth noting that if one <strong>bricks the MZ617</strong> it will be very hard to recover, since we have not been able to find the right files that allow us to flash all partitions - so beware.</p> <p>In general, the device port works well - it is really fun to run Maemo on a real tablet. There are still improvements to be made to the power management as the device does not idle correctly yet. Once the device idles correctly we believe we should get multiple-days uptime without problems.</p> <img alt="" src="/images/xyboard-1.jpg" style="width: 666px; height: 375px;" /> <img alt="" src="/images/xyboard-2.jpg" style="width: 666px; height: 375px;" /> <img alt="" src="/images/xyboard-3.jpg" style="width: 666px; height: 375px;" /> <img alt="" src="/images/xyboard-4.jpg" style="width: 666px; height: 375px;" /> </div> <div class="section" id="librem5"> <h4>Librem5</h4> <p><tt class="docutils literal">sicelo</tt> has been working on making Maemo Leste run on the Librem5 and has shared an initial photo with us:</p> <img alt="" src="/images/librem-initial.jpg" style="width: 500px; height: 375px;" /> <p>More to come later!</p> </div> </div> </div> <div class="section" id="telepathy-communications"> <h2>Telepathy &amp; Communications</h2> <p>The biggest update this time around is to our Telepathy-based communication stack with the addition of various features and protocols. We currently support the following protocols to varying degrees: XMPP, Matrix, SIP, IRC, Telegram, Facebook, Slack and Discord. Most of these protocols also have a corresponding accounts plugin to configure them.</p> <img alt="" src="/images/ham-accounts.png" style="width: 576px; height: 324px;" /> <p>And the different accounts can be used to group contacts in the Contacts application:</p> <img alt="" src="/images/osso-abook-groups.png" style="width: 576px; height: 324px;" /> <p>An overview of some of the currently online accounts:</p> <img alt="" src="/images/accounts-slack-matrix-telegram.png" style="width: 576px; height: 324px;" /> <div class="section" id="telepathy-haze-pidgin-libpurple"> <h3>telepathy-haze (pidgin/libpurple)</h3> <p>The telepathy-haze connection manager can load Pidgin/libpurple plugins, which allows us to use Pidgin plugins from Maemo Leste's contacts and conversations applications. This thus allows us to use libpurple plugins for which no 'native' telepathy connection managers exist.</p> <p>Until recently telepathy-haze lacked support for channels/rooms, which means only 1:1 messages worked. <tt class="docutils literal">freemangordon</tt> has added support in <a class="reference external" href="https://gitlab.freedesktop.org/telepathy/telepathy-haze/-/merge_requests/4/">telepathy-haze MR #4</a>. The work has not yet been merged, but we have deployed it to Maemo Leste in <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/telepathy-haze">maemo-leste-upstream-forks/telepathy-haze</a>, and we are in contact with the Telepathy maintainers to see if we can get the work merged.</p> <div class="section" id="slack"> <h4>slack</h4> <p>We have basic integration for Slack now. You can log in with your Slack account, chat through direct message as well as channels, your contacts on Slack will show up in the Contacts application (including photos), you can start a message session with them from there as well. History fetching does not work (yet).</p> <p>We have created a <a class="reference external" href="https://github.com/maemo-leste-extras/rtcom-accounts-plugin-slack">UI to set up your Slack account</a> and we have packaged the <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/slack-libpurple">libpurple Slack plugin</a>. We also added <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/slack-libpurple/commit/49e4fc3abd66b97fe889565f204e465cb478a495">support for buddy icons</a>.</p> <img alt="" src="/images/osso-abook-groups-slack-contacts.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/accounts-slack-rtcom-plugin.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="facebook"> <h4>facebook</h4> <p><tt class="docutils literal">freemangordon</tt> has been working on getting a plugin working for facebook, it uses <a class="reference external" href="https://github.com/maemo-leste-extras/purple-facebook">purple-facebook</a> through <a class="reference internal" href="#telepathy-haze-pidgin-libpurple">telepathy-haze (pidgin/libpurple)</a> and there is a <a class="reference external" href="https://github.com/maemo-leste-extras/rtcom-accounts-plugin-facebook">UI to configure the FB account</a>.</p> <p>Getting this to work required some additional work on <a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-ui/commit/9284bfa96b65b0a74283fc645d9e38969cd3213d">rtcom-accounts-ui</a>, but things otherwise reportedly have been working well.</p> </div> <div class="section" id="telegram"> <h4>telegram</h4> <p><tt class="docutils literal">Wizzup</tt> got Telegram working using <a class="reference internal" href="#telepathy-haze-pidgin-libpurple">telepathy-haze (pidgin/libpurple)</a>, although the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/716">setup instructions are currently somewhat involved</a>. The <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/tdlib-purple">tdlib-purple</a> is being used and there is a UI to manage the account called <a class="reference external" href="https://github.com/maemo-leste-extras/rtcom-accounts-plugin-telegram">rtcom-accounts-plugin-telegram</a>.</p> <p>However, after the account has been setup, the integration works quite well and will fetch new messages for the device upon connecting and has working address book integration.</p> <p>List of Telegram contacts with avatars:</p> <img alt="" src="/images/osso-abook-groups-telegram-contacts.png" style="width: 576px; height: 324px;" /> <p>Account configuration UI:</p> <img alt="" src="/images/accounts-telegram-rtcom-plugin.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="discord"> <h4>discord</h4> <p><tt class="docutils literal">Wizzup</tt> also got the <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/purple-discord">purple-discord</a> plugin working for Discord, and there is a UI to configure it called <a class="reference external" href="https://github.com/maemo-leste-extras/rtcom-accounts-plugin-discord">rtcom-accounts-plugin-discord</a>. Basic chats seem to work, but Discord's additional IP-based protections make using it still a little difficult: one needs to log into the web version of discord on the same IP, and then logging in will work.</p> </div> </div> <div class="section" id="telepathy-tank-matrix"> <h3>telepathy-tank (Matrix)</h3> <p><tt class="docutils literal">Sander</tt> worked on improving the <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/telepathy-tank">telepathy-tank</a> Matrix connection manager, which uses <a class="reference external" href="https://github.com/quotient-im/libQuotient">libQuotient</a>.</p> <p>The following has been added:</p> <ul class="simple"> <li>Support for creating, joining and leaving Matrix rooms (both 1:1 <em>and</em> groupchat)</li> <li>Detecting the room name and detecting if other devices leave the room</li> <li>Support for end to end encrypted chats (previously messages would just not be received at all)</li> </ul> <p>While these added features are stable, we are still working on getting the code tidied up and the changes upstreamed. For example, the Matrix contacts do not show up in the address book just yet - we're investigating why this would be the case, it might be a problem in our address book rather than in the Telepathy connection manager implementation.</p> <p>The code can be found in the <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/telepathy-tank/tree/groupchat-e2e">groupchat-e2e</a> branch.</p> <p>We have also created a <a class="reference external" href="https://github.com/maemo-leste-extras/rtcom-accounts-plugin-matrix/">UI to configure a Matrix account</a>, for which we had to make some changes to rtcom-accounts-ui <a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-ui/commit/0511c57cbac98d7d19b7dfe27549e834dfeefea3">to not treat the &#64; sign</a> as username/host separation and <a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-ui/commit/3f1f29fc95b113020c1e33fe3babdb462b753597">separate out the server name showing</a>.</p> <p>Below is a screenshot of a 1:1 E2EE chat within Conversations, via a recent version of <a class="reference external" href="https://github.com/quotient-im/libQuotient">libQuotient</a>. which uses <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/olm">libolm</a>.</p> <img alt="" src="/images/tank-conversations.png" style="width: 576px;" /> <p>And here is a group chat in action:</p> <img alt="" src="/images/conversations-matrix-groupchat.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="telepathy-rakia"> <h3>telepathy-rakia</h3> <p>Adding SIP accounts in Maemo is now possible using the provided account setup dialog <a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-plugins/commit/c545748d0b8862c6e1fb3a536418a0acced7f85f">added to the base rtcom-accounts-plugins</a>. which solves <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/657">issue #657</a>.</p> <p>Using such an account it is now possible to send SIP messages when supported and one can also receive and make SIP phone calls with working audio.</p> <img alt="" src="/images/osso-abook-sip-message-call.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="telepathy-ring"> <h3>telepathy-ring</h3> <p>telepathy-ring, the ofono (regular calls) connection manager has been added to our list of upstream forks to ensure that the right mission-control plugin gets installed, which in turns makes sure that the telepathy-ring account is online even when there is no internet (since cellular calls work fine without internet). This setting is controlled by the 'always_dispatch' bit in Telepathy, and it took us quite a while to figure out how this was supposed to work.</p> </div> <div class="section" id="conversations"> <h3>Conversations</h3> <p>Conversations has seen significant improvements since our last news update, amongst other things:</p> <ul class="simple"> <li>support for sending and receiving SMSes now that the <a class="reference external" href="https://github.com/maemo-leste/sphone/pull/4">sphone voicecall manager module was merged</a>;</li> <li>multi window support;</li> <li>working (persistent) notifications, including on the lock screen;</li> <li>support for 'chat state' which will help connection managers determine when a message has been seen;</li> <li>support for group chats including auto-joining channels;</li> <li>drastically lowered memory usage (35 MB idle memory on the overview screen, 45MB with a chat window opened);</li> <li><a class="reference external" href="https://github.com/maemo-leste/conversations/issues/8">fast, full text search in all your messages</a>;</li> <li>initial address book integration;</li> <li>a large refactor of the telepathy client side code;</li> <li>the ability to clear and delete chats;</li> <li>the ability to <a class="reference external" href="https://github.com/maemo-leste/conversations/issues/3">export chats</a>;</li> <li>various graphical changes to improve the user-experience;</li> </ul> <p>The main missing feature right now is the ability to start a <strong>new</strong> chat directly from conversations: <a class="reference external" href="https://github.com/maemo-leste/conversations/issues/10">composing a new message</a>. Currently one has to go through the address book and start sending a message from there. We are aware that this is a severe limitation (especially for SMSes) and will address this shortly.</p> <p>Notification on the lock screen:</p> <img alt="" src="/images/lockscreen-notification.png" style="width: 576px; height: 324px;" /> <p>Notification for a new message when the screen in active:</p> <img alt="" src="/images/conversations-notification.png" style="width: 576px; height: 324px;" /> <p>Database-wide search:</p> <img alt="" src="/images/conversations-search.png" style="width: 576px;" /> </div> <div class="section" id="sphone"> <h3>sphone</h3> <p>The biggest addition to sphone has been the addition of the <a class="reference external" href="https://github.com/maemo-leste/sphone/pull/8">voicecall-manager plugin</a> which makes sphone support audio calls using the Telepathy framework (orchestrated by <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/voicecall/">Sailfish OS voicecall daemon</a>). The reason that this addition is huge is because this allows us to switch SMS and calls over the Telepathy (which means that <a class="reference internal" href="#conversations">Conversations</a> can now handle SMses) and also because it allows us to make SIP and XMPP audio calls using the Telepathy framework.</p> <p><tt class="docutils literal">uvos</tt> has contributed various core sphone changes to support the voicecall-manager and has most recently worked on enabling DTMF support within sphone. <tt class="docutils literal">freemangordon</tt> has made sure that the <tt class="docutils literal"><span class="pre">vcard-field</span></tt> <a class="reference external" href="https://github.com/maemo-leste/sphone/pull/6#event-10594544989">gets stored in the events database</a>.</p> <p>The option to make <a class="reference external" href="https://github.com/maemo-leste/sphone/pull/5">phone calls in landscape mode</a> has also been added to accommodate the Nokia N900, which currently doesn't support portrait mode screen rotation.</p> </div> </div> <div class="section" id="media"> <h2>Media</h2> <p>In our previous post we introduced the Maemo Open Media Player. This updates brings a lot of improvements to the media player, in particular when it comes to performance and stability. However, the single biggest change is that open media player will now actually find and play music stored on your device (instead of just internet radio streams). This was achieved by a significant porting of <tt class="docutils literal"><span class="pre">mafw-tracker-source</span></tt> to newer frameworks.</p> <p><a class="reference external" href="https://github.com/maemo-leste/mafw-tracker-source">mafw-tracker-source</a> is the component that then uses gnome-tracker to deliver the files as input to the open media player and has also received many changes (<a class="reference external" href="https://github.com/maemo-leste/mafw-tracker-source/commits/master/">too many to list here</a>), but the most important improvements are improved tracker ordering and better performance.</p> <img alt="" src="/images/omp-start-screen.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/omp-play-music.png" style="width: 576px; height: 324px;" /> <p>In particular, the gnome-tracker which is used to index your files (and identify them as songs) received a lot of stability fixes and speed improvements. In some cases, fixes were never backported. The most common occurrence was that tracker wouldn't ever actually complete and start up indexing things all over again.</p> <p>In particular, <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/tracker-miners/commit/0ac3ba4e88b38d2d006286a34cf6c72da9311409">these</a> <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/tracker/commit/db6e3b5fe439cafc288d313e55697d6128212067">three</a> <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/tracker/commit/88bb88a2e5a45cdf0cb5346e04f389922b42d022">commits</a> were all essential to the stability.</p> <p><tt class="docutils literal">uvos</tt> has fixed the 'car view' screen (this was broken previously) and has <a class="reference external" href="https://github.com/maemo-leste-extras/openmediaplayer/commit/009194ced182ede5b732c0feecf4230b8c0c99a5">decreased the power usage</a> by ensuring the the UI will not update when the screen is off (previously, the UI would only stop updating if the screen was locked - but the screen can be off and not locked).</p> <img alt="" src="/images/omp-play-music-car-view.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="contacts"> <h2>Contacts</h2> <p>The Contacts (address book) program has received a lot of bugfixes, including a fix for the issue where many online contacts would show as <a class="reference external" href="https://github.com/maemo-leste/osso-abook/commit/37f15bdaeabda4bad43eda042df471cc7c45c14a">&quot;No Name&quot;</a>. The <a class="reference external" href="https://github.com/maemo-leste/osso-abook/commit/121f50e2e13096344f8983c1b74622d9fac8fceb">action time</a> of specific actions (like starting a message or a call) has also been fixed and <a class="reference external" href="https://github.com/maemo-leste/osso-abook/commit/b9f699fbd4ecb446b0a53d8e6b966432ef771938">protocol-based identification also received a fix</a>.</p> <p>The address book will now also properly show the ability to perform an audio or video call to a XMPP contact if they are online and added as a contact - this required a <a class="reference external" href="https://github.com/maemo-leste/eds-backend-telepathy/commit/78e47143060efe736ea0414ccebe6e73a188aa00">fix to eds-backend-telepathy</a> as well as <a class="reference external" href="https://github.com/maemo-leste/osso-abook/commit/4a3c44606f194ee5e00df45b53ea9a748b34bf9f">a fix to the address book</a>.</p> <p>Furthermore, when initiating a call from the address book, the program will now use the right <a class="reference external" href="https://github.com/maemo-leste/osso-abook/commit/56f3e48b44475c09620703cbd8170c952877d2fa">Telepathy request</a> so that sphone and the voicecall manager program will actually act on the request to start a phone call.</p> <p><tt class="docutils literal">uvos</tt> also tried to extend the usability of the address book to try to use hildon-mime to figure out what program to use if there are no telepathy accounts available - see <a class="reference external" href="https://github.com/maemo-leste/osso-abook/pull/2">osso-abook PR #2</a> and <a class="reference external" href="https://github.com/maemo-leste/libhildonmime/pull/5">libhildonmime PR #5</a>.</p> </div> <div class="section" id="documentation"> <h2>Documentation</h2> <p>Cornel-Florentin has continually been working on the Maemo Leste user guide and has added sections on the settings (which is really big chapter!) and contacts (contains a lot of Telepathy work) application as well as on email, application manager and most recently the navigation section.</p> <p>We have now also packaged the <a class="reference external" href="https://github.com/maemo-leste/maemo-user-guide">maemo-user-guide</a> and if you click the &quot;User Guide&quot; icon, the user guide will now open on the device in a browser - and no internet connection is required to read it.</p> <p>We are also hosting an <a class="reference external" href="https://maedevu.maemo.org/docs/userguide/html/">online version of the userguide</a>, but it might lag behind a little on the most recent version.</p> <img alt="" src="/images/user-guide-jib.png" style="width: 324px; height: 576px;" /> <img alt="" src="/images/user-guide-jib-status.png" style="width: 324px; height: 576px;" /> <img alt="" src="/images/user-guide-n900-dillo-language.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="browser"> <h2>Browser</h2> <p><tt class="docutils literal">Sander</tt> has been putting a lot work into making a decent default browser for Maemo Leste (except for on the Nokia N900, where we default to Dillo). Jib now also sports:</p> <ul class="simple"> <li>support for portrait mode;</li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/jib/issues/7">support for ad blocking</a> (lists based on uBlockOrigin)</li> <li>support <cite>file:///</cite> to access local files;</li> <li>various graphical changes to improve the user-experience;</li> <li>handle command line arguments to handle XDG or Hildon opening a URL;</li> </ul> <p>The jib browser has been made specifically for devices with limited CPU, and memory capabilities.</p> <img alt="" src="/images/jib-metabar.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/jib-settings.png" style="width: 324px; height: 576px;" /> </div> <div class="section" id="gtk-qt"> <h2>Gtk / Qt</h2> <p>The Maemo Qt module now <a class="reference external" href="https://github.com/maemo-leste/qt-platform-maemo/commit/c9c5591b60c9ef858aeb6162db87e51818c71592">supports submenus</a> in the top level menu navigation, which means that instead of having all actions of menus and submenus thrown into a single pile, one can now navigate submenus of complex applications quite naturally. Menu bars are also automatically hidden in Maemo which further improves the default experience of non-native Maemo applications, see for example Qt5 Designer:</p> <img alt="" src="/images/qt-menu-nested-designer.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qt-menu-nested-designer-file.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qt-menu-nested-designer-help.png" style="width: 576px; height: 324px;" /> <p>The 'downward arrow' menu indicator is now also <a class="reference external" href="https://github.com/maemo-leste/qt-platform-maemo/pull/2">properly rendered</a> in Qt programs, which solves <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/466">issue #466</a>.</p> <p>We have also fixed the stacked window handling in <a class="reference external" href="https://github.com/maemo-leste/qt-platform-maemo/commit/80cd89f24828f8c44935b5c6c4587b978ca4689c">commit 80cd89f</a> and <a class="reference external" href="https://github.com/maemo-leste/qt-platform-maemo/commit/4ea6b1526909141557b7489fbf935cc3c3572488">commit 4ea6b1526</a>. in our Qt plugin.</p> <p><tt class="docutils literal">freemangordon</tt> has also fixed some of the visual glitches in our qt theme, which solves <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/693">issue #693</a>.</p> </div> <div class="section" id="hildon"> <h2>Hildon</h2> <p>For a while, it was not possible to edit the order of applications in launcher menu of hildon-desktop - this has been broken ever since the addition of the Debian submenu. This has now been addressed in <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/23">hildon-desktop PR #23</a>.</p> <p>hildon-desktop now also supports multiple shortcuts for a single action which solves <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/528">issue #528</a>.</p> <p>The hildon-status-menu now allows for multiple icons per status menu plugin, implemented in <a class="reference external" href="https://github.com/maemo-leste/hildon-status-menu/pull/4">hildon-status-menu PR #4</a>. This allows us to render multiple icons for example for when a device has multiple sim cards or has multiple batteries.</p> <p><a class="reference external" href="https://github.com/maemo-leste/libhildonmime/pull/5">libhildonmime PR #5</a> extends libhildonmime to properly fallback to xdg-open.</p> <p>The terminal application now also has a setting to disable changing the font when the volume keys are pressed, see <a class="reference external" href="https://github.com/maemo-leste/osso-xterm/pull/4">osso-xterm PR #4</a>.</p> <p>DSME, the device state management entity has gained support for using <a class="reference external" href="https://github.com/maemo-leste/dsme/commit/c6aa4ef1cb4d9ea8334ed23b6bebb975a523c0bf">elogind to restart or shutdown the device</a> so that the action is coordinated more effectively to the rest of the system.</p> </div> <div class="section" id="synchronisation"> <h2>Synchronisation</h2> <p>Since the migration to Chimaera, synchronising contacts and address books was seemingly broken. Embarassingly, it turned out that yours truly forgot to <a class="reference external" href="https://github.com/maemo-leste/syncevolution/commit/14bf3f262d39748ced70a6460bd1bd25053a40a4">enable building</a> the Maemo backend of syncevolution with the migration, and once the backend was flipped on and <a class="reference external" href="https://github.com/maemo-leste/syncevolution/commit/149b3db06d02dd3a020b745039df4e4b8b5548b6">a few compilation errors were fixed</a> synchronisation once again started working.</p> <p>If you haven't set up synchronisation, check out the <a class="reference external" href="https://leste.maemo.org/Sync">Sync</a> page on the wiki.</p> </div> <div class="section" id="translations-and-localisation"> <h2>Translations and localisation</h2> <p>Since Maemo Leste has been on weblate to crowdsource translations of the operating system, many users had actually contributed translations. However, manual labour was still involved in getting the new translations built and deployed, and with the help of some automation this has now been done for the 50+ translation repositories that all saw contributions.</p> <p>Some of our own core applications do not yet support localisation (like <a class="reference internal" href="#conversations">Conversations</a>, but we aim to add that soon).</p> </div> <div class="section" id="extra-packages"> <h2>Extra packages</h2> <div class="section" id="maemo-offline-translate"> <h3>Maemo (Offline) Translate</h3> <p>Maemo Translate now supports additional languages with this <a class="reference external" href="https://github.com/maemo-leste-extras/maemo-translate-data/commit/ff97e527568e4167e28299e9ea501bc74deb729d">maemo-translate-data commit</a> - importing the latest models from <a class="reference external" href="https://github.com/mozilla/firefox-translations-models">firefox-translation-models</a>.</p> <p>We also created a script to <a class="reference external" href="https://github.com/maemo-leste-extras/maemo-translate-data/commit/399d55d72e6cbc05ab3023eec2354ece214638f8">automatically make new releases</a> based on firefox-translation-models should we want to do a new release.</p> <p>This adds offline translation support for the following languages:</p> <ul class="simple"> <li>Danish</li> <li>Greek</li> <li>Finnish</li> <li>Croatian</li> <li>Hungarian</li> <li>Indonesian</li> <li>Lithuanian</li> <li>Latvian</li> <li>Romanian</li> <li>Slovak</li> <li>Slovenian</li> <li>Serbian</li> <li>Turkish</li> <li>Vietnamese</li> </ul> <p>Each of these languages can be installed separately. One can also use the meta package to install all of the languages.</p> <p>Note that in addition to using the <a class="reference external" href="https://github.com/maemo-leste-extras/maemo-translate">Maemo Translation GUI</a>, translations can be done programmatically by linking against <a class="reference external" href="https://github.com/maemo-leste-extras/kotki/tree/7c9db3bd3bfe1c9e3602811b3734d6d2f215e012?tab=readme-ov-file#c">libkotki</a>.</p> </div> <div class="section" id="otp"> <h3>OTP</h3> <p>The Maemo &quot;OTP&quot; program (perhaps to be renamed Maemo Authenticator in the future) now <a class="reference external" href="https://github.com/maemo-leste-extras/maeotp/pull/7">supports the more common base32 and hex encoded keys</a>. This allows one to use the OTP program for 2-factor authentication with most services: Github, Gitlab, and Pypi for example.</p> </div> <div class="section" id="drnoksnes"> <h3>DrNokSnes</h3> <p>DrNokSnes, the SNES emulator is now working and packaged - thanks to <tt class="docutils literal">arno11</tt>. This has been a very long time coming (over four years) - see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/331">issue #331</a> for some history.</p> <img alt="" src="/images/droid4-drnoksnes.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/droid4-drnoksnes-play.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="ngi-assure-nlnet-funding"> <h2>NGI Assure: NLnet Funding</h2> <p>The NGI Assure that we applied to is finishing at the end of August, and we have achieved most of our funding goals (but not all). The NGI also invited us to a written interview, which can be <a class="reference external" href="https://ngi.eu/ngi-interviews/interview-with-merlijn-wajer-maemo-leste-ngi-assure-beneficiary/">read here on ngi.eu</a>.</p> <p>We're very thankful to NGI and NLNet for the opportunity.</p> </div> <div class="section" id="delayed-news-update"> <h2>Delayed news update</h2> <p>For those who don't follow day-to-day activities of the project, it may appear as if development has halted - at least judging from the frequency of news updates. Rest assured, this couldn't be further from the truth. Development has progressed to the point of Leste becoming production-ready, supporting many features one reasonably expects from a mobile device.</p> <p>Writing news updates just takes time, and is unfortunately not a task that is easily delegated. In our case, it requires understanding of systems engineering which is highly technical in nature. Thus, we'll sometimes delay news updates in favor of having something substantial to present, and other times we're simply too busy hacking away on the next cool feature.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900, Motorola Droid 3, Droid 4, Bionic and RAZR units available for interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join our effort!</p> </div> 2023-08-13T23:30:00+02:002023-08-13T23:30:00+02:00Merlijn Wajertag:maemo-leste.github.io,2023-08-13:/maemo-leste-five-year-anniversary-and-chimaera-release.html

<p>We're back with another overdue update, marking our five year anniversary as well as the official Chimaera release. Apart from the upgrade to Chimeara / Bullseye (from Beowulf / Buster), here are some other highlights:</p> <ul class="simple"> <li>Work has started on the user manual / user guide;</li> <li>Continued work on supporting more devices;</li> <li>Telepathy-based (VoIP …</li></ul>

<p>We're back with another overdue update, marking our five year anniversary as well as the official Chimaera release. Apart from the upgrade to Chimeara / Bullseye (from Beowulf / Buster), here are some other highlights:</p> <ul class="simple"> <li>Work has started on the user manual / user guide;</li> <li>Continued work on supporting more devices;</li> <li>Telepathy-based (VoIP and XMPP) voice calls are soon coming to sphone;</li> <li>Modem and cellular data enabled by default on various devices;</li> <li>Support for elogind login sessions;</li> <li>Various quality of life fixes such as Qt theming improvements;</li> <li>Better power management on the Nokia N900;</li> <li>Camera application for the Pinephone, additional firmware;</li> <li>Developers now have Nokia N900 phone calls working, but some integration and bug fixing still remains;</li> </ul> <p>(Also check out our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-new-year-update-may-2022-january-2023.html">previous update</a> in case you missed it).</p> <div class="section" id="devuan-chimaera-debian-bullseye"> <h2>Devuan Chimaera (Debian Bullseye)</h2> <p>The upgrade to Devuan Chimaera (Debian Bullseye) has been a long time coming, but it is finally here. We had been testing Maemo Leste based on Chimaera for half a year already, but with this blog post the release (and switchover) is official. The <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/24">Chimaera milestone ticket</a> lists all the packages that were rebuilt and any of the changes made to them.</p> <p>The upgrade brings new Linux kernels to various devices (6.1.x for the Droid 4, Droid Bionic, Nokia N900 and Pinephone), as well as a switch to elogind sessions. This was required for staying compatible with modern software, which now often require some form of login session manager in order to function properly (or at all).</p> <p>Most of the supported devices will now also have their modem activated, as well as having software to make phone calls and use mobile data present on the device, providing a much more phone-like experience out of the box.</p> <p>In fact, the more recent Chimaera images should allow users to make working phone calls on the Pinephone, Motorola Droid 4, Motorola Bionic out of the box. Even on the Nokia N900 calls are now working, but they still require some manual work after the device has started. The author of this news post has been using his Droid 4 as a daily driver for over half a year now.</p> <p>The image builder can now build Chimaera images, see the following commits (<a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/ed150008c1981550e9673ebd9bb19cb28770d3c7">ed150008c</a>, <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/e7a672f9cb9bf46c427576a077bd365a96a5d403">e7a672f9</a>, <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/8f2dee2640e53ffec8c328f343c339ddf153a2c0">8f2dee26</a>, <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/c5ed472f5b2e585c5412ceb12c4f1f6e6ebf4ed3">c5ed472f</a>, <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/3438cadb2e84269f337749f87a0da21b260663b3">3438cadb</a>, <a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/083cbfabffcdad4383117a28964775e156f2947b">083cbfab</a>).</p> <p>Additionally, the image builder base operating system has also been upgraded to Chimaera.</p> <div class="section" id="upgrading"> <h3>Upgrading</h3> <p>Users can perform a <tt class="docutils literal"><span class="pre">dist-upgrade</span></tt> from their Beowulf install to Chimaera, but the process isn't well supported at this point, and we instead recommend users to install a latest image. However, if one prefers to perform a dist-upgrade, please ensure that your beowulf installation is up to date before attempting to dist-upgrade to chimaera. This sequence of commands might get you through the upgrade:</p> <pre class="literal-block"> apt dist-upgrade -o APT::Force-LoopBreak=true dpkg-reconfigure --force gconf2 dpkg-reconfigure --force libgconf-2-4:armhf apt --fix-broken install apt dist-upgrade -o APT::Force-LoopBreak=true </pre> <p>But again, this is not recommended for novice users. However, <strong>this can be done entirely 'live' on the phone, while keeping the UI enabled</strong>. Even after the upgrade is complete, you can still use the phone to an extent - but you really ought to reboot when it's done.</p> </div> <div class="section" id="elogind-and-xorg"> <h3>elogind and Xorg</h3> <p>Xorg now runs as the <tt class="docutils literal">user</tt> user, and no longer as <tt class="docutils literal">root</tt>, as part of the switch to (e)logind.</p> <p>Initially the switch caused trouble because it was no longer possible to ensure that both elogind and Xorg would close all the file descriptors to the input devices, keeping the input devices awake. However, a new kernel mechanism was introduced (the <tt class="docutils literal">inhibited</tt> property) to suspend input devices regardless of whether they are kept open (see this <a class="reference external" href="https://github.com/maemo-leste/mce/pull/58">mce PR</a>) or not. Ironically, Maemo had support for that previously (in the form of a <tt class="docutils literal">disable</tt> property in sysfs), but this was removed by the upstream kernel because it was deemed an unclean mechanism, only to re-implement it again, years later.</p> <p>We also have some policy kit integration now, through the <a class="reference external" href="https://github.com/maemo-leste/policykit-1-hildon">policykit-1-hildon</a> package.</p> <p>DSME also saw some minor changes to be <a class="reference external" href="https://github.com/maemo-leste/dsme/commit/929cde639a74cecde58d1fdf86316daa51ea1e27">compatible with a login session</a>.</p> </div> <div class="section" id="pulseaudio"> <h3>Pulseaudio</h3> <p>The new Pulseaudio in Chimaera had significantly reworked their UCM2 support, and as result our <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/685">audio setup was completely broken</a>. We took a deep dive and figured out what the problem was, only to find out that the headphone plug detection was also broken. These problems have now been fixed in commit <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/1d08e6cbaa4eb18d07fc7a29423ac0db1e98d536">1d08e6cb</a> and commit <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/4b8851518d8d523065dc1bb12df8d368de9d0af2">4b885151</a></p> </div> <div class="section" id="cpu-flags"> <h3>CPU flags</h3> <p>We now also build packages in the Maemo repositories with NEON and Thumb2. Most packages in Debian are already using Thumb2, but not all make use of NEON. See issue <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/691">#691</a> and the jenkins-integration commits <a class="reference external" href="https://github.com/maemo-leste/jenkins-integration/commit/bf2ce8c3423ec12c13f086d1acf64959b073bfaf">bf2ce8c3</a> and <a class="reference external" href="https://github.com/maemo-leste/jenkins-integration/commit/75a8e3fbff361653c0fd01ff1db136b40ec62b80">75a8e3fb</a> for more details.</p> </div> <div class="section" id="qtwebengine"> <h3>qtwebengine</h3> <p>Unfortunately Qt Webengine has a hardcoded list of Qt platform plugins that it will attempt to use 3D acceleration on, so we have had to patch qt web engine to ensure that it also uses 3D acceleration on the Maemo platform plugin.</p> <p>See <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/qtwebengine/commit/c1fbfce8d8ea6c89f65fb8c884d506a39f717049">this patch to qtwebengine</a> for more info. As a result many browsers will now run much more smoothly on Maemo Leste.</p> </div> <div class="section" id="syncevolution"> <h3>syncevolution</h3> <p>The one regression we still have to figure out is syncevolution - as of writing the package doesn't seem to work with its Maemo backends. Syncevolution went through a major release, so we still have to figure out what exactly is broken.</p> <p>We did port the Maemo Telepathy Backend to the new syncevolution version (to have contacts integration), in commits <a class="reference external" href="https://github.com/maemo-leste/eds-backend-telepathy/commit/b96f28389554f2a1d39d6b8eeef3bd1a66e701fc">b96f28389</a>, <a class="reference external" href="https://github.com/maemo-leste/eds-backend-telepathy/commit/e77bd8faec35947582d6009f4675e7aafe5b7e30">e77bd8fae</a>, <a class="reference external" href="https://github.com/maemo-leste/eds-backend-telepathy/commit/334b80cfcd072c5ab7eb7607decfb855b57b7643">334b80cfc</a> and <a class="reference external" href="https://github.com/maemo-leste/eds-backend-telepathy/commit/5be241157c3c344b80ca39e75b63d4c22a282cbf">5be241157</a>.</p> </div> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>On the Pinephone, the Pinhole/Shutter camera application should now let users take pictures. See this <a class="reference external" href="https://leste.maemo.org/PinePhone#How_to_take_a_picture">wiki page</a> for more information.</p> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>The Nokia N900 has seen a lot of love from the community members. The power management has improved a bunch (while not yet hitting the actual low power OMAP modes), and a good battery will give one at least a day of uptime.</p> <p><a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/f0de824b14ccf9070efae90d6dcb97b097ecb325">Blacklisting some modules</a> and <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/7dd372bf75b016c02a7acc13ddae928e722d2339">setting proper parameters on the 1-wire module</a> has significantly improved the battery life.</p> <p>The FM transmitter module has also been enabled in the kernel, as well as some additional features for the <tt class="docutils literal">iotop</tt> program to work properly (see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/706">issue #706</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/703">issue #703</a>.</p> <p>User <tt class="docutils literal">sicelo</tt> has improved the <a class="reference external" href="https://github.com/torvalds/linux/commit/68fdbe090c362e8be23890a7333d156e18c27781">capacity evaluation of the battery</a> in the upstream kernel, which permits <a class="reference external" href="https://github.com/maemo-leste/n900-pm/pull/1">simplifying</a> the <tt class="docutils literal"><span class="pre">n900-pm</span></tt> script.</p> <p>User <tt class="docutils literal">arno II</tt> has contributed a UCM2 file for the Nokia N900, thereby much improving the audio situation on the Nokia N900. He has reported that it can also be used for phone calls when a few other pieces are integrated. The earpiece doesn't work yet, but users should be able to use both the speakers or headphones for calls.</p> <p>The modem still needs to be loaded in a certain way for audio calls to work, and the necessary changes for the <tt class="docutils literal">cmtspeech</tt> package and <tt class="docutils literal">pulseaudio</tt> configuration are still under development.</p> <p>For the next update, users can expect that phone calls will work normally and properly.</p> </div> <div class="section" id="volume-control"> <h3>Volume control</h3> <p>The volume applet has been improved to ensure that it now also <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/615">works on the Pinephone</a>. The right audio sinks are now detected automatically, rather than being hardcoded per device, see <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume/pull/4">maemo-statusmenu-volume PR #4</a> and <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume/issues/3">maemo-statusmenu-volume issue #3</a>.</p> <p>With the <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/0e2611e5c6c952eded5e737189da219a8c2e1f48">volume keys remapped</a>, and having received a UCM2 file, the volume applet now also works on the Nokia N900:</p> <img alt="" src="/images/n900-volume-applet.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="core-software-additions-and-changes"> <h2>Core Software additions and changes</h2> <div class="section" id="mafw-open-media-player"> <h3>mafw / (Open) Media Player</h3> <p>We've been working on making Open Media Player (OMP) and its dependencies work on Maemo Leste. At this point, the internet radio player works, and work is underway to also be able to play files from the file system as well. This involves porting mafw-tracker-source to the newer GNOME APIs and <tt class="docutils literal">freemangordon</tt> has started working on this.</p> <p>This is what the media player looks like when started:</p> <img alt="" src="/images/omp-start.png" style="width: 576px; height: 324px;" /> <p>Listening to a radio stream:</p> <img alt="" src="/images/omp-radio.png" style="width: 576px; height: 324px;" /> <p>Showing the details of a radio stream:</p> <img alt="" src="/images/omp-radio-details.png" style="width: 576px; height: 324px;" /> <p>Adding a new radio stream:</p> <img alt="" src="/images/omp-add-baroque.png" style="width: 576px; height: 324px;" /> <p>Portrait mode:</p> <img alt="" src="/images/omp-portrait.png" style="width: 324px; height: 576px;" /> <p>Open Media Player is now available for installation from the Hildon Application Manager.</p> </div> <div class="section" id="qt-5-styling"> <h3>Qt 5 styling</h3> <p>Some of the Qt5 styling problems that were present on Maemo Leste in the past have now been solved.</p> <p>One of the problems was that some applications had (white) backgrounds that didn't fit with the theme (this was particularly present in the clock application). Another problem was that text wouldn't always contrast well with the background - for example black text on a dark gray background.</p> <p>Various widgets should now also <a class="reference external" href="https://github.com/maemo-leste/qtstyleplugins/commit/83aca5c8f2f69f5815307ebac0a65a9be5522d19">support scrolling by default</a>.</p> </div> <div class="section" id="notifications"> <h3>Notifications</h3> <p>Maemo now implements more of the XDG specification for notification patterns such as the vibration property, but also in general notification ought to be supported in a (much) better fashion. Previously not all XDG categories were supported, but now many more are. This changes were added to <a class="reference external" href="https://github.com/maemo-leste/hildon-plugins-notify-sv">hildon-plugins-notify-sv</a> version <tt class="docutils literal">0.64</tt>.</p> </div> <div class="section" id="telepathy"> <h3>Telepathy</h3> <p><a class="reference external" href="https://github.com/maemo-leste/sphone/pull/4">Work is underway</a> to add a Telepathy module to our sphone application. This would then allow making regular phone calls through Telepathy - as well as XMPP and SIP phone calls. The current work can already be used to make phone calls, but for outgoing calls the &quot;privacy&quot; bit is unconditionally being set, which means that the receiving caller won't be able to see your phone number. XMPP and SIP phone calls start, but the audio isn't being routed properly yet.</p> <p>Having sphone use Telepathy is important, because then we can finally start sending and receiving SMS messages from the Conversations application.</p> <p>This work will be completed by the next news post.</p> <p>Meanwhile, enjoy a screenshot showing SIP messages being exchanged between two Maemo Leste users using Conversations.</p> <img alt="" src="/images/sip-messages-conversations.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="documentation-user-manual"> <h2>Documentation: User Manual</h2> <p>As part of the funding, we have been working on improving our documentation and created a user manual. It is still being worked on and we haven't decided on a place for it yet, but the <a class="reference external" href="http://maemo-leste-manual.motionlibre.org/">manual can be found here</a>.</p> <p>The <a class="reference external" href="https://gitlab.com/motionlibre1/maemo-leste-user-handbook">source code for the manual</a> is also available.</p> <p>Cornel-Florentin, who has worked on the documentation extensively has described the approach below:</p> <p><em>&quot;What we planned to do was first of all to have quite explanatory instructions about how to navigate through the OS's interface, since most people nowadays are pretty much used to the navigation concepts of Android and Apple devices. And since Maemo Leste's interface is different, we thought that this would be the most important aspect about improving user experience, and expectations.</em></p> <p><em>Another important aspect of user friendliness is customization, to make users feel more like home, and this was also prioritized.</em></p> <p><em>To make it very clear to understand all the above mentioned aspects, and not only, almost every detail was accompanied by many screenshots, which actually is what took a big part of the time required writing this manual.</em></p> <p><em>Besides, what also helps to to adjusting users' expectations is a section dedicated to the known bugs, or elements which don't work as expected. Many items here most likely will be short-lived, as they will be solved during the following development stages, but mentioning them is very important, for the reasons given above.</em></p> <p><em>Another important part, before starting writing, was to think about its structure, in order to have it work as a reference too, and so to fit both beginners and more experienced users. This was reworked and rethought a number of times, as progressing, obviously also requiring a serious amount of time. And it's not final, since it might still be modified in the future. It's the living part of the manual, and the under development state of Maemo Leste, which keep it transforming.</em></p> <p><em>Having a good structure allows linking and crosslinking different parts, sections and subsections, enabling packing the documentation in a more compact form, which is easier to follow, grasp, modify and add to in the future. Finding and jumping to the section you're looking for is also much easier this way.</em></p> <p><em>Another structurally beneficial thing is having a glossary of technical terms, so that again, advanced users to not have to crawl through text, skipping trivial information, while at the same time beginners to not feel lost.</em></p> <p><em>The manual is still work in progress, but by following the provided links you can check the already completed parts, which are already considered to be done, but which will still be revised at least one more time before they will go into a final state. Any suggestions and corrections are welcome, so that we can integrate them in the revised versions.&quot;</em></p> </div> <div class="section" id="community-and-supporting-software-updates"> <h2>Community and supporting software updates</h2> <div class="section" id="dors-cluc-2023"> <h3>DORS/CLUC 2023</h3> <p>Maemo Leste gave a talk at DORS/CLUC. There doesn't seem to be a recording online yet, but one can look at the <a class="reference external" href="https://wizzup.org/maemo-leste-dors-cluc-2023.pdf">PDF of the presentation</a> - there isn't any particular news in the presentation though - the aim was to raise awareness.</p> <p>We also had a stand and showed off Maemo Leste hardware to various folks.</p> </div> <div class="section" id="extra-packages"> <h3>Extra packages</h3> <p>Various new packages were added by the community. Some are described in this at length, others like <a class="reference external" href="https://leste.maemo.org/Extras/MStarDict">MStarDict</a> have a wiki page that explain how they work. <a class="reference external" href="https://github.com/maemo-leste-extras/harbour-amazfish">harbour-amazfish</a> was ported over from SailfishOS.</p> <div class="section" id="maemo-weather"> <h4>Maemo Weather</h4> <p><tt class="docutils literal">Sander (dsc)</tt> has built a weather application in Qt called <a class="reference external" href="https://github.com/maemo-leste-extras/NOMWeather">NOMWeather</a>. It looks great and is very usable - you can find some screenshots of the application below.</p> <img alt="" src="/images/maemo-weather-korcula.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/maemo-weather-korcula-wind.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="maemo-offline-translate"> <h4>Maemo (Offline) Translate</h4> <p>Mozilla recently created a browser extension called <a class="reference external" href="https://addons.mozilla.org/en-US/firefox/addon/firefox-translations/">firefox-translations</a> which translates webpages from one language to another <em>without</em> using a third-party service. The translation happens locally, in the browser, via language models created using machine-learning.</p> <p>Since this browser extension is open-source, <tt class="docutils literal">Sander (dsc)</tt> wondered if he could port this translation engine to Maemo Leste for use as a standalone GUI application for quality <strong>offline</strong> translation. This meant porting and packaging the underlying machine learning technologies for low-powered ARM devices (like the Droid 4) which turned out to be a challenging, but not impossible task.</p> <!--  --> <p>The end result is a responsive GUI that offers quick translations.</p> <img alt="" src="/images/maemo-translate-enbg.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/maemo-translate-deen.png" style="width: 576px; height: 324px;" /> <p>Maemo translate is now available from the repository as <cite>maemo-translate</cite>. In addition, check out the individual language packs in the Hildon Application Manager or via <cite>apt search maemo-translate-data</cite></p> <img alt="" src="/images/ham-translate-data.png" style="width: 324px; height: 576px;" /> </div> <div class="section" id="windows-7-theme"> <h4>Windows 7 theme</h4> <p>We have ported the old <a class="reference external" href="http://maemo.org/packages/view/windows7-theme/">Maemo Windows 7 theme</a> - see the <a class="reference external" href="https://github.com/maemo-leste-extras/windows7-theme">windows7-theme</a> extras repository for the source. It can now be installed on your Maemo Leste devices. Find below some screenshots of what it looks like:</p> <img alt="" src="/images/win7-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/win7-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/win7-3.png" style="width: 576px; height: 324px;" /> </div> </div> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900, Motorola Droid 3, Droid 4, Bionic and RAZR units available for interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <!-- .. image:: /images/massdroid.jpg --> <!-- :height: 375px --> <!-- :width: 666px --> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join our effort!</p> </div> 2023-01-12T18:00:00+01:002023-01-12T18:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2023-01-12:/maemo-leste-new-year-update-may-2022-january-2023.html

<p>First of all, happy new year to everyone following along.</p> <p>This is probably our last blog post before our Beta release. This latest update focuses heavily on cellular software and drivers as well as other communication features, but there's also a healthy amount of bugfixes and performance improvements mixed in …</p>

<p>First of all, happy new year to everyone following along.</p> <p>This is probably our last blog post before our Beta release. This latest update focuses heavily on cellular software and drivers as well as other communication features, but there's also a healthy amount of bugfixes and performance improvements mixed in.</p> <p>(Also check out our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-sixteenth-update-november-and-december-2021-january-april-2022.html">previous update</a> in case you missed it).</p> <p>Highlights:</p> <ul class="simple"> <li>big performance improvements for the PinePhone, PineTab and other Lima (Mali GPU) devices;</li> <li>performance and stability improvements for PowerVR devices like the Droid 4, N900, Bionic and more;</li> <li>many modem stability improvements (both ofono and Linux kernel driver) for mapphones (Droid 4, Bionic, Droid 3, etc);</li> <li>the cellular stack is maturing and basically ready for day-to-day usage;</li> <li>RTCom user interfaces landed, allowing one to configure various instant messaging accounts;</li> <li>Alarms are now working;</li> <li>porting to the new Devuan Chimaera (Debian bullseye) is moving along swiftly;</li> </ul> <div class="section" id="images-and-upgrading"> <h2>Images and upgrading</h2> <p>Devuan accidentally <a class="reference external" href="https://dev1galaxy.org/viewtopic.php?id=5213">let their signing key expire</a> (something which has happened to us in the past as well). This meant that any Devuan (and thus, Maemo Leste) user would no longer get updates from the Devuan repositories unless they manually took some action. Our packages were unaffected, so we have just imported the <tt class="docutils literal"><span class="pre">devuan-keyring</span></tt> package into our repository. By simply updating and upgrading twice, you should be all set again.</p> <p>Some of our images <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/630">failed to build for a while</a>, but this issue has now been resolved.</p> </div> <div class="section" id="funding"> <h2>Funding</h2> <p>Back in August 2022 we applied for funding in the &quot;NGI0 Entrust&quot; fund of NLNet, and they have approved our proposal, which focuses on improving our mobile effort in a few key areas:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/644">Moving to the new Debian release</a>: we're looking to move to Devuan Chimaera (Debian bullseye) in the next month, bringing in the latest and greatest software packages. This involves porting Maemo software to new compilers, frameworks, and so on.</li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/25">Supporting more devices</a>: We're looking to bring up Maemo Leste (and thus the Linux kernel and drivers) on the Motorola Razr phone (XT910, XT912), the Motorola Xyboard tablets (MZ609, MZ617), the Motorola Atrix 2 phone (MB865) and the Moto G4 Play.</li> <li>Improving and further integrating the Telepathy communication framework: we're looking at <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/26">adding OMEMO support to the Telepathy Gabble (XMPP) plugin</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/27">integrating XMPP and SIP calls in Maemo</a> and are looking into <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/28">adding/improving Matrix support to Telepathy</a>.</li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/29">Creating and improving our documentation</a>: we're looking to create a user handbook, a contributors guide as well as a developer portal.</li> </ul> <p>The project page of our proposal can be found on the <a class="reference external" href="https://nlnet.nl/project/MaemoLeste-Telepathy/">NLnet website</a>, along with our <a class="reference external" href="https://nlnet.nl/project/MaemoLeste/">now finished previous proposal</a>. (And don't forget, we've also finished a project with <a class="reference external" href="https://dapsi.ngi.eu/hall-of-fame/maemo-leste/">DAPSI</a> in 2022)</p> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>Pinephone support has been greatly improved with the help of <tt class="docutils literal">freemangordon</tt> on the graphics side and <tt class="docutils literal">rafael2k</tt> on the kernel and camera side. <tt class="docutils literal">rafael2k</tt> is our pinephone kernel maintainer.</p> <p>The pinephone kernel will move to Linux 6.1 for Chimaera. <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/4">pine64-kernel PR #4</a> added a newer kernel and initial camera support, <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/5">pine64-kernel PR #5</a> then added v4l support, <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/6">pine64-kernel PR #6</a> added some more fixes. <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/8">pine64-kernel PR #8</a> and <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/9">pine64-kernel PR #9</a> made the usbnet work again.</p> <div class="section" id="graphics"> <h4>Graphics</h4> <p>In one of our previous updates we had mentioned we fixed the graphics corruption bug at the expense of some performance. We have since fixed the problem properly in clutter by <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/clutter-0.8/pull/2">adding support for the buffer age extension</a> and now the performance is once again great. There are still some issues to be tackled: landscape mode is not as snappy as portrait, hitting some slow path in glamor.</p> <p>We believe users may find Maemo Leste in portrait mode one of the snappiest experiences they might have seen yet on the pinephone.</p> <video controls height="480px" width="720px"> <source src="images/pp-leste.mp4" type="video/mp4"> </video></div> <div class="section" id="camera"> <h4>Camera</h4> <p>We have imported <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/libcamera">libcamera</a> and the <a class="reference external" href="https://github.com/maemo-leste/firmware-ov5640">ov5640 firmware</a> thanks to the work of <tt class="docutils literal">rafael2k</tt>, who is also working on packaging a V4L-based camera application which is also used on Sailfish, called <a class="reference external" href="https://github.com/piggz/harbour-advanced-camera">Harbour Advanced Camera</a> - so we might soon have a (default) camera application.</p> </div> </div> <div class="section" id="mapphones-droid-4-bionic-etc-and-nokia-n900"> <h3>Mapphones (Droid 4, Bionic, etc) and Nokia N900</h3> <p>Our kernel for the mapphones and Nokia N900 is now at version 6.1, with various changes to the graphics and modem stack, as well as some other changes.</p> <div class="section" id="modem"> <h4>Modem</h4> <p>The modem support has been greatly improved by <tt class="docutils literal">freemangordon</tt>, to the point where all known bugs seem to be fixed. In the past, calls to the modem would sometimes time out or simply not happen, which would lead to all kinds of problems. It would also take a long time for the modem to show up, and sometimes required restarting ofono, which would also occasionally crash. All of these problems are now resolved. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/445">Issue #445</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/530">issue #530</a> describing those problems are thus now resolved. The commits can be found in this <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/ofono/commits/maemo-ofono">ofono branch</a>, and kernel commits <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/64655c0c2e6498658072a4aeac3539a418397f19">64655c0c</a>, <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/977de3af9a11f681c7b0669f60ae33a941c00380">977de3af</a> and <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/1b2a0860cd17c5ea5d3bf16119945f1dcc46ed8f">1b2a0860</a> are also required.</p> <p>The latest kernel also contains a commit to work around the kernel suspending the audio in a call, which combined with the latest sphone, <strong>make calls work with headphones, earpiece and speakers on the mapphones and Pinephone</strong>.</p> <p>Some intermediate development kernels <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/681#issuecomment-1337958216">broke the modem on the N900, causing the device to bootloop</a> - this remained broken for quite some time, but has since been fixed - apologies for the inconvenience caused by this.</p> </div> <div class="section" id="graphics-1"> <h4>Graphics</h4> <p>The X11 (DDX) driver now supports Xv video acceleration, which (as the name implies) accelerates the playing of videos.</p> <p>The driver now also implements a cache for buffer objects, which drastically improves the scrolling speed in various applications that do not use 3D rendering, see <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/pull/1">xf86-video-omap PR #1</a>.</p> <p>There are also some fixes for some crashes and memory leaks that were occuring before. All of the commits can be found in the <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/commits/master">xf86-video-omap github repo</a>.</p> <p>Previously it wasn't possible to use GLES1 due to Debian disabling it by default (?), but we have now fixed this in our mesa package, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/606">issue #606</a>.</p> </div> <div class="section" id="miscellaneous"> <h4>Miscellaneous</h4> <p>We now use the IIO driver for the accelerometer on the Nokia N900, rather than the input device based driver (see <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/pull/3">droid4-linux PR #3</a> - the IIO (Industrial I/O) subsystem is a better fit for the accelerometer, and we already support this.</p> <p>Additionally, the N900 could no longer use USB networking and more importantly, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/681#issuecomment-1341835131">could no longer charge because it did not detect when connected to a charger</a>. This was also fixed in the kernel.</p> <p>In the past we had reverted some commits to the Linux kernel that caused dramatic power consumption, but now this is no longer necessary as the interval can be changed via sysctl, see <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/32">leste-config PR #32</a>.</p> <!-- * https://github.com/maemo-leste/droid4-battery-calibration/pull/1 (Correct the script path) --> <!-- * https://github.com/maemo-leste/leste-config/pull/31 (Mapphones: up hifi volume a bit) --> <!-- * https://github.com/maemo-leste/bugtracker/issues/348 (flakey usb networking) --> </div> </div> <div class="section" id="bluetooth"> <h3>Bluetooth</h3> <p>Maemo Leste does not currently ship with any bluetooth UI, but <tt class="docutils literal">blueman</tt> can be installed. Once the right kernel modules are also loaded, bluetooth ought to work. <tt class="docutils literal">Wizzup</tt> tried to have his car connect to his Maemo Leste phone recently, but found various things still had to be fixed. The work described below is not yet integrated, as we don't have a (proper) Maemo UI for bluetooth yet.</p> <p>The <tt class="docutils literal">Class</tt> value in <tt class="docutils literal">/etc/bluetooth/main.conf</tt> has to be set to <tt class="docutils literal">0x005a020c</tt>, which will make devices recognize your device as an actual phone. If you don't do this, some devices (like cars) won't even &quot;see&quot; your device.</p> <p>After that, the car would connect to the device. From this point on, <cite>module-bluetooth-discover</cite> had to be loaded in pulseaudio if not already:</p> <pre class="literal-block"> pactl load-module module-bluetooth-discover </pre> <p>Then, just running <cite>mpris-proxy</cite> will cause the car to detect any media player that supports <cite>mpris</cite>, for example <cite>mpd</cite> with <cite>mpdris2</cite> installed. Furthermore, <cite>ofono</cite> and <cite>bluez</cite> will now also collaborate and handle calls correctly - making it possible to accept phone calls from your car!</p> <p>The video below shows this in action:</p> <video controls height="380px" width="676px"> <source src="images/bluetooth-car.webm" type="video/webm"> </video></div> </div> <div class="section" id="device-porting"> <h2>Device porting</h2> <p>As of this news post, we have Maemo Leste booting on a Razr XT910 device <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commits/maemo-6.1">after some Linux kernel changes by uvos and tmlind</a> - but the display doesn't fully refresh properly yet. Most other things seem to work, though, see <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/33">leste-config PR #33</a> and <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/34">leste-config PR #34</a>.</p> <p><tt class="docutils literal">tmlind</tt> added <tt class="docutils literal">kexecboot</tt> support for the Razr XT910/XT912, and Xyboard tablets model MZ609 and MZ617, which will allow us to boot Maemo Leste. The tablets also require some further work on the display bridge, but we're hoping that otherwise most things will start to work relatively soon on those too.</p> <p>The devices already have kexecboot support, with this commit <a class="reference external" href="https://github.com/tmlind/droid4-kexecboot/commit/2c85eea545e33098a960e439e2b20a788ea06cc8">adding support for xt910, mz609 and mz617</a> and this commit <a class="reference external" href="https://github.com/tmlind/droid4-kexecboot/commit/cd2ef83e5b55f33a3012761a4bd68bc519922a19">fixing xt912 support</a>.</p> <!-- TODO: photos of razr, photos of mz609/mz617 --> <p>While we already have initial support for the Droid 3 (XT862), it is not yet stable and the device very frequently resets - we hope to address this soon, but we don't have a clear idea about what exactly causes it yet.</p> </div> <div class="section" id="core-software-additions-and-changes"> <h2>Core Software additions and changes</h2> <div class="section" id="rtcom-real-time-communication-framework"> <h3>rtcom (real time communication) framework</h3> <p>The <a class="reference external" href="https://github.com/maemo-leste/rtcom-presence-ui">&quot;presence&quot; UI</a> is now ready, allowing one to change their presence from status menu.</p> <p>Note the green circle in the status area:</p> <img alt="" src="/images/presence-ui-3.png" style="width: 576px; height: 324px;" /> <p>which shows as a status applet here as well:</p> <img alt="" src="/images/presence-ui-2.png" style="width: 576px; height: 324px;" /> <p>which can be clicked to get to this dialog:</p> <img alt="" src="/images/presence-ui.png" style="width: 576px; height: 324px;" /> <p>We have also added support for wildcard matching queries that search all the messages in the rtcom databases, allowing for fast message history searching in the conversations UI, see <a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger/pull/1">rtcom-eventlogger PR #1</a> and <a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger/pull/2">rtcom-eventlogger PR #2</a>.</p> <p>On top of that, we figured out how to have rudimentary multi-user and group chats work in Telepathy in conversations, but this is not yet available for testing for the general public.</p> <p>The phone application also has seen various improvements. For example, after a call is finished, the window doesn't disappear immediately, but rather stays around for a few seconds so that the user can understand what happened.</p> <p>The rtcom framework now allows setting up not just IRC and XMPP accounts, but also <a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-plugins/commit/c545748d0b8862c6e1fb3a536418a0acced7f85f">SIP (internet telephony) accounts</a>, and during our testing we were even able to utilise <a class="reference external" href="https://github.com/dylex/slack-libpurple">slack-libpurple</a> - but this is not currently packaged or well tested.</p> <div class="section" id="slack"> <h4>slack</h4> <p>Using <a class="reference external" href="https://github.com/dylex/slack-libpurple">slack-libpurple</a> in <tt class="docutils literal"><span class="pre">telepathy-haze</span></tt> (a telepathy connection manager that can load libpurple/pidgin plugins), we got Slack to work, at least in a very basic fashion, on Maemo Leste. We were able to send direct messages to folks, including ourselves:</p> <img alt="" src="/images/slack-conversations.png" style="width: 576px; height: 324px;" /> <p>Here is the other side of that conversation (in the browser):</p> <img alt="" src="/images/laptop-slack.png" /> <p>And here is an overview of the recent communications (names removed):</p> <img alt="" src="/images/slack-overview.png" style="width: 576px; height: 324px;" /> <p>The <tt class="docutils literal"><span class="pre">telepathy-haze</span></tt> processes use about 8MB of RAM, which is a nice change from the many gigabytes that Slack typically uses in a browser tab.</p> </div> </div> <div class="section" id="cellulard"> <h3>cellulard</h3> <p>A new daemon was introduced to our mobile operating system, called <a class="reference external" href="https://github.com/maemo-leste/cellulard">cellulard</a>. Its main task is to deal with the modem on a high level: it will, for example power and online the modem via ofono on startup, or offline the modem in case flight mode is selected.</p> <p>This was necessary because nothing else configures the modem, but also to ensure that we would be able to show SIM PIN entry dialogs on start of the device, as there was previously no program putting the modem in the right state. If no PIN is required and flight mode is not on, the modem will just be put in the online mode upon start of the device.</p> <p>As a result, flight mode now also works as intended.</p> </div> <div class="section" id="maemo-ringtones"> <h3>maemo-ringtones</h3> <p>The <tt class="docutils literal"><span class="pre">maemo-ringtones</span></tt> package that we used to import from Fremantle contained some wrong paths and configuration files, which <tt class="docutils literal">rafael2k</tt> has fixed in <a class="reference external" href="https://github.com/maemo-leste-assets/maemo-ringtones/pull/1">maemo-ringtones PR #1</a>. This makes it so that in the near future the new images will actually use a ringtone out of the box (i.e. without any changes required by the user) when being called.</p> </div> <div class="section" id="alarms"> <h3>alarms</h3> <p>Alarms now work well. Before, alarms could be set, but they wouldn't actually vibrate the phone and play sounds, but this is all fixed now. To achieve this, we had to fix problems in our <a class="reference external" href="https://github.com/maemo-leste/hildon-plugins-notify-sv/pull/1">gst 1.0 port in the notify plugin</a> and <a class="reference external" href="https://github.com/maemo-leste/hildon-plugins-notify-sv/pull/2">fix a crash</a>. We also had to perform the same gstreamer work for the <a class="reference external" href="https://github.com/maemo-leste/clock-ui/pull/1">Qt gst 1.0 code</a>.</p> <img alt="" src="/images/alarm-clock-portrait.png" style="width: 324px; height: 576px;" /> </div> <div class="section" id="calendar"> <h3>calendar</h3> <p>With the addition of the address book as a default application, we have now also updated our instructions on how to synchronise your contacts, calendar and notes on the <a class="reference external" href="https://leste.maemo.org/Sync">Sync wiki page</a>.</p> </div> <div class="section" id="notifications"> <h3>notifications</h3> <p><a class="reference external" href="https://github.com/maemo-leste/hildon-home/pull/2">hildon-home PR #2</a> provides a more up to date and compatible implementation of notifications as defined by freedesktop.org's <tt class="docutils literal">org.freedesktop.Notifications</tt> DBUS specification.</p> </div> <div class="section" id="input-for-gtk3"> <h3>input for gtk3</h3> <p>Thanks to the work of <tt class="docutils literal">freemangordon</tt>, we now support the Hildon virtual keyboard in Gtk 3 (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/537">issue #537</a>) - this is great news in particular for devices that lack a hardware keyboard, such as the pinephone and the Droid bionic. In addition, this also allows for switching keyboard layouts from Gtk 3 applications using hildon-input-method.</p> <p>Gtk3 text input is shown below on the Droid 4:</p> <img alt="" src="/images/gtk3-dino-im.gif" style="width: 576px; height: 324px;" /> <p>(if you happened to see a mouse cursor, that's just how ffmpeg captures the touch screen events)</p> </div> <div class="section" id="mobile-data-improvements"> <h3>mobile data improvements</h3> <p>The <tt class="docutils literal"><span class="pre">libicd-network-ofono</span></tt> package (for mobile data) has seen a lot of improvements, see <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ofono/commits/master">all the commits from September 18th</a> - making it now a quite usable plugin.</p> <p>DHCP for mobile data has been fixed now (see <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ipv4/pull/4">libicd-network-ipv4 PR #4</a>, and one of the shell scripts is now also more <tt class="docutils literal">sh</tt> compliant (see <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ipv4/pull/6">libicd-network-ipv4 PR #6</a>).</p> </div> </div> <div class="section" id="additional-software-changes"> <h2>Additional Software changes</h2> <div class="section" id="hildon-application-manager"> <h3>hildon-application-manager</h3> <p>The Hildon application manager no longer shows debug symbol packages, which was quite pointless for most users and showed every package twice - once for the actual package, and once for its debug symbols.</p> <p>Furthermore, in the process of porting hildon-application-manager to Chimaera (<a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commits/master">which</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/c9a3b01f3c39990df33ae5e02928327df50f8615">was</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/fb07a532ddb8fa3f96880188e97e242f3e2c35cc">actually</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/5ce3388cabe671aff2627818b94616f86a5376de">quite</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/a5b0591a768155087ffa908da01c609e53c2012b">a</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/7acb76a488701bec05fd97d2eca70c06f8514b25">sizeable</a> <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/addecba6527b58da62c1d5cc4e568c4cfbacf63a">undertaking</a>), we have fixed the problem that made the <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/commit/ed2def0fe7151acb0728a3906f25debd206874f2">application crash when the &quot;Details&quot; button was being pressed</a>.</p> <img alt="" src="/images/ham-details.png" style="width: 576px; height: 324px;" /> <p>There are also updates to the <a class="reference external" href="https://github.com/maemo-leste/hildon-application-manager/pull/2">Bulgarian translation</a>.</p> </div> <div class="section" id="qtwebbrowser"> <h3>qtwebbrowser</h3> <p>In Chimaera, we have a custom <tt class="docutils literal">qtwebengine</tt> build to ensure that <tt class="docutils literal">qtwebbrowser</tt> can use 3D acceleration (unfortunately <tt class="docutils literal">qtwebengine</tt> has a hardcoded list of Qt platforms that it supports, so we had to add <tt class="docutils literal">&quot;maemo&quot;</tt> to this list). As a result, the browser is now much snappier. Additionally, the browser now also <a class="reference external" href="https://github.com/maemo-leste-extras/qtwebbrowser/commit/4704f8f793044cdf920a408cae4397fa8b0f2415">supports portrait mode in Chimaera</a>. We'll be working on further integrating the browser in Maemo so that it's easier to interact with.</p> <img alt="" src="/images/qtwebbrowser-portrait-d4.png" style="width: 324px; height: 576px;" /> </div> <div class="section" id="osso-xterm"> <h3>osso-xterm</h3> <p><tt class="docutils literal"><span class="pre">osso-xterm</span></tt> <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/23">now opens the browser</a> when a link is touched / clicked upon.</p> </div> </div> <div class="section" id="chimaera-porting"> <h2>Chimaera porting</h2> <p>As mentioned in other places in the post, we're actively working on porting Maemo Leste from Devuan Beowulf (Debian buster) to Devuan Chimaera (Debian bullseye).</p> <p>Following Debian stable brings along the benefits of up to date software, timely security updates and in general new things that the free software ecosystem brings. In addition, we will also need to maintain less 'forks' of software: sometimes we have to provide a newer package of some software, which requires us to fork it to our own repositories and then build it in our CI, which in turns takes time and also requires us to stay on top of updates and fixes.</p> <p>The Chimaera image will <strong>be our first image that provides working phone calls out of the box</strong> on several supported devices. Previously various cellular packages were hidden in the development repositories -- so our beowulf images never even powered on the modem by default.</p> <p>The main remaining challenge for supporting Chimaera fully is supporting elogind compatible sessions, which we hope to finish in one or two weeks.</p> <!-- We also had to increase the default `disk size for images --> <!-- <https://github.com/maemo-leste/bugtracker/issues/625>`_. --> <p>Progress can be tracked in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/644">issue #644</a> and <a class="reference external" href="https://maedevu.maemo.org/pkgweb/">pkgweb</a> already shows the packages in Chimaera and the image builder has been updated to support building Chimaera images.</p> <p>We do not yet encourage users to switch - we plan to have the full release ready in February and more details will emerge by then.</p> </div> <div class="section" id="community-and-supporting-software-updates"> <h2>Community and supporting software updates</h2> <div class="section" id="openfest-2022"> <h3>OpenFest 2022</h3> <p>Maemo Leste had a presence at the open and free software conference in Sofia, Bulgaria, in October of 2022. <tt class="docutils literal">Wizzup</tt> <a class="reference external" href="https://www.youtube.com/watch?v=I2qnjBZ-Scg">gave a talk on Sunday</a>, and we also had a very well visited stand during both days of the conference. Here we were showing off various devices that Maemo Leste runs on (anticlockwise from bottom left):</p> <ul class="simple"> <li>Allwinner LIME20 tablet in a metal enclosure with wifi and a LTE modem attached over USB</li> <li>Motorola Bionic</li> <li>Motorola Droid 4</li> <li>Pinephone</li> <li>Raspberry pi with a HDMI/USB touchscreen attached</li> <li>Allwinner A33 tablet</li> <li>Two more Droid 4</li> </ul> <p>The Nokia N900 was missing from the stand as we forgot to bring one.</p> <p>The photos below show off parts of the stand, starting with an overview of the stand:</p> <img alt="" src="/images/openfest-2022-1.jpg" style="width: 666px; height: 375px;" /> <p>Here is the tablet that <tt class="docutils literal">freemangordon</tt> has made Leste work on (there are no dd'able images online at the moment):</p> <img alt="" src="/images/openfest-2022-2.jpg" style="width: 666px; height: 375px;" /> <p>Below is an OLIMEX LIME2 (Allwinner A20) board with a resistive 7&quot; screen (800x480px) in a <a class="reference external" href="https://www.olimex.com/Products/OLinuXino/LCD/LCD7-METAL-FRAME/">LCD Metal Frame</a> box, with both a USB wifi dongle and an OLIMEX <a class="reference external" href="https://www.olimex.com/Products/IoT/LTE/USB-gLINK-ANT/open-source-hardware">USB LTE module</a>. This device was actually quite cool, since it was able to send SMSes and make phone calls, just without the audio routing that one would usually expect from a phone call (the USB LTE module doesn't allow for this). As such, it was basically a Maemo Leste tablet that can make phone calls. Various attendees used the device to call themself and noticed that indeed worked.</p> <p>In this photo, it is showing a Jabber chat in Conversations.</p> <img alt="" src="/images/openfest-2022-3.jpg" style="width: 666px; height: 375px;" /> <p>We also had some cool propaganda stickers made for the conference, which were quite popular.</p> <img alt="" src="/images/openfest-2022-4.jpg" style="width: 666px; height: 375px;" /> </div> <div class="section" id="documentation"> <h3>Documentation</h3> <p>We're working with a few folks to develop a centralised and organised place for developer documentation, and also to create a user guide. Hopefully we'll have something to share in a month or two.</p> </div> <div class="section" id="legal-entity-association"> <h3>Legal entity: Association</h3> <p>Maemo Leste is now a registered non profit association in the public interest in the country of Bulgaria (<a class="reference external" href="https://portal.registryagency.bg/CR/en/Reports/ActiveConditionTabResult?uic=206961328">see the registration here</a>). This makes it easier to purchase and send hardware to interested developers and allows us fund developers using the money we have left over from previous funding rounds (some people who worked on the funding projects decided to donate the funding they got to the association). The association is legally prohibited from selling anything and currently consists of 8 founding members.</p> </div> <div class="section" id="jenkins"> <h3>Jenkins</h3> <p>Our Jenkins CI (Continuous Integration) setup, which we use to build all the packages for Maemo Leste was running into problems where its hard disk was filled up. We realised that <strong>every single build we ever did was saved to disk</strong>, which was causing it to fill up. Going forward, only the last three successful builds of each package are now saved.</p> </div> <div class="section" id="themes"> <h3>Themes</h3> <p>We've been looking at using AI to upscale some of the background images of our themes using Real-ESRGAN. Most of themes were developed only for the Nokia N900, with a screen resolution of 800x480 - this makes many of the theme backgrounds looks a little ugly on the larger devices that we have. We've made pretty good progress with this, and hopefully in the next few weeks we'll push out a few 'upscaled' themes that genuinely look better on higher resolution screens.</p> <p>The work on the beta theme can be examined <a class="reference external" href="https://wizzup.org/dirlist/maemo-leste/theme-upsample/beta/">in this directory</a>.</p> </div> <div class="section" id="tor-hidden-service"> <h3>Tor Hidden Service</h3> <p>Maemo Leste now has a Tor hidden service for its package repository. The URL is: <a class="reference external" href="http://maemopkgove3kc2xxzyuk26j3ict6qzbqi3govge3s6h5aokr2uo6eqd.onion">http://maemopkgove3kc2xxzyuk26j3ict6qzbqi3govge3s6h5aokr2uo6eqd.onion</a></p> <p>See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/570">issue #570</a> for a list that also includes the Devuan hidden service URL. Users will have to install <tt class="docutils literal"><span class="pre">apt-transport-tor</span></tt> for this to work.</p> </div> <div class="section" id="lapdock"> <h3>Lapdock</h3> <p><tt class="docutils literal">Blago</tt> received a Motorola Lapdock and he managed to hook the Motorola Droid 4 up to it. Here is a frontal view:</p> <img alt="" src="/images/lapdock-front-view.jpg" style="width: 585px; height: 439px;" /> <p>A view from the side, with the Motorola Droid 4 being visible in the back:</p> <img alt="" src="/images/lapdock-side-view.jpg" style="width: 585px; height: 439px;" /> <p>Another view, but of the back of the lapdock:</p> <img alt="" src="/images/lapdock-back-view.jpg" style="width: 585px; height: 439px;" /> <p><tt class="docutils literal">Blago</tt> is still working on turning all of this into a package, but we will eventually have support for lapdocks (and other external displays, since this just attached to the HDMI port on the phone).</p> </div> <div class="section" id="extra-packages"> <h3>Extra packages</h3> <p><tt class="docutils literal">norayr</tt> has contributed various new packages:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste-extras/msid/">msid</a> - a sid player for the Maemo platform;</li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/live-wallpaper">live-wallpaper</a> support;</li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/shermans-aquarium-maemo">shermans-aquarium-maemo</a>, for a nice live aquarium background on your phone;</li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/mstardict">mstardict</a> - a frontend for star dict dictionary files. Also check out the <a class="reference external" href="https://leste.maemo.org/Extras/MStarDict">wiki page here</a>;</li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/easylist">easylist</a> - an application to manage lists of notes.</li> </ul> </div> <div class="section" id="translation-gui"> <h3>translation gui</h3> <p><tt class="docutils literal">sanderfoobar</tt> is working on an <strong>offline</strong> machine-based (neural network) translation tool, with both command line and user interface, for Maemo. It is based on the same models and code that are used by <a class="reference external" href="https://addons.mozilla.org/en-US/firefox/addon/firefox-translations/">Firefox Translations</a> - he hopes to present this work in some shape in the next few weeks. Currently it can translate a sentence in under a second from and to various European languages. The project welcomes any projects that provide these cool features without relying on cloud services.</p> </div> </div> <div class="section" id="what-s-next"> <h2>What's next</h2> <p>The author of this news post has made it a personal goal to switch from his Nokia N900 Fremantle phone to a Maemo Leste Droid 4 phone on February 1st, 2023 - exactly five years after the first Maemo Leste post. At that point, his contacts and messages will be imported onto the Droid 4 and the SIM will be moved.</p> <p>For this to be achieved, a few tasks will still need to be completed:</p> <ul class="simple"> <li>Finish our Chimaera port;</li> <li>Support Telepathy in sphone so that phone calls are managed using <tt class="docutils literal"><span class="pre">telepathy-ring</span></tt> instead of directly with <tt class="docutils literal">ofono</tt> - this will also help bring SIP and XMPP calls closer to working state;</li> <li>Support messaging contacts from conversations;</li> <li>Support incoming message notifications with conversations;</li> </ul> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900, Motorola Droid 3, Droid 4 and Bionic units available for interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know...</p> <img alt="" src="/images/massdroid.jpg" style="width: 666px; height: 375px;" /> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join our effort!</p> </div> 2022-04-16T09:00:00+02:002022-04-16T09:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2022-04-16:/maemo-leste-sixteenth-update-november-and-december-2021-january-april-2022.html

<p>The long overdue update is finally here, and it's our biggest update yet. (Also check out our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fifteenth-update-januari-october-2021.html">previous update</a> in case you missed it).</p> <p>These past few months have been heavily about stability and bug fixing, but there are some cool additions and improvements to our userspace as well, in …</p>

<p>The long overdue update is finally here, and it's our biggest update yet. (Also check out our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fifteenth-update-januari-october-2021.html">previous update</a> in case you missed it).</p> <p>These past few months have been heavily about stability and bug fixing, but there are some cool additions and improvements to our userspace as well, in particular to the communication and phone aspects of Maemo Leste.</p> <p>Here are a few highlights:</p> <ul class="simple"> <li>improved performance and stability for graphics drivers for OMAP / PowerVR based devices such as Nokia N900 and the Motorola Droid 3, Motorola Droid 4 and Motorola Bionic;</li> <li>graphics rendering problems on the Pinephone and Pinetab are all fixed;</li> <li>Nokia N900 kernel support is now based on 5.15 instead of 5.1 fixing many regressions along the way;</li> <li>addition of the Maemo contacts application and contacts library</li> <li>updates on the conversations application, phone call support and the telepathy framework and user interfaces;</li> <li>2-3 day battery life for the supported Motorola Droid devices</li> </ul> <div class="section" id="images-and-upgrading"> <h2>Images and upgrading</h2> <p>We are still very actively developing Maemo Leste, so many things remain in flux. As a result, you might have to occassionally update using <tt class="docutils literal">apt <span class="pre">dist-upgrade</span></tt> as opposed to just <tt class="docutils literal">apt upgrade</tt> - this is especially true for this update. Alternatively you can just install the latest images if things do break.</p> <p>In the past, sometimes Maemo Leste upgrades would cause unexpected reboots, breaking the system, we've tried to now solve those problems by <a class="reference external" href="https://github.com/maemo-leste/leste-config/blob/master/leste-config-common/usr/sbin/policy-rc.d.leste">preventing certain packages from restarting</a>. Additionally, the presence of the <a class="reference external" href="https://github.com/maemo-leste/leste-config/blob/master/leste-config-common/etc/no_lg_reboots.leste">/etc/no_lg_reboots</a> file will prevent the system from rebooting in cases where services do crash repeatedly.</p> <div class="section" id="new-images"> <h3>New images</h3> <p>We spin new images weekly, but for this blog post have checked that all of the supported devices (<tt class="docutils literal">n900</tt>, <tt class="docutils literal">droid3</tt>, <tt class="docutils literal">droid4</tt>, <tt class="docutils literal">bionic</tt>, <tt class="docutils literal">pinephone</tt>) boot fine. <a class="reference external" href="https://maedevu.maemo.org/images/">You can find the images here</a>.</p> </div> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="omap-and-powervr-drivers"> <h3>OMAP and PowerVR drivers</h3> <p><tt class="docutils literal">freemangordon</tt> has been working really hard together with some other Maemo Leste developers to move to the latest PowerVR drivers available - both in kernel and userspace. In addition to that, there is now <strong>2D EXA</strong> acceleration in X using the PowerVR drivers as well. This has been a multi-year effort by many people, and it's finally here, bringing all devices to the latest Linux kernels.</p> <p>This involved integrating and <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/mesa/commits/maemo/beowulf">improving on the chromium os PowerVR mesa driver</a> (which also brought all the devices up to a newer mesa version - <tt class="docutils literal">21.2.5</tt>), fixing up the <a class="reference external" href="https://github.com/maemo-leste/xf86-video-omap/commits/master">xf86-video-omap</a> driver to support EXA and fix up its buffer management, rotation support, as well as many fixes to the kernel, here are just a few:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/067976f0afd4a65bf32a3f450ee42f508a1b0612">https://github.com/maemo-leste/droid4-linux/commit/067976f0afd4a65bf32a3f450ee42f508a1b0612</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/7708a2ab996360826fa085374ca794cfd034cc4b">https://github.com/maemo-leste/droid4-linux/commit/7708a2ab996360826fa085374ca794cfd034cc4b</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/f56836db3ec4210c5cfaf40fa721a6e21cd7730e">https://github.com/maemo-leste/droid4-linux/commit/f56836db3ec4210c5cfaf40fa721a6e21cd7730e</a></li> </ul> <p>In addition to all of that impressive work, we're also hoping to finally enable the <strong>tear free</strong> operation of the Droid 4 display.</p> <p>The driver also improves stability and fixes various crashes in the previous drivers. The driver is available immediately for the Nokia N900, Motorola Droid 3, Motorola Droid 4 and Droid Bionic.</p> <p>The Nokia N900 won't support rotation yet, but at least it will <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/578">no longer segfault</a> - we know what needs to be done to support rotation, and it's in the works.</p> <p>Some more background information can be found in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/524">issue #524</a>.</p> </div> <div class="section" id="pinephone-mesa-and-clutter"> <h3>Pinephone, Mesa and Clutter</h3> <p>Maemo Leste on the Pinephone suffered from various graphical glitches, but these have now all finally been resolved. There were various problems to resolve, the first one was in clutter, <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/clutter-0.8/commit/13903d341009266d0bfa19806e74625a16ab552a">which assumed that the display drivers were not using double buffering</a>, even though they in fact were.</p> <p>Once that was fixed, another problem surfaced, regarding the preservation of EGL buffers in Mesa. Clutter relies on the fact that the buffers are preserved, <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/clutter-0.8/commit/6f753308446ff833d8c2713357cdc97d94dcb15b">but didn't actually request that support</a>. However, requesting the support was not enough, because Mesa doesn't (always) implement the feature, for which we <a class="reference external" href="https://gitlab.freedesktop.org/mesa/mesa/-/issues/5800">filed this report</a> at mesa.</p> <p><tt class="docutils literal">enunes</tt> was particularly instrumental in helping working around the problem. providing us with a <a class="reference external" href="https://github.com/maemo-leste-upstream-forks/mesa/commit/dde856128e67b0d3760cd3b8fa95c4c1463168bd">minimal stop-gap patch</a> to add support for this feature to mesa while we improve clutter further to switch to buffer age extensions, rather than relying on this feature being available.</p> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>The Nokia N900 was stuck on Linux 5.1 for quite a long time in Maemo Leste, because of the aforementioned graphics driver troubles, which have now finally been resolved. As such we set forth to move to the latest Linux kernel only to found that the support was once again quite broken. More precisely:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/fa7c9a0d1cecf00579b7388f64393ea26c9433d5">Wifi was broken</a> (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/572">see issue #572</a>)</li> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/4f9a153a44cb4a4d34e265e451da507b64e042cd">LEDs were broken</a> (also <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/af2872bfcd6eb527b227b79fddbf6927952c9f86">device tree work was required)</a>;</li> <li>OFF mode was never being hit again <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/b119ddd34750b1a9e2d66745912a2fe9479b85fe">due to memory compaction</a> and <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/a42cb7d0afcde0d4c1dfdfbb6f5eb33597387481">thermal driver changes</a>;</li> <li>The <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/2c7e4a1ac8ec1f908927793e893566aac3dcb9df">N900 modem driver would panic and reset the device upon usage</a>;</li> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/083a17e41a4a9b44ac37de26e5ac357289248e6b">Automatically turning on OFF mode caused race conditions during boot that causes resets</a>;</li> </ul> <p>After spending a week bisecting to find all the various problems, various fixes have already made it mainline, but other breakage still needs more investigate before we can send a fix upstream, but at least our kernel carries the necessary fixes and reverts.</p> <p>We've also unified the Droid 4 and N900 kernel, so all this work can now be found here (the repository will be renamed to <tt class="docutils literal"><span class="pre">omap-linux</span></tt> in due time):</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commits/wip/n900/maemo-5.15-cleaned-up">https://github.com/maemo-leste/droid4-linux/commits/wip/n900/maemo-5.15-cleaned-up</a></li> </ul> <p>As part of the kernel unification, we also created <a class="reference external" href="https://github.com/maemo-leste/maemo-kernel-config">maemo-kernel-config</a> to create kernel images that are N900 u-boot compatible.</p> <p>We're also still working on further Nokia N900 power management improvements, to this end we have created the <a class="reference external" href="https://github.com/maemo-leste/n900-pm">n900-pm script</a>, and have starting improving power management of various drivers (touchscreen work <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/fbe57fb618ffefaed2526acfc3d53b8a8a6fcc79">to use runtime pm</a> and to <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/commit/1fb2c44148536463875bb1d4bbb35c617d7b72e7">disable irqs upon suspend</a> already help some), but there are more drivers that need to be worked on.</p> <p>This <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/545">long github issue</a> details some of the things we went through to get the N900 back in shape.</p> <p>As of writing, we now run the N900 on Linux 5.15 (see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/587">issue #587</a>), and will soon switch to 5.16 or 5.17 in our development channel(s).</p> <p><a class="reference external" href="https://twitter.com/maemoleste/status/1469852192848941058">We also tweeted about this work</a> in what turned out to be our most popular tweet so far.</p> </div> <div class="section" id="motorola-droid-3-droid-4-bionic"> <h3>Motorola Droid 3, Droid 4, Bionic</h3> <div class="section" id="headphone-plug-events"> <h4>Headphone plug events</h4> <p>The Droid 4 (and other mapphones) now support detecting the (un)plugging of a headphone, to ensure that audio is routed properly.</p> </div> <div class="section" id="droid-3-images"> <h4>Droid 3 images</h4> <p>After reporting on the Droid 3 port in the previous update, we are now also offering images for the Droid 3. It's a neat device, much like the Droid 4, feels more sturdy, but comes with less RAM. We still have more issues to work on for the Droid 3 port, though - in particular there is still a common problem where the Droid 3 freezes and resets.</p> <p>The latest Droid 3 image can be found here - keep in mind that a special clownboot kexec bootloader setup is still required (<a class="reference external" href="https://github.com/MerlijnWajer/bionic-clown-boot/tree/solana">see the instructions here</a>).</p> </div> <div class="section" id="power-management"> <h4>Power management</h4> <p>A new mce module called <a class="reference external" href="https://github.com/maemo-leste/mce/commit/f25e8f20562a358d3df37c14e5d7b8639ec869c8">quirks-mapphone</a> has been introduced, introducing additional power saving mechanisms. For example, it will cause the modem not to report on signal strength if the device screen is turned off, which prevents waking up ofono, and then D-Bus, and then programs that listen for ofono on D-Bus. The module also turns off the secondary CPU to prevent additional wakeups (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/594">issue #594</a>), but only if the screen is turned off.</p> <p><tt class="docutils literal">freemangordon</tt> improved the responsiveness of the module somewhat, leading to faster screen lock and unlock (see <a class="reference external" href="https://github.com/maemo-leste/mce/pull/52/files">mce PR #52</a>).</p> <p>Below is a screenshot from a Motorola Droid 4 with a used battery, showing that it has two days of online time left. Keep in mind that this means the device would be online all the time - this is not about suspend to ram time (which is not necessary on OMAP4). Similar time estimates can be expected on the Droid 3 and the Bionic, and there are still things to improve upon. OMAP4 does not yet support <tt class="docutils literal">OFF</tt> mode, but when it does we suspect we will see further power savings. One audio clock also isn't always gated yet, once we figure out why that is the case, we could save a few more milliwatts.</p> <img alt="" src="/images/droid4-2days.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p><tt class="docutils literal">rafael2k</tt> has helped getting our PinePhone support into much better shape. We now ship a 5.15-based kernel fixing up the modem support and audio during phone calls.</p> <p>We now also have a package for <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/327">PinePhone bluetooth firmware</a>. Combined with the graphics updates mentioned in <a class="reference internal" href="#pinephone-mesa-and-clutter">Pinephone, Mesa and Clutter</a> and supported for the <a class="reference external" href="https://github.com/maemo-leste/pine64-kernel/pull/2">light and proximity sensor</a>, the Pinephone is in good shape - better than it has ever been on Maemo Leste.</p> <p>Last but definitely not least, our newer PinePhone kernel images also support the hardware keyboard case for the PinePhone.</p> </div> </div> <div class="section" id="core-software-additions-and-changes"> <h2>Core Software additions and changes</h2> <div class="section" id="osso-abook-addressbook"> <h3>osso-abook (addressbook)</h3> <p>After many months of hard work (maybe even years), the <a class="reference external" href="https://github.com/maemo-leste/osso-abook/">Maemo addressbook library</a> is now ready and the <a class="reference external" href="https://github.com/maemo-leste/osso-addressbook">Contacts user interface</a> based on the library is also shaping up nicely.</p> <p>Importing contacts from a Fremantle Nokia N900 works, and synchronising them with remote servers using syncevolution has also been reported to work. The email client (<cite>modest</cite>) has already integrated support for the address book.</p> <img alt="" src="/images/contacts.png" style="width: 576px; height: 324px;" /> <p>The screenshot above shows the contact overview from the main &quot;Contacts&quot; application - applications can also embed this view or use it as a dialog. All the contacts imported from a Nokia N900 that has been in use for over 10 years.</p> <img alt="" src="/images/contacts-myinformation.png" style="width: 576px; height: 324px;" /> <p>This is the screen of the personal information of the user of the device.</p> <img alt="" src="/images/contacts-settings.png" style="width: 576px; height: 324px;" /> <p>Some of the contact settings are not fully implemented yet - for example, we don't support video calling yet, but at least the setting is there.</p> <img alt="" src="/images/contacts-options.png" style="width: 576px; height: 324px;" /> <p>This screenshot shows the context menu of the contacts application in the overview window.</p> <img alt="" src="/images/contacts-newcontact.png" style="width: 576px; height: 324px;" /> <p>Creating new contacts is also possible!</p> </div> <div class="section" id="conversations"> <h3>conversations</h3> <p>We've been working on an open source replacement for the Conversations application, with many of the core components written by a newcomer - <tt class="docutils literal">dsc</tt>. The <a class="reference external" href="https://github.com/maemo-leste/conversations">replacement is written in Qt5 and QML</a>, and can currently read and show the rtcom communications database, but has only limited addressbook integration. We have had some luck integrating Telepathy, and both sending and receiving SMS/IRC/XMPP messages works (including logging the messages to the RTcom database), but the code is not yet available in the package repositories, as there are still some bugs to solve when using multiple Telepathy accounts.</p> <p>For it to fully work, more work is also required for the Telepathy integration in other parts of the system, in particular we need to get some of the other RTCom components in place. <a class="reference external" href="https://leste.maemo.org/User:Wizzup/Telepathy">This wiki page</a> contains some notes on the various components, but it hasn't been kept up to date with the latest developments yet.</p> <p>The following still needs to be fixed up or outright implemented:</p> <ul class="simple"> <li>Support for starting a new chat with a potentially unknown contact</li> <li>Support for multi-person chat rooms</li> <li>Support for multiple accounts (this should in theory work, but we have to debug how we use Telepathy Qt here)</li> <li>Various UI improvements to clearly separate the different protocols</li> <li>Better support for system themes, some of the assets are currently semi-hardcoded in the QML files</li> </ul> <p>Nevertheless - here are some screenshots of the current application.</p> <p>The screenshot below shows the recent messages overview, scrolling in this screen is also very smooth.</p> <img alt="" src="/images/conversations-overview.png" style="width: 576px; height: 324px;" /> <p>The settings in Conversations are currently limited to switching between the built-in themes and changing the text scaling.</p> <img alt="" src="/images/conversations-settings.png" style="width: 576px; height: 324px;" /> <p>The chat view of a specific conversation typically looks something like this</p> <img alt="" src="/images/conversations-dapsi-message-view-landscape.png" style="width: 576px; height: 324px;" /> <p>and it works in portrait mode, too!</p> <img alt="" src="/images/conversations-dapsi-message-view.png" style="width: 324px; height: 576px;" /> <!-- .. image:: /images/conversations-dapsi-message-view-irssitheme.png --> <!-- :width: 324px --> <!-- :height: 576px --> <p>And of course, we just have to show off the irssi theme...</p> <img alt="" src="/images/conversations-dapsi-message-view-irssitheme-landscape.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="rtcom-accounts-ui"> <h3>rtcom-accounts-ui</h3> <p>The user interface to configure communication accounts is <tt class="docutils literal"><span class="pre">rtcom-accounts-ui</span></tt>, which <tt class="docutils literal">freemangordon</tt> has also been working on. Currently there is already a control panel plugin, which allows configuring a XMPP account. We will be integrating this into conversations Telepathy support, at which point we should soon have working communications for many protocols. At that point, we'll add more plugins for <tt class="docutils literal"><span class="pre">rtcom-accounts-ui</span></tt> to support more protocols.</p> <p>The last piece of this work will be getting <tt class="docutils literal"><span class="pre">rtcom-presence-ui</span></tt> into shape, which adds presence and also (we believe) managing the online status of the Telepathy accounts of the user.</p> <p>These screenshots show the control panel applet in action (and no, we didn't forget to remove the email address or name):</p> <img alt="" src="/images/rtcom-accounts-list.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/rtcom-account-edit.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/rtcom-account-advanced.png" style="width: 576px; height: 324px;" /> <p>The relevant repositories are here:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/libaccounts">https://github.com/maemo-leste/libaccounts</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-ui">https://github.com/maemo-leste/rtcom-accounts-ui</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-plugin-gtalk">https://github.com/maemo-leste/rtcom-accounts-plugin-gtalk</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/rtcom-accounts-ui-client">https://github.com/maemo-leste/rtcom-accounts-ui-client</a></li> </ul> </div> <div class="section" id="sphone"> <h3>sphone</h3> <p>The sphone dialer application has gained basic support for the Maemo address book, and it can also write text and call events to the RTCom database. This means that all incoming messages and calls are being logged (that's a good thing) -- in the future other applications (like conversations) will likely deal with the logging of incoming messages, though.</p> <img alt="" src="/images/sphone-contacts.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="charging-mode"> <h3>charging-mode</h3> <p>Our latest images (and also upgraded devices) now ship with a feature called &quot;charge mode&quot;, which will boot to a special charging-only mode when the phone starts with a usb cable providing power. This was created (based on existing software) by <tt class="docutils literal">uvos</tt>, and here is a video he made to show off the work:</p> <video controls height="480px" width="720px"> <source src="images/charge-mode.webm" type="video/webm"> </video></div> <div class="section" id="virtual-keyboard"> <h3>Virtual keyboard</h3> <p>The virtual keyboard has a mode where it only shows special keys - this had silently been broken but has since been fixed.</p> </div> <div class="section" id="maemo-launcher"> <h3>maemo-launcher</h3> <p>maemo-launcher has seen some fixes with regards to resolving symlinks that are multiple levels deep, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/484">issue #484</a>. This helps selecting alternative default terminal applications.</p> </div> <div class="section" id="hildon-desktop"> <h3>hildon-desktop</h3> <p><tt class="docutils literal">uvos</tt> fixed a particularly interesting bug in hildon-desktop where scrolling the applications would immediately stop scrolling when the touch event ended (i.e. the user stopped touching the touch screen), this was ultimately related to a time overflow, and since <tt class="docutils literal">Fri May 15 02:09:25 2015 UTC</tt> the scroll events were no longer smooth. See <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/17">PR 17</a> for more details.</p> <p>hildon-desktop also now <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/18">quotes commands send to the terminal emulator</a>, ensuring that the commands get through correctly.</p> <p>libhildondesktop will now also (re)load applications and widget applets upon install, <a class="reference external" href="https://github.com/maemo-leste/libhildondesktop/commit/b672af1a60fadbf0453befb908ebf4fc74312b8d">fixed in this commit</a>, for some more information, one can also check out <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/459">issue 459</a>.</p> <p>GTK 3 and higher applications now render properly in fullscreen mode, see this <a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/8">libmatchbox PR #8</a>.</p> </div> <div class="section" id="volume-applet"> <h3>Volume applet</h3> <p>It is now possible to change the volume of the headphones or speakers (depending on what is active) using the volume buttons. <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume/pull/1">maemo-statusmenu-volume pull request #1</a> and the follow up <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume/pull/2">pull request #2</a> made this possible.</p> <img alt="" src="/images/volume-applet.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="additional-software-changes"> <h2>Additional Software changes</h2> <div class="section" id="ofono"> <h3>ofono</h3> <p>The ofono version for all our supported devices has been updated to a more recent release - ofono 1.34. We've additionally also merged in some more patches for better pinephone support (see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/597">issue #597</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/598">issue #598</a>)</p> <p>Having all devices on the same ofono package also helps with maintainability!</p> </div> <div class="section" id="gtk2"> <h3>gtk2</h3> <p>Our Gtk2 sliders weren't as repsonsive to touch input as they should be, due to some Maemo patches that were missing. This is now fixed, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/582">issue #582</a> for more info.</p> <!-- libicd-network-wpasupplicant --> <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> <!-- --> <!-- * libicd-network-wpasupplicant segfault fix when net->type NULL --> </div> <div class="section" id="themes-on-images"> <h3>Themes on images</h3> <p>At some point, loading themes was broken on our 32bit image builds (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/599">see issue #599</a> for what that looks like), but this has since been fixed. The problem turned out to be a problem in QEMU where <cite>readdir()</cite> would fail for a 32 bit guest on a 64 host. We worked around this problem by adding an additional image building machine that is 32 bit.</p> </div> <div class="section" id="pulseaudio-configuration"> <h3>Pulseaudio configuration</h3> <p>We have improved the pulseaudio setup on the devices, in particular:</p> <ul class="simple"> <li>We now set the correct default audio sink on the Pinephone</li> <li>All devices should now automatically switch upon headphone plug or unplug events, using the switch on port module</li> <li>We have added the ability to add arbitrary other config files in the <tt class="docutils literal">/etc/pulse/leste.pa.d</tt> directory.</li> </ul> </div> <div class="section" id="system-log-rsyslog-configuration-changes"> <h3>System log (rsyslog) configuration changes</h3> <p>The latest <tt class="docutils literal"><span class="pre">leste-config</span></tt> separates out the logging so that it is easier to track down problems by reviewing the logs. Some daemons got their own log files in <tt class="docutils literal">/var/log/maemo</tt>, like <tt class="docutils literal">icd2</tt>, <tt class="docutils literal">mce</tt>, <tt class="docutils literal">ofono</tt>, <tt class="docutils literal">dsme</tt>, and so on. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/588">issue #588 for some more details</a>.</p> </div> <div class="section" id="debugfs-entries-in-fstab"> <h3>Debugfs entries in fstab</h3> <p>Upon installation of the <tt class="docutils literal"><span class="pre">leste-config</span></tt> package, the install scripts will check if <tt class="docutils literal">debugfs</tt> is present in <tt class="docutils literal">/etc/fstab</tt>, and if not, it will add a line to mount it. This will not remain the case forever (as it can potentially lead to more security issues), but various kernel power management tweaks are only available through <tt class="docutils literal">debugfs</tt>, so for now we have to keep it mounted.</p> </div> <div class="section" id="default-dns-server-if-none-is-provided"> <h3>Default DNS server if none is provided</h3> <p>In some rare cases where a network does not provide a DNS server over DHCP, devices running Maemo Leste would not be able to resolve any addresses over DNS, as no server was available.</p> <p>We have decided to default to <cite>9.9.9.9</cite> (aka &quot;Quad9&quot;) if nothing else is available. In the future we might replace this by just running a recursive DNS resolver on the device itself. See <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ipv4/commit/49afd837bf5a7764c0cc59854aad2b01175088a4">this commit on libicd-network-ipv4</a> for some more information. <strong>We also very much welcome feedback</strong> regarding alternative or better default DNS servers - we have simply tried to make a decision based on privacy and availability.</p> </div> <div class="section" id="libsdl1-environment-variables-and-enabling-glesv1-in-mesa"> <h3>libsdl1 environment variables and enabling GLESv1 in mesa</h3> <p>For some reason, Debian no longer enabled OpenGLES 1.0 in the Mesa builds. We have changed that in our Mesa build, once again enabling GLESv1.</p> <p>Additionally, we have added some enviroment variables that make SDL prefer EGL over GLX, as that is generally better supported on our devices.</p> </div> <div class="section" id="cssu-features-configuration-editor"> <h3>CSSU Features Configuration Editor</h3> <p>We have ported the <a class="reference external" href="http://wiki.maemo.org/CSSU_Features_Configuration_Editor">CSSU features program</a> from Maemo Fremantle's CSSU. This tools allows customising various parts of hildon-desktop and animations in the environment in general. The port is still work in progress, as some of the original user interface design files seemingly were not included in the source package (and yes there is a small menu key <cite>Main</cite> in the top right that shouldn't be there :-)).</p> <p>The port is somewhat noteworthy since it's a Python Qt5 package using hildon specific features.</p> <img alt="" src="/images/cssufeatures.png" style="width: 576px; height: 324px;" /> </div> </div> <div class="section" id="community-and-supporting-software-updates"> <h2>Community and supporting software updates</h2> <div class="section" id="keyring-and-jenkins-updates"> <h3>Keyring and Jenkins updates</h3> <p>Our key for the &quot;extras&quot; repository silently expired (not the first time), but now we had an easier way to providing updates, by just updating our keyring package. We have also upgraded our Jenkins instance to the latest version(s), and are working on adding a Honeycomb LX2 machine for fast ARM package builds.</p> </div> <div class="section" id="mediawiki-theme"> <h3>Mediawiki theme</h3> <p>IRC user <tt class="docutils literal">ashley</tt> contributed a forward-port of the old Maemo mediawiki theme as a selectable theme on our wiki, <a class="reference external" href="https://leste.maemo.org/index.php?title=Tor&amp;useskin=maemo">and you can preview it here</a>. If you like the theme, you can make it the default from the preferences in mediawiki. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/590">issue #590</a> for some more information.</p> </div> </div> <div class="section" id="what-s-next"> <h2>What's next</h2> <p>Getting Telepathy support for conversations fully worked out together with the RTCom applications will be an amazing thing for our mobile operating system. Once that is working well, we can start adding support for more protocols (we're working on a Telepathy signal plugin using signald), and perhaps also fix up telepathy-hazy, which allows running many Pidgin (libpurple) protocols inside Telepathy.</p> <p>From a stability standpoint, there are some bugs to be investigated still, in particular for the ofono support of the Droid series that we support. There are also some things to improve further for 2D/3D support, but it's looking much better than before.</p> <p>This year we also hope to switch to the new Devuan chimaera (Debian bullseye) release, further modernising our codebase and building on top of the latest and greatest that the free software community has to offer.</p> <p>Finally, we're slowly but surely getting all our of userland in place, while still heavily working on device support for the devices we support. Once userland is more or less complete, it will probably get much easier to port Maemo Leste to other (potentially newer) devices, so look forward to that too.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900 and Motorola Droid 3, Droid 4 and Bionic units available for interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2021-10-28T00:00:00+02:002021-10-28T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2021-10-28:/maemo-leste-fifteenth-update-januari-october-2021.html

<p>The long overdue update is finally here, it's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fourteenth-update-july-august-september-october-november-december-2020.html">last update</a>.</p> <p>Here are a few highlights:</p> <ul class="simple"> <li><a class="reference internal" href="#sphone">sphone</a> call interface;</li> <li><a class="reference internal" href="#modest">modest</a> (mail client);</li> <li><a class="reference internal" href="#gps-interfaces">GPS interfaces</a>;</li> <li>support for <a class="reference internal" href="#tor-wireguard-and-openvpn">Tor, Wireguard and OpenVPN</a>;</li> <li>many <a class="reference internal" href="#mce">mce</a> improvements;</li> <li><a class="reference internal" href="#funding-update">Funding update</a>;</li> <li><a class="reference internal" href="#motorola-droid-3-xt862">Motorola Droid 3 (XT862)</a> port;</li> <li><a class="reference internal" href="#audio-support">Audio support</a> progress;</li> <li><a class="reference internal" href="#address-book">address book</a> progress …</li></ul>

<p>The long overdue update is finally here, it's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fourteenth-update-july-august-september-october-november-december-2020.html">last update</a>.</p> <p>Here are a few highlights:</p> <ul class="simple"> <li><a class="reference internal" href="#sphone">sphone</a> call interface;</li> <li><a class="reference internal" href="#modest">modest</a> (mail client);</li> <li><a class="reference internal" href="#gps-interfaces">GPS interfaces</a>;</li> <li>support for <a class="reference internal" href="#tor-wireguard-and-openvpn">Tor, Wireguard and OpenVPN</a>;</li> <li>many <a class="reference internal" href="#mce">mce</a> improvements;</li> <li><a class="reference internal" href="#funding-update">Funding update</a>;</li> <li><a class="reference internal" href="#motorola-droid-3-xt862">Motorola Droid 3 (XT862)</a> port;</li> <li><a class="reference internal" href="#audio-support">Audio support</a> progress;</li> <li><a class="reference internal" href="#address-book">address book</a> progress;</li> <li>our plan for sms and <a class="reference internal" href="#conversations">conversations</a>;</li> </ul> <div class="section" id="funding-update"> <h2>Funding update</h2> <p>Since our <a class="reference external" href="https://maemo-leste.github.io/funding-from-ngi-eu.html">NGI funding announcement</a> we've been working hard on finishing the milestones as proposed. The <a class="reference internal" href="#tor-wireguard-and-openvpn">Tor, Wireguard and OpenVPN</a> integration is finished and available in the extras repositories.</p> <p>Following the successful completion of this milestone, the <a class="reference external" href="https://dapsi.ngi.eu">DAPSI</a> project has let us know that Maemo Leste has successfully moved into the second phase of the funding!</p> <p>This is great news, and means that we will hopefully be able to deliver on the next milestones of the funding soon, including:</p> <ul class="simple"> <li>&quot;Conversations&quot; UI, using Telepathy to support various protocols (SMS, IRC, XMPP, Matrix, GNU Jami aka ring, Signal)</li> <li>Implementation of some of the above protocols in Telepathy</li> <li>Improve the Maemo sharing libraries</li> </ul> </div> <div class="section" id="core-software-additions-and-changes"> <h2>Core Software additions and changes</h2> <p>There were lots of improvements in the networking stack, as well as to many of the core daemons, this section aims to give a comprehensive overview of all the changes.</p> <div class="section" id="modest"> <h3>modest</h3> <p>modest, the Maemo mail client <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/207">has been brought to Maemo Leste</a>. It relies on <a class="reference external" href="https://github.com/maemo-leste/tinymail">tinymail</a> and <a class="reference external" href="https://github.com/maemo-leste/gtkhtml3">gtkhtml3</a>.</p> <p>We will later on port modest to a newer HTML rendering framework.</p> <img alt="" src="/images/modest-1.jpg" style="width: 576px; height: 324px;" /> <img alt="" src="/images/modest-2.jpg" style="width: 576px; height: 324px;" /> </div> <div class="section" id="gps-interfaces"> <h3>GPS interfaces</h3> <p>We've been continuing our work on the GPS stack and liblocation, packaging various GPS interfaces and fixings bugs as we find them.</p> <p>Currently, there are at least four interfaces in our repositories, they've also gotten their own pages on the wiki:</p> <ul class="simple"> <li><a class="reference external" href="https://leste.maemo.org/Extras/modrana">https://leste.maemo.org/Extras/modrana</a> (more info: <a class="reference external" href="https://wiki.maemo.org/ModRana">https://wiki.maemo.org/ModRana</a>)</li> <li><a class="reference external" href="https://leste.maemo.org/Extras/maep">https://leste.maemo.org/Extras/maep</a></li> <li><a class="reference external" href="https://leste.maemo.org/Extras/cloudgps">https://leste.maemo.org/Extras/cloudgps</a></li> <li><a class="reference external" href="https://leste.maemo.org/Extras/gpsrecorder">https://leste.maemo.org/Extras/gpsrecorder</a></li> </ul> <p>Exporting the GPS logs from gpsrecorder or maep also works fine, as we have shared in <a class="reference external" href="https://twitter.com/maemoleste/status/1389277775664721923">this cycling tweet</a>.</p> </div> <div class="section" id="tor-wireguard-and-openvpn"> <h3>Tor, Wireguard and OpenVPN</h3> <div class="section" id="tor"> <h4>Tor</h4> <p>Tor <a class="reference external" href="https://www.torproject.org/">The Onion Router</a> is software that provides anonymous communication (over the Internet). We've integrated it in Maemo Leste's connectivity framework and user interface.</p> <p>There is a <a class="reference external" href="https://leste.maemo.org/Tor">Tor wiki page</a> with more screenshots and some examples on how to use it. Most of the source code is in the <a class="reference external" href="https://github.com/maemo-leste/libicd-tor">libicd-tor</a> repository.</p> <p>Probably the most simple way to use this code is to install it from the package manager, restart the device and configuring Tor to &quot;Enable Transparent proxying&quot;, which will cause all the traffic of the device to be transmitted over Tor. The screenshot below shows a Droid 4 with Tor with transparent proxying enabled.</p> <img alt="" src="/images/tor-check.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="wireguard"> <h4>Wireguard</h4> <p>Wireguard is a relatively new and simple communication protocol that implements an encrypted Virtual Private Network (VPN). There are many use cases, but a few examples are adding your phone to a Wireguard network that makes it possible to access your LAN from wherever you are, give your device a public IPv4 address, or otherwise tunnel traffic via another machine.</p> <p>There is a <a class="reference external" href="https://leste.maemo.org/Wireguard">Wireguard wiki page</a> with more screenshots and some examples on how to use it. Most of the source code is in the <a class="reference external" href="https://github.com/maemo-leste/libicd-wireguard">libicd-wireguard</a> repository.</p> <p>The screenshow below shows a Droid 4 with Wireguard enabled over wifi, and some interface statistics using <tt class="docutils literal">wg show</tt>.</p> <img alt="" src="/images/wg-show.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="openvpn"> <h4>OpenVPN</h4> <p>The OpenVPN applet and ICD2 plugin is also available, but hasn't seen quite as much testing as the <a class="reference internal" href="#tor">Tor</a> and <a class="reference internal" href="#wireguard">Wireguard</a> plugins.</p> <p>The source can be found here: <a class="reference external" href="https://github.com/maemo-leste/libicd-openvpn">https://github.com/maemo-leste/libicd-openvpn</a></p> </div> <div class="section" id="connui-providers"> <h4>connui providers</h4> <p>Maemo Fremantle supported a feature that wasn't really used much, which were the <a class="reference external" href="http://maemo.org/api_refs/5.0/5.0-final/icd2/group__icd__srv__provider.html">ICD2 service providers</a>, which are a way to add connection &quot;plugins&quot; to specific connections. The example provided was a plugin to disable network logon pages and (automatically) deal with those. We have extended this ICD2 implementation to support Tor, Wireguard and OpenVPN.</p> <p>Since there wasn't too much documentation how this integrated with the rest of the system, we developed <a class="reference external" href="https://github.com/maemo-leste/libicd-provider-dummy/">libicd-provider-dummy</a> to explore how the rest of the system interacts with service providers. For example, service providers can change the icon of the network in the status area, they can add additional icons in the connection dialogs and network status, and also provide customisation of the network names.</p> <p>The code written to support providers in the connui interfaces can be found here in this <a class="reference external" href="https://github.com/maemo-leste/connui-internet/pull/2/">connui-internet pull request</a> and this <a class="reference external" href="https://github.com/maemo-leste/connui-common/pull/1">connui-common pull request</a>.</p> <p>Below is an example of an IAP being configured to use Wireguard service provider - this means it will always connect to Wireguard when connecting to the IAP, and if connecting to Wireguard fails, the network connection will be severed.</p> <img alt="" src="/images/wireguard-provider.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/wireguard-provider-cfg.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="resolvconf"> <h4>resolvconf</h4> <p>Due to the way <tt class="docutils literal"><span class="pre">wg-quick</span></tt> from the Wireguard tools worked, we also had to overhaul our DNS scripts. We initially imported them from Maemo Leste, but recently upgraded them to use <a class="reference external" href="https://github.com/maemo-leste/libicd-network-ipv4/pull/3">resolvconf</a> (issue <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/583">#583</a>), making our setup more robust.</p> </div> </div> <div class="section" id="connui"> <h3>connui</h3> <p>Previously, the connection dialogs on Maemo Leste would malfunction if they invoked programmatically (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/539">#539</a>), this problem has been solved now.</p> </div> <div class="section" id="mce"> <h3>mce</h3> <p><strong>uvos</strong> has been consistently working on improving <tt class="docutils literal">mce</tt> and a lot has changed:</p> <ul class="simple"> <li>mce uses less memory (about 400kB) by using link time optimisations (LTO), <cite>--dynamic-list</cite> and a build system rewrite (<a class="reference external" href="https://github.com/maemo-leste/mce/pull/50">from plain Makefile to cmake</a>). LTO is not in use on Leste yet, as it still causes some problems with upower and tklock.</li> <li>Proximity sensor module based on the <a class="reference external" href="https://github.com/maemo-leste/mce/pull/17">iio system</a></li> <li>Legacy display module is <a class="reference external" href="https://github.com/maemo-leste/mce/pull/48">dropped</a></li> <li>The <cite>alarm</cite> module is now loaded (<a class="reference external" href="https://github.com/maemo-leste/mce/pull/46">PR #46</a>)</li> <li><a class="reference external" href="https://github.com/maemo-leste/mce/pull/49">rtconf</a> support has been added, allowing for using different backends, to make it easier to drop gconf support. Alternative backend types are <cite>ini</cite> files and <cite>gsettings</cite>.</li> <li><a class="reference external" href="https://github.com/maemo-leste/mce/pull/43">battery-guard</a> module was added</li> <li><a class="reference external" href="https://github.com/maemo-leste/mce/pull/47">power-generic</a> module that allows mce to operate in absence of dsme. In combination with the new <cite>lock-generic</cite> module, one can use xdg-screensaver instead of the hildon-specific lock screen.</li> </ul> <p>Additionally, mce now supports some more dbus interfaces for changing various settings, which were previously changed through gconf directly, which made for some awkward architecture:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/profiled/pull/2">https://github.com/maemo-leste/profiled/pull/2</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/osso-applet-display/pull/1">https://github.com/maemo-leste/osso-applet-display/pull/1</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/simple-brightness-applet/pull/2">https://github.com/maemo-leste-extras/simple-brightness-applet/pull/2</a></li> </ul> <!-- Profiles control panel applet --> <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --> <!-- --> <!-- TODO --> <!-- --> <!-- Some fixes, renamed --> <!-- https://github.com/maemo-leste/bugtracker/issues/569 --> </div> <div class="section" id="wireless"> <h3>Wireless</h3> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/489">Hidden access points are now supported</a> in what turned out to be long and painful process of debugging problems in <a class="reference external" href="https://github.com/maemo-leste/connui-internet/commit/181b42acf295ca32812ad6330e36c556d90cb3cb">connui-internet</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/489#issuecomment-881039662">wpasupplicant</a> itself and the <a class="reference external" href="https://github.com/maemo-leste/n9xx-linux/commit/a242bd68f75cf9d68935aaa6f32fa05f3e4d62e9">N900 linux kernel</a>.</p> <p>The network scanning dialog would sometimes render scanning results with a (long) delay, this is now fixed (issue <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/342">#342</a>).</p> </div> <div class="section" id="hildon-input-method"> <h3>hildon-input-method</h3> <p>hildon-input-method recently got some improvements where it can insert characters into windows that do not explicitly support hildon input method (like gtk2). The virtual keyboard can be summoned using dbus and can insert (currently only) english characters into plain X11 windows. See the video below showing how it works in Firefox (the touch screen button is used to summon the virtual keyboard).</p> <video controls height="480px" width="640px"> <source src="images/him-dbus.webm" type="video/webm"> </video><p>In the future, we plan to use the <a class="reference external" href="https://www.freedesktop.org/wiki/Accessibility/AT-SPI2/">at-spi</a> accessibility interface to make the hildon-input-method integration more complete and universal.</p> </div> <div class="section" id="hildon-desktop"> <h3>hildon-desktop</h3> <p>Since our last update, hildon-desktop has supported rotating the devices screen (and adjust the touch input accordingly to match the screen orientation). With this update, we've improved how that is implemented exactly to make it more robust. For example, upon certain updates the touch input would reset to the native orientation, which could be quite confusing. All of this is solved now by making this work directly in hildon-desktop, rather than other scripts that act on dbus signals.</p> <p>Maemo also sets more <tt class="docutils literal">XDG_*</tt> environment variables now to ensure that Hildon applications behave properly, and show the right directories, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/426">issue #426</a>.</p> <p>In some rare cases, hildon-desktop would not boot if the battery is very low, this is fixed now, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/435">issue #435</a>.</p> </div> <div class="section" id="osso-xterm"> <h3>osso-xterm</h3> <p>osso-xterm now opens links in the default browser, and the volume keys should <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/385">change the font size on the Droid 4 and similar devices</a>.</p> </div> <div class="section" id="audio-support"> <h3>Audio support</h3> <p>Maemo Leste has supported basic audio output since the very first release, but one of the many tricky parts of a mobile operating system is the audio routing. For example, when one receives an incoming phone call, any music that is playing should stop, and the ringtone sound should be heard. When a headphone is plugged in during a call, one would expect the audio to switch from earpiece to headphone, but, when a mediaplayer is playing music, unplugging the headphones should perhaps not necessarily lead to music being played on the speakers, as one might disturb others - so different outputs need their own volume control, which needs to be saved somewhere, and so forth.</p> <p>Many of these problems were solved in Maemo Fremantle, and much of that work made it into Sailfish OS (Mer Project), so we've gone full circle and have started packaging their work for Maemo. Here is a non-exhaustive list of packages that we have ported and packaged:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/ohm">https://github.com/maemo-leste/ohm</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/libdres-ohm">https://github.com/maemo-leste/libdres-ohm</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/libtrace-ohm">https://github.com/maemo-leste/libtrace-ohm</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/ohm-plugins-misc">https://github.com/maemo-leste/ohm-plugins-misc</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/pulse-core">https://github.com/maemo-leste/pulse-core</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/pulseaudio-policy-enforcement">https://github.com/maemo-leste/pulseaudio-policy-enforcement</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/pulseaudio-modules-nemo">https://github.com/maemo-leste/pulseaudio-modules-nemo</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/pulseaudio-module-cmtspeech-n9xx">https://github.com/maemo-leste/pulseaudio-module-cmtspeech-n9xx</a></li> </ul> <p>These modules should help us with the audio policy routing, but also contain device-specific support modules, for example in the case of the N900, where the packages should help routing audio to and from the modem during phone calls.</p> <p>More work remains to be done to integrate this on our devices, since audio policies are somewhat complex and many of the components aren't well known to us.</p> </div> <div class="section" id="sphone"> <h3>sphone</h3> <p><a class="reference external" href="https://github.com/maemo-leste/sphone">sphone is a ofono GUI</a> based on gtk, which <cite>uvos</cite> has been modernising and improving a bunch, aiming to make it modular with optional hildon/maemo support. In other words: it's a program that allows you to make phone calls on Maemo Leste, at least theoretically.</p> <p>The integration in Maemo Leste is still very much a work in progress, as is sphone, but it's already working to some degree, as can be seen in this video:</p> <video controls height="360px" width="640px"> <source src="/images/maemo-leste-sphone.webm" type="video/webm"> </video><p>Integration with the Maemo address book (and other address books) is also being worked on. Here's a screenshot of the interface is portrait mode:</p> <img alt="" src="/images/sphone-dialer.png" style="width: 324px; height: 576px;" /> <p>The application is only available in the <strong>-devel</strong> repositories.</p> </div> <div class="section" id="address-book"> <h3>address book</h3> <p>We're still working on fully implementing the Maemo Fremantle address book and contacts framework (osso-abook), but we've made a lot of progress - it should be ready pretty soon.</p> <img alt="" src="images/osso-abook-newcontact.png" style="width: 484px; height: 281px;" /> </div> <div class="section" id="conversations"> <h3>conversations</h3> <p>There is not a lot to report on this subject yet, besides what was mentioned in the <a class="reference internal" href="#funding-update">Funding update</a>.</p> <p>We aim to have the Conversations UI be a frontend for many Telepathy protocols (SMS just being one of them), using the existing (Maemo Fremantle) rtcom (Real Time Communication) framework. The widget set that we will use will likely be Qt, and we will likely using an existing Maemo application and strip out everything we don't need, and then add the parts we want.</p> <p>In concrete steps:</p> <ol class="arabic simple"> <li>Strip <a class="reference external" href="https://github.com/agamez/yappari">yappari</a> of all Whatsapp code, and re-use the GUI as conversations UI frontend - a lot will change, but the general UI is pretty usable;</li> <li>Add support for <a class="reference external" href="https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Architecture/RTCOM">RTCOM</a> using <a class="reference external" href="http://maemo.org/api_refs/5.0/5.0-final/eventlogger/">rtcom-eventlogger</a> and other plugins that might be required;</li> <li>Add a simple telepathy plugin (telepathy-ring for sms most likely);</li> <li>Modify the UI to support multiple protocols the way we want to;</li> <li>Look into user interfaces to modify telepathy protocol parameters;</li> <li>Add more telepathy protocols;</li> </ol> <p>Below is a low-resolution screenshot of what Yappari looks like on Maemo Fremantle - <strong>it is not a screenshot of our current conversations application</strong>.</p> <img alt="" src="images/yappari.jpg" /> </div> <div class="section" id="recovery-boot-option"> <h3>recovery boot option</h3> <p>We now feature a recovery boot option for various devices, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/505">issue #505</a> and <a class="reference external" href="https://github.com/maemo-leste/image-builder/pull/8">image-builder pull request 8</a>. This is not yet available for the Pinephone and N900, but it is for the Droid 3, Droid 4 and Droid Bionic.</p> </div> <div class="section" id="fbkeyboard"> <h3>fbkeyboard</h3> <p>The Maemo Leste emergency rescue boot mode now features a framebuffer keyboard, our modified version of it <a class="reference external" href="https://github.com/maemo-leste/fbkeyboard">can be found in the fbkeyboard repository</a>.</p> <p>fbkeyboard is not available when the device has a hardware keyboard.</p> <img alt="" src="images/bionicfbkeyboard.jpg" style="width: 489px; height: 652px;" /> </div> <div class="section" id="osso-systemui-devlock"> <h3>osso-systemui-devlock</h3> <p>If your Nokia N900 had a lock code set, Maemo Leste would get stuck somewhere during booting with a black screen. This has now been solved, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/495">issue #495</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/343">issue #343</a>.</p> </div> </div> <div class="section" id="additional-software-changes"> <h2>Additional Software changes</h2> <div class="section" id="libsdl-input"> <h3>libsdl input</h3> <p>The libsdl video and input problems we were seeing before have finally been fixed, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/413">issue #413</a>. This is great since it also makes many other applications more usable, for example <cite>cloudgps</cite> . So the (full screen) window placement should now work fine, and both keyboard and mouse input should just work.</p> </div> <div class="section" id="python-bindings"> <h3>Python bindings</h3> <p>We have added python bindings for <cite>libconic</cite>, the hildon connection management library, see <a class="reference external" href="https://github.com/maemo-leste/python-conic">python-conic</a>.</p> </div> <div class="section" id="scummvm"> <h3>ScummVM</h3> <p>ScummVM was broken since our migration to Devuan Beowulf, but rebasing on a newer released fixed the problem, and now <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/353">ScummVM works again</a>.</p> <p>There is also a ScummVM wiki entry now, with various tips and tricks: <a class="reference external" href="https://leste.maemo.org/Extras/ScummVM">https://leste.maemo.org/Extras/ScummVM</a></p> </div> </div> <div class="section" id="community-updates"> <h2>Community updates</h2> <div class="section" id="wiki-updates"> <h3>Wiki updates</h3> <p>We have added wiki pages for various <tt class="docutils literal">Extras</tt> packages, you can find them under the <a class="reference external" href="https://leste.maemo.org/Category:Extras">Category:Extras</a> page.</p> <p>There is now also a package <cite>Infobox</cite> template to make it easy to add a page for a package - if you're a maintainer of a package, please consider making a wiki page entry for it!</p> </div> <div class="section" id="languages-and-translations"> <h3>Languages and Translations</h3> <p>We have imported additional community translations:</p> <ul class="simple"> <li>Arabic</li> <li>Turkish</li> <li>Slovak</li> <li>Hungarian</li> </ul> <p>And we have drastically changed how we get translations to the Maemo Leste devices - we now use the awesome <cite>weblate.org</cite> translation interface, making it easy to change or submit translations, automatically creating Github pull requests in the process.</p> <p>Check out <a class="reference external" href="https://hosted.weblate.org/projects/maemo-leste/#information">Maemo Leste on Weblate.org</a>.</p> </div> <div class="section" id="leste-on-android-via-chroot"> <h3>Leste on Android via chroot</h3> <p><tt class="docutils literal">diejuse</tt> has been experimenting with running Maemo Leste in a chroot on Android, and <a class="reference external" href="https://github.com/diejuse/chroot_Maemo-leste_on_Android">he has documented the process here</a>.</p> <p>Here are two videos of it in action:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/OqFHivcPIRM" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><iframe width="560" height="315" src="https://www.youtube.com/embed/kipuT0VXzC4" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="motorola-droid-3-xt862"> <h3>Motorola Droid 3 (XT862)</h3> <p>This is a new device port (codename <tt class="docutils literal">solana</tt>) - it's still in the early stages, but a lot of things already just work, enough for us to boast about it:</p> <ul class="simple"> <li>Support for kexecboot using <a class="reference internal" href="#clown-boot">clown-boot</a></li> <li>X11 and 3D</li> <li>Audio</li> <li>Wireless</li> </ul> <p>The following still needs work:</p> <ul class="simple"> <li>Brightness control does not work - the screen always has maximum brightness</li> <li>Keyboard backlight doesn't seem to work yet</li> <li>The modem doesn't work yet - it shows up on USB, but the interrupts aren't configured properly.</li> <li>3D shows some frame lag / misdrawing, perhaps the powervr clock needs adjusting</li> <li>Touchscreen buttons do not work yet (the ones on the side)</li> <li>Persistent kernel log store (pstore) does not work yet</li> <li>We might be able to free up 3MB more - we need to see if we can use 512MB ram instead of 509MB</li> <li>The keyboard layout in Leste is not faithful to the icons on the keyboard, but rather mostly mimic droid 4</li> </ul> <p>More information on the <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_3">Droid 3 wiki page</a>.</p> <img alt="" src="images/droid3-photo.jpg" style="width: 500px; height: 500px;" /> <div class="section" id="clown-boot"> <h4>clown-boot</h4> <p><tt class="docutils literal"><span class="pre">clown-boot</span></tt> is the name for a method devised by <strong>uvos</strong> that uses a double-kexec approach to load the kexecboot bootloader, and then the Maemo Leste linux kernel. It was initially created for the Bionic device, but we've re-used the approach for the Motorola Droid 3. We've decided to clean up the code a bit and distributed it over three different repositories for reproducibility:</p> <ul class="simple"> <li>Kernel modules for the Android stock kernel: <a class="reference external" href="https://github.com/maemo-leste/clown-boot-kexec">https://github.com/maemo-leste/clown-boot-kexec</a></li> <li>Mainline-based kernel that is loaded from Android and loads kexecboot: <a class="reference external" href="https://github.com/maemo-leste/clown-boot-kernel">https://github.com/maemo-leste/clown-boot-kernel</a></li> <li>Code used to kexec to kexecboot on Android: <a class="reference external" href="https://github.com/maemo-leste/clown-boot">https://github.com/maemo-leste/clown-boot</a></li> </ul> <p>The older code for clown-boot on the Droid 3 <a class="reference external" href="https://github.com/MerlijnWajer/bionic-clown-boot/tree/solana">can be found here</a>.</p> </div> </div> <div class="section" id="motorola-droid-4-and-droid-bionic"> <h3>Motorola Droid 4 and Droid Bionic</h3> <p>The Motorola Droid 4 should have significantly better power management, due to a <tt class="docutils literal"><span class="pre">quircks-mapphone</span></tt> module introduced in MCE, which will deal with silencing the modem signal strength updates when the display is off and also deal with a (current) power management problem in the modem usb interface that keeps the modem awake even when there is no data to read. See <a class="reference external" href="https://github.com/maemo-leste/mce/commit/f25e8f20562a358d3df37c14e5d7b8639ec869c8">this commit</a> for the code, and <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/25/commits/b01dccd4ffb5e34dda058e231dcf64ee0712b7bb">this leste-config pull request</a> for the addition of the module.</p> <p>The touch screen buttons now provide specific features:</p> <ul class="simple"> <li>The <strong>search</strong> button raises the virtual keyboard, regardless of the application (see <a class="reference internal" href="#hildon-input-method">hildon-input-method</a> improvements)</li> <li>The <strong>back</strong> button will either close a window or go back a stacked window</li> <li>The <strong>home</strong> window will switch to either the window expose view, or the application launcher view</li> <li>The <strong>hamburger</strong> button (three lines) will activate the hildon-specific context menu of applications if they support it</li> </ul> <video controls height="480px" width="640px"> <source src="images/ts-buttons-demonstration.webm" type="video/webm"> </video><p>Some of these features are also added to the pinephone hardware buttons.</p> <p>Finally, <tt class="docutils literal">uvos</tt> has been working on headphone plugin detection, which will make it into our development kernel soon.</p> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>As mentioned in <a class="reference internal" href="#osso-systemui-devlock">osso-systemui-devlock</a>, unlocking devices at boot should now work. We are now also using the <cite>nl80211</cite> interface, as opposed to the <cite>wext</cite> interface.</p> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>Launching the virtual keyboard is now supported in any X11 window, as mentioned in the <a class="reference internal" href="#hildon-input-method">hildon-input-method</a> section, the key to activate it is the volume up key. Once we have the 3D situation on the N900 and Droid devices under control, we will start looking at fixing the 3D rendering problems that seems to occur on the pinephone occasionally.</p> </div> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics, or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 and Bionic units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2021-05-22T10:41:00+02:002021-05-22T10:41:00+02:00Ivan Jelincictag:maemo-leste.github.io,2021-05-22:/maemo-leste-irc-channel-migration.html

<p>Due to the recent events that have happened with FOSS communities and the Freenode IRC network, we've decided to move our channel to the new, community-maintained <a class="reference external" href="https://libera.chat">Libera.chat IRC network</a>.</p> <p>We have hopefully updated all our previous writings, and wiki entries, but if you find any remains of Freenode, let …</p>

<p>Due to the recent events that have happened with FOSS communities and the Freenode IRC network, we've decided to move our channel to the new, community-maintained <a class="reference external" href="https://libera.chat">Libera.chat IRC network</a>.</p> <p>We have hopefully updated all our previous writings, and wiki entries, but if you find any remains of Freenode, let us know so we can change it.</p> <p>See you on Libera IRC! :)</p> 2021-04-24T12:00:00+02:002021-04-24T12:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2021-04-24:/funding-from-ngi-eu.html

<p>A couple of months ago we were made aware of the <a class="reference external" href="https://dapsi.ngi.eu">DAPSI</a> project by our dear Michiel of <a class="reference external" href="https://nlnet.nl">NLnet</a>. DAPSI is one of the projects in the scope of the European Union's <a class="reference external" href="https://www.ngi.eu">Next Generation Internet</a> initiative and it offers funding for projects that research data portability and privacy solutions to …</p>

<p>A couple of months ago we were made aware of the <a class="reference external" href="https://dapsi.ngi.eu">DAPSI</a> project by our dear Michiel of <a class="reference external" href="https://nlnet.nl">NLnet</a>. DAPSI is one of the projects in the scope of the European Union's <a class="reference external" href="https://www.ngi.eu">Next Generation Internet</a> initiative and it offers funding for projects that research data portability and privacy solutions to give people better control over their personal data.</p> <p>Seeing this, we realised that Maemo Leste could be a good fit. We managed to write an application and apply to the open call just before the deadline.</p> <p>A month or so later, we were contacted by the DAPSI team to tell us that our application passed and that we are going to receive funding for the milestones we chose to apply with! Obviously, this is fantastic news for us and it helps us make Maemo Leste sustainable and future proof.</p> <p>The research we are planning to do in the scope of this grant is very interesting and will bring some much needed features to the Maemo Leste ecosystem. We plan to develop various applets that will seamlessly integrate Tor, Wireguard, and OpenVPN into the system and enable a new layer of security and privacy for our community and users.</p> <p>Also part of the grant is work on communication integration in via the Telepathy framework. More concretely, in the scope of DAPSI, we will work on supporting various interfaces in the Telepathy framework: XMPP, GNU Jami, Matrix, and Signal messenger.</p> <p>These should all be able to work with Telepathy as the core, and give us a way to test and develop a generic graphical user interface to all these protocols in Maemo.</p> <p>Finally, we will develop a system library for interoperable sharing of files which will allow us to transfer and share files through various protocols that the system supports, e.g. the above-mentioned.</p> <p>We have to say we're very happy about this research we're going to do and hope that it will speed up some much-needed development that needs to happen.</p> <p>Also, we've gathered enough news to write another update/status post of the current state of Maemo Leste, so you can expect that one soon as well!</p> <p>As always, you can find us on our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> and our <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> 2020-12-27T18:00:00+01:002020-12-27T18:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2020-12-27:/maemo-leste-fourteenth-update-july-august-september-october-november-december-2020.html

<p>It's been several months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-thirteenth-update-april-may-june-2020.html">last update</a>. We've been working hard, and it's been quite a year. Things are shaping up amazingly well, and we're looking forward to entering yet another year of our development efforts!</p> <p>Here are a few highlights:</p> <ul class="simple"> <li>The Maemo Qt5 port is usable now, unlocking …</li></ul>

<p>It's been several months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-thirteenth-update-april-may-june-2020.html">last update</a>. We've been working hard, and it's been quite a year. Things are shaping up amazingly well, and we're looking forward to entering yet another year of our development efforts!</p> <p>Here are a few highlights:</p> <ul class="simple"> <li>The Maemo Qt5 port is usable now, unlocking many applications, like the <a class="reference internal" href="#dorian">Dorian</a> e-book reader <a class="reference external" href="https://github.com/maemo-leste/qalendar">Qalendar</a> Calendar, <a class="reference external" href="https://github.com/maemo-leste/clock-ui">clock-ui</a> clock and alarm, and <a class="reference external" href="https://github.com/maemo-leste/osso-calculator">osso-calculator</a> applications;</li> <li><a class="reference internal" href="#rotation-support">Rotation support</a> is now working for several devices, based on accelerometer and application policies;</li> <li>Major MCE changes, including ambient light sensor support based on the IIO subsystem, accelerometer IIO subsystem, led-control for other devices, user configuration customization, loads of clean ups and more;</li> <li>maemo-input-sounds package finished, adding vibration and sounds;</li> <li>Stable power management for the Droid 4 - lasting days without suspending;</li> <li>Application launcher &quot;Debian&quot; submenu to launch any Debian application;</li> <li>Calendar support is working, including home applet and synchronization using syncevolution;</li> <li>Settings applet including timezone chooser is working;</li> <li>Hildon address book is nearing completion;</li> <li>Motorola Bionic is a new supported device;</li> <li>The GPS stack is working in userspace, and is almost finished;</li> <li>Better PowerVR support upcoming, with higher clock rates and the latest driver version, allowing the N900 to move to the latest kernel again, and gain proper power management.</li> </ul> <div class="section" id="software-changes"> <h2>Software changes</h2> <div class="section" id="packages-interface"> <h3>Packages Interface</h3> <p>We now have a web interface to our packages: <a class="reference external" href="https://maedevu.maemo.org/pkgweb/">https://maedevu.maemo.org/pkgweb/</a></p> <p>It is regenerated every time a package is built in our Jenkins CI instance, and the source code can be found here: <a class="reference external" href="https://github.com/maemo-leste/mpi">https://github.com/maemo-leste/mpi</a></p> </div> <div class="section" id="maemo-input-sounds"> <h3>maemo-input-sounds</h3> <p>We've (re)implemented <a class="reference external" href="https://github.com/maemo-leste/maemo-input-sounds/">Maemo Input Sounds (MIS)</a>, which was a closed Fremantle package. When users interact with Maemo Leste devices, input events are generated for buttons, touchscreen or any other input device. MIS is a daemon that then listens to these events and acts accordingly by providing sound and/or vibration feedback.</p> <p>We also surfaced problems in the Xorg server regarding their XRecord extension, <a class="reference external" href="https://lists.x.org/archives/xorg-devel/2020-July/058582.html">mailed the development list</a>, and later on <a class="reference external" href="https://gitlab.freedesktop.org/xorg/xserver/-/issues/1046">filed a bug report with patch on freedesktop.org</a>, but it looks like no maintainer is home, so we have shipped the patch with our Xorg server.</p> <p>More information in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/389">bug #389</a></p> </div> <div class="section" id="dbus-scripts"> <h3>dbus-scripts</h3> <p>dbus-scripts is a daemon that can execute a command when various events occur on D-Bus. Since most of Maemo Leste relies on D-Bus in some way, this is a powerful tool. A non-exhaustive list of some things one can watch for: keyboard slide changing; screen turning on/off; connecting or disconnecting from a network; incoming sms or phone call; device rotation.</p> <p>This program was a user package in Maemo Fremantle, but we have promoted it to be a core package, since we use it for <a class="reference internal" href="#rotation-support">Rotation support</a> and to work around some power management quirks.</p> <p>We also believe that customizability is an important part of our platform, and this should help making Maemo Leste more extensible.</p> <p>See the <a class="reference external" href="https://wiki.maemo.org/DbusScripts">maemo.org wiki page on dbus-scripts</a> for more information, and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/405">bug #405</a> for some background.</p> <p>Here is an example dbus-scripts rule:</p> <p><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop-rotation-support/blob/maemo/beowulf-devel/scripts/etc/dbus-scripts.d/rotate-ts">https://github.com/maemo-leste/hildon-desktop-rotation-support/blob/maemo/beowulf-devel/scripts/etc/dbus-scripts.d/rotate-ts</a></p> <p>And the command that the example script invokes:</p> <p><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop-rotation-support/blob/maemo/beowulf-devel/scripts/usr/bin/hildon-desktop-rotate-touchscreen.sh">https://github.com/maemo-leste/hildon-desktop-rotation-support/blob/maemo/beowulf-devel/scripts/usr/bin/hildon-desktop-rotate-touchscreen.sh</a></p> </div> <div class="section" id="qt5"> <h3>Qt5</h3> <p>The Qt5 port is in a usable enough state that it is currently available in the main repositories; some of the users might even already have it on their devices!</p> <p>The main features:</p> <ul class="simple"> <li>(Mostly) compatible theme/style with Fremantle;</li> <li>Most Maemo widgets are available;</li> <li>Maemo-style title-bar spinners to indicate progress;</li> <li>Maemo-style menus work;</li> <li>Maemo-style stacked windows work;</li> <li>Maemo-style orientation changes work</li> </ul> <p>Missing features:</p> <ul class="simple"> <li>Virtual keyboard integration;</li> <li>Some widgets;</li> <li>Better APIs/examples for kinetic scrolling for widgets;</li> <li>maemo-launcher caching</li> </ul> <p>The Python package <tt class="docutils literal">PyQt5</tt> should also work.</p> <p>Porting packages from Qt4 to Qt5 is straightforward, and looking at the commit history of these repositories might help those who would like to attempt ports:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/commits/master">https://github.com/maemo-leste-extras/dorian/commits/master</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/clock-ui/commits/master">https://github.com/maemo-leste/clock-ui/commits/master</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/qalendar/commits/master">https://github.com/maemo-leste/qalendar/commits/master</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/osso-calculator/commits/master">https://github.com/maemo-leste/osso-calculator/commits/master</a></li> </ul> </div> <div class="section" id="qalendar"> <h3>Qalendar</h3> <p>We are now also providing <a class="reference external" href="https://github.com/maemo-leste/qalendar">Qalendar</a> as a default Calendar application. It is a FOSS calendar interface written in Qt for Fremantle as an effort to replace the closed source stock calendar. For Maemo Leste, we've ported it to Qt5 and have it working well:</p> <img alt="" src="/images/qalendar-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qalendar-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qalendar-3.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qalendar-4.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/qalendar-5.png" style="width: 576px; height: 324px;" /> <p>Some elements might not be finger-scrollable yet, but otherwise there are no known bugs.</p> <div class="section" id="synchronisation"> <h4>Synchronisation</h4> <p>The calendar application can be synchronized to various calendar backends using <cite>syncevolution</cite>, see also <a class="reference external" href="https://wiki.maemo.org/Sync">https://wiki.maemo.org/Sync</a>. Building the latest syncevolution for Maemo Leste <a class="reference external" href="https://github.com/maemo-leste/calendar-backend/commit/c6e9ef0db493118d44a2958f71180ac70609b071">revealed bugs in calendar-backend which code only ever worked on 32-bit architecture</a>. Further details can be found <a class="reference external" href="https://lists.syncevolution.org/hyperkitty/list/syncevolution&#64;syncevolution.org/thread/ELDL7L37GJHD67OTJWVENURITZ4FV6DL/">on this syncevolution email thread</a>. With that solved, synchronization now works, and you can read about it on <a class="reference external" href="https://leste.maemo.org/Calendar">our Calendar wiki page</a>. There is also a custom GUI written for Maemo to schedule sychronization at set times called <a class="reference external" href="https://github.com/maemo-leste-extras/syncevolution-frontend">syncevolution-frontend</a>. <a class="reference external" href="https://github.com/maemo-leste-extras/cal-home-widget">The home widget has also been ported</a>, showing the upcoming events and current tasks:</p> <img alt="" src="/images/leste-calendar-widget.png" style="width: 572px; height: 343px;" /> <p><strong>We could use someone's help to write a Dockerfile for syncevolution to automatically test the Maemo backend</strong>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/492">see bug #492</a>.</p> </div> </div> <div class="section" id="applet-datetime"> <h3>applet-datetime</h3> <p>An applet for datetime was implemented, and parts reverse-engineered. <a class="reference external" href="https://github.com/maemo-leste/hildon-time-zone-chooser">hildon-time-zone-chooser</a> features a pannable map of the world, along with a button in its EditToolbar to allow you to input the name of a city directly. This is used for timezone selection in the settings menu, but can also be used separately by any other application that needs it.</p> <p>The datetime applet itself allows the user to set the time, date, and timezone, and changing the clock to be a 24 hour clock. This also lays the groundwork for alarms and similar things.</p> <img alt="" src="/images/applet-amsterdam.png" style="width: 572px; height: 343px;" /> <p>Relevant repositories:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/applet-datetime/">https://github.com/maemo-leste/applet-datetime/</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-time-zone-chooser/">https://github.com/maemo-leste/hildon-time-zone-chooser/</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/clock/">https://github.com/maemo-leste/clock/</a></li> </ul> </div> <div class="section" id="clock-ui"> <h3>clock-ui</h3> <p>An initial Qt5 port of <a class="reference external" href="https://github.com/maemo-leste/clock-ui">clock-ui</a> has been finished: this allows changing the time, timezones and manage alarms.</p> <p>For this compoment, the qt gconf library <a class="reference external" href="https://github.com/maemo-leste/libgq-gconf">libgq-gconf</a> has also been ported.</p> <p>The software is a core component and is now packaged, but some bugs remain. We'll pick those up in the coming days and weeks.</p> <img alt="" src="/images/clock-ui-1.png" style="width: 600px; height: 360px;" /> <img alt="" src="/images/clock-ui-2.png" style="width: 600px; height: 360px;" /> <img alt="" src="/images/clock-ui-3.png" style="width: 600px; height: 360px;" /> <img alt="" src="/images/clock-ui-4.png" style="width: 600px; height: 360px;" /> </div> <div class="section" id="alarmd"> <h3>alarmd</h3> <p>Alarmd, the alarm daemon received a <a class="reference external" href="https://github.com/maemo-leste/alarmd/pull/1">runtime fix</a> and an <a class="reference external" href="https://github.com/maemo-leste/alarmd/commit/e7b77f2e912bb71cd879ba17a4bf0d24c13ba06f">initscript dependency fix</a>.</p> <p>The <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/468">python-alarm</a> package is now also packaged, so this kind of code should work:</p> <pre class="literal-block"> &gt;&gt;&gt; alarm.query_event(1501725750.729786, time.time(), 0, 0, '') [15, 17, 18, 19, 20] &gt;&gt;&gt; alarm.get_event(15).appid 'worldclock_alarmd_id' </pre> <p>The alarmd and clockd initscripts were ported to OpenRC, so there are no more insserv/OpenRC runlevel warnings when running apt upgrade/install.</p> </div> <div class="section" id="integration-of-debian-packages"> <h3>Integration of Debian packages</h3> <p>The Hildon menu, where we can see all installed applications that have .desktop entries was expanded with a <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/commit/604d1167860d5750fffe097de121bd7a3e2885f7">submenu</a> that now also shows all &quot;non-hildonized&quot; packages which come from upstream. These can be found in the &quot;Debian&quot; submenu by touching the Debian icon.</p> <img alt="" src="/images/debian-menu-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/debian-menu-2.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="osso-calculator"> <h3>osso-calculator</h3> <p>The Qt calculator <a class="reference external" href="https://github.com/maemo-leste/osso-calculator">osso-calculator</a> has been packaged and ported to Qt5, along with its backend, <a class="reference external" href="https://github.com/maemo-leste/osso-calculator-engine">osso-calculator-engine</a>.</p> <img alt="" src="/images/osso-calculator.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="dorian"> <h3>dorian</h3> <p>Dorian, an epub reader from Maemo Fremantle has also been ported, and works quite well, including portrait mode. Scrolling is quite smooth, especially in fullscreen mode.</p> <img alt="" src="/images/dorian-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/dorian-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/dorian-3.png" style="width: 576px; height: 324px;" /> <p>Relevant repositories, issues and feature requests:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian">https://github.com/maemo-leste-extras/dorian</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/440">https://github.com/maemo-leste/bugtracker/issues/440</a></li> </ul> <p>User <tt class="docutils literal">pere</tt> has also been very helpful, submitting many pull requests:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/4">https://github.com/maemo-leste-extras/dorian/pull/4</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/5">https://github.com/maemo-leste-extras/dorian/pull/5</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/6">https://github.com/maemo-leste-extras/dorian/pull/6</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/13">https://github.com/maemo-leste-extras/dorian/pull/13</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/14">https://github.com/maemo-leste-extras/dorian/pull/14</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/15">https://github.com/maemo-leste-extras/dorian/pull/15</a></li> <li><a class="reference external" href="https://github.com/maemo-leste-extras/dorian/pull/16">https://github.com/maemo-leste-extras/dorian/pull/16</a></li> </ul> </div> <div class="section" id="profilesx"> <h3>profilesx</h3> <p>For managing sound profiles, like ringing/vibrating on notifications and phone calls, we have ported and packaged the open source <a class="reference external" href="https://github.com/maemo-leste-extras/profilesx">profilesx</a> application that was also available on Fremantle. profilesx supports managing multiple (sound) profiles, along with enabling features like autoanswer and loudspeaker.</p> <img alt="" src="/images/profilesx-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/profilesx-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/profilesx-3.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="hildon-desktop"> <h3>hildon-desktop</h3> <div class="section" id="support-for-terminal-applications"> <h4>Support for terminal applications</h4> <p>We <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/9">implemented</a> proper support (and fallbacks) in hildon-desktop that allow us to start .desktop entries that have <tt class="docutils literal">Terminal=true</tt> set and are supposed to open a terminal and run the specific command. Now programs like <tt class="docutils literal">htop</tt> can be run by touching the icon in the menu, or you could even write your own scripts and run them like this! For example, <tt class="docutils literal">Evil_Bob</tt> has his sfeed_curses running from desktop:</p> <video controls height="324px" width="576px"> <source src="/images/droid4-sfeed_curses.webm" type="video/webm"> </video></div> <div class="section" id="snap-to-desktop"> <h4>Snap to desktop</h4> <p>We have decreased the accuracy of 'snap to desktop' to make it easier to align icons on the home screen; previously it would be quite tedious to get them aligned. The time is takes to show a loading preview screen for an application was also decreased. See <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/6">hildon-desktop PR #6</a></p> </div> </div> <div class="section" id="orientation-lock-applet"> <h3>Orientation-lock applet</h3> <p>The orientation lock applet previously installed into the wrong path, causing it to not show up. This has been fixed, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/419">issue #419</a>.</p> </div> <div class="section" id="liblocation-and-location-control"> <h3>liblocation and location-control</h3> <p><a class="reference external" href="https://github.com/maemo-leste/liblocation/">liblocation</a>, <a class="reference external" href="https://github.com/maemo-leste/location-control/">location-control</a>, <a class="reference external" href="https://github.com/maemo-leste/location-daemon/">location-daemon</a>, and a few other pieces of software comprise the GPS/Location stack on Maemo. We have successfully reverse-engineered these binaries from Fremantle and work is well underway on integrating them in the Maemo Leste userspace. Using liblocation, we can talk to our location-daemon and retrieve the current location info and provide it to applications like <a class="reference external" href="https://github.com/maemo-leste-extras/maep">maep</a> that use liblocation as their backend. location-daemon serves as a central point of gps information on Maemo Leste, and it serves its info over the D-Bus Message API. Internally, location-daemon talks to gpsd using its internal libgps library. With this, programs using liblocation can simply gather info from dbus so you can integrate this gps information into your application.</p> <img alt="" src="/images/location-control.png" style="width: 479px; height: 296px;" /> <img alt="" src="/images/maep-1.jpg" style="width: 527px; height: 266px;" /> <img alt="" src="/images/maep-2.jpg" style="width: 576px; height: 324px;" /> <img alt="" src="/images/maep-leste-ams.png" style="width: 576px; height: 324px;" /> <p>Other relevant repositories:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/liblocation">https://github.com/maemo-leste/liblocation</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/location-ui">https://github.com/maemo-leste/location-ui</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/location-status">https://github.com/maemo-leste/location-status</a> (unfinished)</li> <li><a class="reference external" href="https://github.com/maemo-leste/location-daemon">https://github.com/maemo-leste/location-daemon</a> (work in progress)</li> </ul> <div class="section" id="python-location"> <h4>python-location</h4> <p>Work on the status applet and an improved D-Bus interface is still under way. <a class="reference external" href="https://github.com/maemo-leste/python-location">liblocation Python bindings</a> are now also available, here is an example:</p> <pre class="code python literal-block"> <span class="kn">import</span> <span class="nn">location</span><span class="w"> </span><span class="kn">import</span> <span class="nn">gobject</span><span class="w"> </span><span class="k">def</span> <span class="nf">on_error</span><span class="p">(</span><span class="n">control</span><span class="p">,</span> <span class="n">error</span><span class="p">,</span> <span class="n">data</span><span class="p">):</span><span class="w"> </span> <span class="nb">print</span> <span class="s2">&quot;location error: </span><span class="si">%d</span><span class="s2">... quitting&quot;</span> <span class="o">%</span> <span class="n">error</span><span class="w"> </span> <span class="n">data</span><span class="o">.</span><span class="n">quit</span><span class="p">()</span><span class="w"> </span><span class="k">def</span> <span class="nf">on_changed</span><span class="p">(</span><span class="n">device</span><span class="p">,</span> <span class="n">data</span><span class="p">):</span><span class="w"> </span> <span class="k">if</span> <span class="ow">not</span> <span class="n">device</span><span class="p">:</span><span class="w"> </span> <span class="k">return</span><span class="w"> </span> <span class="k">if</span> <span class="n">device</span><span class="o">.</span><span class="n">fix</span><span class="p">:</span><span class="w"> </span> <span class="k">if</span> <span class="n">device</span><span class="o">.</span><span class="n">fix</span><span class="p">[</span><span class="mi">1</span><span class="p">]</span> <span class="o">&amp;</span> <span class="n">location</span><span class="o">.</span><span class="n">GPS_DEVICE_LATLONG_SET</span><span class="p">:</span><span class="w"> </span> <span class="nb">print</span><span class="p">(</span><span class="s2">&quot;lat = </span><span class="si">%f</span><span class="s2">, long = </span><span class="si">%f</span><span class="s2">&quot;</span> <span class="o">%</span> <span class="n">device</span><span class="o">.</span><span class="n">fix</span><span class="p">[</span><span class="mi">4</span><span class="p">:</span><span class="mi">6</span><span class="p">])</span><span class="w"> </span><span class="k">def</span> <span class="nf">on_stop</span><span class="p">(</span><span class="n">control</span><span class="p">,</span> <span class="n">data</span><span class="p">):</span><span class="w"> </span> <span class="n">data</span><span class="o">.</span><span class="n">quit</span><span class="p">()</span><span class="w"> </span><span class="k">def</span> <span class="nf">start_location</span><span class="p">(</span><span class="n">data</span><span class="p">):</span><span class="w"> </span> <span class="n">data</span><span class="o">.</span><span class="n">start</span><span class="p">()</span><span class="w"> </span> <span class="k">return</span> <span class="kc">False</span><span class="w"> </span><span class="n">loop</span> <span class="o">=</span> <span class="n">gobject</span><span class="o">.</span><span class="n">MainLoop</span><span class="p">()</span><span class="w"> </span><span class="n">control</span> <span class="o">=</span> <span class="n">location</span><span class="o">.</span><span class="n">GPSDControl</span><span class="o">.</span><span class="n">get_default</span><span class="p">()</span><span class="w"> </span><span class="n">device</span> <span class="o">=</span> <span class="n">location</span><span class="o">.</span><span class="n">GPSDevice</span><span class="p">()</span><span class="w"> </span><span class="n">control</span><span class="o">.</span><span class="n">set_properties</span><span class="p">(</span><span class="n">preferred_method</span><span class="o">=</span><span class="n">location</span><span class="o">.</span><span class="n">METHOD_USER_SELECTED</span><span class="p">,</span><span class="w"> </span> <span class="n">preferred_interval</span><span class="o">=</span><span class="n">location</span><span class="o">.</span><span class="n">INTERVAL_DEFAULT</span><span class="p">)</span><span class="w"> </span><span class="n">control</span><span class="o">.</span><span class="n">connect</span><span class="p">(</span><span class="s2">&quot;error-verbose&quot;</span><span class="p">,</span> <span class="n">on_error</span><span class="p">,</span> <span class="n">loop</span><span class="p">)</span><span class="w"> </span><span class="n">device</span><span class="o">.</span><span class="n">connect</span><span class="p">(</span><span class="s2">&quot;changed&quot;</span><span class="p">,</span> <span class="n">on_changed</span><span class="p">,</span> <span class="n">control</span><span class="p">)</span><span class="w"> </span><span class="n">control</span><span class="o">.</span><span class="n">connect</span><span class="p">(</span><span class="s2">&quot;gpsd-stopped&quot;</span><span class="p">,</span> <span class="n">on_stop</span><span class="p">,</span> <span class="n">loop</span><span class="p">)</span><span class="w"> </span><span class="n">gobject</span><span class="o">.</span><span class="n">idle_add</span><span class="p">(</span><span class="n">start_location</span><span class="p">,</span> <span class="n">control</span><span class="p">)</span><span class="w"> </span><span class="n">loop</span><span class="o">.</span><span class="n">run</span><span class="p">()</span> </pre> <p>Documentation on the Python APIs can be found here:</p> <ul class="simple"> <li><a class="reference external" href="http://wiki.maemo.org/PyMaemo/Using_Location_API">http://wiki.maemo.org/PyMaemo/Using_Location_API</a></li> <li><a class="reference external" href="http://pymaemo.garage.maemo.org/python_location_manual/location.html">http://pymaemo.garage.maemo.org/python_location_manual/location.html</a></li> </ul> </div> </div> <div class="section" id="major-mce-improvements"> <h3>Major MCE improvements</h3> <p>There have been a lot of MCE changes, <tt class="docutils literal">uvos</tt> has done tremendous work and we will try our best to list all the changes here.</p> <p>New modules:</p> <ul class="simple"> <li><tt class="docutils literal"><span class="pre">iio-als</span></tt>: This module allows for dynamically adjusting the screen brightness and keyboard led brightness based on the ambient light (and the brightness profile); see <a class="reference external" href="https://github.com/maemo-leste/mce/pull/14">MCE PR #14.</a> and <a class="reference external" href="https://github.com/maemo-leste/mce/pull/15">MCE PR #15</a>.</li> <li><tt class="docutils literal"><span class="pre">led-sw</span></tt> + <tt class="docutils literal"><span class="pre">led-dbus</span></tt>: This module supports simple LED patterns for devices that do not (yet) have support for programming LEDs through a dedicated chip. This way we can show notification patterns even if a dedicated chip is not available. Currently in use on the Droid 4 and PinePhone. See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/22">MCE PR #22</a>.</li> <li><tt class="docutils literal"><span class="pre">x11-ctrl</span></tt>: Some of the X11 specific code moved to its own module. See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/21">MCE PR #21</a>.</li> </ul> <p>Refactoring and fixes:</p> <ul class="simple"> <li><tt class="docutils literal">mce.ini.d</tt> support. This splits up the MCE configuration into a core configuration, device specific configuration, and user (customisable) configuration. See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/18">MCE PR #18</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/42">MCE PR #42</a>, <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/5">leste-config PR #5</a> and <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/6">leste-config PR #6</a>.</li> <li>Display inactivity refactoring, see <a class="reference external" href="https://github.com/maemo-leste/mce/pull/16">MCE PR #16</a>.</li> <li>Some evdev vibration fixes, see <a class="reference external" href="https://github.com/maemo-leste/mce/pull/19">MCE PR #19</a>.</li> <li>Removal of <tt class="docutils literal"><span class="pre">mce-hal</span></tt>, see <a class="reference external" href="https://github.com/maemo-leste/mce/pull/20">PR #20</a>.</li> </ul> <p>Additionally, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/429">iio-sensor-proxy is now packaged</a> since MCE relies on it.</p> </div> <div class="section" id="openmediaplayer"> <h3>openmediaplayer</h3> <p>Open Media Player is a clone of the Maemo Fremantle media player, and with the Qt 5 port we've been making progress on bringing it to Maemo Leste <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/25">in issue #25</a>.</p> <p>Currently the application builds with Qt5 and shows the main window and settings, but playlists do not yet render.</p> <p><strong>If anyone feels like helping out, it would be much appreciated!</strong></p> <img alt="" src="/images/omp-initial-1.png" style="width: 716px; height: 385px;" /> <img alt="" src="/images/omp-initial-2.png" style="width: 716px; height: 385px;" /> </div> <div class="section" id="address-book-contacts-and-account-libraries"> <h3>Address book, contacts and account libraries</h3> <p>Particularly exciting is the fact that <tt class="docutils literal">freemangordon</tt> has been working on bringing the Hildon address book framework (libraries and user interfaces) to Maemo Leste. This will allow telepathy and evolution to see and modify the contact lists.</p> <p>The work is still not finished, but it's quite close. The current work is packaged, but not yet in the repositories.</p> <img alt="" src="/images/VirtualBox_leste-beowulf_17_09_2020_15_06_07.png" style="width: 645px; height: 358px;" /> </div> <div class="section" id="rotation-support"> <h3>Rotation support</h3> <p>Orientation and rotation support is now supported natively. Using the hardware accelerometers, mce, and iio-sensors we are able to physically rotate our devices and have the orientation change depending on the 3D position. Obviously, this means portrait and landscape orientation can be switched simply by positioning the device in its respective position. As we're using native kernel interfaces and according userspace, this is supported on all our phones which have working accelerometers.</p> <p>The package <a class="reference external" href="https://github.com/maemo-leste/hildon-desktop-rotation-support">hildon-desktop-rotation-support</a> implements this feature using <a class="reference internal" href="#dbus-scripts">dbus-scripts</a> and the <tt class="docutils literal">xrandr</tt> and <tt class="docutils literal">xinput</tt> utilities.</p> <p>On the Nokia N900 this is not yet enabled, due to the rotation crashing the display server still. This will likely be resolved in an upcoming update to the latest PowerVR driver.</p> </div> <div class="section" id="upower-history"> <h3>UPower history</h3> <p>Our devices now keep UPower history for more than 7 days, which was a hardcoded limit in UPower. We have changed this to 30 days now, to allow for power usage analytics going back further in time. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/421">issue #421</a></p> <!-- * https://wizzup.org/droid4-powerapplet.png + https://wizzup.org/droid4-upower-graph.png --> <!-- + -avg --> </div> <div class="section" id="pulseaudio"> <h3>Pulseaudio</h3> <p>The audio stack uses <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/402">Pulseaudio</a>, as this will be necessary for further work on phone calls due to UCM and profiles. Pulseaudio seamlessly integrates and is configured for all our targets. The base configurations reside in our <a class="reference external" href="https://github.com/maemo-leste/maemo-audio">maemo-audio</a> package and they're pulled in by our main metapackages, so a simple upgrade will configure everything as necessary.</p> <p>For <a class="reference external" href="https://github.com/maemo-leste/leste-config/pull/13/">Droid4, Bionic</a>, and <a class="reference external" href="https://github.com/maemo-leste/leste-config/commit/9693ab7dfff0b7068e2bbaa187a7f9af0ec229f6">Pinephone</a>, we already have UCM2 files in place and we will be utilizing these with our further efforts related to audio and phone calls.</p> <p>With the UCM files in place, <tt class="docutils literal"><span class="pre">pavucontrol-qt</span></tt> will show the proper controls and outputs - for multimedia (Hi Fi) and phone.</p> <img alt="" src="/images/pavucontrol-qt.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/pavucontrol-qt2.png" style="width: 576px; height: 324px;" /> <p>Huge thanks for <tt class="docutils literal">uvos</tt> for creating the UCM2 files for the Droid 4!</p> </div> </div> <div class="section" id="hardware-drivers"> <h2>Hardware &amp; Drivers</h2> <div class="section" id="motorola-droid-bionic"> <h3>Motorola Droid Bionic</h3> <p>Maemo Leste now supports another device - the <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_Bionic">Motorola Droid Bionic</a>!</p> <p><tt class="docutils literal">uvos</tt> contributed this post and also created <a class="reference external" href="https://github.com/IMbackK/bionic-clown-boot">bionic-clown-boot</a> to allow booting non-Android kernels. Kernel patches are already being upstreamed.</p> <p>The Bionic was one of the <a class="reference external" href="https://en.wikipedia.org/wiki/List_of_best-selling_mobile_phones#2011">best selling smartphones in 2011</a>, selling 13 million units that year. That is great news, because that means they should be relatively easy to source.</p> <p>The Bionic is pretty similar to the Droid 4 in hardware but does not have a physical keyboard.</p> </div> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <div class="section" id="on-mainline"> <h4>On mainline</h4> <p>We have been following upstream kernels very closely with the Droid 4 (and now also Bionic), usually jumping to the newest kernel on the day of its release, at least in our <tt class="docutils literal"><span class="pre">beowulf-devel</span></tt> repository. This is great, because we find bugs early, but it also means we deal with bugs every few weeks. Linux 5.9 had been particularly painful with random resets, which we ultimately seem to have fixed (big thanks to <tt class="docutils literal">tmlind</tt> and <tt class="docutils literal">uvos</tt>), but then 5.10 introduced similar problems, which as of yesterday also seem to be fixed. But it serves as a reminder that having mainline support for a device is not something you do once: it requires active maintenance.</p> <p>Additionally, the <a class="reference external" href="https://lkml.org/lkml/2020/6/29/1404">Droid 4 RTC has seen some fixes</a> and more work is pending to be mainlined. Some of that work can be seen here: <a class="reference external" href="https://github.com/tmlind/linux/commits/droid4-pending-v5.10">https://github.com/tmlind/linux/commits/droid4-pending-v5.10</a></p> </div> <div class="section" id="modem-power-management"> <h4>Modem power management</h4> <p>This week we will also merge a power management improvement for the Droid 4 with the modem on, to disable signal strength notifications when the screen is off. These notifications cause a lot of wake ups, so we don't want to receive them when we don't need them. We can fix this with <a class="reference internal" href="#dbus-scripts">dbus-scripts</a>:</p> <pre class="literal-block"> # cat /etc/dbus-scripts.d/idle-modem /root/test.sh * * com.nokia.mce.signal display_status_ind # cat /root/test.sh #!/bin/sh if [ &quot;$5&quot; = &quot;on&quot; ] then printf 'U1234AT+SCRN=1\r' &gt; /dev/gsmtty1 else printf 'U1234AT+SCRN=0\r' &gt; /dev/gsmtty1 fi </pre> </div> <div class="section" id="sd-card-speed"> <h4>SD card speed</h4> <p><tt class="docutils literal">uvos</tt> tried to use a much higher clocking frequency (100Mhz) than standard with a UHS-3 sd card and managed to get a <cite>41.4MB/s</cite> sd card write speed. We'll have to investigate if this work is something we can use in our kernels.</p> </div> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <div class="section" id="u-boot-and-serial"> <h4>u-boot and serial</h4> <p><tt class="docutils literal">Pali</tt> has been doing a lot of work on mainline u-boot on the Nokia N900 again, and it has paid off. Now u-boot boots again (yes, it wasn't booting anymore!) and usbtty (serial communication over usb) now works. This might allow for scripted booting of the Nokia N900.</p> <p>The new u-boot binary can be found here:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/n900/tools/">https://maedevu.maemo.org/images/n900/tools/</a></blockquote> <p>with filename <tt class="docutils literal"><span class="pre">u-boot-2020.12-pali.bin</span></tt>.</p> <p>If you flash this to your device with 0xFFFF and boot with the keyboard open and USB cable connected, you should see something similar to this in <tt class="docutils literal">dmesg</tt>:</p> <pre class="literal-block"> usb 3-1.1.3: new full-speed USB device number 95 using xhci_hcd usb 3-1.1.3: New USB device found, idVendor=0421, idProduct=01c8, bcdDevice= 0.00 usb 3-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-1.1.3: Product: N900 (U-Boot) usb 3-1.1.3: Manufacturer: Nokia usb 3-1.1.3: SerialNumber: 0000000 cdc_acm 3-1.1.3:1.0: ttyACM0: USB ACM device </pre> <p>And to top it off, here is a video of the physical serial on the right, and the usb serial on the left. You can see they are in sync:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/tGGXvguyXWk" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div> </div> <div class="section" id="powervr-ddk-1-17-xorg-glamor-and-clock-fixes"> <h3>PowerVR: DDK 1.17, Xorg Glamor and clock fixes</h3> <p>One of the more exciting things is that <tt class="docutils literal">freemangordon</tt>, <tt class="docutils literal">uvos</tt> and <tt class="docutils literal">tmlind</tt> have been able to get the latest PowerVR DDK 1.17 to run on both the Nokia N900 and the Motorola Droid 4. The work entails not just the kernel side and kernel display driver side, but also the Xorg side: having to bang X11 <tt class="docutils literal">Glamor</tt> and <tt class="docutils literal"><span class="pre">xf86-video-modesetting</span></tt> into shape to conform more closely to the OpenGL(ES) specifications, and fix various bugs. <tt class="docutils literal">freemangordon</tt> is also working on a shim library to expose graphics drivers that support GBM platform display to X11, even if the drivers lack the specific X11 windowing system, which could potentially benefit other drivers that are no longer providing drivers for X11. The shim requires the DRI3 and PRESENT support from X11.</p> <p>One of the problems here is that it looks like X11 is left without maintainers: there are many pending pull requests that contain fixes, and they're mostly just being ignored. Unfortunately, that includes some pull requests we have sent in, so we have had no choice but to fork X11 for now and package our own versions.</p> <p>That said, this driver work would also bring the Nokia N900 back to Linux 5.10 or 5.11, which is great news, as that would likely also benefit the long-awaited <tt class="docutils literal">OFF</tt> mode for the phone (debugging issues on older kernels is no fun), bringing much better power management.</p> <div class="section" id="corruption"> <h4>Corruption</h4> <p><tt class="docutils literal">uvos</tt> also found that the PowerVR SGX driver on the Motorola Droid 4 ran at a much lower clock frequency than it should, which sometimes causes the result to be rendered too late to the display, resulting in the artifacts that we have gotten used to. With the GPU at the right frequency, the rendering artifacts are gone, and the 3D is smoother than ever before.</p> </div> </div> <div class="section" id="pinephone-and-pinetab"> <h3>Pinephone and Pinetab</h3> <p>The Pinephone and Pinetab devices are moving forward as well. Along with the already mentioned working things, most things you'd expect work on the Pine64 devices. We have also implemented the <a class="reference external" href="https://github.com/crust-firmware/crust">crust firmware</a> in our images so power usage is minimal when the devices are suspended!</p> <p>As Maemo Leste is envisioned as an operating system to mainly be used on devices with a hardware keyboard, you can imagine our excitement when Pine64 announced they are looking into a hardware keyboard <a class="reference external" href="https://www.pine64.org/2020/07/29/invitation-to-play-along/">addon</a> for the Pinephone. We'll be following this development, and hope for it to continue successfully :)</p> </div> <div class="section" id="continuous-integration-for-device-images"> <h3>Continuous Integration for device images</h3> <p>On our Jenkins infrastructure, we have been successfully running <a class="reference external" href="https://phoenix.maemo.org/view/Images/">weekly builds</a> for all our device targets. This is a great advantage as we don't have to manually build images whenever we find the free time to do it, but rather have fresh images be built every week so everyone can always download latest images with the most up to date packages installed.</p> <p>This has also encouraged us to improve our image building <a class="reference external" href="https://github.com/parazyd/libdevuansdk">software</a>, clean it up, and make it more efficient and generally just better.</p> <p>At some point in the future, we also plan to look into automated testing of these images, because a successful build doesn't necessarily mean a perfectly working image. More later ;)</p> </div> </div> <div class="section" id="closing-words"> <h2>Closing words</h2> <p>It's been a pretty good year for our project. A lot more core pieces are falling into place, we are attracting more contributors and things are becoming more stable and featureful. The project has received some funding which we have been using to ship devices to folks who want to help out.</p> <p>It's been almost three years since the announcement of our project, and well over three years since we started working on Maemo Leste. And we have come far, and we will keep pushing until we have the secure, open, extendable and customizable mobile operating system that we envision. Built by the community, for the community.</p> <div class="section" id="ecosystem-community"> <h3>Ecosystem &amp; Community</h3> <p>Our community keeps growing, our ecosystem expanding, but there is a lot to wish for too: more regular updates, a better structure for our wiki and an easier way for users to contribute.</p> <p>Readers not familiar with this <a class="reference external" href="https://talk.maemo.org/showthread.php?t=101089&amp;page=5">Maemo Leste Playground thread</a> might like to take a peek at some of the work our community has been doing to make various programs and games run on Maemo Leste.</p> <p>The <a class="reference external" href="http://maemo.org/downloads/product/Maemo5/maemo-org/">Fremantle Maemo.org theme</a> is now <a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-maemo-org">also available in Maemo Leste</a>, and we might switch to using that (community developed) theme by default.</p> <!-- We would have thought that our settings applications would contain so many --> <!-- applets? --> <!-- --> <!-- .. image:: /images/control-panel-filling-up.png --> <!-- :height: 576px --> <!-- :width: 324px --> <!-- --> <!-- Or that multi tasking on the Droid 4 would work so well? --> <!-- --> <!-- .. image:: /images/leste-multi-tasking.png --> <!-- :height: 576px --> <!-- :width: 324px --> </div> <div class="section" id="phone-aspect"> <h3>Phone aspect</h3> <p>The OS might look barebones now, but there is a lot to look forward to when we land some of the final missing pieces: contacts, text communications and phone calls.</p> <p>Lacking phone calls might seem ridiculous to some, <strong>but there are many aspects that matter about a mobile operating system</strong>, and working phone calls without any sense of power management or audio policy modules to automatically switch from/to headset and speakers also make a device hardly usable. We are now at the point where the Motorola Droid 4 lasts for several days on a battery while it is connected to the mobile network, performs quite well, almost all the hardware components work the way they should, and we have a strong (and expanding, to other devices) base to build our phone OS upon.</p> <p>Contacts, phone calls and text-conversations will be the main focus for us going into 2021. We will aim to mimic Fremantle where it makes sense: providing a unified conversations experience, regardless of the instant messaging protocol (leveraging telepathy and libpurple), combined with a featureful phone application.</p> <!-- SORTME --> <!-- ====== --> <!-- * https://wizzup.org/update-notification-1.png --> <!-- https://wizzup.org/update-notification-2.png --> <!-- https://wizzup.org/update-notification-3.png --> <!-- https://wizzup.org/update-notification-4.png --> <!-- https://wizzup.org/update-notification-5.png --> <!-- https://wizzup.org/update-notification-6.png --> <!-- https://wizzup.org/update-notification-7.png --> <!-- * https://github.com/maemo-leste/bugtracker/issues/41 - screen calib applet --> <!-- * mpd with GMPC works nice (make some screenshots), also fullscreen mode is cool --> <!-- * https://github.com/maemo-leste/bugtracker/issues/390#issuecomment-657268449 - --> <!-- progress on call ui libs --> <!-- * "Re: [maemo-leste] WIFI tethering" --> <!-- * https://github.com/maemo-leste/osso-systemui-tklock/pull/2 --> <!-- * 17:44 <parazyd> https://github.com/maemo-leste/bugtracker/issues/447 -> "no more apt warnings about runlevels" --> </div> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics, or helping out, or wish to have a specific package ported, please see our bugtracker.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 and Bionic units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2020-06-24T18:00:00+02:002020-06-24T18:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2020-06-24:/maemo-leste-thirteenth-update-april-2020.html

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-twelfth-update-february-and-march-2020.html">last update</a>, so let's start with a few highlights:</p> <ul class="simple"> <li>We have improved power management on the Droid 4, and currently, under ideal conditions, the power draw is about <tt class="docutils literal">60mW</tt> with the modem turned on. That should last a few days on a decent battery …</li></ul>

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-twelfth-update-february-and-march-2020.html">last update</a>, so let's start with a few highlights:</p> <ul class="simple"> <li>We have improved power management on the Droid 4, and currently, under ideal conditions, the power draw is about <tt class="docutils literal">60mW</tt> with the modem turned on. That should last a few days on a decent battery</li> <li>Various sensors and other hardware of the Motorola Droid 4 are now usable with Maemo Leste</li> <li>A lot of kernel bugs/regressions have been chased and fixed</li> <li>Cellular support is improving; cellular data should now work</li> <li>Maemo Leste Extras should contain quite a few more packages now</li> <li><tt class="docutils literal"><span class="pre">leste-config-*</span></tt> packages now exist to provide seamless configuration updates and changes, so there should be less of a need to &quot;reinstall&quot; on every new image release</li> </ul> <div class="section" id="software-changes"> <h2>Software changes</h2> <div class="section" id="mce"> <h3>mce</h3> <p>The Mode Control Entity has seen significant changes.</p> <p>MCE will now properly blank the screen, allowing the SoC to idle, which in turn allows for significant power saving (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/338">see issue #338</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/5">MCE PR 5</a>).</p> <p>With the newer versions, the touchscreen will also be properly disabled when the device is locked. This will prevent 'accidental' input events being sent to applications while the device is locked. MCE will also close the file descriptors of any touchscreen devices and tell X11 to disable the touchscreens to let the touchscreen driver idle properly. For more details, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/340">issue #340</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/6">MCE PR 6</a> and <a class="reference external" href="https://github.com/maemo-leste/mce/pull/7">MCE PR 7</a>.</p> <p>Furthermore, we've made a change to the default <tt class="docutils literal">/etc/mce/mce.ini</tt> configuration file to prevent accidental shutdowns on the Droid 4. We've <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/392">increased the time one has to press the power key to shutdown the device (issue #392)</a>.</p> <p>ALS (Ambient Light Sensor) support has been extended, and it now also works on the <a class="reference internal" href="#motorola-droid-4">Motorola Droid 4</a>. See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/">MCE PR 8</a>.</p> <p>A module contributed by <tt class="docutils literal">uvos</tt> to support vibration in MCE is also expected to land in the next few days. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/132">issue #132</a> and <a class="reference external" href="https://github.com/maemo-leste/mce/pull/9">MCE PR 9</a>.</p> <p>Something else to look forward to is the execution of mode-change shell scripts, to allow certain programs or scripts to be executed when a device is locked, unlocked, or enters other mce (sub)modes.</p> </div> <div class="section" id="input-and-focus-fixes"> <h3>Input and Focus fixes</h3> <p>libmatchbox2 and hildon-desktop (the Maemo window manager) have had <a class="reference external" href="https://bugs.maemo.org/show_bug.cgi?id=5987">long standing bugs with regards to input focus</a>, which also made it <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/346">impossible to send keyboard events to vanilla Qt 5 applications</a>.</p> <p><tt class="docutils literal">freemangordon</tt> and <tt class="docutils literal">uvos</tt> have been trying to get to the bottom of the problem. The result of that effort is that all known problematic input and focus issues are now fixed. Now xev happily receives events, es2gears responds to keyboard input events, and Qt 5 applications take input the way they are supposed to.</p> <p>Relevant pull requests:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/3">libmatchbox PR 3</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/4">libmatchbox PR 4</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/4">hildon-desktop PR 4</a></li> </ul> </div> <div class="section" id="qt-5-progress-is-being-made"> <h3>Qt 5: Progress is being made</h3> <p>The Maemo Qt 5 port is not finished yet, but has seen various improvements. Merlijn has been doing work porting the &quot;Hildon Input Method&quot; virtual keyboard patches to Qt 5. Due to the more clear architecture of Qt 5, our unwillingness to fork Qt 5 as a whole, and the fact that we're also porting from old <tt class="docutils literal">Xlib</tt> code to <tt class="docutils literal">xcb</tt>, the work is taking a little bit more time. On the upside, all the Maemo Qt 5 bits will hopefully available via a <a class="reference external" href="https://doc.qt.io/qt-5/qpa.html">Qt 5 loadable platform module</a>.</p> <p>Apart from the virtual keyboard, there are at least two important pieces missing:</p> <ul class="simple"> <li>QMenu support, to allow hildon-style menu items to show when the application title is touched/pressed</li> <li>Hildon-style stacked windows</li> </ul> <p>We've also ported over a sample application, <a class="reference external" href="https://github.com/maemo-leste-extras/countdowntimer">countdowntimer</a>:</p> <img alt="" src="/images/countdowntimer.png" style="width: 576px; height: 324px;" /> <p>To make it usable, we had to have the application respect desktop sizes other than the <cite>800x480</cite> that the Nokia N900 screen supports, to prevent it from looking like this:</p> <img alt="" src="/images/leste-qt5-countdowntimer-0.1.png" style="width: 576px; height: 324px;" /> <p>Countdowntimer itself also makes use of the specialised QMenu and Hildon stackable windows, but is already quite usable even without those modifications.</p> <p>Development can be done directly on the VM, using X11 forwarding:</p> <img alt="" src="/images/leste-qt5-designer-x11-forward.png" style="width: 576px; height: 324px;" /> <p>You can also use Qt Designer with the native Maemo theme, but, well...:</p> <img alt="" src="/images/leste-designer-lol.png" style="width: 576px; height: 324px;" /> <p>If you plan to use Qt designer on your device, you might want to look at <a class="reference internal" href="#xephyr-nested-xorg-server-on-maemo">Xephyr (Nested Xorg server) on Maemo</a> instead.</p> <p>In the next month, we hope to mostly finish the Qt 5 port. Keep in mind that many Qt 5 applications are already usable on Maemo Leste as is. This is also documented in <a class="reference internal" href="#community-showcase">Community showcase</a>!</p> </div> <div class="section" id="xephyr-nested-xorg-server-on-maemo"> <h3>Xephyr (Nested Xorg server) on Maemo</h3> <p>Xephyr is a nested X server, which can run in a window on Maemo Leste, allowing you to run any ordinary desktop application on Maemo Leste, in a window.</p> <p>It's especially useful for devices with physical keyboards.</p> <p>Installing it is as simple as:</p> <pre class="literal-block"> sudo apt install xephyr </pre> <p>And then start it as follows:</p> <pre class="literal-block"> Xephyr :1 &amp; </pre> <p>And launch applications inside that server like so:</p> <pre class="literal-block"> DISPLAY=:1 dwm &amp; DISPLAY=:1 xterm </pre> <img alt="" src="/images/xephyr-droid4.png" style="width: 576px; height: 324px;" /> <p>Enjoy!</p> </div> <div class="section" id="cellular-data-and-ofono-support"> <h3>Cellular data and ofono support</h3> <p>The <tt class="docutils literal"><span class="pre">beowulf-devel</span></tt> repository of Maemo Leste now has the <tt class="docutils literal"><span class="pre">libicd-network-ofono</span></tt> plugin for <tt class="docutils literal">icd2</tt> to allow for making GPRS/UMTS/LTE data connections:</p> <img alt="" src="/images/droid4-libicd-network-ofono.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/droid4-libicd-network-ofono-2.png" style="width: 576px; height: 324px;" /> <p>This should work on all of the supported devices, as long as their ofono version (and SIM) supports data connections.</p> <p>Additionally, there were some problems on Beowulf where user <tt class="docutils literal">user</tt> (the default user in Maemo) had no access to the ofono dbus interface, but this has been fixed in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/372">issue #372</a>.</p> <p>Finally, once this work has seen a bit more testing, we will create a meta package to automatically install all the cellular packages, and all devices will automatically get the cellular support when they <tt class="docutils literal">apt update &amp;&amp; apt upgrade</tt>.</p> </div> <div class="section" id="wireless"> <h3>Wireless</h3> <p>Wireless is mostly just working, although the UI still has some rough edges. In particular, sometimes connecting to a network fails if entering the password takes too long.</p> <p>One other bug was fixed: a problem where the networks would appear in the network dialog, but would not be selectable until the next scan returned, which was really annoying. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/253">issue #253</a> and <a class="reference external" href="https://github.com/maemo-leste/connui-internet/pull/1">connui-internet PR</a>.</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/374">https://github.com/maemo-leste/bugtracker/issues/374</a> - two packages, also mention integration</li> </ul> </div> <div class="section" id="themes"> <h3>Themes</h3> <p>The retro <a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-okuda">Okuda theme</a> is now available:</p> <img alt="" src="/images/leste-okuda-desktop.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-okuda-vkb.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-okuda-xterm.png" style="width: 576px; height: 324px;" /> <p><a class="reference external" href="https://github.com/maemo-leste-extras/miku-theme">Miku theme</a>:</p> <img alt="" src="/images/leste-miku-settings.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-miku-desktop.png" style="width: 576px; height: 324px;" /> <p><a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-matrix">Matrix theme</a>:</p> <img alt="" src="/images/leste-matrix-desktop.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-matrix-lock.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="openrc-integration-in-debian-fixes"> <h3>OpenRC integration in Debian fixes</h3> <p>We've successfully submitted a patch to SysVinit upstream, which brings in better support for OpenRC and its internals to both Debian and Devuan. It has not yet propagated to Devuan, but it is expected to happen, of course. In Maemo Leste we already provide the patched version and maintain it ourselves until it is available in Devuan. The patch itself brings in proper OpenRC support in the insserv tool, which means that LSB headers aren't necessary for OpenRC initscripts and they now get installed in the default runlevel without the need for manual interference.</p> <p>The patch was merged in <tt class="docutils literal">6a65f4412a2d24d78741f49e64e1128993341e65</tt>, and can be seen here:</p> <ul class="simple"> <li><a class="reference external" href="http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;id=6a65f4412a2d24d78741f49e64e1128993341e65">http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;id=6a65f4412a2d24d78741f49e64e1128993341e65</a></li> </ul> <p>If you found that some init scripts ended up in <tt class="docutils literal">/etc/runlevels</tt> instead of <tt class="docutils literal">/etc/runlevels/default</tt>, try reinstalling the affected packages; they should install fine now.</p> </div> <div class="section" id="more-languages-added-to-virtual-keyboard-layouts"> <h3>More languages added to virtual keyboard layouts</h3> <p>Many more virtual keyboard layouts have been added. If you were ever in need of a Belarusian or Bulgarian keyboard layout, now is your time to <tt class="docutils literal">apt update &amp;&amp; apt upgrade</tt>.</p> <p>See <a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/2">hildon-input-method-plugins PR 2</a>.</p> </div> <div class="section" id="steps-towards-calls-and-texts"> <h3>Steps towards calls and texts</h3> <p>With <a class="reference internal" href="#cellular-data-and-ofono-support">Cellular data and ofono support</a> improving and other projects getting close to finished, it will soon be time to turn our attention to usable calls and texts on Maemo. We will use many of the same components that Maemo Fremantle uses, just in their updated forms, like the Mer project does.</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390">Issue #390</a> documents some of the steps we will be taking. It will look something like:</p> <ol class="arabic simple"> <li>Perform further analysis on how this works in Fremantle</li> <li>Import all the FOSS components (there are quite a number of them)</li> <li>Figure out audio (routing and) policies</li> <li>Reimplement the non-FOSS ones: call and sms UI are the big ones</li> <li>Use <tt class="docutils literal"><span class="pre">osso-abook</span></tt> in the alternative call and sms UIs</li> </ol> <ul class="simple"> <li>towards proper telepathy integration <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390">https://github.com/maemo-leste/bugtracker/issues/390</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger-plugins">https://github.com/maemo-leste/rtcom-eventlogger-plugins</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger-ui">https://github.com/maemo-leste/rtcom-eventlogger-ui</a></li> </ul> <p>The addressbook interface is also underway and is being RE'd from the Fremantle binaries: <a class="reference external" href="https://github.com/maemo-leste/osso-abook/">https://github.com/maemo-leste/osso-abook/</a></p> </div> <div class="section" id="maemo-input-sounds"> <h3>maemo-input-sounds</h3> <p>To test the MCE vibration driver, work has been started on <a class="reference external" href="https://github.com/maemo-leste/maemo-input-sounds/tree/wip">maemo-input-sounds</a>, which uses the <cite>X11 Record</cite> extension to monitor for touchscreen and key presses, and in reaction to those, either vibrate the device, play a sound, or even both.</p> <p>The status can be tracked in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/389">issue #389</a>. A fully functioning <tt class="docutils literal"><span class="pre">maemo-input-sounds</span></tt> probably depends on getting the audio set up completely (see <a class="reference internal" href="#next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5">Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5</a>).</p> </div> <div class="section" id="calendar-backend-and-frontend"> <h3>Calendar backend and frontend</h3> <p>Some more work is being done by <tt class="docutils literal">buZz</tt> and <tt class="docutils literal">sicelo</tt> to get the calendar software up and running. The backend, <tt class="docutils literal"><span class="pre">calendar-backend</span></tt> is already building fine, but the frontend (<tt class="docutils literal">qalendar</tt>) is still blocking on the Qt 5 port:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/buzztiaan/calendar-backend">https://github.com/buzztiaan/calendar-backend</a></li> <li><a class="reference external" href="https://github.com/buzztiaan/libgq">https://github.com/buzztiaan/libgq</a></li> <li><a class="reference external" href="https://github.com/buzztiaan/qalendar">https://github.com/buzztiaan/qalendar</a></li> </ul> <p>We expect this to fold in rather quickly once <tt class="docutils literal"><span class="pre">osso-abook</span></tt> is mostly ready.</p> </div> <div class="section" id="hildon-home-fixes"> <h3>hildon-home fixes</h3> <p><tt class="docutils literal"><span class="pre">hildon-home</span></tt> would frequently try to monitor non existing directories for changes, but because the directories did not exist, kept retrying the monitor calls. This resulted in significantly higher power usage. This has been fixed now, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/264">issue #264</a> for more details.</p> <p>Additionally, since our move to Beowulf, two plugins for <tt class="docutils literal"><span class="pre">hildon-home</span></tt> would no longer load (due to <tt class="docutils literal"><span class="pre">hildon-home</span></tt> loading them from a non-existing path), but this too has now been fixed:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41">https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba">https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba</a></li> </ul> </div> </div> <div class="section" id="device-support"> <h2>Device support</h2> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>The Motorola Droid 4 has seen a big set of improvements:</p> <ul class="simple"> <li>The <a class="reference internal" href="#ambient-light-sensor">Ambient Light Sensor</a> is now used;</li> <li>The <a class="reference internal" href="#vibration-motor">Vibration Motor</a> is now used;</li> <li>A driver for the <a class="reference internal" href="#accelerometer">Accelerometer</a> is available;</li> <li>Advanced <a class="reference internal" href="#keyboard-layout">keyboard layout</a></li> <li>Basic <a class="reference internal" href="#modem-integration">modem integration</a> in <cite>beowulf-devel</cite> branches;</li> <li>Much improved battery life through better <a class="reference internal" href="#power-management">Power Management</a>;</li> <li>Latest Linux kernel</li> </ul> <div class="section" id="ambient-light-sensor"> <h4>Ambient Light Sensor</h4> <p>Just like the Nokia N900, the Droid has an ambient light sensor, used to measure exactly that: ambient light levels. This can be used to adjust the screen brightness to the ambient light levels, based on the brightness profile selected. For observant users, this already worked on the Nokia N900, but now this also works on the Droid 4.</p> <p>This should make your device more pleasant to use in darker rooms, but also outside - in direct sunlight.</p> <p>Additionally, if the light level is low, the device is unlocked, and the keyboard is exposed, the keyboard backlight LEDs will be turned on, to allow for optimal typing in the dark. :-)</p> <p>See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/">MCE PR 8</a>.</p> </div> <div class="section" id="vibration-motor"> <h4>Vibration Motor</h4> <p>Once <a class="reference external" href="https://github.com/maemo-leste/mce/pull/9">MCE PR 9</a> is merged, the vibration motor on the Motorola Droid 4 (and actually also the Nokia N900 and other devices that support the Linux <a class="reference external" href="https://www.kernel.org/doc/html/latest/input/ff.html">FF</a> interface) will work. This allows for vibration of the device to provide touchscreen haptic feedback to the user, but also when (in the near future) an SMS is received, or the device receives a phone call.</p> <p>See also these notes on Maemo.org <a class="reference external" href="https://wiki.maemo.org/Phone_control#Start_Vibrating_Incoming_Call">on how to start and stop vibrations</a>. Since we are compatible at least on the DBUS level, the original Maemo instructions just apply. It is also possible to add more patterns by editing <tt class="docutils literal">/etc/mce/mce.ini</tt>.</p> </div> <div class="section" id="accelerometer"> <h4>Accelerometer</h4> <p>The accelerometer driver is now enabled, meaning that things like the <a class="reference external" href="https://github.com/buzztiaan/droidsaber">droidsaber</a> are now possible:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/DeCtO8WwaTc" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>This will also be useful for automatically changing the screen orientation, based on the device orientation. The powervr driver might need a bit more work before that will work smoothly and well though.</p> </div> <div class="section" id="power-management"> <h4>Power Management</h4> <p>The power management on the Droid 4 should be in much better shape now. Under ideal circumstances, with the modem online, the device should idle at about <tt class="docutils literal">60mW</tt>. This is made possible by the incredible Linux kernel support, <a class="reference external" href="https://github.com/maemo-leste/droid4-pm">droid4-pm</a>, our various <a class="reference internal" href="#mce">mce</a> improvements, and in general OMAP being well designed when it comes to power management. This should last most batteries for several days. Things might improve a little more if OMAP <tt class="docutils literal">OFF</tt> mode ever starts to work on OMAP 4.</p> <p><tt class="docutils literal">Merlijn</tt> recently acquired a few lab power supplies, and (<a class="reference external" href="https://sourceforge.net/p/sigrok/mailman/message/37014835/">after actually making it work with sigrok, working around insanely stupid firmware bugs</a>) was able to generate the following graph of power usage from a clean power-up, showing the ~3 minutes it takes to fully boot and enter the promised <tt class="docutils literal">60mW</tt> idle power usage:</p> <img alt="" src="/images/droid4-boot.png" style="width: 700px; height: 350px;" /> <p>Here's what using the vibration motor does to the power draw:</p> <img alt="" src="/images/droid4-rumble.png" style="width: 576px; height: 324px;" /> <p>And the same for receiving an SMS (exposing a problem where the modem doesn't properly idle after sms receive - it stays around <tt class="docutils literal">180mW</tt> as opposed to the <tt class="docutils literal">60mW</tt> - this is still being investigated, but it looks like the USB doesn't idle afterwards, requiring to be manually kicked into idle mode):</p> <img alt="" src="/images/droid4-modem-power-recv-sms.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="ntpd-and-power-management"> <h4>NTPD and power management</h4> <p>The <tt class="docutils literal">ntp</tt> daemon currently causes a lot of wake ups, and negatively impacts battery life. The current stop-gap is to stop it manually after booting, by issuing the following as root:</p> <pre class="literal-block"> /etc/init.d/ntp stop </pre> </div> <div class="section" id="cellular-and-power-management"> <h4>Cellular and power management</h4> <p>While the modem itself should idle pretty well, the modem reports on the signal strength very frequently, waking up the device even when the signal strength should not be shown. The signal strength can be temporarily disabled like so:</p> <pre class="literal-block"> printf 'U1234AT+SCRN=0\r' &gt; /dev/gsmtty1 </pre> </div> <div class="section" id="graphing-power-logs-from-the-device"> <h4>Graphing power logs from the device</h4> <p>The GNOME Power Manager can plot upower data, and it runs on Leste:</p> <img alt="" src="/images/leste-droid4-gnome-power-manager.png" style="width: 576px; height: 324px;" /> <p>But the upower data is located in <tt class="docutils literal">/var/lib/upower</tt> and not at all hard to plot yourself, which might actually be more insightful (although this graph is very basic):</p> <img alt="" src="/images/capacity_over_time_from_upower.png" style="width: 576px; height: 324px;" /> <p>We're still figuring out how to properly plot all this data, but more information (including the source to generate the above graph) can be found in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/396">issue #396</a>.</p> <p>Maybe we can take <a class="reference external" href="http://maemo.org/downloads/search/application.html?org_openpsa_products_search%5B1%5D%5Bproperty%5D=title&amp;org_openpsa_products_search%5B1%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B1%5D%5Bvalue%5D=battery&amp;org_openpsa_products_search%5B2%5D%5Bproperty%5D=os&amp;org_openpsa_products_search%5B2%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B2%5D%5Bvalue%5D=Maemo5&amp;fetch=Search">one of these maemo.org applications</a> and port them.</p> </div> <div class="section" id="battery-calibration"> <h4>Battery calibration</h4> <p><tt class="docutils literal">uvos</tt> has written an init script and tool to store the battery capacity when known, and restore it, using <tt class="docutils literal">spinal84</tt>'s experimental kernel patches, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/374">issue #374</a>.</p> <p>It will be added to the Droid 4 meta package imminently, and then eventually everyone should have a calibrated battery, hopefully.</p> <p>Also see <a class="reference external" href="https://github.com/maemo-leste/upower/pull/4">upower PR 4</a> for the UPower fix that was required for this to work properly.</p> </div> <div class="section" id="keyboard-layout"> <h4>Keyboard layout</h4> <p>For a long time, it was not possible to <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/347">summon the special keys virtual keyboard on the Droid 4</a>, which was particularly annoying since some <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/122">important keys were not available</a>.</p> <p>By digging through the N900 keyboard files and learning a bunch about xkb, both of these issues have now been resolved by <tt class="docutils literal">Merlijn</tt>. <tt class="docutils literal">buZz</tt> provided a nice <a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/99343d77464299cdf1d56e461018bd7f974cee42">geometry file</a>, which allows us to visualise the keys on various keyboard levels:</p> <img alt="" src="/images/droid4-keyboard.png" style="width: 576px; height: 224px;" /> <p>(Yes, the shift button on the Droid 4 is mapped to control, and the caps lock key is mapped to shift)</p> <p>Additional extra keys are also available when using the <tt class="docutils literal">ISO_Level3_Shift</tt> key, <a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/ccebc5ea6cc9c14c7822b53317640c8f2f6372b2#diff-5b7bd0a2cb0498ff38e4e466546d5fdcR36">see the actual xkb file for more details</a> and this image for a quick reference:</p> <img alt="" src="/images/droid4-keyboard-2.png" style="width: 576px; height: 224px;" /> <p>Compare that to the N900 layout:</p> <img alt="" src="/images/n900-keyboard.png" style="width: 576px; height: 224px;" /> <p>Bringing up the special keys virtual keyboard is done by pressing the &quot;OK&quot; (<tt class="docutils literal">ISO_Level3_Shift</tt>) key and the Control (<tt class="docutils literal">Shift</tt>) key.</p> <p>And finally, the virtual keyboard didn't look quite good on the Droid 4, since it has a larger resolution, but as of <a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/3">hildon-input-method-plugins PR 3</a>, the keyboard will render properly regardless of the screen dimensions:</p> <img alt="" src="/images/droid4-special-vkb.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="modem-integration"> <h4>Modem integration</h4> <p><tt class="docutils literal">tmlind</tt> and <tt class="docutils literal">Pavel Machek</tt> have been doing a lot of work on improving ofono on the Droid 4. The result of most of that work is currently packaged in the <tt class="docutils literal">droid4</tt> component, so any droid 4 will automatically get the latest/best ofono version. Additionally, the technology is now also reported properly:</p> <img alt="" src="/images/droid4-tech.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/droid4-tech-2g.png" style="width: 576px; height: 324px;" /> <p>More work remains, including upstreaming ofono and dealing with some power management regressions, but it's starting to look quite good indeed.</p> <p>Current work can be found here: <a class="reference external" href="https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm">https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm</a></p> </div> <div class="section" id="increasing-font-size-in-osso-xterm"> <h4>increasing font size in osso-xterm</h4> <p>On the Nokia N900, the font size in osso-xterm can be changed using the volume buttons, but this does not work yet on the Droid 4. The reason is that osso-xterm expects specific (hardcoded) keys to be used to change the font, and the Droid 4 has different keys mapped to its volume buttons, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/385">issue #385</a></p> </div> <div class="section" id="latest-linux-kernel"> <h4>Latest Linux kernel</h4> <p>A month or so ago we switched to Linux 5.7: <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7">https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7</a></p> <p>After that, there were various regressions to figure out, the most painful ones being random resets, which took quite a while to pin down. <tt class="docutils literal">tmlind</tt> has been incredibly helpful in getting these problems resolved. Onto the next Linux version and set of regressions - and bugfixes, and features...</p> </div> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <div class="section" id="powermanagement-update"> <h4>Powermanagement update</h4> <p>A while ago we tweeted out a photo of a Nokia N900 using very little power, while in <tt class="docutils literal">OMAP OFF</tt> mode. We haven't yet brought this to our latest images, but it's still planned (it might be relatively simple, but also might be a lot of work). In addition, we will likely provide an <tt class="docutils literal"><span class="pre">n900-pm</span></tt> script, similar to the <tt class="docutils literal"><span class="pre">droid4-pm</span></tt> script.</p> </div> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>Thanks to the packaging work from people in postmarketOS, we now also support the modem in the Pinephone. While we've mostly been working with cellular things on the Droid4, lots of that work can simply be reused on the Pinephone, and we plan to do so in the near future. A package called <tt class="docutils literal"><span class="pre">pinephone-modem-config</span></tt> can be installed, and along with updating the kernel (latest available version is 5.6), it will bring in modem support. This is already automatically enabled in the latest images. A note to keep in mind: While the modem is off, combined with the latest kernels, the system outputs KEY_WAKEUP events which cause some trouble with the virtual keyboard. The current solution to this is to just have <tt class="docutils literal"><span class="pre">pinephone-modem-config</span></tt> installed and after a reboot, things should be ok. We will see if it's possible to patch this in some proper way in the future.</p> </div> </div> <div class="section" id="weekly-builds"> <h2>Weekly builds</h2> <p>From July, we will also implement and enable weekly image builds on our CI infrastructure. This means we won't be building images on demand anymore. Instead they shall be built each week, containing all the latest packages and goodies. Obviously, this will require more storage space, so we will be removing device images older than five weeks.</p> <p>Hopefully this will also help us polish up our build frameworks and alert us about possible bugs that arise during development. It is also a very important step towards reproducible builds - which is one of our milestones we wish to fulfill.</p> <p>However, for this occasion, we built new images and they can be downloaded as usual. This time we've also built 64bit images for the Raspberry Pi 3 and 4.</p> <ul class="simple"> <li>64bit VM: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200622/">https://maedevu.maemo.org/images/virtual-machines/20200622/</a></li> <li>N900: <a class="reference external" href="https://maedevu.maemo.org/images/n900/20200623/">https://maedevu.maemo.org/images/n900/20200623/</a></li> <li>Droid4: <a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200624/">https://maedevu.maemo.org/images/droid4/20200624/</a></li> <li>Pinephone: <a class="reference external" href="https://maedevu.maemo.org/images/pinephone/20200624/">https://maedevu.maemo.org/images/pinephone/20200624/</a></li> <li>Pinetab: <a class="reference external" href="https://maedevu.maemo.org/images/pinetab/20200624/">https://maedevu.maemo.org/images/pinetab/20200624/</a></li> <li>Pi3: <a class="reference external" href="https://maedevu.maemo.org/images/raspi3-64bit/20200623/">https://maedevu.maemo.org/images/raspi3-64bit/20200623/</a></li> <li>Pi4: <a class="reference external" href="https://maedevu.maemo.org/images/raspi4-64bit/20200623/">https://maedevu.maemo.org/images/raspi4-64bit/20200623/</a></li> </ul> </div> <div class="section" id="community-showcase"> <h2>Community showcase</h2> <div class="section" id="ps-1-emulator"> <h3>PS 1 emulator</h3> <p>PCSX-ReARMed runs quite nicely on the Droid 4:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/BmIAQby4ccM" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>Unfortunately, the community hasn't yet packaged the program for Maemo Leste Extras, but we're confident someone will, at some point.</p> </div> <div class="section" id="photo-light-meter"> <h3>Photo Light meter</h3> <p>Written in Free Pascal, photolightmeter can be used calculate aperture and shutter values.</p> </div> <div class="section" id="telegram"> <h3>Telegram</h3> <p>If you're a fan of Telegram, the desktop client just works on Maemo Leste:</p> <ul class="simple"> <li><a class="reference external" href="https://twitter.com/rfc1087/status/1271796014903635969">https://twitter.com/rfc1087/status/1271796014903635969</a></li> </ul> </div> <div class="section" id="proxmark3"> <h3>Proxmark3</h3> <p>If you like toying with RFID cards, then you can (for example) use the bluetooth module on the Droid 4 to connect a capable reader and run proxmark3 on the Droid itself:</p> <img alt="" src="/images/proxmark3-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/proxmark3-2.png" style="width: 576px; height: 324px;" /> <p>You can find specific installation notes here: <a class="reference external" href="http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276">http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276</a></p> </div> <div class="section" id="quicknote"> <h3>Quicknote</h3> <p>A simple notes application written in Python is also available: <a class="reference external" href="https://github.com/maemo-leste-extras/quicknote">https://github.com/maemo-leste-extras/quicknote</a></p> </div> <div class="section" id="mihphoto"> <h3>mihphoto</h3> <p>A Qt 5 photo viewer is available, and optionally supports multitouch when supplied as a startup argument: <a class="reference external" href="https://github.com/maemo-leste-extras/mihphoto">https://github.com/maemo-leste-extras/mihphoto</a></p> </div> <div class="section" id="personal-ip-address"> <h3>personal-ip-address</h3> <p>The good old personal-ip-address has returned, this time to Leste: <a class="reference external" href="https://github.com/maemo-leste-extras/personal-ip-address">https://github.com/maemo-leste-extras/personal-ip-address</a></p> </div> </div> <div class="section" id="maemo-leste-extras"> <h2>Maemo Leste Extras</h2> <p>More community packages are being maintained in the <tt class="docutils literal">extras</tt> repository and we're very glad and excited about it. If you're interested in maintaing your own community package for Maemo Leste, there are instructions for you to do so on the <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">bugtracker</a> .</p> </div> <div class="section" id="next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5"> <h2>Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5</h2> <p>So what can you expect from future updates?</p> <p>The big things on our radar are still:</p> <ul> <li><p class="first">Audio: Currently most devices do not even ship with <tt class="docutils literal">pulseaudio</tt>, but we'll probably want to start using it, and create ALSA UCM files for our soundcards, provide proper pulseaudio sink names for call routing, and so on. This is also a prerequisite for the <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume">volume applet</a></p> </li> <li><p class="first">Contacts (<tt class="docutils literal"><span class="pre">osso-abook</span></tt>), this will provide all of the Hildon contacts APIs with the evolution database as a abackend, definitely required for proper SMS and Call UI</p> </li> <li><p class="first">Qt 5 updates: hopefully we will soon have the virtual keyboard integration ready, with the hildon menus and stacked windows following right after. That should be enough to make most applications work, and from there on we'll probably port things on an as-needed basis: like APIs for home and status widgets</p> </li> <li><p class="first">Nokia's <tt class="docutils literal">rtcom</tt> packages and telepathy. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390">https://github.com/maemo-leste/bugtracker/issues/390</a> Some of this is covered in <a class="reference internal" href="#steps-towards-calls-and-texts">Steps towards calls and texts</a>, but to reiterate: the plan is to use <cite>telepathy-ring</cite> as an interface to <cite>ofono</cite>, and use <cite>rtcom-eventlogger</cite> and other libraries to read from and log to the same database format as used on Fremantle. This approach is particularly exciting because it allows loading many other telepathy plugins. There also exists a <a class="reference external" href="https://github.com/dylex/slack-libpurple/commits/master">telepathy-haze</a> plugin to load (any) Pidgin (<tt class="docutils literal">libpurple</tt>) plugin, allowing for potentially loading (for example) the <a class="reference external" href="https://github.com/dylex/slack-libpurple">slack-libpurple</a> slack plugin into telepathy, and being able to directly interface with Slack using the native hildon UI, potentially even with contacts, too. And of course, there are also SIP plugins for telepathy, allowing for VOIP calls from the same (native) UI</p> </li> <li><p class="first">Speaking of UIs, once the backend (rtcom) is mostly there, the last thing we'll have to do is to bring up the call and text UIs. The Fremantle SMS UI relied on an html rendering engine, <a class="reference external" href="https://wiki.maemo.org/Conversation_Mods">allowing for cool customisations</a> like these:</p> <img alt="" src="/images/fun-conversations-mod.png" style="width: 432px; height: 256px;" /> </li> </ul> </div> <div class="section" id="web-interface-for-packages"> <h2>Web interface for packages</h2> <p>We're considering creating a web interface to browse the core maemo packages, the development packages and also the extras packages. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/395">issue #395</a> for more details. If you have suggestions, want to see specific features, or want to help out, please do let us know on the issue.</p> <p>Sneak peak of an alpha version of the interface:</p> <img alt="" src="/images/pkg.png" /> </div> <div class="section" id="more-frequent-updates"> <h2>More frequent updates?</h2> <p>We often get the question if we can provide update posts more frequently. Often, we delay update posts because we want to <strong>complete just one more package...</strong> - and then another, and another... So if you'd like to get more frequent update posts, please volunteer to write them for us. If you hang out in the IRC channel, maybe follow the frequent updates and write about them, and we'll be able to post it here, on our website.</p> <p>That said, we're considering doing detailed write-ups of various core components of Maemo Leste every few weeks or so, so if that's your thing, you might be able to peek at those too, soon.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">bugtracker</a></p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2020-06-24T18:00:00+02:002020-06-24T18:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2020-06-24:/maemo-leste-thirteenth-update-april-may-june-2020.html

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-twelfth-update-february-and-march-2020.html">last update</a>, so let's start with a few highlights:</p> <ul class="simple"> <li>We have improved power management on the Droid 4, and currently, under ideal conditions, the power draw is about <tt class="docutils literal">60mW</tt> with the modem turned on. That should last a few days on a decent battery …</li></ul>

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-twelfth-update-february-and-march-2020.html">last update</a>, so let's start with a few highlights:</p> <ul class="simple"> <li>We have improved power management on the Droid 4, and currently, under ideal conditions, the power draw is about <tt class="docutils literal">60mW</tt> with the modem turned on. That should last a few days on a decent battery</li> <li>Various sensors and other hardware of the Motorola Droid 4 are now usable with Maemo Leste</li> <li>A lot of kernel bugs/regressions have been chased and fixed</li> <li>Cellular support is improving; cellular data should now work</li> <li>Maemo Leste Extras should contain quite a few more packages now</li> <li><tt class="docutils literal"><span class="pre">leste-config-*</span></tt> packages now exist to provide seamless configuration updates and changes, so there should be less of a need to &quot;reinstall&quot; on every new image release</li> </ul> <div class="section" id="software-changes"> <h2>Software changes</h2> <div class="section" id="mce"> <h3>mce</h3> <p>The Mode Control Entity has seen significant changes.</p> <p>MCE will now properly blank the screen, allowing the SoC to idle, which in turn allows for significant power saving (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/338">see issue #338</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/5">MCE PR 5</a>).</p> <p>With the newer versions, the touchscreen will also be properly disabled when the device is locked. This will prevent 'accidental' input events being sent to applications while the device is locked. MCE will also close the file descriptors of any touchscreen devices and tell X11 to disable the touchscreens to let the touchscreen driver idle properly. For more details, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/340">issue #340</a>, <a class="reference external" href="https://github.com/maemo-leste/mce/pull/6">MCE PR 6</a> and <a class="reference external" href="https://github.com/maemo-leste/mce/pull/7">MCE PR 7</a>.</p> <p>Furthermore, we've made a change to the default <tt class="docutils literal">/etc/mce/mce.ini</tt> configuration file to prevent accidental shutdowns on the Droid 4. We've <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/392">increased the time one has to press the power key to shutdown the device (issue #392)</a>.</p> <p>ALS (Ambient Light Sensor) support has been extended, and it now also works on the <a class="reference internal" href="#motorola-droid-4">Motorola Droid 4</a>. See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/">MCE PR 8</a>.</p> <p>A module contributed by <tt class="docutils literal">uvos</tt> to support vibration in MCE is also expected to land in the next few days. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/132">issue #132</a> and <a class="reference external" href="https://github.com/maemo-leste/mce/pull/9">MCE PR 9</a>.</p> <p>Something else to look forward to is the execution of mode-change shell scripts, to allow certain programs or scripts to be executed when a device is locked, unlocked, or enters other mce (sub)modes.</p> </div> <div class="section" id="input-and-focus-fixes"> <h3>Input and Focus fixes</h3> <p>libmatchbox2 and hildon-desktop (the Maemo window manager) have had <a class="reference external" href="https://bugs.maemo.org/show_bug.cgi?id=5987">long standing bugs with regards to input focus</a>, which also made it <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/346">impossible to send keyboard events to vanilla Qt 5 applications</a>.</p> <p><tt class="docutils literal">freemangordon</tt> and <tt class="docutils literal">uvos</tt> have been trying to get to the bottom of the problem. The result of that effort is that all known problematic input and focus issues are now fixed. Now xev happily receives events, es2gears responds to keyboard input events, and Qt 5 applications take input the way they are supposed to.</p> <p>Relevant pull requests:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/3">libmatchbox PR 3</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/4">libmatchbox PR 4</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/4">hildon-desktop PR 4</a></li> </ul> </div> <div class="section" id="qt-5-progress-is-being-made"> <h3>Qt 5: Progress is being made</h3> <p>The Maemo Qt 5 port is not finished yet, but has seen various improvements. Merlijn has been doing work porting the &quot;Hildon Input Method&quot; virtual keyboard patches to Qt 5. Due to the more clear architecture of Qt 5, our unwillingness to fork Qt 5 as a whole, and the fact that we're also porting from old <tt class="docutils literal">Xlib</tt> code to <tt class="docutils literal">xcb</tt>, the work is taking a little bit more time. On the upside, all the Maemo Qt 5 bits will hopefully available via a <a class="reference external" href="https://doc.qt.io/qt-5/qpa.html">Qt 5 loadable platform module</a>.</p> <p>Apart from the virtual keyboard, there are at least two important pieces missing:</p> <ul class="simple"> <li>QMenu support, to allow hildon-style menu items to show when the application title is touched/pressed</li> <li>Hildon-style stacked windows</li> </ul> <p>We've also ported over a sample application, <a class="reference external" href="https://github.com/maemo-leste-extras/countdowntimer">countdowntimer</a>:</p> <img alt="" src="/images/countdowntimer.png" style="width: 576px; height: 324px;" /> <p>To make it usable, we had to have the application respect desktop sizes other than the <cite>800x480</cite> that the Nokia N900 screen supports, to prevent it from looking like this:</p> <img alt="" src="/images/leste-qt5-countdowntimer-0.1.png" style="width: 576px; height: 324px;" /> <p>Countdowntimer itself also makes use of the specialised QMenu and Hildon stackable windows, but is already quite usable even without those modifications.</p> <p>Development can be done directly on the VM, using X11 forwarding:</p> <img alt="" src="/images/leste-qt5-designer-x11-forward.png" style="width: 576px; height: 324px;" /> <p>You can also use Qt Designer with the native Maemo theme, but, well...:</p> <img alt="" src="/images/leste-designer-lol.png" style="width: 576px; height: 324px;" /> <p>If you plan to use Qt designer on your device, you might want to look at <a class="reference internal" href="#xephyr-nested-xorg-server-on-maemo">Xephyr (Nested Xorg server) on Maemo</a> instead.</p> <p>In the next month, we hope to mostly finish the Qt 5 port. Keep in mind that many Qt 5 applications are already usable on Maemo Leste as is. This is also documented in <a class="reference internal" href="#community-showcase">Community showcase</a>!</p> </div> <div class="section" id="xephyr-nested-xorg-server-on-maemo"> <h3>Xephyr (Nested Xorg server) on Maemo</h3> <p>Xephyr is a nested X server, which can run in a window on Maemo Leste, allowing you to run any ordinary desktop application on Maemo Leste, in a window.</p> <p>It's especially useful for devices with physical keyboards.</p> <p>Installing it is as simple as:</p> <pre class="literal-block"> sudo apt install xephyr </pre> <p>And then start it as follows:</p> <pre class="literal-block"> Xephyr :1 &amp; </pre> <p>And launch applications inside that server like so:</p> <pre class="literal-block"> DISPLAY=:1 dwm &amp; DISPLAY=:1 xterm </pre> <img alt="" src="/images/xephyr-droid4.png" style="width: 576px; height: 324px;" /> <p>Enjoy!</p> </div> <div class="section" id="cellular-data-and-ofono-support"> <h3>Cellular data and ofono support</h3> <p>The <tt class="docutils literal"><span class="pre">beowulf-devel</span></tt> repository of Maemo Leste now has the <tt class="docutils literal"><span class="pre">libicd-network-ofono</span></tt> plugin for <tt class="docutils literal">icd2</tt> to allow for making GPRS/UMTS/LTE data connections:</p> <img alt="" src="/images/droid4-libicd-network-ofono.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/droid4-libicd-network-ofono-2.png" style="width: 576px; height: 324px;" /> <p>This should work on all of the supported devices, as long as their ofono version (and SIM) supports data connections.</p> <p>Additionally, there were some problems on Beowulf where user <tt class="docutils literal">user</tt> (the default user in Maemo) had no access to the ofono dbus interface, but this has been fixed in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/372">issue #372</a>.</p> <p>Finally, once this work has seen a bit more testing, we will create a meta package to automatically install all the cellular packages, and all devices will automatically get the cellular support when they <tt class="docutils literal">apt update &amp;&amp; apt upgrade</tt>.</p> </div> <div class="section" id="wireless"> <h3>Wireless</h3> <p>Wireless is mostly just working, although the UI still has some rough edges. In particular, sometimes connecting to a network fails if entering the password takes too long.</p> <p>One other bug was fixed: a problem where the networks would appear in the network dialog, but would not be selectable until the next scan returned, which was really annoying. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/253">issue #253</a> and <a class="reference external" href="https://github.com/maemo-leste/connui-internet/pull/1">connui-internet PR</a>.</p> </div> <div class="section" id="themes"> <h3>Themes</h3> <p>The retro <a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-okuda">Okuda theme</a> is now available:</p> <img alt="" src="/images/leste-okuda-desktop.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-okuda-vkb.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-okuda-xterm.png" style="width: 576px; height: 324px;" /> <p><a class="reference external" href="https://github.com/maemo-leste-extras/miku-theme">Miku theme</a>:</p> <img alt="" src="/images/leste-miku-settings.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-miku-desktop.png" style="width: 576px; height: 324px;" /> <p><a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-matrix">Matrix theme</a>:</p> <img alt="" src="/images/leste-matrix-desktop.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-matrix-lock.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="openrc-integration-in-debian-fixes"> <h3>OpenRC integration in Debian fixes</h3> <p>We've successfully submitted a patch to SysVinit upstream, which brings in better support for OpenRC and its internals to both Debian and Devuan. It has not yet propagated to Devuan, but it is expected to happen, of course. In Maemo Leste we already provide the patched version and maintain it ourselves until it is available in Devuan. The patch itself brings in proper OpenRC support in the insserv tool, which means that LSB headers aren't necessary for OpenRC initscripts and they now get installed in the default runlevel without the need for manual interference.</p> <p>The patch was merged in <tt class="docutils literal">6a65f4412a2d24d78741f49e64e1128993341e65</tt>, and can be seen here:</p> <ul class="simple"> <li><a class="reference external" href="http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;id=6a65f4412a2d24d78741f49e64e1128993341e65">http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;id=6a65f4412a2d24d78741f49e64e1128993341e65</a></li> </ul> <p>If you found that some init scripts ended up in <tt class="docutils literal">/etc/runlevels</tt> instead of <tt class="docutils literal">/etc/runlevels/default</tt>, try reinstalling the affected packages; they should install fine now.</p> </div> <div class="section" id="more-languages-added-to-virtual-keyboard-layouts"> <h3>More languages added to virtual keyboard layouts</h3> <p>Many more virtual keyboard layouts have been added. If you were ever in need of a Belarusian or Bulgarian keyboard layout, now is your time to <tt class="docutils literal">apt update &amp;&amp; apt upgrade</tt>.</p> <p>See <a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/2">hildon-input-method-plugins PR 2</a>.</p> </div> <div class="section" id="steps-towards-calls-and-texts"> <h3>Steps towards calls and texts</h3> <p>With <a class="reference internal" href="#cellular-data-and-ofono-support">Cellular data and ofono support</a> improving and other projects getting close to finished, it will soon be time to turn our attention to usable calls and texts on Maemo. We will use many of the same components that Maemo Fremantle uses, just in their updated forms, like the Mer project does.</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390">Issue #390</a> documents some of the steps we will be taking. It will look something like:</p> <ol class="arabic simple"> <li>Perform further analysis on how this works in Fremantle</li> <li>Import all the FOSS components (there are quite a number of them)</li> <li>Figure out audio (routing and) policies</li> <li>Reimplement the non-FOSS ones: call and sms UI are the big ones</li> <li>Use <tt class="docutils literal"><span class="pre">osso-abook</span></tt> in the alternative call and sms UIs</li> </ol> <p>The addressbook interface is also underway and is being RE'd from the Fremantle binaries: <a class="reference external" href="https://github.com/maemo-leste/osso-abook/">https://github.com/maemo-leste/osso-abook/</a></p> </div> <div class="section" id="maemo-input-sounds"> <h3>maemo-input-sounds</h3> <p>To test the MCE vibration driver, work has been started on <a class="reference external" href="https://github.com/maemo-leste/maemo-input-sounds/tree/wip">maemo-input-sounds</a>, which uses the <cite>X11 Record</cite> extension to monitor for touchscreen and key presses, and in reaction to those, either vibrate the device, play a sound, or even both.</p> <p>The status can be tracked in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/389">issue #389</a>. A fully functioning <tt class="docutils literal"><span class="pre">maemo-input-sounds</span></tt> probably depends on getting the audio set up completely (see <a class="reference internal" href="#next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5">Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5</a>).</p> </div> <div class="section" id="calendar-backend-and-frontend"> <h3>Calendar backend and frontend</h3> <p>Some more work is being done by <tt class="docutils literal">buZz</tt> and <tt class="docutils literal">sicelo</tt> to get the calendar software up and running. The backend, <tt class="docutils literal"><span class="pre">calendar-backend</span></tt> is already building fine, but the frontend (<tt class="docutils literal">qalendar</tt>) is still blocking on the Qt 5 port:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/buzztiaan/calendar-backend">https://github.com/buzztiaan/calendar-backend</a></li> <li><a class="reference external" href="https://github.com/buzztiaan/libgq">https://github.com/buzztiaan/libgq</a></li> <li><a class="reference external" href="https://github.com/buzztiaan/qalendar">https://github.com/buzztiaan/qalendar</a></li> </ul> <p>We expect this to fold in rather quickly once <tt class="docutils literal"><span class="pre">osso-abook</span></tt> is mostly ready.</p> </div> <div class="section" id="hildon-home-fixes"> <h3>hildon-home fixes</h3> <p><tt class="docutils literal"><span class="pre">hildon-home</span></tt> would frequently try to monitor non existing directories for changes, but because the directories did not exist, kept retrying the monitor calls. This resulted in significantly higher power usage. This has been fixed now, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/264">issue #264</a> for more details.</p> <p>Additionally, since our move to Beowulf, two plugins for <tt class="docutils literal"><span class="pre">hildon-home</span></tt> would no longer load (due to <tt class="docutils literal"><span class="pre">hildon-home</span></tt> loading them from a non-existing path), but this too has now been fixed:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41">https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba">https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba</a></li> </ul> </div> </div> <div class="section" id="device-support"> <h2>Device support</h2> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>The Motorola Droid 4 has seen a big set of improvements:</p> <ul class="simple"> <li>The <a class="reference internal" href="#ambient-light-sensor">Ambient Light Sensor</a> is now used;</li> <li>The <a class="reference internal" href="#vibration-motor">Vibration Motor</a> is now used;</li> <li>A driver for the <a class="reference internal" href="#accelerometer">Accelerometer</a> is available;</li> <li>Advanced <a class="reference internal" href="#keyboard-layout">keyboard layout</a></li> <li>Basic <a class="reference internal" href="#modem-integration">modem integration</a> in <cite>beowulf-devel</cite> branches;</li> <li>Much improved battery life through better <a class="reference internal" href="#power-management">Power Management</a>;</li> <li>Latest Linux kernel</li> </ul> <div class="section" id="ambient-light-sensor"> <h4>Ambient Light Sensor</h4> <p>Just like the Nokia N900, the Droid has an ambient light sensor, used to measure exactly that: ambient light levels. This can be used to adjust the screen brightness to the ambient light levels, based on the brightness profile selected. For observant users, this already worked on the Nokia N900, but now this also works on the Droid 4.</p> <p>This should make your device more pleasant to use in darker rooms, but also outside - in direct sunlight.</p> <p>Additionally, if the light level is low, the device is unlocked, and the keyboard is exposed, the keyboard backlight LEDs will be turned on, to allow for optimal typing in the dark. :-)</p> <p>See <a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/">MCE PR 8</a>.</p> </div> <div class="section" id="vibration-motor"> <h4>Vibration Motor</h4> <p>Once <a class="reference external" href="https://github.com/maemo-leste/mce/pull/9">MCE PR 9</a> is merged, the vibration motor on the Motorola Droid 4 (and actually also the Nokia N900 and other devices that support the Linux <a class="reference external" href="https://www.kernel.org/doc/html/latest/input/ff.html">FF</a> interface) will work. This allows for vibration of the device to provide touchscreen haptic feedback to the user, but also when (in the near future) an SMS is received, or the device receives a phone call.</p> <p>See also these notes on Maemo.org <a class="reference external" href="https://wiki.maemo.org/Phone_control#Start_Vibrating_Incoming_Call">on how to start and stop vibrations</a>. Since we are compatible at least on the DBUS level, the original Maemo instructions just apply. It is also possible to add more patterns by editing <tt class="docutils literal">/etc/mce/mce.ini</tt>.</p> </div> <div class="section" id="accelerometer"> <h4>Accelerometer</h4> <p>The accelerometer driver is now enabled, meaning that things like the <a class="reference external" href="https://github.com/buzztiaan/droidsaber">droidsaber</a> are now possible:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/DeCtO8WwaTc" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>This will also be useful for automatically changing the screen orientation, based on the device orientation. The powervr driver might need a bit more work before that will work smoothly and well though.</p> </div> <div class="section" id="power-management"> <h4>Power Management</h4> <p>The power management on the Droid 4 should be in much better shape now. Under ideal circumstances, with the modem online, the device should idle at about <tt class="docutils literal">60mW</tt>. This is made possible by the incredible Linux kernel support, <a class="reference external" href="https://github.com/maemo-leste/droid4-pm">droid4-pm</a>, our various <a class="reference internal" href="#mce">mce</a> improvements, and in general OMAP being well designed when it comes to power management. This should last most batteries for several days. Things might improve a little more if OMAP <tt class="docutils literal">OFF</tt> mode ever starts to work on OMAP 4.</p> <p><tt class="docutils literal">Merlijn</tt> recently acquired a few lab power supplies, and (<a class="reference external" href="https://sourceforge.net/p/sigrok/mailman/message/37014835/">after actually making it work with sigrok, working around insanely stupid firmware bugs</a>) was able to generate the following graph of power usage from a clean power-up, showing the ~3 minutes it takes to fully boot and enter the promised <tt class="docutils literal">60mW</tt> idle power usage:</p> <img alt="" src="/images/droid4-boot.png" style="width: 700px; height: 350px;" /> <p>Here's what using the vibration motor does to the power draw:</p> <img alt="" src="/images/droid4-rumble.png" style="width: 576px; height: 324px;" /> <p>And the same for receiving an SMS (exposing a problem where the modem doesn't properly idle after sms receive - it stays around <tt class="docutils literal">180mW</tt> as opposed to the <tt class="docutils literal">60mW</tt> - this is still being investigated, but it looks like the USB doesn't idle afterwards, requiring to be manually kicked into idle mode):</p> <img alt="" src="/images/droid4-modem-power-recv-sms.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="ntpd-and-power-management"> <h4>NTPD and power management</h4> <p>The <tt class="docutils literal">ntp</tt> daemon currently causes a lot of wake ups, and negatively impacts battery life. The current stop-gap is to stop it manually after booting, by issuing the following as root:</p> <pre class="literal-block"> /etc/init.d/ntp stop </pre> </div> <div class="section" id="cellular-and-power-management"> <h4>Cellular and power management</h4> <p>While the modem itself should idle pretty well, the modem reports on the signal strength very frequently, waking up the device even when the signal strength should not be shown. The signal strength can be temporarily disabled like so:</p> <pre class="literal-block"> printf 'U1234AT+SCRN=0\r' &gt; /dev/gsmtty1 </pre> </div> <div class="section" id="graphing-power-logs-from-the-device"> <h4>Graphing power logs from the device</h4> <p>The GNOME Power Manager can plot upower data, and it runs on Leste:</p> <img alt="" src="/images/leste-droid4-gnome-power-manager.png" style="width: 576px; height: 324px;" /> <p>But the upower data is located in <tt class="docutils literal">/var/lib/upower</tt> and not at all hard to plot yourself, which might actually be more insightful (although this graph is very basic):</p> <img alt="" src="/images/capacity_over_time_from_upower.png" style="width: 576px; height: 324px;" /> <p>We're still figuring out how to properly plot all this data, but more information (including the source to generate the above graph) can be found in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/396">issue #396</a>.</p> <p>Maybe we can take <a class="reference external" href="http://maemo.org/downloads/search/application.html?org_openpsa_products_search%5B1%5D%5Bproperty%5D=title&amp;org_openpsa_products_search%5B1%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B1%5D%5Bvalue%5D=battery&amp;org_openpsa_products_search%5B2%5D%5Bproperty%5D=os&amp;org_openpsa_products_search%5B2%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B2%5D%5Bvalue%5D=Maemo5&amp;fetch=Search">one of these maemo.org applications</a> and port them.</p> </div> <div class="section" id="battery-calibration"> <h4>Battery calibration</h4> <p><tt class="docutils literal">uvos</tt> has written an init script and tool to store the battery capacity when known, and restore it, using <tt class="docutils literal">spinal84</tt>'s experimental kernel patches, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/374">issue #374</a>.</p> <p>It will be added to the Droid 4 meta package imminently, and then eventually everyone should have a calibrated battery, hopefully.</p> <p>Also see <a class="reference external" href="https://github.com/maemo-leste/upower/pull/4">upower PR 4</a> for the UPower fix that was required for this to work properly.</p> </div> <div class="section" id="keyboard-layout"> <h4>Keyboard layout</h4> <p>For a long time, it was not possible to <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/347">summon the special keys virtual keyboard on the Droid 4</a>, which was particularly annoying since some <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/122">important keys were not available</a>.</p> <p>By digging through the N900 keyboard files and learning a bunch about xkb, both of these issues have now been resolved by <tt class="docutils literal">Merlijn</tt>. <tt class="docutils literal">buZz</tt> provided a nice <a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/99343d77464299cdf1d56e461018bd7f974cee42">geometry file</a>, which allows us to visualise the keys on various keyboard levels:</p> <img alt="" src="/images/droid4-keyboard.png" style="width: 576px; height: 224px;" /> <p>(Yes, the shift button on the Droid 4 is mapped to control, and the caps lock key is mapped to shift)</p> <p>Additional extra keys are also available when using the <tt class="docutils literal">ISO_Level3_Shift</tt> key, <a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/ccebc5ea6cc9c14c7822b53317640c8f2f6372b2#diff-5b7bd0a2cb0498ff38e4e466546d5fdcR36">see the actual xkb file for more details</a> and this image for a quick reference:</p> <img alt="" src="/images/droid4-keyboard-2.png" style="width: 576px; height: 224px;" /> <p>Compare that to the N900 layout:</p> <img alt="" src="/images/n900-keyboard.png" style="width: 576px; height: 224px;" /> <p>Bringing up the special keys virtual keyboard is done by pressing the &quot;OK&quot; (<tt class="docutils literal">ISO_Level3_Shift</tt>) key and the Control (<tt class="docutils literal">Shift</tt>) key.</p> <p>And finally, the virtual keyboard didn't look quite good on the Droid 4, since it has a larger resolution, but as of <a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/3">hildon-input-method-plugins PR 3</a>, the keyboard will render properly regardless of the screen dimensions:</p> <img alt="" src="/images/droid4-special-vkb.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="modem-integration"> <h4>Modem integration</h4> <p><tt class="docutils literal">tmlind</tt> and <tt class="docutils literal">Pavel Machek</tt> have been doing a lot of work on improving ofono on the Droid 4. The result of most of that work is currently packaged in the <tt class="docutils literal">droid4</tt> component, so any droid 4 will automatically get the latest/best ofono version. Additionally, the technology is now also reported properly:</p> <img alt="" src="/images/droid4-tech.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/droid4-tech-2g.png" style="width: 576px; height: 324px;" /> <p>More work remains, including upstreaming ofono and dealing with some power management regressions, but it's starting to look quite good indeed.</p> <p>Current work can be found here: <a class="reference external" href="https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm">https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm</a></p> </div> <div class="section" id="increasing-font-size-in-osso-xterm"> <h4>increasing font size in osso-xterm</h4> <p>On the Nokia N900, the font size in osso-xterm can be changed using the volume buttons, but this does not work yet on the Droid 4. The reason is that osso-xterm expects specific (hardcoded) keys to be used to change the font, and the Droid 4 has different keys mapped to its volume buttons, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/385">issue #385</a></p> </div> <div class="section" id="latest-linux-kernel"> <h4>Latest Linux kernel</h4> <p>A month or so ago we switched to Linux 5.7: <a class="reference external" href="https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7">https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7</a></p> <p>After that, there were various regressions to figure out, the most painful ones being random resets, which took quite a while to pin down. <tt class="docutils literal">tmlind</tt> has been incredibly helpful in getting these problems resolved. Onto the next Linux version and set of regressions - and bugfixes, and features...</p> </div> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <div class="section" id="powermanagement-update"> <h4>Powermanagement update</h4> <p>A while ago we tweeted out a photo of a Nokia N900 using very little power, while in <tt class="docutils literal">OMAP OFF</tt> mode. We haven't yet brought this to our latest images, but it's still planned (it might be relatively simple, but also might be a lot of work). In addition, we will likely provide an <tt class="docutils literal"><span class="pre">n900-pm</span></tt> script, similar to the <tt class="docutils literal"><span class="pre">droid4-pm</span></tt> script.</p> </div> </div> <div class="section" id="pinephone"> <h3>Pinephone</h3> <p>Thanks to the packaging work from people in postmarketOS, we now also support the modem in the Pinephone. While we've mostly been working with cellular things on the Droid4, lots of that work can simply be reused on the Pinephone, and we plan to do so in the near future. A package called <tt class="docutils literal"><span class="pre">pinephone-modem-config</span></tt> can be installed, and along with updating the kernel (latest available version is 5.6), it will bring in modem support. This is already automatically enabled in the latest images. A note to keep in mind: While the modem is off, combined with the latest kernels, the system outputs KEY_WAKEUP events which cause some trouble with the virtual keyboard. The current solution to this is to just have <tt class="docutils literal"><span class="pre">pinephone-modem-config</span></tt> installed and after a reboot, things should be ok. We will see if it's possible to patch this in some proper way in the future.</p> </div> </div> <div class="section" id="weekly-builds"> <h2>Weekly builds</h2> <p>From July, we will also implement and enable weekly image builds on our CI infrastructure. This means we won't be building images on demand anymore. Instead they shall be built each week, containing all the latest packages and goodies. Obviously, this will require more storage space, so we will be removing device images older than five weeks.</p> <p>Hopefully this will also help us polish up our build frameworks and alert us about possible bugs that arise during development. It is also a very important step towards reproducible builds - which is one of our milestones we wish to fulfill.</p> <p>However, for this occasion, we built new images and they can be downloaded as usual. This time we've also built 64bit images for the Raspberry Pi 3 and 4.</p> <ul class="simple"> <li>64bit VM: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200622/">https://maedevu.maemo.org/images/virtual-machines/20200622/</a></li> <li>N900: <a class="reference external" href="https://maedevu.maemo.org/images/n900/20200623/">https://maedevu.maemo.org/images/n900/20200623/</a></li> <li>Droid4: <a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200624/">https://maedevu.maemo.org/images/droid4/20200624/</a></li> <li>Pinephone: <a class="reference external" href="https://maedevu.maemo.org/images/pinephone/20200624/">https://maedevu.maemo.org/images/pinephone/20200624/</a></li> <li>Pinetab: <a class="reference external" href="https://maedevu.maemo.org/images/pinetab/20200624/">https://maedevu.maemo.org/images/pinetab/20200624/</a></li> <li>Pi3: <a class="reference external" href="https://maedevu.maemo.org/images/raspi3-64bit/20200623/">https://maedevu.maemo.org/images/raspi3-64bit/20200623/</a></li> <li>Pi4: <a class="reference external" href="https://maedevu.maemo.org/images/raspi4-64bit/20200623/">https://maedevu.maemo.org/images/raspi4-64bit/20200623/</a></li> </ul> </div> <div class="section" id="community-showcase"> <h2>Community showcase</h2> <div class="section" id="ps-1-emulator"> <h3>PS 1 emulator</h3> <p>PCSX-ReARMed runs quite nicely on the Droid 4:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/BmIAQby4ccM" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>Unfortunately, the community hasn't yet packaged the program for Maemo Leste Extras, but we're confident someone will, at some point.</p> </div> <div class="section" id="photo-light-meter"> <h3>Photo Light meter</h3> <p>Written in Free Pascal, photolightmeter can be used calculate aperture and shutter values.</p> </div> <div class="section" id="telegram"> <h3>Telegram</h3> <p>If you're a fan of Telegram, the desktop client just works on Maemo Leste:</p> <ul class="simple"> <li><a class="reference external" href="https://twitter.com/rfc1087/status/1271796014903635969">https://twitter.com/rfc1087/status/1271796014903635969</a></li> </ul> </div> <div class="section" id="proxmark3"> <h3>Proxmark3</h3> <p>If you like toying with RFID cards, then you can (for example) use the bluetooth module on the Droid 4 to connect a capable reader and run proxmark3 on the Droid itself:</p> <img alt="" src="/images/proxmark3-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/proxmark3-2.png" style="width: 576px; height: 324px;" /> <p>You can find specific installation notes here: <a class="reference external" href="http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276">http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276</a></p> </div> <div class="section" id="quicknote"> <h3>Quicknote</h3> <p>A simple notes application written in Python is also available: <a class="reference external" href="https://github.com/maemo-leste-extras/quicknote">https://github.com/maemo-leste-extras/quicknote</a></p> </div> <div class="section" id="mihphoto"> <h3>mihphoto</h3> <p>A Qt 5 photo viewer is available, and optionally supports multitouch when supplied as a startup argument: <a class="reference external" href="https://github.com/maemo-leste-extras/mihphoto">https://github.com/maemo-leste-extras/mihphoto</a></p> </div> <div class="section" id="personal-ip-address"> <h3>personal-ip-address</h3> <p>The good old personal-ip-address has returned, this time to Leste: <a class="reference external" href="https://github.com/maemo-leste-extras/personal-ip-address">https://github.com/maemo-leste-extras/personal-ip-address</a></p> </div> </div> <div class="section" id="maemo-leste-extras"> <h2>Maemo Leste Extras</h2> <p>More community packages are being maintained in the <tt class="docutils literal">extras</tt> repository and we're very glad and excited about it. If you're interested in maintaing your own community package for Maemo Leste, there are instructions for you to do so on the <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">bugtracker</a> .</p> </div> <div class="section" id="next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5"> <h2>Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5</h2> <p>So what can you expect from future updates?</p> <p>The big things on our radar are still:</p> <ul> <li><p class="first">Audio: Currently most devices do not even ship with <tt class="docutils literal">pulseaudio</tt>, but we'll probably want to start using it, and create ALSA UCM files for our soundcards, provide proper pulseaudio sink names for call routing, and so on. This is also a prerequisite for the <a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume">volume applet</a></p> </li> <li><p class="first">Contacts (<tt class="docutils literal"><span class="pre">osso-abook</span></tt>), this will provide all of the Hildon contacts APIs with the evolution database as a abackend, definitely required for proper SMS and Call UI</p> </li> <li><p class="first">Qt 5 updates: hopefully we will soon have the virtual keyboard integration ready, with the hildon menus and stacked windows following right after. That should be enough to make most applications work, and from there on we'll probably port things on an as-needed basis: like APIs for home and status widgets</p> </li> <li><p class="first">Nokia's <tt class="docutils literal">rtcom</tt> packages and telepathy. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390">https://github.com/maemo-leste/bugtracker/issues/390</a> Some of this is covered in <a class="reference internal" href="#steps-towards-calls-and-texts">Steps towards calls and texts</a>, but to reiterate: the plan is to use <cite>telepathy-ring</cite> as an interface to <cite>ofono</cite>, and use <cite>rtcom-eventlogger</cite> and other libraries to read from and log to the same database format as used on Fremantle. This approach is particularly exciting because it allows loading many other telepathy plugins. There also exists a <a class="reference external" href="https://github.com/dylex/slack-libpurple/commits/master">telepathy-haze</a> plugin to load (any) Pidgin (<tt class="docutils literal">libpurple</tt>) plugin, allowing for potentially loading (for example) the <a class="reference external" href="https://github.com/dylex/slack-libpurple">slack-libpurple</a> slack plugin into telepathy, and being able to directly interface with Slack using the native hildon UI, potentially even with contacts, too. And of course, there are also SIP plugins for telepathy, allowing for VOIP calls from the same (native) UI</p> </li> <li><p class="first">Speaking of UIs, once the backend (rtcom) is mostly there, the last thing we'll have to do is to bring up the call and text UIs. The Fremantle SMS UI relied on an html rendering engine, <a class="reference external" href="https://wiki.maemo.org/Conversation_Mods">allowing for cool customisations</a> like these:</p> <img alt="" src="/images/fun-conversations-mod.png" style="width: 432px; height: 256px;" /> </li> </ul> </div> <div class="section" id="web-interface-for-packages"> <h2>Web interface for packages</h2> <p>We're considering creating a web interface to browse the core maemo packages, the development packages and also the extras packages. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/395">issue #395</a> for more details. If you have suggestions, want to see specific features, or want to help out, please do let us know on the issue.</p> <p>Sneak peak of an alpha version of the interface:</p> <img alt="" src="/images/pkg.png" /> </div> <div class="section" id="more-frequent-updates"> <h2>More frequent updates?</h2> <p>We often get the question if we can provide update posts more frequently. Often, we delay update posts because we want to <strong>complete just one more package...</strong> - and then another, and another... So if you'd like to get more frequent update posts, please volunteer to write them for us. If you hang out in the IRC channel, maybe follow the frequent updates and write about them, and we'll be able to post it here, on our website.</p> <p>That said, we're considering doing detailed write-ups of various core components of Maemo Leste every few weeks or so, so if that's your thing, you might be able to peek at those too, soon.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you have questions, are interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">bugtracker</a></p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2020-03-25T19:00:00+01:002020-03-25T19:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2020-03-25:/maemo-leste-twelfth-update-february-and-march-2020.html

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-eleventh-update-january-2020.html">pre-FOSDEM 2020 update</a>, and let's start with a few highlights:</p> <ul class="simple"> <li>We've been around for two years now!</li> <li>We switched from Devuan <strong>ascii</strong> (Debian stretch) to Devuan <strong>beowulf</strong> (Debian buster)</li> <li><a class="reference internal" href="#motorola-droid-4">Motorola Droid 4</a> images are available, with <strong>3D acceleration and decent to good power management …</strong></li></ul>

<p>It's been several weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-eleventh-update-january-2020.html">pre-FOSDEM 2020 update</a>, and let's start with a few highlights:</p> <ul class="simple"> <li>We've been around for two years now!</li> <li>We switched from Devuan <strong>ascii</strong> (Debian stretch) to Devuan <strong>beowulf</strong> (Debian buster)</li> <li><a class="reference internal" href="#motorola-droid-4">Motorola Droid 4</a> images are available, with <strong>3D acceleration and decent to good power management</strong>.</li> <li><a class="reference internal" href="#pinephone-pinetab-images">Pinephone/Pinetab images</a> are now available.</li> <li>We gave a <strong>main track talk at FOSDEM</strong>: <a class="reference external" href="https://fosdem.org/2020/schedule/event/smartphones/">https://fosdem.org/2020/schedule/event/smartphones/</a></li> <li>N900 hardware support improvements such as TV-out, beginnings of camera support</li> <li><strong>Localisation support and theming</strong> is now available from the control panel, with many languages already supported.</li> </ul> <p><strong>And if you're in a rush</strong>, at least read the <a class="reference internal" href="#summarising">summarising</a> section.</p> <div class="section" id="fosdem-2020"> <h2>FOSDEM 2020</h2> <p>We gave a main-track talk at FOSDEM 2020, you can read the summary on the FOSDEM website, or through the Maemo Leste FOSDEM application:</p> <img alt="" src="/images/droid4-sojourner-fosdem.png" style="width: 576px; height: 324px;" /> <p><a class="reference external" href="https://fosdem.org/2020/schedule/event/smartphones/">The video is available here</a>.</p> </div> <div class="section" id="reminder-that-our-repositories-changed"> <h2>Reminder that our repositories changed</h2> <p><a class="reference external" href="https://maemo-leste.github.io/maemo-leste-repositories-and-community-packages.html">Please see the previous announcement</a>.</p> </div> <div class="section" id="base-os-upgraded-to-devuan-beowulf-debian-buster"> <h2>Base OS upgraded to Devuan Beowulf (Debian Buster)</h2> <p>All of our core packages (way more than 100) are now ported to work on the latest Debian &amp; Devuan stable. The <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/299">entire list is documented in issue #299</a></p> <p>This was a multi-month effort involving everyone in the core team, and it marks a big step forward!</p> <p>A few packages remain to be ported from ascii (oldstable) to beowulf, but those were not in use yet on ascii either.</p> <p>The recommended way to upgrade is to download the latest image for your device, and install the new image. Otherwise, if you're feeling adventurous, you can try to use change <cite>/etc/apt/sources.list</cite>, change <cite>ascii</cite> to <cite>beowulf</cite>, and run <cite>apt update &amp;&amp; apt dist-upgrade</cite>.</p> <div class="section" id="maemo-leste-extras"> <h3>Maemo Leste Extras</h3> <p>Not all extras packages have been ported yet (this is not an exhaustive list): <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker/issues/4">https://github.com/maemo-leste-extras/bugtracker/issues/4</a></p> <p>If you're interested in helping out in porting existing packages, or even maintaining your own packages for Maemo Leste, be sure to check out the README in the <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">ticket tracking repository for Maemo Leste Extras!</a></p> </div> </div> <div class="section" id="device-support"> <h2>Device support</h2> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>Wiki page: <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_4">https://leste.maemo.org/Motorola_Droid_4</a></p> <div class="section" id="powervr-3d"> <h4>PowerVR 3D</h4> <p>Maemo Leste now runs on the Motorola Droid 4 with 3D acceleration. And not just 3D acceleration, a lot more hardware support has improved. The end result, quite frankly, is stunning: Maemo Leste runs fast and buttersmooth. The Motorola Droid 4 truly feels like an upgrade to the Nokia N900 now. This has been a multi-year multi-man effort, and it's great to see it pay off.</p> <p>Here's a video that was made a week ago or so, some of the rendering artifacts are no longer present:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/XCnErJnkWQM" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div> <div class="section" id="wireless"> <h4>Wireless</h4> <p>Additionally, we've mostly fixed the wireless stability issues (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/296">see #296</a>). Apparently, the wireless firmware and bluetooth firmware need to be loaded in a specific order, and there currently is no way to do this properly in mainline Linux, so we've resorted to blacklisting the bluetooth module for now.</p> </div> <div class="section" id="power-management"> <h4>Power management</h4> <p>Power management is looking very promising (<cite>0.01A</cite> or less at <cite>4.4V</cite> when idle). The package <cite>droid4-powermanagement</cite> (<a class="reference external" href="https://github.com/maemo-leste/droid4-pm">https://github.com/maemo-leste/droid4-pm</a>) is now available on the latest image, and it should significantly improve battery life. Some work on MCE is pending, but once that is merged, users will be able to enjoy better power management (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/338">#338</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/340">#340</a>).</p> <p>I would not be surprised if we can manage several days of battery time in the next month or two.</p> </div> <div class="section" id="battery-calibration"> <h4>Battery calibration</h4> <p>Battery calibration is still being worked on, and a percentage will only be shown once the battery has (almost fully) discharged and charged, and does not persist across reboots. This is being worked on.</p> </div> <div class="section" id="audio"> <h4>Audio</h4> <p>Audio should work out of the box. You will find that the speaker and headphones are muted, but the wiki will contain instructions on setting up the audio mixers.</p> </div> <div class="section" id="modem-and-calls"> <h4>Modem and calls</h4> <p>The Motorola Droid 4 image is capable of performing calls, but they do not work via ofono yet. Pavel has been working on an ofono port for the Droid 4, and hopefully others will help him out soon and complete the initial port. Having ofono support in place will make the Droid 4 the ultimate developer device.</p> <p>Shortly from now, we hope to have instructions on how to perform a test phone call on the wiki.</p> </div> <div class="section" id="custom-bootup-logo"> <h4>Custom bootup logo</h4> <p>You can replace the Motorola logo on boot with a sweet Maemo Leste logo:</p> <img alt="" src="/images/Droid4_leste_logo.jpg" style="width: 525px; height: 390px;" /> <p>Instructions can be found here: <a class="reference external" href="https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO">https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO</a></p> </div> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>Wiki page: <a class="reference external" href="https://leste.maemo.org/Nokia_N900">https://leste.maemo.org/Nokia_N900</a></p> <p>The Nokia N900 has also seen some power management love, and we've been able to reach deep idle states, which we also shared on twitter <a class="reference external" href="https://twitter.com/maemoleste/status/1226265997981646849">https://twitter.com/maemoleste/status/1226265997981646849</a> -- however, this work is not yet usable in the latest image.</p> <div class="section" id="tv-out"> <h4>TV out</h4> <p>What is usable, is using the Nokia's composite out functionality, which is kinda neat:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/RNEJYYQyftI" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>Enabling it can be done like this:</p> <pre class="literal-block"> 02:57 &lt; Wizzup&gt; Had to change Jack Function in alsamixer to TV OUT, and use xrandr: xrandr --output TV --mode 800x480 --same-as LCD xrandr --output TV --set SignalProperties PAL xrandr --output TV --set TVScale 100 </pre> </div> <div class="section" id="camera-support"> <h4>Camera support</h4> <p>You read that right -- Pavel posted instructions on how to use the N900 camera and take photos with it. Some work remains before we'll have a stock application where taking photos just works, but it's great news. If you wanted to start hacking on it, the instructions were shared on the mailing list, and you can see the archive here:</p> <blockquote> <a class="reference external" href="https://lists.dyne.org/lurker/message/20200306.084252.32b5515a.en.html">https://lists.dyne.org/lurker/message/20200306.084252.32b5515a.en.html</a></blockquote> </div> <div class="section" id="sw-machine-cover"> <h4>SW_MACHINE_COVER</h4> <p>The Nokia N900 has a sensor for the backcover, and when it's removed, current mainline Linux will refuse to recognize the MicroSD card, as it uses this sensor to detect the card. Hopefully this will be changed in the future, and the backcover will be exposed as an input device, with the key <cite>SW_MACHINE_COVER</cite>:</p> <blockquote> <a class="reference external" href="https://marc.info/?l=linux-omap&amp;m=158168528609413&amp;w=2">https://marc.info/?l=linux-omap&amp;m=158168528609413&amp;w=2</a></blockquote> </div> </div> <div class="section" id="pinephone-pinetab-let"> <h3>Pinephone &amp; Pinetab(let)</h3> <p>Wiki page: <a class="reference external" href="https://leste.maemo.org/PinePhone">https://leste.maemo.org/PinePhone</a></p> <p>We've also uploaded a Pinephone image! We uploaded one before, which we didn't quite intend to share with the public yet, but Pine64 already shared our ascii Pinephone image on Twitter a while back:</p> <blockquote> <a class="reference external" href="https://twitter.com/thepine64/status/1231702499305893891">https://twitter.com/thepine64/status/1231702499305893891</a></blockquote> <p>Well, the beowulf image is here, and it's even better.</p> <div class="section" id="for-developers"> <h4>For developers</h4> <p>Still, keep in mind that these are images for developers. Some things definitely do not work yet, and the lack of a hardware keyboard makes using some parts of UI a bit of a challenge, at least the places where the virtual keyboard is not yet available.</p> </div> <div class="section" id="keyboard-monitoring"> <h4>Keyboard monitoring</h4> <p>The upcoming <a class="reference external" href="https://www.pine64.org/pinetab/">Pine64 tablet</a> has a removable keyboard, and the Maemo virtual keyboard should only show up when the keyboard is not attached to the tablet. Previously, removing the keyboard from the tablet caused MCE to crash, <a class="reference external" href="https://github.com/maemo-leste/mce/commit/0bec2e390e42f49bdbf01976a3b17609ddfd1483">but this has now been fixed</a>, and together with the <a class="reference external" href="https://github.com/maemo-leste/ke-recv-extra/pull/3">keyboard attached monitoring</a>, the Pinetab is in a much better shape.</p> </div> </div> </div> <div class="section" id="software-additions"> <h2>Software additions</h2> <div class="section" id="hildon-desktop-improvements"> <h3>hildon-desktop improvements</h3> <p>We have now switched hildon-desktop on all our devices to clutter 0.8, as opposed to clutter 1.2. The reason is poor performance, in particular on PowerVR devices (but likely also on other devices), and the unwillingness of the clutter 1.2 maintainer to fix it. We package clutter 0.8, but downstream distributions will likely have to go through a bit of pain to get our latest and fastest bits packaged (sorry!).</p> </div> <div class="section" id="theme-switching-control-panel-applet"> <h3>Theme switching control panel applet</h3> <p>For a long time, changing the default theme was not well documented, because Maemo Fremantle had a control panel applet for it, and <a class="reference external" href="https://github.com/maemo-leste/hildon-control-panel-personalisation">now we do too</a>, which fixes <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/306">issue #306</a>.</p> <p>Try it out for yourself!</p> </div> <div class="section" id="themes-available-in-the-extras-repository"> <h3>Themes available in the extras repository</h3> <p>We've imported our first community made theme from Maemo.org, <a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-marina/">hildon-theme-marina</a>. To achieve this, we also had to import <a class="reference external" href="https://github.com/maemo-leste/hildon-theme-layout">hildon-theme-layout</a> and <a class="reference external" href="https://github.com/maemo-leste/hildon-theme-tools/">hildon-theme-tools</a> (and fix it up in the process).</p> <p>Relevant bug report: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/336">#336</a></p> </div> <div class="section" id="language-and-region-switching-control-panel-applet"> <h3>Language and region switching control panel applet</h3> <p>Maemo Fremantle supported many languages, and since we implement the same base, the translations can be reused. There is now an application to switch between languages (source: <a class="reference external" href="https://github.com/maemo-leste/osso-applet-languageregional">https://github.com/maemo-leste/osso-applet-languageregional</a>), this was covered in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/304">issue #304</a></p> <p>This is what the language applet looks like:</p> <img alt="" src="/images/droid4-language-applet-english.png" style="width: 576px; height: 324px;" /> <p>Here, the language is set to English and still makes sense:</p> <img alt="" src="/images/droid4-cp-english.png" style="width: 576px; height: 324px;" /> <p>After changing the language to Dutch, and confirming that the device will indeed reboot, this is what the control panel looks like now:</p> <img alt="" src="/images/droid4-cp-dutch.png" style="width: 576px; height: 324px;" /> <p>Confusing, right?</p> <img alt="" src="/images/droid4-status-dutch.png" style="width: 576px; height: 324px;" /> <p>Additionally, language names now resolve in the hildon input method control panel.</p> </div> <div class="section" id="attached-keyboard-slider-monitoring"> <h3>Attached keyboard slider monitoring</h3> <p>Maemo Leste now keeps track of the slide state of a keyboard, and the virtual keyboard will act accordingly. If the keyboard slide is opened, the virtual keyboard will not show up by default, but if the keyboard slide is closed, and the virtual keyboard is enabled, it will work as expected.</p> <p>Relevant pull requests:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/ke-recv/pull/2">https://github.com/maemo-leste/ke-recv/pull/2</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/ke-recv-extra/pull/3">https://github.com/maemo-leste/ke-recv-extra/pull/3</a></li> </ul> </div> <div class="section" id="modem-cellular-updates"> <h3>Modem/cellular updates</h3> <p>The &quot;connui&quot; userspace to interface with the modem is still being worked on, but more progress was made recently. The PIN entry dialog now works, on start, like one would expect it to:</p> <img alt="" src="/images/pinentry-n900.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/pinentry-n900-2.png" style="width: 576px; height: 324px;" /> <p>Once the PIN is filled in (or skipped), the homescreen shows the operator name and the RAT (radio access technology) that is currently in use:</p> <img alt="" src="/images/homescreen-cellular-n900.png" style="width: 576px; height: 324px;" /> <p>This work is only available in the development repositories, as it's not stable enough to be used on a day to be day basis without being aware of all the bugs. Yours truly is working hard to get this piece finished.</p> <p>The package <cite>libicd-network-ofono</cite> is also still being worked, in particular, IP assignment for the data connections is not yet implemented. Once this works, it'll likely be possible to have data connections working on devices that have ofono support for their modem.</p> </div> <div class="section" id="desktop-widgets-calendar-support"> <h3>Desktop widgets &amp; calendar support</h3> <p>Previously, desktop widgets would crash hildon-home (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/326">#326</a>), this has now been fixed. Sicelo has made some progress getting the calendar backend and widgets to run, but more work remains to be done, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/203">#203</a>.</p> </div> </div> <div class="section" id="devices-hardware"> <h2>Devices / Hardware</h2> <div class="section" id="virtual-machine-images"> <h3>Virtual Machine images</h3> <p>New Virtual Machine images are available for download:</p> <ul class="simple"> <li><a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200324/">https://maedevu.maemo.org/images/virtual-machines/20200324/</a></li> </ul> <p>We build qcow2 images usually used with QEMU, VirtualBox VDI images, and Vagrant images.</p> <p>Currently, the mouse cursor might not be visible, we're working on resolving this problem.</p> <p><a class="reference external" href="https://leste.maemo.org/Virtual_Machine">https://leste.maemo.org/Virtual_Machine</a></p> </div> <div class="section" id="nokia-n900-images"> <h3>Nokia N900 images</h3> <p>New images are available for download:</p> <ul class="simple"> <li><a class="reference external" href="https://maedevu.maemo.org/images/n900/20200323/">https://maedevu.maemo.org/images/n900/20200323/</a></li> </ul> </div> <div class="section" id="motorola-droid-4-images"> <h3>Motorola Droid 4 images</h3> <p>New images are available for download: <a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200323/">https://maedevu.maemo.org/images/droid4/20200323/</a></p> </div> <div class="section" id="pinephone-pinetab-images"> <h3>Pinephone/Pinetab images</h3> <p>New images are available for download:</p> <ul class="simple"> <li><a class="reference external" href="https://maedevu.maemo.org/images/pinephone/20200323/">https://maedevu.maemo.org/images/pinephone/20200323/</a></li> <li><a class="reference external" href="https://maedevu.maemo.org/images/pinetab/20200324/">https://maedevu.maemo.org/images/pinetab/20200324/</a></li> </ul> <p>These images are very usable, and have 3D acceleration with the open source Lima drivers. There is still some jittery performance, but hopefully it will be fixed with time as we go forward and the mesa driver gets improved.</p> </div> </div> <div class="section" id="summarising"> <h2>Summarising</h2> <p><a class="reference external" href="https://maemo-leste.github.io/maemo-leste-standing-on-the-shoulders-of-giants.html">It has been two years since our very first news post</a>, and we've come a long way.</p> <p>With 3D support now looking quite decent on the Droid 4, we now have a device that is easily obtainable, has great mainline support, very decent power management, and is able to make calls right now. By focussing on supporting the Nokia N900, Droid 4 and the Pinephone, and developing software with these devices in mind, we can expect to be able to perform phone calls in the next few months, if not weeks. It will take time for our userspace software to mature, but things are looking really bright for Maemo Leste.</p> <p>I think we're putting together a great versatile mobile Linux distribution, with its own userspace, based on top of Debian, the universal operation system. It really is just Devuan/Debian at the core, and everything happens through the Debian package manager. There are no read-only images, specific partitions that you must have to install a new over the air update -- updates just work with <cite>apt upgrade</cite>.</p> <p>You will see that you can update from <cite>ascii</cite> to <cite>beowulf</cite> with <cite>dist-upgrade</cite>, and at the end of the upgrade, you will <strong>still</strong> have a functional <cite>ascii</cite> system. And when you reboot - you will have the new <cite>beowulf</cite> (buster) version. We think that's powerful.</p> <p>Additionally, some (old and new) members from the community have started contributed their packages to our <a class="reference external" href="https://github.com/maemo-leste-extras">&quot;Extras&quot; repository</a>. Make sure to check that out too, or even better: port and contribute packages that you would love to see!</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2020-02-25T19:20:00+01:002020-02-25T19:20:00+01:00Ivan Jelincictag:maemo-leste.github.io,2020-02-25:/maemo-leste-repositories-and-community-packages.html

<p>In-between our technical updates, we have another short update on our repository organization.</p> <p>After the proposition and discussion we've had on our IRC channel and our <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/320">bugtracker</a>, we've reorganized our repositories into a nicer and cleaner structure.</p> <p>In short, we now have a single pool containing all the packages and …</p>

<p>In-between our technical updates, we have another short update on our repository organization.</p> <p>After the proposition and discussion we've had on our IRC channel and our <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/320">bugtracker</a>, we've reorganized our repositories into a nicer and cleaner structure.</p> <p>In short, we now have a single pool containing all the packages and their different versions, for all the different dists that we support. This is mainly a nice way to keep a simpler repository structure, but also helpful when building <tt class="docutils literal">devel</tt> packages, so their versions can be automatically incremented in a correct manner. Last, but not least, it allows us to easily support more than one <tt class="docutils literal">dist</tt>, so we will eventually be able to support both Devuan and Debian at the same time.</p> <p>Due to this, the repository entries in <tt class="docutils literal">/etc/apt/sources.list</tt> require a small change - instead of the <tt class="docutils literal">deb</tt> entries we've had:</p> <pre class="literal-block"> deb http://maedevu.maemo.org/leste leste main deb http://maedevu.maemo.org/leste-extras leste-extras main </pre> <p>We now have</p> <pre class="literal-block"> deb http://maedevu.maemo.org/leste ascii main deb http://maedevu.maemo.org/extras ascii main </pre> <p>With this, there is less ambiguity and it is easier for both users and developers to figure out which Devuan version Leste is currently based on, and will also allow easier upgrading when Maemo Leste rebases to a newer Devuan version.</p> <p>So, to switch your existing Maemo Leste installations, just use the latter two links in <tt class="docutils literal">/etc/apt/sources.list</tt>. Simple!</p> <p>As for the images containing these changes, we are working on finalizing them and they'll be ready for our next blog update.</p> <div class="section" id="community-packages"> <h2>Community packages</h2> <p>We're close to finalizing our community infrastructure, and we'd love to invite you to maintain community packages for Maemo Leste. Like Fremantle, we call them Extras, and they reside in a separate <a class="reference external" href="https://github.com/maemo-leste-extras/">organization</a>.</p> <p>If you would like to maintain a community package, have a look at the bugtracker in Maemo Leste Extras and follow the <a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker">README</a>. We invite everyone to try out the procedure and provide feedback!</p> <p>See you there :)</p> </div> 2020-01-13T01:00:00+01:002020-01-13T01:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2020-01-13:/maemo-leste-eleventh-update-january-2020.html

<p>It's been a few weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-tenth-update-december-2019.html">end of 2019 update</a>, and let's start with a few highlights:</p> <ul class="simple"> <li>We have a main track talk in the FOSDEM 2020 <a class="reference external" href="https://fosdem.org/2020/schedule/event/smartphones/">Freedom Track</a> - make sure to meet us there if you're attending FOSDEM.</li> <li>New <a class="reference internal" href="#virtual-machine">Virtual Machine</a> images are available: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200103/">https://maedevu.maemo.org …</a></li></ul>

<p>It's been a few weeks since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-tenth-update-december-2019.html">end of 2019 update</a>, and let's start with a few highlights:</p> <ul class="simple"> <li>We have a main track talk in the FOSDEM 2020 <a class="reference external" href="https://fosdem.org/2020/schedule/event/smartphones/">Freedom Track</a> - make sure to meet us there if you're attending FOSDEM.</li> <li>New <a class="reference internal" href="#virtual-machine">Virtual Machine</a> images are available: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200103/">https://maedevu.maemo.org/images/virtual-machines/20200103/</a></li> <li>New <a class="reference internal" href="#nokia-n900">Nokia N900</a> images are available: <a class="reference external" href="https://maedevu.maemo.org/images/n900/20200112/">https://maedevu.maemo.org/images/n900/20200112/</a></li> <li>New <a class="reference internal" href="#motorola-droid-4">Motorola Droid 4</a> images are available: <a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200112/">https://maedevu.maemo.org/images/droid4/20200112/</a></li> <li>Leste <strong>Extras</strong> repository is now set up and usable.</li> <li>An overview of various (important) development tasks is tracked on the wiki: <a class="reference external" href="https://leste.maemo.org/Development/Tasks">https://leste.maemo.org/Development/Tasks</a></li> </ul> <p><em>There will be a separate post for the Pinephone in the next few days, along with images for the Pinephone.</em></p> <div class="section" id="software-additions"> <h2>Software additions</h2> <p>There have been many additions, bugfixes and improvements, perhaps best illustrated by this screenshot of a developer's Nokia N900 running Maemo Leste:</p> <img alt="" src="/images/leste-swstate.png" style="width: 576px; height: 324px;" /> <p>The above screenshot shows the availability of python bindings (binary clock), importing Fremantle themes, the progress of connui-cellular (status bar with 3G logo, signal bar, operator name 'KPN' on the home screen), and homescreen shortcuts of applications that have been ported, including a package manager and PDF reader.</p> <div class="section" id="leste-extras-software-repository"> <h3>Leste &quot;Extras&quot; software repository</h3> <p>We now have a separate repository called <cite>leste-extras</cite> for non-core packages, similar to the &quot;Maemo Extras&quot; repository - <a class="reference external" href="http://maemo.org/downloads/updated/Maemo5/">http://maemo.org/downloads/updated/Maemo5/</a></p> <p>Currently <cite>leste-extras</cite> contains a few games, emulators and status widgets. Eventually, it will be home to status widgets, home widgets, different browsers, map applications, games, and more.</p> <p><a class="reference external" href="https://github.com/maemo-leste-extras">https://github.com/maemo-leste-extras</a></p> <p>Keep in mind that in addition to the packages available in this repository, every package available in Debian can be installed using <cite>apt-get install</cite> - usability will vary.</p> <div class="section" id="wishlist"> <h4>Wishlist</h4> <p>If there is a specific application you would like to see (ported), the wiki now contains an <a class="reference external" href="https://leste.maemo.org/Wishlist">Application Wishlist</a>. Feel free to add suggestions to the table.</p> </div> <div class="section" id="porting"> <h4>Porting</h4> <p>Porting applications from Maemo Fremantle (&quot;Maemo 5&quot;) is usually not very hard, and sometimes particularly simple, as outlined in this <a class="reference external" href="https://talk.maemo.org/showpost.php?p=1563848&amp;postcount=18">talk.maemo.org forum post</a>. In general, if an application depends on libraries that are mostly available in Debian, and uses gtk2, it should be not very hard to port. If it relies on Qt, it is not yet possible to properly port it, as we do not have a usable Qt5 Hildon port yet. A <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/261">gtk3 port is in the works</a> -but help is needed.</p> <p>One application that was ported recently is the <a class="reference internal" href="#pdf-reader">PDF Reader</a>.</p> </div> </div> <div class="section" id="python-support"> <h3>Python support</h3> <p><a class="reference external" href="http://wiki.maemo.org/PyMaemo">Maemo had pretty decent Python bindings and documentation for them</a> -- and they were only available for Python 2.5, which is beyond ancient. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/260">Issue #260</a> was created to modernise and port some of the python bindings to Maemo Leste, allowing us to run port and build (new) python applications.</p> <p>As of a few weeks, <a class="reference external" href="https://github.com/maemo-leste/pygtk">pygtk</a> is available with hildon widget support, <a class="reference external" href="https://github.com/maemo-leste/python-hildon">python-hildon</a>, <a class="reference external" href="https://github.com/maemo-leste/python-hildondesktop">python-hildondesktop</a> and <a class="reference external" href="https://github.com/maemo-leste/python-osso">python-osso</a> are all available as well. These are the main bindings to the Maemo mobile environment. They have all been ported to Python 2.7. Python 2.7 is now end of life, so we'll have to migrate to 3.x eventually, but 2.7 seemed like a good and useful intermediate goal.</p> <p>And, surely enough, python applications like the binary clock applet now run:</p> <img alt="" src="/images/python-maemo-binaryclock.png" style="width: 576px; height: 324px;" /> <p>Here one can see a home widget example:</p> <img alt="" src="/images/python-hildon-homewidget.png" style="width: 576px; height: 324px;" /> <p>And a status bar example:</p> <img alt="" src="/images/python-hildon-statuswidget.png" style="width: 576px; height: 324px;" /> <p>Hildon-type stacked windows in Python:</p> <img alt="" src="/images/python-hildon-stack.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/python-hildon-stack-sub.png" style="width: 576px; height: 324px;" /> <p>Hildon-type wizards:</p> <img alt="" src="/images/python-hildon-wizard1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/python-hildon-wizard2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/python-hildon-wizard3.png" style="width: 576px; height: 324px;" /> <p>Hildon menus:</p> <img alt="" src="/images/python-hildon-menu1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/python-hildon-menu2.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="pdf-reader"> <h3>PDF reader</h3> <p>Maemo 5 features a PDF reader, and it has now been ported to Maemo Leste, <a class="reference external" href="https://github.com/maemo-leste/osso-pdf-viewer/commits/master">the osso-pdf-viewer source can be found here</a>. Porting was slightly more involved than we hoped, but all in all it was maybe half a day of work. Porting did reveal that there is a bug in the underlying maemo file manager libraries, making it impossible for users to select a file to open if the enviroment variable <cite>MYDOCSDIR</cite> is set, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/280">#280</a>. This bug also effects the SNES emulator drnoksnes, so we'll hopefully get it resolved soon.</p> <p>Even though it's currently hard to open PDFs, the application is available in the core Maemo Leste repository now, and part of the new images.</p> <img alt="" src="/images/leste-pdf-n900-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-pdf-n900-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-pdf-n900-3.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-pdf-n900-4.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="hildon-application-manager"> <h3>Hildon Application Manager</h3> <p>Another core component of Maemo is &quot;HAM&quot;, also known as the &quot;Hildon Application Manager&quot;. It's an user interface to the Debian package manager, <cite>apt</cite>, which allows users to discover, install and uninstall packages, and it also notifies the user when updates are available, and if the user agrees, updates the system. You can adjust the frequency of update checks.</p> <p>This was a relatively quick port, and there are likely bugs, so there is more work to be done. Nevertheless, it works.</p> <p>This screenshot shows the device informing the user there are (important) updates to be installed (<strong>Yellow &quot;!&quot; icon</strong>).</p> <img alt="" src="/images/leste-update-notification-via-alarmd-and-status-applet.png" style="width: 576px; height: 324px;" /> <p>Clicking on the updates button in the status menu will show the following sequence of dialogs:</p> <img alt="" src="/images/leste-n900-ham-updates.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-3.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-4.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-5.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-6.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-7.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/leste-n900-ham-updates-8.png" style="width: 576px; height: 324px;" /> <p>As of today, the Hildon Application Manager will also automatically add and enable our <a class="reference internal" href="#leste-extras-software-repository">Leste &quot;Extras&quot; software repository</a>.</p> </div> <div class="section" id="portrait-mode"> <h3>Portrait mode</h3> <p>For a long time, our hildon-desktop environment completely did not work in so called &quot;Portrait&quot; mode -- where the screen is higher than it is wide. This is very common now in smart phones. As a result, many devices have &quot;Portrait&quot; as the native orientation of the display. The Droid 4 and Pinephone are no exception.</p> <p>Maemo Leste still doesn't work very well yet in Portrait mode (although the original Maemo Fremantle does mostly work really well in Portrait mode). There were some real show stopping bugs, in particular <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/214">#214</a>, which resulted in the entire desktop been drawn offscreen. Some bugs still remain, like <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/283">#283</a> and these affect the Pinephone in a negative way.</p> <p>Nevertheless, here's a photo of a Motorola Droid 4 in Portrait mode:</p> <img alt="" src="/images/droid4-rot3.jpg" style="width: 324px; height: 575px;" /> </div> <div class="section" id="games"> <h3>Games</h3> <p>Various games have been ported from Fremantle, and they work really well on the Nokia N900. Most games still require some fixes to work on devices with other screen sizes and orientations.</p> <ul> <li><p class="first">brainparty:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/IlweegA2ORQ" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first">Latest ScummVM from git works on the N900:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/DHGaUI8wA7Q" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first">UAE4ALL is also in the <cite>leste-extras</cite> repository, but could see some more testing.</p> </li> </ul> <p>The marbles port is in the works, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/275">the mahjong port mostly works (#275)</a>, and the chess port compiles, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/277">but is not yet functional (#277)</a></p> <p>Related issues:</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/259">#259</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/273">#273</a></p> <p>User Angel Vega also has UAE4ALL and milkytracker running on Maemo Leste:</p> <blockquote> <iframe width="560" height="315" src="https://www.youtube.com/embed/UGcQ4NV3jO8" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></blockquote> </div> <div class="section" id="upstream"> <h3>Upstream</h3> <p>Maemo and Mer (base system for Sailfish OS and Nemo Mobile) share a lot of core packages, even though those have diverged over time. <cite>spiiroin</cite> has Maemo Leste running with various core packages replaced with their (newer!) Mer equivalents:</p> <ul class="simple"> <li><a class="reference external" href="https://git.sailfishos.org/spiiroin/mce/tree/maemo-leste-hacking">https://git.sailfishos.org/spiiroin/mce/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://git.sailfishos.org/spiiroin/dsme/tree/maemo-leste-hacking">https://git.sailfishos.org/spiiroin/dsme/tree/maemo-leste-hacking</a></li> </ul> <p>We hope to make use of this work in the (near) future and use the same base software as Mer does. The evolved versions of MCE and DSME that are used in Mer also have some features that we will need, like being able to deal with the new (well, not so new anymore) kernel vibration interface.</p> </div> <div class="section" id="connui-cellular"> <h3>connui-cellular</h3> <p>connui-cellular is the piece of software that contains a lot of widgets and libraries used in cellular activities. The home widget that displays the operator name, the program that asks you for your PIN to unlock your SIM card, the status applet that shows the strength of your cellular signal, what technology is being used to connect to the network, the Phone settings applet. And more. This piece is being ported to ofono, but it's not ready for general use yet. You might see various screenshots in this blogpost already featuring various pieces of <cite>connui-cellular</cite> - it is available in the <cite>leste-devel</cite> repository, which contains unstable or testing versions of our software.</p> <p>Hopefully in the next one or two weeks a first version will make it to the production <cite>leste</cite> repository.</p> <p>This video shows that unlocking your SIM using the pin-entry dialog now works:</p> <blockquote> <iframe width="560" height="315" src="https://www.youtube.com/embed/BpJPTc8Q_4c" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></blockquote> </div> <div class="section" id="osso-abook"> <h3>osso-abook</h3> <p>Maemo had a pretty good address book and presence (for Instant Messaging and SIP calling) system. Developer freemangordon is working on getting that in Maemo Leste as well. It's a rather big task, so it might take a while, but we will rely on this piece of software to integrate our various contact applications. Examples of this would be the <cite>modest</cite> email client, and a not-yet-existing dialer and SMS application.</p> </div> <div class="section" id="themes"> <h3>Themes</h3> <p>One of the cool things about being compatible with Maemo 5 &quot;Fremantle&quot; on various levels is that it's often really easy to cherry pick things we like.</p> <p>In this case, one can literally just download a theme from the maemo.org website and install it on Maemo Leste. For example, the <a class="reference external" href="http://maemo.org/downloads/product/Maemo5/hildon-theme-marina/">Marina Theme</a> can be installed with <cite>dpkg -i &lt;debhere&gt;</cite>. Currently, the <cite>/usr/share/themes/default</cite> symlink also needs to be updated, but after that, the themes from Maemo 5 &quot;Fremantle&quot; are fully usable on Maemo Leste.</p> <p><a class="reference external" href="http://maemo.org/downloads/search/application.html?org_openpsa_products_search%5B1%5D%5Bproperty%5D=title&amp;org_openpsa_products_search%5B1%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B1%5D%5Bvalue%5D=theme&amp;org_openpsa_products_search%5B2%5D%5Bproperty%5D=os&amp;org_openpsa_products_search%5B2%5D%5Bconstraint%5D=LIKE&amp;org_openpsa_products_search%5B2%5D%5Bvalue%5D=Maemo5&amp;fetch=Search">There are a lot of themes available too</a>, we are hoping to eventually have a default theme with a Maemo Leste logo, there was <a class="reference external" href="https://talk.maemo.org/showthread.php?t=100905">some discussion about a default Maemo Leste theme on talk.maemo.org</a></p> </div> </div> <div class="section" id="devices-hardware"> <h2>Devices / Hardware</h2> <div class="section" id="virtual-machine"> <h3>Virtual Machine</h3> <p>New Virtual Machine images are available: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200103/">https://maedevu.maemo.org/images/virtual-machines/20200103/</a></p> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p><a class="reference external" href="https://maedevu.maemo.org/images/n900/20200112/">New N900 images are available here</a>, main changes include:</p> <ol class="arabic simple"> <li>There are now udev rules in place to allow using the modem with ofono. (Just <cite>apt install ofono mdbus; mdbus2 -s org.ofono</cite> and you should see the modem)</li> <li><cite>hildon-application-manager</cite> is now installed by default, as is the <cite>osso-pdf-reader</cite> application. Users can install packages from Leste &quot;Extras&quot; directly from the <cite>hildon-application-manager</cite>.</li> <li>Specific rules in <cite>/etc/network/interfaces</cite> for <cite>usb0</cite> are removed because they confliced with <cite>ke-recv</cite>, net result is that usb networking should be more smooth now.</li> </ol> </div> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p><a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200112/">New Motorola Droid 4 images are available here</a>, main changes include:</p> <ol class="arabic simple"> <li>udev rules for the modem.</li> <li>Much newer kernel (5.4.0 based) with a ton of fixes and improvements, including modem and audio support.</li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/286">An ofono fork with rudimentary support for the Motorola Droid 4 modem (#286)</a>. It is not installed by default, but <cite>apt install ofono</cite> will get you set up with the right version. It does not yet support the <cite>SimManager</cite> interface, which <cite>connui-cellular</cite> will need. If someone wants to implement this, that would be great.</li> <li>Support for PowerVR testing and development. The current image will allow developers to build a PowerVR kernel module and test it, without having to recompile or patch the Linux kernel.</li> </ol> <div class="section" id="audio"> <h4>Audio</h4> <p>Sound works, but requires three manual steps every boot. Basically, you need to insert the modules. Inserting them at boot time will not work:</p> <pre class="literal-block"> modprobe snd-soc-cpcap modprobe snd-soc-motmdm modprobe snd-soc-audio-graph-card </pre> </div> <div class="section" id="bluetooth"> <h4>Bluetooth</h4> <p>If you like bluetooth, installing <a class="reference external" href="https://github.com/TI-ECS/bt-firmware/blob/master/TIInit_10.6.15.bts">this firmware file</a> to <cite>/lib/firmware/ti-connectivity/TIInit_10.6.15.bts</cite> will make it work after a reboot:</p> <pre class="literal-block"> # hcitool scan Scanning ... C0:38:F9:A6:29:BA Nokia N900 </pre> </div> <div class="section" id="powervr-3d-acceleration"> <h4>PowerVR / 3D acceleration</h4> <p>Detailed instructions on how to play with PowerVR using this image will follow, but you will need at least:</p> <ol class="arabic simple"> <li><a class="reference external" href="https://github.com/tmlind/pvr-omap4-dkms/blob/testing-v5.4/README_DROID4">https://github.com/tmlind/pvr-omap4-dkms/blob/testing-v5.4/README_DROID4</a></li> <li>This package: <a class="reference external" href="https://launchpad.net/ubuntu/artful/armhf/libdri2-1/1.0.0~git20120510+26fee2e-0ubuntu2">https://launchpad.net/ubuntu/artful/armhf/libdri2-1/1.0.0~git20120510+26fee2e-0ubuntu2</a></li> <li><cite>apt install xserver-xorg-video-omap</cite></li> <li>Rename <cite>/etc/X11/xorg.conf.d.pvr</cite> to <cite>/etc/X11/xorg.conf.d</cite></li> </ol> <p><strong>DOING SO WILL BREAK HILDON-DESKTOP AND MIGHT MAKE YOUR SYSTEM BOOT LOOP, SO CONTINUE AT YOUR OWN RISK</strong>.</p> </div> </div> <div class="section" id="interested"> <h3>Interested?</h3> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> </div> 2019-12-31T17:45:00+01:002019-12-31T17:45:00+01:00Merlijn Wajertag:maemo-leste.github.io,2019-12-31:/maemo-leste-tenth-update-december-2019.html

<p>It's been a few months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-ninth-update-march-till-august-2019.html">ninth update</a>, and a lot has happened on a technical front. That will all be covered in an early January update. This update will mostly be about the non-technical part of Maemo Leste.</p> <p><strong>First of all - happy new year to everyone reading this …</strong></p>

<p>It's been a few months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-ninth-update-march-till-august-2019.html">ninth update</a>, and a lot has happened on a technical front. That will all be covered in an early January update. This update will mostly be about the non-technical part of Maemo Leste.</p> <p><strong>First of all - happy new year to everyone reading this. I believe 2020 will be a very interesting and hopefully prosperous year for the project.</strong></p> <div class="section" id="openfest"> <h2>OpenFest</h2> <p>In early November, we gave a talk at OpenFest 2019. Several of the core Maemo Leste developers also met up at the event, and we also had interesting talks with the folks from <a class="reference external" href="https://tehnoetic.com/">Techno Ethical</a> - they left with a Droid 4 to run Maemo Leste on.</p> <p>The official recording of the OpenFest 2019 is not yet uploaded to youtube, but you can find a video which bundyo made, here:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/UjzEd504_jY" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div> <div class="section" id="nlnet-funding"> <h2>NLNet - funding!</h2> <p>You read that right, we applied for funding and we received it. You can read the writeup here <a class="reference external" href="https://nlnet.nl/project/MaemoLeste/">on the NLNet website</a>. We will share details in the coming weeks.</p> </div> <div class="section" id="fosdem-2020"> <h2>FOSDEM 2020</h2> <p>Maemo Leste will be present at FOSDEM in 2020 - with a talk. This time it will not be a lightning talk, but will be a talk on Sunday, for the <a class="reference external" href="https://fosdem.org/2020/schedule/track/freedom/">Freedom track</a>, in the Janson room, together with someone from postmarketOS!</p> <p>Once we finalise our talk abstract and description, the talk will show up on the FOSDEM website.</p> </div> <div class="section" id="talk-maemo-org-subforum"> <h2>talk.maemo.org subforum</h2> <p><a class="reference external" href="https://talk.maemo.org/forumdisplay.php?f=66">We now have a talk.maemo.org subforum</a>.</p> </div> <div class="section" id="some-videos-with-a-few-technical-updates"> <h2>Some videos with a few technical updates</h2> <p>Although the start of the update said there wouldn't be a lot of technical updates, here's a short summary of what to expect in the technical update next week:</p> <ul> <li><p class="first">hildon-desktop rotation bug is fixed!</p> </li> <li><p class="first">Maemo Leste runs on the PinePhone and PineTab</p> </li> <li><p class="first">hildon-application-manager is kind of working</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/t-DiJJkyYrk" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first">brainparty running on an N900 running Maemo Leste:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/IlweegA2ORQ" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first">PowerVR acceleration starts to work on the Motorola Droid 4</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/6byvcCjEazE" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first">Cellular work continues steadily</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/BpJPTc8Q_4c" ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></li> <li><p class="first"><a class="reference external" href="https://talk.maemo.org/showpost.php?p=1563667&amp;postcount=330">Python gtk and hildon support is now in place</a></p> </li> </ul> <div class="section" id="interested"> <h3>Interested?</h3> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> </div> 2019-08-24T15:00:00+02:002019-08-24T15:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2019-08-24:/maemo-leste-ninth-update-march-till-august-2019.html

<p>It's been way too long since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-eight-update-january-february-2019.html">eight update</a>. A lot of things happened and we're still making steady progress.</p> <div class="section" id="general-direction-alpha-status"> <h2>General direction &amp; Alpha status</h2> <p>The last couple of months has been dominated by work on cellular support and the upcoming PinePhone and PineTablet devices. The Pine64 project plans to start …</p></div>

<p>It's been way too long since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-eight-update-january-february-2019.html">eight update</a>. A lot of things happened and we're still making steady progress.</p> <div class="section" id="general-direction-alpha-status"> <h2>General direction &amp; Alpha status</h2> <p>The last couple of months has been dominated by work on cellular support and the upcoming PinePhone and PineTablet devices. The Pine64 project plans to start shipping the PinePhone a couple months from now, and we hope to have a usable-enough image so that the PinePhone can ship with the option of having Maemo Leste installed. This might also explain the focus on the modem/cellular work, which this article will discuss in greater detail later on.</p> <p>The <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">N900 Alpha milestone</a> status is looking quite good, with a couple of (relatively minor) changes remaining, the most prominent being <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/17">completion of the virtual keyboard package</a>, we need to add monitoring of the keyboard slide status. This should be a day of work at most. The other meaningful (non bug fix) addition will be welcome application, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/229">as pioneered by Pavel</a>.</p> <p>We've seen more and more people join the IRC channel, get a device to develop on, and slowly help porting / adding new applications, so that's exciting!</p> <!-- cellular --> <!-- 'basic os' --> <!-- qt support libs --> <!-- support multiple devices --> <!-- pinephone aims --> <!-- -> then (or: already!) port new stuff --> </div> <div class="section" id="software-additions-connectivity"> <h2>Software additions &amp; Connectivity</h2> <p>In the connectivity domain there's been a couple of things going on, connui-cellular was ready to be ported to ofono, the daemon that interfaces with the modem. Freemangordon started working on <cite>libicd-network-ofono</cite>, the <cite>icd2</cite> plugin that will allow for setting up GPRS/UMTS/LTE data connections, and Freemangordon and Wizzup have been working on porting <cite>connui-common</cite> and <cite>connui-cellular</cite> to ofono. While porting, effort is been made to support multiple modems and dual sim setups. Maemo supported neither, so it will require some architectural changes down the line.</p> <p>The tracking issue for 3G data support can be found seen here: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/76">https://github.com/maemo-leste/bugtracker/issues/76</a></p> <div class="section" id="connui-cellular"> <h3>connui-cellular</h3> <p>connui-cellular is a big package that contains a lot:</p> <ol class="arabic simple" start="0"> <li>Shared code (library) to interface with the various cellular daemons</li> <li><dl class="first docutils"> <dt>Control panel (Settings) applet to:</dt> <dd><ul class="first last"> <li>Set up call forwarding</li> <li>Set up / change what radio technologies should be used (2G, 3G, etc)</li> <li>Set up roaming options</li> <li>Change, set or reset pin code for the sim card</li> </ul> </dd> </dl> </li> <li>Hildon-home applet to show the operator name on the desktop</li> <li>Hildon status bar applet to show the signal strength, radio access technology, sim card status and more.</li> <li>Dialogs to enter pin codes for a sim card</li> <li>Roaming related dialogs.</li> </ol> <p>So this is a very important package to have (fully) working. Porting it to ofono requires replacing a ton of functions, mostly in the shared code. An effort is being made on the <a class="reference external" href="https://github.com/maemo-leste/connui-cellular/compare/ofono-port">ofono-port branch</a>.</p> <p>There are two tickets open to track this progress in (they should probably be merged):</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/195">https://github.com/maemo-leste/bugtracker/issues/195</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/256">https://github.com/maemo-leste/bugtracker/issues/256</a></li> </ul> <p>While it's still work in progress, the operator name widget and the status bar applet is already mostly functional, as can be seen on this Nokia N900, being connected to the Dutch operator <cite>KPN</cite>, over 3G.</p> <img alt="" src="/images/leste-n900-cellular-v0.1.png" style="width: 576px; height: 324px;" /> <p>Maemo did not support 4G/LTE at all, so we also added that, as can be seen in this virtual machine using a modem via usb-passthrough:</p> <img alt="" src="/images/leste-cellular-operator-name-home.png" style="width: 608px; height: 300px;" /> <p>(Thanks to <cite>sicelo</cite> for creating the logo - and before you ask, yes, we're going to switch from <cite>4G</cite> to <cite>LTE</cite> as a logo text)</p> <p>The following pages on the wiki contain some more information (although some of it may surely be outdated):</p> <ol class="arabic simple"> <li><a class="reference external" href="https://leste.maemo.org/Status/Mobile_Data">https://leste.maemo.org/Status/Mobile_Data</a></li> <li><a class="reference external" href="https://leste.maemo.org/Status/Mobile_Data/Dev">https://leste.maemo.org/Status/Mobile_Data/Dev</a></li> </ol> </div> <div class="section" id="libicd-network-ofono"> <h3>libicd-network-ofono</h3> <p>As mentioned, work has started on libicd-network-ofono, the <cite>icd2</cite> plugin that will allow setting up a data connection. Currently the plugin will find modems, and provision them. The connection will then show up in the usual connection dialog:</p> <img alt="" src="/images/leste-libicd-network-ofono-0.1.png" style="width: 576px; height: 324px;" /> <p>And if you select it, it will power up the modem, but not yet connect you to a data network:</p> <img alt="" src="/images/leste-libicd-network-ofono-0.1-2.png" style="width: 576px; height: 324px;" /> <p>There's more work to be done in this area - and help is appreciated:</p> <p><a class="reference external" href="https://github.com/maemo-leste/libicd-network-ofono">https://github.com/maemo-leste/libicd-network-ofono</a></p> </div> <div class="section" id="connui-common"> <h3>connui-common</h3> <p>connui-common contains (as the name suggests) common code shared within the connui stack. It has also seen porting to libgofono.</p> <p>Recently in an effort to migrate all our packages to the upcoming Devuan release, we upgraded the build system, but as a result, dialogs were being installed into an architecture specific path, which is the way it's supposed to be, but this resulted in certain dialog plugins not being loaded at all. Ultimately, it meant that you could no longer get any wireless connection dialog when you updated your system. The bug had apparently existed for a while, but it has now been fixed, for more details see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/251">bug #251</a>.</p> <!-- hildon application manager --> <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~ --> <!-- --> <!-- Being worked on by minicom TODO links --> </div> <div class="section" id="mode-control-entity"> <h3>mode control entity</h3> <p>For a few months, changing the brightness no longer worked from the settings applet, this was due to the fact that <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/232">there were several user dbus-daemon instances</a> running, and applications were not able to chat with each other. This has now been fixed.</p> </div> <div class="section" id="welcome-application"> <h3>welcome application</h3> <p>We'll soon have a welcome application of some sorts, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/229">as documented in issue #229</a>, to allow resizing of the rootfs, changing default passwords, and so on. And ... unlike most of the core Maemo software, this is written in Python, using pygtk.</p> </div> <div class="section" id="alarmd"> <h3>alarmd</h3> <p>Maemo has a package called <cite>alarmd</cite>, which is used to set and manage alarms. The phone can wake itself even when it's completely powered off to alarm the user. <cite>alarmd</cite> and <cite>alarmclient</cite> are already built and can be installed to Maemo Leste, and a sample alarm run will look like this:</p> <pre class="literal-block"> alarmclient -b label=Snooze,flags=TYPE_SNOOZE+WHEN_RESPONDED \ -b label=Stop,flags=WHEN_RESPONDED, \ -n title='Two Button Alarm',message='Hello there', alarm_time=5 </pre> <img alt="" src="/images/leste-alarm-client.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="audio"> <h3>Audio</h3> <p>Currently, audio mostly just works on the devices that we support (Nokia N900, Motorola Droid 4, Pinephone devkit, Allwinner tablets...). However, for a phone to be particular usable we'll need to deal with audio policies sooner or later. That is: if you plug in a headphone, you expect the output of programs to go to the headphone jack. And if you don't have a headphone jack plugged in, you expect audio to go over the speakers. Unless you're being called, in which case you probably initially want the audio to go over the earpiece. Maemo's audio policies and routing were relatively complex and involved multiple pieces of software, some which are not open source.</p> <p>That said, we do currently have opened up one of these packages, thanks to the hard work done by <cite>spinal84</cite>: <a class="reference external" href="https://github.com/spinal84/alsa-policy-enforcement">https://github.com/spinal84/alsa-policy-enforcement</a></p> </div> <div class="section" id="games"> <h3>Games</h3> <p>Maemo Fremantle has lots of fun games packaged, lots of emulators too. Now that graphics acceleration on the Nokia N900 works quite well, and acceleration on most Mali devices will work quite well, we're starting to package some of the Maemo game frameworks and games.</p> <p>Keep in mind that a lot of games are already available from the Debian repositories, and many of them will just work.</p> <p>If there's a specific game/app you'd like to see ported, feel free to add it to this list on the wiki: <a class="reference external" href="https://leste.maemo.org/Status/Games">https://leste.maemo.org/Status/Games</a></p> <p>The relevant issues are <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/18">#18</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/238">#238</a>.</p> <p>Here are some screenshots showing off the work done so far for Mahjong and Marbles:</p> <img alt="" src="/images/mahjong-start-screen.png" style="width: 400px; height: 300px;" /> <img alt="" src="/images/mahjong-score-screen.png" style="width: 400px; height: 300px;" /> <img alt="" src="/images/mahjong-game-over-screen.png" style="width: 400px; height: 300px;" /> <img alt="" src="/images/marbles-start-screen.png" style="width: 400px; height: 300px;" /> <!-- Games & Emulation --> <!-- ^^^^^^^^^^^^^^^^^ --> <!-- --> <!-- - pvr showoff --> <!-- -> prboom / freedoom1 --> <!-- -> pokemon blue --> </div> <div class="section" id="sms-calls"> <h3>SMS &amp; Calls</h3> <p>As part of the <cite>connui</cite> work, we also tried to make <a class="reference external" href="https://developer.gnome.org/platform-overview/unstable/tech-telepathy.html.en">telepathy</a> (the GNOME messaging backend/daemon) work with ofono. After installing <cite>telepathy-ring</cite>, which was already packaged in Debian (!) and adding a <cite>tel</cite> account through Empathy <a class="reference external" href="https://blogs.gnome.org/wjjt/2010/07/15/sending-smses-with-empathy-and-telepathy-ring/">per these instructions</a> , we were able to send and receive SMS texts. It was surprisingly easy. This should work on the Nokia N900, Motorola Droid 4 and Pinephone too. The UI is not particularly usable yet (it won't show you a new window if you get a text from a new/unknown number, and it uses gtk3, we need to add our gtk3 port), but it's a great start!</p> <p>One caveat is that the Debian version also trails upstream quite a bit: <a class="reference external" href="https://git.merproject.org/mer-core/telepathy-ring">https://git.merproject.org/mer-core/telepathy-ring</a> - so we'll probably have to package our own version eventually.</p> <p>This should theoretically also work for calls, but the SIM card that was used in this test doesn't allow for calls.</p> <p>Here's a screenshot of the UI in action, sending a SMS to a Maemo Fremantle device from Maemo Leste, and the receiving a response from the Maemo Fremantle device:</p> <img alt="" src="/images/leste-sms-telepathy-ring-1.png" style="width: 596px; height: 276px;" /> </div> <div class="section" id="python-support"> <h3>Python support</h3> <p>Maemo had <a class="reference external" href="http://wiki.maemo.org/PyMaemo">pretty decent python support</a> and we're also planning to bring some of that over pretty soon too, so that we can port and import more packages from Maemo Fremantle. Maemo Fremantle uses Python 2.5, so there's likely some porting work involved. Most of the Fremantle PyMaemo work is stored in this repository: <a class="reference external" href="https://vcs.maemo.org/svn/pymaemo/">https://vcs.maemo.org/svn/pymaemo/</a> (of which we also at least locally have a git-svn version).</p> <p>We're looking for someone to help us with this, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/260">issue #260 for more details</a>.</p> </div> </div> <div class="section" id="device-support-kernel-work"> <h2>Device support &amp; Kernel work</h2> <p>There's been exciting progress on the PowerVR (GPU for Nokia N900, Motorola Droid 4 and other devices) and Mali-400 (GPU for the PinePhone, PineTab, etc) drivers. Lima (the Mali-400 driver) has been merged to mainline Linux (so it's included in the kernel by default) and mesa (the open source 3d library) also merged the lima backend.</p> <div class="section" id="powervr"> <h3>PowerVR</h3> <p>Nikolaus was able to get a binary/reference implementation to run on Linux 5.3-rc4, with some patches and glue code, and basic demos work:</p> <blockquote> <a class="reference external" href="https://marc.info/?l=linux-kernel&amp;m=156577301216115&amp;w=2">https://marc.info/?l=linux-kernel&amp;m=156577301216115&amp;w=2</a></blockquote> <p>After that, others picked up some of the work and as a result it should now be easier to test/load PowerVR glue code.</p> <p>Given that basic demos seem to work, we should attempt to load the powervr module with a matching binary/reference implementation for the Droid 4, and hope that it loads. Getting acceleration in X11 should then be possible (as documented previously) using <a class="reference external" href="https://github.com/TexasInstruments/dri3wsegl">dri3wsegl</a>. And perhaps we can move the Nokia N900 to using DRM instead too, at some point.</p> <p>Next steps are documented in the repository, here:</p> <blockquote> <a class="reference external" href="https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/blob/letux/latest-pvr/drivers/staging/pvr/TODO">https://github.com/openpvrsgx-devgroup/linux_openpvrsgx/blob/letux/latest-pvr/drivers/staging/pvr/TODO</a></blockquote> </div> <div class="section" id="lima"> <h3>Lima</h3> <p>There has been quite some activity with Lima, and after being able to run <a class="reference external" href="https://www.youtube.com/watch?v=ihCVsaEMNzY">hildon-desktop with lima back in 2018</a>, we expect the performance and stability to be a lot better now. Once we <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/214">fix a bug in hildon-desktop</a>, we will record demos of Maemo Leste on the PinePhone and PineTab using the Lima driver.</p> </div> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <p>Recently, the radio transmitter on the Nokia N900 started to work, and <a class="reference external" href="https://leste.maemo.org/Nokia_N900#Status">that is now reflected in the Nokia N900 status page</a></p> <p>We also enabled various features in a newer kernel:</p> <ul class="simple"> <li>Vibration driver is now enabled, and can be tested using <cite>fftest</cite>.</li> <li>iptables/nftables options have been enabled to allow for nat to share phone connections with PCs</li> </ul> <p>The stable release channels also got all the latest PowerVR work, so a simple <cite>apt update &amp;&amp; apt upgrade</cite> should land users with the fastest PowerVR bits.</p> </div> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>The Motorola Droid 4 modem has been working in mainline for a while, but recently some more fixes made the modem work decently with a work-in-progress ofono driver. It's now possible to make calls, send SMS, receive SMS and use internet connections. We aim to package a newer kernel with these fixes and an ofono with enabled backend when we find some time (or when someone steps up to do this...)</p> <p>Additionally, most of the patches on top of mainline for the Motorola Droid 4 have been merged, reducing potential maintenance burdens, and making it easier for others to build their own kernel (previously finding the right patches and the right versions of patches was a little tricky)</p> </div> <div class="section" id="pinephone-pinetab"> <h3>PinePhone &amp; PineTab</h3> <p>As previously discussed, Pine64 is creating a <a class="reference external" href="https://www.pine64.org/pinephone/">Phone</a> meant to run FOSS mobile platforms, for the community, by the community. They are also <a class="reference external" href="https://www.pine64.org/pinetab/">making a Tablet</a> (which they have also kindly given to us).</p> <p>They aim to produce the actual phone early 2020 and have generated some press for Maemo Leste: <a class="reference external" href="https://liliputing.com/2019/06/pinephone-149-linux-smartphone-could-support-ubuntu-sailfish-maemo-luneos-and-more.html">https://liliputing.com/2019/06/pinephone-149-linux-smartphone-could-support-ubuntu-sailfish-maemo-luneos-and-more.html</a></p> <p>Through collaboration and the already amazing <a class="reference external" href="https://linux-sunxi.org">linux-sunxi</a> project we have device trees and kernels that work quite well on the &quot;Don't be evil&quot; devkit:</p> <blockquote> <a class="reference external" href="https://gitlab.com/pine64-org/linux/wikis/Don't-be-evil-devkit">https://gitlab.com/pine64-org/linux/wikis/Don't-be-evil-devkit</a></blockquote> <p>Back in April we made a video showing (64 bit arm) Maemo Leste running on the devkit, without hardware acceleration (apologies for the poor video quality, we'll do a better one soon):</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/JRjhuAC6jo4" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>There are also <a class="reference external" href="https://maedevu.maemo.org/images/pinephone-dontbeevil/">images available for download</a> (probably won't do you much good unless you have a devkit - and they didn't make that many). We also have a <a class="reference external" href="https://leste.maemo.org/Pine64_Anakin_Devkit">PinePhone device page</a> documenting the current kernel support status.</p> <p>In early September we hope to pick up a PinePhone prototype. Hopefully we'll soon also be able to get some images for the PineTab, as we believe Maemo Leste should work quite well on tablets too.</p> </div> </div> <div class="section" id="infrastructure-distribution"> <h2>Infrastructure &amp; Distribution</h2> <p>We have migrated our Mediawiki instance (<a class="reference external" href="https://leste.maemo.org">https://leste.maemo.org</a>) and our Jenkins (<a class="reference external" href="https://phoenix.maemo.org">https://phoenix.maemo.org</a>) to a new machine with faster storage and more RAM.</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/235">armel builds have been disabled</a> , as we currently have no devices that need armel. We might enable armel builds again when we need them.</p> <p>We've also been working on migrating the Devuan Beowulf (Debian Buster), most of the work is just porting packages to a newer <cite>debhelper</cite> version, and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/234">help here would be much appreciated</a>.</p> </div> <div class="section" id="community-documentation"> <h2>Community &amp; Documentation</h2> <p>We've been continually but slowly been documenting <a class="reference external" href="https://leste.maemo.org/Category:Device">device support status</a> and the <a class="reference external" href="https://leste.maemo.org/Status">status of the various core components</a>. There is still a lot to be done to improve the wiki, though.</p> <p>Next on the list will be a tutorial on how to start developing with Maemo Leste, which has been requested several times.</p> </div> <div class="section" id="closing-notes-direction"> <h2>Closing notes / Direction</h2> <p>While we could soon make the N900 Alpha release, we've shifted gears a little more to get the cellular code and UI in place. One reason for this is that we hope to have a usable phone, SMS and contact application ready before the Pinephone goes on sale. We'd love for Maemo Leste to be developer (and maybe FOSS-enthousiast) ready when the PinePhone is ready.</p> <p>What that means is that we will need the following in place:</p> <ul class="simple"> <li>2G/3G/LTE data connections working</li> <li>Usable (ish) interface for SMS and calls.</li> <li>Usable (ish) contacts interface</li> <li>(Somewhat sane) audio routing - switching between headphone, earpiece and speakers.</li> <li>Some contacts UI</li> </ul> <p>It would be great if we could also have:</p> <ul class="simple"> <li>Qt5 and Gtk3 port ready</li> </ul> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2019-03-11T20:00:00+01:002019-03-11T20:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2019-03-11:/maemo-leste-eight-update-january-february-2019.html

<p>It's been two months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-seventh-update-december-2018.html">seventh update</a> and there's a lot to talk about!</p> <p>Let's start off with a gentle reminder - don't forget that we have a mailing list - <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. The mailing list archives are now also functional: <a class="reference external" href="https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html">https …</a></p>

<p>It's been two months since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-seventh-update-december-2018.html">seventh update</a> and there's a lot to talk about!</p> <p>Let's start off with a gentle reminder - don't forget that we have a mailing list - <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. The mailing list archives are now also functional: <a class="reference external" href="https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html">https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html</a></p> <div class="section" id="software-additions"> <h2>Software additions</h2> <p>There have been various additions to our userspace, although most of the work in the last two months has been focused on fixing bugs and driver/kernel support.</p> <div class="section" id="connui-cellular"> <h3>connui-cellular</h3> <p>freemangordon is still steadily working on connui, which is one of the core components of our modem support:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/connui-common">https://github.com/maemo-leste/connui-common</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/connui-cellular">https://github.com/maemo-leste/connui-cellular</a></li> </ul> <p>Once a few other things are sorted (integration with <a class="reference external" href="https://telepathy.freedesktop.org/">Telepathy</a>) we will begin work on the <cite>icd2</cite> oFono plugin, which will provide the actual connectivity part.</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/196">https://github.com/maemo-leste/bugtracker/issues/196</a> <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/195">https://github.com/maemo-leste/bugtracker/issues/195</a></p> </div> <div class="section" id="powervr"> <h3>PowerVR</h3> <p>There has been a lot of movement on the PowerVR side (the 3D acceleration unit/ GPU that a number of our supported devices - such as N900 and the Droid 4 - use).</p> <p>Developers from various platforms and devices are now trying to work on a single PowerVR patchset for mainline to make it easier to support new devices, and eventually attempt to mainline various kernel components. Since a couple of weeks, there is now a Github repository that contains recent kernel sources with some form of PowerVR support: <a class="reference external" href="https://github.com/openpvrsgx-devgroup">https://github.com/openpvrsgx-devgroup</a></p> <p>A mailing list for this effort is still being worked out, but the initial message (over a year ago) can be viewed here: <a class="reference external" href="https://www.pyra-handheld.com/pipermail/kernel/2018-January/002315.html">https://www.pyra-handheld.com/pipermail/kernel/2018-January/002315.html</a></p> <p>And the recent continuation can be read here: <a class="reference external" href="https://www.pyra-handheld.com/pipermail/kernel/2019-February/003094.html">https://www.pyra-handheld.com/pipermail/kernel/2019-February/003094.html</a> (And in thread form <a class="reference external" href="https://www.pyra-handheld.com/pipermail/kernel/2019-February/thread.html#3094">https://www.pyra-handheld.com/pipermail/kernel/2019-February/thread.html#3094</a>)</p> <p>Hopefully there will soon be a base to support PowerVR on <cite>omap</cite>, <cite>sunxi</cite> and <cite>exynos</cite> platforms.</p> <p>Additionally, <cite>spinal84</cite> has, through truly admirable perseverance, figured out how to work around the PowerVR hangs and general slowness of Maemo Leste on the Nokia N900 and we've been working on <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/218">ensuring those fixes end up in the alpha (#218)</a></p> <p>You can see a video of PowerVR on Maemo Leste with better performance here:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/M28Ojvg9i9Q" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div> <div class="section" id="generic-64-bit-arm-rootfs"> <h3>Generic 64 bit ARM rootfs</h3> <p>There is now a generic root filesystem image for 64 bit ARM devices available, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/205">#205</a>:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/arm64-generic/">https://maedevu.maemo.org/images/arm64-generic/</a></blockquote> <p>This is useful for adding support for a new arm64 device. Previously we had to take the Raspberry Pi 3 image and remove device specific packages/drivers. The PineTablet and PinePhone will probably make some use of this generic rootfs.</p> </div> </div> <div class="section" id="device-support"> <h2>Device support</h2> <p>The last two months have been particularly exciting for device support. Both the Nokia N900 and the Motorola Droid 4 now ship with Linux 5.0 with some additional patches.</p> <div class="section" id="nokia-n900"> <h3>Nokia N900</h3> <div class="section" id="easier-installation"> <h4>Easier installation</h4> <p>For the Nokia N900, a new (and easier) way to install Maemo Leste is available and <a class="reference external" href="https://leste.maemo.org/Nokia_N900#If_you_don.27t_want_to_use.2Finstall_Fremantle.2C_or_want_to_install_quickly">documented on our wiki</a> - it is aimed only for users who have no intention of running the old Maemo (Fremantle). Suggested improvements are welcome, please add them to this ticket: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/211">Provide a way to flash leste (or u-boot) directly</a></p> <p>Newer images for the Nokia N900 are also available:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/n900/">https://maedevu.maemo.org/images/n900/</a></blockquote> </div> <div class="section" id="funroll-all-loops"> <h4>-funroll-all-loops</h4> <p>And a performance optimised clutter and hildon-desktop are (temporarily) available here, kindly provided by <cite>spinal84</cite>:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/n900/hd-temporary/">https://maedevu.maemo.org/images/n900/hd-temporary/</a></blockquote> <p><strong>Before you install this optimised clutter and hildon-desktop, ensure that your installation is up to date, either by installing the latest image and upgrading or just running apt update &amp;&amp; apt upgrade!</strong></p> <p>You can install these packages by downloading both, and then running:</p> <blockquote> dpkg -i hildon-desktop_2.2.160_armhf.deb libclutter-0.8-0_0.8.2-0maemo68_armhf.deb</blockquote> <p>Subsequent updates might replace your optimised hildon-desktop again, but you can reinstall it with the same command.</p> </div> <div class="section" id="linux-5-0"> <h4>Linux 5.0</h4> <p>Newer kernel images for the Nokia N900 are also available, but you will have to make sure that your <cite>/boot</cite> partition is an <cite>ext2</cite> filesystem, older Maemo Leste images shipped with <cite>/boot</cite> as a <cite>vfat</cite> partition. You can copy all the files in <cite>/boot</cite> to a temporary location, and then call <cite>mkfs.ext2</cite> on the boot partition and finally copy the files back. Here is a screenshot of Maemo Leste on the Nokia N900 using Linux 5.0:</p> <img alt="" src="/images/leste-n900-linux-5.0.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="faster-charging"> <h4>Faster charging</h4> <p>The N900 will now charge using up to 950mAh, instead of the previous 650mAh, see <a class="reference external" href="https://github.com/maemo-leste/n9xx-linux/pull/4">this pull request for n9xx-linux</a>.</p> </div> <div class="section" id="rebooting-who-does-that-anyway"> <h4>rebooting, who does that anyway?</h4> <p>All known problems regarding device shutdown and reboot have been fixed:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/125">N900: Device Does Not Boot After Shutdown From System Menu Until Battery Removed</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/85">Not possible to shutdown the system (N900)</a></li> </ul> </div> <div class="section" id="lookenpeepers-1"> <h4><a class="reference external" href="https://en.wikipedia.org/wiki/Blinkenlights">lookenpeepers</a></h4> <p>The LED patterns on the Nokia N900 should now also work just like Fremantle, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/186">#186</a>.</p> </div> </div> <div class="section" id="motorola-droid-4"> <h3>Motorola Droid 4</h3> <p>The Motorola Droid has seen some love - the most significant changes are way better kernel and driver support. The device is still not particularly useful for day-to-day usage due to the lack of PowerVR acceleration (but we'll get there). Experimental modem support is now in place, as well as audio and GPS support. This is the result of years of hard work from various people in the FOSS community, and it's amazing how well supported the device has become.</p> <p>The Droid 4 is now also on Linux 5.0:</p> <img alt="" src="/images/droid4-linux-5.0.png" style="width: 613px; height: 360px;" /> <div class="section" id="giving-android-the-kexecboot"> <h4>Giving Android the kexecboot</h4> <p>It should now be a lot easier to install Maemo Leste, thanks to all the work done by Tony Lindgren on <a class="reference external" href="https://github.com/tmlind/droid4-kexecboot">kexecboot</a>. The installation process is documented on our wiki:</p> <blockquote> <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_4#Installation_using_kexecboot">https://leste.maemo.org/Motorola_Droid_4#Installation_using_kexecboot</a></blockquote> <p>Make sure that you use the latest images, since they have been modified to work well with kexecboot:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/droid4/">https://maedevu.maemo.org/images/droid4/</a></blockquote> <p>The latest images also contain a Debian kernel package for the kernel (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/220">see #220</a>: <cite>linux-image-droid4</cite> (currently at version <cite>5.0.0+1m7.1_armhf.deb</cite>), and the source can be found here: <a class="reference external" href="https://github.com/maemo-leste/droid4-linux">https://github.com/maemo-leste/droid4-linux</a></p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/206">https://github.com/maemo-leste/bugtracker/issues/206</a></p> </div> <div class="section" id="audio"> <h4>Audio</h4> <p>Audio works now too, including various switches to control the modem and echo cancellation:</p> <img alt="" src="/images/droid4-alsamixer.png" style="width: 613px; height: 360px;" /> </div> <div class="section" id="ofono-support"> <h4>oFono support</h4> <p>Pavel Machek has been working on <a class="reference external" href="https://github.com/pavelmachek/ofono/tree/d4">oFono support for the Droid 4</a>, and we will attempt to package that work for the Droid 4 soon. Then we should hopefully have a working UI test voice calls.</p> </div> <div class="section" id="random-screenshot"> <h4>Random screenshot</h4> <p>The Droid4 is generally more responsive than the Nokia N900 when it comes to CPU and IO bound operations, but this is not yet visible due to everything being rendered through a 3D pipeline on the cpu. Regardless, here's a screenshot with various applications running on the Droid 4:</p> <img alt="" src="/images/droid4-various-apps.png" style="width: 613px; height: 360px;" /> </div> </div> <div class="section" id="pinephone-anakin-devkit"> <h3>PinePhone &quot;Anakin&quot; Devkit</h3> <p>Pine64 PinePhone first development kit was sent to us some time before FOSDEM, and it took quite some time to test out various patch sets and fixes to these patch sets, but now the display works well, and the lima driver also works. The lima driver is still experimental, and hildon-desktop tends to crash under lima, but we'll get to solving those issues eventually.</p> <p>At FOSDEM, the UBPorts people figured out how to make the touchscreen work as well, so we will probably release an image some time soon for the devkit, as it should quite closely match the upcoming PineTab.</p> </div> </div> <div class="section" id="community"> <h2>Community</h2> <div class="section" id="devuan-conference"> <h3>Devuan Conference</h3> <p>There is a Devuan (the distribution that Maemo Leste is based on) conference in Amsterdam in April, so if you're around, it might be fun checking it out: <a class="reference external" href="https://devuan.org/os/debian-fork/d1conf-announce-20190119">https://devuan.org/os/debian-fork/d1conf-announce-20190119</a></p> </div> <div class="section" id="fosdem"> <h3>FOSDEM</h3> <p>FOSDEM 2019 was a lot of fun, and <a class="reference external" href="https://fosdem.org/2019/schedule/event/maemo_leste_mobile/">we gave a lightning talk:</a></p> <div class="section" id="this-video-is-optimised-for-800-480-on-firefox-3-5"> <h4>This video is optimised for 800*480 on Firefox 3.5</h4> <video width="750" height="441" controls> <source src="https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.webm" type="video/webm"> <p>Your browser doesn't support HTML5 video. Here is a <a href="https://video.fosdem.org/2019/H.2215/maemo_leste_mobile.webm">link to the video</a> instead.</p> </video><p>The slides can be found here:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/media/fosdem-2019-maemo-leste.pdf">https://maedevu.maemo.org/media/fosdem-2019-maemo-leste.pdf</a></blockquote> <p>After the talk, we chatted for over an hour in the hall next to the Lightning Talks room. Several postmarketOS developers showed up, as did old Nokia employees who actually worked on Maemo Fremantle! The people from Necunos also showed up and demonstrated their prototype NC_1 board.</p> </div> <div class="section" id="mobile-humans-and-martians"> <h4>Mobile humans and martians</h4> <p>Also present at FOSDEM were people from PostmarketOS, UBPorts and KDE Plasma, and we got together for a picture:</p> <img alt="" src="/images/fosdem-meetup.jpg" style="width: 576px; height: 324px;" /> <p>Additionally, various community hardware vendors were also present. The Pine64 community had a stand, where they presented their first phase <a class="reference external" href="http://wiki.pine64.org/index.php/Project_Anakin">Anakin devkit</a> and the <a class="reference external" href="http://wiki.pine64.org/index.php/Project_Don%27t_be_evil">&quot;Don't be evil&quot;</a> second phase devkit. Maemo Leste will receive several &quot;Don't be evil&quot; devkits somewhere this months, when they start shipping. In fact, there is already a placeholder for Maemo Leste OS releases: <a class="reference external" href="http://wiki.pine64.org/index.php/Project_Don%27t_be_evil#Maemo_OS_build">http://wiki.pine64.org/index.php/Project_Don%27t_be_evil#Maemo_OS_build</a></p> <p>Some of us also met with the Necunos team and discussed some more details of their upcoming device, of which Maemo Leste will also receive a devkit.</p> </div> </div> <div class="section" id="artwork"> <h3>Artwork</h3> <p>A member of <a class="reference external" href="http://talk.maemo.org">talk.maemo.org</a> created this <a class="reference external" href="https://talk.maemo.org/showthread.php?t=100648&amp;highlight=maemo+legend">Crest of Maemo</a> and offered to send it our way!</p> <img alt="" src="/images/crestofmaemo.jpg" style="width: 688px; height: 866px;" /> <p>A loving fan has created this large reproduction of the Nokia N900, including <cite>hildon-desktop</cite>, the <cite>osso-xterm</cite> application, the status applets and even real backlight! The metal theme looks quite good, too.</p> <img alt="" src="/images/n900-giant-reproduction.jpg" style="width: 600px; height: 400px;" /> </div> <div class="section" id="some-screenshots"> <h3>Some screenshots</h3> <p>The next couple of updates will probably be accompanied with screenshots showing off some software straight from Debian repositories running on Maemo Leste, to show off how many applications are already available.</p> <div class="section" id="cute-theme"> <h4>Cute theme?</h4> <p>Qt5 applications can be started with different themes, this is Wireshark with the default theme:</p> <img alt="" src="/images/wireshark-leste.png" style="width: 576px; height: 324px;" /> <p>And this is wireshark with our (work in progress) Qt5 theme:</p> <img alt="" src="/images/wireshark-leste-style-wip.png" style="width: 576px; height: 324px;" /> <p>Wireshark is not particularly usable on such a small resolution regardless, but at least the theme fits - usability aside.</p> </div> <div class="section" id="gtk"> <h4>GTK</h4> <p>Other applications from Debian are also quite usable, without any recompilation whatsoever. This is GMPC, the Gnome frontend of MPD, the music player daemon. (These applications are not &quot;hildonised&quot;, that is, they are not optimised for Maemo Leste per se, but it does goes to show that this might not always be necessary either):</p> <img alt="" src="/images/gmpc.png" style="width: 576px; height: 324px;" /> <p>And here are it's initial assistant dialogs:</p> <img alt="" src="/images/gmpc-assistant.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/gmpc-assistant-2.png" style="width: 576px; height: 324px;" /> <p>In this case, the virtual keyboard is also integrated in standard Debian gtk applications, such as netsurf, a very lightweight browser:</p> <img alt="" src="/images/netsurf-vkb.png" style="width: 576px; height: 324px;" /> <p>And the resulting web page render:</p> <img alt="" src="/images/netsurf-maemo-leste.png" style="width: 576px; height: 324px;" /> </div> </div> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>The last missing item before we release an Alpha is to add support for keyboard slide monitoring to either <cite>mce</cite> or <cite>ke-recv-extra</cite>, so that the slide value for the keyboard is set properly in gconf. This is required to have the virtual keyboard behave on phones with physical keyboards: if the keyboard is opened, then we only want to present special symbols not present on the keyboard, if the keyboard is closed, then we may want to present the full virtual keyboard instead.</p> <p>Other than that, it seems like we've reached almost all of our <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Alpha goals</a>, to the point that we might actually issue the first Alpha release soon!</p> <p>We may end up switching to Devuan Beowulf (Debian Buster) before or after the Alpha, it depends on how time it takes to port to the newer release, as well as the amount of bugs introduced by doing so.</p> <p>We will likely also have one or two days of downtime on our Jenkins build service while we migrate it to a more powerful server to speed up build times and ensure that we will not run out of storage any time soon.</p> <p>Personally, I hope that we will be able to get decent support for modems in place soon: with <cite>connui-cellular</cite> well on underway it may soon be time to start working on the <cite>oFono</cite> plugin for <cite>icd2</cite>. At least the Nokia N900 and Droid 4 now also have a working modem and (mostly) working oFono support, so that should be promising.</p> <p>Hopefully we'll also get PowerVR support for the Droid 4 hammered out soon, that will make the device a lot more usable.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p><strong>We have several Nokia N900 and Motorola Droid 4 units available to interested developers</strong>, so if you are interested in helping out but have trouble acquiring a device, let us know.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2019-01-17T20:00:00+01:002019-01-17T20:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2019-01-17:/maemo-leste-seventh-update-december-2018.html

<p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-sixth-update-november-2018.html">sixth update</a> and there's quite some stuff to talk about!</p> <p>First of all, sorry for the delay in the update, it's overdue by almost two weeks. Second of all, if you missed our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-lima-works.html">lima update</a>, make sure to check that out!</p> <div class="section" id="fosdem"> <h2>FOSDEM</h2> <p>There will …</p></div>

<p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-sixth-update-november-2018.html">sixth update</a> and there's quite some stuff to talk about!</p> <p>First of all, sorry for the delay in the update, it's overdue by almost two weeks. Second of all, if you missed our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-lima-works.html">lima update</a>, make sure to check that out!</p> <div class="section" id="fosdem"> <h2>FOSDEM</h2> <p>There will be a lightning talk about <a class="reference external" href="https://fosdem.org/2019/schedule/event/maemo_leste_mobile/">Maemo Leste at FOSDEM 2019</a> - we will try our best to bring a couple of demo devices and show off Maemo Leste after the lightning talk!</p> <div class="section" id="pine64"> <h3>Pine64</h3> <p>The Pine64 community will have a stand at FOSDEM, where they will show their prototypes of the PineTablet and PinePhone - they might even be able to show off Maemo Leste running on their prototypes.</p> </div> <div class="section" id="necunos-nc-1"> <h3>Necunos NC_1</h3> <p><a class="reference external" href="https://necunos.com/news/necunos-nc_1-and_ne_1-press-release/">Necunos NC_1 and NE_1</a> has launched, and <a class="reference external" href="https://necunos.com/shop/#!/Necunos-NC_1/p/127507133/category=0">can be ordered with Maemo Leste preinstalled</a> - at least, if we manage to have a usable image by the time they plan to ship the devices - we don't have Maemo Leste running on their device yet.</p> <p>Necunos has told us that we will probably get a Necunos development kit at FOSDEM.</p> </div> </div> <div class="section" id="aarch64-images"> <h2>Aarch64 images!</h2> <p>The first aarch64 images are now available, for the raspberry pi 3. They still lack hardware acceleration, but almost all of the (essential) packages for Maemo Leste are now also working/built for 64 bit arm:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/raspi3-64bit/20181219/">https://maedevu.maemo.org/images/raspi3-64bit/20181219/</a></blockquote> <p>And the aarch64 packages are confirmed to also work on other devices - like the Pine64 Anakin Devkit!</p> </div> <div class="section" id="motorola-droid-4-improvements"> <h2>Motorola Droid 4 improvements</h2> <p>The Linux kernel developers (little elves) have been working hard on improving <a class="reference external" href="https://lkml.org/lkml/2018/12/16/231">modem support for the Motorola Droid 4</a>, which should make ofono and/or modemmanager integration way easier, which is good news! We're tracking <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/150">ofono support for the Droid 4</a> in this issue.</p> <p>And they also report that during <a class="reference external" href="https://lkml.org/lkml/2018/12/28/429">idle the phone battery life might be almost 5 days</a>.</p> <p>We have contributed a patch that should make the charger events on the Droid 4 fast. Before, the events were not being sent by the kernel, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/206">Issue #206</a>. (<a class="reference external" href="https://patchwork.kernel.org/patch/10744035/">Patch here</a>)</p> <p>PowerVR support for the Droid 4 should make the device quite usable, so that should perhaps soon become a priority. We have a couple of spare Droid 4 devices now, so if you're a capable developer and want to help out with kernel or userspace development, but don't have a device, we can perhaps arrange to get you one.</p> </div> <div class="section" id="nokia-n900-improvements"> <h2>Nokia N900 improvements</h2> <p><cite>spinal84</cite> and <cite>freemangordon</cite> have made some great progress towards making Maemo Leste on the N900 feel more like Maemo Fremantle - in a good way. Graphics are more smooth, charging detection responds almost instantaneously now, and the RGB led works like you're used to in Fremantle.</p> <p>There are newer images, even though those are likely already a bit outdated:</p> <blockquote> <a class="reference external" href="https://maedevu.maemo.org/images/n900/20181222/">https://maedevu.maemo.org/images/n900/20181222/</a></blockquote> <div class="section" id="battery-improvements"> <h3>Battery improvements</h3> <p>spinal84 has been working on fixing up the battery/power parts of the N900, and he has succeeded. With this <a class="reference external" href="https://github.com/maemo-leste/status-area-applet-battery/pull/4">status-area-applet-battery pull request</a> and this <a class="reference external" href="https://github.com/maemo-leste/upower/pull/3">upower pull request</a>, state changes in charging are now picked up instantly. (Fixes <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/67">#67</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/70">#70</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/167">#167</a>)</p> </div> <div class="section" id="rgb-led-support"> <h3>RGB LED support</h3> <p>This <a class="reference external" href="https://github.com/maemo-leste/mce/pull/2">mce pull request</a> makes the RGB led on the N900 usable, and when the right patterns are enabled from the Settings, the LED patterns should start to work. Soon we'll be able to close <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/186">issue #186</a>.</p> </div> <div class="section" id="rebooting-shutdown-watchdog"> <h3>Rebooting, Shutdown, Watchdog</h3> <p>We've been working hard on fixing two of the last few remaining alpha tickets:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/125">N900: Device Does Not Boot After Shutdown From System Menu Until Battery Removed</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/85">Not possible to shutdown the system (N900)</a></li> </ul> <p>Various fixes to dsme made a difference, and in some cases, now allow for clean shutdown and reboot. However, more work seems to be required to make it always work reliably. The PowerVR module for the current kernel also has some bugs that prevent clean shutdown.</p> <p><a class="reference external" href="https://github.com/maemo-leste/dsme/commit/8831309eebb232fbd7d6e678f7803e3177cdd458">https://github.com/maemo-leste/dsme/commit/8831309eebb232fbd7d6e678f7803e3177cdd458</a> <a class="reference external" href="https://github.com/maemo-leste/dsme/commit/2d4db8f5e14bc0f131ee5402915188b01968f8e0">https://github.com/maemo-leste/dsme/commit/2d4db8f5e14bc0f131ee5402915188b01968f8e0</a></p> <p>On the subject of PowerVR...</p> </div> <div class="section" id="powervr-gpu"> <h3>PowerVR/GPU</h3> <p>A lot of time has been spent trying to figure out why PowerVR hangs for minutes on startup. In this process, <cite>freemangordon</cite> wrote a patch to bring the PowerVR up to its proper clock speed, which greatly improves the performance of PowerVR in general, but this unfortunately does not fix the slowness/hang on startup.</p> <p>More investigation will be required to fix the temporary hang on start.</p> </div> <div class="section" id="sms-and-voice-calls"> <h3>SMS and Voice calls</h3> <p>unicsy_demo, a tool to test and use various modem functionality (amongst other things) <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/174">has now been packaged (#174)</a>, and success looks like this:</p> <img alt="" src="/images/n900-ofone-initial.png" style="width: 576px; height: 324px;" /> <p>Incoming SMS works (sending SMS works as well):</p> <img alt="" src="/images/n900-ofone-incoming-sms.png" style="width: 576px; height: 324px;" /> <p>Working voice calls is still work in progress, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/77">Issue #77</a>.</p> </div> <div class="section" id="g-3g-and-4g-data"> <h3>2G, 3G and 4G data</h3> <p><cite>freemangordon</cite> has been doing more work on connui, to make it feasible to implement the ofono/data plugin for icd2. Apart from a plugin icd2, there's more work required, as we'll have to implement or replace various dbus interfaces that Fremantle offers.</p> <p>The current work can be found here:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/connui-cellular">https://github.com/maemo-leste/connui-cellular</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/connui-common/commits/master">https://github.com/maemo-leste/connui-common/commits/master</a></li> </ul> <p>The next step will be to make an overview of all the work that needs to be done, and then start picking up the tasks one by one.</p> </div> <div class="section" id="flasher-u-boot-work"> <h3>Flasher/u-boot work</h3> <p>We're working on a way to make testing and installing Maemo Leste easier than the current procedure - which involves installing and updating Maemo Fremantle before running Maemo Leste. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/211">Issue 211</a> covers this in more detail, but our hope is that we can make it so that users can flash u-boot to the device, and then be able to directly boot Fremantle or Leste, or another OS, like postmarketOS.</p> <p>There is also some upstream churn going on regarding u-boot support for the Nokia N900, see:</p> <ul class="simple"> <li><a class="reference external" href="https://lists.denx.de/pipermail/u-boot/2018-December/353007.html">https://lists.denx.de/pipermail/u-boot/2018-December/353007.html</a></li> <li><a class="reference external" href="https://lists.denx.de/pipermail/u-boot/2018-December/353008.html">https://lists.denx.de/pipermail/u-boot/2018-December/353008.html</a></li> </ul> </div> </div> <div class="section" id="lima"> <h2>Lima</h2> <p>As mentioned in our last <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-lima-works.html">lima update</a>, the driver can now render <cite>hildon-desktop</cite>. Not everything renders correctly. Some borders are missing, as can be seen here, but otherwise - it's working quite fast and smooth:</p> <img alt="" src="/images/lima-twister-wifi.png" style="width: 512px; height: 300px;" /> <p>The lima mesa package in our repository is still on Mesa 18.2, while upstream lima has moved to Mesa 18.3. We need to rebuild the latest 18.3 version and check if it still works.</p> <p>We also tried to compile lima for aarch64, but ran into internal errors in <cite>ld</cite> when linking the final drivers:</p> <blockquote> <a class="reference external" href="https://web.archive.org/web/20190117070625/https://phoenix.maemo.org/job/mesa-binaries/architecture=arm64,label=arm64/1/console">https://web.archive.org/web/20190117070625/https://phoenix.maemo.org/job/mesa-binaries/architecture=arm64,label=arm64/1/console</a></blockquote> <p>This is slightly problematic, because we need the aarch64 version for the Pine64 Anakin Devkit. But perhaps the issue will be gone with mesa 18.3.</p> <p>If you want to follow lima activity, you can do so here: <a class="reference external" href="https://gitlab.freedesktop.org/lima/mesa/activity">https://gitlab.freedesktop.org/lima/mesa/activity</a></p> </div> <div class="section" id="maemo-leste-and-mer"> <h2>Maemo Leste and Mer</h2> <p><cite>spiirion</cite> has been working on making mer versions of some core software (like <cite>dsme</cite> and <cite>mce</cite>) work on Maemo Leste. At this point, he has some of it working here:</p> <ul class="simple"> <li><a class="reference external" href="https://git.merproject.org/spiiroin/mce-dev/tree/maemo-leste-hacking">https://git.merproject.org/spiiroin/mce-dev/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://git.merproject.org/spiiroin/libdsme/tree/maemo-leste-hacking">https://git.merproject.org/spiiroin/libdsme/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://git.merproject.org/spiiroin/libiphb/tree/maemo-leste-hacking">https://git.merproject.org/spiiroin/libiphb/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://git.merproject.org/spiiroin/dsme/tree/maemo-leste-hacking">https://git.merproject.org/spiiroin/dsme/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://git.merproject.org/spiiroin/mce/tree/maemo-leste-hacking">https://git.merproject.org/spiiroin/mce/tree/maemo-leste-hacking</a></li> <li><a class="reference external" href="https://github.com/spiiroin/mce-plugin-libhybris/tree/maemo-leste-hacking">https://github.com/spiiroin/mce-plugin-libhybris/tree/maemo-leste-hacking</a></li> </ul> </div> <div class="section" id="samsung-s5pv210-support"> <h2>Samsung S5PV210 support?</h2> <p>Someone from the community named <cite>PabloPL</cite> has made impressive progress with making an Exynos based phone work with mainline, <a class="reference external" href="https://github.com/PabloPL/linux/wiki">see the current status of mainline plus patches here</a>. The Samsung Galaxy S (i9000) also has a PowerVR GPU, just like the Droid4, so hopefully we can collaborate on making PowerVR better supported on mainline Linux (although the userspace will probably remain closed forever).</p> <p><cite>PabloPL</cite> also has an open issue for supporting PowerVR: <a class="reference external" href="https://github.com/PabloPL/linux/issues/18">https://github.com/PabloPL/linux/issues/18</a></p> </div> <div class="section" id="community"> <h2>Community</h2> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>A lot has happened in the past month and a half, and it's been hard to focus on one specific issue, but nevertheless we've made a lot of progress.</p> <p>Our current software/driver goals are:</p> <ul class="simple"> <li>Fix reboot/poweroff issues</li> <li>Make text and voice calls work on N900 and Droid4</li> <li>Fix PowerVR issues on N900, make PowerVR work on the Droid4</li> <li>Work on 2g/3g/4g data plugin for icd2</li> </ul> <p>As for new hardware enablement/drivers, we plan to:</p> <ul class="simple"> <li>Build the lima driver for mesa 18.3 for aarch64 and armhf</li> <li>Make Leste work properly on the Anakin kit, hopefully -before- FOSDEM</li> <li>Make Leste work on Necunos NC_1 development kit when we get one.</li> </ul> <p>At that point, we're almost ready for the first alpha release. We might move the (large) <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/53">Qt task</a> to a next alpha or beta release. If you're experienced with Qt, we would definitely use the help!</p> <p>Finally, if you have a spare device that we already support, there may be developers who would be very happy to recieve it by post and make Maemo Leste work (even) better! We now have a couple of spare Motorola Droid 4 devices that we can give to developers who want to work on phone calls and/or PowerVR support.</p> <p>If you have a spare Nexus 5 or Nokia N900, those might turn out to be quite helpful as well.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2018-12-07T23:50:00+01:002018-12-07T23:50:00+01:00Merlijn Wajertag:maemo-leste.github.io,2018-12-07:/maemo-leste-lima-works.html

<p>This update is relatively small - but it does contain something huge: Lima now renders hildon-desktop!</p> <div class="section" id="mali-gpus-and-the-lima-driver"> <h2>Mali GPUs and the Lima Driver</h2> <p>As we documented in our November 2018 update <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-sixth-update-november-2018.html">November 2018 update</a>, we were making progress trying to get the Lima driver to run on some Allwinner devices.</p> <p>This is …</p></div>

<p>This update is relatively small - but it does contain something huge: Lima now renders hildon-desktop!</p> <div class="section" id="mali-gpus-and-the-lima-driver"> <h2>Mali GPUs and the Lima Driver</h2> <p>As we documented in our November 2018 update <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-sixth-update-november-2018.html">November 2018 update</a>, we were making progress trying to get the Lima driver to run on some Allwinner devices.</p> <p>This is important, as a lot of ARM devices have a Mali GPU. Not all of them have a Mali-400 or Mali-450, but a big chunk of them does - especially the Allwinner single board computers and tablets. However, ARM does not provide a free (as in freedom) driver for their GPUs. Back in 2014, <a class="reference external" href="https://www.youtube.com/watch?v=7z6xjIRXcp4">Luc Verhaegen presented his (and others) work on freeing the Mali</a> - a talk that I also personally attended and got me excited about the possibility of using a free driver on my Allwinner devices. Some time later, he <a class="reference external" href="https://libv.livejournal.com/27461.html">documented why he had stopped working on the driver</a> - but eventually others (in particular Qiang Yu) have picked up the work, <a class="reference external" href="https://gitlab.freedesktop.org/lima">and the current code can be found here</a> - the kernel side of this work has also been <a class="reference external" href="https://lists.freedesktop.org/archives/dri-devel/2018-May/177314.html">submitted for review</a> to the Linux kernel.</p> <p>Excited (once again) at the prospect of having a FOSS Mali driver, we set up <a class="reference external" href="https://phoenix.maemo.org/job/mesa-binaries/">(semi) automatic builds</a> and added it to the <a class="reference external" href="https://maedevu.maemo.org/leste/pool/lima/m/mesa/">lima component of our Maemo Leste Devuan/Debian repository</a> of lima-mesa, the mesa code that supports lima. In our latest update, we stated that, unfortunately, <a class="reference external" href="https://gitlab.freedesktop.org/lima/mesa/issues/70">lima cannot render hildon-desktop yet</a> (and that <a class="reference external" href="https://github.com/apitrace/apitrace/issues/599">we ran into (and fixed) an apitrace issue</a>), but this is no longer true, with the last few commits to <cite>lima/mesa</cite>, it is possible to run hildon-desktop (albeit some render artifacts remain), and we have made a video showing it in action on our <a class="reference external" href="https://leste.maemo.org/A33-TurboX-Twister">A33 &quot;TurboX Twister&quot; tablet</a>:</p> <iframe width="560" height="315" src="https://www.youtube.com/embed/ihCVsaEMNzY" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><p>(<a class="reference external" href="https://github.com/maemo-leste/lime2-linux/tree/lime2-and-twister-4.19-rc4-20181207">Kernel tree can be found here.</a>)</p> <p>This is also great news for the Pine64 project, who are developing a <a class="reference external" href="http://wiki.pine64.org/index.php/Project_Anakin">Pine64 phone and Pine64 tablet</a> (and have been so kind to send us a &quot;Project Anakit&quot; development kit as well) - because now their phone will have a free software driver!</p> <p>To be clear, the experience is not entirely smooth, and we've had the driver crash on us a few times - but it's FOSS, so anyone can attempt to fix it (as people are doing already). Onwards!</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2018-12-05T09:00:00+01:002018-12-05T09:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2018-12-05:/maemo-leste-sixth-update-november-2018.html

<p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fifth-update-september-october-2018.html">fifth update</a> and there's quite some stuff to talk about!</p> <div class="section" id="media"> <h2>Media</h2> <p>Our talk introducing Maemo Leste at <a class="reference external" href="https://www.youtube.com/watch?v=WT1hwtEPt7o">OpenFest 2018</a> is now online (The <a class="reference external" href="https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf">slides are also available</a>).</p> <p>We have also switched to a more clear Pelican theme for our (this) website and added a …</p></div>

<p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fifth-update-september-october-2018.html">fifth update</a> and there's quite some stuff to talk about!</p> <div class="section" id="media"> <h2>Media</h2> <p>Our talk introducing Maemo Leste at <a class="reference external" href="https://www.youtube.com/watch?v=WT1hwtEPt7o">OpenFest 2018</a> is now online (The <a class="reference external" href="https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf">slides are also available</a>).</p> <p>We have also switched to a more clear Pelican theme for our (this) website and added a <a class="reference external" href="https://maemo-leste.github.io/pages/screenshots.html">Screenshots</a> page!</p> </div> <div class="section" id="software"> <h2>Software</h2> <div class="section" id="aarch64"> <h3>aarch64</h3> <p>Our <a class="reference external" href="https://phoenix.maemo.org/">Jenkins</a> instance now has <strong>aarch64</strong> (<strong>arm64</strong>) builds for almost all our packages and we have a working Raspberry Pi 3 with <strong>aarch64</strong> Maemo userland. Images for the Raspberry 3 (and other devices) will follow in December.</p> </div> <div class="section" id="qt5"> <h3>Qt5</h3> <p>Work on porting the Maemo style and Maemo widgets to Qt5 is still progressing. There are still some issues to sort out - some widgets end up being too large or fullscreen when they should not be. Regardless, here is an example widget:</p> <img alt="" src="/images/n900-qt5.png" style="width: 576px; height: 324px;" /> <p>Once the Qt5 port is in better shape, we'll work on supporting GStreamer 1.0 as well, so that we can build <a class="reference external" href="https://wiki.maemo.org/Open_Media_Player">Open Media Player</a>.</p> </div> <div class="section" id="lima-driver-for-mali-gpus-apitrace"> <h3>lima driver for Mali GPUs, apitrace</h3> <p>The open source <a class="reference external" href="https://gitlab.freedesktop.org/lima/">lima</a> driver is a driver for Mali GPUs (see the <a class="reference external" href="https://www.youtube.com/watch?v=7z6xjIRXcp4">FOSDEM talk</a>).</p> <p>The lima driver is still under heavy development, and it is not yet merged into mesa yet. We <a class="reference external" href="https://phoenix.maemo.org/job/mesa-binaries/">use Jenkins to build a Lima enabled mesa for us</a>, which can be found in the <cite>lima</cite> component in our repositories: <a class="reference external" href="https://maedevu.maemo.org/leste/pool/lima/">https://maedevu.maemo.org/leste/pool/lima/</a> The lima driver also has a kernel component, which is already included in our latest Allwinner images.</p> <p>However, <a class="reference external" href="https://gitlab.freedesktop.org/lima/mesa/issues/70">lima cannot render hildon-desktop yet</a>; and while trying to submit a debug trace using apitrace <a class="reference external" href="https://github.com/apitrace/apitrace/issues/599">we ran into (and fixed) an apitrace issue</a>, and now a proper debug trace is also submitted to the Lima driver developers.</p> <p>Finally, we have a <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/181">tracking ticket for Lima support</a>.</p> </div> <div class="section" id="icd2-and-clockd-code-improvements-documentation"> <h3>icd2 and clockd code improvements, documentation</h3> <p><em>spinal84</em> has been continuing his great work on cleaning up the <em>icd2</em> and <em>clockd</em> code, as well as documenting it (this list is not exhaustive):</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/icd2/pull/9">https://github.com/maemo-leste/icd2/pull/9</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/clockd/pull/4">https://github.com/maemo-leste/clockd/pull/4</a></li> </ul> </div> <div class="section" id="hildon-application-manager-ham"> <h3>Hildon Application Manager (HAM)</h3> <p>What is a mobile distribution without a GUI package manager? We took the source straight from Maemo Fremantle, fixed a few compilation errors, and behold, the package manager starts (and that's probably about it, nothing else was tested yet):</p> <img alt="" src="/images/raspi-ham.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="shutdown-woes"> <h3>Shutdown woes</h3> <p>One of the remaining alpha blocker bugs is that shutting down the device using the UI doesn't work the way it's supposed to work. We've now <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/125#issuecomment-443454882">figured out the problem</a> and will be able to move forward with both a temporary and more permanent solution. The reason is that the shutdown feature actually tries to bring the device into the so called <strong>act dead</strong> mode, in which mode the device acts like it's not powered on. Sounds scary? Perhaps, but this feature is for example essential for the phone to turn itself on on an alarm (and more, but we have to figure that out, the entire Maemo Fremantle boot process is documented here: <a class="reference external" href="http://wiki.maemo.org/Maemo_5_boot_process">http://wiki.maemo.org/Maemo_5_boot_process</a>).</p> </div> <div class="section" id="calendar-support"> <h3>Calendar support</h3> <p>While no code has been written yet, we have a plan on how to move forward with <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/203">calendar support</a>. The various components (backend and GUI) are open source or have open source clones/implementations. Unfortunately, the GUI will (also) depend on Qt5 port being brought to a usable state.</p> </div> </div> <div class="section" id="devices"> <h2>Devices</h2> <div class="section" id="pinetablet-pinephone-anakin-devkit"> <h3>PineTablet/PinePhone &quot;Anakin&quot; devkit</h3> <p>The Pine64 folks are making a PineTablet and a PinePhone, and they were so kind as to provide us with <em>three</em> developer kits, more information on the developer kit can be found here:</p> <p><a class="reference external" href="http://wiki.pine64.org/index.php/Project_Anakin">http://wiki.pine64.org/index.php/Project_Anakin</a></p> <p>This developer kit is one of the main reasons that our packages are now available on <strong>aarch64</strong>. We'll share updates once more starts to work on the developer kit.</p> <img alt="" src="/images/Anakin_kit_1.jpg" style="width: 300px; height: 400px;" /> <img alt="" src="/images/Anakin_kit_2.jpg" style="width: 300px; height: 400px;" /> </div> </div> <div class="section" id="distribution"> <h2>Distribution</h2> <p>Maemo Leste is based on Devuan, currently targetting <strong>Devuan Ascii</strong>, which closely tracks <strong>Debian Stretch</strong> (current stable version of Debian).</p> <div class="section" id="devuan-beowulf-debian-buster"> <h3>Devuan Beowulf (Debian Buster)</h3> <p>We've making some progress towards porting and building the Maemo Leste packages on the next version of Devuan: Beowulf (which in turn is based on upcoming version of Debian: Buster). Jenkins now supports building our packages for this upcoming release. It will be a while before Beowulf is released, but when it is, we will be ready!</p> </div> <div class="section" id="leste-devel-repository"> <h3>leste-devel repository</h3> <p>We have introduced a <cite>leste-devel</cite> repository, which developers and users can use to test experimental code changes; see <a class="reference external" href="https://github.com/maemo-leste/icd2/pull/9#issuecomment-443375660">this icd2 pull request</a> on how we currently use this repository.</p> </div> </div> <div class="section" id="documentation"> <h2>Documentation</h2> <p>We've put some more effort into our <a class="reference external" href="https://leste.maemo.org/Status">Software Status</a> page - it now covers more software components and also (might) have some information on the status of each component.</p> </div> <div class="section" id="open-issues"> <h2>Open issues</h2> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues">https://github.com/maemo-leste/bugtracker/issues</a></p> <ul class="simple"> <li>For virtual keyboard to work, you have to reboot once after booting the fresh/new image. Then the virtual keyboard can be enabled from the settings <cite>Text Input</cite> applet.</li> <li>Several devices still lack 3D acceleration support, making the user experience particularly painful.</li> </ul> </div> <div class="section" id="community"> <h2>Community</h2> <div class="section" id="no-fosdem-stand"> <h3>No FOSDEM stand</h3> <p>Together with postmarketOS we applied for a stand at FOSDEM 2019, which unfortunately was not accepted. However, both the postmarketOS and Maemo Leste people will attend FOSDEM regardlessly.</p> </div> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>Most of our attention has been focussed on reaching the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Alpha release</a> and we're down to 4 issues before we reach the alpha milestone.</p> <p>Two issues pertain to reboot/poweroff not functioning as it should, one is for Qt5 and one for the final pieces of the virtual keyboard - monitoring the slide state of the keyboard (open or closed).</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2018-11-06T23:00:00+01:002018-11-06T23:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2018-11-06:/maemo-leste-fifth-update-september-october-2018.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fourth-update-july-august-2018.html">fourth update</a> and there's quite some stuff to talk about!</p> <p>Don't forget that we have a mailing list - <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. The mailing list archives are now also functional: <a class="reference external" href="https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html">https://lists.dyne.org/lurker/mindex/maemo-leste …</a></p>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-fourth-update-july-august-2018.html">fourth update</a> and there's quite some stuff to talk about!</p> <p>Don't forget that we have a mailing list - <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. The mailing list archives are now also functional: <a class="reference external" href="https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html">https://lists.dyne.org/lurker/mindex/maemo-leste&#64;19700101.000000.00000000.en.html</a></p> <div class="section" id="software-additions"> <h2>Software additions</h2> <p>There have been lots of changes all over the place, below follows an attempt to highlight some of those changes.</p> <div class="section" id="boot-issues-resolved"> <h3>Boot issues resolved</h3> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/83">issue #83</a> is now fixed and the lock screen now works properly on boot, without requiring parallel boot to be enabled (in fact, parallel boot is still buggy, so don't enable it).</p> </div> <div class="section" id="scrolling-in-osso-xterm"> <h3>Scrolling in osso-xterm</h3> <p>Spinal84 <a class="reference external" href="https://github.com/maemo-leste/osso-xterm/pull/1">fixed scrolling in osso-xterm</a>, which is a really welcome addition.</p> </div> <div class="section" id="usb-gadget-host-otg-mode"> <h3>USB Gadget/Host/OTG mode</h3> <p>Maemo Leste uses the Linux <a class="reference external" href="https://www.kernel.org/doc/Documentation/usb/gadget_configfs.txt">gadget configfs</a> to configure USB gadgets. The userspace library used to interface with the kernel configfs is <a class="reference external" href="https://github.com/maemo-leste/libusbgx">libusbgx</a>.</p> <p>The new <a class="reference external" href="https://github.com/maemo-leste/hildon-usb-gadgets">hildon-usb-gadgets</a> package uses libusbgx to implement two simple gadgets: a network gadget and a mass storage gadget. The mass storage gadget needs significantly more work, so it's mostly a stub right now.</p> <p>This is complemented by the initial udev-enabled (previous versions relied on the now deprecated hal) version of <a class="reference external" href="https://github.com/maemo-leste/ke-recv">ke-recv</a>, which received kernel events regarding usb cable plugging and managed the gadget mode of the phone. The branch &quot;nextgen-usbhack&quot; contains the udev work and hildon-usb-gadgets integration.</p> <p>The same udev code was used to bring up <a class="reference external" href="https://github.com/maemo-leste/hildon-status-bar-usb">hildon-status-bar-usb</a>, the lengthy path to getting this to work is documented in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/39">issue #39</a></p> <p>The result of this work can be seen here:</p> <img alt="" src="/images/n900-usb-pcsuite-3.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-usb-pcsuite-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-usb-pcsuite-2.png" style="width: 576px; height: 324px;" /> <p>By default, ke-recv will always enter &quot;PC Suite&quot; mode for now, which really just means that any device that is capable of usb peripherals will have usb networking set up to ease debugging. The device will assign itself the static IP <cite>192.168.42.2</cite>, so something like this on the host device should bring up communication: <cite>ifconfig usb0 up 192.168.42.1</cite>.</p> <p>More information on usb networking can be found on this page: <a class="reference external" href="https://leste.maemo.org/Status/USB_Peripheral">https://leste.maemo.org/Status/USB_Peripheral</a></p> <p>This currently works on the Nokia N900, Motorola Droid 4, and Allwinner devices (like the LIME2 and A33 Twister Tablet).</p> <p>To be able to detect whether a device is connected to a PC or just a &quot;wall charger&quot;, we have to rely on musb (and other similar drivers). Unfortunately, musb will only expose this state if a gadget is loaded. As a result, a usb gadget is always loaded, even when it's not in use.</p> <p>The <cite>ke-recv</cite> and <cite>hildon-status-bar-usb</cite> code still requires some significant refactoring - they both share the same udev code, but right now this code is just duplicated amongst the two projects. The <cite>hildon-usb-gadgets</cite> repository could also see some more love - both in terms of the descriptors of the gadgets and the actual code. So if you know some C - this might be a fun project to pick up!</p> </div> <div class="section" id="nokia-n900-led-control"> <h3>Nokia N900 LED control</h3> <p>It turns out that some control over the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/186">RGB led on the N900</a> already works using mce.</p> <p>Simply running the following command:</p> <pre class="literal-block"> echo 0 &gt; /sys/class/power_supply/bq24150a-0/stat_pin_enable </pre> <p>Will disable the LED override when the N900 is being charged, and then this dbus command will show the communication LED pattern:</p> <pre class="literal-block"> dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:&quot;PatternCommunicationIM&quot; </pre> <p>This command will disable the pattern:</p> <pre class="literal-block"> dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_deactivate string:&quot;PatternCommunicationIM&quot; </pre> <p>In fact, other Maemo.org examples also work on Leste already, <a class="reference external" href="https://wiki.maemo.org/Phone_control#Make_an_.22Email_Style.22_notification_dialog">like this message dialog created using dbus and Python</a>:</p> <pre class="literal-block"> import dbus bus = dbus.SessionBus() proxy = bus.get_object('org.freedesktop.Notifications', '/org/freedesktop/Notifications') interface = dbus.Interface(proxy,dbus_interface='org.freedesktop.Notifications') interface.Notify('Notification', 0, 'control_bluetooth_paired', 'Testing 123', 'Hello World', [], {}, 0) </pre> <p>Results in:</p> <img alt="" src="/images/leste-message.png" style="width: 576px; height: 324px;" /> </div> <div class="section" id="new-kernel-and-image-for-the-a33-twister-tablet-and-the-lime2"> <h3>New kernel and image for the A33 Twister tablet and the LIME2</h3> <p>There is now a first image available for the <a class="reference external" href="https://leste.maemo.org/A33-TurboX-Twister">A33 Twister tablet</a>. The image features working usb gadget/otg, battery, charging, touchscreen and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/192">(unstable) wireless</a>. Currently, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/191">backlight is not working</a>, so the screen is not very bright, and there is no 3D acceleration yet, and also no accelerated video decoding yet.</p> <p>On the 3D front, we have managed to run the open source 3D driver on the LIME2 (which will also work for other devices with Mali GPUs), the mesa gears demo program works:</p> <img alt="" src="/images/lima-lime2.jpg" style="width: 576px; height: 324px;" /> <p>However, the driver is not yet able to run the Hildon desktop UI - the kernel hangs.</p> <p>The source code for this driver can be found here:</p> <ul class="simple"> <li><a class="reference external" href="https://gitlab.freedesktop.org/lima/mesa">https://gitlab.freedesktop.org/lima/mesa</a></li> <li><a class="reference external" href="https://gitlab.freedesktop.org/lima/linux">https://gitlab.freedesktop.org/lima/linux</a></li> </ul> <p>The lima driver is currently enabled in our LIME2 and A33 Twister tablet kernel (4.18 based):</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/lime2-linux/tree/lime2-and-twister">https://github.com/maemo-leste/lime2-linux/tree/lime2-and-twister</a></li> </ul> <p>However, the userland required to actually run any 3D demos is lacking, since it requires a newer mesa (and other supporting packages), which are not currently available in Devuan ascii.</p> <p>The LIME2 images expect a 4.3 inch touchscreen to be connected, but should also work over HDMI. <em>hildon-home</em> doesn't look so bad at 480x272px, does it?</p> <img alt="" src="/images/lime2-home.png" /> </div> <div class="section" id="porting-maemo-extras-packages"> <h3>Porting Maemo Extras packages</h3> <p>One of the advantages of being really close to Maemo Fremantle is that a lot of the existing Maemo applications require minimal work to run on Maemo Leste. Out of curiousity, we imported the wifi signal applet (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/185">issue #185</a>). The maemo.org extras page for the package is here: <a class="reference external" href="http://maemo.org/packages/view/wifi-signal-applet/">http://maemo.org/packages/view/wifi-signal-applet/</a></p> <p>With minimal changes (<a class="reference external" href="https://github.com/maemo-leste/wifi-signal-applet">https://github.com/maemo-leste/wifi-signal-applet</a>) compiled and just works:</p> <img alt="" src="/images/n900-wifi-applet.png" style="width: 576px; height: 324px;" /> <p>This package is now available in our main repository, as <em>wifi-signal-applet</em>.</p> <p>Going forward, we should probably have a separate repository (or repository component) for non-essential packages like the wifi-signal-applet. We'll have to set up in a such a way that it easy for others to also submit and build packages. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/194">Feedback is welcome in ticket #194</a></p> </div> <div class="section" id="qt5-and-gstreamer"> <h3>Qt5 and gstreamer!</h3> <p><em>freemangordon</em> has started the immense task of porting the Maemo style and widgets to Qt5, which is one of the last remaining big items for our N900 alpha image:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/qtstyleplugins">https://github.com/maemo-leste/qtstyleplugins</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/qtmaemo5">https://github.com/maemo-leste/qtmaemo5</a></li> </ul> <p>This screenshot shows Qt5 in action on Maemo Leste:</p> <img alt="" src="/images/leste-qt5-widget-1.png" style="width: 400px; height: 340px;" /> <p>In the process, he also ported several mafw components to gstreamer 1.0 and packaged them for Leste:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/?utf8=%E2%9C%93&amp;q=mafw&amp;type=&amp;language=">https://github.com/maemo-leste/?utf8=%E2%9C%93&amp;q=mafw&amp;type=&amp;language=</a></li> </ul> <p>Once these components are in place, we could even look at porting <a class="reference external" href="https://wiki.maemo.org/Open_Media_Player">Open Media Player</a> from Fremantle!</p> <p>Packages from Maemo Fremantle that rely on Qt 4.x will likely need to be ported to Qt 5 before they will run on Maemo Leste.</p> </div> </div> <div class="section" id="documentation"> <h2>Documentation</h2> <p><em>spinal84</em> has been working on adding documentation to various repositories and he has also been working on generating the required doxygen documentation for various projects:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/mce/pull/1">https://github.com/maemo-leste/mce/pull/1</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/ke-recv/pull/1">https://github.com/maemo-leste/ke-recv/pull/1</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/ke-recv-extra/pull/1">https://github.com/maemo-leste/ke-recv-extra/pull/1</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/status-area-applet-battery/pull/1">https://github.com/maemo-leste/status-area-applet-battery/pull/1</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/icd2/pull/3">https://github.com/maemo-leste/icd2/pull/3</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/clockd/pull/3">https://github.com/maemo-leste/clockd/pull/3</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/icd2/pull/8">https://github.com/maemo-leste/icd2/pull/8</a></li> </ul> </div> <div class="section" id="images"> <h2>Images</h2> <p><em>parazyd</em> has built new images for all the currently supported devices:</p> <ul class="simple"> <li>Virtual machine: <a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20181102/">https://maedevu.maemo.org/images/virtual-machines/20181102/</a></li> <li>Nokia N900: <a class="reference external" href="https://maedevu.maemo.org/images/n900/20181103/">https://maedevu.maemo.org/images/n900/20181103/</a></li> <li>Motorola Droid 4: <a class="reference external" href="https://maedevu.maemo.org/images/droid4/20181103/">https://maedevu.maemo.org/images/droid4/20181103/</a></li> <li>A33 Twister tablet: <a class="reference external" href="https://maedevu.maemo.org/images/turbox-twister/20181103/">https://maedevu.maemo.org/images/turbox-twister/20181103/</a></li> <li>Raspi 2/3: <a class="reference external" href="https://maedevu.maemo.org/images/raspi2/20181103/">https://maedevu.maemo.org/images/raspi2/20181103/</a></li> <li>N9: <a class="reference external" href="https://maedevu.maemo.org/images/n9/20181103/">https://maedevu.maemo.org/images/n9/20181103/</a></li> <li>N950: <a class="reference external" href="https://maedevu.maemo.org/images/n950/20181103/">https://maedevu.maemo.org/images/n950/20181103/</a></li> </ul> <p>We have not been able to test all of them, so please do, and let us know if something is broken!</p> <div class="section" id="open-issues"> <h3>Open issues</h3> <ul class="simple"> <li>For virtual keyboard to work, you have to reboot once after booting the fresh/new image. Then the virtual keyboard can be enabled from the settings <cite>Text Input</cite> applet.</li> <li>Several devices still lack 3D acceleration support, making the user experience particularly painful.</li> </ul> </div> </div> <div class="section" id="community"> <h2>Community</h2> <p>We're slowly but steadily moving forward and we seem to be attracting more developers - which is fantastic news. Hopefully once we reach an Alpha state for the Nokia N900, we will be able to reach out to more developers and get even more people on board.</p> <div class="section" id="openfest-2018"> <h3>OpenFest 2018</h3> <p>Three of us got together at OpenFest 2018 in Sofia, Bulgaria. We also held a presentation at OpenFest, the official videos will be made available later, but the slides for the presentation can be downloaded here: <a class="reference external" href="https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf">https://maedevu.maemo.org/media/openfest-2018-maemo-leste.pdf</a></p> <p>Someone from the community has additionally also recorded the talk (thanks for that), and you can find the recording here: <a class="reference external" href="http://talk.maemo.org/showpost.php?p=1550095&amp;postcount=152">http://talk.maemo.org/showpost.php?p=1550095&amp;postcount=152</a></p> </div> <div class="section" id="fosdem-2019"> <h3>FOSDEM 2019</h3> <p>We've submitted a proposal for a talk about Maemo Leste at FOSDEM; we hope that it will be accepted. Additionally, we've submitted a request for a stand at FOSDEM, together with the people from <a class="reference external" href="https://postmarketos.org">postmarketOS</a>!</p> </div> <div class="section" id="pinetab-pinephone"> <h3>PineTab, PinePhone?</h3> <p><a class="reference external" href="https://www.pine64.org/">Pine64</a> has announced that they are going to produce an Allwinner tablet and an Allwinner phone. They are planning to provide details before or at <a class="reference internal" href="#fosdem-2019">FOSDEM 2019</a> <a class="footnote-reference" href="#footnote-1" id="footnote-reference-1">[1]</a> <a class="footnote-reference" href="#footnote-2" id="footnote-reference-2">[2]</a>. An Allwinner phone will hopefully be quite well supported by mainline, since most of the components have drivers in mainline now - perhaps even the Lima driver will be usable on time.</p> <p>We have reached out to Pine64, and they have kindly agreed to send development kits our way!</p> <table class="docutils footnote" frame="void" id="footnote-1" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> <tr><td class="label"><a class="fn-backref" href="#footnote-reference-1">[1]</a></td><td><a class="reference external" href="https://itsfoss.com/pinebook-kde-smartphone/">https://itsfoss.com/pinebook-kde-smartphone/</a></td></tr> </tbody> </table> <table class="docutils footnote" frame="void" id="footnote-2" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> <tr><td class="label"><a class="fn-backref" href="#footnote-reference-2">[2]</a></td><td><a class="reference external" href="https://www.notebookcheck.net/Pine64-maker-of-cheap-Linux-laptops-may-be-making-a-cheap-Linux-phone.346011.0.html">https://www.notebookcheck.net/Pine64-maker-of-cheap-Linux-laptops-may-be-making-a-cheap-Linux-phone.346011.0.html</a></td></tr> </tbody> </table> </div> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>Most of our attention has been focussed on reaching the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Alpha release</a> and we're down to 4 issues before we reach the alpha milestone.</p> <p>Two issues pertain to reboot/poweroff not functioning as it should, one is for Qt5 and one for the final pieces of the virtual keyboard - monitoring the slide state of the keyboard (open or closed).</p> <div class="section" id="nexus-5"> <h3>Nexus 5?</h3> <p>Some time was also spent on working on the (upcoming!) <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/189">Nexus 5 port</a>, which isn't quite functional, as you can see:</p> <img alt="" src="/images/leste-n5-initial.jpg" style="width: 526px; height: 400px;" /> <p>There is a work in progress status page on our wiki: <a class="reference external" href="https://leste.maemo.org/Nexus_5">https://leste.maemo.org/Nexus_5</a></p> </div> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out. Another great way to get in touch is to join the <a class="reference external" href="https://leste.maemo.org/IRC_channel">IRC channel</a>.</p> <p>If you like our work and want to see it continue, join us!</p> </div> 2018-08-31T23:39:00+02:002018-08-31T23:39:00+02:00Merlijn Wajertag:maemo-leste.github.io,2018-08-31:/maemo-leste-fourth-update-july-august-2018.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-third-update-may-june-2018.html">third update</a> and there's quite some stuff to talk about!</p> <p>First of all, we now also have a <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. We hope to add a bit more structure to our development by not just relying …</p>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-third-update-may-june-2018.html">third update</a> and there's quite some stuff to talk about!</p> <p>First of all, we now also have a <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>. Be sure to subscribe for updates, questions and development. We hope to add a bit more structure to our development by not just relying on IRC, but also mailing lists, acknowledging that this is likely a more widely accepted method for coordinating development. We'll see how that pans out!</p> <div class="section" id="software-additions"> <h2>Software additions</h2> <p>The last two months were focussed mostly on wrapping on some projects and integration, we hope to close the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">N900 Alpha release milestone</a> soon.</p> <div class="section" id="virtual-keyboard"> <h3>Virtual keyboard</h3> <p>The <strong>virtual keyboard implementation is now usable</strong>, and works (almost!) out of the box on the latest Nokia N900 images. We've added the <cite>hildon-input-meta</cite> package, which, together with some files from Fremantle, makes the virtual keyboard work:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/image-builder/commit/e5f273a647098352c1ee8491cb42908ac686796f">https://github.com/maemo-leste/image-builder/commit/e5f273a647098352c1ee8491cb42908ac686796f</a></li> </ul> <p>If you want a virtual keyboard on the Nokia N900, take the latest image, boot it, then reboot it once it has fully booted. After that, go to <cite>Settings</cite>, <cite>Text Input</cite> and check the <cite>Use virtual keyboard</cite> option. In future releases, this likely will not be required, and we should able to close <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/17">issue #17</a> soon.</p> <p>The special keys virtual keyboard (the one that complements a hardware keyboard, if present) does not yet show up when the keyboard slide is open, unless this gconf key is set:</p> <pre class="literal-block"> gconftool-2 -s /system/osso/af/slide-open -t bool true </pre> <p><strong>osso-xterm</strong> now also supports the virtual keyboard, before this didn't work.</p> </div> <div class="section" id="networking"> <h3>Networking</h3> <p><strong>Wifi integration in the images is now also completed</strong>, when using the latest Nokia N900 image (or any device, really), wireless should work out of the box. See our previous update on what is supported or not, and also check out the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Wifi+Connectivity+(improvements)%22">Wifi connectivity improvements</a> milestone!</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/136">EAP PAP for TTLS is now shown by default</a></p> </div> <div class="section" id="location"> <h3>Location</h3> <p>Some work has been done exploring our options for GPS, in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/57">issue #57</a>.</p> </div> <div class="section" id="audio"> <h3>Audio</h3> <p><strong>Speakers are no longer muted by default</strong> on the Nokia N900, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/58">issue #58</a>. Additionally, and largely because of fixing this issue, status-area-applet-battery will no longer warn about low battery levels if the battery is not (yet) calibrated (and thus no longer make sad &quot;low battery&quot; sounds every minute or so).</p> </div> <div class="section" id="touch-input"> <h3>Touch input</h3> <p><strong>Support for capacitive touch devices</strong> has been improved a lot, previously some buttons and menus simply did not respond to touch events on capacitive screens, notably the hildon application menu and the controls of hildon-home.</p> <p>This has now been fixed, with changes to libmatchbox2 and hildon-desktop to support touch events:</p> <ul class="simple"> <li><a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/commit/5c18fb8583f14feab404b45853149adb502f2fcc">https://github.com/maemo-leste/libmatchbox2/commit/5c18fb8583f14feab404b45853149adb502f2fcc</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/commit/bab369db0be57bca9366fe9e1a7cde0c40fffbb5">https://github.com/maemo-leste/hildon-desktop/commit/bab369db0be57bca9366fe9e1a7cde0c40fffbb5</a></li> <li><a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/commit/180c5069e1a3ccc0e3a31c86a997ac1bdbc82d22">https://github.com/maemo-leste/hildon-desktop/commit/180c5069e1a3ccc0e3a31c86a997ac1bdbc82d22</a></li> </ul> </div> <div class="section" id="power-usage"> <h3>Power usage</h3> <p>Some initial research is being done on power usage/saving, <strong>it is reported that Maemo Leste currently uses about 90mA, versus the 10mA that Fremantle uses</strong>. We hope to bring down the power usage a lot while more hardware components get supported. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/170">issue #170</a></p> </div> </div> <div class="section" id="images"> <h2>Images</h2> <p>There are now new (pre-alpha) images available for the Nokia N900:</p> <pre class="literal-block"> https://maedevu.maemo.org/images/n900/20180831/ </pre> <div class="section" id="open-issues"> <h3>Open issues</h3> <ul> <li><p class="first">Lock screen and related functionality does not work yet. The issue here is a race condition in our startup script and X session scripts. The issue is documented in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/83">issue #83</a>, and a temporary workaround is to issue these two commands after booting:</p> <pre class="literal-block"> dbus-send --system --type=signal /com/nokia/startup/signal com.nokia.startup.signal.init_done dbus-send --system --type=signal /com/whatever com.nokia.HildonDesktop.ready </pre> </li> <li><p class="first">For virtual keyboard to work, you have to reboot once after booting the fresh/new image. Then the virtual keyboard can be enabled from the settings <cite>Text Input</cite> applet.</p> </li> </ul> </div> </div> <div class="section" id="documentation-community"> <h2>Documentation/Community</h2> <p>The amount of people actively contributing code is still only two. We need more testers and developers.</p> <p>If you're interested, please join the <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a>, check out this thread on maemo.org:</p> <blockquote> <a class="reference external" href="https://talk.maemo.org/showthread.php?t=100192&amp;page=1">https://talk.maemo.org/showthread.php?t=100192&amp;page=1</a></blockquote> <p>Additionally, more work has been done on our <a class="reference external" href="https://leste.maemo.org/">Wiki</a>, with device status tables per device, as well as some additional instructions.</p> <p>Here is an example of the current Nokia N900 page: <a class="reference external" href="https://leste.maemo.org/Nokia_N900">https://leste.maemo.org/Nokia_N900</a></p> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>The one big remaining item before we will reach the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">N900 Alpha release milestone</a> is Qt. Previously, we anticiated we would port over Qt4, but for various reasons (gstreamer 0.10 vs 1.0 support being one of them) we will instead attempt to port the Maemo Qt4 work to Qt5. This means that in the future any software using Qt4 will have to be ported to Qt5.</p> <p><a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/83">issue #83</a> causing the lockscreen not to work on boot will also need to be addressed, possibly by drastically changing our X session startup scripts.</p> <p>Once the Alpha release milestone has been reached, we will focus our attention towards the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/3">Beta release for the N900</a>, which should bring:</p> <ul class="simple"> <li>2G/3G/4G(?) data support in <cite>icd2</cite></li> <li>(Very) basic/rudimentary voice calls</li> <li>A media player</li> <li>Support for usb gadgets and general usb integration: porting <cite>hildon-status-bar-usb</cite> and <cite>ke-recv</cite></li> <li>Vibration, proximity sensor and accelerometer support</li> </ul> <p>Maybe, if we need a distraction, we will look at <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/130">Wireguard integration</a>.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Please also join our <a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste">mailing list</a> to stay up to date, ask questions and/or help out.</p> <p>If you like our work and want to see happen and continue, join us!</p> <p>We're currently on irc.libera.chat in #maemo-leste, but also hang out in #maemo. We also monitor the mailing list and github issues closely.</p> </div> 2018-05-15T00:00:00+02:002018-05-15T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2018-05-15:/maemo-leste-third-update-may-june-2018.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-second-update-april-2018.html">second update</a> and there's quite some stuff to talk about!</p> <div class="section" id="on-the-software-side"> <h2>On the software side</h2> <div class="section" id="networking"> <h3>Networking</h3> <p>This month was focussed on connectivity. A lot of progress has been made in this area. Internet Connectivity Daemon (<cite>icd</cite>) is now quite functional and works together nicely with …</p></div></div>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a while since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-second-update-april-2018.html">second update</a> and there's quite some stuff to talk about!</p> <div class="section" id="on-the-software-side"> <h2>On the software side</h2> <div class="section" id="networking"> <h3>Networking</h3> <p>This month was focussed on connectivity. A lot of progress has been made in this area. Internet Connectivity Daemon (<cite>icd</cite>) is now quite functional and works together nicely with the new <cite>libicd-network-wpasupplicant</cite> plugin which adds wireless connectivity using <cite>wpa_supplicant</cite> as a backend. The <cite>connui</cite> (which provide network settings and network UI) packages are also mostly ready, which means that we have a network daemon with wireless plugin, and working UI.</p> <p>At this point, open wireless networks, WEP networks, WPA and RSN (WPA2) PSK and EAP networks should work. Not all EAP protocols are implemented yet, but it's enough to be able to connect to well known networks like <cite>eduroam</cite> or <cite>spacenet</cite>:</p> <img alt="" src="/images/n900-libicd-wpasupplicant-spacenet.png" style="width: 576px; height: 324px;" /> <p>Further required improvements are listed here, in this milestone:</p> <blockquote> <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/7">https://github.com/maemo-leste/bugtracker/milestone/7</a></blockquote> <p>Some of these points are quite important, such as <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/137">verifying server side certificates</a>, others are more for completeness sake, like <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/145">supporting all EAP authentication mechanisms</a>.</p> <p>See section <a class="reference internal" href="#wireless-connectivity-screenshots-on-the-nokia-n900">Wireless Connectivity Screenshots on the Nokia N900</a> at the end of this update for 13 screenshots showing off some of the current wireless functionality on the Nokia N900.</p> <p>As of today, it is also possible to connect to a network directly from the normal network scanning dialog, instead of having to use the settings UI to first add a network.</p> <p><strong>IPv6</strong> is not yet implemented by us in <cite>icd2</cite>, but there is a milestone that details what should be done: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/8">https://github.com/maemo-leste/bugtracker/milestone/8</a></p> <p>In the previous April update, we have mentioned packaging <cite>wl1251-cal</cite> which should make wireless on the N900 more bearable - it does, but it somehow makes it impossible (currently) to bring up the network interface upon startup, we're still trying to figure out why this is happening.</p> </div> <div class="section" id="accessibility"> <h3>Accessibility</h3> <p>There is quite a bit of progress on accessibility! Currently Maemo Leste is really only usable if the device has a keyboard, or a working USB OTG port to attach a USB keyboard; but this will change, since we hope to have an integrated virtual keyboard soon. Localisation of the virtual keyboard layout should also work for the initial release.</p> <img alt="" src="/images/virtual-keyboard-vmware.png" style="width: 670px; height: 500px;" /> </div> <div class="section" id="devices"> <h3>Devices</h3> <p><strong>There are no new images to go along with this update, but we hope to release new ones in a few weeks from now, with the connectivity and virtual keyboard working.</strong></p> <p>On the <strong>Nokia N900</strong> side, not a lot of extra hardware enablement has been committed, but in an attempt to save some power, the kernel now supports disabling the touchscreen entirely, instead of always keeping it powered, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/118">#118</a></p> <p>On the <strong>Motorola Droid 4</strong> side:</p> <ul class="simple"> <li>The Motorola Droid 4 now properly locks/unlocks using the power key, this was fixed in mce in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/71">#71</a>.</li> <li>The Motorola Droid 4 battery applet no longer complains about an empty battery constantly: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/90">#90</a></li> </ul> <p>The Motorola Droid 4 does not yet have any GPU acceleration, but we're hoping to change that in the coming months, by adding support similar to the Nokia N900 acceleration. We're hoping to leverage previous drivers for the Pandaboard (same gpu, same OMAP soc) in combination with this DRI3 driver: <a class="reference external" href="https://github.com/TexasInstruments/dri3wsegl">https://github.com/TexasInstruments/dri3wsegl</a> There is some documentation on the wiki: <a class="reference external" href="https://leste.maemo.org/Motorola_Droid_4/PowerVR">https://leste.maemo.org/Motorola_Droid_4/PowerVR</a></p> <p>The Motorola Droid 4 will also likely be used to do our first phone call (and other modem) tests, since support for phone calls on the droid seems to be furthest along.</p> <p>Finally, a user tried our Droid 4 image on a very similar device: the Droid Bionic (thinking he had actually gotten a Droid 4), and it actually seemed to work:</p> <blockquote> <ul class="simple"> <li><a class="reference external" href="https://talk.maemo.org/showpost.php?p=1544793&amp;postcount=102">https://talk.maemo.org/showpost.php?p=1544793&amp;postcount=102</a></li> <li><a class="reference external" href="https://talk.maemo.org/showpost.php?p=1544823&amp;postcount=105">https://talk.maemo.org/showpost.php?p=1544823&amp;postcount=105</a></li> </ul> </blockquote> <p><strong>Support for a tablet</strong>: our device list has long mentioned an Allwinner A33 tablet, but nothing else was published/known, that changes now with this device page on our wiki: <a class="reference external" href="https://leste.maemo.org/A33-TurboX-Twister">https://leste.maemo.org/A33-TurboX-Twister</a></p> <p>There are no tablet images available yet, and for the different Allwinner tablets we might need to make different images (or more complicated images that support multiple devices), but it's nice to see the software work on a tablet as well!</p> <img alt="" src="/images/a33-twister-prealpha.jpg" style="width: 430px; height: 243px;" /> </div> </div> <div class="section" id="documentation-community"> <h2>Documentation/Community</h2> <p>The amount of people actively working on the project has increased slightly, but the amount of people writing code has been steady since the start. We hope that more people will get involved. There is a semi lengthy thread at talk.maemo.org:</p> <blockquote> <a class="reference external" href="https://talk.maemo.org/showthread.php?t=100192&amp;page=1">https://talk.maemo.org/showthread.php?t=100192&amp;page=1</a></blockquote> <p>And we now are actively working on wiki:</p> <blockquote> <a class="reference external" href="https://leste.maemo.org">https://leste.maemo.org</a></blockquote> <p>The device pages from maemo-leste.github.io are now migrated to the wiki:</p> <blockquote> <a class="reference external" href="https://leste.maemo.org/Category:Device">https://leste.maemo.org/Category:Device</a></blockquote> <p>Next we'll been trying to document the current state of Maemo Leste in a more clear manner, and we'll try to clearly document what could (easily) be picked up by new developers. Any help here is also required - so if anything is unclear, please join us in IRC or on the talk.maemo.org thread and ask away!</p> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>We are making steady progress towards the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Nokia N900 alpha release</a>. Most of the work done for this milestone also directly benefits other devices, but we are trying to get at least one device properly supported quickly.</p> <p>In the coming weeks, we are going to try to:</p> <ul class="simple"> <li>Document more about the current state of the project and how people can help out;</li> <li>Stabilise the wireless plugin;</li> <li>Finish the virtual keyboard;</li> <li>Get new pre-alpha images for developers ready</li> </ul> <p>After that, one of the developers will briefly look at supporting the Nexus 5, because it is a device that is pretty decently supported by mainline, has 3D acceleration and there is some progress on calls using the modem as well.</p> <p>After this is done, there are several things that would make sense to focus on:</p> <ul class="simple"> <li>2G/3G/4G ofono plugin for icd2, creating a UI for 2G, 3G and 4G connectivity for devices with a supported modem;</li> <li>Provide a port of Qt4 so that many other applications can be built;</li> <li>Look into phone calls with (one of) the Nokia N900, Droid 4 and Nexus 5;</li> <li>Finishing the USB slave/OTG support widgets and daemons <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/107">#107</a>;</li> <li>Look at solving some of the parallel boot issues <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/83">#83</a>; when enabling OpenRC parallel boot, these issues actually go away, but for some reason the Nokia N900 specifically doesn't work with parallel boot yet.</li> </ul> <p>All in all, we're marching ahead and hopefully will be able to reach the <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Nokia N900 alpha release milestone</a>.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>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.</p> <p>We're currently on irc.libera.chat in #maemo-leste, but also hang out in #maemo. We also monitor the github issues closely.</p> </div> <div class="section" id="wireless-connectivity-screenshots-on-the-nokia-n900"> <h2>Wireless Connectivity Screenshots on the Nokia N900</h2> <img alt="" src="/images/n900-net-1.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-2.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-3.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-4.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-5.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-6.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-7.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-8.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-9.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-10.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-11.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-12.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-net-13.png" style="width: 576px; height: 324px;" /> </div> 2018-04-25T00:00:00+02:002018-04-25T00:00:00+02:00Merlijn Wajertag:maemo-leste.github.io,2018-04-25:/maemo-leste-second-update-april-2018.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been over a month since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-first-update-march-2018.html">first update</a> and there's quite some stuff to talk about!</p> <div class="section" id="on-the-software-side"> <h2>On the software side</h2> <ul> <li><p class="first">We now also have a <a class="reference external" href="https://leste.maemo.org">Wiki</a> - which is not particularly impressive yet, but the device pages will be moved over shortly.</p> </li> <li><p class="first">We have added images for a new device …</p></li></ul></div>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been over a month since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-first-update-march-2018.html">first update</a> and there's quite some stuff to talk about!</p> <div class="section" id="on-the-software-side"> <h2>On the software side</h2> <ul> <li><p class="first">We now also have a <a class="reference external" href="https://leste.maemo.org">Wiki</a> - which is not particularly impressive yet, but the device pages will be moved over shortly.</p> </li> <li><p class="first">We have added images for a new device with decent mainline support - the <a class="reference external" href="https://maemo-leste.github.io/pages/raspberry-pi-2-3-status.html">Raspberry Pi 3</a> (Original and Raspi2 might work, but is not yet tested). On the Raspberry Pi 3 the 3D acceleration works nicely and hildon-desktop can run on a full HD screen. This makes for a nice native development platform. The image is armhf, not yet <cite>aarch64</cite> (or, <cite>arm64</cite>, if you wish). But since the Raspberry Pi 3 supports <cite>aarch64</cite>, it will make for a nice testing ground when we decide to work on <cite>aarch64</cite> support.</p> <p><a class="reference external" href="http://maedevu.maemo.org/images/raspi2/">http://maedevu.maemo.org/images/raspi2/</a></p> </li> <li><p class="first">The N950 port that <cite>wicket64</cite> is working now has an initial image out. There is also an image for the N9, but this image is as of yet untested, see also issue <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/121">#121</a>.</p> <p>The images can be found here: <a class="reference external" href="http://maedevu.maemo.org/images/n950/">http://maedevu.maemo.org/images/n950/</a> The initial announcement of the ports is on <a class="reference external" href="https://talk.maemo.org/showpost.php?p=1543077&amp;postcount=67">this talk.maemo.org thread</a></p> <img alt="" src="/images/n950-initial-port.jpg" /> </li> <li><p class="first">The N900 wireless should be improved with the latest packages, as we have packaged <cite>wl1251-cal</cite>. This will divert the <cite>ti-connectivity</cite> firmware and instead use the firmware in <cite>cal</cite> on the N900. It also makes it possible to use the mac address saved in cal. Left to implement would be using ofono to get the right regulatory settings for the region. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/102">https://github.com/maemo-leste/bugtracker/issues/102</a></p> </li> <li><p class="first"><cite>maemo-security-certman</cite> (required for connectivity) has been ported to OpenSSL 1.1.0, and <cite>maemo-security-certman-applet</cite> seems to work now. Currently the certificate store used by <cite>maemo-security-certman</cite> is not the (devuan) system one, but this will follow in due time, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/116">#116</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/117">#117</a></p> <img alt="" src="/images/certman-applet.png" style="width: 576px; height: 324px;" /> </li> <li><p class="first">Our dd-able images shipped with new <cite>ext4</cite> features that were not backwards compatible, causing issues mounting these filesystems from Maemo Fremantle, Safestrap and just plain Linux desktops. We have now reverted these incompatible features, so new images should be compatible with relatively old kernels/systems.</p> </li> <li><p class="first">The musb problems mentioned in our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-first-update-march-2018.html">first update</a> have both been merged to Linux, in Linux 4.16. We are not yet shipping Linux 4.16 for all devices as we will have to rebase some of our other patches. The fixes have additionally been backported to the Linux 4.9 and Linux 4.14 stable trees.</p> </li> <li><p class="first"><cite>hildon-usb-status-bar</cite> has not been finished up yet, the status is the same as in the March update, we hope to wrap this up in the next update.</p> </li> <li><p class="first">There are experimental SDL patches that have applied remaining maemo patches on top of the libsdl in devuan: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/18">https://github.com/maemo-leste/bugtracker/issues/18</a></p> </li> <li><p class="first">There is a wish to have usbnet enabled on otg-capable devices by default. We haven't finished this yet, it might in part depend on <cite>hildon-usb-status-bar</cite> work, but we hope to have finished this next month. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/107">https://github.com/maemo-leste/bugtracker/issues/107</a></p> </li> <li><p class="first">Audio patches for the <a class="reference external" href="https://maemo-leste.github.io/pages/droid-4-status.html">Motorola Droid 4</a> were posted to the <cite>linux-omap</cite> mailing list and several people have been trying them out, including for basic phone calls!</p> </li> <li><p class="first">On the OMAP mailing list there are also several people making good progress on making phone calls with the modem in the <a class="reference external" href="https://maemo-leste.github.io/pages/droid-4-status.html">Motorola Droid 4</a>, which is super exciting!</p> </li> <li><p class="first">Mouse cursor should now be visible if a non-touch input is used; this is useful on devices that do not (typically) have a touch screen such as the LIME2 or the Raspberry Pi 3, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/50">#50</a></p> </li> <li><p class="first">The reverse engineering process for ICd2 and connui is nearing completion, with most of the important bits now fully functional. Most importantly, <cite>icd2</cite>, <cite>connui-common</cite> and <cite>connui-internet</cite> are all packaged now.</p> <p>There's ongoing work to finish the <a class="reference external" href="https://github.com/maemo-leste/libicd-network-wpasupplicant">libicd-network-wpasupplicant module</a> for icd2, which is taking slightly longer than expected, but when finished the wifi connectivity will work properly through the hildon UI.</p> <p>Additionally, the <cite>libicd-network-dummy</cite> and <cite>libicd-network-usb</cite> modules are also available now.</p> <p>Meanwhile, enjoy a screenshot of an empty network dialog on the Raspberry pi:</p> <img alt="" src="/images/raspi-conndlg.png" style="width: 576px; height: 324px;" /> </li> <li><p class="first">Our Jenkins instance is now world-viewable - <a class="reference external" href="https://phoenix.maemo.org/">https://phoenix.maemo.org/</a></p> </li> <li><p class="first">NotKit has done some work on making maemo-leste run on de Gemini PDA with Android kernel and libhybris, and he got it to work! The result can be seen here:</p> <img alt="" src="/images/gemini-pda.jpg" style="width: 426px; height: 320px;" /> </li> <li><p class="first">This <a class="reference external" href="https://github.com/TexasInstruments/dri3wsegl">DRI3WSEGL</a> repository recently surfaced, which might make it possible to have OpenGLES accelerated 2D and 3D on <cite>omapdrmfb</cite> using the <cite>modesetting</cite> driver - this would be a great step forward, although at least on the N900, we would still require the binary PowerVR userspace driver. Nevertheless, this might also make possible PowerVR acceleration on the Droid 4 easier.</p> </li> </ul> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>Connectivity is not wrapped up, so that still remains a big goal. Once that is done, the reverse engineering efforts will likely focus on a virtual keyboard, which is another big missing piece.</p> <p>There's a good chance we'll soon patch together a newer Droid 4 kernel to test all the recent development, including phone calls. Phone calls are a big deal, and it would be great if we can soon start playing with that on the Droid 4, and later on also the N900.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>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.</p> <p>We're currently on irc.libera.chat in #maemo-leste, but also hang out in #maemo. We also monitor the github issues closely.</p> </div> 2018-03-02T12:00:00+01:002018-03-02T12:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2018-03-02:/maemo-leste-first-update-march-2018.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a month since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-standing-on-the-shoulders-of-giants.html">first post</a> and there's a lot of stuff to talk about!</p> <p>First of all, someone added us to <a class="reference external" href="https://en.wikipedia.org/wiki/Maemo#Maemo-Leste">Wikipedia</a>, cool!</p> <p>Devuan, the distribution that Maemo Leste is based on, has released a beta version of &quot;Devuan ASCII&quot; (Devuan 2.0): <a class="reference external" href="https://files.devuan.org/devuan_ascii_beta/README.txt">https://files.devuan.org …</a></p>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>It's been a month since our <a class="reference external" href="https://maemo-leste.github.io/maemo-leste-standing-on-the-shoulders-of-giants.html">first post</a> and there's a lot of stuff to talk about!</p> <p>First of all, someone added us to <a class="reference external" href="https://en.wikipedia.org/wiki/Maemo#Maemo-Leste">Wikipedia</a>, cool!</p> <p>Devuan, the distribution that Maemo Leste is based on, has released a beta version of &quot;Devuan ASCII&quot; (Devuan 2.0): <a class="reference external" href="https://files.devuan.org/devuan_ascii_beta/README.txt">https://files.devuan.org/devuan_ascii_beta/README.txt</a> Maemo Leste uses Devuan Ascii, so we're happy to see ASCII being close to a release.</p> <div class="section" id="on-the-software-side"> <h2>On the software side</h2> <p>We have imported various new packages, added new device images, and have been working on fixing and enhancing existing packages.</p> <ul> <li><p class="first">We have ported the community-ssu battery applet from <cite>hal</cite> to <cite>UPower</cite>, and it is now available as an update (via apt) and installed by default in the new images. (See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/36">#36</a>) There are still some open issues ( <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/90">#90</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/67">#67</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/68">#68</a>, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/70">#70</a>)</p> </li> <li><p class="first">The battery applet work also uncovered some kernel bugs. The first one related to the status of the battery not being correct. This bug was fixed shortly after the bug was reported, with patches in this thread: <a class="reference external" href="https://marc.info/?l=linux-pm&amp;m=151933105213158&amp;w=2">N900 battery status fixes</a>. Another issue was uncovered when the battery applet seemed to get charging events with a very long delay (60s+). The patch is currently on the mailing list, but will hopefully make its way into the kernel after it has gotten some review: <a class="reference external" href="https://marc.info/?l=linux-kernel&amp;m=151994358415447&amp;w=2">[RFC PATCH] power: supply: bq27xxx: Call power_supply_changed on status change</a>.</p> <img alt="" src="/images/n900-charging-battery-applet.png" style="width: 576px; height: 324px;" /> </li> <li><p class="first">The usb status bar has received some initial porting work from <cite>hal</cite> to <cite>udev</cite>, and now the UI will pop up when the N900 (only supported device right now) is connected to a PC. Actually changing the USB gadgets does not yet work, since we intend to switch to <cite>configfs</cite> and <cite>libusbgx</cite> instead of the deprecated gadget modes, so that we can also provide more complex gadgets in the near future, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/39">#39</a>. While porting the applet, a few kernel bugs were uncovered. The first problem was that reading the <cite>vbus</cite> status from sysfs caused kernel OOPSes. This should be fixed with this patch: <a class="reference external" href="https://marc.info/?l=linux-omap&amp;m=151977053826963&amp;w=2">[PATCH v2 1/1] usb: musb: call pm_runtime_{get,put}_sync before reading vbus registers</a>. The second issue is that sometimes the <cite>mode</cite> file in the <cite>musb-hdrc</cite> controller will return <cite>(null)</cite> rather than a sensible mode (e.g. <cite>b_idle</cite>, <cite>b_peripheral</cite>, etc). This has been reported here: <a class="reference external" href="https://marc.info/?l=linux-kernel&amp;m=151994805016878&amp;w=2">usb: musb: &quot;(null)&quot; in sysfs mode file after disabling a gadget (and at other times, system hangs)</a>. As the title suggests, at other times the device would simply reboot when switching to another gadget. So there's more work to be done in this area.</p> <img alt="" src="/images/leste-initial-usb-applet.png" style="width: 576px; height: 324px;" /> </li> <li><p class="first">The system menu and lock screen mostly works, but doesn't work directly from startup on the N900. This is likely a boot (race) condition triggered in part by the fact that <cite>hildon-desktop</cite> currently starts slowly. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/83">#83</a>, and meanwhile, enjoy screenshots of working UI:</p> <img alt="" src="/images/n900-lock-slider.png" style="width: 576px; height: 324px;" /> <img alt="" src="/images/n900-system-menu.png" style="width: 576px; height: 324px;" /> </li> <li><p class="first">To be able to quickly get some of these kernel fixes to Maemo Leste, we have git repositories with some device specific kernel patches. Now, at least for the N900, we also have a package: <cite>linux-image-n900 - Linux kernel package for Nokia N900 (4.15)</cite>. It currently already carries all of the fixes mentioned above.</p> </li> </ul> <ul class="simple"> <li>The orientation lock applet is also ported, but has yet to see any reasonable testing, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/37">#37</a>.</li> </ul> <ul> <li><p class="first">The <cite>Mode Control Entity</cite> (mce) can now control the backlight on the Droid4, and likely on almost every other device with Linux mainline support out there, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/65">#65</a>.</p> </li> <li><p class="first"><cite>mce</cite> can now read the battery status using <cite>UPower</cite>, profiting from earlier work done on the battery applet, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/87">#87</a></p> </li> <li><p class="first"><cite>ofono</cite> no longer crashes, as reported in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/61">#61</a>. We have also imported the latest ofono release, since the required version was not yet present in Debian sid (nor in Devuan).</p> </li> <li><p class="first">With some work, <cite>ofono</cite> can be used to set up a <cite>2g/3g</cite> data connection, as described in <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/61">#61</a>. It is also possible to send a text and start a phone call, using dbus. The phone call is without audio. At present, there is no integration or UI available in Maemo Leste for any of this.</p> </li> <li><p class="first"><a class="reference external" href="http://maedevu.maemo.org/images/droid4/">Motorola Droid4 images are now available</a>, but be mindful that you need to have already rooted the device and to have installed safestrap. <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/26">#26</a> We hope that someone will volunteer to extend our current device pages with installation instructions, or at least pointers to said instructions (see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/75">#75</a>).</p> </li> <li><p class="first">There are also <a class="reference external" href="http://maedevu.maemo.org/images/olimex-lime2/">LIME2 images available</a>. Like the Droid4 image, they do not yet contain any hardware acceleration. At present, the LIME2 images also require that a HDMI monitor is hooked up at boot time. (If someone tries out the images, please document your experience and consider adding to our devices pages). There is an open issue that contains the current state of the images: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/43">#43</a>.</p> </li> <li><p class="first">There are now also <cite>armel</cite> images available for the N900, but <strong>they do not yet work</strong>, so please stick to <cite>armhf</cite> images for now. See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/92">#92</a>.</p> </li> <li><p class="first">Our repositories were missing source packages for many packages, so <cite>apt-get build-dep</cite> and <cite>apt-get source</cite> often did not work. This is now resolved, see <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/84">#84</a>.</p> <p>Several people have inquired about a &quot;Scratchbox&quot; like tool. Currently, development is done on the devices themselves, or virtual machines. You can simply use the standard Debian development tools for all development and packaging, so at this point there does not seem to be a reason to develop a Scratchbox-like environment.</p> </li> <li><p class="first">A <strong>lot</strong> of work has gone into readying <cite>connui</cite> and <cite>icd2</cite> (the connectivity UI, API, daemon and plugins) for Maemo Leste. Unfortunately, it is not in a completed state yet, but it's getting quite close. More on that later on in this post.</p> </li> </ul> <p>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: <a class="reference external" href="http://maedevu.maemo.org/irc.txt">http://maedevu.maemo.org/irc.txt</a></p> </div> <div class="section" id="what-is-next"> <h2>What is next?</h2> <p>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: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/milestone/4">Alpha release milestone</a>.</p> <p>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.</p> <div class="section" id="connectivity"> <h3>Connectivity</h3> <p>The first big thing that we want to attempt to get into a working state is <cite>connui</cite>, <cite>icd2</cite> and <cite>wpa_supplicant</cite> integration for <cite>icd2</cite>. 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 <cite>connui</cite>, and then we need to write a plugin for <cite>icd2</cite> that communicates with <cite>wpa_supplicant</cite>, the de-facto wifi daemon. (See <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/73">#73</a> and <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/42">#42</a>) We will need someone to finish the <cite>icd2</cite> documentation in doxygen format: <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/28">#28</a></p> <p>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 <cite>NetworkManager</cite> or <cite>connui</cite>, and somehow hooking those up to <cite>icd2</cite>.</p> <p>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 <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/27">#27</a>.</p> </div> <div class="section" id="android-in-a-box"> <h3>Android in a box</h3> <p>The best way to run Android applications on GNU/Linux seems to be <a class="reference external" href="https://anbox.io/">Anbox</a>, which is in the process in being packaged for Debian (and Devuan): <a class="reference external" href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884797">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884797</a> We have a ticket for anbox support, <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/9">#9</a>.</p> <p>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.</p> </div> <div class="section" id="drivers-and-packaging"> <h3>Drivers and packaging</h3> <p>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 <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/43">#43</a>.</p> <p>The Droid 4 also currently has no 3D acceleration. We hope that a more lightweight version of <cite>hildon-desktop</cite> can provide some solace here <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/51">#51</a>.</p> <p>Finishing the USB gadget code is definitely a short term goal, but that depends on how fast we can get the kernel bugs resolved.</p> <p>Another thing we want to wrap up soon is importing the Maemo Qt patches ( <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/53">#53</a>), since that will allow us (and hopefully, others) to import many more packages from Maemo Fremantle. Examples of such packages are clockui (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/55">#55</a>), osso-calculator (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/54">#54</a>) and open media player (<a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/25">#25</a>).</p> <p>Packaging <cite>pulseaudio</cite> 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 <a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/62">#62</a>.</p> </div> <div class="section" id="platform-support"> <h3>Platform support</h3> <p>We might look at supporting <cite>arm64</cite> in the near future, if we have a (virtual) device that we can test our builds on.</p> </div> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>If you're interested in specifics, or helping out, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>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.</p> <p>We're currently on irc.libera.chat in #maemo-leste, but also hang out in #maemo. We also monitor the github issues closely.</p> </div> 2018-02-01T12:00:00+01:002018-02-01T12:00:00+01:00Merlijn Wajertag:maemo-leste.github.io,2018-02-01:/maemo-leste-standing-on-the-shoulders-of-giants.html

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>We are happy to announce the immediate availability of Maemo <cite>Leste</cite> (pre-alpha), a GNU+Linux distribution in spirit of <a class="reference external" href="http://maemo.org">Maemo Fremantle</a>, originally developed by <cite>Nokia</cite> for their internet tablets and phones, like the famous <cite>Nokia N900</cite>.</p> <p>Maemo <cite>Leste</cite> aims to provide a similar experience to Maemo <cite>Fremantle</cite>, but based on …</p>

<img alt="" src="/images/logo.png" style="width: 250px; height: 353px;" /> <p>We are happy to announce the immediate availability of Maemo <cite>Leste</cite> (pre-alpha), a GNU+Linux distribution in spirit of <a class="reference external" href="http://maemo.org">Maemo Fremantle</a>, originally developed by <cite>Nokia</cite> for their internet tablets and phones, like the famous <cite>Nokia N900</cite>.</p> <p>Maemo <cite>Leste</cite> aims to provide a similar experience to Maemo <cite>Fremantle</cite>, but based on a modern and free software stack. The initially targetted device is the <a class="reference external" href="https://maemo-leste.github.io/pages/n900-status.html">Nokia N900</a>, but other (currently unsupported) targets exist (<a class="reference external" href="https://maemo-leste.github.io/pages/droid-4-status.html">Motorola Droid 4</a>, <a class="reference external" href="https://maemo-leste.github.io/pages/generic-amd64-status.html">Generic AMD64</a>, <a class="reference external" href="https://maemo-leste.github.io/pages/allwinner-a20-lime2-status.html">Allwinner A20 LIME2</a>, <a class="reference external" href="https://maemo-leste.github.io/pages/allwinner-a33-tablet-status.html">Allwinner A33 Tablet</a>)</p> <p>In short, we aim to provide a free and open GNU+Linux based distribution for tablets and phones, based on proven and existing code.</p> <div class="section" id="history"> <h2>History</h2> <p>The <a class="reference external" href="https://en.wikipedia.org/wiki/Maemo">Maemo</a> operating system was originally developed by Nokia for it's line of internet tablets, such as the <a class="reference external" href="https://en.wikipedia.org/wiki/Nokia_770_Internet_Tablet">Nokia N770</a>, <a class="reference external" href="https://en.wikipedia.org/wiki/Nokia_800">Nokia N800</a>, <a class="reference external" href="https://en.wikipedia.org/wiki/Nokia_810">Nokia N810</a> and the <a class="reference external" href="https://en.wikipedia.org/wiki/Nokia_N900">Nokia N900 phone</a>. The <cite>Maemo</cite> version for the Nokia N900 was <cite>Fremantle</cite>.</p> <p>After Nokia stopped working on <cite>Maemo</cite> getting ready to transition to <cite>Meego</cite>, the community picked up maintainership of <cite>Maemo</cite>, resulting in the <a class="reference external" href="http://wiki.maemo.org/Community_SSU">Community SSU</a> effort that, to this day, provides updates for the Nokia N900.</p> <p>Additionally, the community has been working on upstreaming most of the kernel drivers for the Nokia, the current status can be seen on <a class="reference external" href="https://elinux.org/N900">elinux.org/N900</a>, resulting in the N900 probably being the best supported phone by Linux mainline.</p> <p>Maemo <cite>Leste</cite> uses a modern base (in the form of Devuan/Debian) and aims to make most of the software from Maemo <cite>Fremantle</cite> available as a repository. Maemo <cite>Fremantle</cite> was also based on Debian and uses the same package manager, making the transition a natural one.</p> </div> <div class="section" id="what-have-we-done-so-far"> <h2>What have we done so far?</h2> <p>We have set up a Jenkins instance <a class="footnote-reference" href="#footnote-1" id="footnote-reference-1">[*]</a> that is used to build any packages that we have created, ported or imported from Fremantle and the Community SSU. Currently, this Jenkins instance still builds for both jessie and stretch, but we plan to turn off the jessie builds soon. All of the imported packages are hosted on our Github project space: <a class="reference external" href="https://github.com/maemo-leste/">https://github.com/maemo-leste/</a></p> <p>We have working <a class="footnote-reference" href="#footnote-2" id="footnote-reference-2">[†]</a> 3D acceleration on the N900 on the latest <a class="reference external" href="https://github.com/maemo-leste/n9xx-linux/tree/pvr-wip">Linux kernel</a> (with minimal patches) and a <a class="reference external" href="https://github.com/maemo-leste/n9xx-xf86-video-fbdev-sgx">forward-ported X driver</a>, this does still require userspace blobs, which are packaged in the <cite>n900</cite> component of our repository.</p> <p>There is a meta package available called <cite>hildon-meta</cite> which installs most of the packages we have ported. For the <cite>Nokia N900</cite> and the <a class="reference external" href="https://maemo-leste.github.io/pages/allwinner-a20-lime2-status.html">Allwinner A20 LIME2</a>, we have images available that can be copied to a SD card. These images should boot directly to Maemo <cite>hildon-desktop</cite>.</p> <p>If you have neither of these devices, you can also install Maemo <cite>Leste</cite> in a <a class="reference external" href="https://maemo-leste.github.io/pages/generic-amd64-status.html">64 bit Intel/AMD virtual machine</a>, or try to port Maemo <cite>Leste</cite> to another device. In general, any Linux supported device that has some GPU acceleration (or software rendering with llvmpipe) should be a viable target.</p> <p>We are also gradually phasing out old and unmaintained software (some of this has already been done by the Community SSU folks). Maemo <cite>Fremantle</cite> uses the now unmaintained <cite>upstart</cite>, which has been replaced with the actively maintained <cite>OpenRC</cite>. We have also replaced <cite>hald</cite> with <cite>eudev</cite> (udev) (and related packages such as <cite>upower</cite>), and adjusted the Maemo software to deal with these.</p> <table class="docutils footnote" frame="void" id="footnote-1" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> <tr><td class="label"><a class="fn-backref" href="#footnote-reference-1">[*]</a></td><td>Our package build infrastructure glue scripts can be found at <a class="reference external" href="https://github.com/maemo-leste/jenkins-integration">https://github.com/maemo-leste/jenkins-integration</a>. Packages are (re)built on demand, depending on whether new code is pushed. Package builds have a specific workflow and versioning explained more in-depth here: &lt;url to jenkins page&gt;</td></tr> </tbody> </table> <table class="docutils footnote" frame="void" id="footnote-2" rules="none"> <colgroup><col class="label" /><col /></colgroup> <tbody valign="top"> <tr><td class="label"><a class="fn-backref" href="#footnote-reference-2">[†]</a></td><td>Albeit currently somewhat slower than we'd like, but it is usable</td></tr> </tbody> </table> </div> <div class="section" id="what-is-in-the-current-pre-alpha-release"> <h2>What is in the current pre-alpha release?</h2> <p>The current pre-alpha release should boot to hildon-desktop (the &quot;main&quot; component of the desktop environment) on the N900. It may take a few minutes due to an open issue in powervr that causes the startup in particular to be very slow. Wireless should work, once <cite>wpa_supplicant.conf</cite> entries are set; the keyboard should have sensible key mappings and the lock switch and other buttons should work. The Fremantle xterm application also works, as should the status area (with a single status applet - the 'profile' applet)</p> <p>It is possible to install all the packages in devuan/debian, but do not expect them to work smoothly; Firefox can be installed, but it is not optimised for mobile usage, and scrolling using the touchscreen will not work either.</p> <img alt="Initial bringup of hildon-desktop on the Nokia N900" src="/images/maemo-leste-ascii-h-d-n900-3.jpg" style="width: 576px; height: 324px;" /> <p>The Motorola Droid 4 and LIME2 images not yet ready, but here are some screenshots showing initial bringup of the environment anyway.</p> <img alt="Initial bringup of hildon-desktop on the Motorola Droid 4" src="/images/droid4-h-d-2.jpg" style="width: 576px; height: 324px;" /> <p>Droid 4 running <cite>hildon-desktop</cite>.</p> <img alt="Lime2 outputting a FullHD hildon-desktop to a monitor" src="/images/lime2-h-d-2.jpg" style="width: 576px; height: 324px;" /> <p>LIME2 outputting <cite>hildon-desktop</cite> to a 1920x1080 screen.</p> </div> <div class="section" id="what-are-the-next-steps"> <h2>What are the next steps?</h2> <p>We are working on porting more Maemo (Fremantle) userland towards our Leste base, in order to provide a better and more familiar interface and experience for users and developers. More status applets, connectivity (wifi, 2g/3g) UI are on their way. Most packages need some sort of porting, and others are not even open yet, and will need to be replaced or opened up. The wiki pages <a class="reference external" href="https://wiki.maemo.org/Free_Maemo">Free Maemo</a> and <a class="reference external" href="https://wiki.maemo.org/Fremantle_closed_packages">Fremantle closed packages</a> lists these various packages.</p> <p>We will also try to prepare working images for the Droid 4 and the LIME2, hopefully with some 3D acceleration.</p> <p>If you're interested in specifics, or helping our, or wish to have a specific package ported, please see our <a class="reference external" href="https://github.com/maemo-leste/bugtracker">bugtracker</a>.</p> <p>Once more bits are in place, we will start looking at 2g/3g connectivity and phone calls. Power saving options might then also be something to look at.</p> </div> <div class="section" id="interested"> <h2>Interested?</h2> <p>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.</p> <p>We're currently on irc.libera.chat in #maemo-leste, but also hang out in #maemo. We monitor the github issues closely, but also aim to find an appropriate (or set up a) mailing list.</p> </div>