Maemo Leste Wiki - User contributions [en]

Category:Extras

2026-04-28T16:35:14Z

Arno11: update

This page contains a list of packages in Maemo Leste Extras with wiki pages

To install packages from extras you need to add one of the following repositories according to the used release.

<code>
deb https://maedevu.maemo.org/extras daedalus main contrib non-free

deb https://maedevu.maemo.org/extras excalibur main contrib non-free
</code>

Main Page

2026-04-28T16:03:46Z

Arno11: /* Description */

== Description ==

Welcome to the Maemo Leste wiki; Maemo Leste continues the legacy of Maemo Fremantle. We aim to provide a free Maemo experience on mobile phones and tablets like the Nokia N900, Motorola Droid 4, PinePhone, 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]] 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://phoenix.maemo.org/view/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 Github: [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 Github: [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://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

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

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

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

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

IRC channel

2026-04-28T16:01:30Z

Arno11: matrix not working anymore with irc

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

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

Development

2026-04-26T21:48:11Z

Arno11: /* Developing on a device */

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

== Communication and organising ==

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

== Task Summary ==

For current (semi) impactful tasks, see

[[Development/Tasks]]

== Codename ==

* Maemo Leste is currently based on Devuan Daedalus, which is based on Debian Bookworm.

== Guides ==

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

== Technical ==

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

=== Jenkins ===

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

=== Developing on a device ===

All development software and tests end up in 'daedalus-devel' apt source. For enabling this edit '/etc/apt/sources.list' and add this line:

deb https://maedevu.maemo.org/leste daedalus-devel main contrib non-free droid4

The exact line might depend on your device; just copy the maemo daedalus line and change daedalus to daedalus-devel - for example, if you're not on a mapphone (droid) device, you probably don't want the droid4 component in the line.

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

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

=== Building a Maemo Leste image ===

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

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

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

=== Crossbuilding ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

$ uname -m
aarch64

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

$ exit
$ sudo umount dev/pts dev proc

=== Localization ===

See [[Localization]]

=== TODO ===

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

Development

2026-04-26T21:43:50Z

Arno11: /* Codename */

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

== Communication and organising ==

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

== Task Summary ==

For current (semi) impactful tasks, see

[[Development/Tasks]]

== Codename ==

* Maemo Leste is currently based on Devuan Daedalus, which is based on Debian Bookworm.

== Guides ==

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

== Technical ==

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

=== Jenkins ===

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

=== Developing on a device ===

All development software and tests end up in 'chimaera-devel' apt source. For enabling this edit '/etc/apt/sources.list' and add this line:

deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free droid4

The exact line might depend on your device; just copy the maemo chimaera line and change chimaera to chimaera-devel - for example, if you're not on a mapphone (droid) device, you probably don't want the droid4 component in the line.

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

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

=== Building a Maemo Leste image ===

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

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

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

=== Crossbuilding ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

$ uname -m
aarch64

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

$ exit
$ sudo umount dev/pts dev proc

=== Localization ===

See [[Localization]]

=== TODO ===

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

Main Page

2026-04-26T21:41:24Z

Arno11: /* Description */

== Description ==

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

You can find us on '''irc.libera.chat''', channel '''#maemo-leste''', you can [[IRC channel|use Matrix]] 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]] 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://phoenix.maemo.org/view/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 Github: [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 Github: [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://github.com/maemo-leste/mpi https://github.com/maemo-leste/mpi]

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

* Our Forum [https://talk.maemo.org/forumdisplay.php?f=66 https://talk.maemo.org/forumdisplay.php?f=66]

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

* Our Twitter: [https://twitter.com/maemoleste @maemoleste]

* Distrowatch: [https://distrowatch.com/dwres.php?resource=submit Maemo Leste] (give us an upvote)
</div>

Nokia N900

2025-12-06T04:55:48Z

Arno11: /* Overclocking - Old method for 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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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.

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.

'''Note for Chimaera image:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Only for Chimaera: Dist-upgrade to -devel (not working without)

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

2025-04-17T08:18:10Z

Arno11: /* SD Card and first boot */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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.

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.

'''Note for Chimaera image:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Only for Chimaera: Dist-upgrade to -devel (not working without)

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

2025-04-17T08:15:02Z

Arno11: /* Voice Calls / SIP Calls */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note for Chimaera image:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Only for Chimaera: Dist-upgrade to -devel (not working without)

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

2025-04-17T08:12:15Z

Arno11: /* Overclocking - Old method for 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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note for Chimaera image:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Dist-upgrade to -devel (not working without)

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

2025-04-17T08:07:53Z

Arno11: /* SD Card and first boot */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note for Chimaera image:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Dist-upgrade to -devel (not working without)

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

2025-04-17T08:03:57Z

Arno11: /* Web browsing */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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

- Dist-upgrade to -devel (not working without)

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

2025-04-17T08:00:28Z

Arno11: /* Deactivating apt-worker */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

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
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 Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
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>

(wait for a few seconds...)

<pre>
chmod +w /home/user/omap3-n900.dts
</pre>

(then the funny part...)

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

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

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>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>
deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900
</pre>

in <code>/etc/apt/sources.list</code>

('''Warning:''' don't remove other sources in this file)

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 ===

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>
sudo apt install links2
</pre>

To use it in graphical mode, run in terminal:

<code>links2 -g</code> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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

2024-09-14T20:40:44Z

Arno11:

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:36:17Z

Arno11:

{{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
|media=microSDHC (up to 512GB)
|usb=Micro USB 2.0 Slave
|camera=
|sensors=
|other=
|headers=
|battery=1320mAh
|sw_kernel=6.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:26:57Z

Arno11: /* Overclocking */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:20:10Z

Arno11: /* Status table */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:17:23Z

Arno11: /* Voice Calls / SIP Calls */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

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:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:15:29Z

Arno11: /* More SWAP / SWAP activation */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:09:34Z

Arno11: /* SD Card and first boot */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

<pre>deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900</pre>

in <pre>/etc/apt/sources.list</pre>

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:07:46Z

Arno11: /* SD Card and first boot */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

'''Note:''' it is recommended to dist-upgrade to -devel to enable more features by adding

deb https://maedevu.maemo.org/leste chimaera-devel main contrib non-free n900

in /etc/apt/sources.list

('''Warning:''' don't remove other sources in this file)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T20:01:41Z

Arno11: /* Overclocking */

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-09-14T19:58:49Z

Arno11:

{{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.6
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-07-17T10:37:54Z

Arno11: /* Voice Calls / SIP Calls */

{{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.1
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate it through the transitions.ini file:

<pre>[HOME]

radius = 0

radius_more = 0
</pre>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -a -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.76 / 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-07-17T10:27:41Z

Arno11: /* Status table */

{{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.1
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate it through the transitions.ini file:

<pre>[HOME]

radius = 0

radius_more = 0
</pre>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.76 / 6.6 LTS (experimental) || 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-07-17T10:24:31Z

Arno11: /* Status table */

{{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.1
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate it through the transitions.ini file:

<pre>[HOME]

radius = 0

radius_more = 0
</pre>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.76 / 6.6 LTS (experimental) || 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
|-
| 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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

2024-07-17T10:21:08Z

Arno11: /* More SWAP / SWAP activation */

{{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.1
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate it through the transitions.ini file:

<pre>[HOME]

radius = 0

radius_more = 0
</pre>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.76 / 6.6 LTS (experimental) || 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), 850MHz is not working with all devices, Turbo mode works.
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection
|-
| 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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]]

Extras/drnoksnes

2024-07-15T15:58:59Z

Arno11: /* Tested Super Nintendo/ SNES games */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only with armhf architecture at the moment (Nokia N900 and Motorola Droid 4).

The emulator uses the original maemo 5 GUI: This version of DrNokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

In settings/Zoom, 'Scale to fit' is recommended to be able to switch between fullscreen and window mode easely.

On N900 target framerate at '50-60 fps' works better than 'auto'.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, World Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

[[File:2024-06-07-224020 800x480 scrot.png]]

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

Extras/drnoksnes

2024-07-15T15:21:09Z

Arno11: /* Status */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only with armhf architecture at the moment (Nokia N900 and Motorola Droid 4).

The emulator uses the original maemo 5 GUI: This version of DrNokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

In settings/Zoom, 'Scale to fit' is recommended to be able to switch between fullscreen and window mode easely.

On N900 target framerate at '50-60 fps' works better than 'auto'.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

[[File:2024-06-07-224020 800x480 scrot.png]]

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

Extras/drnoksnes

2024-07-15T15:01:57Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only with armhf architecture at the moment (Nokia N900 and Motorola Droid 4).

The emulator uses the original maemo 5 GUI: This version of DrNokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

In settings/Zoom, 'Scale to fit' is recommended to be able to switch between fullscreen and window mode easely.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

[[File:2024-06-07-224020 800x480 scrot.png]]

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

Extras/drnoksnes

2024-07-15T14:52:49Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrNokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

[[File:2024-06-07-224020 800x480 scrot.png]]

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

Extras/drnoksnes

2024-07-15T11:33:14Z

Arno11: /* Tips */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrnokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

[[File:2024-06-07-224020 800x480 scrot.png]]

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

File:2024-06-07-224020 800x480 scrot.png

2024-07-15T11:32:44Z

Arno11:

Streetfighter

Extras/drnoksnes

2024-07-15T11:31:32Z

Arno11: /* Tested Super Nintendo/ SNES games */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrnokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

[[File:2024-06-07-223735 800x480 scrot.png]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

File:2024-06-07-223735 800x480 scrot.png

2024-07-15T11:30:59Z

Arno11:

Kong

Extras/drnoksnes

2024-07-15T11:30:01Z

Arno11: /* Status */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrnokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

[[File:2024-06-07-223207 800x480 scrot.png]]

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

File:2024-06-07-223207 800x480 scrot.png

2024-07-15T11:29:16Z

Arno11:

Mario

Extras/drnoksnes

2024-07-15T11:27:33Z

Arno11: /* Status */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrnokSnes is a clone of the old maemo one.

== Status ==

[[File:2024-07-15-124249 800x480 scrot.png]]

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

File:2024-07-15-124249 800x480 scrot.png

2024-07-15T11:26:50Z

Arno11:

Drnoksnes GUI

Extras/drnoksnes

2024-07-15T11:20:45Z

Arno11: Created page with "{{Infobox Package |status=Working |devices=Nokia_N900,Motorola_Droid_4 |date_in_repo=2024-07-14 |maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes |cate..."

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-07-14
|maemo_leste_repo=https://github.com/maemo-leste-extras/drnoksnes
|category=Games
|packager=[[User:Arno11]]
}}

DrNokSnes is a Super Nintendo / SNES emulator running on Maemo-Leste.

It works only on armhf architecture devices at the moment like Nokia N900 and Motorola Droid.

The emulator uses the original maemo 5 GUI: This version of DrnokSnes is a clone of the old maemo one.

== Status ==

* SNES games are playable, with sound and input, running at 50-60 fps on N900.

Default configuration is already optimised. Like other emulators it is recommended to disable hildon compositing while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly from the GUI.

=== Tested Super Nintendo/ SNES games ===

Donkey Kong Country 1 & 2, FF VI , ISS, Killer Instinct, Zelda a Link to the Past, John Madden Football, Mickey Magical Quest, Secret of Mana, Street Fighter II Turbo, Super Mario Allstars, Super Mario World, Super Mario Kart, Mega Man X, NHLPA Hockey 93, Pinball Fantasy, Puzzle Bubble, R-Type 3, Samurai Showdown, Super Probotector, Super Tennis, Workd Heroes.

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/bin/drnoksnes -c /usr/games/drnoksnes.conf /game_path

Default keymap is visible in /usr/games/drnoksnes.conf

On N900, it could be useful to activate boost mode (720MHz or 805MHz).

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Try to improve sound in some games

[[Category:Extras]]

Nokia N900

2024-07-12T21:05:50Z

Arno11: /* Status table */

{{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.1
|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 ===

* Latest image: https://phoenix.maemo.org/job/leste-image-n900/lastSuccessfulBuild/artifact/arm-sdk/dist/
* Image archive: https://maedevu.maemo.org/images/n900/

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:

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

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

<code>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
</code>

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:

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

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

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

==== Existing Fremantle ====

If you have a functional Fremantle installation, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1"

2. Install "Linux kernel for power user (boot image for U-Boot)". This is optional, but recommended.

3. Add Maemo Leste menu item (run as root):
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
u-boot-update-bootmenu

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

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

modprobe ledtrig-default-on

And:

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

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 Nokia N900. Don't detach the charger immediately, give it some time after you see "Fully charged" message (10 minutes should be enough).
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration from the beginning (fully charge the device again).
* 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, reboot the device.

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

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

It uses 250-500-550-600-720-805-850MHz 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 850MHz.

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

'''WARNING: some devices can't run at 850MHz. For this specific case, select powersave governor instead of ondemand, activate boost mode, replace 850000 by 805000 (or 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):

cat > /etc/bootmenu.d/30-maemo-leste-Overclock.item << "EOF" &&
ITEM_NAME="Maemo Leste Overclock"
ITEM_KERNEL="uImageX"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext2"
EOF
u-boot-update-bootmenu

2) From Maemo Leste (run as root):

<code>cp /usr/lib/linux-image-omap/omap3-n900.dtb /home/user</code>

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

(wait for a few seconds...)

<code>chmod +w /home/user/omap3-n900.dts</code>

(then the funny part...)

<code>nano /home/user/omap3-n900.dts</code>

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

Find "opp-table" with <code>ctl+w</code> and 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>

Then <code>ctl+x</code> to save and close.

And still as root:

<code>rm /home/user/omap3-n900.dtb</code>

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

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 (ie vmlinuz-6.1.30)

As root:

<code>cat /boot/vmlinuz-<version> /home/user/omap3-n900.dtb > /tmp/zImage_dtb</code>

<code>mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -d /tmp/zImage_dtb /boot/uImageX</code>

That's it !

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, most probably because of their lower build quality.

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

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.

('''Note:''' it is recommended to dist-upgrade to -devel to enable more features)

=== 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 .nomedia file in /home/user folder:

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

=== Deactivating apt-worker ===

Run:

<pre>gconftool -s --type int /apps/hildon/update-notifier/check_interval 2147483647</pre>

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

Install cpufrequtils.

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

=== More SWAP / SWAP activation ===

Enabling swap on eMMC 768MB partition if not already activated on first boot (works on the fly):

<pre>sudo swapon /dev/mmcblk1p3</pre> (editing /etc/fstab/ is not needed and done automatically on next reboot)

(Note: eMMC swap is '''highly recommended''' and faster than SD card swap)

'''Other possibility:''' 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 /swapfile</pre>

<pre>sudo mkswap /swapfile</pre>

<pre>sudo swapon /swapfile</pre>

To make the change permanent open:

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

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

As root

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

See Fremantle documentation for perfect setup.

'''Note: like Fremantle, blur effect can cause lags and slowness.''' It is possible to deactivate it through the transitions.ini file:

<pre>[HOME]

radius = 0

radius_more = 0
</pre>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using an easy tweak-

<pre>sudo apt install links2</pre>

To use it in graphical mode, run in terminal:

<pre>links2 -g</pre> or press the hildon desktop icon.

Then press <code>Ctl + Shift + N</code> to disable Hildon composition -links2 performances will increase a lot-

Press <code>Ctl + Shift + N</code> if you want to enable Hildon composition again.

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

- Dist-upgrade to -devel (not working without)

Now SIP calls and SIP messages are working out of the box using Twinkle. (select voicecall profile in pavucontrol)

Voice calls are now working out of the box as well.

If sound is distorted, run:

<code>sudo chrt -f -p 99 $(pgrep pulseaudio)</code>

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.76 / 6.6 LTS (experimental) || 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), 850MHz is not working with all devices, Turbo mode works.
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection
|-
| 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 || evdev interface not supported in mce since it depends on iio-sensor-proxy support. https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/issues/363 for possible 'fix'
|-
| 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]]

Extras/pcsx rearmed

2024-06-29T20:15:14Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'backspace' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at full speed with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.
(The correct typo is for example 'scph7502.bin')

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-08T11:10:45Z

Arno11:

{{Infobox Package
|status=Working / Debian packaging is WIP
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at full speed with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.
(The correct typo is for example 'scph7502.bin')

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-08T10:42:43Z

Arno11: /* Status */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at full speed with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.
(The correct typo is for example 'scph7502.bin')

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-08T10:34:08Z

Arno11: /* Configuration */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.
(The correct typo is for example 'scph7502.bin')

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-08T10:33:37Z

Arno11: /* Configuration */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.
(The correct typo is for example scph7502.bin)

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-08T10:28:27Z

Arno11: /* Status */

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NTSC or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NTSC).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-07T21:51:44Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NSCT or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NSCT).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well).

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Configuration ==

Original Bios file can't be provided. The emulator use HLE bios by default which works with some games. For a full working emulation, a real pcsx bios is needed and must be added in '/usr/games/pcsx/bios' directory.

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-07T21:43:02Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NSCT or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NSCT).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well.

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

Fullscreen mode can be activated with 'F' key by default.

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]

Extras/pcsx rearmed

2024-06-07T21:37:40Z

Arno11:

{{Infobox Package
|status=Working
|devices=[[Nokia_N900]],[[Motorola_Droid_4]]
|date_in_repo=2024-05-27
|maemo_leste_repo=https://github.com/maemo-leste-extras/pcsx_rearmed
|category=Games
|packager=[[User:Arno11]]
}}

Pcsx_rearmed is a Playstation 1 emulator running on Maemo-Leste.

It works only on Nokia N900 and Motorola Droid 4 at the moment (thanks to their physical keyboards).

The emulator uses a generic GTK UI: The old maemo 5 touch GUI is not working at the moment.

== Status ==

[[File:2024-06-07-064926 800x480 scrot.png|500px|center]]

* Playstation games are playable, with sound and input, running at 25-30 fps on N900 with frameskip=1 usually but really depending of the game and if it is a NSCT or PAL version.

[[File:2024-06-07-065751 800x480 scrot.png|500px|center]]

Without frameskip and sound, games run usually at 50 or 60 fps with default CPU frequencies and buildin_gpu. But again, it is really depending of the game: some of them are 'locked' at 24 fps (PAL) or 30 fps (NSCT).

On N900, boost mode (overclock) is recommended if you play with sound. Otherwise it works well with stock frequencies, specially with the buildin_gpu.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

Default configuration is already optimised without sound and 25-30 fps. Like other emulators hildon compositing must be deactivated while playing, using Ctl+Shift+N.

Keymapping and all other parameters can be modified directly in the user config file available in /usr/games/pcsx/.pcsx/pcsx.cfg

Only buildin_gpu and gpu_unai are working (but really well.

It is possible (not all games) to speed up and increase framerate using the 'fast forward' option.

[[File:2024-06-07-100831 800x480 scrot.png|500px|center]]

WARNING: on N900 in the GUI, 'enter menu' is associated to 'escape' key.
'back' is associated to 'e' key (hardcoded).

Almost all configuration parameters are available from the GUI.

=== Tested Playstation/Psx/PsOne games===

Driver, MetalSlugX, Ace Combat 3, Spyro the Dragon, Final Fantasy 8, Legend of Mana, Medal of Honor, Metal Gear Solid, Gran Turismo, Tekken 3, V-Rally, Moto Racer 2, ISS Pro Evolution.

[[File:2024-06-07-065424 800x480 scrot.png|500px|center]]

[[File:2024-06-07-070020 800x480 scrot.png|500px|center]]

== Tips ==

If (for some reason) the GUI is not working, it is possible to directly launch a game from command line:

/usr/games/pcsx/pcsx /game_dir/your_game.zip

Default keymap is visible in /usr/games/pcsx/.pcsx/pcsx.cfg

On N900, to activate boost mode (720MHz or 805MHz):

As root:

echo 1 > /sys/devices/system/cpu/cpufreq/boost

echo 720000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

== TODO ==

* Implement sane default keys for the devices

* Try to implement Maemo 5 -touch- UI

[[Category:Extras]]