URI: 
       maemoleste_github_io.atom.xml - sfeed_tests - sfeed tests and RSS and Atom files
  HTML git clone git://git.codemadness.org/sfeed_tests
   DIR Log
   DIR Files
   DIR Refs
   DIR README
   DIR LICENSE
       ---
       maemoleste_github_io.atom.xml (348680B)
       ---
            1 <?xml version="1.0" encoding="utf-8"?>
            2 <feed xmlns="http://www.w3.org/2005/Atom"><title>Maemo Leste</title><link href="https://maemo-leste.github.io/" rel="alternate"></link><link href="https://maemo-leste.github.io/feeds/all.atom.xml" rel="self"></link><id>https://maemo-leste.github.io/</id><updated>2020-06-24T18:00:00+02:00</updated><entry><title>Maemo Leste - Thirteenth Update (April) 2020</title><link href="https://maemo-leste.github.io/maemo-leste-thirteenth-update-april-2020.html" rel="alternate"></link><published>2020-06-24T18:00:00+02:00</published><updated>2020-06-24T18:00:00+02:00</updated><author><name>Merlijn Wajer</name></author><id>tag:maemo-leste.github.io,2020-06-24:/maemo-leste-thirteenth-update-april-2020.html</id><summary type="html">&lt;p&gt;It's been several weeks since our &lt;a class="reference external" href="{filename}/maemo-leste-update-february-and-march-2020.rst"&gt;last update&lt;/a&gt;, so let's start
            3 with a few highlights:&lt;/p&gt;
            4 &lt;ul class="simple"&gt;
            5 &lt;li&gt;We have improved power management on the Droid 4, and currently, under ideal
            6 conditions, the power draw is about &lt;tt class="docutils literal"&gt;60mW&lt;/tt&gt; with the modem turned on. That
            7 should last a few days on a decent battery …&lt;/li&gt;&lt;/ul&gt;</summary><content type="html">&lt;p&gt;It's been several weeks since our &lt;a class="reference external" href="{filename}/maemo-leste-update-february-and-march-2020.rst"&gt;last update&lt;/a&gt;, so let's start
            8 with a few highlights:&lt;/p&gt;
            9 &lt;ul class="simple"&gt;
           10 &lt;li&gt;We have improved power management on the Droid 4, and currently, under ideal
           11 conditions, the power draw is about &lt;tt class="docutils literal"&gt;60mW&lt;/tt&gt; with the modem turned on. That
           12 should last a few days on a decent battery&lt;/li&gt;
           13 &lt;li&gt;Various sensors and other hardware of the Motorola Droid 4 are now usable with
           14 Maemo Leste&lt;/li&gt;
           15 &lt;li&gt;A lot of kernel bugs/regressions have been chased and fixed&lt;/li&gt;
           16 &lt;li&gt;Cellular support is improving; cellular data should now work&lt;/li&gt;
           17 &lt;li&gt;Maemo Leste Extras should contain quite a few more packages now&lt;/li&gt;
           18 &lt;li&gt;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;leste-config-*&lt;/span&gt;&lt;/tt&gt; packages now exist to provide seamless configuration updates
           19 and changes, so there should be less of a need to &amp;quot;reinstall&amp;quot; on every new
           20 image release&lt;/li&gt;
           21 &lt;/ul&gt;
           22 &lt;div class="section" id="software-changes"&gt;
           23 &lt;h2&gt;Software changes&lt;/h2&gt;
           24 &lt;div class="section" id="mce"&gt;
           25 &lt;h3&gt;mce&lt;/h3&gt;
           26 &lt;p&gt;The Mode Control Entity has seen significant changes.&lt;/p&gt;
           27 &lt;p&gt;MCE will now properly blank the screen, allowing the SoC to idle, which
           28 in turn allows for significant power saving (&lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/338"&gt;see issue #338&lt;/a&gt;, &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/5"&gt;MCE PR 5&lt;/a&gt;).&lt;/p&gt;
           29 &lt;p&gt;With the newer versions, the touchscreen will also be properly disabled when the
           30 device is locked. This will prevent 'accidental' input events being sent to
           31 applications while the device is locked. MCE will also close the file
           32 descriptors of any touchscreen devices and tell X11 to disable the touchscreens
           33 to let the touchscreen driver idle properly. For more details, see &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/340"&gt;issue #340&lt;/a&gt;, &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/6"&gt;MCE PR 6&lt;/a&gt; and &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/7"&gt;MCE PR 7&lt;/a&gt;.&lt;/p&gt;
           34 &lt;p&gt;Furthermore, we've made a change to the default &lt;tt class="docutils literal"&gt;/etc/mce/mce.ini&lt;/tt&gt; configuration
           35 file to prevent accidental shutdowns on the Droid 4. We've &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/392"&gt;increased the time
           36 one has to press the power key to shutdown the device (issue #392)&lt;/a&gt;.&lt;/p&gt;
           37 &lt;p&gt;ALS (Ambient Light Sensor) support has been extended, and it now also works on the
           38 &lt;a class="reference internal" href="#motorola-droid-4"&gt;Motorola Droid 4&lt;/a&gt;. See &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/"&gt;MCE PR 8&lt;/a&gt;.&lt;/p&gt;
           39 &lt;p&gt;A module contributed by &lt;tt class="docutils literal"&gt;uvos&lt;/tt&gt; to support vibration in MCE is also expected to
           40 land in the next few days. See &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/132"&gt;issue #132&lt;/a&gt; and &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/9"&gt;MCE PR 9&lt;/a&gt;.&lt;/p&gt;
           41 &lt;p&gt;Something else to look forward to is the execution of mode-change shell scripts,
           42 to allow certain programs or scripts to be executed when a device is locked,
           43 unlocked, or enters other mce (sub)modes.&lt;/p&gt;
           44 &lt;/div&gt;
           45 &lt;div class="section" id="input-and-focus-fixes"&gt;
           46 &lt;h3&gt;Input and Focus fixes&lt;/h3&gt;
           47 &lt;p&gt;libmatchbox2 and hildon-desktop (the Maemo window manager) have had &lt;a class="reference external" href="https://bugs.maemo.org/show_bug.cgi?id=5987"&gt;long standing
           48 bugs with regards to input focus&lt;/a&gt;, which also made it
           49 &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/346"&gt;impossible to send keyboard events to vanilla Qt 5 applications&lt;/a&gt;.&lt;/p&gt;
           50 &lt;p&gt;&lt;tt class="docutils literal"&gt;freemangordon&lt;/tt&gt; and &lt;tt class="docutils literal"&gt;uvos&lt;/tt&gt; have been trying to get to the bottom of the problem.
           51 The result of that effort is that all known problematic input and focus issues
           52 are now fixed. Now xev happily receives events, es2gears responds to keyboard input
           53 events, and Qt 5 applications take input the way they are supposed to.&lt;/p&gt;
           54 &lt;p&gt;Relevant pull requests:&lt;/p&gt;
           55 &lt;ul class="simple"&gt;
           56 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/3"&gt;libmatchbox PR 3&lt;/a&gt;&lt;/li&gt;
           57 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/libmatchbox2/pull/4"&gt;libmatchbox PR 4&lt;/a&gt;&lt;/li&gt;
           58 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/hildon-desktop/pull/4"&gt;hildon-desktop PR 4&lt;/a&gt;&lt;/li&gt;
           59 &lt;/ul&gt;
           60 &lt;/div&gt;
           61 &lt;div class="section" id="qt-5-progress-is-being-made"&gt;
           62 &lt;h3&gt;Qt 5: Progress is being made&lt;/h3&gt;
           63 &lt;p&gt;The Maemo Qt 5 port is not finished yet, but has seen various improvements.
           64 Merlijn has been doing work porting the &amp;quot;Hildon Input Method&amp;quot; virtual keyboard
           65 patches to Qt 5. Due to the more clear architecture of Qt 5, our
           66 unwillingness to fork Qt 5 as a whole, and the fact that we're also porting from
           67 old &lt;tt class="docutils literal"&gt;Xlib&lt;/tt&gt; code to &lt;tt class="docutils literal"&gt;xcb&lt;/tt&gt;, the work is taking a little bit more
           68 time. On the upside, all the Maemo Qt 5 bits will hopefully available via a
           69 &lt;a class="reference external" href="https://doc.qt.io/qt-5/qpa.html"&gt;Qt 5 loadable platform module&lt;/a&gt;.&lt;/p&gt;
           70 &lt;p&gt;Apart from the virtual keyboard, there are at least two important pieces
           71 missing:&lt;/p&gt;
           72 &lt;ul class="simple"&gt;
           73 &lt;li&gt;QMenu support, to allow hildon-style menu items to show when the application
           74 title is touched/pressed&lt;/li&gt;
           75 &lt;li&gt;Hildon-style stacked windows&lt;/li&gt;
           76 &lt;/ul&gt;
           77 &lt;p&gt;We've also ported over a sample application, &lt;a class="reference external" href="https://github.com/maemo-leste-extras/countdowntimer"&gt;countdowntimer&lt;/a&gt;:&lt;/p&gt;
           78 &lt;img alt="" src="/images/countdowntimer.png" style="width: 576px; height: 324px;" /&gt;
           79 &lt;p&gt;To make it usable, we had to have the application respect desktop sizes other
           80 than the &lt;cite&gt;800x480&lt;/cite&gt; that the Nokia N900 screen supports, to prevent it from
           81 looking like this:&lt;/p&gt;
           82 &lt;img alt="" src="/images/leste-qt5-countdowntimer-0.1.png" style="width: 576px; height: 324px;" /&gt;
           83 &lt;p&gt;Countdowntimer itself also makes use of the specialised QMenu and Hildon
           84 stackable windows, but is already quite usable even without those modifications.&lt;/p&gt;
           85 &lt;p&gt;Development can be done directly on the VM, using X11 forwarding:&lt;/p&gt;
           86 &lt;img alt="" src="/images/leste-qt5-designer-x11-forward.png" style="width: 576px; height: 324px;" /&gt;
           87 &lt;p&gt;You can also use Qt Designer with the native Maemo theme, but, well...:&lt;/p&gt;
           88 &lt;img alt="" src="/images/leste-designer-lol.png" style="width: 576px; height: 324px;" /&gt;
           89 &lt;p&gt;If you plan to use Qt designer on your device, you might want to look at &lt;a class="reference internal" href="#xephyr-nested-xorg-server-on-maemo"&gt;Xephyr
           90 (Nested Xorg server) on Maemo&lt;/a&gt; instead.&lt;/p&gt;
           91 &lt;p&gt;In the next month, we hope to mostly finish the Qt 5 port. Keep in mind that many
           92 Qt 5 applications are already usable on Maemo Leste as is. This is also documented in
           93 &lt;a class="reference internal" href="#community-showcase"&gt;Community showcase&lt;/a&gt;!&lt;/p&gt;
           94 &lt;/div&gt;
           95 &lt;div class="section" id="xephyr-nested-xorg-server-on-maemo"&gt;
           96 &lt;h3&gt;Xephyr (Nested Xorg server) on Maemo&lt;/h3&gt;
           97 &lt;p&gt;Xephyr is a nested X server, which can run in a window on Maemo Leste, allowing you
           98 to run any ordinary desktop application on Maemo Leste, in a window.&lt;/p&gt;
           99 &lt;p&gt;It's especially useful for devices with physical keyboards.&lt;/p&gt;
          100 &lt;p&gt;Installing it is as simple as:&lt;/p&gt;
          101 &lt;pre class="literal-block"&gt;
          102 sudo apt install xephyr
          103 &lt;/pre&gt;
          104 &lt;p&gt;And then start it as follows:&lt;/p&gt;
          105 &lt;pre class="literal-block"&gt;
          106 Xephyr :1 &amp;amp;
          107 &lt;/pre&gt;
          108 &lt;p&gt;And launch applications inside that server like so:&lt;/p&gt;
          109 &lt;pre class="literal-block"&gt;
          110 DISPLAY=:1 dwm &amp;amp;
          111 DISPLAY=:1 xterm
          112 &lt;/pre&gt;
          113 &lt;img alt="" src="/images/xephyr-droid4.png" style="width: 576px; height: 324px;" /&gt;
          114 &lt;p&gt;Enjoy!&lt;/p&gt;
          115 &lt;/div&gt;
          116 &lt;div class="section" id="cellular-data-and-ofono-support"&gt;
          117 &lt;h3&gt;Cellular data and ofono support&lt;/h3&gt;
          118 &lt;p&gt;The &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;beowulf-devel&lt;/span&gt;&lt;/tt&gt; repository of Maemo Leste now has the
          119 &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;libicd-network-ofono&lt;/span&gt;&lt;/tt&gt; plugin for &lt;tt class="docutils literal"&gt;icd2&lt;/tt&gt; to allow for making GPRS/UMTS/LTE data
          120 connections:&lt;/p&gt;
          121 &lt;img alt="" src="/images/droid4-libicd-network-ofono.png" style="width: 576px; height: 324px;" /&gt;
          122 &lt;img alt="" src="/images/droid4-libicd-network-ofono-2.png" style="width: 576px; height: 324px;" /&gt;
          123 &lt;p&gt;This should work on all of the supported devices, as long as their ofono version
          124 (and SIM) supports data connections.&lt;/p&gt;
          125 &lt;p&gt;Additionally, there were some problems on Beowulf where user &lt;tt class="docutils literal"&gt;user&lt;/tt&gt; (the default
          126 user in Maemo) had no access to the ofono dbus interface, but this has been fixed in
          127 &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/372"&gt;issue #372&lt;/a&gt;.&lt;/p&gt;
          128 &lt;p&gt;Finally, once this work has seen a bit more testing, we will create a meta
          129 package to automatically install all the cellular packages, and all devices
          130 will automatically get the cellular support when they &lt;tt class="docutils literal"&gt;apt update &amp;amp;&amp;amp; apt
          131 upgrade&lt;/tt&gt;.&lt;/p&gt;
          132 &lt;/div&gt;
          133 &lt;div class="section" id="wireless"&gt;
          134 &lt;h3&gt;Wireless&lt;/h3&gt;
          135 &lt;p&gt;Wireless is mostly just working, although the UI still has some rough edges. In
          136 particular, sometimes connecting to a network fails if entering the password
          137 takes too long.&lt;/p&gt;
          138 &lt;p&gt;One other bug was fixed: a problem where the networks would appear in the
          139 network dialog, but would not be selectable until the next scan returned, which
          140 was really annoying. See &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/253"&gt;issue #253&lt;/a&gt; and &lt;a class="reference external" href="https://github.com/maemo-leste/connui-internet/pull/1"&gt;connui-internet PR&lt;/a&gt;.&lt;/p&gt;
          141 &lt;ul class="simple"&gt;
          142 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/374"&gt;https://github.com/maemo-leste/bugtracker/issues/374&lt;/a&gt; - two packages, also
          143 mention integration&lt;/li&gt;
          144 &lt;/ul&gt;
          145 &lt;/div&gt;
          146 &lt;div class="section" id="themes"&gt;
          147 &lt;h3&gt;Themes&lt;/h3&gt;
          148 &lt;p&gt;The retro &lt;a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-okuda"&gt;Okuda theme&lt;/a&gt; is now available:&lt;/p&gt;
          149 &lt;img alt="" src="/images/leste-okuda-desktop.png" style="width: 576px; height: 324px;" /&gt;
          150 &lt;img alt="" src="/images/leste-okuda-vkb.png" style="width: 576px; height: 324px;" /&gt;
          151 &lt;img alt="" src="/images/leste-okuda-xterm.png" style="width: 576px; height: 324px;" /&gt;
          152 &lt;p&gt;&lt;a class="reference external" href="https://github.com/maemo-leste-extras/miku-theme"&gt;Miku theme&lt;/a&gt;:&lt;/p&gt;
          153 &lt;img alt="" src="/images/leste-miku-settings.png" style="width: 576px; height: 324px;" /&gt;
          154 &lt;img alt="" src="/images/leste-miku-desktop.png" style="width: 576px; height: 324px;" /&gt;
          155 &lt;p&gt;&lt;a class="reference external" href="https://github.com/maemo-leste-extras/hildon-theme-matrix"&gt;Matrix theme&lt;/a&gt;:&lt;/p&gt;
          156 &lt;img alt="" src="/images/leste-matrix-desktop.png" style="width: 576px; height: 324px;" /&gt;
          157 &lt;img alt="" src="/images/leste-matrix-lock.png" style="width: 576px; height: 324px;" /&gt;
          158 &lt;/div&gt;
          159 &lt;div class="section" id="openrc-integration-in-debian-fixes"&gt;
          160 &lt;h3&gt;OpenRC integration in Debian fixes&lt;/h3&gt;
          161 &lt;p&gt;We've successfully submitted a patch to SysVinit upstream, which brings in better
          162 support for OpenRC and its internals to both Debian and Devuan. It has not yet
          163 propagated to Devuan, but it is expected to happen, of course. In Maemo Leste we
          164 already provide the patched version and maintain it ourselves until it is
          165 available in Devuan. The patch itself brings in proper OpenRC support in the
          166 insserv tool, which means that LSB headers aren't necessary for OpenRC
          167 initscripts and they now get installed in the default runlevel without the need
          168 for manual interference.&lt;/p&gt;
          169 &lt;p&gt;The patch was merged in &lt;tt class="docutils literal"&gt;6a65f4412a2d24d78741f49e64e1128993341e65&lt;/tt&gt;, and can be
          170 seen here:&lt;/p&gt;
          171 &lt;ul class="simple"&gt;
          172 &lt;li&gt;&lt;a class="reference external" href="http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;amp;id=6a65f4412a2d24d78741f49e64e1128993341e65"&gt;http://git.savannah.nongnu.org/cgit/sysvinit/insserv.git/commit/?h=1.22.0&amp;amp;id=6a65f4412a2d24d78741f49e64e1128993341e65&lt;/a&gt;&lt;/li&gt;
          173 &lt;/ul&gt;
          174 &lt;p&gt;If you found that some init scripts ended up in &lt;tt class="docutils literal"&gt;/etc/runlevels&lt;/tt&gt; instead of
          175 &lt;tt class="docutils literal"&gt;/etc/runlevels/default&lt;/tt&gt;, try reinstalling the affected packages; they should
          176 install fine now.&lt;/p&gt;
          177 &lt;/div&gt;
          178 &lt;div class="section" id="more-languages-added-to-virtual-keyboard-layouts"&gt;
          179 &lt;h3&gt;More languages added to virtual keyboard layouts&lt;/h3&gt;
          180 &lt;p&gt;Many more virtual keyboard layouts have been added. If you were ever in need of
          181 a Belarusian or Bulgarian keyboard layout, now is your time to &lt;tt class="docutils literal"&gt;apt update &amp;amp;&amp;amp;
          182 apt upgrade&lt;/tt&gt;.&lt;/p&gt;
          183 &lt;p&gt;See &lt;a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/2"&gt;hildon-input-method-plugins PR 2&lt;/a&gt;.&lt;/p&gt;
          184 &lt;/div&gt;
          185 &lt;div class="section" id="steps-towards-calls-and-texts"&gt;
          186 &lt;h3&gt;Steps towards calls and texts&lt;/h3&gt;
          187 &lt;p&gt;With &lt;a class="reference internal" href="#cellular-data-and-ofono-support"&gt;Cellular data and ofono support&lt;/a&gt; improving and other projects getting
          188 close to finished, it will soon be time to turn our attention to usable calls and
          189 texts on Maemo. We will use many of the same components that Maemo Fremantle
          190 uses, just in their updated forms, like the Mer project does.&lt;/p&gt;
          191 &lt;p&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390"&gt;Issue #390&lt;/a&gt; documents
          192 some of the steps we will be taking. It will look something like:&lt;/p&gt;
          193 &lt;ol class="arabic simple"&gt;
          194 &lt;li&gt;Perform further analysis on how this works in Fremantle&lt;/li&gt;
          195 &lt;li&gt;Import all the FOSS components (there are quite a number of them)&lt;/li&gt;
          196 &lt;li&gt;Figure out audio (routing and) policies&lt;/li&gt;
          197 &lt;li&gt;Reimplement the non-FOSS ones: call and sms UI are the big ones&lt;/li&gt;
          198 &lt;li&gt;Use &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;osso-abook&lt;/span&gt;&lt;/tt&gt; in the alternative call and sms UIs&lt;/li&gt;
          199 &lt;/ol&gt;
          200 &lt;ul class="simple"&gt;
          201 &lt;li&gt;towards proper telepathy integration &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390"&gt;https://github.com/maemo-leste/bugtracker/issues/390&lt;/a&gt;&lt;/li&gt;
          202 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger-plugins"&gt;https://github.com/maemo-leste/rtcom-eventlogger-plugins&lt;/a&gt;&lt;/li&gt;
          203 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/rtcom-eventlogger-ui"&gt;https://github.com/maemo-leste/rtcom-eventlogger-ui&lt;/a&gt;&lt;/li&gt;
          204 &lt;/ul&gt;
          205 &lt;p&gt;The addressbook interface is also underway and is being RE'd from the Fremantle
          206 binaries: &lt;a class="reference external" href="https://github.com/maemo-leste/osso-abook/"&gt;https://github.com/maemo-leste/osso-abook/&lt;/a&gt;&lt;/p&gt;
          207 &lt;/div&gt;
          208 &lt;div class="section" id="maemo-input-sounds"&gt;
          209 &lt;h3&gt;maemo-input-sounds&lt;/h3&gt;
          210 &lt;p&gt;To test the MCE vibration driver, work has been started on &lt;a class="reference external" href="https://github.com/maemo-leste/maemo-input-sounds/tree/wip"&gt;maemo-input-sounds&lt;/a&gt;, which uses the
          211 &lt;cite&gt;X11 Record&lt;/cite&gt; extension to monitor for touchscreen and key presses, and in
          212 reaction to those, either vibrate the device, play a sound, or even both.&lt;/p&gt;
          213 &lt;p&gt;The status can be tracked in &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/389"&gt;issue #389&lt;/a&gt;. A fully functioning
          214 &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;maemo-input-sounds&lt;/span&gt;&lt;/tt&gt; probably depends on getting the audio set up completely
          215 (see &lt;a class="reference internal" href="#next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5"&gt;Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5&lt;/a&gt;).&lt;/p&gt;
          216 &lt;/div&gt;
          217 &lt;div class="section" id="calendar-backend-and-frontend"&gt;
          218 &lt;h3&gt;Calendar backend and frontend&lt;/h3&gt;
          219 &lt;p&gt;Some more work is being done by &lt;tt class="docutils literal"&gt;buZz&lt;/tt&gt; and &lt;tt class="docutils literal"&gt;sicelo&lt;/tt&gt; to get the calendar
          220 software up and running.  The backend, &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;calendar-backend&lt;/span&gt;&lt;/tt&gt; is already building
          221 fine, but the frontend (&lt;tt class="docutils literal"&gt;qalendar&lt;/tt&gt;) is still blocking on the Qt 5 port:&lt;/p&gt;
          222 &lt;ul class="simple"&gt;
          223 &lt;li&gt;&lt;a class="reference external" href="https://github.com/buzztiaan/calendar-backend"&gt;https://github.com/buzztiaan/calendar-backend&lt;/a&gt;&lt;/li&gt;
          224 &lt;li&gt;&lt;a class="reference external" href="https://github.com/buzztiaan/libgq"&gt;https://github.com/buzztiaan/libgq&lt;/a&gt;&lt;/li&gt;
          225 &lt;li&gt;&lt;a class="reference external" href="https://github.com/buzztiaan/qalendar"&gt;https://github.com/buzztiaan/qalendar&lt;/a&gt;&lt;/li&gt;
          226 &lt;/ul&gt;
          227 &lt;p&gt;We expect this to fold in rather quickly once &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;osso-abook&lt;/span&gt;&lt;/tt&gt; is mostly ready.&lt;/p&gt;
          228 &lt;/div&gt;
          229 &lt;div class="section" id="hildon-home-fixes"&gt;
          230 &lt;h3&gt;hildon-home fixes&lt;/h3&gt;
          231 &lt;p&gt;&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;hildon-home&lt;/span&gt;&lt;/tt&gt; would frequently try to monitor non existing directories for
          232 changes, but because the directories did not exist, kept retrying the monitor
          233 calls. This resulted in significantly higher power usage. This has been fixed
          234 now, see &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/264"&gt;issue #264&lt;/a&gt;
          235 for more details.&lt;/p&gt;
          236 &lt;p&gt;Additionally, since our move to Beowulf, two plugins for &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;hildon-home&lt;/span&gt;&lt;/tt&gt; would
          237 no longer load (due to &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;hildon-home&lt;/span&gt;&lt;/tt&gt; loading them from a non-existing path),
          238 but this too has now been fixed:&lt;/p&gt;
          239 &lt;ul class="simple"&gt;
          240 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41"&gt;https://github.com/maemo-leste/hildon-home/commit/13a8a03196a33e51396ceb61ce307d9655a4ea41&lt;/a&gt;&lt;/li&gt;
          241 &lt;li&gt;&lt;a class="reference external" href="https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba"&gt;https://github.com/maemo-leste/hildon-home/commit/a505d58a6ae87cb032ec20a606d54d69f3582fba&lt;/a&gt;&lt;/li&gt;
          242 &lt;/ul&gt;
          243 &lt;/div&gt;
          244 &lt;/div&gt;
          245 &lt;div class="section" id="device-support"&gt;
          246 &lt;h2&gt;Device support&lt;/h2&gt;
          247 &lt;div class="section" id="motorola-droid-4"&gt;
          248 &lt;h3&gt;Motorola Droid 4&lt;/h3&gt;
          249 &lt;p&gt;The Motorola Droid 4 has seen a big set of improvements:&lt;/p&gt;
          250 &lt;ul class="simple"&gt;
          251 &lt;li&gt;The &lt;a class="reference internal" href="#ambient-light-sensor"&gt;Ambient Light Sensor&lt;/a&gt; is now used;&lt;/li&gt;
          252 &lt;li&gt;The &lt;a class="reference internal" href="#vibration-motor"&gt;Vibration Motor&lt;/a&gt; is now used;&lt;/li&gt;
          253 &lt;li&gt;A driver for the &lt;a class="reference internal" href="#accelerometer"&gt;Accelerometer&lt;/a&gt; is available;&lt;/li&gt;
          254 &lt;li&gt;Advanced &lt;a class="reference internal" href="#keyboard-layout"&gt;keyboard layout&lt;/a&gt;&lt;/li&gt;
          255 &lt;li&gt;Basic &lt;a class="reference internal" href="#modem-integration"&gt;modem integration&lt;/a&gt; in &lt;cite&gt;beowulf-devel&lt;/cite&gt; branches;&lt;/li&gt;
          256 &lt;li&gt;Much improved battery life through better &lt;a class="reference internal" href="#power-management"&gt;Power Management&lt;/a&gt;;&lt;/li&gt;
          257 &lt;li&gt;Latest Linux kernel&lt;/li&gt;
          258 &lt;/ul&gt;
          259 &lt;div class="section" id="ambient-light-sensor"&gt;
          260 &lt;h4&gt;Ambient Light Sensor&lt;/h4&gt;
          261 &lt;p&gt;Just like the Nokia N900, the Droid has an ambient light sensor, used to measure
          262 exactly that: ambient light levels. This can be used to adjust the screen
          263 brightness to the ambient light levels, based on the brightness profile
          264 selected. For observant users, this already worked on the Nokia N900, but now
          265 this also works on the Droid 4.&lt;/p&gt;
          266 &lt;p&gt;This should make your device more pleasant to use in darker rooms, but also
          267 outside - in direct sunlight.&lt;/p&gt;
          268 &lt;p&gt;Additionally, if the light level is low, the device is unlocked, and the
          269 keyboard is exposed, the keyboard backlight LEDs will be turned on, to allow for
          270 optimal typing in the dark. :-)&lt;/p&gt;
          271 &lt;p&gt;See &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/8/"&gt;MCE PR 8&lt;/a&gt;.&lt;/p&gt;
          272 &lt;/div&gt;
          273 &lt;div class="section" id="vibration-motor"&gt;
          274 &lt;h4&gt;Vibration Motor&lt;/h4&gt;
          275 &lt;p&gt;Once &lt;a class="reference external" href="https://github.com/maemo-leste/mce/pull/9"&gt;MCE PR 9&lt;/a&gt; is merged, the vibration motor on the Motorola Droid 4 (and actually also the Nokia
          276 N900 and other devices that support the Linux &lt;a class="reference external" href="https://www.kernel.org/doc/html/latest/input/ff.html"&gt;FF&lt;/a&gt; interface) will work.
          277 This allows for vibration of the device to provide touchscreen haptic feedback to the user,
          278 but also when (in the near future) an SMS is received, or
          279 the device receives a phone call.&lt;/p&gt;
          280 &lt;p&gt;See also these notes on Maemo.org &lt;a class="reference external" href="https://wiki.maemo.org/Phone_control#Start_Vibrating_Incoming_Call"&gt;on how to start and stop vibrations&lt;/a&gt;. Since we
          281 are compatible at least on the DBUS level, the original Maemo instructions just
          282 apply. It is also possible to add more patterns by editing &lt;tt class="docutils literal"&gt;/etc/mce/mce.ini&lt;/tt&gt;.&lt;/p&gt;
          283 &lt;/div&gt;
          284 &lt;div class="section" id="accelerometer"&gt;
          285 &lt;h4&gt;Accelerometer&lt;/h4&gt;
          286 &lt;p&gt;The accelerometer driver is now enabled, meaning that things like the
          287 &lt;a class="reference external" href="https://github.com/buzztiaan/droidsaber"&gt;droidsaber&lt;/a&gt; are now possible:&lt;/p&gt;
          288 &lt;iframe width="560" height="315" src="https://www.youtube.com/embed/DeCtO8WwaTc"
          289  ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope;
          290 picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;&lt;p&gt;This will also be useful for automatically changing the screen orientation, based
          291 on the device orientation. The powervr driver might need a bit more work before
          292 that will work smoothly and well though.&lt;/p&gt;
          293 &lt;/div&gt;
          294 &lt;div class="section" id="power-management"&gt;
          295 &lt;h4&gt;Power Management&lt;/h4&gt;
          296 &lt;p&gt;The power management on the Droid 4 should be in much better shape now. Under
          297 ideal circumstances, with the modem online, the device should idle at about
          298 &lt;tt class="docutils literal"&gt;60mW&lt;/tt&gt;. This is made possible by the incredible Linux kernel support, &lt;a class="reference external" href="https://github.com/maemo-leste/droid4-pm"&gt;droid4-pm&lt;/a&gt;, our various &lt;a class="reference internal" href="#mce"&gt;mce&lt;/a&gt; improvements,
          299 and in general OMAP being well designed when it comes to power management. This
          300 should last most batteries for several days. Things might improve a little more
          301 if OMAP &lt;tt class="docutils literal"&gt;OFF&lt;/tt&gt; mode ever starts to work on OMAP 4.&lt;/p&gt;
          302 &lt;p&gt;&lt;tt class="docutils literal"&gt;Merlijn&lt;/tt&gt; recently acquired a few lab power supplies, and (&lt;a class="reference external" href="https://sourceforge.net/p/sigrok/mailman/message/37014835/"&gt;after actually making it
          303 work with sigrok, working around insanely stupid firmware bugs&lt;/a&gt;) was able to
          304 generate the following graph of power usage from a clean power-up, showing the
          305 ~3 minutes it takes to fully boot and enter the promised &lt;tt class="docutils literal"&gt;60mW&lt;/tt&gt; idle power
          306 usage:&lt;/p&gt;
          307 &lt;img alt="" src="/images/droid4-boot.png" style="width: 700px; height: 350px;" /&gt;
          308 &lt;p&gt;Here's what using the vibration motor does to the power draw:&lt;/p&gt;
          309 &lt;img alt="" src="/images/droid4-rumble.png" style="width: 576px; height: 324px;" /&gt;
          310 &lt;p&gt;And the same for receiving an SMS (exposing a problem where the modem doesn't
          311 properly idle after sms receive - it stays around &lt;tt class="docutils literal"&gt;180mW&lt;/tt&gt; as opposed to the
          312 &lt;tt class="docutils literal"&gt;60mW&lt;/tt&gt; - this is still being investigated, but it looks like the USB doesn't
          313 idle afterwards, requiring to be manually kicked into idle mode):&lt;/p&gt;
          314 &lt;img alt="" src="/images/droid4-modem-power-recv-sms.png" style="width: 576px; height: 324px;" /&gt;
          315 &lt;/div&gt;
          316 &lt;div class="section" id="ntpd-and-power-management"&gt;
          317 &lt;h4&gt;NTPD and power management&lt;/h4&gt;
          318 &lt;p&gt;The &lt;tt class="docutils literal"&gt;ntp&lt;/tt&gt; daemon currently causes a lot of wake ups, and negatively impacts
          319 battery life. The current stop-gap is to stop it manually after booting, by
          320 issuing the following as root:&lt;/p&gt;
          321 &lt;pre class="literal-block"&gt;
          322 /etc/init.d/ntp stop
          323 &lt;/pre&gt;
          324 &lt;/div&gt;
          325 &lt;div class="section" id="cellular-and-power-management"&gt;
          326 &lt;h4&gt;Cellular and power management&lt;/h4&gt;
          327 &lt;p&gt;While the modem itself should idle pretty well, the modem reports on the signal
          328 strength very frequently, waking up the device even when the signal strength
          329 should not be shown. The signal strength can be temporarily disabled like so:&lt;/p&gt;
          330 &lt;pre class="literal-block"&gt;
          331 printf 'U1234AT+SCRN=0\r' &amp;gt; /dev/gsmtty1
          332 &lt;/pre&gt;
          333 &lt;/div&gt;
          334 &lt;div class="section" id="graphing-power-logs-from-the-device"&gt;
          335 &lt;h4&gt;Graphing power logs from the device&lt;/h4&gt;
          336 &lt;p&gt;The GNOME Power Manager can plot upower data, and it runs on Leste:&lt;/p&gt;
          337 &lt;img alt="" src="/images/leste-droid4-gnome-power-manager.png" style="width: 576px; height: 324px;" /&gt;
          338 &lt;p&gt;But the upower data is located in &lt;tt class="docutils literal"&gt;/var/lib/upower&lt;/tt&gt; and not at all hard to plot
          339 yourself, which might actually be more insightful (although this graph is very
          340 basic):&lt;/p&gt;
          341 &lt;img alt="" src="/images/capacity_over_time_from_upower.png" style="width: 576px; height: 324px;" /&gt;
          342 &lt;p&gt;We're still figuring out how to properly plot all this data, but more
          343 information (including the source to generate the above graph) can be found in
          344 &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/396"&gt;issue #396&lt;/a&gt;.&lt;/p&gt;
          345 &lt;p&gt;Maybe we can take &lt;a class="reference external" href="http://maemo.org/downloads/search/application.html?org_openpsa_products_search%5B1%5D%5Bproperty%5D=title&amp;amp;org_openpsa_products_search%5B1%5D%5Bconstraint%5D=LIKE&amp;amp;org_openpsa_products_search%5B1%5D%5Bvalue%5D=battery&amp;amp;org_openpsa_products_search%5B2%5D%5Bproperty%5D=os&amp;amp;org_openpsa_products_search%5B2%5D%5Bconstraint%5D=LIKE&amp;amp;org_openpsa_products_search%5B2%5D%5Bvalue%5D=Maemo5&amp;amp;fetch=Search"&gt;one of these maemo.org applications&lt;/a&gt; and port them.&lt;/p&gt;
          346 &lt;/div&gt;
          347 &lt;div class="section" id="battery-calibration"&gt;
          348 &lt;h4&gt;Battery calibration&lt;/h4&gt;
          349 &lt;p&gt;&lt;tt class="docutils literal"&gt;uvos&lt;/tt&gt; has written an init script and tool to store the battery capacity when
          350 known, and restore it, using &lt;tt class="docutils literal"&gt;spinal84&lt;/tt&gt;'s experimental kernel patches, see
          351 &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/374"&gt;issue #374&lt;/a&gt;.&lt;/p&gt;
          352 &lt;p&gt;It will be added to the Droid 4 meta package imminently, and then eventually
          353 everyone should have a calibrated battery, hopefully.&lt;/p&gt;
          354 &lt;p&gt;Also see &lt;a class="reference external" href="https://github.com/maemo-leste/upower/pull/4"&gt;upower PR 4&lt;/a&gt; for the
          355 UPower fix that was required for this to work properly.&lt;/p&gt;
          356 &lt;/div&gt;
          357 &lt;div class="section" id="keyboard-layout"&gt;
          358 &lt;h4&gt;Keyboard layout&lt;/h4&gt;
          359 &lt;p&gt;For a long time, it was not possible to &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/347"&gt;summon the special keys virtual keyboard
          360 on the Droid 4&lt;/a&gt;, which
          361 was particularly annoying since some &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/122"&gt;important keys were not available&lt;/a&gt;.&lt;/p&gt;
          362 &lt;p&gt;By digging through the N900 keyboard files and learning a bunch about xkb, both
          363 of these issues have now been resolved by &lt;tt class="docutils literal"&gt;Merlijn&lt;/tt&gt;. &lt;tt class="docutils literal"&gt;buZz&lt;/tt&gt; provided a nice
          364 &lt;a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/99343d77464299cdf1d56e461018bd7f974cee42"&gt;geometry file&lt;/a&gt;, which allows us to visualise the keys on various keyboard levels:&lt;/p&gt;
          365 &lt;img alt="" src="/images/droid4-keyboard.png" style="width: 576px; height: 224px;" /&gt;
          366 &lt;p&gt;(Yes, the shift button on the Droid 4 is mapped to control, and the caps lock
          367 key is mapped to shift)&lt;/p&gt;
          368 &lt;p&gt;Additional extra keys are also available when using the &lt;tt class="docutils literal"&gt;ISO_Level3_Shift&lt;/tt&gt;
          369 key, &lt;a class="reference external" href="https://github.com/maemo-leste/xkb-data/commit/ccebc5ea6cc9c14c7822b53317640c8f2f6372b2#diff-5b7bd0a2cb0498ff38e4e466546d5fdcR36"&gt;see the actual xkb file for more details&lt;/a&gt; and this image for a quick reference:&lt;/p&gt;
          370 &lt;img alt="" src="/images/droid4-keyboard-2.png" style="width: 576px; height: 224px;" /&gt;
          371 &lt;p&gt;Compare that to the N900 layout:&lt;/p&gt;
          372 &lt;img alt="" src="/images/n900-keyboard.png" style="width: 576px; height: 224px;" /&gt;
          373 &lt;p&gt;Bringing up the special keys virtual keyboard is done by pressing the &amp;quot;OK&amp;quot;
          374 (&lt;tt class="docutils literal"&gt;ISO_Level3_Shift&lt;/tt&gt;) key and the Control (&lt;tt class="docutils literal"&gt;Shift&lt;/tt&gt;) key.&lt;/p&gt;
          375 &lt;p&gt;And finally, the virtual keyboard didn't look quite good on the Droid 4, since
          376 it has a larger resolution, but as of &lt;a class="reference external" href="https://github.com/maemo-leste/hildon-input-method-plugins/pull/3"&gt;hildon-input-method-plugins PR 3&lt;/a&gt;, the
          377 keyboard will render properly regardless of the screen dimensions:&lt;/p&gt;
          378 &lt;img alt="" src="/images/droid4-special-vkb.png" style="width: 576px; height: 324px;" /&gt;
          379 &lt;/div&gt;
          380 &lt;div class="section" id="modem-integration"&gt;
          381 &lt;h4&gt;Modem integration&lt;/h4&gt;
          382 &lt;p&gt;&lt;tt class="docutils literal"&gt;tmlind&lt;/tt&gt; and &lt;tt class="docutils literal"&gt;Pavel Machek&lt;/tt&gt; have been doing a lot of work on improving ofono
          383 on the Droid 4. The result of most of that work is currently packaged in the
          384 &lt;tt class="docutils literal"&gt;droid4&lt;/tt&gt; component, so any droid 4 will automatically get the latest/best
          385 ofono version. Additionally, the technology is now also reported properly:&lt;/p&gt;
          386 &lt;img alt="" src="/images/droid4-tech.png" style="width: 576px; height: 324px;" /&gt;
          387 &lt;img alt="" src="/images/droid4-tech-2g.png" style="width: 576px; height: 324px;" /&gt;
          388 &lt;p&gt;More work remains, including upstreaming ofono and dealing with some power
          389 management regressions, but it's starting to look quite good indeed.&lt;/p&gt;
          390 &lt;p&gt;Current work can be found here:
          391 &lt;a class="reference external" href="https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm"&gt;https://github.com/maemo-leste/ofono-d4/tree/motmdm-serdev-ngsm&lt;/a&gt;&lt;/p&gt;
          392 &lt;/div&gt;
          393 &lt;div class="section" id="increasing-font-size-in-osso-xterm"&gt;
          394 &lt;h4&gt;increasing font size in osso-xterm&lt;/h4&gt;
          395 &lt;p&gt;On the Nokia N900, the font size in osso-xterm can be changed using the volume
          396 buttons, but this does not work yet on the Droid 4. The reason is that
          397 osso-xterm expects specific (hardcoded) keys to be used to change the font, and
          398 the Droid 4 has different keys mapped to its volume buttons, see &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/385"&gt;issue #385&lt;/a&gt;&lt;/p&gt;
          399 &lt;/div&gt;
          400 &lt;div class="section" id="latest-linux-kernel"&gt;
          401 &lt;h4&gt;Latest Linux kernel&lt;/h4&gt;
          402 &lt;p&gt;A month or so ago we switched to Linux 5.7:
          403 &lt;a class="reference external" href="https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7"&gt;https://github.com/maemo-leste/droid4-linux/tree/droid4-pending-v5.7&lt;/a&gt;&lt;/p&gt;
          404 &lt;p&gt;After that, there were various regressions to figure out, the most painful ones
          405 being random resets, which took quite a while to pin down. &lt;tt class="docutils literal"&gt;tmlind&lt;/tt&gt; has been
          406 incredibly helpful in getting these problems resolved. Onto the next Linux
          407 version and set of regressions - and bugfixes, and features...&lt;/p&gt;
          408 &lt;/div&gt;
          409 &lt;/div&gt;
          410 &lt;div class="section" id="nokia-n900"&gt;
          411 &lt;h3&gt;Nokia N900&lt;/h3&gt;
          412 &lt;div class="section" id="powermanagement-update"&gt;
          413 &lt;h4&gt;Powermanagement update&lt;/h4&gt;
          414 &lt;p&gt;A while ago we tweeted out a photo of a Nokia N900 using very little power,
          415 while in &lt;tt class="docutils literal"&gt;OMAP OFF&lt;/tt&gt; mode. We haven't yet brought this to our latest images,
          416 but it's still planned (it might be relatively simple, but also might be a lot
          417 of work). In addition, we will likely provide an &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;n900-pm&lt;/span&gt;&lt;/tt&gt; script, similar to
          418 the &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;droid4-pm&lt;/span&gt;&lt;/tt&gt; script.&lt;/p&gt;
          419 &lt;/div&gt;
          420 &lt;/div&gt;
          421 &lt;div class="section" id="pinephone"&gt;
          422 &lt;h3&gt;Pinephone&lt;/h3&gt;
          423 &lt;p&gt;Thanks to the packaging work from people in postmarketOS, we now also support
          424 the modem in the Pinephone. While we've mostly been working with cellular things
          425 on the Droid4, lots of that work can simply be reused on the Pinephone, and we
          426 plan to do so in the near future. A package called &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;pinephone-modem-config&lt;/span&gt;&lt;/tt&gt;
          427 can be installed, and along with updating the kernel (latest available version
          428 is 5.6), it will bring in modem support. This is already automatically enabled
          429 in the latest images. A note to keep in mind: While the modem is off, combined
          430 with the latest kernels, the system outputs KEY_WAKEUP events which cause some
          431 trouble with the virtual keyboard. The current solution to this is to just have
          432 &lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;pinephone-modem-config&lt;/span&gt;&lt;/tt&gt; installed and after a reboot, things should be ok.
          433 We will see if it's possible to patch this in some proper way in the future.&lt;/p&gt;
          434 &lt;/div&gt;
          435 &lt;/div&gt;
          436 &lt;div class="section" id="weekly-builds"&gt;
          437 &lt;h2&gt;Weekly builds&lt;/h2&gt;
          438 &lt;p&gt;From July, we will also implement and enable weekly image builds on our CI
          439 infrastructure. This means we won't be building images on demand anymore.
          440 Instead they shall be built each week, containing all the latest packages and
          441 goodies. Obviously, this will require more storage space, so we will be
          442 removing device images older than five weeks.&lt;/p&gt;
          443 &lt;p&gt;Hopefully this will also help us polish up our build frameworks and alert us
          444 about possible bugs that arise during development. It is also a very important
          445 step towards reproducible builds - which is one of our milestones we wish to
          446 fulfill.&lt;/p&gt;
          447 &lt;p&gt;However, for this occasion, we built new images and they can be downloaded as
          448 usual. This time we've also built 64bit images for the Raspberry Pi 3 and 4.&lt;/p&gt;
          449 &lt;ul class="simple"&gt;
          450 &lt;li&gt;64bit VM: &lt;a class="reference external" href="https://maedevu.maemo.org/images/virtual-machines/20200622/"&gt;https://maedevu.maemo.org/images/virtual-machines/20200622/&lt;/a&gt;&lt;/li&gt;
          451 &lt;li&gt;N900: &lt;a class="reference external" href="https://maedevu.maemo.org/images/n900/20200623/"&gt;https://maedevu.maemo.org/images/n900/20200623/&lt;/a&gt;&lt;/li&gt;
          452 &lt;li&gt;Droid4: &lt;a class="reference external" href="https://maedevu.maemo.org/images/droid4/20200624/"&gt;https://maedevu.maemo.org/images/droid4/20200624/&lt;/a&gt;&lt;/li&gt;
          453 &lt;li&gt;Pinephone: &lt;a class="reference external" href="https://maedevu.maemo.org/images/pinephone/20200624/"&gt;https://maedevu.maemo.org/images/pinephone/20200624/&lt;/a&gt;&lt;/li&gt;
          454 &lt;li&gt;Pinetab: &lt;a class="reference external" href="https://maedevu.maemo.org/images/pinetab/20200624/"&gt;https://maedevu.maemo.org/images/pinetab/20200624/&lt;/a&gt;&lt;/li&gt;
          455 &lt;li&gt;Pi3: &lt;a class="reference external" href="https://maedevu.maemo.org/images/raspi3-64bit/20200623/"&gt;https://maedevu.maemo.org/images/raspi3-64bit/20200623/&lt;/a&gt;&lt;/li&gt;
          456 &lt;li&gt;Pi4: &lt;a class="reference external" href="https://maedevu.maemo.org/images/raspi4-64bit/20200623/"&gt;https://maedevu.maemo.org/images/raspi4-64bit/20200623/&lt;/a&gt;&lt;/li&gt;
          457 &lt;/ul&gt;
          458 &lt;/div&gt;
          459 &lt;div class="section" id="community-showcase"&gt;
          460 &lt;h2&gt;Community showcase&lt;/h2&gt;
          461 &lt;div class="section" id="ps-1-emulator"&gt;
          462 &lt;h3&gt;PS 1 emulator&lt;/h3&gt;
          463 &lt;p&gt;PCSX-ReARMed runs quite nicely on the Droid 4:&lt;/p&gt;
          464 &lt;iframe width="560" height="315" src="https://www.youtube.com/embed/BmIAQby4ccM"
          465  ;rameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope;
          466 picture-in-picture" allowfullscreen&gt;&lt;/iframe&gt;&lt;p&gt;Unfortunately, the community hasn't yet packaged the program for Maemo Leste
          467 Extras, but we're confident someone will, at some point.&lt;/p&gt;
          468 &lt;/div&gt;
          469 &lt;div class="section" id="photo-light-meter"&gt;
          470 &lt;h3&gt;Photo Light meter&lt;/h3&gt;
          471 &lt;p&gt;Written in Free Pascal, photolightmeter can be used calculate aperture and
          472 shutter values.&lt;/p&gt;
          473 &lt;/div&gt;
          474 &lt;div class="section" id="telegram"&gt;
          475 &lt;h3&gt;Telegram&lt;/h3&gt;
          476 &lt;p&gt;If you're a fan of Telegram, the desktop client just works on Maemo Leste:&lt;/p&gt;
          477 &lt;ul class="simple"&gt;
          478 &lt;li&gt;&lt;a class="reference external" href="https://twitter.com/rfc1087/status/1271796014903635969"&gt;https://twitter.com/rfc1087/status/1271796014903635969&lt;/a&gt;&lt;/li&gt;
          479 &lt;/ul&gt;
          480 &lt;/div&gt;
          481 &lt;div class="section" id="proxmark3"&gt;
          482 &lt;h3&gt;Proxmark3&lt;/h3&gt;
          483 &lt;p&gt;If you like toying with RFID cards, then you can (for example) use the bluetooth
          484 module on the Droid 4 to connect a capable reader and run proxmark3 on the Droid
          485 itself:&lt;/p&gt;
          486 &lt;img alt="" src="/images/proxmark3-1.png" style="width: 576px; height: 324px;" /&gt;
          487 &lt;img alt="" src="/images/proxmark3-2.png" style="width: 576px; height: 324px;" /&gt;
          488 &lt;p&gt;You can find specific installation notes here: &lt;a class="reference external" href="http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276"&gt;http://web.archive.org/web/20200623220049/https://paste.debian.net/plainh/34a66276&lt;/a&gt;&lt;/p&gt;
          489 &lt;/div&gt;
          490 &lt;div class="section" id="quicknote"&gt;
          491 &lt;h3&gt;Quicknote&lt;/h3&gt;
          492 &lt;p&gt;A simple notes application written in Python is also available:
          493 &lt;a class="reference external" href="https://github.com/maemo-leste-extras/quicknote"&gt;https://github.com/maemo-leste-extras/quicknote&lt;/a&gt;&lt;/p&gt;
          494 &lt;/div&gt;
          495 &lt;div class="section" id="mihphoto"&gt;
          496 &lt;h3&gt;mihphoto&lt;/h3&gt;
          497 &lt;p&gt;A Qt 5 photo viewer is available, and optionally supports multitouch when
          498 supplied as a startup argument:
          499 &lt;a class="reference external" href="https://github.com/maemo-leste-extras/mihphoto"&gt;https://github.com/maemo-leste-extras/mihphoto&lt;/a&gt;&lt;/p&gt;
          500 &lt;/div&gt;
          501 &lt;div class="section" id="personal-ip-address"&gt;
          502 &lt;h3&gt;personal-ip-address&lt;/h3&gt;
          503 &lt;p&gt;The good old personal-ip-address has returned, this time to Leste:
          504 &lt;a class="reference external" href="https://github.com/maemo-leste-extras/personal-ip-address"&gt;https://github.com/maemo-leste-extras/personal-ip-address&lt;/a&gt;&lt;/p&gt;
          505 &lt;/div&gt;
          506 &lt;/div&gt;
          507 &lt;div class="section" id="maemo-leste-extras"&gt;
          508 &lt;h2&gt;Maemo Leste Extras&lt;/h2&gt;
          509 &lt;p&gt;More community packages are being maintained in the &lt;tt class="docutils literal"&gt;extras&lt;/tt&gt; repository and
          510 we're very glad and excited about it. If you're interested in maintaing your own
          511 community package for Maemo Leste, there are instructions for you to do so on
          512 the &lt;a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker"&gt;bugtracker&lt;/a&gt; .&lt;/p&gt;
          513 &lt;/div&gt;
          514 &lt;div class="section" id="next-up-audio-routing-pulseaudio-contacts-calls-sms-qt-5"&gt;
          515 &lt;h2&gt;Next up: Audio routing/Pulseaudio, Contacts, Calls/SMS, Qt 5&lt;/h2&gt;
          516 &lt;p&gt;So what can you expect from future updates?&lt;/p&gt;
          517 &lt;p&gt;The big things on our radar are still:&lt;/p&gt;
          518 &lt;ul&gt;
          519 &lt;li&gt;&lt;p class="first"&gt;Audio: Currently most devices do not even ship with &lt;tt class="docutils literal"&gt;pulseaudio&lt;/tt&gt;, 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 &lt;a class="reference external" href="https://github.com/maemo-leste/maemo-statusmenu-volume"&gt;volume applet&lt;/a&gt;&lt;/p&gt;
          520 &lt;/li&gt;
          521 &lt;li&gt;&lt;p class="first"&gt;Contacts (&lt;tt class="docutils literal"&gt;&lt;span class="pre"&gt;osso-abook&lt;/span&gt;&lt;/tt&gt;), this will provide all of the Hildon contacts APIs
          522 with the evolution database as a abackend, definitely required for proper SMS and
          523 Call UI&lt;/p&gt;
          524 &lt;/li&gt;
          525 &lt;li&gt;&lt;p class="first"&gt;Qt 5 updates: hopefully we will soon have the virtual keyboard integration
          526 ready, with the hildon menus and stacked windows following right after. That
          527 should be enough to make most applications work, and from there on we'll
          528 probably port things on an as-needed basis: like APIs for home and status
          529 widgets&lt;/p&gt;
          530 &lt;/li&gt;
          531 &lt;li&gt;&lt;p class="first"&gt;Nokia's &lt;tt class="docutils literal"&gt;rtcom&lt;/tt&gt; packages and telepathy. &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/390"&gt;https://github.com/maemo-leste/bugtracker/issues/390&lt;/a&gt;
          532 Some of this is covered in &lt;a class="reference internal" href="#steps-towards-calls-and-texts"&gt;Steps towards calls and texts&lt;/a&gt;, but to reiterate:
          533 the plan is to use &lt;cite&gt;telepathy-ring&lt;/cite&gt; as an interface to &lt;cite&gt;ofono&lt;/cite&gt;, and use
          534 &lt;cite&gt;rtcom-eventlogger&lt;/cite&gt; and other libraries to read from and log to the same
          535 database format as used on Fremantle.
          536 This approach is particularly exciting because it allows loading many other
          537 telepathy plugins. There also exists a &lt;a class="reference external" href="https://github.com/dylex/slack-libpurple/commits/master"&gt;telepathy-haze&lt;/a&gt; plugin to load
          538 (any) Pidgin (&lt;tt class="docutils literal"&gt;libpurple&lt;/tt&gt;) plugin, allowing for potentially loading (for
          539 example) the &lt;a class="reference external" href="https://github.com/dylex/slack-libpurple"&gt;slack-libpurple&lt;/a&gt;
          540 slack plugin into telepathy, and being able to directly
          541 interface with Slack using the native hildon UI, potentially even with
          542 contacts, too. And of course, there are also SIP plugins for telepathy,
          543 allowing for VOIP calls from the same (native) UI&lt;/p&gt;
          544 &lt;/li&gt;
          545 &lt;li&gt;&lt;p class="first"&gt;Speaking of UIs, once the backend (rtcom) is mostly there, the last thing
          546 we'll have to do is to bring up the call and text UIs. The Fremantle SMS UI
          547 relied on an html rendering engine, &lt;a class="reference external" href="https://wiki.maemo.org/Conversation_Mods"&gt;allowing for cool customisations&lt;/a&gt; like these:&lt;/p&gt;
          548 &lt;img alt="" src="/images/fun-conversations-mod.png" style="width: 432px; height: 256px;" /&gt;
          549 &lt;/li&gt;
          550 &lt;/ul&gt;
          551 &lt;/div&gt;
          552 &lt;div class="section" id="web-interface-for-packages"&gt;
          553 &lt;h2&gt;Web interface for packages&lt;/h2&gt;
          554 &lt;p&gt;We're considering creating a web interface to browse the core maemo packages,
          555 the development packages and also the extras packages. See &lt;a class="reference external" href="https://github.com/maemo-leste/bugtracker/issues/395"&gt;issue #395&lt;/a&gt; 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.&lt;/p&gt;
          556 &lt;p&gt;Sneak peak of an alpha version of the interface:&lt;/p&gt;
          557 &lt;img alt="" src="/images/pkg.png" /&gt;
          558 &lt;/div&gt;
          559 &lt;div class="section" id="more-frequent-updates"&gt;
          560 &lt;h2&gt;More frequent updates?&lt;/h2&gt;
          561 &lt;p&gt;We often get the question if we can provide update posts more frequently. Often,
          562 we delay update posts because we want to &lt;strong&gt;complete just one more package...&lt;/strong&gt; -
          563 and then another, and another... So if you'd like to get more frequent update
          564 posts, please volunteer to write them for us. If you hang out in the IRC
          565 channel, maybe follow the frequent updates and write about them, and we'll be
          566 able to post it here, on our website.&lt;/p&gt;
          567 &lt;p&gt;That said, we're considering doing detailed write-ups of various core components
          568 of Maemo Leste every few weeks or so, so if that's your thing, you might be able
          569 to peek at those too, soon.&lt;/p&gt;
          570 &lt;/div&gt;
          571 &lt;div class="section" id="interested"&gt;
          572 &lt;h2&gt;Interested?&lt;/h2&gt;
          573 &lt;p&gt;If you have questions, are interested in specifics, or helping out, or wish to have a specific
          574 package ported, please see our &lt;a class="reference external" href="https://github.com/maemo-leste-extras/bugtracker"&gt;bugtracker&lt;/a&gt;&lt;/p&gt;
          575 &lt;p&gt;&lt;strong&gt;We have several Nokia N900 and Motorola Droid 4 units available to interested
          576 developers&lt;/strong&gt;, so if you are interested in helping out but have trouble acquiring
          577 a device, let us know.&lt;/p&gt;
          578 &lt;p&gt;Please also join our &lt;a class="reference external" href="https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/maemo-leste"&gt;mailing list&lt;/a&gt; to stay
          579 up to date, ask questions and/or help out. Another great way to get in touch is
          580 to join the &lt;a class="reference external" href="https://leste.maemo.org/IRC_channel"&gt;IRC channel&lt;/a&gt;.&lt;/p&gt;
          581 &lt;p&gt;If you like our work and want to see it continue, join us!&lt;/p&gt;
          582 &lt;/div&gt;
codemadness.org:70 /git/sfeed_tests/file/input/sfeed/realworld/maemoleste_github_io.atom.xml.gph:593: line too long