Maemo Leste Wiki - User contributions [en]

Google Pixel 3a

2026-10-18T08:57:59Z

Arno11-n900:

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=IMX355, IMX363
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000 / 3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40 / 50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Packages needed: blueman, pipewire, pipewire-pulse, wireplumber, bluez, pipewire-audio, libspa-0.2-bluetooth

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not set as default sink:'''

To check bluetooth device sink number:

<pre>
wpctl status
</pre>

Look in Audio ---> Sinks

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. Fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-18T08:53:26Z

Arno11-n900: /* Remaining issues */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=IMX355, IMX363
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Packages needed: blueman, pipewire, pipewire-pulse, wireplumber, bluez, pipewire-audio, libspa-0.2-bluetooth

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not set as default sink:'''

To check bluetooth device sink number:

<pre>
wpctl status
</pre>

Look in Audio ---> Sinks

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. Fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-18T08:52:03Z

Arno11-n900: /* Bluetooth (testing with Pipewire) */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=IMX355, IMX363
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Packages needed: blueman, pipewire, pipewire-pulse, wireplumber, bluez, pipewire-audio, libspa-0.2-bluetooth

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not set as default sink:'''

To check bluetooth device sink number:

<pre>
wpctl status
</pre>

Look in Audio ---> Sinks

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-16T15:16:46Z

Arno11-n900: /* Bluetooth (testing with Pipewire) */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=IMX355, IMX363
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Install blueman package from apt.

Run:

<pre>
bluetoothctl power on
sudo hciconfig hci0 up
</pre>

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not the default sink:'''

To check bluetooth device sink number:

<pre>
wpctl status
</pre>

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-16T15:07:09Z

Arno11-n900:

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=IMX355, IMX363
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Install blueman package from apt.

Run:

<pre>
bluetoothctl power on
sudo hciconfig hci0 up
</pre>

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not the default sink:'''

To check bluetooth sink number:

<pre>
wpctl status
</pre>

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-16T15:04:19Z

Arno11-n900:

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=BMI160, AK0991X, TMD2725, BMP380, MAX11261
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Install blueman package from apt.

Run:

<pre>
bluetoothctl power on
sudo hciconfig hci0 up
</pre>

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not the default sink:'''

To check bluetooth sink number:

<pre>
wpctl status
</pre>

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-15T20:08:58Z

Arno11-n900: /* Bluetooth (testing with Pipewire) */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Install blueman package from apt.

Run:

<pre>
bluetoothctl power on
sudo hciconfig hci0 up
</pre>

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

'''If you pair and connect a headset, note that bluetooth device is not the default sink:'''

To check bluetooth sink number:

<pre>
wpctl status
</pre>

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-15T20:06:14Z

Arno11-n900: /* Tweaks */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

=== Bluetooth (testing with Pipewire) ===

Install blueman package from apt.

Run:

<pre>
bluetoothctl power on
sudo hciconfig hci0 up
</pre>

Launch blueman and search/pair/connect your device.

Sending files between Pixel 3a and android phones works.

If you pair and connect a headset, note that bluetooth device is not the default sink:

To check bluetooth sink number:

<pre>
wpctl status
</pre>

Then:

<pre>
wpctl set-default <bluetooth device sink number>
</pre>

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-11T12:47:17Z

Arno11-n900: /* Remaining issues */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

== Remaining issues ==

Broken notification sounds (notify-sv).

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-10-11T12:45:32Z

Arno11-n900: /* GPS with ModemManager and Geoclue (testing, not implemented, WIP) */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

'''Note: Comaps experimental maemo version is also able to report coordinates.'''

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

A23-Q8H-v1.5

2026-09-27T07:44:24Z

Arno11-n900:

{{Infobox Device
|image=[[File:A23-q8h-v1.5-ccit.jpg|250px|alt=image of Q8H tablet, running leste]]
|manufacturer=CCIT? (Ippo?)
|codename=Q8H v1.5
|dimensions=181mm x 121mm x 10.5mm
|release_date=2015-01-29
|category=Supported
|soc=Allwinner A23 @1.5Ghz underclocked @1.2Ghz Cortex-A7 Armv7-A
|dram=512MiB DDR3 @ 480MHz
|power=DC 5V @ 2A
|display=800x480 7" capacitive touch
|video=Mali 400
|audio=3.5mm headphone plug, internal speaker, internal microphone
|network=RTL8703AS
|storage=4GB?
|usb=Micro USB 2.0 Host
|camera=0.3MP (640x480)
|sensors=
|other=
|headers=UART?
|battery=?mAh 3.7V Li-Ion battery
|sw_kernel=6.12
|sw_serial=N/A
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=N/A
|sw_screen=Yes
|sw_hdmi=N/A
|sw_tv=No
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=N/A
|sw_sms=N/A
|sw_wifi=Yes, firmware required
|sw_ethernet=N/A
|sw_irda=N/A
|sw_2g3gdata=N/A
|sw_4gdata=N/A
|sw_bluetooth=Yes, firmware required
|sw_fmtx=N/A
|sw_fmrx=N/A
|sw_nfc=N/A
|sw_accelerometer=Yes
|sw_compass=N/A
|sw_gyro=N/A
|sw_proximity=N/A
|sw_als=N/A
|sw_gps=N/A
|sw_agps=N/A
|sw_frontcam=N/A
|sw_backcam=N/A
|sw_idlepower=1.4W-3.7W (WIP)
|sw_standbytime=N/A
}}

== Installation ==
Simply write the image to a sdcard and put it on the device, it should load u-boot and kernel automatically.

== Notes ==
Like most devices with silead touch screen you may need to extract touch screen driver from android firmware. firmware for this tablet was <code>gsl1680-b482-q8-a70.fw</code>, which could be either taken from [https://github.com/onitake/gsl-firmware here] or from android directly.
while the screen resolution was 800 x 480, touch panel had 900 x 600.

=== Wireless and Bluetooth ===
On devices that ship with realtek 8702as (or 8723bs), a firmware and a binary config file are required for wifi/bluetooth driver to work properly.
these are available under package <code>firmware-realtek</code>.
a patch is needed for bluetooth driver to work properly, which is just for correct probing of the card.

note that sdio currently doesn't function if device is rebooted, powering it off and turning it on again works.

=== Power usage ===
Hungry beast, sips 1A with everything on and max and sips 300mA with everything (but wifi) off and cpu mostly idle.
this results in very poor temps and runtime, some of which can be improved thru [https://github.com/crust-firmware/crust crust] (since appearently deep sleep support in mainline for allwinner kernels is very poor, if non existant?) or better dt/kernel setups.

== Status ==
{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.12 || Mainline + patches (for bluetooth, wireless and screen rotation)
|-
| Serial || Probably || Need to locate it on the board
|-
| Charging || Yes || charging via AC in works
|-
| Wireless || Yes || Realtek 8703as, Driver is still in staging (rt8723bs)
|-
| Bluetooth || Yes? || Realtek 8703as, Uses rt8723bs driver, seems to work, but not tested much
|-
| Micro USB || WIP || Only works in otg (with dr_mode = "host" in dts), might need further device tree improvments
|-
| Keyboard || N/A || Device has no keyboard
|-
| Screen || Yes || sunxi drm (with simplefb)
|-
| 3D Acceleration || Yes || Mali 400, Lima
|-
| Touchscreen || Yes || Silead gsl1688?, Capacitive
|-
| Speaker || WIP || works, but a bit underwhelming, might be amplifiers
|-
| Headphone || WIP || works, but does not mute speakers when plugged in
|-
| Accelerometer || Yes? || Memsic 6255, There is a screen rotation sensor, mxc6255 driver can be used for it, but doesn't seem to work very well
|-
| Proximity sensor || N/A || Not sure if available
|-
| eMMC || No || Likely dts issues
|-
| HW accelerated video encode/decode || ? || Should work with Cedrus driver, but not tested
|-
| Camera || ? || Not tested
|}

[[Category:Device]]

Purism Librem5

2026-09-27T07:43:21Z

Arno11-n900:

{{Infobox Device
|manufacturer=Purism
|codename=Librem5
|dimensions=74×152×15 mm
|release_date=
|soc=NXP i.MX 8M Quad core Cortex-A53, 64bit ARM (auxiliary 266MHz Cortex-M4F)
|dram=3GB LPDDR4-3200
|power=
|display=1440x720 IPS TFT 5.7″
|video=Vivante GC7000Lite
|audio=
|network=
|storage=32GB
|usb=
|camera=
|sensors=
|other=
|category=Supported
}}

== Installation ==

[[Category:Device]]

PinePhone

2026-09-27T07:42:44Z

Arno11-n900:

{{Stub}}

{{Infobox Device
|image=[[File:Phinephone_leste.jpg|250px]]
|manufacturer=Pine64
|codename=
|dimensions=160.5x76.6x9.2mm
|release_date=
|soc=Allwinner A64 Cortex-A53 arm64v8
|dram=2GB or 3GB LPDDR3 SDRAM
|power=
|display=1440x720 5.95″
|video=ARM Mali 400 MP2 GPU
|audio=
|network=
|storage=16GB or 32GB eMMC
|usb=
|camera=GalaxyCore GC2145, OmniVision OV5640
|sensors=ST LIS3MDL compass, InvenSense MPU-6050 accelerometer, SensorTek STK3335 proximity and illuminance
|other=
}}

This is for all PinePhones starting with the first Pinephone (Braveheart) phone, but not for the PinePhone Pro.

== Notes ==

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.

== Status ==

Currently, most things work, for example you can:

* Run any applications in Debian and Devuan on your phone
* Connect to wifi
* Use the terminal
* Connect to 2G/3G/4G data connections
* Make and receive phone calls and SMS
* PinePhone keyboard is supported

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.17 || Mainline + some patches: https://git.maemo.org/leste-upstream-forks/pine64-kernel/src/branch/orange-pi-6.17-megi-maemo
|-
| Serial || Yes || Via headphone jack (disable headphone switch)
|-
| Charging || Yes ||
|-
| Wireless || Yes || Involves installing out of tree driver
|-
| Ethernet || N/A || ps: USB Ethernet adapter tested and works
|-
| Bluetooth || YES || No UI integration yet
|-
| Infrared || N/A || TX only (hardware limitation).
|-
| USB C || Yes || Peripheral/slave, exposes network gadget by default. Host Untested
|-
| Keyboard || Yes || When a PP keyboard is connected, it works out-of-the-box
|-
| Screen || Yes || Modesetting driver
|-
| 3D Acceleration || Yes || mesa-lima
|-
| Touchscreen || Yes || Capacitive
|-
| Audio || Yes || Pulseaudio and UCM units
|-
| 2G/3G/4G data || YES || Works with ofono;
|-
| SMS || YES || Works with ofono, will using telepathy-ring. Sphone and Conversations are currently available
|-
| Phone calls || YES || Works with ofono; Calls work with sphone as UI
|-
| VoLTE || YES || Quectel EG25 has VoLTE support, no userland required, but setting VoLTE profile might be needed
|-
| Accelerometer || Yes ||
|-
| Proximity sensor || Yes ||
|-
| RGB LED || WIP || Works, but mce can't deal with LEDs without controllers yet.
|-
| Vibration Motor || ? ||
|-
| GPS || WIP || Works with WIP Leste GPS stack
|-
| Cameras || WIP || Driver present for rear (OV5640) and front (GC2145) cameras. User space support in progress with libcamera.
|}

=== More Information ===

* Virtual keyboard should work in all gtk2 applications (not yet in gtk3 and qt, but this is coming).
* 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.
* WiFi and terminal work.
* Some rendering bugs in portrait mode remain, so the default desktop orientation is landscape for now (<code>xrandr -o right</code>). Please note that if orientation is changed (e.g. with <code>xrandr -o normal</code>) the ui will still be reading original key positions.
* Screen brightness adjustments in UI do not work on the Pinephone yet. There is also a user reported when "brightness" UI setting is set to minimum (no visual change normally), the screen will stay black after reboot with WiFi set to ON with kill switch. However screen is normal after reboot if WiFi set to OFF with kill switch even minimum "brightness" UI setting. You may still change the screen brightness with terminal commands: <code>xrandr --output DSI-1 --brightness 0.5</code>
* Performance is not bad, but will get better, with hildon-desktop optimisations and as lima improves.
* Many "games" packages in the Application Manager don't work well yet.
* '''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:
$ echo 'AT+QMBNCFG="select","Commercial-TMO_VoLTE"' | atinout - /dev/EG25.AT -
In order to list all specific VoLTE profiles, use:
$ echo 'AT+QMBNCFG="list"' | atinout - /dev/EG25.AT -
To enable calling out over VoLTE, use:
$ echo 'AT+QCFG="ims",1' | atinout - /dev/EG25.AT -
Reboot the modem by rebooting the phone.

== Installation ==
Unlike most phones, it's pretty simple.

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

Create a new msdos partition table using fdisk

$ sudo fdisk /dev/''SDCARD''
# press 'p' to view current table
# press 'o' to erase and make a new table
# press 'w' to write changes and quit

==== Write the image to an SD-Card. ====

Download the latest image and the associated checksum file from [https://maedevu.maemo.org/images/pinephone/ here].

$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''IMAGE FILE''
$ wget https://maedevu.maemo.org/images/pinephone/''DATE''/''CHECKSUM FILE''
$ sha256sum maemo-leste-*-arm64-pinephone-*.img.xz
$ cat maemo-leste-*-arm64-pinephone-*.img.xz.sha56
Compare the output. If they do not match, stop and ask someone in the project for help. If the checksums match, extract the image:
$ unxz maemo-leste-*-arm64-pinephone-*.img.xz
Write the image to microSD. '''''Be very careful with this step''''' to select the correct device.
$ dd if=maemo-leste-*-arm64-pinephone-*.img /path/to/sd-card bs=4M status=progress conv=fsync
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.

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.

=== eMMC Installation ===
'''Some notes have been adapted from the [https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Installation_to_the_eMMC Pine64 Wiki]'''.
==== Preparing the .img file for eMMC boot ====

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

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

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.

$ sudo losetup -P /dev/loop0 maemo-leste-*-arm64-pinephone-*.img

Mount the second partition to /mnt and the first partition to /mnt/boot and enter /mnt:

$ sudo mount /dev/loop0p2 /mnt
$ sudo mount /dev/loop0p1 /mnt/boot
$ cd /mnt

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

Now we need to edit <code>boot.scr</code>. For that you will need to download <code>boot.txt</code> from Maemo Leste github:

$ cd /mnt/boot
$ sudo wget https://raw.githubusercontent.com/maemo-leste/pine64-uboot/master/boot.txt

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>.

To regenerate <code>boot.scr</code> you need to install <code>u-boot-tools</code> first to be able to use mkimage.

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

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

Leave /mnt and unmount the partitions:

$ cd ~
$ sudo umount -R /mnt

We can now save the image we just modified using dd:

$ sudo dd if=/dev/loop0 of=maemo-leste-1.0-arm64-pinephone-EMMC.img

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

We can now remove the loop device we created earlier:

$ sudo losetup -d /dev/loop0

==== Install Using Tow-Boot ====

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.

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 dd command or a utility such as Etcher or Gnome Disks, etc.

==== Install Using JumpDrive ====

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.

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.

[https://wiki.pine64.org/wiki/PinePhone_Installation_Instructions#Using_JumpDrive JumpDrive instructions are on the Pine64 wiki.]

==== Install from the booted microSD ====
# Flash Maemo Leste to the microSD card
# Insert microSD card and boot the phone
# 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.
# Extract the image file so that it only ends in ".img"
# 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.
# Turn off phone, remove microSD card and then turn on the phone.

== Post-Installation ==

=== How to take a picture ===

Maemo userland to take pictures or make videos is ready yet. The default camera app is pinhole: https://github.com/piggz/harbour-pinhole/

Both cameras (rear and front) are supported. Work in ongoing to improve the camera app.

To open the (pinhole) camera from the terminal:
$ harbour-pinhole

Or open it from Maemo desktop "Camera" icon.

In order to trigger auto-focus:
$ v4l2-ctl -d /dev/v4l-subdev1 -c focus_automatic_continuous=1

Or trigger autofocus using the commands to start and stop manually:
$ v4l2-ctl -d /dev/v4l-subdev1 -c auto_focus_start=1

then wait till it gets the focus where you want, then
$ v4l2-ctl -d /dev/v4l-subdev1 -c auto_focus_stop=1

You can use this script as reference to take a picture:
https://github.com/OpenMandrivaAssociation/pinephone-tools/blob/master/camera-setup

Or use libcamera tools (libcamera-tools package). To list the cameras:
$ cam -l

Example to capture 10 pictures with the rear camera:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/some_dir --capture=10

Example to capture 10 pictures with the front camera:
$ cam --camera "/base/i2c-csi/front-camera@3c" --file=/home/user/some_dir --capture=10

And then, conver the raw ".bin" files to some useful format with ffmpeg or any other image conversion tool. Example:
$ ffmpeg -f image2 -vcodec rawvideo -s 1600x1200 -pix_fmt bayer_bggr8 -i picture.bin converted_picture.jpeg

Other option is to use "cam" to capture to DNG. Example:
$ cam --camera "/base/i2c-csi/rear-camera@4c" --file=/home/user/frame-#.dng --capture=10

And then convert to .ppm (for .tiff use "-T" cmd line parameter). Eg:
$ dcraw frame-cam0-stream0-000001.dng

Also the graphical tool "qcam" is working! Run it with:
$ qcam -r gles -spixelformat=NV21,width=1280,height=720 -platform xcb -style=fusion

=== Enabling Flash Light / Torch ===

Enable:
$ echo 1 > /sys/class/leds/white:flash/brightness

Disable:
$ echo 0 > /sys/class/leds/white:flash/brightness

Trigger flash strobe:
$ echo 1 > /sys/class/leds/white:flash/flash_strobe

=== PinePhone Keyboard ===

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 ):

$ ppkb-i2c-flasher -e i2c -i fw-user.bin write reset

Load the xkb layout ( available here: https://codeberg.org/phalio/ppkb-layouts/src/branch/main/xkb )

$ setxkbmap pp altgr

=== Suspend ===

Suspend can be triggered with:
$ echo mem > /sys/power/state

A temporary workaround for calling suspend from UI is here: https://github.com/rafael2k/maemo-suspend/

=== Volume Applet ===

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:

sink_name=alsa_output.0.HiFi__hw_PinePhone_0__sink

=== Installing apps ===

* Apps can be installed just as on any Devuan system with:
$ sudo apt install ''package-name''
* There is also the app store.

=== Launching apps ===

This works for any app. Say for instance, you want to run Iceweasel/Firefox:

* Launch apps from the desktop
* Launch apps from your console:
$ iceweasel &
* Install a universal app launcher that you can run from desktop:
$ sudo apt install desktop-cmd-exec

=== Make apps show up on desktop ===

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])

To view a list of currently installed apps, do:

$ sudo apt list --installed | less

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.

=== Unhide the keyboard ===

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).

=== Note about Calculator ===

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.

=== Time zone / World Clock ===

Currently (06/15/2022) the interface to the default GUI clock has a few bugs but the workaround is to:

* 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.

* Or just use the console:

$ sudo date -s HH:MM
$ sudo date -s YYYYMMDD
$ sudo ln -s /usr/share/zoneinfo/YOURREGION/YOURCITY /etc/localtime

=== More Tips & Tricks ===

Visit [https://leste.maemo.org/Tricks '''this page'''] for more general advice on customizing Maemo on your PinePhone.

[[Category:Device]]

Nokia N9

2026-09-27T07:41:30Z

Arno11-n900:

{{Infobox Device
|image=
|manufacturer=Nokia
|codename=Lankku
|dimensions=116.5x61.2x12.1mm
|release_date=September 2011
|soc=TI OMAP3630
|dram=1024M
|power=
|display=480x854 3.9" AMOLED
|video=PowerVR SGX530
|audio=
|network=
|storage=16/64GB flash
|usb=
|camera=
|sensors=
|other=
}}

[[Category:Device]]

== Status ==

TODO

== Mainline Linux ==

14:49 <sre> tmlind: parazyd: not sure if you found my old n9/50 display branch already (I did not read full history since you pinged me). I think only this patch is needed to get display output on n9/50:
https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-n900.git/commit/?h=n950-display-tony&id=d4cbc226a30b29bf2583ffff97b052c9ec68c8a3
14:52 <parazyd> I have these: https://github.com/parazyd/arm-sdk/tree/master/extra/patches/linux-n9-patches
14:52 <parazyd> But it's 4.16
14:59 <sre> parazyd: ok, 4.16 is... old. Basically the features for the first four patches reached mainline. Patches 5-7 add automatic rotation and have not yet been integrated,
but screen works without them (one just needs to rotate
manually). Also they are easy to rebase and I don't see any problems upstreaming them after Tomi's cleanup series has landed.
14:59 <sre> The 'rotation' property is already documented in DT bindings :) Finally patch 8 is required on OMAP3 devices and has not yet been upstreamed either. Without that display does not work at all on n9/50.
15:00 <sre> Also on mainline the DSI command mode panel driver works like the other DRM panel drivers, so the panel timing is described in the driver instead of DT.
15:00 <sre> so support for "nokia,pyrenees" needs to be added in the driver instead of describing the timings in DT

== Partitioning ==

https://talk.maemo.org/showthread.php?t=91914

== Installation ==

'''WORK IN PROGRESS'''

In Harmattan, go to '''Settings->Applications->Installations''' and enable '''Allow installation from non-Store sources'''.
Then connect to WiFi and navigate to http://maedevu.maemo.org/images/n9/n9repomirror_0.7.2_armel.deb and install the package.

After installation, go to '''Settings->Security->Developer mode''' and enable '''Developer mode'''. Your device will do some
operations and then reboot. Once rebooted, reconnect to WiFi if necessary and go back to '''Settings->Security->Developer mode'''
and install '''Debugging''' (other packages as a plus). Now you should have a Terminal app.

For root access, in the terminal you can type:

$ devel-su
Password: rootme

For ssh access, set a password for the user:
$ devel-su
# passwd user

Then you can ssh:
$ ssh user@RM696

Remove openmode warning:
$ devel-su
# disclaimer-cal remove View-openmode

Download ubiboot (on device):

$ mkdir -p /home/user/MyDocs/boot && cd /home/user/MyDocs/boot
$ wget http://maedevu.maemo.org/images/n9/ubiboot-02_0.3.5_301013.tar
$ tar xf ubiboot-02_0.3.5_301013.tar
$ rm ubiboot-02_0.3.5_301013.tar
$ md5sum *
e76ed3f0cf0cc172f668b970ae778a71 md5sums.txt
d1e1a6eb6d877f53a01e946a5ccf5017 ubiboot-02.menus.cpio
adfbdc7d6cca6638b2dd079105d8daeb ubiboot.conf
d6d7081cffe2684944f141bc9a71fea9 zImage_2.6.32.54-ubiboot-02_301013
$ devel-su
# cd /boot
# wget http://maedevu.maemo.org/images/n9/zImage_2.6.32.54-openmode_l2fix
# cd /
# wget http://maedevu.maemo.org/images/n9/preinits.tar
# md5sum preinits.tar
515a8e1e5506f45afbc139c137d496b7 preinits.tar
# tar xf preinits.tar
# rm preinits.tar

Put your device in Upgrade mode:

$ lsusb
Bus 001 Device 084: ID 0421:0105 Nokia Mobile Phones Nokia Firmware Upgrade Mode

Disable watchdogs:

# 0xFFFF -F no-omap-wd,no-ext-wd,no-lifeguard-reset

Power off the N9 completely, and run flasher to flash ubiboot kernel, then connect the N9 with USB:

# flasher -a firmware.bin -k zImage_2.6.32.54-ubiboot-02_301013 --flash-only=kernel -f -R

If everything was performed correctly, the device should boot in an animated bootmenu if you disconnected
the USB cable, or maintenance mode if USB is still connected.

Motorola Razr (2011)

2026-09-27T07:40:26Z

Arno11-n900:

{{Infobox Device
|image=[[File:XT910Lockscreen.jpg|250px]]
|manufacturer=Motorola
|codename=Spyder XT910, XT912
|dimensions=130x68.9x7.1mm
|release_date=11-11-11
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|display=960x540 4.3"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=
|other=
|category=unsupported
|sw_kernel=6.1
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Unkown
|sw_audio=Unkown
|sw_calls=Unkown
|sw_sms=Unkown
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Unkown
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=No
|sw_compass=No
|sw_gyro= No
|sw_proximity=Yes
|sw_als=No
|sw_gps=Unkown
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=Unkown
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

* A Razr or Droid Razr or Droid Razr MAXX with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux or Windows system
* Android Tools: fastboot
* get allow-mbmloader-flashing-mbm.bin for your device (xt910 or xt912) from an android update zip
* Flashing tools:
** XZ Utils and coreutils for Linux
** Etcher[https://github.com/balena-io/etcher] for Windows

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

# utags-xt910-16-mmcblk1p8-boots-mmcblk1p13-kexecboot.bin
# droid4-kexecboot.img

Installation:

# Create a working directory with above mentioned files in it
# Power off the Razr and connect it to the host machine with MicroUSB cable
# Start the device in fastboot mode. For this press power button and bottom volume key simultaneously and release them after a second.

=== Setting up kexecboot ===

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

<pre>
sudo fastboot flash mbm allow-mbmloader-flashing-mbm.bin
sudo fastboot reboot-bootloader
sudo fastboot flash bpsw droid4-kexecboot.img
sudo fastboot flash utags utags-xt910-16-mmcblk1p8-boots-mmcblk1p13-kexecboot.bin
sudo fastboot reboot
</pre>

The device should reboot and show kexecboot menu for a few seconds before it boots to Android.

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

The battery in 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.

== Serial Cable ==

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

== Bluetooth ==

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

Using a bluetooth headset:
sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now.

== Additional Tips ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

logos can be flashed via fastboot flash logo.bin logo.bin

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

== Using a configured Leste sdcard in a different Razr ==

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.

To recalibrate the wifi firmware on a different Razr, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.
[[Category:Device]]

Motorola Droid Bionic

2026-09-27T07:39:50Z

Arno11-n900:

{{Infobox Device
|image=[[File:Bionic.jpg|250px]]
|manufacturer=Motorola
|codename=Targa XT875
|dimensions=127x67.3x12.7mm
|release_date=2011-09-8
|soc=TI OMAP4430
|dram=1024MB DDR2
|power=
|display=960x540 4.3"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, Kionix KXTf9 accelerometer, St L3GD20H Gyro, ISL29030 proximity and illuminance, TMP105 temperature sensor
|other=
|category=Supported
|sw_kernel=5.18.x
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=No
|sw_touchscreen=Yes
|sw_keyboard=
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes, [[https://github.com/maemo-leste/pvr-omap4/|SGX540, closed driver|]]
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=No, needs kernel work
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No, needs kernel/userspace work
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=70mW, needs sim inserted
|sw_standbytime=91.8h (with HW4X)
}}

== Installation ==

Hardware requirements:

* Droid Bionic with fully charged battery
* MicroUSB cable
* MicroSD card

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

Download from https://phoenix.maemo.org/view/Images/job/leste-image-bionic/

# Latest maemo-leste-1.0-armhf-bionic-*.img.xz

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

# droid4-kexecboot.img

Download or clone https://github.com/IMbackK/bionic-clown-boot

Follow the instructions in bionic-clown-boot's readme to install kexecboot on your device.

Now, flash the Maemo Leste image to your sdcard:

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

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

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

== Notes ==

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

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

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

== Serial Cable ==

As explained at http://muru.com/linux/d4 , the Droid 4 and Bionic both expose 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 Bionic, using instructions at https://jethomson.wordpress.com/2010/02/21/diy-usb-to-serial-cable-for-3usd/

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded

== Unlocking the modem for usage in Europe ==

Tony suggested these values, Wizzup confirmed it to work on his Bionic in Europe/Amsterdam.

<pre>
apt install build-essential
git clone https://github.com/tmlind/tcmdrw
cd tcmdrw
make
./tcmdrw 1877=8703E80400000200
./tcmdrw 6850=05
</pre>

Tony also writes:

<pre>
22:34 < tmlind> hmm so i had to do this for 3g gain: tcmdrw 1143=aaff0000, got that value from xt910 firmware i think, otherwise 3g signal was weak
22:43 < tmlind> Wizzup: great, the 1143 setting is for 1900 frequency only to get decent signal on t-mo in the us
</pre>

<pre>
22:37 < tmlind> i also had to do tcmdrw 6850=05 for 3g voice to work properly
</pre>

== Stuff to try ==

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

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

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

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

==== USSD ====

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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.10.4 || Mainline + some patches not yet in mainline - see https://git.maemo.org/leste/droid4-linux
|-
| Serial || Yes || On MicroUSB port, requires [[#Serial Cable|special cable]]
|-
| Charging || Yes ||
|-
| USB slave || Yes ||
|-
| USB host (OTG) || No ||
|-
| Touchscreen || Yes || Capacitive
|-
| Keyboard || N/A ||
|-
| Screen || Yes ||
|-
| HDMI-out || Yes || No UI integration
|-
| TV-out || N/A ||
|-
| 3D Acceleration || Yes || PowerVR SGX540 (closed driver) - https://git.maemo.org/leste/pvr-omap4/
|-
| Vibration Motor || Yes ||
|-
| Audio || Yes || Switch around in alsamixer to get the right outputs working ('Speaker Right' set to 'HiFi' and 'HiFi' set to above 0 gets you output)
|-
| Phone calls || WIP || Untested
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Wifi || Yes ||
|-
| Ethernet || N/A ||
|-
| IrDA || N/A || Missing in hardware
|-
| 2G/3G data || Yes || Works with ofono, no UI yet - see https://git.maemo.org/leste/connui-cellular/
|-
| 4G data || No || Needs kernel work
|-
| Bluetooth || Yes || Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded
|-
| FM Transmitter || No || Apparently exists, and will need serdev kernel modules/drivers
|-
| FM Receiver || No ||
|-
| Nfc || No || no hardware
|-
| Accelerometer || Yes ||
|-
| Compass || Yes || Available in /sys (after loading ak8975 module. No Leste integration)
|-
| Gyro || No || needs kernel work
|-
| Proximity sensor || Yes ||
|-
| Ambient Light Sensor || Yes ||
|-
| GPS || Yes || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| AGPS || No ||
|-
| Front Camera || No ||
|-
| Back Camera(s) || No ||
|-
| Idle power consumption || ~70 mW || Needs sim inserted
|-
| Idle Battery life on new battery || 91.8 h || With HW4X
|}

[[Category:Device]]

Motorola Droid 4

2026-09-27T07:39:05Z

Arno11-n900:

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|display=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, TMP105 temperature, ISL29030 proximity and illuminance
|other=
|category=Supported
|sw_kernel=6.18 LTS
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
# NOTE: be sure there's only one file matching maemo-leste-5.0-armhf-droid4-*.img.xz before running this command
xzcat maemo-leste-5.0-armhf-droid4-*.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

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]):
udevadm hwdb --update
udevadm trigger

This should survive a reboot.

== Serial Cable ==

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

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

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

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded. So you should do:

<pre>
sudo apt install firmware-ti-connectivity
sudo modprobe hci_uart
sudo hciconfig hci0 up
sudo hcitool lescan
</pre>

== Stuff to try ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

<pre>
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
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
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
</pre>

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

==== USSD ====

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

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

If one wants to mirror the screen on HDMI, this can be done like so, for landscape:

<pre>
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1
</pre>

For rotation, something like this might or might not work:

<pre>
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00ROT"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right
</pre>

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

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

==== Torch ====

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.

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):

<source>
##Install the prerequisites
$ sudo apt install i2c-tools

## Turn LED on in torch mode
$ sudo i2cset -y 2 0x53 0x10 0x1a

## Turn LED on in privacy indication mode
$ sudo i2cset -y 2 0x53 0x10 0x19

## Turn LED off (in any mode)
$ sudo i2cset -y 2 0x53 0x10 0x18

## Use LED for doing a hella bright flash for some time once and then turn off
$ sudo i2cset -y 2 0x53 0x10 0x1b

</source>

== Using a configured Leste sdcard in a different Droid4 ==

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.

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.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

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

== Status overview ==

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

[[Category:Device]]

Motorola Droid 3

2026-09-27T07:38:21Z

Arno11-n900:

{{Infobox Device
|image=
[[File:Motorola Droid 3 Leste Chimera.jpg|thumb]]
|manufacturer=Motorola
|codename=Solana XT862 / XT860
|dimensions=todo
|release_date=todo
|soc=TI OMAP4430
|dram=512MB DDR2
|power=
|display=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=todo
|other=
|category=Supported
|sw_kernel=6.1.9
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=No
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=No (needs modem work)
|sw_sms=No (needs modem work)
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=
|sw_4g=No
|sw_bluetooth=todo
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=No (needs modem work)
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=
|sw_standbytime=
}}

'''This device is called "Motorola Milestone 3" outside of the US.'''

== Installation ==

Hardware requirements:

* Droid 3 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux system
* Android Tools: fastboot adb

Download latest Chimera release from https://maedevu.maemo.org/images/droid3/

# Latest maemo-leste-1.0-armhf-droid3-20240908.img.xz

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

# droid4-kexecboot.img

Download or clone https://github.com/MerlijnWajer/bionic-clown-boot/tree/solana (solana branch!)

Follow the instructions in bionic-clown-boot's readme to install kexecboot on your device.

Now, flash the Maemo Leste image to your sdcard.

== Notes ==

IMPORTANT: Set the USB mode to "PC mode" instead of "mass storage mode" on your device before running install.sh
on bionic-clown-boot

Device is still heavy work in the progress. The following is known not to work:

* Brightness control (screen is always max brightness) You can scale the brightness using xrandr:
<pre>
xrandr --output DSI-1 --brightness 0.5
</pre>
* Keyboard backlight
* Modem interrupts, it is visible on USB but other communication with it doesn't work
* pstore (needs figuring out what the reserved memory is on Android)
* See if we can use 512MB ram instead of 509MB (see dts)
* <s>3d shows some frame lag / misdrawing, so probably powervr clock needs adjusting</s> (seems solved on kernel 5.15)
* <s>touchscreen buttons do not work yet</s> (fixed on 5.15)
* keyboard layout in Leste is not faithful to the icons on the keyboard, but rather mostly mimic droid 4

Additionally, the device suffers from random hangs while in use, causing resets. When pstore works, we can hopefully figure this out. <s>(Haven't seen them on 5.15)</s> (Came back on kernel 6.x) It might be a power-management-related issue, or a GPU issue (last log line shows something about OMAP complaining about DRM), or something else. The emergency shell works just fine with no hangs at all.

There is a workaround to the random hangs that work for some in 6.1. Here is how to work around this.

Download the latest Chimaera release: maemo-leste-1.0-armhf-droid3-20250608.img.xz and follow the same installation instructions provided above.

*From the kexecboot menu, select the "emergency shell" startup.
*Bypass the login prompt, ALT-D, the kernel will continue to boot into the Hildon window manager.
*Immediately try and configure your wifi settings, the device might hang and reboot. Reset the battery and try again until you get it configured.
*Once wifi is configured, let the device sleep, having the screen off reduces the chances of it freezing up again.
*ssh/scp in to the D3 from another device.
*Replace the script in the /etc/init.d/powervr with this:
<pre>
#!/sbin/openrc-run

depend() {
after eudev kmod
before xorg xsession hildon-desktop
}

start() {
ebegin "Starting PowerVR"

modprobe pvrsrvkm_omap4_sgx540_120 || true

for i in 1 2 3 4 5; do
[ -e /sys/bus/platform/devices/56000000.gpu/power/control ] && break
sleep 1
done

#echo 0xffffffff > /sys/module/pvrsrvkm_omap4_sgx540_120/parameters/gPVRDebugLevel 2>/dev/null || true
echo on > /sys/bus/platform/devices/56000000.gpu/power/control 2>/dev/null || true

/usr/bin/pvrsrvinit || true

eend 0
}

stop() {
ebegin "Stopping PowerVR"
eend 0
}
</pre>

*Reboot always using the "emergency shell" startup. Use xrandr to reduce the screen brightness. Chimaera should run without random hangs.

Also, the device often comes network locked. [[User:Wizzup]] has access to Sigmakey software and can help remotely remove the network lock.

If you run the battery dead, you cannot recharge using the MicroUSB cable. It is recommended to purchase a wall-wort to externally charge the battery.

If you have got the device stuck, you should hold the power button for about 7 seconds. Droid3 will display a white LED letting you know that it is shutting down. Once the LED shuts off, power on the device at any time. If this doesn't work, remove the battery and reset it.

== Conversations ==

*You can join IRC channels in conversations.
*You can create contacts in osso-addressbook to send messages or make calls.
*XMPP works.

== Music ==

*Lollypop works very well for the droid3. The controls are a bit small but are manageable.
*CMUS works, but chews up a lot of battery. It uses some remote M3 CPUs which are not available to normal Linux.

== Gallery ==
<gallery>
neofetch.png
Terminal.JPG
Htop.png
Main.png
Status.png
Lollypop.png
3600bat.JPG
irssi.JPG
</gallery>
[[Category:Device]]

Nokia N900

2026-09-27T07:36:47Z

Arno11-n900:

{{Infobox Device
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]
|manufacturer=Nokia
|codename=Rover, RX-51
|dimensions=110.9mm x 59.8mm x 18mm
|release_date=2009-11-11
|category=Supported
|soc=TI OMAP 3430 @600MHz overclock @805MHz Cortex-A8 Armv7‑A
|dram=256 MB Mobile DDR
|power=
|display=800x480 3.5" Resistive TFT
|video=PowerVR SGX530
|audio=
|network=WL1251
|storage=32GB
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=6.18
|sw_serial=Yes, UART under battery, 2.7V max!
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=
|sw_tv=Yes
|sw_3daccel=Yes, closed driver
|sw_vibration=Yes
|sw_audio=Yes (complex, ucm, no speaker protection)
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=Yes, actually CIR, not IrDA
|sw_2g3gdata=Yes
|sw_4gdata=
|sw_bluetooth=No
|sw_fmtx=Yes
|sw_fmrx=No
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=
|sw_backcam=
|sw_idlepower=160mW (WIP)
|sw_standbytime=
}}

== Installation ==

The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.

=== Image installation ===

* Images built automatically can be obtained at the download page: https://maedevu.maemo.org/images/n900/
* If you want to build a current image yourself use debos: https://git.maemo.org/leste-cicd/debos-leste but beware that downloadable images are genereally more stable than the most recent development build.

dd the image to an sd card.

If using a Windows machine, you can use [https://etcher.io/ Etcher]

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)

=== Bootloader (U-Boot) setup ===

==== Quick ====

If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly (dual boot mode):

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/ on *nix systems make sure to $ chmod a+x 0xFFFF

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/ save it in a subfolder called test.

3. Turn off Nokia N900, issue the following command on PC <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code> you will get a message similar to the following:

<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
</pre>

and the connect Nokia N900 to the PC. you will then get a message like so:

<pre>
Found USB device: RX-51/RM-680/RM-696 (0x421:0x106) in Cold flashing mode
USB device product string: Nokia USB ROM
USB device serial number string: (not detected)
Detected USB device: (not detected)
Waiting for ASIC ID...
Detected OMAP3430 chip (revision 87)
Device: (not detected)
HW revision: (not detected)
NOLO version: (not detected)
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: (not detected)
Content eMMC version: (not detected)
Root device: (not detected)
USB host mode: (not detected)
R&D mode: (not detected)
Switching to NOLO mode...
Sending OMAP memory boot message...
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Load image:
File: test/u-boot-2013.04-2.bin
Image type: kernel
Image size: 212864 bytes
Sending image header...
Sending image...
100% [#################################################################]
Done
</pre>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code> you will get an output such as:
<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Booting kernel with default cmdline...
</pre>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. The screen might not be backlit so it will be difficult to read. 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>. The screen might be very dim and look off. So it might be difficult to see. Boot up the first time will take a long time full 2 min on test. Some text will show and will then go back to black screen but eventually you will see the splash screen and later the icons will show.

To flash u-boot permanently, you can issue the following command:

'''(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)''')

<pre>
sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f
</pre>

==== Existing Fremantle ====

If you have a functional Fremantle installation and you want to keep it, you can follow these steps instead:

1. Install <code>u-boot-flasher</code> (U-Boot with kernel 2.6.28-omap1). This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

2. Check with <code>uname -a</code> to be sure what kernel you are running. If you were running a power kernel, install "Linux kernel for power user (boot image for U-Boot)". This is important, to ensure that the correct kernel is booted, otherwise modules will not match and boot will fail.

3. Add Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

4. Reboot the device with the keyboard slide open (U-boot will boot the default option if the keyboard slide is closed)

=== Increase filesystem size ===

Run the following script: <code>/etc/expandcard.sh</code>

== Serial ==

http://n900.elektranox.org/serial-adapter.html

http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports

Use this command line (specifically the part after <code>rootwait</code>):

<pre>
root=/dev/mmcblk0p2 rootwait console=ttyS2,115200 verbose earlyprintk debug
</pre>

== Notes ==
=== Speakers ===

* 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.
=== Torch ===

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.

In the meantime, the LEDs can be used as a torch manually using <code>i2cset</code>.
However, '''BE WARNED:''' setting wrong values via i2c runs the risk of over-driving the LEDs and causing permanent hardware damage.

<source lang="shell-session">
# Install the prerequisites
$ sudo apk add i2c-tools

# Unload the driver in case it is already loaded. We will use i2c manually
$ sudo modprobe -r adp1653

# Enable the chip
$ echo 88 | sudo tee /sys/class/gpio/export
$ echo "out" | sudo tee /sys/class/gpio/gpio88/direction
$ echo 1 | sudo tee /sys/class/gpio/gpio88/value

# Turn the torch on, using the lowest torch current - DO NOT use other values here or you risk burning the LED
# Values between 1 and 7 enable the red privacy/recording led, with different intensity
# 0x8 is the lowest torch intensity, and we do not recommend going above it
$ sudo i2cset -y 2 0x30 0x0 0x8

# Turn the torch off
$ sudo i2cset -y 2 0x30 0x0 0x0

# Disable the chip
$ echo 0 | sudo tee /sys/class/gpio/gpio88/value
$ echo 88 | sudo tee /sys/class/gpio/unexport
</source>

== Power Management ==

This ticket tracks hitting idle states for the N900: https://github.com/maemo-leste/bugtracker/issues/545

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

* https://wiki.maemo.org/N900_Hardware_Power_management
* https://wiki.maemo.org/N900_Hardware_Power_Consumption

Run:
<pre>
modprobe ledtrig-default-on
</pre>

And:
<pre>
echo default-on > /sys/class/leds/debug::sleep/trigger
</pre>

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.

Currently it does not yet reliably reach any sleep modes.

See this code for a work in progress power management script: https://github.com/maemo-leste/n900-pm

== Battery calibration ==

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.

Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.

* Fully charge the Nokia N900
* 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 process from the beginning (fully charge the device again).
* 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.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* 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.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

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.

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.
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.

== Accessing MTD ==

List devices:
cat /proc/mtd

Mount:
apt install mtd-utils
mkdir -vp /mnt/fremantle
ubiattach -p /dev/mtd5
mount -t ubifs ubi:rootfs /mnt/fremantle

== Overclocking (optional) ==

'''Overclocking is now available in -devel using cpufreq boost.'''

It uses 250-500-550-600-720-805MHz frequencies

To enable it, edit:

<code>/sys/devices/system/cpu/cpufreq/boost</code>

And replace 0 by 1.

It is possible to customise max/min/available frequencies editing files in:

<code>/sys/devices/system/cpu/cpu0/cpufreq/</code>

'''No other steps are needed and updates/upgrades work with boost mode.'''

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

As root
<code>cpufreq-set -c 0 -g conservative</code>

'''WARNING: some devices can't run at 805MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 805000 by 720000 in scaling_max_freq file and finally select conservative governor'''

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

1) From Fremantle: add new Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

2) From Maemo Leste (run as root):

<pre>
cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user
dtc -I dtb -O dts /home/user/omap3-n900.dtb -o /home/user/omap3-n900.dts
</pre>

Edit:

<pre>
/home/user/omap3-n900.dts
</pre>

(Now it's time to modify frequencies and voltage: be careful to do exactly the same)

Replace all content in "opp-table { opp1 opp2 opp3 opp4 opp5 opp6 };"

New opp-table for example:

<pre>
opp-table {
compatible = "operating-points-v2-ti-cpu";
syscon = < 0x05 >;
phandle = < 0x03 >;

opp1-250000000 {
opp-hz = < 0x00 0xee6b280 >;
opp-microvolt = < 0xee098 0xee098 0xee098 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp2-500000000 {
opp-hz = < 0x00 0x1dcd6500 >;
opp-microvolt = < 0x106738 0x106738 0x106738 >;
opp-supported-hw = < 0xffffffff 0x03 >;
opp-suspend;
};

opp3-600000000 {
opp-hz = < 0x00 0x23c34600 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp4-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp5-850000000 {
opp-hz = < 0x00 0x32a9f880 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};
};
</pre>

And still as root:

<pre>
rm /home/user/omap3-n900.dtb
dtc -I dts -O dtb /home/user/omap3-n900.dts -o /home/user/omap3-n900.dtb
</pre>

Check your kernel version:

<code>uname -r</code>

For example if the result is 6.1.30, your vmlinuz version is vmlinuz-6.1.30

In the next command, replace "vmlinuz-<version>" by yours (i.e vmlinuz-6.1.30)

As root:

<pre>
cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb
mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX
</pre>

Now reboot and select 'Maemo Leste Overclock' in bootmenu.

('''WARNING with old method:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))

== Tips / Tweaks ==

=== SD Card and first boot===

To avoid overall slowness, SDXC U3 microSD card is a must. Class10 U1 cards are usually too slow to run Leste on N900 unfortunately.

'''WARNING''': unresponsive / freezing screen is normal during Hildon-desktop loading.

'''WARNING''': do not use zram and/or zswap.

First boot is a bit complicated because Leste is loading lot of things even if hildon-desktop is already visible (wait at least 3 min before clicking somewhere).
Connecting to Wi-Fi must be avoided until the second boot (otherwise apt-worker starts automatically and N900 is unresponsive for few minutes).
Don't forget to run /etc/expandcard.sh on first boot and check if swap is activated.
Then reboot.

=== Gnome-tracker in $HOME ===

By default trackers are indexing the entire $HOME folder, causing severe slowdown.

To avoid this issue, the solution (until a proper fix) is to add a <code>.nomedia</code> file in /home/user folder:

<pre>
touch /home/user/.nomedia
</pre>

=== Removing 250MHz CPU frequency (example) ===

Install <code>cpufrequtils</code>.

Replace 250000 by 500000 in <pre>/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq</pre>

'''Not persistent after reboot'''

=== More SWAP / SWAP activation (testing purpose) ===

('''Note: SWAP is already activated by default and use a swap file on SD card''')

Create a simple 1GB swap file on the SDcard if swap is missing:

<pre>sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576</pre>

(It takes some time...)

<pre>
sudo chmod 600 /
sudo mkswap /swapfile
sudo swapon /swapfile
</pre>

To make the change permanent open <code>/etc/fstab</code>:

<pre>
sudo nano /etc/fstab
</pre>

And add this line:

<pre>
/swapfile swap swap defaults 0 0
</pre>

To check if the swap is active:

<pre>
sudo swapon --show
</pre>

=== Tweaking Transitions (already optimized by default now) ===

Many options are missing in CSSU Features package but it is possible to edit them in transitions.ini.

As root

<pre>
nano /usr/share/hildon-desktop/transitions.ini
</pre>

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate/modify it through the transitions.ini file:

<pre>
[HOME]

radius = 1

radius_more = 2
</pre>

=== Video playing ===

Video playing is working fine using SMPLAYER:

- In Options / Preferences / General:

Media engine: Other: /user/bin/mplayer

- In Options / Preferences / Video:

Output driver: xv (0 - OMAP Textured Video)

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse (or User defined)

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: Auto

- In Options / Preferences / Performance:

Unable Allow frame drop

Hardware decoding: None

Prefer 360p - 480p max video format

(With overclocking, Video is working well using KODI 17.6 with equivalent A/V settings)

=== Voice Calls / SIP Calls ===

Now SIP calls and SIP messages are working out of the box using Twinkle.

Voice calls are now working out of the box as well.

If sound is distorted with Pulseaudio, run:

<pre>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</pre>

'''Note: Leste uses Pipewire by default now.'''

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.18 LTS || Mainline + PowerVR Patches: https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || Requires special hardware
|-
| Charging || Yes ||
|-
| Wireless || Yes || Firmware is non-free
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible
|-
| Keyboard || Yes ||
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || closed PowerVR driver
|-
| Overclock || Yes || up to 805MHz (stable & supported), 850MHz works with some devices (not supported), Turbo mode works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection and FMTX
|-
| Video || Yes || Xv acceleration, up to 360-480p. Max 360p for online streaming with SMplayer.
|-
| 2G/3G/3.5G data || Yes || Works with ofono - UI is working, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with Sphone or ofono scripts. Works with Conversations in -devel.
|-
| Phone calls || Yes || UCM support, sound is good. Works in 2G, 3G and 3.5G mode, works with Sphone
|-
| SIP calls / IM || Yes || Works with Twinkle, TLS transport is supported, Telepathy/Sphone integration is WIP
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Select 'FM Transmitter' in Pavucontrol
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>
|-
| FM Receiver || No || Depends on working Bluetooth stack
|-
| Accelerometer || Yes || Not used in Leste at the moment, since UI rotation does not work on N900
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || <code>evdev</code> 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'
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || No hardware
|-
| 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>
|-
| GPS || Yes ||
|-
| Infrared || Yes || TX only (hardware limitation). Works with pwm-ir-tx driver (patched)
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2026-09-27T07:29:00Z

Arno11-n900: /* Removing 250MHz CPU frequency (example) */

{{Infobox Device
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]
|manufacturer=Nokia
|codename=Rover, RX-51
|dimensions=110.9mm x 59.8mm x 18mm
|release_date=2009-11-11
|category=Supported
|soc=TI OMAP 3430 @600MHz overclock @805MHz Cortex-A8 Armv7‑A
|dram=256 MB Mobile DDR
|power=
|lcd=800x480 3.5" Resistive TFT
|video=PowerVR SGX530
|audio=
|network=WL1251
|storage=32GB
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=6.18
|sw_serial=Yes, UART under battery, 2.7V max!
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=
|sw_tv=Yes
|sw_3daccel=Yes, closed driver
|sw_vibration=Yes
|sw_audio=Yes (complex, ucm, no speaker protection)
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=Yes, actually CIR, not IrDA
|sw_2g3gdata=Yes
|sw_4gdata=
|sw_bluetooth=No
|sw_fmtx=Yes
|sw_fmrx=No
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=
|sw_backcam=
|sw_idlepower=160mW (WIP)
|sw_standbytime=
}}

== Installation ==

The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.

=== Image installation ===

* Images built automatically can be obtained at the download page: https://maedevu.maemo.org/images/n900/
* If you want to build a current image yourself use debos: https://git.maemo.org/leste-cicd/debos-leste but beware that downloadable images are genereally more stable than the most recent development build.

dd the image to an sd card.

If using a Windows machine, you can use [https://etcher.io/ Etcher]

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)

=== Bootloader (U-Boot) setup ===

==== Quick ====

If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly (dual boot mode):

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/ on *nix systems make sure to $ chmod a+x 0xFFFF

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/ save it in a subfolder called test.

3. Turn off Nokia N900, issue the following command on PC <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code> you will get a message similar to the following:

<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
</pre>

and the connect Nokia N900 to the PC. you will then get a message like so:

<pre>
Found USB device: RX-51/RM-680/RM-696 (0x421:0x106) in Cold flashing mode
USB device product string: Nokia USB ROM
USB device serial number string: (not detected)
Detected USB device: (not detected)
Waiting for ASIC ID...
Detected OMAP3430 chip (revision 87)
Device: (not detected)
HW revision: (not detected)
NOLO version: (not detected)
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: (not detected)
Content eMMC version: (not detected)
Root device: (not detected)
USB host mode: (not detected)
R&D mode: (not detected)
Switching to NOLO mode...
Sending OMAP memory boot message...
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Load image:
File: test/u-boot-2013.04-2.bin
Image type: kernel
Image size: 212864 bytes
Sending image header...
Sending image...
100% [#################################################################]
Done
</pre>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code> you will get an output such as:
<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Booting kernel with default cmdline...
</pre>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. The screen might not be backlit so it will be difficult to read. 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>. The screen might be very dim and look off. So it might be difficult to see. Boot up the first time will take a long time full 2 min on test. Some text will show and will then go back to black screen but eventually you will see the splash screen and later the icons will show.

To flash u-boot permanently, you can issue the following command:

'''(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)''')

<pre>
sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f
</pre>

==== Existing Fremantle ====

If you have a functional Fremantle installation and you want to keep it, you can follow these steps instead:

1. Install <code>u-boot-flasher</code> (U-Boot with kernel 2.6.28-omap1). This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

2. Check with <code>uname -a</code> to be sure what kernel you are running. If you were running a power kernel, install "Linux kernel for power user (boot image for U-Boot)". This is important, to ensure that the correct kernel is booted, otherwise modules will not match and boot will fail.

3. Add Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

4. Reboot the device with the keyboard slide open (U-boot will boot the default option if the keyboard slide is closed)

=== Increase filesystem size ===

Run the following script: <code>/etc/expandcard.sh</code>

== Serial ==

http://n900.elektranox.org/serial-adapter.html

http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports

Use this command line (specifically the part after <code>rootwait</code>):

<pre>
root=/dev/mmcblk0p2 rootwait console=ttyS2,115200 verbose earlyprintk debug
</pre>

== Notes ==
=== Speakers ===

* 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.
=== Torch ===

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.

In the meantime, the LEDs can be used as a torch manually using <code>i2cset</code>.
However, '''BE WARNED:''' setting wrong values via i2c runs the risk of over-driving the LEDs and causing permanent hardware damage.

<source lang="shell-session">
# Install the prerequisites
$ sudo apk add i2c-tools

# Unload the driver in case it is already loaded. We will use i2c manually
$ sudo modprobe -r adp1653

# Enable the chip
$ echo 88 | sudo tee /sys/class/gpio/export
$ echo "out" | sudo tee /sys/class/gpio/gpio88/direction
$ echo 1 | sudo tee /sys/class/gpio/gpio88/value

# Turn the torch on, using the lowest torch current - DO NOT use other values here or you risk burning the LED
# Values between 1 and 7 enable the red privacy/recording led, with different intensity
# 0x8 is the lowest torch intensity, and we do not recommend going above it
$ sudo i2cset -y 2 0x30 0x0 0x8

# Turn the torch off
$ sudo i2cset -y 2 0x30 0x0 0x0

# Disable the chip
$ echo 0 | sudo tee /sys/class/gpio/gpio88/value
$ echo 88 | sudo tee /sys/class/gpio/unexport
</source>

== Power Management ==

This ticket tracks hitting idle states for the N900: https://github.com/maemo-leste/bugtracker/issues/545

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

* https://wiki.maemo.org/N900_Hardware_Power_management
* https://wiki.maemo.org/N900_Hardware_Power_Consumption

Run:
<pre>
modprobe ledtrig-default-on
</pre>

And:
<pre>
echo default-on > /sys/class/leds/debug::sleep/trigger
</pre>

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.

Currently it does not yet reliably reach any sleep modes.

See this code for a work in progress power management script: https://github.com/maemo-leste/n900-pm

== Battery calibration ==

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.

Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.

* Fully charge the Nokia N900
* 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 process from the beginning (fully charge the device again).
* 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.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* 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.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

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.

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.
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.

== Accessing MTD ==

List devices:
cat /proc/mtd

Mount:
apt install mtd-utils
mkdir -vp /mnt/fremantle
ubiattach -p /dev/mtd5
mount -t ubifs ubi:rootfs /mnt/fremantle

== Overclocking (optional) ==

'''Overclocking is now available in -devel using cpufreq boost.'''

It uses 250-500-550-600-720-805MHz frequencies

To enable it, edit:

<code>/sys/devices/system/cpu/cpufreq/boost</code>

And replace 0 by 1.

It is possible to customise max/min/available frequencies editing files in:

<code>/sys/devices/system/cpu/cpu0/cpufreq/</code>

'''No other steps are needed and updates/upgrades work with boost mode.'''

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

As root
<code>cpufreq-set -c 0 -g conservative</code>

'''WARNING: some devices can't run at 805MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 805000 by 720000 in scaling_max_freq file and finally select conservative governor'''

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

1) From Fremantle: add new Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

2) From Maemo Leste (run as root):

<pre>
cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user
dtc -I dtb -O dts /home/user/omap3-n900.dtb -o /home/user/omap3-n900.dts
</pre>

Edit:

<pre>
/home/user/omap3-n900.dts
</pre>

(Now it's time to modify frequencies and voltage: be careful to do exactly the same)

Replace all content in "opp-table { opp1 opp2 opp3 opp4 opp5 opp6 };"

New opp-table for example:

<pre>
opp-table {
compatible = "operating-points-v2-ti-cpu";
syscon = < 0x05 >;
phandle = < 0x03 >;

opp1-250000000 {
opp-hz = < 0x00 0xee6b280 >;
opp-microvolt = < 0xee098 0xee098 0xee098 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp2-500000000 {
opp-hz = < 0x00 0x1dcd6500 >;
opp-microvolt = < 0x106738 0x106738 0x106738 >;
opp-supported-hw = < 0xffffffff 0x03 >;
opp-suspend;
};

opp3-600000000 {
opp-hz = < 0x00 0x23c34600 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp4-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp5-850000000 {
opp-hz = < 0x00 0x32a9f880 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};
};
</pre>

And still as root:

<pre>
rm /home/user/omap3-n900.dtb
dtc -I dts -O dtb /home/user/omap3-n900.dts -o /home/user/omap3-n900.dtb
</pre>

Check your kernel version:

<code>uname -r</code>

For example if the result is 6.1.30, your vmlinuz version is vmlinuz-6.1.30

In the next command, replace "vmlinuz-<version>" by yours (i.e vmlinuz-6.1.30)

As root:

<pre>
cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb
mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX
</pre>

Now reboot and select 'Maemo Leste Overclock' in bootmenu.

('''WARNING with old method:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))

== Tips / Tweaks ==

=== SD Card and first boot===

To avoid overall slowness, SDXC U3 microSD card is a must. Class10 U1 cards are usually too slow to run Leste on N900 unfortunately.

'''WARNING''': unresponsive / freezing screen is normal during Hildon-desktop loading.

'''WARNING''': do not use zram and/or zswap.

First boot is a bit complicated because Leste is loading lot of things even if hildon-desktop is already visible (wait at least 3 min before clicking somewhere).
Connecting to Wi-Fi must be avoided until the second boot (otherwise apt-worker starts automatically and N900 is unresponsive for few minutes).
Don't forget to run /etc/expandcard.sh on first boot and check if swap is activated.
Then reboot.

=== Gnome-tracker in $HOME ===

By default trackers are indexing the entire $HOME folder, causing severe slowdown.

To avoid this issue, the solution (until a proper fix) is to add a <code>.nomedia</code> file in /home/user folder:

<pre>
touch /home/user/.nomedia
</pre>

=== Removing 250MHz CPU frequency (example) ===

Install <code>cpufrequtils</code>.

Replace 250000 by 500000 in <pre>/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq</pre>

'''Not persistent after reboot'''

=== More SWAP / SWAP activation (testing purpose) ===

('''Note: SWAP is already activated by default and use a swap file on SD card''')

Create a simple 1GB swap file on the SDcard if swap is missing:

<pre>sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576</pre>

(It takes some time...)

<pre>
sudo chmod 600 /
sudo mkswap /swapfile
sudo swapon /swapfile
</pre>

To make the change permanent open <code>/etc/fstab</code>:

<pre>
sudo nano /etc/fstab
</pre>

And add this line:

<pre>
/swapfile swap swap defaults 0 0
</pre>

To check if the swap is active:

<pre>
sudo swapon --show
</pre>

=== Tweaking Transitions (already optimized by default now) ===

Many options are missing in CSSU Features package but it is possible to edit them in transitions.ini.

As root

<pre>
nano /usr/share/hildon-desktop/transitions.ini
</pre>

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate/modify it through the transitions.ini file:

<pre>
[HOME]

radius = 1

radius_more = 2
</pre>

=== Video playing ===

Video playing is working fine using SMPLAYER:

- In Options / Preferences / General:

Media engine: Other: /user/bin/mplayer

- In Options / Preferences / Video:

Output driver: xv (0 - OMAP Textured Video)

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse (or User defined)

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: Auto

- In Options / Preferences / Performance:

Unable Allow frame drop

Hardware decoding: None

Prefer 360p - 480p max video format

(With overclocking, Video is working well using KODI 17.6 with equivalent A/V settings)

=== Voice Calls / SIP Calls ===

Now SIP calls and SIP messages are working out of the box using Twinkle.

Voice calls are now working out of the box as well.

If sound is distorted with Pulseaudio, run:

<pre>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</pre>

'''Note: Leste uses Pipewire by default now.'''

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.18 LTS || Mainline + PowerVR Patches: https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || Requires special hardware
|-
| Charging || Yes ||
|-
| Wireless || Yes || Firmware is non-free
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible
|-
| Keyboard || Yes ||
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || closed PowerVR driver
|-
| Overclock || Yes || up to 805MHz (stable & supported), 850MHz works with some devices (not supported), Turbo mode works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection and FMTX
|-
| Video || Yes || Xv acceleration, up to 360-480p. Max 360p for online streaming with SMplayer.
|-
| 2G/3G/3.5G data || Yes || Works with ofono - UI is working, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with Sphone or ofono scripts. Works with Conversations in -devel.
|-
| Phone calls || Yes || UCM support, sound is good. Works in 2G, 3G and 3.5G mode, works with Sphone
|-
| SIP calls / IM || Yes || Works with Twinkle, TLS transport is supported, Telepathy/Sphone integration is WIP
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Select 'FM Transmitter' in Pavucontrol
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>
|-
| FM Receiver || No || Depends on working Bluetooth stack
|-
| Accelerometer || Yes || Not used in Leste at the moment, since UI rotation does not work on N900
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || <code>evdev</code> 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'
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || No hardware
|-
| 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>
|-
| GPS || Yes ||
|-
| Infrared || Yes || TX only (hardware limitation). Works with pwm-ir-tx driver (patched)
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2026-09-27T07:24:50Z

Arno11-n900: /* Tips / Tweaks */

{{Infobox Device
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]
|manufacturer=Nokia
|codename=Rover, RX-51
|dimensions=110.9mm x 59.8mm x 18mm
|release_date=2009-11-11
|category=Supported
|soc=TI OMAP 3430 @600MHz overclock @805MHz Cortex-A8 Armv7‑A
|dram=256 MB Mobile DDR
|power=
|lcd=800x480 3.5" Resistive TFT
|video=PowerVR SGX530
|audio=
|network=WL1251
|storage=32GB
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=6.18
|sw_serial=Yes, UART under battery, 2.7V max!
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=
|sw_tv=Yes
|sw_3daccel=Yes, closed driver
|sw_vibration=Yes
|sw_audio=Yes (complex, ucm, no speaker protection)
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=Yes, actually CIR, not IrDA
|sw_2g3gdata=Yes
|sw_4gdata=
|sw_bluetooth=No
|sw_fmtx=Yes
|sw_fmrx=No
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=
|sw_backcam=
|sw_idlepower=160mW (WIP)
|sw_standbytime=
}}

== Installation ==

The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.

=== Image installation ===

* Images built automatically can be obtained at the download page: https://maedevu.maemo.org/images/n900/
* If you want to build a current image yourself use debos: https://git.maemo.org/leste-cicd/debos-leste but beware that downloadable images are genereally more stable than the most recent development build.

dd the image to an sd card.

If using a Windows machine, you can use [https://etcher.io/ Etcher]

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)

=== Bootloader (U-Boot) setup ===

==== Quick ====

If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly (dual boot mode):

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/ on *nix systems make sure to $ chmod a+x 0xFFFF

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/ save it in a subfolder called test.

3. Turn off Nokia N900, issue the following command on PC <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code> you will get a message similar to the following:

<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
</pre>

and the connect Nokia N900 to the PC. you will then get a message like so:

<pre>
Found USB device: RX-51/RM-680/RM-696 (0x421:0x106) in Cold flashing mode
USB device product string: Nokia USB ROM
USB device serial number string: (not detected)
Detected USB device: (not detected)
Waiting for ASIC ID...
Detected OMAP3430 chip (revision 87)
Device: (not detected)
HW revision: (not detected)
NOLO version: (not detected)
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: (not detected)
Content eMMC version: (not detected)
Root device: (not detected)
USB host mode: (not detected)
R&D mode: (not detected)
Switching to NOLO mode...
Sending OMAP memory boot message...
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Load image:
File: test/u-boot-2013.04-2.bin
Image type: kernel
Image size: 212864 bytes
Sending image header...
Sending image...
100% [#################################################################]
Done
</pre>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code> you will get an output such as:
<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Booting kernel with default cmdline...
</pre>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. The screen might not be backlit so it will be difficult to read. 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>. The screen might be very dim and look off. So it might be difficult to see. Boot up the first time will take a long time full 2 min on test. Some text will show and will then go back to black screen but eventually you will see the splash screen and later the icons will show.

To flash u-boot permanently, you can issue the following command:

'''(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)''')

<pre>
sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f
</pre>

==== Existing Fremantle ====

If you have a functional Fremantle installation and you want to keep it, you can follow these steps instead:

1. Install <code>u-boot-flasher</code> (U-Boot with kernel 2.6.28-omap1). This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

2. Check with <code>uname -a</code> to be sure what kernel you are running. If you were running a power kernel, install "Linux kernel for power user (boot image for U-Boot)". This is important, to ensure that the correct kernel is booted, otherwise modules will not match and boot will fail.

3. Add Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

4. Reboot the device with the keyboard slide open (U-boot will boot the default option if the keyboard slide is closed)

=== Increase filesystem size ===

Run the following script: <code>/etc/expandcard.sh</code>

== Serial ==

http://n900.elektranox.org/serial-adapter.html

http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports

Use this command line (specifically the part after <code>rootwait</code>):

<pre>
root=/dev/mmcblk0p2 rootwait console=ttyS2,115200 verbose earlyprintk debug
</pre>

== Notes ==
=== Speakers ===

* 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.
=== Torch ===

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.

In the meantime, the LEDs can be used as a torch manually using <code>i2cset</code>.
However, '''BE WARNED:''' setting wrong values via i2c runs the risk of over-driving the LEDs and causing permanent hardware damage.

<source lang="shell-session">
# Install the prerequisites
$ sudo apk add i2c-tools

# Unload the driver in case it is already loaded. We will use i2c manually
$ sudo modprobe -r adp1653

# Enable the chip
$ echo 88 | sudo tee /sys/class/gpio/export
$ echo "out" | sudo tee /sys/class/gpio/gpio88/direction
$ echo 1 | sudo tee /sys/class/gpio/gpio88/value

# Turn the torch on, using the lowest torch current - DO NOT use other values here or you risk burning the LED
# Values between 1 and 7 enable the red privacy/recording led, with different intensity
# 0x8 is the lowest torch intensity, and we do not recommend going above it
$ sudo i2cset -y 2 0x30 0x0 0x8

# Turn the torch off
$ sudo i2cset -y 2 0x30 0x0 0x0

# Disable the chip
$ echo 0 | sudo tee /sys/class/gpio/gpio88/value
$ echo 88 | sudo tee /sys/class/gpio/unexport
</source>

== Power Management ==

This ticket tracks hitting idle states for the N900: https://github.com/maemo-leste/bugtracker/issues/545

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

* https://wiki.maemo.org/N900_Hardware_Power_management
* https://wiki.maemo.org/N900_Hardware_Power_Consumption

Run:
<pre>
modprobe ledtrig-default-on
</pre>

And:
<pre>
echo default-on > /sys/class/leds/debug::sleep/trigger
</pre>

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.

Currently it does not yet reliably reach any sleep modes.

See this code for a work in progress power management script: https://github.com/maemo-leste/n900-pm

== Battery calibration ==

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.

Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.

* Fully charge the Nokia N900
* 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 process from the beginning (fully charge the device again).
* 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.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* 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.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

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.

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.
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.

== Accessing MTD ==

List devices:
cat /proc/mtd

Mount:
apt install mtd-utils
mkdir -vp /mnt/fremantle
ubiattach -p /dev/mtd5
mount -t ubifs ubi:rootfs /mnt/fremantle

== Overclocking (optional) ==

'''Overclocking is now available in -devel using cpufreq boost.'''

It uses 250-500-550-600-720-805MHz frequencies

To enable it, edit:

<code>/sys/devices/system/cpu/cpufreq/boost</code>

And replace 0 by 1.

It is possible to customise max/min/available frequencies editing files in:

<code>/sys/devices/system/cpu/cpu0/cpufreq/</code>

'''No other steps are needed and updates/upgrades work with boost mode.'''

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

As root
<code>cpufreq-set -c 0 -g conservative</code>

'''WARNING: some devices can't run at 805MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 805000 by 720000 in scaling_max_freq file and finally select conservative governor'''

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

1) From Fremantle: add new Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

2) From Maemo Leste (run as root):

<pre>
cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user
dtc -I dtb -O dts /home/user/omap3-n900.dtb -o /home/user/omap3-n900.dts
</pre>

Edit:

<pre>
/home/user/omap3-n900.dts
</pre>

(Now it's time to modify frequencies and voltage: be careful to do exactly the same)

Replace all content in "opp-table { opp1 opp2 opp3 opp4 opp5 opp6 };"

New opp-table for example:

<pre>
opp-table {
compatible = "operating-points-v2-ti-cpu";
syscon = < 0x05 >;
phandle = < 0x03 >;

opp1-250000000 {
opp-hz = < 0x00 0xee6b280 >;
opp-microvolt = < 0xee098 0xee098 0xee098 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp2-500000000 {
opp-hz = < 0x00 0x1dcd6500 >;
opp-microvolt = < 0x106738 0x106738 0x106738 >;
opp-supported-hw = < 0xffffffff 0x03 >;
opp-suspend;
};

opp3-600000000 {
opp-hz = < 0x00 0x23c34600 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp4-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp5-850000000 {
opp-hz = < 0x00 0x32a9f880 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};
};
</pre>

And still as root:

<pre>
rm /home/user/omap3-n900.dtb
dtc -I dts -O dtb /home/user/omap3-n900.dts -o /home/user/omap3-n900.dtb
</pre>

Check your kernel version:

<code>uname -r</code>

For example if the result is 6.1.30, your vmlinuz version is vmlinuz-6.1.30

In the next command, replace "vmlinuz-<version>" by yours (i.e vmlinuz-6.1.30)

As root:

<pre>
cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb
mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX
</pre>

Now reboot and select 'Maemo Leste Overclock' in bootmenu.

('''WARNING with old method:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))

== Tips / Tweaks ==

=== SD Card and first boot===

To avoid overall slowness, SDXC U3 microSD card is a must. Class10 U1 cards are usually too slow to run Leste on N900 unfortunately.

'''WARNING''': unresponsive / freezing screen is normal during Hildon-desktop loading.

'''WARNING''': do not use zram and/or zswap.

First boot is a bit complicated because Leste is loading lot of things even if hildon-desktop is already visible (wait at least 3 min before clicking somewhere).
Connecting to Wi-Fi must be avoided until the second boot (otherwise apt-worker starts automatically and N900 is unresponsive for few minutes).
Don't forget to run /etc/expandcard.sh on first boot and check if swap is activated.
Then reboot.

=== Gnome-tracker in $HOME ===

By default trackers are indexing the entire $HOME folder, causing severe slowdown.

To avoid this issue, the solution (until a proper fix) is to add a <code>.nomedia</code> file in /home/user folder:

<pre>
touch /home/user/.nomedia
</pre>

=== Removing 250MHz CPU frequency (example) ===

Install <code>cpufrequtils</code>.

Replace 250000 by 500000 in <pre>/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq</pre>

=== More SWAP / SWAP activation (testing purpose) ===

('''Note: SWAP is already activated by default and use a swap file on SD card''')

Create a simple 1GB swap file on the SDcard if swap is missing:

<pre>sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576</pre>

(It takes some time...)

<pre>
sudo chmod 600 /
sudo mkswap /swapfile
sudo swapon /swapfile
</pre>

To make the change permanent open <code>/etc/fstab</code>:

<pre>
sudo nano /etc/fstab
</pre>

And add this line:

<pre>
/swapfile swap swap defaults 0 0
</pre>

To check if the swap is active:

<pre>
sudo swapon --show
</pre>

=== Tweaking Transitions (already optimized by default now) ===

Many options are missing in CSSU Features package but it is possible to edit them in transitions.ini.

As root

<pre>
nano /usr/share/hildon-desktop/transitions.ini
</pre>

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate/modify it through the transitions.ini file:

<pre>
[HOME]

radius = 1

radius_more = 2
</pre>

=== Video playing ===

Video playing is working fine using SMPLAYER:

- In Options / Preferences / General:

Media engine: Other: /user/bin/mplayer

- In Options / Preferences / Video:

Output driver: xv (0 - OMAP Textured Video)

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse (or User defined)

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: Auto

- In Options / Preferences / Performance:

Unable Allow frame drop

Hardware decoding: None

Prefer 360p - 480p max video format

(With overclocking, Video is working well using KODI 17.6 with equivalent A/V settings)

=== Voice Calls / SIP Calls ===

Now SIP calls and SIP messages are working out of the box using Twinkle.

Voice calls are now working out of the box as well.

If sound is distorted with Pulseaudio, run:

<pre>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</pre>

'''Note: Leste uses Pipewire by default now.'''

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.18 LTS || Mainline + PowerVR Patches: https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || Requires special hardware
|-
| Charging || Yes ||
|-
| Wireless || Yes || Firmware is non-free
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible
|-
| Keyboard || Yes ||
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || closed PowerVR driver
|-
| Overclock || Yes || up to 805MHz (stable & supported), 850MHz works with some devices (not supported), Turbo mode works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection and FMTX
|-
| Video || Yes || Xv acceleration, up to 360-480p. Max 360p for online streaming with SMplayer.
|-
| 2G/3G/3.5G data || Yes || Works with ofono - UI is working, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with Sphone or ofono scripts. Works with Conversations in -devel.
|-
| Phone calls || Yes || UCM support, sound is good. Works in 2G, 3G and 3.5G mode, works with Sphone
|-
| SIP calls / IM || Yes || Works with Twinkle, TLS transport is supported, Telepathy/Sphone integration is WIP
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Select 'FM Transmitter' in Pavucontrol
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>
|-
| FM Receiver || No || Depends on working Bluetooth stack
|-
| Accelerometer || Yes || Not used in Leste at the moment, since UI rotation does not work on N900
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || <code>evdev</code> 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'
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || No hardware
|-
| 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>
|-
| GPS || Yes ||
|-
| Infrared || Yes || TX only (hardware limitation). Works with pwm-ir-tx driver (patched)
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2026-09-27T07:20:18Z

Arno11-n900: /* More SWAP / SWAP activation (testing purpose) */

{{Infobox Device
|image=[[File:Nokia N900 - Leste pre-alpha.jpg|250px]]
|manufacturer=Nokia
|codename=Rover, RX-51
|dimensions=110.9mm x 59.8mm x 18mm
|release_date=2009-11-11
|category=Supported
|soc=TI OMAP 3430 @600MHz overclock @805MHz Cortex-A8 Armv7‑A
|dram=256 MB Mobile DDR
|power=
|lcd=800x480 3.5" Resistive TFT
|video=PowerVR SGX530
|audio=
|network=WL1251
|storage=32GB
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=6.18
|sw_serial=Yes, UART under battery, 2.7V max!
|sw_charging=Yes
|sw_usb_slave=Gadgets only
|sw_usb_host=With hacks
|sw_touchscreen=Yes, single-touch
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=
|sw_tv=Yes
|sw_3daccel=Yes, closed driver
|sw_vibration=Yes
|sw_audio=Yes (complex, ucm, no speaker protection)
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=Yes, actually CIR, not IrDA
|sw_2g3gdata=Yes
|sw_4gdata=
|sw_bluetooth=No
|sw_fmtx=Yes
|sw_fmrx=No
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=
|sw_backcam=
|sw_idlepower=160mW (WIP)
|sw_standbytime=
}}

== Installation ==

The installation consists of two steps: copying the image to the microsd card, and setting up the bootloader on the phone.

=== Image installation ===

* Images built automatically can be obtained at the download page: https://maedevu.maemo.org/images/n900/
* If you want to build a current image yourself use debos: https://git.maemo.org/leste-cicd/debos-leste but beware that downloadable images are genereally more stable than the most recent development build.

dd the image to an sd card.

If using a Windows machine, you can use [https://etcher.io/ Etcher]

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)

=== Bootloader (U-Boot) setup ===

==== Quick ====

If you don't want to configure u-boot from Fremantle, or your Fremantle rootfs is broken), or you just want to install quickly (dual boot mode):

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/ on *nix systems make sure to $ chmod a+x 0xFFFF

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/ save it in a subfolder called test.

3. Turn off Nokia N900, issue the following command on PC <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code> you will get a message similar to the following:

<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
</pre>

and the connect Nokia N900 to the PC. you will then get a message like so:

<pre>
Found USB device: RX-51/RM-680/RM-696 (0x421:0x106) in Cold flashing mode
USB device product string: Nokia USB ROM
USB device serial number string: (not detected)
Detected USB device: (not detected)
Waiting for ASIC ID...
Detected OMAP3430 chip (revision 87)
Device: (not detected)
HW revision: (not detected)
NOLO version: (not detected)
Kernel version: (not detected)
Initfs version: (not detected)
Software release version: (not detected)
Content eMMC version: (not detected)
Root device: (not detected)
USB host mode: (not detected)
R&D mode: (not detected)
Switching to NOLO mode...
Sending OMAP memory boot message...
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Load image:
File: test/u-boot-2013.04-2.bin
Image type: kernel
Image size: 212864 bytes
Sending image header...
Sending image...
100% [#################################################################]
Done
</pre>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code> you will get an output such as:
<pre>
0xFFFF v0.8 // Open Free Fiasco Firmware Flasher
Not a local device
Waiting for USB device...
Found USB device: SU-18/RX-34/RX-44/RX-48/RX-51/RM-680/RM-696 (0x421:0x105) in NOLO mode
USB device product string: Nokia N900 (Update mode)
USB device serial number string: MUN233033
Detected USB device: RX-51
Initializing NOLO...
Device: RX-51
HW revision: 2204
NOLO version: 1.4.14
Kernel version: 2.6.28-20101501+0m5
Initfs version: (not detected)
Software release version: RX-51_2009SE_21.2011.38-1.203.1_PR_203
Content eMMC version: RX-51_2009SE_10.2010.13-2.UK-IRELAND
Root device: flash
USB host mode: disabled
R&D mode: disabled
Booting kernel with default cmdline...
</pre>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. The screen might not be backlit so it will be difficult to read. 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>. The screen might be very dim and look off. So it might be difficult to see. Boot up the first time will take a long time full 2 min on test. Some text will show and will then go back to black screen but eventually you will see the splash screen and later the icons will show.

To flash u-boot permanently, you can issue the following command:

'''(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)''')

<pre>
sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f
</pre>

==== Existing Fremantle ====

If you have a functional Fremantle installation and you want to keep it, you can follow these steps instead:

1. Install <code>u-boot-flasher</code> (U-Boot with kernel 2.6.28-omap1). This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

2. Check with <code>uname -a</code> to be sure what kernel you are running. If you were running a power kernel, install "Linux kernel for power user (boot image for U-Boot)". This is important, to ensure that the correct kernel is booted, otherwise modules will not match and boot will fail.

3. Add Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

4. Reboot the device with the keyboard slide open (U-boot will boot the default option if the keyboard slide is closed)

=== Increase filesystem size ===

Run the following script: <code>/etc/expandcard.sh</code>

== Serial ==

http://n900.elektranox.org/serial-adapter.html

http://wiki.maemo.org/N900_Hardware_Hacking#Debug_ports

Use this command line (specifically the part after <code>rootwait</code>):

<pre>
root=/dev/mmcblk0p2 rootwait console=ttyS2,115200 verbose earlyprintk debug
</pre>

== Notes ==
=== Speakers ===

* 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.
=== Torch ===

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.

In the meantime, the LEDs can be used as a torch manually using <code>i2cset</code>.
However, '''BE WARNED:''' setting wrong values via i2c runs the risk of over-driving the LEDs and causing permanent hardware damage.

<source lang="shell-session">
# Install the prerequisites
$ sudo apk add i2c-tools

# Unload the driver in case it is already loaded. We will use i2c manually
$ sudo modprobe -r adp1653

# Enable the chip
$ echo 88 | sudo tee /sys/class/gpio/export
$ echo "out" | sudo tee /sys/class/gpio/gpio88/direction
$ echo 1 | sudo tee /sys/class/gpio/gpio88/value

# Turn the torch on, using the lowest torch current - DO NOT use other values here or you risk burning the LED
# Values between 1 and 7 enable the red privacy/recording led, with different intensity
# 0x8 is the lowest torch intensity, and we do not recommend going above it
$ sudo i2cset -y 2 0x30 0x0 0x8

# Turn the torch off
$ sudo i2cset -y 2 0x30 0x0 0x0

# Disable the chip
$ echo 0 | sudo tee /sys/class/gpio/gpio88/value
$ echo 88 | sudo tee /sys/class/gpio/unexport
</source>

== Power Management ==

This ticket tracks hitting idle states for the N900: https://github.com/maemo-leste/bugtracker/issues/545

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

* https://wiki.maemo.org/N900_Hardware_Power_management
* https://wiki.maemo.org/N900_Hardware_Power_Consumption

Run:
<pre>
modprobe ledtrig-default-on
</pre>

And:
<pre>
echo default-on > /sys/class/leds/debug::sleep/trigger
</pre>

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.

Currently it does not yet reliably reach any sleep modes.

See this code for a work in progress power management script: https://github.com/maemo-leste/n900-pm

== Battery calibration ==

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.

Here are described the steps necessary to calibrate your battery. This should help if you see "Battery not calibrated" message in the status applet.

* Fully charge the Nokia N900
* 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 process from the beginning (fully charge the device again).
* 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.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* 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.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

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.

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.
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.

== Accessing MTD ==

List devices:
cat /proc/mtd

Mount:
apt install mtd-utils
mkdir -vp /mnt/fremantle
ubiattach -p /dev/mtd5
mount -t ubifs ubi:rootfs /mnt/fremantle

== Overclocking (optional) ==

'''Overclocking is now available in -devel using cpufreq boost.'''

It uses 250-500-550-600-720-805MHz frequencies

To enable it, edit:

<code>/sys/devices/system/cpu/cpufreq/boost</code>

And replace 0 by 1.

It is possible to customise max/min/available frequencies editing files in:

<code>/sys/devices/system/cpu/cpu0/cpufreq/</code>

'''No other steps are needed and updates/upgrades work with boost mode.'''

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

As root
<code>cpufreq-set -c 0 -g conservative</code>

'''WARNING: some devices can't run at 805MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 805000 by 720000 in scaling_max_freq file and finally select conservative governor'''

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

1) From Fremantle: add new Maemo Leste menu item (run as root):
<pre>
cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << __EOF__
ITEM_NAME="Maemo Leste"
ITEM_KERNEL="uImage"
ITEM_DEVICE="\${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
__EOF__
</pre>

(press enter at the end if necessary)

And then run:

<pre>
u-boot-update-bootmenu
</pre>

2) From Maemo Leste (run as root):

<pre>
cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user
dtc -I dtb -O dts /home/user/omap3-n900.dtb -o /home/user/omap3-n900.dts
</pre>

Edit:

<pre>
/home/user/omap3-n900.dts
</pre>

(Now it's time to modify frequencies and voltage: be careful to do exactly the same)

Replace all content in "opp-table { opp1 opp2 opp3 opp4 opp5 opp6 };"

New opp-table for example:

<pre>
opp-table {
compatible = "operating-points-v2-ti-cpu";
syscon = < 0x05 >;
phandle = < 0x03 >;

opp1-250000000 {
opp-hz = < 0x00 0xee6b280 >;
opp-microvolt = < 0xee098 0xee098 0xee098 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp2-500000000 {
opp-hz = < 0x00 0x1dcd6500 >;
opp-microvolt = < 0x106738 0x106738 0x106738 >;
opp-supported-hw = < 0xffffffff 0x03 >;
opp-suspend;
};

opp3-600000000 {
opp-hz = < 0x00 0x23c34600 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp4-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x124f80 0x124f80 0x124f80 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};

opp5-850000000 {
opp-hz = < 0x00 0x32a9f880 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x03 >;
};
};
</pre>

And still as root:

<pre>
rm /home/user/omap3-n900.dtb
dtc -I dts -O dtb /home/user/omap3-n900.dts -o /home/user/omap3-n900.dtb
</pre>

Check your kernel version:

<code>uname -r</code>

For example if the result is 6.1.30, your vmlinuz version is vmlinuz-6.1.30

In the next command, replace "vmlinuz-<version>" by yours (i.e vmlinuz-6.1.30)

As root:

<pre>
cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb
mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX
</pre>

Now reboot and select 'Maemo Leste Overclock' in bootmenu.

('''WARNING with old method:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))

== Tips / Tweaks ==

=== SD Card and first boot===

To avoid overall slowness, SDXC U3 microSD card is a must. Class10 U1 cards are usually too slow to run Leste on N900 unfortunately.

'''WARNING''': unresponsive / freezing screen is normal during Hildon-desktop loading.

'''WARNING''': do not use zram and/or zswap.

First boot is a bit complicated because Leste is loading lot of things even if hildon-desktop is already visible (wait at least 3 min before clicking somewhere).
Connecting to Wi-Fi must be avoided until the second boot (otherwise apt-worker starts automatically and N900 is unresponsive for few minutes).
Don't forget to run /etc/expandcard.sh on first boot and check if swap is activated.
Then reboot.

=== Gnome-tracker in $HOME ===

By default trackers are indexing the entire $HOME folder, causing severe slowdown.

To avoid this issue, the solution (until a proper fix) is to add a <code>.nomedia</code> file in /home/user folder:

<pre>
touch /home/user/.nomedia
</pre>

=== Removing 250MHz CPU frequency (example) ===

Install <code>cpufrequtils</code>.

Replace 250000 by 500000 in <pre>/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq</pre>

=== More SWAP / SWAP activation (testing purpose) ===

('''Note: SWAP is already activated by default and use a swap file on SD card''')

Create a simple 1GB swap file on the SDcard if swap is missing:

<pre>sudo dd if=/dev/zero of=/swapfile bs=1024 count=1048576</pre>

(It takes some time...)

<pre>
sudo chmod 600 /
sudo mkswap /swapfile
sudo swapon /swapfile
</pre>

To make the change permanent open <code>/etc/fstab</code>:

<pre>
sudo nano /etc/fstab
</pre>

And add this line:

<pre>
/swapfile swap swap defaults 0 0
</pre>

To check if the swap is active:

<pre>
sudo swapon --show
</pre>

=== Tweaking Transitions (already optimized by default now) ===

Many options are missing in CSSU Features package but it is possible to edit them in transitions.ini.

As root

<pre>
nano /usr/share/hildon-desktop/transitions.ini
</pre>

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate/modify it through the transitions.ini file:

<pre>
[HOME]

radius = 1

radius_more = 2
</pre>

=== Video playing ===

Video playing is working fine using SMPLAYER:

- In Options / Preferences / General:

Media engine: Other: /user/bin/mplayer

- In Options / Preferences / Video:

Output driver: xv (0 - OMAP Textured Video)

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse (or User defined)

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: Auto

- In Options / Preferences / Performance:

Unable Allow frame drop

Hardware decoding: None

Prefer 360p - 480p max video format

(With overclocking, Video is working well using KODI 17.6 with equivalent A/V settings)

=== Voice Calls / SIP Calls ===

Now SIP calls and SIP messages are working out of the box using Twinkle.

Voice calls are now working out of the box as well.

If sound is distorted, run:

<pre>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</pre>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.18 LTS || Mainline + PowerVR Patches: https://github.com/maemo-leste/droid4-linux
|-
| Serial || Yes || Requires special hardware
|-
| Charging || Yes ||
|-
| Wireless || Yes || Firmware is non-free
|-
| Ethernet || N/A ||
|-
| Micro USB || Yes || USB Network, Mass Storage. OTG not working, although it might be possible
|-
| Keyboard || Yes ||
|-
| Screen || Yes ||
|-
| 3D Acceleration || Yes || closed PowerVR driver
|-
| Overclock || Yes || up to 805MHz (stable & supported), 850MHz works with some devices (not supported), Turbo mode works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection and FMTX
|-
| Video || Yes || Xv acceleration, up to 360-480p. Max 360p for online streaming with SMplayer.
|-
| 2G/3G/3.5G data || Yes || Works with ofono - UI is working, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with Sphone or ofono scripts. Works with Conversations in -devel.
|-
| Phone calls || Yes || UCM support, sound is good. Works in 2G, 3G and 3.5G mode, works with Sphone
|-
| SIP calls / IM || Yes || Works with Twinkle, TLS transport is supported, Telepathy/Sphone integration is WIP
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Select 'FM Transmitter' in Pavucontrol
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>
|-
| FM Receiver || No || Depends on working Bluetooth stack
|-
| Accelerometer || Yes || Not used in Leste at the moment, since UI rotation does not work on N900
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || <code>evdev</code> 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'
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || No hardware
|-
| 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>
|-
| GPS || Yes ||
|-
| Infrared || Yes || TX only (hardware limitation). Works with pwm-ir-tx driver (patched)
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Motorola Droid 3

2026-09-27T06:54:28Z

Arno11-n900: /* Conversations */

{{Infobox Device
|image=
[[File:Motorola Droid 3 Leste Chimera.jpg|thumb]]
|manufacturer=Motorola
|codename=Solana XT862 / XT860
|dimensions=todo
|release_date=todo
|soc=TI OMAP4430
|dram=512MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=todo
|other=
|category=Supported
|sw_kernel=6.1.9
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=No
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=No (needs modem work)
|sw_sms=No (needs modem work)
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=
|sw_4g=No
|sw_bluetooth=todo
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=No (needs modem work)
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=
|sw_standbytime=
}}

'''This device is called "Motorola Milestone 3" outside of the US.'''

== Installation ==

Hardware requirements:

* Droid 3 with fully charged battery
* MicroUSB cable
* MicroSD card

Software requirements:
* Host Linux system
* Android Tools: fastboot adb

Download latest Chimera release from https://maedevu.maemo.org/images/droid3/

# Latest maemo-leste-1.0-armhf-droid3-20240908.img.xz

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

# droid4-kexecboot.img

Download or clone https://github.com/MerlijnWajer/bionic-clown-boot/tree/solana (solana branch!)

Follow the instructions in bionic-clown-boot's readme to install kexecboot on your device.

Now, flash the Maemo Leste image to your sdcard.

== Notes ==

IMPORTANT: Set the USB mode to "PC mode" instead of "mass storage mode" on your device before running install.sh
on bionic-clown-boot

Device is still heavy work in the progress. The following is known not to work:

* Brightness control (screen is always max brightness) You can scale the brightness using xrandr:
<pre>
xrandr --output DSI-1 --brightness 0.5
</pre>
* Keyboard backlight
* Modem interrupts, it is visible on USB but other communication with it doesn't work
* pstore (needs figuring out what the reserved memory is on Android)
* See if we can use 512MB ram instead of 509MB (see dts)
* <s>3d shows some frame lag / misdrawing, so probably powervr clock needs adjusting</s> (seems solved on kernel 5.15)
* <s>touchscreen buttons do not work yet</s> (fixed on 5.15)
* keyboard layout in Leste is not faithful to the icons on the keyboard, but rather mostly mimic droid 4

Additionally, the device suffers from random hangs while in use, causing resets. When pstore works, we can hopefully figure this out. <s>(Haven't seen them on 5.15)</s> (Came back on kernel 6.x) It might be a power-management-related issue, or a GPU issue (last log line shows something about OMAP complaining about DRM), or something else. The emergency shell works just fine with no hangs at all.

There is a workaround to the random hangs that work for some in 6.1. Here is how to work around this.

Download the latest Chimaera release: maemo-leste-1.0-armhf-droid3-20250608.img.xz and follow the same installation instructions provided above.

*From the kexecboot menu, select the "emergency shell" startup.
*Bypass the login prompt, ALT-D, the kernel will continue to boot into the Hildon window manager.
*Immediately try and configure your wifi settings, the device might hang and reboot. Reset the battery and try again until you get it configured.
*Once wifi is configured, let the device sleep, having the screen off reduces the chances of it freezing up again.
*ssh/scp in to the D3 from another device.
*Replace the script in the /etc/init.d/powervr with this:
<pre>
#!/sbin/openrc-run

depend() {
after eudev kmod
before xorg xsession hildon-desktop
}

start() {
ebegin "Starting PowerVR"

modprobe pvrsrvkm_omap4_sgx540_120 || true

for i in 1 2 3 4 5; do
[ -e /sys/bus/platform/devices/56000000.gpu/power/control ] && break
sleep 1
done

#echo 0xffffffff > /sys/module/pvrsrvkm_omap4_sgx540_120/parameters/gPVRDebugLevel 2>/dev/null || true
echo on > /sys/bus/platform/devices/56000000.gpu/power/control 2>/dev/null || true

/usr/bin/pvrsrvinit || true

eend 0
}

stop() {
ebegin "Stopping PowerVR"
eend 0
}
</pre>

*Reboot always using the "emergency shell" startup. Use xrandr to reduce the screen brightness. Chimaera should run without random hangs.

Also, the device often comes network locked. [[User:Wizzup]] has access to Sigmakey software and can help remotely remove the network lock.

If you run the battery dead, you cannot recharge using the MicroUSB cable. It is recommended to purchase a wall-wort to externally charge the battery.

If you have got the device stuck, you should hold the power button for about 7 seconds. Droid3 will display a white LED letting you know that it is shutting down. Once the LED shuts off, power on the device at any time. If this doesn't work, remove the battery and reset it.

== Conversations ==

*You can join IRC channels in conversations.
*You can create contacts in osso-addressbook to send messages or make calls.
*XMPP works.

== Music ==

*Lollypop works very well for the droid3. The controls are a bit small but are manageable.
*CMUS works, but chews up a lot of battery. It uses some remote M3 CPUs which are not available to normal Linux.

== Gallery ==
<gallery>
neofetch.png
Terminal.JPG
Htop.png
Main.png
Status.png
Lollypop.png
3600bat.JPG
irssi.JPG
</gallery>
[[Category:Device]]

Motorola Droid 4

2026-09-27T06:48:16Z

Arno11-n900:

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, TMP105 temperature, ISL29030 proximity and illuminance
|other=
|category=Supported
|sw_kernel=6.18 LTS
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
# NOTE: be sure there's only one file matching maemo-leste-5.0-armhf-droid4-*.img.xz before running this command
xzcat maemo-leste-5.0-armhf-droid4-*.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

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]):
udevadm hwdb --update
udevadm trigger

This should survive a reboot.

== Serial Cable ==

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

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

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

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded. So you should do:

<pre>
sudo apt install firmware-ti-connectivity
sudo modprobe hci_uart
sudo hciconfig hci0 up
sudo hcitool lescan
</pre>

== Stuff to try ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

<pre>
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
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
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
</pre>

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

==== USSD ====

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

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

If one wants to mirror the screen on HDMI, this can be done like so, for landscape:

<pre>
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1
</pre>

For rotation, something like this might or might not work:

<pre>
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00ROT"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right
</pre>

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

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

==== Torch ====

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.

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):

<source>
##Install the prerequisites
$ sudo apt install i2c-tools

## Turn LED on in torch mode
$ sudo i2cset -y 2 0x53 0x10 0x1a

## Turn LED on in privacy indication mode
$ sudo i2cset -y 2 0x53 0x10 0x19

## Turn LED off (in any mode)
$ sudo i2cset -y 2 0x53 0x10 0x18

## Use LED for doing a hella bright flash for some time once and then turn off
$ sudo i2cset -y 2 0x53 0x10 0x1b

</source>

== Using a configured Leste sdcard in a different Droid4 ==

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.

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.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

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

== Status overview ==

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

[[Category:Device]]

Google Pixel 3a

2026-09-27T06:46:00Z

Arno11-n900:

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, capacitive
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes
|sw_backcam=Yes
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Template:Infobox Device

2026-09-27T06:21:20Z

Arno11-n900:

{{Infobox
| abovestyle = background: #dedede;
| headerstyle = background: #dedede;

| above = {{{name|<includeonly>{{PAGENAME}}</includeonly>}}}

| image = {{{image|}}}
| caption = {{{caption|}}}
| header2 =
| label2 = Manufacturer
| data2 = {{{manufacturer|}}}
| header3 =
| label3 = Codename
| data3 = {{{codename|}}}
| header4 =
| label4 = Dimensions
| data4 = {{{dimensions|}}}
| header5 =
| label5 = Release Date
| data5 = {{{release_date|}}}
| header6 =
| label6 = Website
| data6 = {{{website|}}}
| header7 =
| label7 = Category
| data7 = {{{category|}}}

| header8 = Specifications
| label8 =
| data8 =
| header9 =
| label9 = SoC
| data9 = {{{soc|}}}
| header10 =
| label10 = DRAM
| data10 = {{{dram|}}}
| header11 =
| label11 = NAND
| data11 = {{{nand|}}}
| header12 =
| label12 = Power
| data12 = {{{power|}}}

| header13 = Hardware Features
| label13 =
| data13 =
| header14 =
| label14 = Display
| data14 = {{{display|}}}
| header15 =
| label15 = Input
| data15 = {{{input|}}}
| header16 =
| label16 = Video
| data16 = {{{video|}}}
| header17 =
| label17 = Audio
| data17 = {{{audio|}}}
| header18 =
| label18 = Network
| data18 = {{{network|}}}
| header19 =
| label19 = Storage
| data19 = {{{storage|}}}
| header20 =
| label20 = USB
| data20 = {{{usb|}}}
| header21 =
| label21 = Camera
| data21 = {{{camera|}}}
| header22 =
| label22 = Sensors
| data22 = {{{sensors|}}}
| header23 =
| label23 = External Headers
| data23 = {{{headers|}}}
| header24 =
| label24 = Battery Capacity
| data24 = {{{battery|}}}

| header25 = Software Features
| label25 =
| data25 =
| header26 =
| label26 = Kernel
| data26 = {{{sw_kernel|}}}
| header27 =
| label27 = Serial
| data27 = {{{sw_serial|}}}
| header28 =
| label28 = Charging
| data28 = {{{sw_charging|}}}
| header29 =
| label29 = USB Slave
| data29 = {{{sw_usb_slave|}}}
| header30 =
| label30 = USB Host
| data30 = {{{sw_usb_host|}}}
| header31 =
| label31 = Touchscreen
| data31 = {{{sw_touchscreen|}}}
| header32 =
| label32 = Keyboard
| data32 = {{{sw_keyboard|}}}
| header33 =
| label33 = Screen
| data33 = {{{sw_screen|}}}
| header34 =
| label34 = HDMI-out
| data34 = {{{sw_hdmi|}}}
| header35 =
| label35 = TV-out
| data35 = {{{sw_tv|}}}
| header36 =
| label36 = 3D acceleration
| data36 = {{{sw_3daccel|}}}
| header37 =
| label37 = Vibration motor
| data37 = {{{sw_vibration|}}}
| header38 =
| label38 = Audio
| data38 = {{{sw_audio|}}}
| header39 =
| label39 = Phone calls
| data39 = {{{sw_calls|}}}
| header40 =
| label40 = SMS
| data40 = {{{sw_sms|}}}
| header41 =
| label41 = Wifi
| data41 = {{{sw_wifi|}}}
| header42 =
| label42 = Ethernet
| data42 = {{{sw_ethernet|}}}
| header43 =
| label43 = IrDA
| data43 = {{{sw_irda|}}}
| header44 =
| label44 = 2G/3G data
| data44 = {{{sw_2g3gdata|}}}
| header45 =
| label45 = 4G data
| data45 = {{{sw_4gdata|}}}
| header46 =
| label46 = Bluetooth
| data46 = {{{sw_bluetooth|}}}
| header47 =
| label47 = FM transmitter
| data47 = {{{sw_fmtx|}}}
| header48 =
| label48 = FM receiver
| data48 = {{{sw_fmrx|}}}
| header49 =
| label49 = NFC
| data49 = {{{sw_nfc|}}}
| header50 =
| label50 = Accelerometer
| data50 = {{{sw_accelerometer|}}}
| header51 =
| label51 = Compass
| data51 = {{{sw_compass|}}}
| header52 =
| label52 = Gryo
| data52 = {{{sw_gyro|}}}
| header53 =
| label53 = Proximity Sensor
| data53 = {{{sw_proximity|}}}
| header54 =
| label54 = Ambient Light Sensor
| data54 = {{{sw_als|}}}
| header55 =
| label55 = GPS
| data55 = {{{sw_gps|}}}
| header56 =
| label56 = A-GPS
| data56 = {{{sw_agps|}}}
| header57 =
| label57 = Front Camera
| data57 = {{{sw_frontcam|}}}
| header58 =
| label58 = Back Camera(s)
| data58 = {{{sw_backcam|}}}
| header59 =
| label59 = Idle Power Consumption
| data59 = {{{sw_idlepower|}}}
| header60 =
| label60 = Stand by time
| data60 = {{{sw_standbytime|}}}
}}

[[Category:Devices]]

Google Pixel 3a

2026-09-27T06:17:34Z

Arno11-n900:

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|display=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, multitouch
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes, qcam only
|sw_backcam=Yes, qcam only
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Template:Infobox Device

2026-09-27T06:16:16Z

Arno11-n900:

{{Infobox
| abovestyle = background: #dedede;
| headerstyle = background: #dedede;

| above = {{{name|<includeonly>{{PAGENAME}}</includeonly>}}}

| image = {{{image|}}}
| caption = {{{caption|}}}
| header2 =
| label2 = Manufacturer
| data2 = {{{manufacturer|}}}
| header3 =
| label3 = Codename
| data3 = {{{codename|}}}
| header4 =
| label4 = Dimensions
| data4 = {{{dimensions|}}}
| header5 =
| label5 = Release Date
| data5 = {{{release_date|}}}
| header6 =
| label6 = Website
| data6 = {{{website|}}}
| header7 =
| label7 = Category
| data7 = {{{category|}}}

| header8 = Specifications
| label8 =
| data8 =
| header9 =
| label9 = SoC
| data9 = {{{soc|}}}
| header10 =
| label10 = DRAM
| data10 = {{{dram|}}}
| header11 =
| label11 = NAND
| data11 = {{{nand|}}}
| header12 =
| label12 = Power
| data12 = {{{power|}}}

| header13 = Hardware Features
| label13 =
| data13 =
| header14 =
| label14 = Display
| data14 = {{{display|}}}
| header15 =
| label15 = Input
| data15 = {{{input|}}}
| header16 =
| label16 = Video
| data16 = {{{video|}}}
| header17 =
| label17 = Audio
| data17 = {{{audio|}}}
| header18 =
| label18 = Network
| data18 = {{{network|}}}
| header19 =
| label19 = Storage
| data19 = {{{storage|}}}
| header20 =
| label20 = USB (Host/OTG)
| data20 = {{{usb|}}}
| header21 =
| label21 = Camera
| data21 = {{{camera|}}}
| header22 =
| label22 = Sensors
| data22 = {{{sensors|}}}
| header23 =
| label23 = External Headers
| data23 = {{{headers|}}}
| header24 =
| label24 = Battery Capacity
| data24 = {{{battery|}}}

| header25 = Software Features
| label25 =
| data25 =
| header26 =
| label26 = Kernel
| data26 = {{{sw_kernel|}}}
| header27 =
| label27 = Serial
| data27 = {{{sw_serial|}}}
| header28 =
| label28 = Charging
| data28 = {{{sw_charging|}}}
| header29 =
| label29 = USB Slave
| data29 = {{{sw_usb_slave|}}}
| header30 =
| label30 = USB Host
| data30 = {{{sw_usb_host|}}}
| header31 =
| label31 = Touchscreen
| data31 = {{{sw_touchscreen|}}}
| header32 =
| label32 = Keyboard
| data32 = {{{sw_keyboard|}}}
| header33 =
| label33 = Screen
| data33 = {{{sw_screen|}}}
| header34 =
| label34 = HDMI-out
| data34 = {{{sw_hdmi|}}}
| header35 =
| label35 = TV-out
| data35 = {{{sw_tv|}}}
| header36 =
| label36 = 3D acceleration
| data36 = {{{sw_3daccel|}}}
| header37 =
| label37 = Vibration motor
| data37 = {{{sw_vibration|}}}
| header38 =
| label38 = Audio
| data38 = {{{sw_audio|}}}
| header39 =
| label39 = Phone calls
| data39 = {{{sw_calls|}}}
| header40 =
| label40 = SMS
| data40 = {{{sw_sms|}}}
| header41 =
| label41 = Wifi
| data41 = {{{sw_wifi|}}}
| header42 =
| label42 = Ethernet
| data42 = {{{sw_ethernet|}}}
| header43 =
| label43 = IrDA
| data43 = {{{sw_irda|}}}
| header44 =
| label44 = 2G/3G data
| data44 = {{{sw_2g3gdata|}}}
| header45 =
| label45 = 4G data
| data45 = {{{sw_4gdata|}}}
| header46 =
| label46 = Bluetooth
| data46 = {{{sw_bluetooth|}}}
| header47 =
| label47 = FM transmitter
| data47 = {{{sw_fmtx|}}}
| header48 =
| label48 = FM receiver
| data48 = {{{sw_fmrx|}}}
| header49 =
| label49 = NFC
| data49 = {{{sw_nfc|}}}
| header50 =
| label50 = Accelerometer
| data50 = {{{sw_accelerometer|}}}
| header51 =
| label51 = Compass
| data51 = {{{sw_compass|}}}
| header52 =
| label52 = Gryo
| data52 = {{{sw_gyro|}}}
| header53 =
| label53 = Proximity Sensor
| data53 = {{{sw_proximity|}}}
| header54 =
| label54 = Ambient Light Sensor
| data54 = {{{sw_als|}}}
| header55 =
| label55 = GPS
| data55 = {{{sw_gps|}}}
| header56 =
| label56 = A-GPS
| data56 = {{{sw_agps|}}}
| header57 =
| label57 = Front Camera
| data57 = {{{sw_frontcam|}}}
| header58 =
| label58 = Back Camera(s)
| data58 = {{{sw_backcam|}}}
| header59 =
| label59 = Idle Power Consumption
| data59 = {{{sw_idlepower|}}}
| header60 =
| label60 = Stand by time
| data60 = {{{sw_standbytime|}}}
}}

[[Category:Devices]]

Google Pixel 3a

2026-09-23T20:01:33Z

Arno11-n900: /* GPS with ModemManager and Geoclue (testing, not implemented, WIP) */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|lcd=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, multitouch
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes, qcam only
|sw_backcam=Yes, qcam only
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

<pre>
sudo apt install geoclue-2-demo
</pre>

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, '''where-am-i''' should show network coordinates and GPS coordinates a bit later.

Once network or GPS coordinates appear in '''where-am-i''', Firefox is able to report coordinates in location websites like Google Maps.

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-09-23T19:54:10Z

Arno11-n900: /* Tweaks */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|lcd=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, multitouch
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes, qcam only
|sw_backcam=Yes, qcam only
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

=== GPS with ModemManager and Geoclue (testing, not implemented, WIP) ===

To enable GPS:

<pre>
qmicli -d qrtr://0 --loc-set-engine-lock=mt
qmicli -d qrtr://0 --loc-set-nmea-types=all
mmcli -m any --location-enable-gps-nmea
</pre>

To disable GPS:

<pre>
mmcli -m any --location-disable-gps-nmea
qmicli -d qrtr://0 --loc-stop
</pre>

To start location:

<pre>
qmicli -d qrtr://0 --loc-start
</pre>

Then, in 2 different terminals:

<pre>
/usr/libexec/geoclue-2.0/demos/agent
</pre>

and

<pre>
/usr/libexec/geoclue-2.0/demos/where-am-i
</pre>

After a while, where-am-i should show network coordinates and gps coordinates a bit later.

Once network or gps coordinates appear in where-am-i, Firefox is able to report coordinates in location websites like Google Maps.

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-09-23T19:37:25Z

Arno11-n900: /* Tweaks */

{{Infobox Device
|image=[[File:300px-Google-sargo.png|300px]]
|manufacturer=Google
|codename=Pixel 3a/3a XL, Google sargo/bonito
|release_date=2019
|category=Supported
|dram=4GB
|soc=2 x 2 GHz, 6 x 1.7GHz
|lcd=1080x2220 OLED
|video= adreno 615
|audio=yes
|network=yes
|storage=64GB
|usb=Micro USB C
|camera=yes
|sensors=yes
|battery=3000/3700mAh
|sw_kernel=6.12
|sw_charging=Yes
|sw_touchscreen=Yes, multitouch
|sw_screen=Yes
|sw_3daccel=Yes
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_irda=No
|sw_2g3gdata=Yes, ModemManager only
|sw_4gdata=Yes, ModemManager only
|sw_bluetooth=Yes
|sw_fmtx=No
|sw_fmrx=No
|sw_accelerometer=Yes
|sw_proximity=Yes
|sw_gps=Yes, ModemManager only
|sw_agps=Yes, ModemManager only
|sw_frontcam=Yes, qcam only
|sw_backcam=Yes, qcam only
|sw_idlepower=280mW
|sw_standbytime=40/50h
}}

== Installation ==

WIP

'''WARNING: Flashing Maemo Leste to your device will erase your Android installation and all the data contained in it.'''

It is recommended to upgrade Android to the latest available version and install all system updates before installing Maemo-leste, because Maemo-leste uses FW files from Android partitions for enabling various peripherals, as mentioned in Mobian [https://wiki.debian.org/InstallingDebianOn/Google/Pixel3a wiki]

Install fastboot and last android-sdk-platform-tools on your computer.

=== Flash mode ===

WIP

To enter flash mode (fastboot):

Hold "Volume Down" and "Power" buttons until fastboot appears.

Then connect your PC and your phone through USB.

=== Bootloader setup ===

WIP

Device bootloader needs to be unlocked: from Android, go to "About phone" page in Settings app. Then, click 7 times on the build number to enable developer settings.
From Setting main page, go to "System", "Developer options" and enable OEM unlocking.

Before flashing Maemo Leste, you need to unlock the bootloader in fastboot mode with this command:

<pre>
fastboot flashing unlock
</pre>

=== Installation with fastboot ===

WIP

Fastboot (useful) commands:

<pre>
fastboot getvar current-slot
</pre>

<pre>
fastboot set_active a
</pre>

or

<pre>
fastboot set_active b
</pre>

Download necessary img's files [https://maedevu.maemo.org/images/pixel3a/20260906-excalibur/ here] '''(.tar.xz archive includes both sargo and bonito img's files)'''

From fastboot menu:

<pre>
fastboot flash boot <boot.img>

fastboot flash userdata <excalibur-sdm670.img>

fastboot oem uart enable

fastboot reboot
</pre>

'''Warning:''' TODO it is confusing how to use fastboot flash boot/boot_a/boot_b command. Needs clarifications.

'''Note:''' The bootloader on the Pixel 3a appends console=null to the kernel cmdline by default, which hides the boot logs on the screen. A custom manufacturer fastboot command can configure console=tty0: 'fastboot oem uart enable'

== Tweaks ==

WIP

=== First boot ===

=== Recommanded useful apps ===

coolkbd, brightness applet, orientation lock applet

=== Firefox(-esr) tips ===

To activate touchscreen scrolling:

Edit

<pre>
/usr/share/applications/hildon/firefox-esr.desktop
</pre>

modify "Exec" line

<pre>
Exec=bash -c 'MOZ_USE_XINPUT2=1 /usr/bin/firefox-esr'
</pre>

To modify scaling and fit to Pixel 3a screen in portrait mode, go to "about:config" and edit

<pre>
layout.css.devPixelsPerPx 0.8
</pre>

=== Mobile data (workaround) ===

Ofono doesn't handle qrtr properly unfortunately, however it is possible to run ModemManager just for mobile data, as a workaround.

(Note: network-manager package is needed)

See PMOS page [https://wiki.postmarketos.org/wiki/Modem#Mobile_Data Mobile data]

and [https://wiki.postmarketos.org/wiki/Modem#Getting_ModemManager_logs ModemManager init script]

That works fine even with ofono running at the same time.

=== Portrait VS Landscape ===

Almost all apps can run in portrait mode with hildon-desktop, however few apps like osso-addressbook or chromium need to be added by-hand in transitions.ini whitelist:

<pre>
/usr/share/hildon-desktop/transitions.ini
</pre>

Some apps can be also locked in landscape mode if needed (blacklist). It is particulary useful for video apps like smplayer.

Rotation is currently chaotic, it is recommanded to lock the device in portrait mode using Orientation Lock Applet and allow automatic landscape rotation for specific apps in transitions.ini file if needed (until a proper rotation fix).

=== Video recording (testing) ===

Both back and front cameras work (more or less) and it is already possible to record some videos using gst-launch and libcamera:

<pre>
sudo apt install libcamera-tools
sudo apt install gstreamer1.0-libcamera
sudo apt install gstreamer1.0-plugins-ugly
</pre>

First test to show video stream: (sudo needed ATM)

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! queue ! videoconvert ! autovideosink
</pre>

Then, to record a video: (sudo needed ATM)

'''(i2c-bus@0 for back and i2c-bus@1 for front camera)'''

<pre>
sudo gst-launch-1.0 -e libcamerasrc camera-name="/base/soc@0/cci@ac4a000/i2c-bus@1/camera@1a" ! video/x-raw,framerate=17/2 ! queue ! videoconvert ! x264enc tune=zerolatency bitrate=4000 speed-preset=ultrafast ! h264parse ! mp4mux ! filesink location=videotest.mp4
</pre>

That is only an example and a WIP. Lot of parameters need to be added or modified.

'''Note: libcamera-tools provides qcam which can be used to take some pictures. Colors are a bit wrong and rotation seems not calibrated properly.

== Remaining issues ==

Mobile data not working with ofono (qrtr implementation).

Rotation accuracy.

GPS with geoclue implementation for Maemo location apps.

Phone calls work nicely with ofono/sphone, however incoming calls work only if you make an outgoing call first (after boot).

Current draw is a bit high out of the box. fixed in newer kernel. (6.12 patched kernel is available however)

[[Category:Device]]

Google Pixel 3a

2026-09-20T10:11:52Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T10:06:11Z

Arno11-n900: /* Installation */

Google Pixel 3a

2026-09-20T10:05:39Z

Arno11-n900: /* Installation */

Google Pixel 3a

2026-09-20T07:52:52Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:51:41Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:44:48Z

Arno11-n900: /* Installation */

Google Pixel 3a

2026-09-20T07:44:20Z

Arno11-n900: /* Flash mode */

Google Pixel 3a

2026-09-20T07:40:21Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:34:09Z

Arno11-n900: /* Installation */

Google Pixel 3a

2026-09-20T07:21:59Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:17:02Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:16:02Z

Arno11-n900: /* Installation with fastboot */

Google Pixel 3a

2026-09-20T07:11:13Z

Arno11-n900: /* Installation with fastboot */

Motorola Droid 4

2026-09-19T21:33:21Z

Arno11-n900: /* Installation */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, TMP105 temperature, ISL29030 proximity and illuminance
|other=
|category=Supported
|sw_kernel=5.18.x
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
# NOTE: be sure there's only one file matching maemo-leste-5.0-armhf-droid4-*.img.xz before running this command
xzcat maemo-leste-5.0-armhf-droid4-*.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

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]):
udevadm hwdb --update
udevadm trigger

This should survive a reboot.

== Serial Cable ==

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

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

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

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded. So you should do:

<pre>
sudo apt install firmware-ti-connectivity
sudo modprobe hci_uart
sudo hciconfig hci0 up
sudo hcitool lescan
</pre>

== Stuff to try ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

<pre>
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
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
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
</pre>

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

==== USSD ====

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

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

If one wants to mirror the screen on HDMI, this can be done like so, for landscape:

<pre>
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1
</pre>

For rotation, something like this might or might not work:

<pre>
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00ROT"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right
</pre>

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

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

==== Torch ====

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.

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):

<source>
##Install the prerequisites
$ sudo apt install i2c-tools

## Turn LED on in torch mode
$ sudo i2cset -y 2 0x53 0x10 0x1a

## Turn LED on in privacy indication mode
$ sudo i2cset -y 2 0x53 0x10 0x19

## Turn LED off (in any mode)
$ sudo i2cset -y 2 0x53 0x10 0x18

## Use LED for doing a hella bright flash for some time once and then turn off
$ sudo i2cset -y 2 0x53 0x10 0x1b

</source>

== Using a configured Leste sdcard in a different Droid4 ==

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.

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.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

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

== Status overview ==

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

[[Category:Device]]

Motorola Droid 4

2026-09-19T21:21:08Z

Arno11-n900: /* Bluetooth */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, TMP105 temperature, ISL29030 proximity and illuminance
|other=
|category=Supported
|sw_kernel=5.18.x
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
# NOTE: be sure there's only one file matching maemo-leste-5.0-armhf-droid4-*.img.xz before running this command
xzcat maemo-leste-5.0-armhf-droid4-*.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

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]):
udevadm hwdb --update
udevadm trigger

This should survive a reboot.

== Serial Cable ==

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

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

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

== Bluetooth ==

Needs firmware - install latest firmware-ti-connectivity - See also https://git.maemo.org/leste/bugtracker/issues/290. Due to interference with WiFi, load driver manually, AFTER wifi module loaded. So you should do:

<pre>
sudo apt install firmware-ti-connectivity
sudo modprobe hci_uart
sudo hciconfig hci0 up
sudo hcitool lescan
</pre>

== Stuff to try ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

<pre>
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
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
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
</pre>

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

==== USSD ====

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

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

If one wants to mirror the screen on HDMI, this can be done like so, for landscape:

<pre>
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1
</pre>

For rotation, something like this might or might not work:

<pre>
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00ROT"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right
</pre>

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

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

==== Torch ====

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.

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):

<source>
##Install the prerequisites
$ sudo apt install i2c-tools

## Turn LED on in torch mode
$ sudo i2cset -y 2 0x53 0x10 0x1a

## Turn LED on in privacy indication mode
$ sudo i2cset -y 2 0x53 0x10 0x19

## Turn LED off (in any mode)
$ sudo i2cset -y 2 0x53 0x10 0x18

## Use LED for doing a hella bright flash for some time once and then turn off
$ sudo i2cset -y 2 0x53 0x10 0x1b

</source>

== Using a configured Leste sdcard in a different Droid4 ==

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.

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.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

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

== Status overview ==

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

[[Category:Device]]

Motorola Droid 4

2026-09-19T21:17:27Z

Arno11-n900: /* Updating */

{{Infobox Device
|image=[[File:Motorola Droid 4 - Leste pre-alpha.jpg|250px]]
|manufacturer=Motorola
|codename=Maserati XT894
|dimensions=127x67.3x12.7mm
|release_date=2012-02-10
|soc=TI OMAP4430 Cortex-A9 Armv7‑A
|dram=1024MB DDR2
|power=
|lcd=960x540 4"
|video=PowerVR SGX540
|audio=
|network=
|storage=16GB flash
|usb=
|camera=
|sensors=AK8975 compass, LIS3DH accelerometer, TMP105 temperature, ISL29030 proximity and illuminance
|other=
|category=Supported
|sw_kernel=5.18.x
|sw_serial=Yes, [[#Serial Cable|special cable]]
|sw_charging=Yes
|sw_usb_slave=Yes
|sw_usb_host=Yes
|sw_touchscreen=Yes
|sw_keyboard=Yes
|sw_screen=Yes
|sw_hdmi=Yes
|sw_tv=
|sw_3daccel=Yes [https://github.com/maemo-leste/pvr-omap4] (closed)
|sw_vibration=Yes
|sw_audio=Yes
|sw_calls=Yes
|sw_sms=Yes
|sw_wifi=Yes
|sw_ethernet=
|sw_irda=
|sw_2g3gdata=Yes
|sw_4g=No
|sw_bluetooth=Yes, [[#Bluetooth|see notes]]
|sw_fmtx=No, but apparently exists, needs serdev kernel modules/drivers
|sw_fmrx=
|sw_nfc=
|sw_accelerometer=Yes
|sw_compass=Yes, no integration
|sw_gyro=
|sw_proximity=Yes
|sw_als=Yes
|sw_gps=Yes
|sw_agps=No
|sw_frontcam=No
|sw_backcam=No
|sw_idlepower=120mW
|sw_standbytime=
}}

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

On Linux:
<pre>
# NOTE: be sure there's only one file matching maemo-leste-5.0-armhf-droid4-*.img.xz before running this command
xzcat maemo-leste-5.0-armhf-droid4-*.img.xz | sudo dd status=progress bs=1M of=/dev/MICROSDCARD-DEVICE
sync
</pre>

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

The keyboard layout is extended to provide more standard keys.
[[File:Maemo-leste-droid4-kbd-2021-07.png|center|620px|thumb|maemo-leste droid4 keyboard]]
Key mapping can be tested with the 'xev' program.

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]):
udevadm hwdb --update
udevadm trigger

This should survive a reboot.

== Serial Cable ==

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

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

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

== Bluetooth ==

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:

<pre>
sudo apt install firmware-ti-connectivity
sudo modprobe hci_uart
sudo hciconfig hci0 up
sudo hcitool lescan
</pre>

== Stuff to try ==

==== Using a battery without temperature sensor ====

Modprobe the pmic driver as follows:
<pre>
cpcap-battery ignore_temperature_probe=1
</pre>

==== Flashing the boot logo ====

More info: https://github.com/xsetiadi/droid4-kexecboot/blob/master/LOGO

<pre>
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
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
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
</pre>

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

==== USSD ====

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

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

If one wants to mirror the screen on HDMI, this can be done like so, for landscape:

<pre>
xrandr --newmode "960x540_60.00" 40.75 960 992 1088 1216 540 543 548 562 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1
</pre>

For rotation, something like this might or might not work:

<pre>
xrandr --newmode "960x540_60.00ROT" 43.00 544 576 632 720 960 963 973 996 -hsync +vsync
xrandr --addmode HDMI-1 "960x540_60.00ROT"
xrandr --output HDMI-1 --mode "960x540_60.00" --same-as DSI-1 --rotate right
</pre>

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

==== BT Audio headset ====

sudo apt install pulseaudio-module-bluetooth blueman bluez
sudo modprobe hci_uart
pactl load-module module-bluetooth-discover
blueman-manager

Pair & trust your device in blueman, connect audiosink. You can close blueman now. The quality seems a bit better in 'offline mode'.

==== Torch ====

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.

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):

<source>
##Install the prerequisites
$ sudo apt install i2c-tools

## Turn LED on in torch mode
$ sudo i2cset -y 2 0x53 0x10 0x1a

## Turn LED on in privacy indication mode
$ sudo i2cset -y 2 0x53 0x10 0x19

## Turn LED off (in any mode)
$ sudo i2cset -y 2 0x53 0x10 0x18

## Use LED for doing a hella bright flash for some time once and then turn off
$ sudo i2cset -y 2 0x53 0x10 0x1b

</source>

== Using a configured Leste sdcard in a different Droid4 ==

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.

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.

To recalibrate the wifi firmware on a different Droid4, you must reset the FEM parameters to stock settings on the new device, then recalibrate.
If you can get the device online (usb networking or moving close to the WLAN AP) this can be done with.
apt reinstall firmware-ti-connectivity
If not, you can download the firmware-ti-connectivity_[version]_all.deb on another Leste device
apt download firmware-ti-connectivity
Then copy the .deb to your new device and install that (as root) with
dpkg -i firmware-ti-connectivity_[version]_all.deb
Then (as root) re-calibrate the wifi chip by running
/usr/bin/maserati-calibrate
Then reboot.

== Gallery ==

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

== Status overview ==

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

[[Category:Device]]

Main Page

2026-09-19T16:16:27Z

Arno11-n900: /* Links */

== Description ==

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

You can find us on '''irc.libera.chat''', channel '''#maemo-leste''', you can [[IRC channel|use IRC]] to connect if you wish.

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

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

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

For some devices, we have development images available, such as the [[Nokia N900]], the [[Motorola Droid 4]], the [[Google Pixel 3a]] 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.

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

== Useful resources, lists and pages ==

* To get started with a new install, see [[Getting_Started|Getting Started]].
* Read our [[Leste_FAQ|Frequently Asked Questions]]
* List of [[:Category:Device]] with support to varying degrees
* Latest downloadable images: https://maedevu.maemo.org/images/
* List of "extras" software packages that have a wiki page: https://leste.maemo.org/Category:Extras
* Read how to get started with [[Development]]
* You have an application you want to see in Leste? Please let us know [[Wishlist|here]].
* For a list of presentations/talks featuring Maemo Leste, see [[Talks]]

== Links ==

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

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

* Our Bugtracker: [https://git.maemo.org/leste/bugtracker/issues https://git.maemo.org/leste/bugtracker/issues]

* Our Forgejo: [https://git.maemo.org/leste https://git.maemo.org/leste]

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

* Our Extras Forgejo: [https://git.maemo.org/leste-extras https://git.maemo.org/leste-extras]

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

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

* Our IRC 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/)

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

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

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

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

* RSS Leste feed: https://git.maemo.org/leste.rss

* RSS bugtracker feed: https://git.maemo.org/leste/bugtracker.rss

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

Development/Building Packages

2026-09-19T15:14:19Z

Arno11-n900: /* Maemo Leste Extras */

= Maintenance workflow =

Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.

Taking the https://git.maemo.org/leste/libcal package as an example - a valid repository contains at least two git branches:

# master
# maemo/beowulf

Ideally, the branches should have no difference, but sometimes this may vary.
Your git repository should contain your code, and a '''debian''' directory - which contains the debian package build logic.
The compat level of the package should be no less than '''9''' and preferably it should use '''debhelper'''.

Once you have your package ready and it builds locally on your Maemo Leste VM/device, there are just a couple more things to
do to make it ready for building on Jenkins:

== The git tag ==

In '''debian/changelog''' you should have your package version. It is very important to have a git tag that reflects this version
so Jenkins and jenkins-debian-glue can figure out which revision to build.

Keep in mind that the git tag should '''only''' contain the upstream version and no package revisions or epochs, for example if we have:

<code>libcal (0.3-2) unstable; urgency=medium</code>

Our git tag would be 0.3, and '''not''' 0.3-2

Once tagged, push the tag to git origin.

NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD, so there is no need to update the tag when changing the packaging (i.e. in debian directory). Tag shall be updated only when there are changes to the source files.

== gbp.conf ==

Your '''debian''' directory should contain a file called '''gbp.conf''' with the following contents:

<code>
[DEFAULT]

upstream-tag=%(version)s
</code>

Once all this is in place, make sure that you have a '''maemo/$codename''' branch containing all this ready and pushed.

= How you can build packages =

Building a packages is easier than one might think, it requires roughly the following steps:

#. Access to a Devuan/Debian system (you can use a [[Virtual_Machine|VM running Maemo Leste]] or a [[:Category:Device|Device running Maemo Leste]].
#. Source code of a package, obtain either via '''git''' or '''apt source <packagename>'''
#. Install build dependencies (run from source directory): '''sudo apt-get build-dep .'''
#. Build a package using '''dpkg-buildpackage -uc -b'''

You can now install the package you have just built with '''dpkg -i somename.deb'''

Also see: https://wiki.debian.org/HowToPackageForDebian

== Submitting changes ==

If you make changes to a package, please submit a pull request for the repository of that package, likely: https://git.maemo.org/leste-extras/PACKAGENAME

For now, we will take care of updating tags and branches.

= How packages end up in the repository =

There are currently two repositories:

* The main repository: https://maedevu.maemo.org/leste
* The extras repository: https://maedevu.maemo.org/extras

The packages in the extras repository are not core, but useful applications nonetheless.

The codenames and an /etc/apt/sources.list file entry would look like the following:

<code>
deb https://maedevu.maemo.org/leste beowulf main contrib non-free

deb https://maedevu.maemo.org/extras beowulf main contrib non-free
</code>

Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup)

== How packages are built using Jenkins ==

Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)

All packages are hosted on https://git.maemo.org/explore/repos and a current list of all the packages in Jenkins can be found here:

https://git.maemo.org/leste/jenkins-integration/src/branch/master/config.py

Every repository has a branch for each release, for example:

# maemo/beowulf - main branch for Devuan Beowulf target
# maemo/beowulf-devel - optional branch for Devuan Beowulf with unstable/testing version

See [[Development/Branches]] for more information on the usual branches flow.

= Maemo Leste Extras =

If you wish to maintain your own package in Maemo Leste, you can apply a package at https://git.maemo.org/leste-extras/bugtracker
Have a look at the README in that repository and open a ticket.

== Consideration for HAM ==
For packages built for extras to appear correctly in Hildon Application Manager, be aware that Maemo packaging system
included a few enhancements that HAM assumes. The most important one is that your application will '''only''' appear in HAM if the
<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through
<code>.desktop</code> files, while the former is done in <code>debian/control</code>.

== Adding an icon to the package in HAM ==

In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
Next, have your Build-Depends contain '''maemo-system-services-dev'''. maemo-system-services-dev will pull in the debhelper plugin.
Following this, in your '''debian/control''', under your '''Package''', add the following entry:

<pre>
XB-Maemo-Icon-26: ${maemo:icon26}
</pre>

And finally, in '''debian/rules''', assuming you're using debhelper, add this:

<pre>
override_dh_gencontrol:
dh_maemo_icon
dh_gencontrol
</pre>

Finally, if using quilt, add the icon in '''debian/source/include-binaries'''

<pre>$ echo debian/maemo-icon.png >> debian/source/include-binaries</pre>

Further reading: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections

Development/Building Packages

2026-09-19T15:13:02Z

Arno11-n900: /* How packages are built using Jenkins */

= Maintenance workflow =

Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.

Taking the https://git.maemo.org/leste/libcal package as an example - a valid repository contains at least two git branches:

# master
# maemo/beowulf

Ideally, the branches should have no difference, but sometimes this may vary.
Your git repository should contain your code, and a '''debian''' directory - which contains the debian package build logic.
The compat level of the package should be no less than '''9''' and preferably it should use '''debhelper'''.

Once you have your package ready and it builds locally on your Maemo Leste VM/device, there are just a couple more things to
do to make it ready for building on Jenkins:

== The git tag ==

In '''debian/changelog''' you should have your package version. It is very important to have a git tag that reflects this version
so Jenkins and jenkins-debian-glue can figure out which revision to build.

Keep in mind that the git tag should '''only''' contain the upstream version and no package revisions or epochs, for example if we have:

<code>libcal (0.3-2) unstable; urgency=medium</code>

Our git tag would be 0.3, and '''not''' 0.3-2

Once tagged, push the tag to git origin.

NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD, so there is no need to update the tag when changing the packaging (i.e. in debian directory). Tag shall be updated only when there are changes to the source files.

== gbp.conf ==

Your '''debian''' directory should contain a file called '''gbp.conf''' with the following contents:

<code>
[DEFAULT]

upstream-tag=%(version)s
</code>

Once all this is in place, make sure that you have a '''maemo/$codename''' branch containing all this ready and pushed.

= How you can build packages =

Building a packages is easier than one might think, it requires roughly the following steps:

#. Access to a Devuan/Debian system (you can use a [[Virtual_Machine|VM running Maemo Leste]] or a [[:Category:Device|Device running Maemo Leste]].
#. Source code of a package, obtain either via '''git''' or '''apt source <packagename>'''
#. Install build dependencies (run from source directory): '''sudo apt-get build-dep .'''
#. Build a package using '''dpkg-buildpackage -uc -b'''

You can now install the package you have just built with '''dpkg -i somename.deb'''

Also see: https://wiki.debian.org/HowToPackageForDebian

== Submitting changes ==

If you make changes to a package, please submit a pull request for the repository of that package, likely: https://git.maemo.org/leste-extras/PACKAGENAME

For now, we will take care of updating tags and branches.

= How packages end up in the repository =

There are currently two repositories:

* The main repository: https://maedevu.maemo.org/leste
* The extras repository: https://maedevu.maemo.org/extras

The packages in the extras repository are not core, but useful applications nonetheless.

The codenames and an /etc/apt/sources.list file entry would look like the following:

<code>
deb https://maedevu.maemo.org/leste beowulf main contrib non-free

deb https://maedevu.maemo.org/extras beowulf main contrib non-free
</code>

Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup)

== How packages are built using Jenkins ==

Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)

All packages are hosted on https://git.maemo.org/explore/repos and a current list of all the packages in Jenkins can be found here:

https://git.maemo.org/leste/jenkins-integration/src/branch/master/config.py

Every repository has a branch for each release, for example:

# maemo/beowulf - main branch for Devuan Beowulf target
# maemo/beowulf-devel - optional branch for Devuan Beowulf with unstable/testing version

See [[Development/Branches]] for more information on the usual branches flow.

= Maemo Leste Extras =

If you wish to maintain your own package in Maemo Leste, you can apply a package at https://github.com/maemo-leste-extras/bugtracker
Have a look at the README in that repository and open a ticket.

== Consideration for HAM ==
For packages built for extras to appear correctly in Hildon Application Manager, be aware that Maemo packaging system
included a few enhancements that HAM assumes. The most important one is that your application will '''only''' appear in HAM if the
<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through
<code>.desktop</code> files, while the former is done in <code>debian/control</code>.

== Adding an icon to the package in HAM ==

In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
Next, have your Build-Depends contain '''maemo-system-services-dev'''. maemo-system-services-dev will pull in the debhelper plugin.
Following this, in your '''debian/control''', under your '''Package''', add the following entry:

<pre>
XB-Maemo-Icon-26: ${maemo:icon26}
</pre>

And finally, in '''debian/rules''', assuming you're using debhelper, add this:

<pre>
override_dh_gencontrol:
dh_maemo_icon
dh_gencontrol
</pre>

Finally, if using quilt, add the icon in '''debian/source/include-binaries'''

<pre>$ echo debian/maemo-icon.png >> debian/source/include-binaries</pre>

Further reading: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections