Maemo Leste Wiki - User contributions [en]

Propaganda

2021-07-08T15:40:46Z

Parazyd:

Propaganda

2021-07-08T15:39:00Z

Parazyd:

File:MaemoSealeste.jpg

2021-07-08T15:37:39Z

Parazyd:

Propaganda

2021-07-08T15:37:18Z

Parazyd:

Main Page

2021-06-12T09:44:24Z

Parazyd:

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Getting Started ==

See [[Getting_Started|Getting Started]]

== Frequently Asked Questions ==

See [[Leste_FAQ|FAQ]]

== Devices ==

See [[:Category:Device]] (not all are fully supported)

== Extras packages with wiki pages ==

https://leste.maemo.org/Category:Extras

== Latest Images ==

https://phoenix.maemo.org/view/Images/

== Development ==

See [[Development]]

== Roadmap ==

=== Project milestones ===
https://github.com/maemo-leste/bugtracker/milestones

=== Wishlist ===

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

== Talks ==

See [[Talks]]

== Links ==
<div>
The central point of meeting and talking is IRC (irc.libera.chat in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://freenode.irclog.whitequark.org/maemo-leste/

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Our Package index and info: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Leste FAQ

2021-05-25T05:24:05Z

Parazyd:

{{Stub}}

=== What is Maemo Leste? ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== What is mainline Linux? ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== How to translate Maemo Leste into my language? ===

We have our translation source files on Weblate, so anyone can contribute. See our [[Localization]] page for more information.

Main Page

2021-05-22T09:53:22Z

Parazyd: /* Description */

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Getting Started ==

See [[Getting_Started|Getting Started]]

== Frequently Asked Questions ==

See [[Leste_FAQ|FAQ]]

== Supported Devices ==

See [[:Category:Device]]

== Latest Images ==

https://phoenix.maemo.org/view/Images/

== Development ==

See [[Development]]

== Roadmap ==

=== Project milestones ===
https://github.com/maemo-leste/bugtracker/milestones

=== Wishlist ===

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

== Talks ==

See [[Talks]]

== Links ==
<div>
The central point of meeting and talking is IRC (irc.libera.chat in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://freenode.irclog.whitequark.org/maemo-leste/

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Our Package index: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Main Page

2021-05-22T09:00:44Z

Parazyd: /* Description */

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''irc.libera.chat''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Getting Started ==

See [[Getting_Started|Getting Started]]

== Frequently Asked Questions ==

See [[Leste_FAQ|FAQ]]

== Supported Devices ==

See [[:Category:Device]]

== Latest Images ==

https://phoenix.maemo.org/view/Images/

== Development ==

See [[Development]]

== Roadmap ==

=== Project milestones ===
https://github.com/maemo-leste/bugtracker/milestones

=== Wishlist ===

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

== Talks ==

See [[Talks]]

== Links ==
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://freenode.irclog.whitequark.org/maemo-leste/

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Our Package index: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

IRC channel

2021-05-22T09:00:23Z

Parazyd:

We are on '''irc.libera.chat''' ; channel '''#maemo-leste'''

We want everyone to feel free in our channel, but also remain productive. Therefore, while we do not 'police' the channel, it is also good etiquette to remain on-topic as far as possible.

If you use Matrix, then you can connect to the IRC channel via Libera's bridge. Simply join the room '''#libera_#maemo-leste:matrix.org'''. However, please note the following caveats when using the bridge:
* Matrix allows a message to have multiple lines (i.e. include returns). This does not look good on IRC clients. Therefore, please refrain from sending multi-line messages
* Matrix allows sending media and files within the chat, while IRC does not. On IRC, this will appear as an URL. Please do not send any media or files directly into an IRC room. Use a pastebin, and paste the URL to the item, and include a brief explanation about the link. Otherwise no one might be willing to open it

Propaganda

2021-05-11T14:04:39Z

Parazyd: Created page with "200px 200px 200px 200px 200px File:Refuse-duopo..."

File:Refuse-duopoly.jpg

2021-05-11T14:02:08Z

Parazyd:

File:Privacy-and-more.png

2021-05-11T14:01:51Z

Parazyd:

File:Join-leste.jpg

2021-05-11T14:01:34Z

Parazyd:

File:Great-war.jpg

2021-05-11T14:01:23Z

Parazyd:

File:Dont-slave.jpg

2021-05-11T14:01:13Z

Parazyd:

File:Os-addicts.jpg

2021-05-11T14:00:57Z

Parazyd:

Getting Started

2021-05-10T09:18:28Z

Parazyd: /* Expand the root partition to fill SD card */

= Installation to SD Card =

After updating device firmware with included script (eg. flash-droid-4-fw.sh):

Download an image appropriate for your device from [http://maedevu.maemo.org/images/]

Insert a microsd card into your computer and find the device with cat /proc/partitions

Decompress and write the image to your microsd card device:

xzcat maemo-leste-VERSION.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

= Expand the root partition to fill SD card =

A helpful script is included to expand the root partition to fill the microSD card.
After booting and logging in to root, execute: /etc/expandcard.sh

This will expand the root partition to fill the microSD card using resize2fs.

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Development

2021-05-07T06:19:22Z

Parazyd:

Maemo Leste development is split up in a few different places.

== Communication and organising ==

* Our https://maemo-leste.github.io website is where we post (news) updates, as well as on talk.maemo.org (see this subforum https://talk.maemo.org/forumdisplay.php?f=66 and this maemo.org thread: https://talk.maemo.org/showthread.php?t=100192)
* There is the issue tracker; for filing bugs and keeping track of issues/milestones. https://github.com/maemo-leste/bugtracker
* The day-to-day development and user chatter mostly takes place in the [[IRC channel]]
* We also have a mailing list, at [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]
* This wiki: for documenting the status of various long-running projects, status per device, etc.

== Task Summary ==

For current (semi) impactful tasks, see

[[Development/Tasks]]

== Codename ==

* Maemo Leste is currently based on Devuan Beowulf, which is based on Debian Buster.

== Guides ==

* [[Development/Porting Packages]]
* [[Development/Building Packages]]
* [[Development/Modified Software]]
* [[Development/Device Bringup]]
* https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide

== Technical ==

All our git repositories can be found here: https://github.com/maemo-leste

=== Jenkins ===

To aid development and provide "continous integration" we have a build server, which takes a git repository and builds software and packages it, and will automatically make said package end up in Maemo Leste repositories. This is done by Jenkins, and the instance can be found here: https://phoenix.maemo.org/

=== Developing on a device ===

Actual development is mostly done from within Maemo Leste itself. (For Maemo Fremantle developers, this might sound weird, but there is essentially no need for a 'scratchbox' type VM)

The current developers mostly work in a [[Virtual_Machine|Virtual Machine]] or on a [[Raspberry Pi 2|Raspberry Pi]].

=== Building a Maemo Leste image ===

See https://leste.maemo.org/Image_Builder

=== List of Programs/Daemon specific to Maemo ===

https://leste.maemo.org/Development/Daemons

=== Crossbuilding ===

Multiarch is an ability present on modern Debian systems that allows you to build native packages for different architectures. This is nice because you can build packages for an ARM based phone using the full power of your x86 based PC/Mac/Notebook or a server.

Here we show how you can easily setup a multiarch environment and build a native package for Maemo Leste running on Nokia N900. We are going to make a container (chroot) for this job. It's because we don't want to pollute our main system.

# Make a container for our development system
DIR=/var/lib/container/stretch
sudo apt-get install qemu-user-static debootstrap systemd-container &&
sudo debootstrap --arch=armhf stretch $DIR http://deb.debian.org/debian &&
echo "strech_cross" | sudo tee $DIR/etc/debian_chroot &&
sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D $DIR

# Setup build environment inside the container
cat >> ~/.bashrc << EOF &&
export PKG_CONFIG_PATH=/usr/lib/pkgconfig
export CC=arm-linux-gnueabihf-gcc
export JOBS=$(grep processor /proc/cpuinfo | wc -l)
EOF
dpkg --add-architecture armhf &&
apt-get -y install --no-install-recommends build-essential crossbuild-essential-armhf ca-certificates &&
cat >> /etc/apt/sources.list << "EOF" &&
deb http://maedevu.maemo.org/leste ascii main contrib non-free n900
deb http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900

deb-src http://deb.debian.org/debian stretch main
deb-src http://maedevu.maemo.org/leste ascii main contrib non-free n900
deb-src http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900
EOF
wget --no-check-certificate https://maedevu.maemo.org/testing-key.asc &&
apt-key add testing-key.asc &&
rm -f testing-key.asc &&
rm -f /var/cache/apt/archives/*.deb &&
apt-get update &&
exec bash

# Build Xorg for Nokia N900
apt-get source xserver-xorg-core &&
cd xorg-server-1.19.2 &&
wget https://raw.githubusercontent.com/buildroot/buildroot/88e0f214dcb7c2a99a4425a70673d2aa5f48d720/package/x11r7/xserver_xorg-server/1.20.4/0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch &&
mv -v 0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch debian/patches &&
echo -e "# crossbuild fix\n0002-configure.ac-Fix-check-for-CLOCK_MONOTONIC.patch" >> debian/patches/series &&
apt-get -y build-dep -a armhf . &&
time dpkg-buildpackage -aarmhf -j$JOBS -b &&
echo OK || echo FAIL

To login the container later:
sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D /var/lib/container/stretch

To remove the container:
sudo rm -fr /var/lib/container/stretch

=== Cross-distro solution for development inside an ARM/ARM64 chroot on a PC ===

It's possible to set up an emulated chroot development environment for ARM on x86/amd64 that will work on almost any Linux distro with just a few simple steps. This will work for systemd-less distros including Devuan and even Maemo Leste on x86/amd64. This guide provides an example for how to set up a generic ARM64 development chroot on a Debian-based distro. This method can similarly be used with images (tarballs) for other devices.

1. Install the QEMU full system emulation static binaries and [http://binfmt-support.nongnu.org/ support for foreign binaries]:

$ sudo apt-get install qemu-user-static binfmt-support

The installation should register ARM binaries for automatic execution via QEMU. You can verify this with '''update-binfmts''':

$ sudo update-binfmts --display qemu-arm
qemu-arm (enabled):
package = qemu-user-static
type = magic
offset = 0
magic = \x7f\x45\x4c\x46\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00
mask = \xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff
interpreter = /usr/bin/qemu-arm-static
detector =

2. Find the [http://maedevu.maemo.org/images/arm64-generic/ latest] Maemo Leste ARM64 tarball and download and extract it:

$ mkdir leste-arm64
$ cd leste-arm64
$ curl http://maedevu.maemo.org/images/arm64-generic/20190226/maemo-leste-1.0-arm64-generic-20190226.tar.gz | gunzip -c | sudo tar xvf -

3. From the same directory, configure the chroot with a few resources from your host system:

$ sudo mount -t proc proc proc
$ sudo mount -o bind /dev dev
$ sudo mount -o bind /dev/pts dev/pts

4. From the same directory, create a symlink for the mount table:

$ sudo ln -s /proc/mounts etc/mtab

5. From the same directory, set the locale, enter the chroot and switch to the unprivileged user:

$ sudo LC_ALL=C chroot . /bin/su - user

You'll now be ready to use your Maemo Leste ARM64 development environment:

$ uname -m
aarch64

Once you have finished with it, you can exit and unmount the resources you previously mounted:

$ exit
$ sudo umount dev/pts dev proc

=== Localization ===

See [[Localization]]

=== TODO ===

* Discuss where people look to pick up issues (clear answer is the bugtracker, but still)
* How people can make changes and how to send them in

Localization

2021-05-07T06:17:34Z

Parazyd: Created page with "Maemo Leste localization is done with existing packages from Fremantle. The sources are located in one of our GitHub organizations: https://github.com/maemo-leste-translation..."

Maemo Leste localization is done with existing packages from Fremantle.

The sources are located in one of our GitHub organizations: https://github.com/maemo-leste-translations

We also have infrastructure integration with Weblate: https://hosted.weblate.org/projects/maemo-leste/ .
On Weblate people can contribute translation improvements, or even new languages, and pull requests should
automagically be made against our repositories, so maintainers can simply merge it.

Talks

2021-05-04T18:28:43Z

Parazyd: Add Pavel's talk on installfest.cz

== installfest.cz - 3rd March 2021 ==

''' Rok Linuxového telefonu''' - ''Pavel Machek''

[https://installfest.cz/if21/ Event info]

Video [https://www.youtube.com/watch?v=KYmn9-0Tzz8&list=PLub6xBWO8gV-DFBwRbs4xJq4sTGcvEcN0&index=2 YouTube] (via [https://yewtu.be/watch?v=KYmn9-0Tzz8 invidious])

== Bitreichcon 2020 - 2nd May 2020 ==

'''The state of Maemo Leste''' - ''Ivan Jelincic (parazyd)''

[gopher://bitreich.org/1/con/2020 Event info (gopher)]

Slides: [gopher://bitreich.org/0/con/2020/rec/state-of-maemo-leste.md markdown]

Audio: [gopher://bitreich.org/9/con/2020/rec/brcon2020-state-of-maemo-leste.ogg OGG]

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

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

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

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

== OpenFest 2019 - 2nd November 2019==

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

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

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

== OpenAlt 2019 - 2nd November 2019 ==

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

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

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

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

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

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

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

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

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

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

== OpenFest 2018 - 4th November 2018 ==

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

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

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

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

== OpenAlt 2018 - 3rd November 2018 ==

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

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

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

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

Talks

2021-05-04T18:21:50Z

Parazyd: Add Bitreichcon 2020 talk.

== Bitreichcon 2020 - 2nd May 2020 ==

'''The state of Maemo Leste''' - ''Ivan Jelincic (parazyd)''

[gopher://bitreich.org/1/con/2020 Event info (gopher)]

Slides: [gopher://bitreich.org/0/con/2020/rec/state-of-maemo-leste.md markdown]

Audio: [gopher://bitreich.org/9/con/2020/rec/brcon2020-state-of-maemo-leste.ogg OGG]

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

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

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

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

== OpenFest 2019 - 2nd November 2019==

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

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

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

== OpenAlt 2019 - 2nd November 2019 ==

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

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

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

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

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

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

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

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

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

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

== OpenFest 2018 - 4th November 2018 ==

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

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

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

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

== OpenAlt 2018 - 3rd November 2018 ==

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

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

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

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

Status/GPS

2021-03-03T13:31:53Z

Parazyd: /* Setting up GPSD with gpsfake on a VM */

== Fremantle Gypsy ==

is actually not gypsy. Rather (some) gypsy calls implemented as "location-daemon".
location-daemon/gypsy gets spawned after an application requests GPS. How exactly - TBD.

== Setting up GPSD with gpsfake on a VM ==

Install gpsd and gpsd-clients:

<pre>
apt install gpsd gpsd-clients
</pre>

Stop apparmor (for testing only!):

<pre>
/etc/init.d/apparmor stop
aa-teardown
</pre>

And then you can run gpsfake using test files from the gpsd repo:

<pre>
git clone https://github.com/maemo-leste-upstream-forks/pkg-gpsd
gpsfake -c 1 pkg-gpsd/test/daemon/nokia-ld-4w.log
</pre>

Then in another terminal, type:

<pre>
cgps
</pre>

And you should see the information from the GPS log be replayed.

== Relevant URLs ==

* https://github.com/maemo-leste/bugtracker/issues/151
* https://github.com/maemo-leste/bugtracker/issues/57
* http://talk.maemo.org/showthread.php?t=100363
* <s>(On combining multiple gps sources such as A-GPS/SUPL and gpsd) https://lists.gnu.org/archive/html/gpsd-dev/2012-07/msg00018.html</s> (not actually relevant, A-GPS needs to fed to the GPS driver/subsystem, not merged as info into gpsd)
* supl implementation: https://github.com/tajuma/supl
* https://talk.maemo.org/showthread.php?t=93910
* https://github.com/postmarketOS/gps-nokia-n900/blob/master/gps-nokia-n900.c

== Regarding Droid 4 GPS ==

<pre>
17:05 < Wizzup> tmlind: wrt gps on the droid, you said there is currently a bug that allows opening
/dev/gnss* only once?
17:09 < tmlind> Wizzup: i think that was a bug in gpsd, did not happen last time i tried. if you hit
that one, opening secondary clients like gpspipe -R won't output anything
17:09 < Wizzup> ah, so it's not a kernel problem, ok
17:10 < Wizzup> once maemo-input-sounds is done (hopefully tonight) I will work on location stuff in
case I can go on vacation and need gps, or until fmg is done with abook and we then
look at rtcom
17:10 < Wizzup> in any case, I was wondering what the gps status is, but I think we'll start gpsd on
demand, so that's fine
17:11 < Wizzup> from a pm pov, I assume closing the fd will stop gps recv?
17:11 < Wizzup> also, this is on the wiki: 22:30 < tmlind> hmm there's a probably kernel gnss bug for
gsp access fyi, you can currently only open one connection before you have to restart
gpsd :)
17:13 < tmlind> Wizzup: yeah so if hiking, you probably want to modprobe gnss_motmdm rate_ms=3000 or
even higher to allow the soc to sleep inbetween
17:14 < tmlind> Wizzup: the default gpsd options only open device if there's a client and times out
automatically
17:14 < Wizzup> interesting.
17:14 < Wizzup> regarding module - well noted
17:14 < Wizzup> I didn't know gpsd auto closed, that's nice.
17:15 < tmlind> i think i measured about 200 - 250 mW with gps enabled screen blanked etc
</pre>

== Regarding A-GPS in general, but also N900 and Droid 4 specifics ==

<pre>
17:15 < Wizzup> also ran into this: https://lists.gnu.org/archive/html/gpsd-dev/2012-07/msg00018.html
17:15 < Entitlement> Wizzup - [ Re: [gpsd-dev] Using multiple location sources to improve accuracy and
r ]
17:15 < Wizzup> (regarding agps)
17:15 < tmlind> Wizzup: yeah so don't enable gpsd -n option, that will keep the gps open
17:15 < Wizzup> looks like ESR suggests to write a daemon that sits in the middle and mixes in agps
info
17:15 < Wizzup> ok
17:16 < Wizzup> regarding rate_ms, I wonder if it makes more sense to keep it lower until a proper fix
is found
17:16 < Wizzup> although I suppose that's only the reporting rate, so it probably doesn't matter
17:16 < tmlind> yeah it defaults to 1s so just leave it out by default
17:16 < tmlind> it will be some generic option eventually and not a module param
17:17 -!- z3ntu_ [z3ntumatri@gateway/shell/matrix.org/x-lnssiqwycssoqteb] has quit [Quit: Idle for 30+
days]
17:18 < tmlind> not sure how much stuff i'll get done over next few months in general, but at some
point i'm planning to continue on the droid4-agps tool..
17:19 < Wizzup> tmlind: what would that do?
17:19 < Wizzup> I figured agps could be done via with https://github.com/tajuma/supl
17:19 < Entitlement> Wizzup - [ GitHub - tajuma/supl ]
17:19 < Wizzup> s/via with/with this/
17:20 -!- peetah [~peetah@cha92-9-82-236-202-86.fbx.proxad.net] has joined #maemo-leste
17:22 < bencoh> (tested and more or less working on maemo5, btw)
17:22 < Wizzup> bencoh: just now?
17:22 < bencoh> no
17:22 < Wizzup> :)
17:23 < bencoh> I used it to proxify supl requests to google
17:23 < tmlind> Wizzup: hmm maybe not sure. in this case we need to download qcom provided up to date
xtra2.bin file for the gnss, not sure if the older formats work at all for the gnss
17:25 < bencoh> tmlind: I'd tend to think you would need to keep gps "always on" before the first fix
17:25 < bencoh> otherwise you will never get enough information from satellites
17:25 < bencoh> (unless you have agps/supl, of course)
17:26 < Wizzup> tmlind: from what I can tell that tool just takes lac/mcc/mns and such (like we can
get from ofono or from modem directly) and just calls to a SUPL service?
17:27 < bencoh> Wizzup: google would even return you a rough position with those
17:27 < tmlind> bencoh: yes it does that already automatically and won't start idling until the fix is
done
17:27 < bencoh> tmlind: ah, I see
17:28 < tmlind> Wizzup: yeh i figured, not sure if the modem nvram settings for supl are working or
not, i somehow have an impression they're only working for some older modems, could be
wrong
17:28 < Wizzup> I don't know enough about AGPS clearly, but from what I currently understand, it's
just a data connection to a server with some cell data
17:29 < Wizzup> so I am not sure what the modem would do specifically
17:29 < Wizzup> I suppose there are probably many "assisted" methods
17:29 < bencoh> Wizzup: you're supposed to receive orbital data / almanac
17:30 < Wizzup> ah
17:30 < bencoh> and feed it to the gps subsystem
17:30 < tmlind> yeah this xtra2.bin stuff is an almanac in some proprietary format for a week i think
17:30 < Wizzup> oh, right, to actually feed it
17:30 < Wizzup> I get it now.
17:30 < Wizzup> when I was searching for methods to tell gpsd about agps nothing turned out, explains
it now
17:31 < Wizzup> s/turned out/turned up/
17:31 < bencoh> iiuc on n900, the modem itself manages the supl connection; the location daemon only
acts as a proxy to provide it a tcp connection
17:31 < Wizzup> ok, yeah, so for the n900 we will have to RE some stuff
17:31 < bencoh> yeah
17:31 < tmlind> bencoh: afaik also mdm6600 nvram has something for supl server, not sure if it works
though
17:32 < tmlind> bencoh: if you want to try it, you can tweak the nvram values with tcmdrw on
github.com/tmlind
17:32 < bencoh> tmlind: meaning implementing/RE-ing such a proxy would make sense for both platforms
17:33 < tmlind> bencoh: hmm proxy running where? on the device?
17:33 < bencoh> on n900/maemo5, yeah
17:33 < bencoh> iirc it is location-proxy (forked on demand I think)
17:33 < tmlind> well i think the modem uses the supl server directly probably based on some
requirements from the ministry of silly walks
17:34 < Wizzup> bencoh: there is location-proxy and location-daemon btw
17:34 < bencoh> it does; the "proxy" only provides the modem with a mean to open a tcp socket and
read/write to it
17:34 < bencoh> Wizzup: indeed
17:34 < Wizzup> if you have more info please share :)
17:34 < Wizzup> I can RE some stuff, but want to RE the right things only
17:35 < bencoh> I haven't toyed with those for quite some time, but lemme see
17:35 < tmlind> well the thing to try with droid4 mdm6600 would be to configure supl server in nvram,
start modem data connection, then gps and see how fast it gets a fix
17:38 < tmlind> i'd try clearing openpst NV_AAGPS_XTRA_ENABLED_I value to try to disable xtra2.bin
use, then try to configure whatever nvram values there might be for a supl server,
sorry no idea what those entries might be but i see the dumps contain some url in hex
format
17:40 < bencoh> Wizzup: see /usr/lib/liblas.so.0.0.0
17:41 < bencoh> especially the las_socket_*
17:41 < bencoh> location-proxy refers to those
17:42 < Wizzup> hm 32K
17:42 < Wizzup> this is likely all n900 specific though right?
17:42 < bencoh> Wizzup: http://pastebin.notk.org/pastebin.php?show=f7f7b371d
17:42 < Entitlement> bencoh - [ pastebin private pastebin - collaborative debugging tool ]
17:42 < bencoh> most likely n900-specific yeah
17:42 < tmlind> hmm so a quick search for the NV_AAGPS_XTRA_ENABLED_I points to some earlier pastebin
page at https://pastebin.com/dyfsUcHc, maybe try configuring those and disable xtra
stuff?
17:42 < Entitlement> tmlind - [ QPST 378 NV Items that are in i535 but NOT in i535 dev ed -
Pastebin.com ]
17:43 < bencoh> tmlind: I don't think supl server address would go into nvram
17:43 < Wizzup> bencoh: ah, so you're suggesting we make some generic "how to write supl data to a
modem" lib?
17:43 < bencoh> tmlind: well, unless it has a mean to actually ask for a specific supl server from the
AP processor
17:43 < tmlind> bencoh: i'm pretty sure the uri goes to nvram, see NV_CGPS_UMTS_PDE_SERVER_ADDR_URL_I
in the link above
17:43 < bencoh> oh
17:44 < bencoh> well, on n900/maemo5, the host gets to decide on that
17:44 < tmlind> ok
17:45 < bencoh> Wizzup: I guess we would want a "generic" glue lib with support for various (two?)
platforms
17:45 < tmlind> bencoh: there seems to be a bunch PDE related nvram entries, see libopenpst dm_nv.h
file
17:46 < bencoh> right
17:47 < bencoh> Actually I wonder if the supl connection would need to go through the host cpu at all
on the mdm6600
17:47 < tmlind> bencoh: no afaik it can't
17:48 < bencoh> it might try and use the gprs/umts data channels
17:48 < tmlind> i think it has to
17:48 < bencoh> without even bothering with the host
17:48 < tmlind> right
17:48 < bencoh> it's a completely different design then
17:48 < bencoh> meaning it should work automagically once we setup pde server properly
17:49 < tmlind> yeah it should hopefully unless it's working only in the xtra2.bin mode
17:49 < bencoh> and that it'll stop working forever once supl servers break support for it
17:49 < tmlind> bencoh: so i did also a tool for the xtra2.bin stuff but it's not complete, also on my
github page droid4-agps or something like that
17:49 < bencoh> (unlike n900, where we managed to somehow get some kind of support using supl-proxy
from tajuma)
17:50 < tmlind> bencoh: at least the supl stuff is a standard format, let's hope it works :)
17:51 < bencoh> it's "standard" until google decides some input fields become mandatory
17:51 < bencoh> but yeah
17:51 < tmlind> i think there are other supl servers available too, right?
17:51 < Wizzup> bencoh: there were other supl servers I think
17:51 < bencoh> (I think that's the reason supl.google.com doesn't work on n900 without any proxy)
17:51 < Wizzup> bencoh: oh?
17:51 < bencoh> well, it depends on your phone service provider
17:52 < bencoh> vodaphone has (had?) one for their customers, but it's not available from outside
their network
17:52 < bencoh> nokia died
17:52 < bencoh> I think sony had one, but ...
17:53 < bencoh> we could also run one, but we'd need to write a fair bit of code for that
17:53 < Wizzup> didn't see any code for it so far
17:53 < Wizzup> (googling around)
17:54 < Wizzup> as in, for a supl server
17:54 < bencoh> Wizzup: https://github.com/fairwaves/RRLP-2.8
17:54 < Entitlement> bencoh - [ GitHub - fairwaves/RRLP-2.8: OpenBTS 2.8 RRLP server, Fairwaves
version ]
17:55 < bencoh> that's for the rrlp part
17:56 < bencoh> I don't remember whether they implemented the SUPL part, but if not, one would need to
wrap the RRLP payload in SUPL packets
17:56 < tmlind> well just having a server proxying the supl data from various sources should do, sort
of what ntpd does
17:57 < Wizzup> it would be nice to have a supl server one can just run, though
17:57 < tmlind> yup
17:57 < bencoh> tmlind: yup, that's exactly what we started doing on maemo5/n900
17:57 < Wizzup> all of this sounds like we will just do GPS with A-GPS first though ;)
17:57 < Wizzup> (for leste, to at least get the frameworks in place)
17:58 < bencoh> I ran a supl-proxy everytime I needed to get a gps fix
17:54 < bencoh> Wizzup: https://github.com/fairwaves/RRLP-2.8
17:54 < Entitlement> bencoh - [ GitHub - fairwaves/RRLP-2.8: OpenBTS 2.8 RRLP server, Fairwaves
version ]
17:55 < bencoh> that's for the rrlp part
17:56 < bencoh> I don't remember whether they implemented the SUPL part, but if not, one would need to
wrap the RRLP payload in SUPL packets
17:56 < tmlind> well just having a server proxying the supl data from various sources should do, sort
of what ntpd does
17:57 < Wizzup> it would be nice to have a supl server one can just run, though
17:57 < tmlind> yup
17:57 < bencoh> tmlind: yup, that's exactly what we started doing on maemo5/n900
17:57 < Wizzup> all of this sounds like we will just do GPS with A-GPS first though ;)
17:57 < Wizzup> (for leste, to at least get the frameworks in place)
17:58 < bencoh> I ran a supl-proxy everytime I needed to get a gps fix
17:58 < Wizzup> I should probably do it on fremantle too, didn't look at the proxying
17:58 < bencoh> (I think it stopped working at some point, but I haven't investigated it. It might be
a cert issue)
17:58 < tmlind> well i meant running a proxying supl server on maemo.org picking data from various
sources so devices would just point to the maemo supl server
17:58 < bencoh> Wizzup: Sicelo eventually wrote a howto https://wiki.maemo.org/N900_GPS_Proxy
17:58 < Entitlement> bencoh - [ N900 GPS Proxy - maemo.org wiki ]
17:59 < bencoh> tmlind: *nod*
17:59 < Wizzup> check
17:59 < Wizzup> tmlind: ah, right
17:59 < Wizzup> that's definitely a good stopgap at least
18:00 < bencoh> We almost have the code for that
18:00 < tmlind> yeah then adding supl data from some open source data feed could be just added
18:00 < bencoh> we just need to add multi-client support to supl-proxy
18:00 < tmlind> cool
18:01 < bencoh> err, except that supl-proxy will actually fetch data for every request
18:01 < tmlind> heh that probably creates a google maps traffic jam to where that server is hosted :)
18:01 < bencoh> :))
18:02 < tmlind> not sure if there are some legal aspects to consider there, not familiar with the supl
stuff really
18:02 < bencoh> you need to supply a valid cell (mnc/lac/whatever) coordinate, and supl response is
customized accordingly
18:02 < bencoh> afaict
18:02 < tmlind> huh why do you need mnc/lac?
18:03 < tmlind> to limit the data size?
18:03 < bencoh> I'm pretty certain you wouldn't need it in theory to get a full ephemeric/almanac dump
18:03 < tmlind> bbl
18:03 < bencoh> but iirc it's mandatory for supl.google.com
18:04 < bencoh> (I can see a pretty good reason for that, actually ... google loves knowing where you
are)
18:06 < Wizzup> yeah
18:06 < Wizzup> from 3) A-GPS here , there seem to be only a few
https://www.reddit.com/r/privacy/comments/cldrym/how_to_degoogle_lineageos_in_2019/
18:06 < Entitlement> Wizzup - [ How to deGoogle LineageOS in 2019 : privacy ]
18:06 < Wizzup> (providers that run a supl server)
18:12 < bencoh> wow, supl.sonyericsson.com actually works as well
18:13 < bencoh> and vodafone too. funny, last time I tried I couldn't use it
18:17 < tmlind> cool, anyways multiple source for the proxying supl server would be best, sort of like
with nptd
18:17 * bencoh nods
</pre>

Tricks

2021-02-05T08:48:51Z

Parazyd:

__FORCETOC__

= Randomize MAC Address =
Some users may wish to change the MAC address of an interface, for e.g. to prevent wifi networks associating their MAC address with their network usage pattern.

The macchanger package addresses this by either automatically or manually changing the MAC address of enabled interfaces.

apt install -y macchanger

During installation, the package configuration allows user to select automatic change of MAC address when interface is brought up. This may interfere with USB networking. As an alternative, user can manually change the wlan0 MAC.

macchanger wlan0 -e -a
ifconfig wlan0 up

= Keyboard / Mouse sharing with PC =
To use a Leste device while working at desktop it can be convenient to share mouse and keyboard of the host pc with the leste device. The 'barrier' client/server program, forked from 'synergy', allows this.

https://github.com/debauchee/barrier Barrier software-KVM switch

A hildonized Maemo-leste binary of the client is not available at time of this writing. Developers and testers may wish to disable undesired modules included with the barrier source, before compiling.

= Touchscreen support in Firefox (firefox-esr) =

Add the necessary environment variable:

echo "MOZ_USE_XINPUT2 DEFAULT=1" >> /etc/security/pam_env.conf

Then in firefox, open '''about:config''' and set '''dom.w3c_touch_events.enabled''' to '''1'''.

You can also set a mobile useragent by creating a string key called '''general.useragent.override'''.
Then set something like this:

Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0

Tricks

2021-02-05T08:47:27Z

Parazyd: Cleanup

= Randomize MAC Address =
Some users may wish to change the MAC address of an interface, for e.g. to prevent wifi networks associating their MAC address with their network usage pattern.

The macchanger package addresses this by either automatically or manually changing the MAC address of enabled interfaces.

apt install -y macchanger

During installation, the package configuration allows user to select automatic change of MAC address when interface is brought up. This may interfere with USB networking. As an alternative, user can manually change the wlan0 MAC.

macchanger wlan0 -e -a
ifconfig wlan0 up

= Keyboard / Mouse sharing with PC =
To use a Leste device while working at desktop it can be convenient to share mouse and keyboard of the host pc with the leste device. The 'barrier' client/server program, forked from 'synergy', allows this.

https://github.com/debauchee/barrier Barrier software-KVM switch

A hildonized Maemo-leste binary of the client is not available at time of this writing. Developers and testers may wish to disable undesired modules included with the barrier source, before compiling.

= Touchscreen support in Firefox (firefox-esr) =

Add the necessary environment variable:

echo "MOZ_USE_XINPUT2 DEFAULT=1" >> /etc/security/pam_env.conf

Then in firefox, open '''about:config''' and set '''dom.w3c_touch_events.enabled''' to '''1'''.

You can also set a mobile useragent by creating a string key called '''general.useragent.override'''.
Then set something like this:

Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0

Tricks

2021-02-05T08:45:10Z

Parazyd: Firefox tip for touchscreen

List of tricks:

==== Randomize MAC Address ====
Some users may wish to change the MAC address of an interface, for e.g. to prevent wifi networks associating their MAC address with their network usage pattern.

The macchanger package addresses this by either automatically or manually changing the MAC address of enabled interfaces.
<pre>apt install -y macchanger
</pre>
During installation, the package configuration allows user to select automatic change of MAC address when interface is brought up. This may interfere with USB networking. As an alternative, user can manually change the wlan0 MAC.
<pre>
macchanger wlan0 -e -a
ifconfig wlan0 up
</pre>

==== Keyboard / Mouse sharing with PC ====
To use a leste device while working at desktop it can be convenient to share mouse and keyboard of the host pc with the leste device. The 'barrier' client/server program, forked from 'synergy', allows this.
<pre>
https://github.com/debauchee/barrier Barrier software-KVM switch
</pre>
A hildonized maemo-leste binary of the client is not available at time of this writing. Developers and testers may wish to disable undesired modules included with the barrier source, before compiling.

==== Touchscreen support in Firefox (firefox-esr) ====

Add the necessary environment variable:

echo "MOZ_USE_XINPUT2 DEFAULT=1" >> /etc/security/pam_env.conf

Then in firefox, open '''about:config''' and set '''dom.w3c_touch_events.enabled''' to '''1'''.

You can also set a mobile useragent by creating a string key called '''general.useragent.override'''.
Then set something like this:

Mozilla/5.0 (Android 9; Mobile; rv:68.0) Gecko/68.0 Firefox/68.0

Motorola Droid 4

2021-02-04T21:41:35Z

Parazyd: /* Status */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Implemented with Pulseaudio and UCM files
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

[[Category:Device]]

Motorola Droid 4

2021-02-04T21:39:46Z

Parazyd: /* Status */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
}}

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| Wireless || Yes ||
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || OTG and USB network
|-
| Keyboard || Yes || Slightly modified keyboard layout, see https://www.spinics.net/lists/linux-omap/msg135137.html (TLDR; Shift key produces CTRL, SYM produces ALT, and Caps lock produces SHIFT)
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || Not yet ||
|-
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)
|-
| Gyro || N/A ||
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || N/A || Missing in hardware
|-
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/
|-
| Idle power consumption || ~120mW || Needs sim inserted
|}

== Installation ==

Hardware requirements:

* Droid4 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

Download from https://maedevu.maemo.org/images/droid4/

# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# flash-droid-4-fw.sh
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz

Download from https://github.com/tmlind/droid4-kexecboot.git

# utags-mmcblk1p13.bin
# droid4-kexecboot.img

Check what kernel version your Android OS runs.
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".
If you have at least 3.0.8, you may skip "Updating Android" step below.

Installation:

# Create a working directory with above mentioned files in it
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip
# Power off Droid4 and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Updating Android ===

This will reinstall the Android OS on your device, deleting all user data. Do a backup, if you want to save something. When everything is ready, go to the working directory mentioned above and run:
<pre>
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml
sudo bash ../flash-droid-4-fw.sh
popd
</pre>

=== Setting up kexecboot ===

Now, assuming you are in the working directory, install kexecboot:

<pre>
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-mmcblk1p13.bin
sudo fastboot reboot
</pre>

If you did "Updating Android" the device should run the firstboot steps.
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.

=== Install Maemo Leste to the sdcard ===

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.

You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.

== Updating ==

Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:

* Poweroff device, grab the SD card
* Backup any important files
* Grab the latest image from https://phoenix.maemo.org/view/Images/
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE

== Notes ==

The battery in Droid4 is not easily removable. If you got the device stuck, use this combo: power button + bottom volume key. You should hold them for about 7 seconds. Droid4 will then reboot.

If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.

Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.
Blacklisting the module may help if you have such problems:
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf

Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]

Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 exposes a serial console on the USB port. You can construct the required cable easily by following the instructions there. If you have old Nokia CA-42 or DKU-5 cables, then you can use them with the Droid 4, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

While using the serial cable, if you lose the connection, the following may help:

<pre>
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with
the console login propt later
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help
</pre>

== Stuff to try ==

==== Blinkenlights ====
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light

==== Wifi ====

The WL1285C Wifi chip in the droid 4 has no onboard nvmem to save its calibration parameters or its MAC address. Instead it gets these parameters from a configuration file provided by the kernel. By default a generic file is provided but for optimal range and a correct persistent MAC address a calibration procedure must be performed.

Install necessary tools:
<pre>
apt-get install ti-utils-wilink6 droid4-wlanconfig
</pre>
Run calibration:
<pre>
sudo maserati-calibrate
</pre>

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

<pre>
Read modem output:
# cat /dev/motmdm1 &

Online modem:
# printf "AT+CFUN=1\r" > /dev/motmdm1

Connect to network:

# printf "AT+COPS=1\r" > /dev/motmdm1

Print connected network:

# printf "AT+COPS?\r" > /dev/motmdm1

Not sure, do it anyway:

# printf "AT+SCRN=0\r" > /dev/motmdm1

Dial a number:

# printf "ATD+1234567890\r" > /dev/motmdm1

Hang up:

# printf "ATH\r" > /dev/motmdm1

Answer incoming call:

# printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in alsamixer, make sure echo cancellation is turned on. I had to set Call out to "speakerphone" and set the right speaker to "voice" codec, and set volume for both call and voice to something non-zero.

==== 3G Internet ====
<pre>
22:12 < pave1> qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
22:12 < pave1> route del default
22:12 < pave1> sudo ifconfig wwan0 up
22:12 < pave1> dhclient wwan0
</pre>

==== GPS ====
<pre>
modprobe gnss-motmdm and point gpsd to use /dev/gnss0
</pre>

22:30 < tmlind> hmm there's a probably kernel gnss bug for gsp access fyi, you can currently only open one connection before you have to restart gpsd :)

Can try to <pre>
mkfifo /tmp/gps
cat /dev/gnss0 > /tmp/gps
Then point gpsd to use /tmp/gps
</pre>

==== USSD ====

<pre>
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8:
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output
</pre>

==== HDMI ====
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier.
<pre>
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off
</pre>
Return to internal touchscreen display.
<pre>
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off
</pre>

==== Keyboard / Mouse sharing with PC ====
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4.
<pre>
[https://github.com/debauchee/barrier Barrier software-KVM switch]
</pre>
Developers and testers may wish to disable the googley bits before compiling.

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
Cant_have_2_much_leste.jpg
Leste-neverball.jpg
Statsfun.jpg
Leste-glmatrix.png
Droid4-leste-utox2.jpg
Droid4-leste-pcsx.jpg
Droid4-leste-surf_master.jpg
</gallery>

[[Category:Device]]

Anbox

2021-01-27T09:55:34Z

Parazyd:

= Installation =

From extras

apt install anbox

Or install anbox from HAM.

[[File:Anbox-ham.png|400px]]

You might have to enable zram or classic swap (at least 1GB).

= Usage =

The initscript should automatically start anbox container-manager.

supervise-daemon anbox-container-manager --start /usr/bin/anbox -- container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img
\_ /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img

You should be able to start Anbox through '''Menu->Anbox'''. Be patient with the splash screen. It can take a looong time.

== Alternative (CLI) ==

Same as above, the initscript should start anbox's container manager.

As '''user''' in a terminal:

export ANBOX_LOG_LEVEL=debug
anbox session-manager

This should output:

user@devuan-pinephone:~$ anbox session-manager
[ 2021-01-18 14:20:08] [Renderer.cpp:165@initialize] Using a surfaceless EGL context
[ 2021-01-18 14:20:08] [Renderer.cpp:248@initialize] Successfully initialized EGL
[ 2021-01-18 14:21:03] [session_manager.cpp:264@operator()] Android successfully booted

In another terminal, also as '''user''':

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

Please note that '''it takes a long time to start''' an activity for the first time. So be patient. Subsequent runs should be faster.
You can view "progress" in htop. anbox should be using the CPU. When the usage is low, you should be ready to start activities.

== Tips ==

=== Free memory after usage ===

To free up some memory after you're done with usage:

kill -3 `pgrep -f session-manager`

=== Logs ===

You can export an environment variable to get some more debug output from Anbox

export ANBOX_LOG_LEVEL=debug

Plus, you can also find some useful logs in /var/lib/anbox/logs.

=== Running Anbox in the Leste VM ===

Under qemu, it is possible to run Anbox in a VM. (Please add instructions for other VM backends if you test them)

A command line that is tested to work:

qemu-system-x86_64 -enable-kvm -cpu host -m 4G \
-smp cores=4 -drive file=maemo-leste.qcow2,if=virtio \
-net nic -net user,hostfwd=tcp::2223-:22 \
-usb -device usb-tablet \
-vga virtio -display gtk,gl=on

The <code>-vga virtio -display gtk,gl=on</code> is the important part. It should also be possible
to use plain SDL rather than GTK with <code>-display sdl,gl=on</code> instead. When booted, you
should see that hardware acceleration is enabled in the kernel log.

# dmesg | grep -i dri

Once enabled, on beowulf you also need the backports kernel, so you can install it by enabling the
backports repository:

# echo "deb https://pkgmaster.devuan.org/merged beowulf-backports main" >> /etc/apt/sources.list
# apt update
# apt -t beowulf-backports install linux-image-amd64
# reboot
# apt install anbox

Then you can use Anbox normally.

= Further reading =

https://wiki.postmarketos.org/wiki/Anbox

https://anbox.io/

Anbox

2021-01-27T09:54:08Z

Parazyd: /* Installation */

File:Anbox-ham.png

2021-01-27T09:52:17Z

Parazyd: Anbox in HAM

Anbox in HAM

Anbox

2021-01-27T09:47:02Z

Parazyd: /* Tips */

= Installation =

From extras

apt install anbox

Or install anbox from HAM.

You might have to enable zram or classic swap (at least 1GB).

= Usage =

The initscript should automatically start anbox container-manager.

supervise-daemon anbox-container-manager --start /usr/bin/anbox -- container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img
\_ /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img

You should be able to start Anbox through '''Menu->Anbox'''. Be patient with the splash screen. It can take a looong time.

== Alternative (CLI) ==

Same as above, the initscript should start anbox's container manager.

As '''user''' in a terminal:

export ANBOX_LOG_LEVEL=debug
anbox session-manager

This should output:

user@devuan-pinephone:~$ anbox session-manager
[ 2021-01-18 14:20:08] [Renderer.cpp:165@initialize] Using a surfaceless EGL context
[ 2021-01-18 14:20:08] [Renderer.cpp:248@initialize] Successfully initialized EGL
[ 2021-01-18 14:21:03] [session_manager.cpp:264@operator()] Android successfully booted

In another terminal, also as '''user''':

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

Please note that '''it takes a long time to start''' an activity for the first time. So be patient. Subsequent runs should be faster.
You can view "progress" in htop. anbox should be using the CPU. When the usage is low, you should be ready to start activities.

== Tips ==

=== Free memory after usage ===

To free up some memory after you're done with usage:

kill -3 `pgrep -f session-manager`

=== Logs ===

You can export an environment variable to get some more debug output from Anbox

export ANBOX_LOG_LEVEL=debug

Plus, you can also find some useful logs in /var/lib/anbox/logs.

=== Running Anbox in the Leste VM ===

Under qemu, it is possible to run Anbox in a VM. (Please add instructions for other VM backends if you test them)

A command line that is tested to work:

qemu-system-x86_64 -enable-kvm -cpu host -m 4G \
-smp cores=4 -drive file=maemo-leste.qcow2,if=virtio \
-net nic -net user,hostfwd=tcp::2223-:22 \
-usb -device usb-tablet \
-vga virtio -display gtk,gl=on

The <code>-vga virtio -display gtk,gl=on</code> is the important part. It should also be possible
to use plain SDL rather than GTK with <code>-display sdl,gl=on</code> instead. When booted, you
should see that hardware acceleration is enabled in the kernel log.

# dmesg | grep -i dri

Once enabled, on beowulf you also need the backports kernel, so you can install it by enabling the
backports repository:

# echo "deb https://pkgmaster.devuan.org/merged beowulf-backports main" >> /etc/apt/sources.list
# apt update
# apt -t beowulf-backports install linux-image-amd64
# reboot
# apt install anbox

Then you can use Anbox normally.

Main Page

2021-01-26T18:57:01Z

Parazyd: /* Getting Started */

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Getting Started ==

See [[Getting_Started|Getting Started]]

== Frequently Asked Questions ==

See [[Leste_FAQ|FAQ]]

== Supported Devices ==

See [[:Category:Device]]

== Latest Images ==

https://phoenix.maemo.org/view/Images/

== Development ==

See [[Development]]

== Roadmap ==

=== Project milestones ===
https://github.com/maemo-leste/bugtracker/milestones

=== Wishlist ===

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

== Talks ==

See [[Talks]]

== Links ==
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Our Package index: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Main Page

2021-01-26T18:56:40Z

Parazyd:

= Description =

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.

You can find us on '''freenode''', channel '''#maemo-leste'''.

For an overview of the current status, you might want to check out: [[Status]]

Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.

The project is currently not usable as a daily driver for your device. Maemo Leste is currently in development phase and we are actively searching for developers.

For some devices, we have development images available, such as the N900. So far we have set up Devuan/Debian repositories for our packages, with builds for armhf, arm64 and amd64. We have FOSS replacements for some closed Maemo packages, further building on the Maemo community efforts to replace all closed bits by open software.

If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.

== Getting Started ==

[[Getting_Started]]

== Frequently Asked Questions ==

See [[Leste_FAQ|FAQ]]

== Supported Devices ==

See [[:Category:Device]]

== Latest Images ==

https://phoenix.maemo.org/view/Images/

== Development ==

See [[Development]]

== Roadmap ==

=== Project milestones ===
https://github.com/maemo-leste/bugtracker/milestones

=== Wishlist ===

You have an application you want to see in Leste? Please let us know [[Wishlist|here]].

== Talks ==

See [[Talks]]

== Links ==
<div>
The central point of meeting and talking is IRC (irc.freenode.net in #maemo-leste) and this thread: https://talk.maemo.org/showthread.php?t=100192.

*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]

*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]

*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]

*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]

*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/

*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]

*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]

*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )

*Our Package index: [https://maedevu.maemo.org/pkgweb/ https://maedevu.maemo.org/pkgweb/] which runs [https://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]

*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]

*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]
</div>

Anbox

2021-01-18T21:16:22Z

Parazyd: /* Usage */

Anbox

2021-01-18T21:15:35Z

Parazyd: /* Usage */

Anbox

2021-01-18T21:08:51Z

Parazyd: /* Usage */

Anbox

2021-01-18T21:04:48Z

Parazyd: /* Usage */

PinePhone

2021-01-18T16:06:27Z

Parazyd: /* Status */

{{Stub}}

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

The first Pinephone (braveheart) phone

== Notes ==

''' [https://maedevu.maemo.org/images/pinephone/ Testing images repo.] '''

''' What you can do with the 20200223 image:'''

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* (With not yet finished userspace, terminal only) connect to 2G/3G/4G data connections

''' TODO mention/link to:'''

* USB peripheral
* Develop for Maemo Leste and work on applications that interface with modems
* Make it work on latest pine64 kernel

''' Note that: '''

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* Default virtual keyboard is set to off. You may want to go to setting and change that first for using the terminal. Click the top left corner->"Settings"->"Text input"->check the "Use virtual keyboard" option. You may also want to change the keyboard layout by changing the dictionary setting.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* We are not shipping the latest Pinephone kernel yet (feel free to work on that, or anything above!)
* Many "games" packages in the Application Manager don't work well yet.
* For some reason the X cursor is still shows (usually it's hidden)
*

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.10 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A ||
|-
| Bluetooth || ? ||
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave only, exposes network gadget by default. Host Untested
|-
| Keyboard || N/A || !
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G data || WIP || Works with ofono; UI underway: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || WIP || Works with ofono, will using telepathy-ring, no UI yet, not enabled by default
|-
| Phone calls || WIP || Reported to work, not enabled by default, community is quite far along, needs to work package their work
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|}

== Installation ==

(Work in Progress)

Currently:
* .img.xz does not match .img.sha
* working out how to install .tar.gz

Unlike most phones, it's pretty simple.

Download the image and the corresponding <code>.sha</code> file, then verify the image's integrity:

$ cat maemo-leste-*-arm64-pinephone-*.img.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz

or

$ cat maemo-leste-*-arm64-pinephone-*.tar.gz.sha
$ sha256sum maemo-leste-*-arm64-pinephone-*.tar.gz

Verify that the number that each command spits out is exactly the same number. If it is not, do not use the image. Try redownloading or ask for help.

=== SD Card Installation ===
==== Prepare the SD card ====

Format the SD card as ext4 using any of your preferred tools.

====if you downloaded the .img.xz====

extract the image:

$ cp maemo-leste-*-arm64-pinephone-*.img.xz /path/to/sd-card
$ cd /path/to/sd-card
$ tar --extract -f maemo-leste-*-arm64-pinephone-*.img.xz

dd the image to an sd card. If using a Windows machine, you can use [https://etcher.io/ Etcher] NOTE: Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to.

In a terminal window, use the command below, making sure you replace the input file <code>if=</code> argument with the path to your file, and the <code>/dev/sdX</code> in the output file <code>of=</code> argument with the correct device name. This is very important, as you will lose all the data on the hard drive if you provide the wrong device name. Make sure the device name is the name as described above, with no partition numbers. For example: sdd, not sdds1 or sddp1; mmcblk0, not mmcblk0p1. In most cases with SD cards, your computer might read the SD card as mmcblk0 or something similar. Don't copy and paste this command, type it out and use TAB completion.

$ dd bs=4M if=maemo-leste-*-arm64-pinephone-*.img of=/dev/sdX conv=fsync

Please note that block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Also note that if you are not logged in as root you will need to prefix this with sudo.

====if you downloaded the .tar.gz====

This might work?

$ cp maemo-leste-*-arm64-pinephone-*.tar.gz /path/to/sd-card
$ cd /path/to/image/
$ tar --extract -f maemo-leste-*-arm64-pinephone-*.tar.gz

Then insert SD card, replace the back cover, and turn it on.

These steps should work in theory, but at the moment the image is unbootable.

=== eMMC Installation ===

==== Extract the image ====

Download the .img.xz version of the image and extract it:

$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz

==== Modify the image to use eMMC paths ====

The image, by default, points to <code>/dev/mmcblk0</code> for SD cards, which must be modified to point to <code>/dev/mmcblk2</code> for the eMMC. To start, determine the starting points of the image partitions:

$ fdisk -u -l maemo-leste-*-arm64-pinephone-*.img.xz

In the output of this command, look for the '''Start''' column and multiply these values individually with the value given by the '''Units''' section -- this gives the offsets of the partitions from the beginning of the file.

Mount the first partition and enter it:

$ sudo mount -o loop,offset=<Partition 1 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>boot.txt</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Regenerate <code>boot.scr</code>:

$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr

Leave the first partition and unmount it:

$ cd ~
$ sudo umount /mnt

Mount the second partition and enter it:

$ sudo mount -o loop,offset=<Partition 2 offset> maemo-leste-*-arm64-pinephone-*.img /mnt
$ cd /mnt

Use the editor of your choice to edit <code>etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.

Leave the second partition and unmount it:

$ cd ~
$ sudo umount /mnt

The image is now ready to be installed to the eMMC.

==== Install image to eMMC ====

Refer to the [https://wiki.pine64.org/index.php/PinePhone_Software_Release#Installation_to_eMMC_.28Optional.29 Pine64 Wiki].

[[Category:Device]]

Anbox

2021-01-18T15:57:24Z

Parazyd: /* Installation */

Getting Started

2021-01-18T14:57:17Z

Parazyd: /* More RAM */

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary. It's probably convenient to set allocation to 1024.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-01-18T14:53:26Z

Parazyd: /* More RAM */

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zramswap''' as necessary.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-01-18T14:46:18Z

Parazyd: /* (SSH) Login */

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

In images newer than 17 January 2021, root SSH is disabled by default.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zram''' as necessary.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Getting Started

2021-01-18T14:44:55Z

Parazyd:

= (SSH) Login =

User credentials are: '''user:user'''

Root credentials are: '''root:toor'''

You should prefer logging in as user and then escalating to root with sudo as necessary.

= Useful Bits =

* Default lockcode is "12345"
* Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.

= More RAM =

You can install '''zram-tools''' from the repo, and edit '''/etc/default/zram''' as necessary.
hildon-base (and it's hildon-env-setup initscript) are aware if zramswap in installed and will activate zram.
If you have an image older than 17 January 2021, you should remove the existing zram initscript and install zram-tools to utilize this functionality.

Remove it with:

rc-update del zram
rm /etc/init.d/zram

= Tweaking =

See [[Tweaking]]

Anbox

2021-01-18T14:22:11Z

Parazyd: /* Usage */

= Installation =

From extras

apt install anbox

Or install anbox from HAM.

= Usage =

The initscript should automatically start anbox container-manager.

supervise-daemon anbox-container-manager --start /usr/bin/anbox -- container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img
\_ /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img

As '''user''':

export ANBOX_LOG_LEVEL=debug
anbox session-manager

This should output:

user@devuan-pinephone:~$ anbox session-manager
[ 2021-01-18 14:20:08] [Renderer.cpp:165@initialize] Using a surfaceless EGL context
[ 2021-01-18 14:20:08] [Renderer.cpp:248@initialize] Successfully initialized EGL
[ 2021-01-18 14:21:03] [session_manager.cpp:264@operator()] Android successfully booted

In another terminal, also as '''user''':

anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

There is also an option with using '''anbox-launch.sh''' but I have not gotten it to work successfully.

Please note that '''it takes a long time to start''' an activity for the first time. So be patient. Subsequent runs should be faster.
You can view "progress" in htop. anbox should be using the CPU. When the usage is low, you should be ready to start activities.

You can also find some useful logs in /var/lib/anbox/logs

Anbox

2021-01-18T14:17:56Z

Parazyd: /* Usage */

= Installation =

From extras

apt install anbox

Or install anbox from HAM.

= Usage =

The initscript should automatically start anbox container-manager.

supervise-daemon anbox-container-manager --start /usr/bin/anbox -- container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img
\_ /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img

As '''user''':

export ANBOX_LOG_LEVEL=debug
anbox session-manager
anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

There is also an option with using '''anbox-launch.sh''' but I have not gotten it to work successfully.

Please note that '''it takes a long time to start''' an activity for the first time. So be patient. Subsequent runs should be faster.
You can view "progress" in htop. anbox should be using the CPU. When the usage is low, you should be ready to start activities.

You can also find some useful logs in /var/lib/anbox/logs

Anbox

2021-01-18T14:16:46Z

Parazyd: /* Usage */

Anbox

2021-01-18T14:16:17Z

Parazyd: /* Installation */

Anbox

2021-01-18T14:16:04Z

Parazyd:

= Installation =

From extras

apt install anbox

= Usage =

The initscript should automatically start anbox container-manager.

supervise-daemon anbox-container-manager --start /usr/bin/anbox -- container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img
\_ /usr/bin/anbox container-manager --daemon --privileged --data-path=/var/lib/anbox --android-image=/usr/share/anbox/android.img

As '''user''':

anbox session-manager
anbox launch --package=org.anbox.appmgr --component=org.anbox.appmgr.AppViewActivity

There is also an option with using '''anbox-launch.sh''' but I have not gotten it to work successfully.

Please note that '''it takes a long time to start''' an activity for the first time. So be patient. Subsequent runs should be faster.
You can view "progress" in htop. anbox should be using the CPU. When the usage is low, you should be ready to start activities.

Anbox

2021-01-18T14:15:15Z

Parazyd:

Anbox

2021-01-18T14:14:31Z

Parazyd: Created page with "= Installation = From extras apt install anbox = Usage = The initscript should automatically start anbox container-manager. supervise-daemon anbox-container-manager --s..."