https://leste.maemo.org/api.php?action=feedcontributions&feedformat=atom&user=HalftuxMaemo Leste Wiki - User contributions [en]2026-06-05T07:02:54ZUser contributionsMediaWiki 1.45.3https://leste.maemo.org/index.php?title=Main_Page&diff=1764Main Page2025-04-24T11:59:17Z<p>Halftux: /* Links */ added new git</p>
<hr />
<div>== Description ==<br />
<br />
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, PinePhone, Allwinner Tablets and more.<br />
<br />
You can find us on '''irc.libera.chat''', channel '''#maemo-leste''', you can [[IRC channel|use Matrix]] to connect if you wish.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Chimaera (Debian Chimaera) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
For some devices, we have development images available, such as the [[Nokia N900]], the [[Motorola Droid 4]] and the [[PinePhone]]. 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.<br />
<br />
If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.<br />
<br />
== Useful resources, lists and pages ==<br />
<br />
* To get started with a new install, see [[Getting_Started|Getting Started]].<br />
* Read our [[Leste_FAQ|Frequently Asked Questions]]<br />
* List of [[:Category:Device]] with support to varying degrees<br />
* Latest downloadable images: https://phoenix.maemo.org/view/Images/<br />
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras<br />
* Read how to get started with [[Development]]<br />
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]<br />
<br />
== Links ==<br />
<br />
<div><br />
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.<br />
<br />
* Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
* Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues] new: [https://git.maemo.org/leste/bugtracker/issues https://git.maemo.org/leste/bugtracker/issues]<br />
<br />
* Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/] new: [https://git.maemo.org/leste https://git.maemo.org/leste]<br />
<br />
* Our Github subdomain: [https://maemo-leste.github.io/ https://maemo-leste.github.io/]<br />
<br />
* Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/] new: [https://git.maemo.org/leste-extras https://git.maemo.org/leste-extras]<br />
<br />
* Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/<br />
<br />
* Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br />
<br />
* Our IRC chat history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://libera.irclog.whitequark.org/maemo-leste/ (previously: https://freenode.irclog.whitequark.org/maemo-leste/)<br />
<br />
* Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )<br />
<br />
* 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]<br />
<br />
* Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]<br />
<br />
* RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]<br />
<br />
* Our Twitter: [https://twitter.com/maemoleste @maemoleste]<br />
<br />
* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Image_Builder&diff=1727Image Builder2025-01-13T12:52:11Z<p>Halftux: /* Maemo 7 Leste */</p>
<hr />
<div>= How to build your own images =<br />
<br />
== Maemo 7 Leste ==<br />
<br />
'''[https://github.com/maemo-leste/image-builder Image Builder on Github]'''<br />
<br />
1.) Install the following packages (for libpython-dev you could choose libpython3-dev and create a symlink from python3 to python): <br />
<pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre><br />
<br />
<br />
1.1) For '''[https://github.com/maemo-leste/arm-sdk arm-sdk]''' you need these packages and sudo permissions are required for the user that is running the build.<br />
<pre><br />
zsh sudo cgpt parted xz-utils<br />
</pre><br />
<br />
<br />
1.2) If you're using a distribution that is not Devuan, you will have to add a beowulf/chimaera[default]/deadalus target to its scripts until the patch is merged upstream<br />
<pre><br />
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres<br />
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera<br />
</pre><br />
<br />
<br />
2.) In your terminal, run the following commands (where maemo is a symlink and could point to these blends beowulf, chimaera[default] or daedalus): <br />
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git<br />
$ cd image-builder/arm-sdk<br />
$ zsh -f<br />
$ source sdk<br />
$ load devuan DEVICE_NAME maemo<br />
$ build_arm_dist<br />
<br />
Note: replace <code>DEVICE_NAME</code> with your board name:<br />
<br />
* arm64-generic<br />
* <strike>beagleboneblack</strike><br />
* bionic<br />
* <strike>chromeacer</strike><br />
* <strike>chromeveyron</strike><br />
* mz617<br />
* n900<br />
* n950<br />
* n9<br />
* droid3<br />
* droid4<br />
* <strike>odroidxu</strike><br />
* <strike>odroidxu4</strike><br />
* <strike>ouya</strike><br />
* raspi1<br />
* raspi2<br />
* raspi3<br />
* raspi4<br />
* <strike>rock64</strike><br />
* pinephone-dontbeevil<br />
* pinephone<br />
* pinetab<br />
* pocophone-f1<br />
* sunxi<br />
* turbox-twister<br />
* xt910<br />
* xt912</div>Halftuxhttps://leste.maemo.org/index.php?title=Image_Builder&diff=1726Image Builder2025-01-13T12:47:17Z<p>Halftux: /* Maemo 7 Leste */</p>
<hr />
<div>= How to build your own images =<br />
<br />
== Maemo 7 Leste ==<br />
<br />
'''[https://github.com/maemo-leste/image-builder Image Builder on Github]'''<br />
<br />
1.) Install the following packages (for libpython-dev you could choose libpython3-dev and create a symlink from python3 to python): <br />
<pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre><br />
<br />
<br />
1.1) For '''[https://github.com/maemo-leste/arm-sdk arm-sdk]''' you need these packages and sudo permissions are required for the user that is running the build.<br />
<pre><br />
zsh sudo cgpt parted xz-utils<br />
</pre><br />
<br />
<br />
1.2) If you're using a distribution that is not Devuan, you will have to add a beowulf/chimaera[default]/deadalus target to its scripts until the patch is merged upstream<br />
<pre><br />
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres<br />
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera<br />
</pre><br />
<br />
<br />
2.) In your terminal, run the following commands (where maemo is a symlink and could point to these blends beowulf, chimaera[default] or daedalus): <br />
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git<br />
$ cd image-builder/arm-sdk<br />
$ zsh -f<br />
$ source sdk<br />
$ load devuan DEVICE_NAME maemo<br />
$ build_arm_dist<br />
<br />
Note: replace <code>DEVICE_NAME</code> with your board name:<br />
<br />
* arm64-generic<br />
* <strike>beagleboneblack</strike><br />
* bionic<br />
* <strike>chromeacer</strike><br />
* <strike>chromeveyron</strike><br />
* n900<br />
* n950<br />
* n9<br />
* droid3<br />
* droid4<br />
* <strike>odroidxu</strike><br />
* <strike>odroidxu4</strike><br />
* <strike>ouya</strike><br />
* raspi1<br />
* raspi2<br />
* raspi3<br />
* raspi4<br />
* <strike>rock64</strike><br />
* pinephone-dontbeevil<br />
* pinephone<br />
* pinetab<br />
* pocophone-f1<br />
* sunxi<br />
* turbox-twister</div>Halftuxhttps://leste.maemo.org/index.php?title=Image_Builder&diff=1725Image Builder2025-01-13T12:47:04Z<p>Halftux: /* Maemo 7 Leste */</p>
<hr />
<div>= How to build your own images =<br />
<br />
== Maemo 7 Leste ==<br />
<br />
'''[https://github.com/maemo-leste/image-builder Image Builder on Github]'''<br />
<br />
1.) Install the following packages (for libpython-dev you could choose libpython3-dev and create a symlink from python3 to python): <br />
<pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre><br />
<br />
<br />
1.1) For '''[https://github.com/maemo-leste/arm-sdk arm-sdk]''' you need these packages and sudo permissions are required for the user that is running the build.<br />
<pre><br />
zsh sudo cgpt parted xz-utils<br />
</pre><br />
<br />
<br />
1.2) If you're using a distribution that is not Devuan, you will have to add a beowulf/chimaera[default]/deadalus target to its scripts until the patch is merged upstream<br />
<pre><br />
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres<br />
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera<br />
</pre><br />
<br />
<br />
2.) In your terminal, run the following commands (where maemo is a symlink and could point to these blends beowulf, chimaera[default] or daedalus): <br />
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git<br />
$ cd image-builder/arm-sdk<br />
$ zsh -f<br />
$ source sdk<br />
$ load devuan DEVICE_NAME maemo<br />
$ build_arm_dist<br />
<br />
Note: replace <code>DEVICE_NAME</code> with your board name:<br />
<br />
* arm64-generic<br />
* <strike>beagleboneblack</strike><br />
* bionic<br />
* <strike>chromeacer</strike><br />
* <strike>chromeveyron</strike><br />
* n900<br />
* n950<br />
* n9<br />
* droid3<br />
* droid4<br />
* <strike>odroidxu</strike><br />
* <strike>odroidxu4</strike><br />
* </strike>ouya</strike><br />
* raspi1<br />
* raspi2<br />
* raspi3<br />
* raspi4<br />
* <strike>rock64</strike><br />
* pinephone-dontbeevil<br />
* pinephone<br />
* pinetab<br />
* pocophone-f1<br />
* sunxi<br />
* turbox-twister</div>Halftuxhttps://leste.maemo.org/index.php?title=Image_Builder&diff=1724Image Builder2025-01-09T15:43:53Z<p>Halftux: /* Maemo 7 Leste */</p>
<hr />
<div>= How to build your own images =<br />
<br />
== Maemo 7 Leste ==<br />
<br />
'''[https://github.com/maemo-leste/image-builder Image Builder on Github]'''<br />
<br />
1.) Install the following packages (for libpython-dev you could choose libpython3-dev and create a symlink from python3 to python): <br />
<pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre><br />
<br />
<br />
1.1) For '''[https://github.com/maemo-leste/arm-sdk arm-sdk]''' you need these packages and sudo permissions are required for the user that is running the build.<br />
<pre><br />
zsh sudo cgpt parted xz-utils<br />
</pre><br />
<br />
<br />
1.2) If you're using a distribution that is not Devuan, you will have to add a beowulf/chimaera[default]/deadalus target to its scripts until the patch is merged upstream<br />
<pre><br />
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres<br />
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera<br />
</pre><br />
<br />
<br />
2.) In your terminal, run the following commands (where maemo is a symlink and could point to these blends beowulf, chimaera[default] or daedalus): <br />
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git<br />
$ cd image-builder/arm-sdk<br />
$ zsh -f<br />
$ source sdk<br />
$ load devuan DEVICE_NAME maemo<br />
$ build_arm_dist<br />
<br />
Note: replace <code>DEVICE_NAME</code> with your board name:<br />
<br />
* arm64-generic<br />
* beagleboneblack<br />
* bionic<br />
* chromeacer<br />
* chromeveyron<br />
* n900<br />
* n950<br />
* n9<br />
* droid3<br />
* droid4<br />
* odroidxu<br />
* odroidxu4<br />
* ouya<br />
* raspi1<br />
* raspi2<br />
* raspi3<br />
* raspi4<br />
* rock64<br />
* pinephone-dontbeevil<br />
* pinephone<br />
* pinetab<br />
* pocophone-f1<br />
* sunxi<br />
* turbox-twister</div>Halftuxhttps://leste.maemo.org/index.php?title=Image_Builder&diff=1723Image Builder2025-01-09T13:09:50Z<p>Halftux: /* Maemo 7 Leste */</p>
<hr />
<div>= How to build your own images =<br />
<br />
== Maemo 7 Leste ==<br />
<br />
'''[https://github.com/maemo-leste/image-builder Image Builder on Github]'''<br />
<br />
1.) Install the following packages (for libpython-dev you could choose libpython3-dev and create a symlink from python3 to python): <br />
<pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre><br />
<br />
<br />
1.1) For '''[https://github.com/maemo-leste/arm-sdk arm-sdk]''' you need these packages and sudo permissions are required for the user that is running the build.<br />
<pre><br />
zsh sudo cgpt parted xz-utils<br />
</pre><br />
<br />
<br />
1.2) If you're using a distribution that is not Devuan, you will have to add a beowulf/chimaera[default]/deadalus target to its scripts until the patch is merged upstream<br />
<pre><br />
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres<br />
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera<br />
</pre><br />
<br />
<br />
2.) In your terminal, run the following commands (where maemo is a symlink and could point to these blends beowulf, chimaera[default] or daedalus): <br />
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git<br />
$ cd image-builder/arm-sdk<br />
$ zsh -f<br />
$ source sdk<br />
$ load devuan DEVICE_NAME maemo<br />
$ build_arm_dist<br />
<br />
Note: replace <code>DEVICE_NAME</code> with your board name:<br />
<br />
* beagleboneblack<br />
* chromeacer<br />
* chromeveyron<br />
* n900<br />
* n950<br />
* n9<br />
* droid3<br />
* droid4<br />
* bionic<br />
* odroidxu<br />
* odroidxu4<br />
* ouya<br />
* raspi1<br />
* raspi2<br />
* raspi3<br />
* raspi4<br />
* rock64<br />
* pinephone-dontbeevil<br />
* pinephone<br />
* pinetab<br />
* sunxi<br />
* turbox-twister</div>Halftuxhttps://leste.maemo.org/index.php?title=PinePhone&diff=1722PinePhone2025-01-05T15:06:31Z<p>Halftux: Added information, specifications and picture</p>
<hr />
<div>{{Stub}}<br />
<br />
{{Infobox Device<br />
|image=[[File:Phinephone_leste.jpg|250px]]<br />
|manufacturer=Pine64<br />
|codename=<br />
|dimensions=160.5x76.6x9.2mm<br />
|release_date=<br />
|soc=Allwinner A64 <br>Cortex-A53 <br>arm64v8<br />
|dram=2GB or 3GB LPDDR3 SDRAM<br />
|power=<br />
|lcd=1440x720 5.95″<br />
|video=ARM Mali 400 MP2 GPU<br />
|audio=<br />
|network=<br />
|storage=16GB or 32GB eMMC<br />
|usb=<br />
|camera=GalaxyCore GC2145, <br>OmniVision OV5640<br />
|sensors=ST LIS3MDL compass, <br>InvenSense MPU-6050 accelerometer, <br>SensorTek STK3335 proximity and illuminance<br />
|other=<br />
}}<br />
<br />
This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro. <br />
<br />
== Notes ==<br />
<br />
Go here for '''[https://maedevu.maemo.org/images/pinephone/ latest images to test.] ''' Please [[Main_Page#Links|get in touch with us]] to report any issues or learn how to help out with the project.<br />
<br />
== Status ==<br />
<br />
Currently, most things work, for example you can:<br />
<br />
* Run any applications in Debian and Devuan on your phone<br />
* Connect to wifi<br />
* Use the terminal<br />
* Connect to 2G/3G/4G data connections<br />
* Make and receive phone calls and SMS<br />
* PinePhone keyboard is supported<br />
<br />
<br />
{| class="wikitable"<br />
! Feature<br />
! Leste supported<br />
! Notes<br />
|-<br />
| Kernel version || 5.15 || Mainline + some patches: https://github.com/maemo-leste/pine64-kernel<br />
|-<br />
| Serial || Yes || Via headphone jack (disable headphone switch)<br />
|-<br />
| Charging || Yes ||<br />
|-<br />
| Wireless || Yes || Involves installing out of tree driver<br />
|-<br />
| Ethernet || N/A || ps: USB Ethernet adapter tested and works<br />
|-<br />
| Bluetooth || YES || No UI integration yet<br />
|-<br />
| Infrared || N/A || TX only (hardware limitation). <br />
|-<br />
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested<br />
|-<br />
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box<br />
|-<br />
| Screen || Yes || Modesetting driver<br />
|-<br />
| 3D Acceleration || Yes || mesa-lima<br />
|-<br />
| Touchscreen || Yes || Capacitive<br />
|-<br />
| Audio || Yes || Pulseaudio and UCM units<br />
|-<br />
| 2G/3G/4G data || YES || Works with ofono;<br />
|-<br />
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available<br />
|-<br />
| Phone calls || YES || Works with ofono; Calls work with sphone as UI<br />
|-<br />
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed<br />
|-<br />
| Accelerometer || Yes ||<br />
|-<br />
| Proximity sensor || Yes || <br />
|-<br />
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.<br />
|-<br />
| Vibration Motor || ? || <br />
|-<br />
| GPS || WIP || Works with WIP Leste GPS stack<br />
|-<br />
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.<br />
|}<br />
<br />
=== More Information ===<br />
<br />
* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).<br />
* Default virtual keyboard is set to on. You can check by tapping the top left corner->"Settings"->"Text input"-> ensure the "Use virtual keyboard" option is checked. You may also want to change the keyboard layout by changing the dictionary settings.<br />
* WiFi and terminal work.<br />
* 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.<br />
* 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><br />
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.<br />
* Many "games" packages in the Application Manager don't work well yet.<br />
* '''VoLTE should work out-of-the-box.''' If not, please set the VoLTE profile via AT commands. For example, for T-Mobile in US, do:<br />
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -<br />
In order to list all specific VoLTE profiles, use:<br />
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -<br />
To enable calling out over VoLTE, use:<br />
$ echo 'AT+QCFG="ims",1' | atinout - /dev/EG25.AT -<br />
Reboot the modem by rebooting the phone.<br />
<br />
== Installation ==<br />
Unlike most phones, it's pretty simple.<br />
<br />
=== SD Card Installation ===<br />
==== Prepare the SD card ====<br />
<br />
Create a new msdos partition table using fdisk<br />
<br />
$ sudo fdisk /dev/''SDCARD'' <br />
# press 'p' to view current table<br />
# press 'o' to erase and make a new table<br />
# press 'w' to write changes and quit<br />
<br />
==== Write the image to an SD-Card. ====<br />
<br />
Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here]. <br />
<br />
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''<br />
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''<br />
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz<br />
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56<br />
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:<br />
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz<br />
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.<br />
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync<br />
Block size set to 4M will work most of the time. If not, try 1M, although this will take considerably longer. Do not use partition numbers, or it won't boot. 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.<br />
<br />
<small>Make absolutely 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 device you selected, make sure it is the correct one. You can use Gnome Disks, gparted, [https://etcher.io/ Etcher], etc...your choice. Again, as with all of these tools, be careful to select the microSD card not your computer hard drive.</small><br />
<br />
=== eMMC Installation ===<br />
'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.<br />
==== Preparing the .img file for eMMC boot ====<br />
<br />
Download the .img.xz version of the image and extract it:<br />
<br />
$ unxz -k maemo-leste-*-arm64-pinephone-*.img.xz<br />
<br />
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, mount the image to a loop device.<br />
<br />
$ sudo losetup -P /dev/loop0 maemo-leste-*-arm64-pinephone-*.img<br />
<br />
Mount the second partition to /mnt and the first partition to /mnt/boot and enter /mnt:<br />
<br />
$ sudo mount /dev/loop0p2 /mnt<br />
$ sudo mount /dev/loop0p1 /mnt/boot<br />
$ cd /mnt<br />
<br />
Use the editor of your choice to edit <code>/mnt/etc/fstab</code>, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code>.<br />
<br />
Now we need to edit <code>boot.scr</code>. For that you will need to download <code>boot.txt</code> from Maemo Leste github:<br />
<br />
$ cd /mnt/boot<br />
$ sudo wget https://raw.githubusercontent.com/maemo-leste/pine64-uboot/master/boot.txt<br />
<br />
Now we do the same step as we did for the fstab, replacing <code>/dev/mmcblk0</code> with <code>/dev/mmcblk2</code> in <code>boot.txt</code>.<br />
<br />
<br />
To regenerate <code>boot.scr</code> you need to install <code>u-boot-tools</code> first to be able to use mkimage.<br />
<br />
Regenerate <code>boot.scr</code>:<br />
<br />
$ sudo mkimage -A arm -O linux -T script -C none -a 0 -e 0 -d boot.txt boot.scr<br />
<br />
Leave /mnt and unmount the partitions:<br />
<br />
$ cd ~<br />
$ sudo umount -R /mnt<br />
<br />
We can now save the image we just modified using dd:<br />
<br />
$ sudo dd if=/dev/loop0 of=maemo-leste-1.0-arm64-pinephone-EMMC.img<br />
<br />
The image is now ready to be installed to the eMMC.<br />
<br />
We can now remove the loop device we created earlier:<br />
<br />
$ sudo losetup -d /dev/loop0<br />
<br />
==== Install Using Tow-Boot ====<br />
<br />
If you [https://tow-boot.org/devices/pine64-pinephoneA64.html flashed tow-boot to the PinePhone] the eMMC can be flashed by holding vol+ on startup to boot into USB Mass Storage mode.<br />
<br />
The process of flashing Maemo Leste to the eMMC is identical to that of any other storage medium - e.g. a microSD card. You can use the <i>dd</i> command or a utility such as Etcher or Gnome Disks, etc.<br />
<br />
==== Install Using JumpDrive ====<br />
<br />
You can flash Maemo Leste to eMMC using JumpDrive. This utility boots from microSD and exposes the internal eMMC flash storage when the PinePhone is connected to a computer.<br />
<br />
The process of flashing Maemo Leste to the exposed and mounted eMMC is identical to that of any other storage medium - e.g. a microSD card. <br />
<br />
[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]<br />
<br />
==== Install from the booted microSD ====<br />
# Flash Maemo Leste to the microSD card<br />
# Insert microSD card and boot the phone<br />
# Download the latest Maemo Leste image on the booted OS; if you get errors during download, you'll have to expand the partition; and don't forget to re-check the checksums when you download.<br />
# Extract the image file so that it only ends in ".img"<br />
# Flash the image file to eMMC using <code>dd if='''IMAGE.img''' of=/dev/'''mmcblkX''' bs=1M status=progress conv=fsync</code> where X is the number label of the eMMC (of the disk, not the partition!). Use the command <code>lsblk</code> to check your devices: typically with the current kernel the microSD card is ''/dev/mmcblk0'' and the eMMC is ''/dev/mmcblk2'' but as always with ''dd'' be extremely cautious to get the devices correct. <br />
# Turn off phone, remove microSD card and then turn on the phone.<br />
<br />
== Post-Installation ==<br />
<br />
=== How to take a picture ===<br />
<br />
Maemo userland to take pictures or make videos is ready yet. The default camera app is pinhole: https://github.com/piggz/harbour-pinhole/<br />
<br />
Both cameras (rear and front) are supported. Work in ongoing to improve the camera app.<br />
<br />
To open the (pinhole) camera from the terminal:<br />
$ harbour-pinhole<br />
<br />
Or open it from Maemo desktop "Camera" icon.<br />
<br />
In order to trigger auto-focus:<br />
$ v4l2-ctl -d /dev/v4l-subdev1 -c focus_automatic_continuous=1<br />
<br />
Or trigger autofocus using the commands to start and stop manually:<br />
$ v4l2-ctl -d /dev/v4l-subdev1 -c auto_focus_start=1<br />
<br />
then wait till it gets the focus where you want, then <br />
$ v4l2-ctl -d /dev/v4l-subdev1 -c auto_focus_stop=1<br />
<br />
You can use this script as reference to take a picture:<br />
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup<br />
<br />
Or use libcamera tools (libcamera-tools package). To list the cameras:<br />
$ cam -l<br />
<br />
Example to capture 10 pictures with the rear camera:<br />
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10<br />
<br />
Example to capture 10 pictures with the front camera:<br />
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10<br />
<br />
And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:<br />
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg<br />
<br />
Other option is to use "cam" to capture to DNG. Example:<br />
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/frame-#.dng --capture=10<br />
<br />
And then convert to .ppm (for .tiff use "-T" cmd line parameter). Eg:<br />
$ dcraw frame-cam0-stream0-000001.dng<br />
<br />
Also the graphical tool "qcam" is working! Run it with:<br />
$ qcam -r gles -spixelformat=NV21,width=1280,height=720 -platform xcb -style=fusion<br />
<br />
=== Enabling Flash Light / Torch ===<br />
<br />
Enable:<br />
$ echo 1 > /sys/class/leds/white:flash/brightness<br />
<br />
Disable:<br />
$ echo 0 > /sys/class/leds/white:flash/brightness<br />
<br />
Trigger flash strobe:<br />
$ echo 1 > /sys/class/leds/white:flash/flash_strobe<br />
<br />
=== PinePhone Keyboard ===<br />
<br />
First of all, make sure you have the latest firmware loaded in the keyboard (firmware is here: https://github.com/maemo-leste-upstream-forks/pinephone-keyboard/tree/master/firmware/build and userland here: https://github.com/maemo-leste-upstream-forks/pinephone-keyboard ):<br />
<br />
$ ppkb-i2c-flasher -e i2c -i fw-user.bin write reset<br />
<br />
Load the xkb layout ( available here: https://codeberg.org/phalio/ppkb-layouts/src/branch/main/xkb )<br />
<br />
$ setxkbmap pp altgr<br />
<br />
=== Suspend ===<br />
<br />
Suspend can be triggered with:<br />
$ echo mem > /sys/power/state<br />
<br />
A temporary workaround for calling suspend from UI is here: https://github.com/rafael2k/maemo-suspend/<br />
<br />
=== Volume Applet ===<br />
<br />
Volume applet ( https://github.com/maemo-leste/maemo-statusmenu-volume ) needs a change in "sink_name" at "/usr/share/maemo-statusmenu-volume/sinks.ini". Edit the sinks.ini in order the sink_name is:<br />
<br />
sink_name=alsa_output.0.HiFi__hw_PinePhone_0__sink<br />
<br />
=== Installing apps ===<br />
<br />
* Apps can be installed just as on any Devuan system with:<br />
$ sudo apt install ''package-name''<br />
* There is also the app store.<br />
<br />
=== Launching apps ===<br />
<br />
This works for any app. Say for instance, you want to run Iceweasel/Firefox:<br />
<br />
* Launch apps from the desktop<br />
* Launch apps from your console:<br />
$ iceweasel &<br />
* Install a universal app launcher that you can run from desktop:<br />
$ sudo apt install desktop-cmd-exec<br />
<br />
=== Make apps show up on desktop ===<br />
<br />
Apps installed via apt, or otherwise not installed from the app store, don't come with desktop icons pre-configured and so won't show up on the desktop. If you want desktop icons for your apps, you have to edit .desktop files for the apps you want to show up on the desktop, see ([https://wiki.archlinux.org/title/Desktop_entries examples])<br />
<br />
To view a list of currently installed apps, do:<br />
<br />
$ sudo apt list --installed | less<br />
<br />
This should help you figure out for which apps to configure .desktop icons. A benefit with all this is that you can decide which apps you want to show or hide.<br />
<br />
=== Unhide the keyboard ===<br />
<br />
The virtual keyboard can be summoned by hitting the volume-up key while the cursor is in a text field (such as the URL bar in a web browser like Firefox). This will be fixed in a future release (image tested: 20220731).<br />
<br />
=== Note about Calculator ===<br />
<br />
The default GUI calculator works (08/15/2022) but you won't see the numbers appear on screen until after you touch the next key. It should be used in landscape mode for best results, as there are additional display issues in portrait mode.<br />
<br />
=== Time zone / World Clock ===<br />
<br />
Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to: <br />
<br />
* Go to Settings > Date and Time > and adjust time zone and date and time there. This also has some bugs, but only in portrait mode.<br />
<br />
* Or just use the console:<br />
<br />
$ sudo date -s HH:MM<br />
$ sudo date -s YYYYMMDD<br />
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime<br />
<br />
<br />
<br />
=== More Tips & Tricks ===<br />
<br />
Visit [https://leste.maemo.org/Tricks '''this page'''] for more general advice on customizing Maemo on your PinePhone.<br />
<br />
[[Category:Device]]</div>Halftuxhttps://leste.maemo.org/index.php?title=File:Phinephone_leste.jpg&diff=1721File:Phinephone leste.jpg2025-01-05T14:56:35Z<p>Halftux: Just an initial picture of the Phinephone running Maemo Leste</p>
<hr />
<div>== Summary ==<br />
Just an initial picture of the Phinephone running Maemo Leste</div>Halftuxhttps://leste.maemo.org/index.php?title=Nokia_N900&diff=1568Nokia N9002023-10-20T11:13:10Z<p>Halftux: </p>
<hr />
<div>{{Infobox Device<br />
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]<br />
|manufacturer=Nokia<br />
|codename=Rover, RX-51<br />
|dimensions=110.9mm x 59.8mm x 18mm<br />
|release_date=2009-11-11<br />
|category=Supported<br />
|soc=TI OMAP 3430 @600MHz <br>overclock @850MHz <br>Cortex-A8 <br>Armv7‑A<br />
|dram=256 MB Mobile DDR<br />
|power=<br />
|lcd=800x480 3.5" Resistive TFT<br />
|video=PowerVR SGX530<br />
|audio=<br />
|network=WL1251<br />
|storage=32GB<br />
|usb=Micro USB 2.0 Slave<br />
|camera=<br />
|sensors=<br />
|other=<br />
|headers=<br />
|battery=1320mAh<br />
|sw_kernel=6.1<br />
|sw_serial=Yes, UART under battery, 2.7V max!<br />
|sw_charging=Yes<br />
|sw_usb_slave=Gadgets only<br />
|sw_usb_host=With hacks<br />
|sw_touchscreen=Yes, single-touch<br />
|sw_keyboard=Yes<br />
|sw_screen=Yes<br />
|sw_hdmi=<br />
|sw_tv=Yes<br />
|sw_3daccel=Yes, closed driver<br />
|sw_vibration=Yes<br />
|sw_audio=Yes (complex, ucm, no speaker protection)<br />
|sw_calls=Yes/WIP<br />
|sw_sms=Yes<br />
|sw_wifi=Yes, firmware required<br />
|sw_ethernet=<br />
|sw_irda=Yes, actually CIR, not IrDA<br />
|sw_2g3gdata=Yes<br />
|sw_4gdata=<br />
|sw_bluetooth=No<br />
|sw_fmtx=Yes<br />
|sw_fmrx=No<br />
|sw_nfc=<br />
|sw_accelerometer=Yes<br />
|sw_compass=<br />
|sw_gyro=<br />
|sw_proximity=Yes<br />
|sw_als=Yes<br />
|sw_gps=Yes<br />
|sw_agps=No<br />
|sw_frontcam=<br />
|sw_backcam=<br />
|sw_idlepower=160mW (WIP)<br />
|sw_standbytime=<br />
}}<br />
<br />
== Installation ==<br />
<br />
The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.<br />
<br />
=== Image installation ===<br />
<br />
* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/<br />
* Image archive: https://maedevu.maemo.org/images/n900/<br />
<br />
dd the image to an sd card.<br />
<br />
If using a Windows machine, you can use [https://etcher.io/ Etcher]<br />
<br />
See the next section on how to boot. (using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613)<br />
<br />
=== Bootloader (U-Boot) setup ===<br />
<br />
==== Quick ====<br />
<br />
If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly:<br />
<br />
1. Either download 0xFFFF (binary for x86) from https://maedevu.maemo.org/images/n900/tools/ or build from source from https://github.com/pali/0xFFFF/<br />
<br />
2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/<br />
<br />
3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code><br />
<br />
4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code><br />
<br />
This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.<br />
<br />
To flash u-boot permanently, you can issue the following command<br />
<br />
'''(Be careful though. This will replace the existing fremantle kernel. Only do this if you do not care about the existing maemo installation or you know how to recover from this condition)''')<br />
<br />
<code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f</code><br />
<br />
==== Existing Fremantle ====<br />
<br />
If you have a functional Fremantle installation, you can follow these steps instead:<br />
<br />
1. Install "U-Boot with kernel 2.6.28-omap1"<br />
<br />
2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.<br />
<br />
3. Add Maemo Leste menu item (run as root):<br />
cat > /etc/bootmenu.d/30-maemo-leste.item << "EOF" &&<br />
ITEM_NAME="Maemo Leste"<br />
ITEM_KERNEL="uImage"<br />
ITEM_DEVICE="${EXT_CARD}p1"<br />
ITEM_FSTYPE="ext2"<br />
EOF<br />
u-boot-update-bootmenu<br />
<br />
4. Reboot the device with the keyboard slide open (U-boot will boot the default option if the keyboard slide is closed)<br />
<br />
<br />
=== Increase filesystem size ===<br />
<br />
Run the following script: <code>/etc/expandcard.sh</code><br />
<br />
== Serial ==<br />
<br />
http://n900.elektranox.org/serial-adapter.html<br />
<br />
http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports<br />
<br />
Use this command line (specifically the part after rootwait):<br />
<br />
<pre><br />
root=/dev/mmcblk0p2 rootwait console=ttyS2,115200 verbose earlyprintk debug<br />
</pre><br />
<br />
== Notes ==<br />
=== Speakers ===<br />
<br />
* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them. There is no clear consensus about this, but it is best to err on the side of caution.<br />
=== Torch ===<br />
<br />
The N900 has an Analog Devices ADP1653 flash controller, mainly for use with the camera. It drives two white power LEDs connected in series, and has an additional red indicator led (referred to as a privacy indicator). The ADP1653 has a driver in mainline kernel, and it probes fine. However, some DTS changes are needed to make it work, since the driver requires it to be tied to a camera.<br />
<br />
In the meantime, the LEDs can be used as a torch manually using <code>i2cset</code>. <br />
However, '''BE WARNED:''' setting wrong values via i2c runs the risk of over-driving the LEDs and causing permanent hardware damage.<br />
<br />
<source lang="shell-session"><br />
Install the prerequisites<br />
$ sudo apk add i2c-tools<br />
<br />
Unload the driver in case it is already loaded. We will use i2c manually<br />
$ sudo modprobe -r adp1653<br />
<br />
Enable the chip<br />
$ echo 88 | sudo tee /sys/class/gpio/export<br />
$ echo "out" | sudo tee /sys/class/gpio/gpio88/direction<br />
$ echo 1 | sudo tee /sys/class/gpio/gpio88/value<br />
<br />
Turn the torch on, using the lowest torch current - DO NOT use other values here or you risk burning the LED<br />
Values between 1 and 7 enable the red privacy/recording led, with different intensity<br />
0x8 is the lowest torch intensity, and we do not recommend going above it<br />
$ sudo i2cset -y 2 0x30 0x0 0x8<br />
<br />
Turn the torch off<br />
$ sudo i2cset -y 2 0x30 0x0 0x0<br />
<br />
Disable the chip<br />
$ echo 0 | sudo tee /sys/class/gpio/gpio88/value<br />
$ echo 88 | sudo tee /sys/class/gpio/unexport<br />
</source><br />
<br />
== Power Management ==<br />
<br />
This ticket tracks hitting idle states for the N900: https://github.com/maemo-leste/bugtracker/issues/545<br />
<br />
Power usage right now is reported to be about 45mA (idle, modem ON and data ON). On a good battery this will last for about 30 hours. Power management on the N900 is being worked on: https://github.com/maemo-leste/bugtracker/issues/170<br />
<br />
* https://wiki.maemo.org/N900_Hardware_Power_management<br />
* https://wiki.maemo.org/N900_Hardware_Power_Consumption<br />
<br />
<br />
Run:<br />
<br />
modprobe ledtrig-default-on<br />
<br />
And:<br />
<br />
echo default-on > /sys/class/leds/debug::sleep/trigger<br />
<br />
To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.<br />
<br />
Currently it does not yet reliably reach any sleep modes.<br />
<br />
See this code for a work in progress power management script: https://github.com/maemo-leste/n900-pm<br />
<br />
== Battery calibration ==<br />
<br />
Nokia N900 has bq27200 integrated circuit for monitoring battery state. The datasheet can be found here: http://www.ti.com/lit/ds/symlink/bq27200.pdf. If you are curious, check the section called "Gas Gauge Operation" for how the battery calibration is done in a low level.<br />
<br />
Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.<br />
<br />
* Fully charge Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).<br />
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).<br />
* You may use the device as you normally do. You may power it off, power it on, reboot. All as usual. Just don't connect the device to a charger or a PC using the USB cable.<br />
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.<br />
* Wait for about 20 seconds and attach the charger. If the device was powered off because of battery depletion, it's fine. The battery should have done the calibration cycle. Just attach the charger to the device, give it a minute and press power button to start booting.<br />
* If you still see "Battery not calibrated" message, reboot the device.<br />
<br />
After the first calibration cycle you will see that it has ~1700 mAh for the fully charged battery. This value is wrong. It's how the battery calibration works in low level: it can't change the fully charged value of the battery in steps that exceed 12.5%. What this means for us: it's needed to repeat the calibration cycle several times to get more accurate value. It may take about 3-7 calibration cycles to get the proper mAh value for fully charged battery. If you spend some time on this process, you will get really accurate battery gauge and you will always know how much charge is remaining.<br />
<br />
Tip 1. If for any reason you want to reset the battery calibration value to see the message “Battery is not calibrated” again, you should remove the battery from the device for about 6 hours.<br />
Tip 2. If you replace the battery, you may want to do 1-2 calibration cycles described above to update the gauge for your new battery.<br />
<br />
== Accessing MTD ==<br />
<br />
List devices:<br />
cat /proc/mtd<br />
<br />
Mount:<br />
apt install mtd-utils<br />
mkdir -vp /mnt/fremantle<br />
ubiattach -p /dev/mtd5<br />
mount -t ubifs ubi:rootfs /mnt/fremantle<br />
<br />
== Overclocking ==<br />
<br />
Nokia N900 with Leste is stable using following scalable frequencies and is much, much faster:<br />
<br />
250-500-600-720-850MHz<br />
<br />
To be able to overclock two steps are needed:<br />
<br />
1) From Fremantle: add new Maemo Leste menu item (run as root):<br />
<br />
cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&<br />
ITEM_NAME="Maemo Leste Overclock"<br />
ITEM_KERNEL="uImageX"<br />
ITEM_DEVICE="${EXT_CARD}p1"<br />
ITEM_FSTYPE="ext2"<br />
EOF<br />
u-boot-update-bootmenu<br />
<br />
2) From Maemo Leste (run as root):<br />
<br />
<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code><br />
<br />
<code>dtc -I dtb -O dts /home/user/omap3-n900.dtb -o /home/user/omap3-n900.dts</code><br />
<br />
(wait for a few seconds...)<br />
<br />
<code>chmod +w /home/user/omap3-n900.dts</code><br />
<br />
(then the funny part...)<br />
<br />
<code>nano /home/user/omap3-n900.dts</code><br />
<br />
(Now it's time to modify frequencies and voltage: be careful to do exactly the same)<br />
<br />
Find "opp-table" with <code>ctl+w</code> and Replace all content in "opp-table { opp1 opp2 opp3 opp4 opp5 opp6 };" <br />
<br />
New opp-table:<br />
<br />
<pre>opp-table {<br />
compatible = "operating-points-v2-ti-cpu";<br />
syscon = < 0x05 >;<br />
phandle = < 0x03 >;<br />
<br />
opp1-250000000 {<br />
opp-hz = < 0x00 0xee6b280 >;<br />
opp-microvolt = < 0xee098 0xee098 0xee098 >;<br />
opp-supported-hw = < 0xffffffff 0x03 >;<br />
};<br />
<br />
opp2-500000000 {<br />
opp-hz = < 0x00 0x1dcd6500 >;<br />
opp-microvolt = < 0x106738 0x106738 0x106738 >;<br />
opp-supported-hw = < 0xffffffff 0x03 >;<br />
opp-suspend;<br />
};<br />
<br />
opp3-600000000 {<br />
opp-hz = < 0x00 0x23c34600 >;<br />
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;<br />
opp-supported-hw = < 0xffffffff 0x03 >;<br />
};<br />
<br />
opp4-720000000 {<br />
opp-hz = < 0x00 0x2aea5400 >;<br />
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;<br />
opp-supported-hw = < 0xffffffff 0x03 >;<br />
};<br />
<br />
opp5-850000000 {<br />
opp-hz = < 0x00 0x32a9f880 >;<br />
opp-microvolt = < 0x149970 0x149970 0x149970 >;<br />
opp-supported-hw = < 0xffffffff 0x03 >;<br />
};<br />
<br />
opp6-720000000 {<br />
opp-hz = < 0x00 0x2aea5400 >;<br />
opp-microvolt = < 0x149970 0x149970 0x149970 >;<br />
opp-supported-hw = < 0xffffffff 0x02 >;<br />
turbo-mode;<br />
};<br />
};</pre><br />
<br />
Then <code>ctl+x</code> to save and close.<br />
<br />
And still as root:<br />
<br />
<code>rm /home/user/omap3-n900.dtb</code><br />
<br />
<code>dtc -I dts -O dtb /home/user/omap3-n900.dts -o /home/user/omap3-n900.dtb</code><br />
<br />
<br />
Check your kernel version:<br />
<br />
<code>uname -r</code><br />
<br />
For example if the result is 6.1.30, your vmlinuz version is vmlinuz-6.1.30<br />
<br />
In the next command, replace "vmlinuz-<version>" by yours (ie vmlinuz-6.1.30)<br />
<br />
As root:<br />
<br />
<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code><br />
<br />
<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code><br />
<br />
That's it !<br />
<br />
Now reboot and select "Maemo Leste Overclock in bootmenu".<br />
<br />
<br />
('''WARNING:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))<br />
<br />
<br />
Installing cpufrequtils is useful to change frequency governors.<br />
<br />
Prefer "conservative" instead of "ondemand" governor.<br />
<br />
"Performance" governor locks N900 at 850MHz.<br />
<br />
As root<br />
<code>cpufreq-set -c 0 -g conservative</code><br />
<br />
== Tips / Tweaks ==<br />
<br />
<br />
=== SD Card ===<br />
<br />
To avoid overall slowness, please only use SDHC Class 10 or better.<br />
<br />
=== Social messaging ===<br />
<br />
Conversations app is compatible with libpurple and irc/bitlbee server.<br />
<br />
Twitter, Signal, Telegram, FB Messenger and others are working.<br />
<br />
(most audio and video links are playable)<br />
<br />
=== Video playing ===<br />
<br />
Video playing is working fine using SMPLAYER:<br />
<br />
- In Options / Preferences / General:<br />
<br />
Media engine: Other: /user/bin/mplayer<br />
<br />
- In Options / Preferences / Video:<br />
<br />
Output driver: xv<br />
<br />
Only unable Double buffering and Disable screensaver<br />
<br />
<br />
- In Options / Preferences / Audio:<br />
<br />
Output driver: pulse<br />
<br />
Disable everything else<br />
<br />
Channel by default: 2 (Stereo)<br />
<br />
High speed playback: No<br />
<br />
- In Options / Preferences / Performance:<br />
<br />
Unable Allow frame drop<br />
<br />
Hardware decoding: None<br />
<br />
Prefer 360p - 480p max video format<br />
<br />
(With overclocking, Video is working well using KODI 17.6 with equivalent A/V settings)<br />
<br />
=== Tweaking Transitions ===<br />
<br />
Many options are missing in CSSU Features package but it is possible to edit them in transitions.ini.<br />
<br />
As root<br />
<br />
<code>nano /usr/share/hildon-desktop/transitions.ini</code><br />
<br />
See Fremantle documentation for perfect setup.<br />
<br />
=== More SWAP / SWAP activation ===<br />
<br />
To enable swap on eMMC 768MB partition if not already activated on first boot (works on the fly):<br />
<br />
<pre>sudo swapon /dev/mmcblk1p3</pre><br />
<br />
<br />
Other possibility: create a simple 1GB swap file on the SDcard if swap is missing:<br />
<br />
<pre>sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576</pre><br />
<br />
(It takes some time...)<br />
<br />
<pre>sudo chmod 600 /swapfile</pre><br />
<br />
<pre>sudo mkswap /swapfile</pre><br />
<br />
<pre>sudo swapon /swapfile</pre><br />
<br />
To make the change permanent open:<br />
<br />
<pre>sudo nano /etc/fstab</pre><br />
<br />
And add this line:<br />
<br />
<pre>/swapfile swap swap defaults 0 0</pre><br />
<br />
To check if the swap is active:<br />
<br />
<pre>sudo swapon --show</pre><br />
<br />
=== Web browsing ===<br />
<br />
Links2 is currently the fastest and the most usable web browser on N900 -using few tweaks-<br />
<br />
<pre>sudo apt install links2</pre><br />
<br />
To use it in graphical mode, run in terminal:<br />
<br />
<pre>links2 -g</pre> or press the hildon desktop icon.<br />
<br />
<br />
Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-<br />
<br />
<br />
Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.<br />
<br />
=== Retroarch ===<br />
<br />
'''First things to do:'''<br />
<br />
Edit <pre>/home/user/.config/retroarch/retroarch.cfg</pre><br />
<br />
menu_driver = "glui"<br />
<br />
menu_show_core_updater = "true"<br />
<br />
video_driver = "gl"<br />
<br />
video_vsync = "true"<br />
<br />
menu_unified_control = "true"<br />
<br />
menu_core_enable = "true"<br />
<br />
quick_menu_show_options = "true"<br />
<br />
<br />
'''Some emulators are working well:<br />
'''<br />
<br />
- QuickNES (NES/Famicom)<br />
<br />
- Snes9x 2005 (SNES/Super Famicom)<br />
<br />
Others at 70-80% speed:<br />
<br />
- Genesis Plus GX (SEGA MS/GG/MD/CD)<br />
<br />
Go to Online Updater / Core Updater to download emulators<br />
<br />
'''Retroarch recommended settings:'''<br />
<br />
To avoid crashes, use only "glui" Menu Driver<br />
<br />
'''Driver'''<br />
<br />
Input driver "X", joypad driver "linuxraw", video driver "gl", audio driver "null", location driver "null"<br />
<br />
'''Video'''<br />
<br />
Aspect ratio "core provided", Integer scaler "no", Threaded Video "yes", Vertical Sync "yes", Hard gpu Sync "no", <br />
<br />
'''Audio'''<br />
<br />
Audio Enable "no"<br />
<br />
'''Input''' (very important)<br />
<br />
Unified Menu Controls "yes"<br />
<br />
Input User 1 Binds (keyboard settings)<br />
<br />
'''Directory''' (very important)<br />
<br />
Core "/home/user"<br />
<br />
'''Default keyboard keys'''<br />
<br />
'''X''' validate/ok<br />
<br />
'''C''' cancel/back<br />
<br />
'''F''' fullscreen (never close Retroarch in fullscreen mode)<br />
<br />
== Status table ==<br />
<br />
{| class="wikitable"<br />
! Feature<br />
! Leste supported<br />
! Notes<br />
|-<br />
| Kernel version || 6.1.48 || Mainline + PowerVR Patches: https://github.com/maemo-leste/droid4-linux<br />
|-<br />
| Serial || Yes || Requires special hardware<br />
|-<br />
| Charging || Yes ||<br />
|-<br />
| Wireless || Yes || Firmware is non-free<br />
|-<br />
| Ethernet || N/A ||<br />
|-<br />
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible<br />
|-<br />
| Keyboard || Yes ||<br />
|-<br />
| Screen || Yes ||<br />
|-<br />
| 3D Acceleration || Yes || closed PowerVR driver<br />
|-<br />
| Overclock || Yes || up to 850MHz (stable), Turbo mode works<br />
|-<br />
| Touchscreen || Yes || Resistive<br />
|-<br />
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection<br />
|-<br />
| 2G/3G/3.5G data || Yes || Works with ofono - UI is working, see https://github.com/maemo-leste/connui-cellular/<br />
|-<br />
| 4G data || N/A || no hardware<br />
|-<br />
| SMS || Yes || Works with ofono and Conversations UI<br />
|-<br />
| Phone calls || Yes || Works well using ofono scripts, UCM support, some integration and bug fixing still remains with Sphone, sound is good. Works in 2G, 3G and 3.5G mode, low latency. <br />
|-<br />
| SIP calls / IM || Yes || Works with Twinkle, TLS transport is supported, Telepathy/Sphone integration is WIP<br />
|-<br />
| Bluetooth || No || Driver needs some work<br />
|-<br />
| FM Transmitter || Yes || Select 'FM Transmitter' in Pavucontrol<br />
Install <code>v4l-utils</code> and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code><br />
|-<br />
| FM Receiver || No || Depends on working Bluetooth stack<br />
|-<br />
| Accelerometer || Yes || Not used in Leste at the moment, since UI rotation does not work on N900<br />
|-<br />
| Compass || N/A || No hardware<br />
|-<br />
| Gyro || N/A|| No hardware<br />
|-<br />
| Proximity sensor || Yes || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'<br />
|-<br />
| Ambient Light Sensor || Yes ||<br />
|-<br />
| Vibration Motor || Yes || <br />
|-<br />
| HDMI-out || N/A || No hardware<br />
|-<br />
| TV-out || Yes || Enable in alsamixer (Jack Function in alsamixer to TV OUT), enable with <code>xrandr --output TV --mode 800x480 --same-as LCD</code>. Set PAL/NTSC with <code>xrandr --output TV --set SignalProperties PAL</code>, and scale with <code>xrandr --output TV --set TVScale 90</code>.<br />
|-<br />
| GPS || Yes || <br />
|-<br />
| Infrared || Yes || TX only (hardware limitation). Works with pwm-ir-tx driver (patched)<br />
|-<br />
| Camera || No || Needs complex v4l work, no leste integration<br />
|-<br />
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode<br />
|}<br />
<br />
<br />
[[Category:Device]]</div>Halftuxhttps://leste.maemo.org/index.php?title=Motorola_Razr_(2011)&diff=1567Motorola Razr (2011)2023-10-20T11:09:06Z<p>Halftux: </p>
<hr />
<div>{{Infobox Device<br />
|image=[[File:XT910Lockscreen.jpg|250px]]<br />
|manufacturer=Motorola<br />
|codename=Spyder XT910, XT912<br />
|dimensions=130x68.9x7.1mm<br />
|release_date=11-11-11<br />
|soc=TI OMAP4430 <br>Cortex-A9 <br>Armv7‑A<br />
|dram=1024MB DDR2<br />
|power=<br />
|lcd=960x540 4.3"<br />
|video=PowerVR SGX540 <br />
|audio=<br />
|network=<br />
|storage=16GB flash<br />
|usb=<br />
|camera=<br />
|sensors=<br />
|other=<br />
|category=unsupported<br />
|sw_kernel=6.1<br />
|sw_serial=Yes, [[#Serial Cable|special cable]]<br />
|sw_charging=Yes<br />
|sw_usb_slave=Yes<br />
|sw_usb_host=Yes<br />
|sw_touchscreen=Yes<br />
|sw_keyboard=Yes<br />
|sw_screen=Yes<br />
|sw_hdmi=Yes<br />
|sw_tv=<br />
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br />
|sw_vibration=Unkown<br />
|sw_audio=Unkown<br />
|sw_calls=Unkown<br />
|sw_sms=Unkown<br />
|sw_wifi=Yes<br />
|sw_ethernet=<br />
|sw_irda=<br />
|sw_2g3gdata=Unkown<br />
|sw_4g=No<br />
|sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br />
|sw_fmtx=No<br />
|sw_fmrx=<br />
|sw_nfc=<br />
|sw_accelerometer=No<br />
|sw_compass=No<br />
|sw_gyro= No<br />
|sw_proximity=Yes<br />
|sw_als=No<br />
|sw_gps=Unkown<br />
|sw_agps=No<br />
|sw_frontcam=No<br />
|sw_backcam=No<br />
|sw_idlepower=Unkown<br />
|sw_standbytime=<br />
}}<br />
<br />
== Installation ==<br />
<br />
Hardware requirements:<br />
<br />
* A Razr or Droid Razr or Droid Razr MAXX with fully charged battery<br />
* MicroUSB cable<br />
* MicroSD card<br />
<br />
Software requirements:<br />
* Host Linux or Windows system<br />
* Android Tools: fastboot<br />
* get allow-mbmloader-flashing-mbm.bin for your device (xt910 or xt912) from an android update zip<br />
* Flashing tools:<br />
** XZ Utils and coreutils for Linux<br />
** Etcher[https://github.com/balena-io/etcher] for Windows<br />
<br />
Download from https://github.com/tmlind/droid4-kexecboot.git<br />
<br />
# utags-xt910-16-mmcblk1p8-boots-mmcblk1p13-kexecboot.bin<br />
# droid4-kexecboot.img<br />
<br />
Installation:<br />
<br />
# Create a working directory with above mentioned files in it<br />
# Power off the Razr and connect it to the host machine with MicroUSB cable<br />
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br />
<br />
=== Setting up kexecboot ===<br />
<br />
Now, assuming you are in the working directory, install kexecboot:<br />
<br />
<pre><br />
sudo fastboot flash mbm allow-mbmloader-flashing-mbm.bin<br />
sudo fastboot reboot-bootloader<br />
sudo fastboot flash bpsw droid4-kexecboot.img<br />
sudo fastboot flash utags utags-xt910-16-mmcblk1p8-boots-mmcblk1p13-kexecboot.bin<br />
sudo fastboot reboot<br />
</pre><br />
<br />
The device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br />
<br />
=== Install Maemo Leste to the sdcard ===<br />
<br />
Now, flash the Maemo Leste image to your sdcard:<br />
<br />
On Linux:<br />
<pre><br />
xzcat maemo-leste-1.0-armhf-razr-$DATE.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br />
sync<br />
</pre><br />
<br />
On Windows: Use Etcher<br />
<br />
Wait for sync to complete and insert MicroSD card into the Razr. Reboot the device and select Maemo Leste from the kexecboot menu.<br />
<br />
You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br />
<br />
== Updating ==<br />
<br />
Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:<br />
<br />
* Poweroff device, grab the SD card<br />
* Backup any important files<br />
* Grab the latest image from https://phoenix.maemo.org/view/Images/<br />
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br />
<br />
== Notes ==<br />
<br />
The battery in Razr 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. Razr will then reboot.<br />
<br />
== Serial Cable ==<br />
<br />
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 Razr, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/<br />
<br />
== Bluetooth ==<br />
<br />
Needs firmware - install latest firmware-ti-connectivity - See also https://github.com/maemo-leste/bugtracker/issues/290. Due to interference with WiFi, load driver (hci_uart) manually, AFTER wifi module loaded<br />
<br />
Using a bluetooth headset:<br />
sudo apt install pulseaudio-module-bluetooth blueman bluez<br />
sudo modprobe hci_uart<br />
pactl load-module module-bluetooth-discover<br />
blueman-manager<br />
<br />
Pair & trust your device in blueman, connect audiosink. You can close blueman now.<br />
<br />
== Additional Tips ==<br />
<br />
==== Using a battery without temperature sensor ====<br />
<br />
Modprobe the pmic driver as follows:<br />
<pre><br />
cpcap-battery ignore_temperature_probe=1<br />
</pre><br />
<br />
==== Flashing the boot logo ====<br />
<br />
More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO<br />
<br />
logos can be flashed via fastboot flash logo.bin logo.bin<br />
<br />
==== HDMI ====<br />
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br />
<pre><br />
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br />
</pre><br />
Return to internal touchscreen display.<br />
<pre><br />
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br />
</pre><br />
<br />
== Using a configured Leste sdcard in a different Razr ==<br />
<br />
A configured Razr Leste installation will have a unique wlan firmware calibration. The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.<br />
<br />
To recalibrate the wifi firmware on a different Razr, you must reset the FEM parameters to stock settings on the new device, then recalibrate. <br />
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.<br />
apt reinstall firmware-ti-connectivity <br />
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device<br />
apt download firmware-ti-connectivity<br />
Then copy the .deb to your new device and install that (as root) with<br />
dpkg -i firmware-ti-connectivity_[version]_all.deb <br />
Then (as root) re-calibrate the wifi chip by running<br />
/usr/bin/maserati-calibrate<br />
Then reboot.<br />
[[Category:Device]]</div>Halftuxhttps://leste.maemo.org/index.php?title=Motorola_Droid_4&diff=1566Motorola Droid 42023-10-20T11:04:00Z<p>Halftux: infobox device changes</p>
<hr />
<div>{{Infobox Device<br />
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]<br />
|manufacturer=Motorola<br />
|codename=Maserati XT894<br />
|dimensions=127x67.3x12.7mm<br />
|release_date=2012-02-10<br />
|soc=TI OMAP4430 <br>Cortex-A9 <br>Armv7‑A <br />
|dram=1024MB DDR2<br />
|power=<br />
|lcd=960x540 4"<br />
|video=PowerVR SGX540 <br />
|audio=<br />
|network=<br />
|storage=16GB flash<br />
|usb=<br />
|camera=<br />
|sensors=AK8975 compass, <br>LIS3DH accelerometer, <br>TMP105 temperature, <br>ISL29030 proximity and illuminance <br />
|other=<br />
|category=Supported<br />
|sw_kernel=5.18.x<br />
|sw_serial=Yes, [[#Serial Cable|special cable]]<br />
|sw_charging=Yes<br />
|sw_usb_slave=Yes<br />
|sw_usb_host=Yes<br />
|sw_touchscreen=Yes<br />
|sw_keyboard=Yes<br />
|sw_screen=Yes<br />
|sw_hdmi=Yes<br />
|sw_tv=<br />
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)<br />
|sw_vibration=Yes<br />
|sw_audio=Yes<br />
|sw_calls=Yes<br />
|sw_sms=Yes<br />
|sw_wifi=Yes<br />
|sw_ethernet=<br />
|sw_irda=<br />
|sw_2g3gdata=Yes<br />
|sw_4g=No<br />
|sw_bluetooth=Yes, [[#Bluetooth|see notes]] <br />
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers<br />
|sw_fmrx=<br />
|sw_nfc=<br />
|sw_accelerometer=Yes<br />
|sw_compass=Yes, no integration<br />
|sw_gyro=<br />
|sw_proximity=Yes<br />
|sw_als=Yes<br />
|sw_gps=Yes<br />
|sw_agps=No<br />
|sw_frontcam=No<br />
|sw_backcam=No<br />
|sw_idlepower=120mW<br />
|sw_standbytime=<br />
}}<br />
<br />
== Installation ==<br />
<br />
Hardware requirements:<br />
<br />
* Droid4 with fully charged battery<br />
* MicroUSB cable<br />
* MicroSD card<br />
<br />
Software requirements:<br />
* Host Linux or Windows system<br />
* Android Tools: fastboot<br />
* Flashing tools:<br />
** XZ Utils and coreutils for Linux<br />
** Etcher[https://github.com/balena-io/etcher] for Windows<br />
<br />
Download from https://maedevu.maemo.org/images/droid4/<br />
<br />
# VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br />
# flash-droid-4-fw.sh<br />
# Latest maemo-leste-1.0-armhf-droid4-*.img.xz<br />
<br />
Download from https://github.com/tmlind/droid4-kexecboot.git<br />
<br />
# utags-mmcblk1p13.bin<br />
# droid4-kexecboot.img<br />
<br />
Check what kernel version your Android OS runs.<br />
For this go to Settings -> About phone. Slide to the bottom, where you can see "Kernel version".<br />
If you have at least 3.0.8, you may skip "Updating Android" step below.<br />
<br />
Installation:<br />
<br />
# Create a working directory with above mentioned files in it<br />
# unzip VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip<br />
# Power off Droid4 and connect it to the host machine with MicroUSB cable<br />
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.<br />
<br />
=== Updating Android ===<br />
<br />
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:<br />
<pre><br />
pushd VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml<br />
sudo bash ../flash-droid-4-fw.sh<br />
popd<br />
</pre><br />
<br />
=== Setting up kexecboot ===<br />
<br />
Now, assuming you are in the working directory, install kexecboot:<br />
<br />
<pre><br />
sudo fastboot flash mbm VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml/allow-mbmloader-flashing-mbm.bin<br />
sudo fastboot reboot-bootloader<br />
sudo fastboot flash bpsw droid4-kexecboot.img<br />
sudo fastboot flash utags utags-mmcblk1p13.bin<br />
sudo fastboot reboot<br />
</pre><br />
<br />
If you did "Updating Android" the device should run the firstboot steps.<br />
If you didn't, the device should reboot and show kexecboot menu for a few seconds before it boots to Android.<br />
<br />
=== Install Maemo Leste to the sdcard ===<br />
<br />
Now, flash the Maemo Leste image to your sdcard:<br />
<br />
On Linux:<br />
<pre><br />
xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br />
sync<br />
</pre><br />
<br />
On Windows: Use Etcher<br />
<br />
Wait for sync to complete and insert MicroSD card into Droid4. Reboot the device and select Maemo Leste from the kexecboot menu.<br />
<br />
You should now see Maemo Leste booting up, and it will show you hildon-desktop after a minute.<br />
<br />
== Updating ==<br />
<br />
Normally you can just apt update && apt dist-upgrade to update to the latest version. If for some reason this fails:<br />
<br />
* Poweroff device, grab the SD card<br />
* Backup any important files<br />
* Grab the latest image from https://phoenix.maemo.org/view/Images/<br />
* Write it as before : xzcat maemo-leste-1.0-armhf-droid4-20190227.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE<br />
<br />
== Notes ==<br />
<br />
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.<br />
<br />
If Maemo is still running, you can also hold just the power button for ~10 seconds, and the device will run poweroff.<br />
<br />
Some users reported that Bluetooth kernel module interfere badly with the WiFi driver on their devices.<br />
Blacklisting the module may help if you have such problems:<br />
echo "blacklist hci_uart" >> /etc/modprobe.d/blacklist.conf<br />
<br />
Also see [[Motorola_Droid_4/Modem]] [[Motorola_Droid_4/PowerVR]]<br />
<br />
Also see: http://elektranox.org/droid4/ and http://muru.com/linux/d4/<br />
<br />
<br />
The keyboard layout is extended to provide more standard keys.<br />
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]<br />
Key mapping can be tested with the 'xev' program.<br />
<br />
It may be necessary to run the follow commands as root in order to get the OK key to function correctly (see [https://github.com/maemo-leste/bugtracker/issues/510#issuecomment-815618591 here]):<br />
udevadm hwdb --update<br />
udevadm trigger<br />
<br />
== Serial Cable ==<br />
<br />
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/<br />
<br />
While using the serial cable, if you lose the connection, the following may help:<br />
<br />
<pre><br />
18:43 < tmlind> sicelo: hmm the uart debug cable multiplexing still has issues, if the uart disappears during boot it should come back with <br />
the console login propt later<br />
18:45 < tmlind> try plugging in a pc usb cable then back to uart cable in case that might help<br />
</pre><br />
<br />
== Bluetooth ==<br />
<br />
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. So you should do:<br />
<br />
<pre><br />
sudo apt install firmware-ti-connectivity<br />
sudo modprobe hci_uart<br />
sudo hciconfig hci0 up<br />
sudo hcitool lescan<br />
</pre><br />
<br />
<br />
== Stuff to try ==<br />
<br />
==== Using a battery without temperature sensor ====<br />
<br />
Modprobe the pmic driver as follows:<br />
<pre><br />
cpcap-battery ignore_temperature_probe=1<br />
</pre><br />
<br />
==== Flashing the boot logo ====<br />
<br />
More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO<br />
<br />
<pre><br />
15:04 < tmlind> Wizzup: i think the logo on droid4 can be flashed with fastboot flash logo logo.bin or something, can also be just written to logo partition from m-l<br />
[snip]<br />
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin<br />
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition<br />
09:26 < xsetiadi> like i do last year<br />
09:26 < xsetiadi> instead of flashing using command: fastboot flash logo.bin logo.bin i just flash it with command: fastboot flash logo logo.bin<br />
</pre><br />
<br />
==== Blinkenlights ====<br />
Adding this in rc.local above the ''exit 0'' gets you some blinkenlights to watschen und relaxen.<br />
echo cpu > /sys/class/leds/lm3532::kbd_backlight/trigger # gets you a cpu activity monitor on the keyboard backlight<br />
echo mmc0 > /sys/class/leds/shift-key-light/trigger # gets you a 'hdd led' of the SD card on the capslock light<br />
<br />
==== USSD ====<br />
<br />
<pre><br />
22:45 < tmlind> fyi, here's how to send USSD to query balance for example: printf "AT+CUSD=1,#999#,0\r" > /dev/motmdm1<br />
22:47 < tmlind> fyi, for parsing incoming USSD, this web interface works if set to utf-8: <br />
https://www.mobilefish.com/services/latin_utf_base64_to_hex/latin_utf_base64_to_hex.php#text_hex_output<br />
</pre><br />
<br />
==== HDMI ====<br />
Move output to external 1080p monitor. Disabling DSI-1 output gets xorg pointer displayed on HDMI, for use with a mouse or barrier. <br />
<pre><br />
xrandr --output HDMI-1 --mode 1920x1080 --output DSI-1 --off<br />
</pre><br />
Return to internal touchscreen display.<br />
<pre><br />
xrandr --output DSI-1 --auto --rotate right --output HDMI-1 --off<br />
</pre><br />
<br />
<br />
If one wants to mirror the screen on HDMI, this can be done like so, for landscape:<br />
<br />
<pre><br />
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync<br />
xrandr --addmode HDMI-1 "960x540_60.00"<br />
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1<br />
</pre><br />
<br />
For rotation, something like this might or might not work:<br />
<br />
<pre><br />
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync<br />
xrandr --addmode HDMI-1 "960x540_60.00ROT"<br />
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right<br />
</pre><br />
<br />
==== Keyboard / Mouse sharing with PC ====<br />
To use droid4 while working at desktop it can be convenient to share mouse and keyboard of the host pc with droid4. <br />
<pre><br />
[https://github.com/debauchee/barrier Barrier software-KVM switch]<br />
</pre><br />
Developers and testers may wish to disable the googley bits before compiling.<br />
<br />
==== BT Audio headset ====<br />
<br />
sudo apt install pulseaudio-module-bluetooth blueman bluez<br />
sudo modprobe hci_uart<br />
pactl load-module module-bluetooth-discover<br />
blueman-manager<br />
<br />
Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.<br />
<br />
==== Torch ====<br />
<br />
The Droid 4 has a TI LM3559 flash torch controller. This provides flash functionality when taking pictures, usage as a torch, and provides privacy indication (in this mode, the LED flashes in a fast heartbeat pattern). A driver for it exists in mainline, but it requires some DTS work, since it is tied to a camera device. <br />
<br />
If you want to use it in the meantime, direct i2c access can be used as follows (since this is direct access, be careful about each of the commands below):<br />
<br />
<source><br />
##Install the prerequisites<br />
$ sudo apt install i2c-tools<br />
<br />
## Turn LED on in torch mode<br />
$ sudo i2cset -y 2 0x53 0x10 0x1a<br />
<br />
## Turn LED on in privacy indication mode<br />
$ sudo i2cset -y 2 0x53 0x10 0x19<br />
<br />
## Turn LED off (in any mode)<br />
$ sudo i2cset -y 2 0x53 0x10 0x18<br />
<br />
## Use LED for doing a hella bright flash for some time once and then turn off<br />
$ sudo i2cset -y 2 0x53 0x10 0x1b<br />
<br />
</source><br />
<br />
== Using a configured Leste sdcard in a different Droid4 ==<br />
<br />
A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device. <br />
<br />
The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.<br />
<br />
To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate. <br />
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.<br />
apt reinstall firmware-ti-connectivity <br />
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device<br />
apt download firmware-ti-connectivity<br />
Then copy the .deb to your new device and install that (as root) with<br />
dpkg -i firmware-ti-connectivity_[version]_all.deb <br />
Then (as root) re-calibrate the wifi chip by running<br />
/usr/bin/maserati-calibrate<br />
Then reboot.<br />
<br />
== Gallery ==<br />
<br />
<gallery><br />
Motorola-Droid4-20200125.jpeg<br />
Droid4-neofetch.JPG<br />
Droid4_htop.jpg<br />
Droid4_leste_logo.jpg<br />
Cant_have_2_much_leste.jpg<br />
Leste-neverball.jpg<br />
Statsfun.jpg<br />
Leste-glmatrix.png<br />
Droid4-leste-utox2.jpg<br />
Droid4-leste-pcsx.jpg<br />
Droid4-leste-surf_master.jpg<br />
Droid4_Daimonin_Hdmi.jpg<br />
</gallery><br />
<br />
== Old status overview ==<br />
<br />
<br />
{| class="wikitable"<br />
! Feature<br />
! Leste supported<br />
! Notes<br />
|-<br />
| Kernel version || 5.9.0 || Mainline + some patches not yet in mainline - see https://github.com/maemo-leste/droid4-linux<br />
|-<br />
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]<br />
|-<br />
| Charging || Yes ||<br />
|-<br />
| Wireless || Yes ||<br />
|-<br />
| Ethernet || N/A ||<br />
|-<br />
| Micro USB || Yes || OTG and USB network<br />
|-<br />
| 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)<br />
|-<br />
| Screen || Yes ||<br />
|-<br />
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://github.com/maemo-leste/pvr-omap4/<br />
|-<br />
| Touchscreen || Yes || Capacitive<br />
|-<br />
| Audio || Yes || Implemented with Pulseaudio and UCM files<br />
|-<br />
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://github.com/maemo-leste/connui-cellular/<br />
|-<br />
| 4G data || No || Needs kernel work<br />
|-<br />
| SMS || Yes || Works with ofono. Needs Leste UI<br />
|-<br />
| Phone calls || Yes || Works with ofono (good call quality, too), needs Leste UI<br />
|-<br />
| 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<br />
|-<br />
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers<br />
|-<br />
| FM Receiver || Not yet ||<br />
|-<br />
| Accelerometer || Yes || Available in /sys, and as input device via iio-uinput<br />
|-<br />
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration applications using it yet)<br />
|-<br />
| Gyro || N/A || <br />
|-<br />
| Proximity sensor || Yes ||<br />
|-<br />
| Ambient Light Sensor || Yes ||<br />
|-<br />
| Vibration Motor || Yes || <br />
|-<br />
| HDMI-out || Yes || No UI integration<br />
|-<br />
| TV-out || N/A ||<br />
|-<br />
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]<br />
|-<br />
| Infrared || N/A || Missing in hardware<br />
|-<br />
| Camera || No || See https://elektranox.org/2018/02/0025-droid-camera/<br />
|-<br />
| Idle power consumption || ~120mW || Needs sim inserted<br />
|}<br />
<br />
[[Category:Device]]</div>Halftuxhttps://leste.maemo.org/index.php?title=Category:Extras&diff=1561Category:Extras2023-09-04T21:00:15Z<p>Halftux: Added extras repository link</p>
<hr />
<div>This page contains a list of packages in Maemo Leste Extras with wiki pages<br />
<br />
To install packages from extras you need to add one of the following repositories according to the used release.<br />
<br />
<code><br />
deb https://maedevu.maemo.org/extras beowulf main contrib non-free<br />
<br />
deb https://maedevu.maemo.org/extras chimaera main contrib non-free<br />
</code></div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=997Main Page2021-05-05T14:40:29Z<p>Halftux: /* Links */ added irclog whitequark</p>
<hr />
<div>= Description =<br />
<br />
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.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Beowulf (Debian Buster) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
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.<br />
<br />
If you have not used Maemo before, you might want to check out some of the tips on the [[HowTo]] page.<br />
<br />
== Getting Started ==<br />
<br />
See [[Getting_Started|Getting Started]]<br />
<br />
== Frequently Asked Questions ==<br />
<br />
See [[Leste_FAQ|FAQ]]<br />
<br />
== Supported Devices ==<br />
<br />
See [[:Category:Device]]<br />
<br />
== Latest Images ==<br />
<br />
https://phoenix.maemo.org/view/Images/<br />
<br />
== Development ==<br />
<br />
See [[Development]]<br />
<br />
== Roadmap ==<br />
<br />
=== Project milestones ===<br />
https://github.com/maemo-leste/bugtracker/milestones<br />
<br />
=== Wishlist ===<br />
<br />
You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
<br />
== Talks ==<br />
<br />
See [[Talks]]<br />
<br />
== Links ==<br />
<div><br />
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.<br />
<br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/] and https://phoenix.maemo.org/view/Images/<br />
<br />
*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br />
<br />
*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt] and https://freenode.irclog.whitequark.org/maemo-leste/<br />
<br />
*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )<br />
<br />
*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]<br />
<br />
*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]<br />
<br />
*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Nokia_N950&diff=756Nokia N9502020-05-29T08:56:07Z<p>Halftux: /* Installation */ changed link to the image</p>
<hr />
<div>{{Stub}}<br />
<br />
{{Infobox Device<br />
|image=<br />
|manufacturer=Nokia<br />
|codename=<br />
|dimensions=<br />
|release_date=<br />
|soc=<br />
|dram=<br />
|power=<br />
|lcd=<br />
|video=<br />
|audio=<br />
|network=<br />
|storage=<br />
|usb=<br />
|camera=<br />
|sensors=<br />
|other=<br />
}}<br />
<br />
<br />
[https://github.com/maemo-leste/bugtracker/issues/121 Status]<br />
<br />
=== Installation ===<br />
<br />
''' [http://www.swagman.org/juice/ubiboot/ubiboot-02/ ubiboot] from eMMC '''<br />
# [http://www.swagman.org/juice/ubiboot/README Install ubiboot].<br />
# [https://talk.maemo.org/showthread.php?t=91914 Create a new slice on the eMMC] and format it to ext4.<br />
# Mount your new ext4 slice and unpack the .tar.gz dist ([https://maedevu.maemo.org/images/n9/ N9], [https://maedevu.maemo.org/images/n950/ N950]) to it.<br />
# Configure <code>ubiboot.conf</code>. This guide assumes you will use slot 5 for Maemo Leste ([https://github.com/dderby/ubiboot-animatronics/blob/master/ubiboot.conf example]):<br />
#* Set '''G_OS5_INITSCRIPT''' to <code>\/sbin\/preinit</code><br />
#* Set '''G_OS5_NUM''' to <code>1</code><br />
#* Set '''G_OS5_PARTITION''' to the partition number of your Maemo Leste slice<br />
#* Set '''G_OS5_NAME''' to <code>Maemo</code><br />
#* Set '''G_OS5_1_LABEL''' to <code>Maemo Leste - Linux 4.16</code> or whatever description you like<br />
#* Set '''G_OS5_1_FILE''' to <code>/boot/Maemo/boot/zImage</code><br />
# Reboot to ubiboot and select the slot for Maemo Leste.<br />
If you don't want to repartition your eMMC, there are two alternatives:<br />
* Use [https://talk.maemo.org/showthread.php?t=94042 N9 Easy Boot].<br />
* Unpack the dist to Harmattan's <code>/home</code> directory and set '''G_OS5_PARTITION''' in ubiboot.conf to <code>3</code>. This will result in Maemo Leste sharing a slice with Harmattan's <code>/home</code>. Be careful when removing Maemo Leste, not to remove Harmattan's <code>user</code> or <code>developer</code> home directories.<br />
<br />
=== Kernel development ===<br />
<br />
Linux 4.16.4 plus patches<br />
<br />
N950 status: https://elinux.org/N950<br />
<br />
N9 status: https://elinux.org/N9<br />
<br />
Sources: [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/log/?h=linux-4.16.y linux-stable 4.16.y], [https://github.com/parazyd/arm-sdk/tree/master/extra/patches/linux-n950-patches N950 patches], [https://github.com/parazyd/arm-sdk/tree/master/extra/patches/linux-n9-patches N9 patches]<br />
<br />
&nbsp;<br />
<br />
<br />
[[Category:Device]]</div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=655Main Page2020-03-03T14:00:16Z<p>Halftux: /* Links */ added rss feed link</p>
<hr />
<div>= Description =<br />
<br />
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.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
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.<br />
<br />
= Frequently Asked Questions =<br />
<br />
See [[Leste_FAQ|FAQ]]<br />
<br />
= Supported Devices =<br />
<br />
See [[:Category:Device]]<br />
<br />
= Development =<br />
<br />
See [[Development]]<br />
<br />
= Roadmap =<br />
<br />
== Project milestones ==<br />
https://github.com/maemo-leste/bugtracker/milestones<br />
<br />
== Wishlist ==<br />
<br />
You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
<br />
= Talks =<br />
<br />
See [[Talks]]<br />
<br />
= Links =<br />
<div><br />
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.<br />
<br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br />
<br />
*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]<br />
<br />
*Our YouTube channel: [https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w https://www.youtube.com/channel/UCgAWiHvWSuJAg5hjk7JYn1w] (via [https://www.invidio.us/channel/UCgAWiHvWSuJAg5hjk7JYn1w Invidious] )<br />
<br />
*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
*RSS feed: [https://maemo-leste.github.io/feeds/all.atom.xml https://maemo-leste.github.io/feeds/all.atom.xml]<br />
<br />
*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=595Main Page2020-01-30T13:03:16Z<p>Halftux: /* Links */ irc history</p>
<hr />
<div>= Description =<br />
<br />
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.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Also see our [[Leste_FAQ|FAQ]].<br />
<br />
= Supported Devices =<br />
<br />
See [[:Category:Device]]<br />
<br />
= Development =<br />
<br />
See [[Development]]<br />
<br />
= Roadmap =<br />
<br />
== Project milestones ==<br />
https://leste.maemo.org/index.php?title=Wishlist&action=edit&redlink=1<br />
https://github.com/maemo-leste/bugtracker/milestones<br />
<br />
== Wishlist ==<br />
<br />
You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
<br />
= Links =<br />
<div><br />
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.<br />
<br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br />
<br />
*Our IRC history: [http://maedevu.maemo.org/irc.txt http://maedevu.maemo.org/irc.txt]<br />
<br />
*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=594Main Page2020-01-30T12:51:57Z<p>Halftux: /* Links */</p>
<hr />
<div>= Description =<br />
<br />
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.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Also see our [[Leste_FAQ|FAQ]].<br />
<br />
= Supported Devices =<br />
<br />
See [[:Category:Device]]<br />
<br />
= Development =<br />
<br />
See [[Development]]<br />
<br />
= Roadmap =<br />
<br />
== Project milestones ==<br />
https://leste.maemo.org/index.php?title=Wishlist&action=edit&redlink=1<br />
https://github.com/maemo-leste/bugtracker/milestones<br />
<br />
== Wishlist ==<br />
<br />
You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
<br />
= Links =<br />
<div><br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
*Our Jenkins build server: [https://phoenix.maemo.org/ https://phoenix.maemo.org/]<br />
<br />
*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
The central point of meeting and talking is IRC and this thread: https://talk.maemo.org/showthread.php?t=100192.<br />
</div><br />
<br />
*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]</div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=593Main Page2020-01-30T12:48:25Z<p>Halftux: /* Links */</p>
<hr />
<div>= Description =<br />
<br />
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.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
For an overview of the current status, you might want to check out: [[Status]]<br />
<br />
Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Also see our [[Leste_FAQ|FAQ]].<br />
<br />
= Supported Devices =<br />
<br />
See [[:Category:Device]]<br />
<br />
= Development =<br />
<br />
See [[Development]]<br />
<br />
= Roadmap =<br />
<br />
== Project milestones ==<br />
https://leste.maemo.org/index.php?title=Wishlist&action=edit&redlink=1<br />
https://github.com/maemo-leste/bugtracker/milestones<br />
<br />
== Wishlist ==<br />
<br />
You have an application you want to see in Leste? Please let us know [[Wishlist|here]].<br />
<br />
= Links =<br />
<div><br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Extras Github: [https://github.com/maemo-leste-extras/ https://github.com/maemo-leste-extras/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
*Mailing List: [https://lists.dyne.org/lurker/list/maemo-leste.en.html https://lists.dyne.org/lurker/list/maemo-leste.en.html]<br />
<br />
The central point of meeting and talking is IRC and this thread: https://talk.maemo.org/showthread.php?t=100192.<br />
</div><br />
<br />
*[https://distrowatch.com/dwres.php?resource=submit Maemo Leste on Distrowatch (voting)]</div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=11Main Page2018-04-27T19:49:13Z<p>Halftux: structure, description update</p>
<hr />
<div>= Description =<br />
<br />
Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.<br />
<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
<br />
Maemo Leste is based on Devuan Ascii (Debian Stretch) and all the "supported" devices ship with recent Linux (mainline-based) kernels.<br />
<br />
The project is 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.<br />
<br />
So far we have set up devuan/debian repositories for our packages, with builds for armel, armhf 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.<br />
<br />
&nbsp;<br />
<br />
= Supported Devices =<br />
<br />
&nbsp;<br />
<br />
== N900 ==<br />
<br />
[https://maemo-leste.github.io/pages/n900-status.html Status]<br />
<br />
=== Installation ===<br />
<br />
''' U-Boot from sdcard '''<br />
<br />
''' Boot through flasher from sdcard'''<br />
<br />
=== Kernel development ===<br />
<br />
Status: [https://elinux.org/N900 https://elinux.org/N900]<br />
<br />
Sources: [https://github.com/pali/linux-n900 https://github.com/pali/linux-n900]<br />
<br />
&nbsp;<br />
<br />
== N9/N950 ==<br />
<br />
&nbsp;<br />
<br />
== Droid 4 ==<br />
<br />
&nbsp;<br />
<br />
== Generic AMD64 ==<br />
<br />
&nbsp;<br />
<br />
== Allwinner A20 LIME2 ==<br />
<br />
&nbsp;<br />
<br />
== Allwinner A33 Tablet ==<br />
<br />
&nbsp;<br />
<br />
== Raspberry 2 or 3 ==<br />
<br />
&nbsp;<br />
<br />
<br />
= Development =<br />
<br />
&nbsp;<br />
<br />
== Set up a VM ==<br />
<br />
&nbsp;<br />
<br />
== Packages needed testing ==<br />
<br />
&nbsp;<br />
<br />
== Packages needed building ==<br />
<br />
&nbsp;<br />
<br />
== Packages needed porting ==<br />
<br />
&nbsp;<br />
<br />
= Links =<br />
<div><br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
The central point of meeting and talking is IRC and this thread: https://talk.maemo.org/showthread.php?t=100192.<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=10Main Page2018-04-27T17:04:32Z<p>Halftux: created basic structure</p>
<hr />
<div>= Description =<br />
<br />
Welcome to the Maemo Leste website; Maemo Leste continues the legacy of Maemo. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, Allwinner Tablets and more.<br />
<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.<br />
<br />
&nbsp;<br />
<br />
= Supported Devices =<br />
<br />
&nbsp;<br />
<br />
== N900 ==<br />
<br />
[https://maemo-leste.github.io/pages/n900-status.html Status]<br />
<br />
<br />
&nbsp;<br />
<br />
== N9/N950 ==<br />
<br />
&nbsp;<br />
<br />
== Droid 4 ==<br />
<br />
&nbsp;<br />
<br />
== Generic AMD64 ==<br />
<br />
&nbsp;<br />
<br />
== Allwinner A20 LIME2 ==<br />
<br />
&nbsp;<br />
<br />
== Allwinner A33 Tablet ==<br />
<br />
&nbsp;<br />
<br />
== Raspberry 2 or 3 ==<br />
<br />
&nbsp;<br />
<br />
<br />
= Development =<br />
<br />
&nbsp;<br />
<br />
= Links =<br />
<div><br />
*Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
*Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
*Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
*Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
The central point of meeting and talking is IRC and this thread: https://talk.maemo.org/showthread.php?t=100192.<br />
</div></div>Halftuxhttps://leste.maemo.org/index.php?title=Main_Page&diff=9Main Page2018-04-23T15:21:40Z<p>Halftux: added link to images</p>
<hr />
<div><strong>Welcome to the Maemo Leste Wiki.</strong><br />
<br />
Our Blog: [https://maemo-leste.github.io https://maemo-leste.github.io]<br />
<br />
Our Bugtracker: [https://github.com/maemo-leste/bugtracker/issues https://github.com/maemo-leste/bugtracker/issues]<br />
<br />
Our Github: [https://github.com/maemo-leste/ https://github.com/maemo-leste/]<br />
<br />
Our Images: [http://maedevu.maemo.org/images/ http://maedevu.maemo.org/images/]<br />
<br />
The central point of meeting and talking is IRC and this thread: https://talk.maemo.org/showthread.php?t=100192.<br />
<br />
You can find us on '''freenode''', channel '''#maemo-leste'''.</div>Halftux