Maemo Leste Wiki - User contributions [en]

Nokia N900

2026-01-07T14:58:35Z

Sicelo: /* Existing Fremantle */

{{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 and you want to keep it, you can follow these steps instead:

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

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

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

(press enter at the end if necessary)

And then run:

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

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

=== Increase filesystem size ===

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

== Serial ==

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

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

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

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

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

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them. There is no clear consensus about this, but it is best to err on the side of caution.
=== Torch ===

The N900 has an Analog Devices ADP1653 flash controller, mainly for use with the camera. It drives two white power LEDs connected in series, and has an additional red indicator led (referred to as a privacy indicator). The ADP1653 has a driver in mainline kernel, and it probes fine. However, some DTS changes are needed to make it work, since the driver requires it to be tied to a camera.

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

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

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

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

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

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

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

== Power Management ==

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

Power usage right now is reported to be about 45mA (idle, modem ON and data ON). On a good battery this will last for about 30 hours. Power management on the N900 is being worked on: https://github.com/maemo-leste/bugtracker/issues/170

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

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

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

To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.

Currently it does not yet reliably reach any sleep modes.

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

== Battery calibration ==

Nokia N900 has bq27200 integrated circuit for monitoring battery state. The datasheet can be found here: http://www.ti.com/lit/ds/symlink/bq27200.pdf. If you are curious, check the section called "Gas Gauge Operation" for how the battery calibration is done in a low level.

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

* Fully charge the Nokia N900
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration process from the beginning (fully charge the device again).
* You may use the device as you normally do. You may power it off, power it on, reboot. All as usual. Just don't connect the device to a charger or a PC using the USB cable.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* Wait for about 20 seconds and attach the charger. If the device was powered off because of battery depletion, it's fine. The battery should have done the calibration cycle. Just attach the charger to the device, give it a minute and press power button to start booting.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

After the first calibration cycle you will see that it has ~1700 mAh for the fully charged battery. This value is wrong. It's how the battery calibration works in low level: it can't change the fully charged value of the battery in steps that exceed 12.5%. What this means for us: it's needed to repeat the calibration cycle several times to get more accurate value. It may take about 3-7 calibration cycles to get the proper mAh value for fully charged battery. If you spend some time on this process, you will get really accurate battery gauge and you will always know how much charge is remaining.

Tip 1. If for any reason you want to reset the battery calibration value to see the message “Battery is not calibrated” again, you should remove the battery from the device for about 6 hours.
Tip 2. If you replace the battery, you may want to do 1-2 calibration cycles described above to update the gauge for your new battery.

== Accessing MTD ==

List devices:
cat /proc/mtd

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

== Overclocking (optional) ==

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

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

To enable it, edit:

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

And replace 0 by 1.

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

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

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

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

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

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

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

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

(press enter at the end if necessary)

And then run:

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

2) From Maemo Leste (run as root):

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

(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

2026-01-07T14:17:05Z

Sicelo: /* Existing Fremantle */

{{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 and you want to keep it, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1". This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

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

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

(press enter at the end if necessary)

And then run:

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

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

=== Increase filesystem size ===

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

== Serial ==

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

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

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

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

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

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them. There is no clear consensus about this, but it is best to err on the side of caution.
=== Torch ===

The N900 has an Analog Devices ADP1653 flash controller, mainly for use with the camera. It drives two white power LEDs connected in series, and has an additional red indicator led (referred to as a privacy indicator). The ADP1653 has a driver in mainline kernel, and it probes fine. However, some DTS changes are needed to make it work, since the driver requires it to be tied to a camera.

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

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

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

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

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

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

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

== Power Management ==

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

Power usage right now is reported to be about 45mA (idle, modem ON and data ON). On a good battery this will last for about 30 hours. Power management on the N900 is being worked on: https://github.com/maemo-leste/bugtracker/issues/170

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

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

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

To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.

Currently it does not yet reliably reach any sleep modes.

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

== Battery calibration ==

Nokia N900 has bq27200 integrated circuit for monitoring battery state. The datasheet can be found here: http://www.ti.com/lit/ds/symlink/bq27200.pdf. If you are curious, check the section called "Gas Gauge Operation" for how the battery calibration is done in a low level.

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

* Fully charge the Nokia N900
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration process from the beginning (fully charge the device again).
* You may use the device as you normally do. You may power it off, power it on, reboot. All as usual. Just don't connect the device to a charger or a PC using the USB cable.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* Wait for about 20 seconds and attach the charger. If the device was powered off because of battery depletion, it's fine. The battery should have done the calibration cycle. Just attach the charger to the device, give it a minute and press power button to start booting.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

After the first calibration cycle you will see that it has ~1700 mAh for the fully charged battery. This value is wrong. It's how the battery calibration works in low level: it can't change the fully charged value of the battery in steps that exceed 12.5%. What this means for us: it's needed to repeat the calibration cycle several times to get more accurate value. It may take about 3-7 calibration cycles to get the proper mAh value for fully charged battery. If you spend some time on this process, you will get really accurate battery gauge and you will always know how much charge is remaining.

Tip 1. If for any reason you want to reset the battery calibration value to see the message “Battery is not calibrated” again, you should remove the battery from the device for about 6 hours.
Tip 2. If you replace the battery, you may want to do 1-2 calibration cycles described above to update the gauge for your new battery.

== Accessing MTD ==

List devices:
cat /proc/mtd

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

== Overclocking (optional) ==

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

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

To enable it, edit:

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

And replace 0 by 1.

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

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

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

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

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

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

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

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

(press enter at the end if necessary)

And then run:

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

2) From Maemo Leste (run as root):

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

(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

2026-01-07T14:15:27Z

Sicelo: /* Existing Fremantle */

{{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 and you want to keep it, you can follow these steps instead:

1. Install "U-Boot with kernel 2.6.28-omap1". This will 'flash' u-boot into the kernel area. This u-boot also contains the kernel itself, so doing this is safe.

2. If you were not running the stock kernel, install "Linux kernel for power user (boot image for U-Boot)". This is important, to ensure that the correct kernel is booted, otherwise modules will not match and boot will fail.

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

(press enter at the end if necessary)

And then run:

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

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

=== Increase filesystem size ===

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

== Serial ==

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

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

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

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

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

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them. There is no clear consensus about this, but it is best to err on the side of caution.
=== Torch ===

The N900 has an Analog Devices ADP1653 flash controller, mainly for use with the camera. It drives two white power LEDs connected in series, and has an additional red indicator led (referred to as a privacy indicator). The ADP1653 has a driver in mainline kernel, and it probes fine. However, some DTS changes are needed to make it work, since the driver requires it to be tied to a camera.

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

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

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

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

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

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

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

== Power Management ==

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

Power usage right now is reported to be about 45mA (idle, modem ON and data ON). On a good battery this will last for about 30 hours. Power management on the N900 is being worked on: https://github.com/maemo-leste/bugtracker/issues/170

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

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

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

To enable the OMAP sleep debug LEDs (on the keyboard). Open keyboard, turn off the screen with the slider, and the LEDs will turn off if the phone ever reaches sleep modes.

Currently it does not yet reliably reach any sleep modes.

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

== Battery calibration ==

Nokia N900 has bq27200 integrated circuit for monitoring battery state. The datasheet can be found here: http://www.ti.com/lit/ds/symlink/bq27200.pdf. If you are curious, check the section called "Gas Gauge Operation" for how the battery calibration is done in a low level.

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

* Fully charge the Nokia N900
* Detach the charger and don't attach it again until the battery is fully depleted. Remember: if you attach the charger (or USB cable) at least once, you will need to start the calibration process from the beginning (fully charge the device again).
* You may use the device as you normally do. You may power it off, power it on, reboot. All as usual. Just don't connect the device to a charger or a PC using the USB cable.
* When your Nokia N900 has battery depleted, it will alarm you with the "battery low" sound.
* Wait for about 20 seconds and attach the charger. If the device was powered off because of battery depletion, it's fine. The battery should have done the calibration cycle. Just attach the charger to the device, give it a minute and press power button to start booting.
* If you still see "Battery not calibrated" message, you will need to restart the calibration process from scratch.

After the first calibration cycle you will see that it has ~1700 mAh for the fully charged battery. This value is wrong. It's how the battery calibration works in low level: it can't change the fully charged value of the battery in steps that exceed 12.5%. What this means for us: it's needed to repeat the calibration cycle several times to get more accurate value. It may take about 3-7 calibration cycles to get the proper mAh value for fully charged battery. If you spend some time on this process, you will get really accurate battery gauge and you will always know how much charge is remaining.

Tip 1. If for any reason you want to reset the battery calibration value to see the message “Battery is not calibrated” again, you should remove the battery from the device for about 6 hours.
Tip 2. If you replace the battery, you may want to do 1-2 calibration cycles described above to update the gauge for your new battery.

== Accessing MTD ==

List devices:
cat /proc/mtd

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

== Overclocking (optional) ==

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

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

To enable it, edit:

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

And replace 0 by 1.

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

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

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

Installing cpufrequtils is useful to change frequency governors.

Prefer "conservative" instead of "ondemand" governor.

"Performance" governor locks N900 at 805MHz.

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

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

== Overclocking - Old method for testing purpose ==

To be able to overclock two steps are needed:

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

(press enter at the end if necessary)

And then run:

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

2) From Maemo Leste (run as root):

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

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

Status/GPS

2025-06-29T20:03:57Z

Sicelo: migrate links to git.maemo.org

== Fremantle Gypsy ==

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

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

Install gpsd and gpsd-clients:

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

Stop apparmor (for testing only!):

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

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

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

Then in another terminal, type:

<pre>
cgps
</pre>

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

== Relevant URLs ==

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

== Regarding Droid 4 GPS ==

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

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

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

Status/GPS

2025-06-29T20:02:48Z

Sicelo: migrate links to git.maemo.org

== Fremantle Gypsy ==

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

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

Install gpsd and gpsd-clients:

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

Stop apparmor (for testing only!):

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

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

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

Then in another terminal, type:

<pre>
cgps
</pre>

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

== Relevant URLs ==

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

== Regarding Droid 4 GPS ==

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

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

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

Motorola Droid Bionic

2025-06-29T20:01:20Z

Sicelo: migrate links to git.maemo.org

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

== Installation ==

Hardware requirements:

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

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

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

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

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

# droid4-kexecboot.img

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

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

Now, flash the Maemo Leste image to your sdcard:

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

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

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

== Notes ==

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

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

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

== Serial Cable ==

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

== Bluetooth ==

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

== Unlocking the modem for usage in Europe ==

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

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

Tony also writes:

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

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

== Stuff to try ==

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

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

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

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

==== USSD ====

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

== Old status table ==

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

[[Category:Device]]

Motorola Droid Bionic

2025-06-29T19:59:18Z

Sicelo: migrate links to git.maemo.org

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

== Installation ==

Hardware requirements:

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

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

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

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

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

# droid4-kexecboot.img

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

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

Now, flash the Maemo Leste image to your sdcard:

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

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

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

== Notes ==

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

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

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

== Serial Cable ==

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

== Bluetooth ==

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

== Unlocking the modem for usage in Europe ==

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

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

Tony also writes:

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

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

== Stuff to try ==

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

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

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

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

==== USSD ====

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

== Old status table ==

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

[[Category:Device]]

Development/Tasks

2025-06-29T19:58:31Z

Sicelo: migrate links to git.maemo.org

== Applications ==

This page lists some of the more important open issues for Maemo Leste. We have a complete list here, on github, but it's a bit hard to navigate: https://git.maemo.org/leste/bugtracker/issues

{| class="wikitable"
! Task
! Description
! Task Status
! User(s) working on task
! GH Bug
! URLs
! Notes
|-

| Gtk3 port of theme and hildon widgets || Big task, port hildon widgets and theme from gtk2 to gtk3. Funding is available for this task || WIP || || https://git.maemo.org/leste/bugtracker/issues/261 || || Parayzd was working on this
|-
| Qt5 of theme and hildon widgets || Significant task || MOSTLY || [[User:freemangordon]] made a start, [[User:Wizzup]] picked up some of the work || || https://git.maemo.org/leste/qtstyleplugins/ + https://git.maemo.org/leste/qt-platform-maemo/tree/qmenu || Mainly usable already!
|-
| libicd-network-ofono should set up ipv4 upon connect || Required to get usable cellular data. Provisioning is done, but the actual link itself is not yet set up. Once we have this, we should have usable cellular data on all devices with a supported modem. || DONE || || || ||
|-
| Extend ofono droid4 modem support || This is done and should be stable. || DONE || Tony, Pavel, [[User:freemangordon]] and [[User:Wizzup]] are working on this || || https://github.com/pavelmachek/ofono/commits/d4-v1.29 ||
|-
| Finish connui-cellular port to ofono || Porting of connui libraries, status and home applets, settings applets and pincode applets to ofono || WIP || [[User:Wizzup]] || https://git.maemo.org/leste/bugtracker/issues/256 || https://git.maemo.org/leste/connui-cellular ||
|-
| Test phone calls on the N900 || Figure out cmtspeechdata magic || WORKS || [[User:Wizzup]], [[User:Sicelo]], Pavel || || ||
|-
| Create simple phone UI to test dialing/accepting phone calls using Telepathy || Can use sphone, which works for calls right now, just not using Telepathy. || WORKS || ? || || ||
|-
|"hildonize" surf2 or create a simple "hildonized" webkit browser || See "Jib" || DONE || [[User:Wizzup]], dsc || || ||
|-
| Look at N900 power saving || We do not hit omap off modes nearly as much as we should (in fact, we never do), this should be looked at || WIP || [[User:Wizzup]], tmlind || || || Actually works quite well on the droid4. Let's do the same for Droid4. :)
|-
| osso-abook || We need osso-abook in place for all applications that need contacts (phone ui, sms ui, email ui, more) || DONE || [[User:freemangordon]] || ||https://git.maemo.org/leste/osso-abook || Making good progress
|-
| Port all packages for maemo-leste to debhelper 9 or higher || Requires for us to migrate to a newer Debian (Buster) / Devuan (Beowulf) || DONE || [[User:Parazyd]], [[User:Wizzup]], [[User:meridion]], [[User:Spinal84]] || https://git.maemo.org/leste/bugtracker/issues/234 || ||
|-
| Monitor keyboard slide and attached state || Required on devices with a keyboard like [[Nokia_N900]] and [[Motorola_Droid_4]] to show specific parts of the virtual keyboard, or rotate || DONE || [[User:ThomasAH]], Spinal84 || https://git.maemo.org/leste/ke-recv/pull/2 ; https://git.maemo.org/leste/bugtracker/issues/17#issuecomment-528497018 || ke-recv part for slide monitoring is in place, we just need live keyboard-attached monitoring now. https://git.maemo.org/leste/mce/blob/master/event-input.c#L474 https://git.maemo.org/leste/ke-recv-extra/blob/master/src/input-device.c || mce has quite some usable code for this already, resulting code should probably go into ke-recv-extra (aka hulda). mer-core (sailfish/nemomobile) has keyboard monitoring integrated into mce, so we could also look at (using) that
|-
| Forward-port clutter patches from Nokia N900 clutter 0.8 to libclutter1.0 ? || *MAYBE* Required on devices with a PowerVR GPU like [[Nokia_N900]] and [[Motorola_Droid_4]] for hildon-desktop to work. In particular important for Droid 4 to get accelerated hildon-desktop || DONE (by staying at clutter 0.8) || || || https://github.com/spinal84/clutter-0.8/tree/blit/debian/patches ||
|-
| Set up leste "extras" repository || A repository with non-core applications, games, etc would be very welcome || DONE || [[User:Wizzup]], [[User:Parazyd]] || || https://git.maemo.org/leste-extras ; https://maemo.org/downloads/score/Maemo5/25/ ||
|-
| hildon-application-manager usable || We currently have HAM packaged, but it needs fixes for various compile issues we hacked around, cssu-specific parts need to be removed, and we need to figure out what we need to do for our repositories to make it work well || DONE || [[User:minicom]], [[User:Wizzup]], [[User:Parazyd]] || || || Goal is to have a usable app manager, so let's just use it, fix it, use it, etc.
|-
| Fix virtual keyboard rendering || On a screen that is not the same of the N900 (800x480), the virtual keyboard doesn't look very pretty. Lets just make it work on any display size || DONE || || || ||
|-
| Fix remaining hildon-desktop portait mode issues || The application launcher results in a black screen, and osso-xterm in portait mode is also resulting in a black screen || DONE || [[User:freemangordon]] || || ||
|-
| Test phone calls on the droid4 || Phone calls should work, with audio, when alsamixer is set up properly, let's test it! || DONE || [[User:Wizzup]], [[User:Sicelo]] || || ||
|-
|}

Development/Porting Packages

2025-06-29T19:52:59Z

Sicelo: migrate links to git.maemo.org

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `optipng` installed. (media-gfx/optipng in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://git.maemo.org/leste-extras/ maemo-leste-extras] and [https://git.maemo.org/leste-extras/bugtracker/issues/ open an issue] in the [https://git.maemo.org/leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get an invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@git.maemo.org:leste-extras/msid

$ git remote -v
maemo git@git.maemo.org:leste-extras/msid (fetch)
maemo git@git.maemo.org:leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To git.maemo.org:leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' by visiting:
remote: https://git.maemo.org/leste-extras/msid/pull/new/maemo/beowulf
remote:
To git.maemo.org:leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>

== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Main Page

2025-06-29T16:21:08Z

Sicelo: focus on our Git instance

== 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 Chimaera (Debian Chimaera) 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-03-08T18:48:14Z

Sicelo: corrections wrt. fuel gauge

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

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

Status

2024-09-19T21:21:32Z

Sicelo:

{{Stub}}

For Device specific status pages, see See [[:Category:Device]]

The table below documents what features work on Maemo Leste on at least one device, without (a lot of) console hackery. This usually means that the feature should be decently integrated and that there has to be a UI available. This is *independent* of specific device drivers or just specified devices and doesn't mean that it necessarily works on a device

{| class="wikitable"
! Feature
! Status
! Leste software
! Notes
|-
| Desktop environment || OK || hildon || hildon home, hildon desktop, .
|-
| [[Terminal]] || OK || [https://github.com/maemo-leste/osso-xterm osso-xterm] ||
|-
| [[Status/VirtualKeyboard|Virtual keyboard]] || WIP || [https://github.com/maemo-leste/hildon-input-meta hildon-input-meta] || Should work fine for all devices, GTK2 only.
|-
| [[Status/Wireless|Wireless]] || OK || [https://github.com/maemo-leste/libicd-network-wpasupplicant libicd-network-wpasupplicant] || Works out of the box
|-
| Bluetooth || WIP || Just works if supported in the kernel, but no Maemo UI available to configure it, blueman-manager can be used ||
|-
| [[Status/Browser|Browser]] || WIP || jib || due to CPU/RAM, N900 uses Dillo
|-
| [[Status/Audio|Audio]] || OK || ? || [Basic audio/sounds work (like, notifications, charging notification, etc); will need to import alsa-policy-enforcement, port OHM
|-
| Battery / charging || OK || [https://github.com/maemo-leste/status-area-applet-battery status-area-applet-battery], [https://github.com/maemo-leste/mce mce], [https://github.com/maemo-leste-upstream-forks/upower upower] ||
|-
| [[Status/USB Peripheral|USB Peripheral]] || OK || [https://github.com/maemo-leste/hildon-status-bar-usb hildon-status-bar-usb], [https://github.com/maemo-leste/ke-recv ke-recv] || Basic support in place for N900/Droid4/Allwinner, see https://github.com/maemo-leste/bugtracker/issues/39 ; https://github.com/maemo-leste/bugtracker/issues/179 ; https://github.com/maemo-leste/ke-recv
|-
| LED control || OK || mce || Make sure the notifications are enabled in settings.
|-
| [[Status/Mobile Data|Mobile Data]] || OK || [https://github.com/maemo-leste/connui-cellular connui-cellular] [https://github.com/maemo-leste/libicd-network-ofono libicd-network-ofono] ||
|-
| [[Status/GPS|GPS]] || OK || gpsd, liblocation, location-daemon ||
|-
| [[Status/SMS|SMS]] || OK || sphone, conversations, ofono, telepathy-ring ? ||
|-
| [[Status/Phone Calls|Phone Calls]] || OK || sphone, ofono, telepathy-ring ? ||
|-
| [[Status/Application Manager|Application Manager]] || OK || [https://github.com/maemo-leste/hildon-application-manager hildon-application-manager] || Works fine, theme might look a bit off on higher resolution displays
|-
| [[Status/Media Player|Media Player]] || WIP || OMP (open media player):listening to radio streams and local music/video works || [https://github.com/maemo-leste/bugtracker/issues/25 tracking issue]
|-
| [[Status/PDF Viewer|PDF Viewer]] || Mostly works || osso-pdf-viewer || [https://github.com/maemo-leste/osso-pdf-viewer osso-pdf-viewer]
|-
| [[Status/Games|Games & Entertainment]] || OK || Works (available in [[Leste Extras]] || [https://github.com/maemo-leste/bugtracker/issues/18 sdl fullscreen] [https://github.com/maemo-leste/bugtracker/issues/238 game importing]
|-
| [[Status/Theming|Theming]] || OK || Works with themes (available in [[Leste Extras]] ||
|-
| [[Calendar|Calendar]] || OK || Qalendar UI, syncing works. (UI needs some scrolling work) ||
|-
| [[Qt|Qt]] || OK || Qt5 port mostly works || https://github.com/maemo-leste/qtstyleplugins/ + https://github.com/maemo-leste/qt-platform-maemo
|}

Leste FAQ

2024-09-19T21:12:41Z

Sicelo: fix typos; drop systemd vs openrc section since we are somewhat willing to support systemd in future

{{Stub}}

=== What is Maemo Leste? ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== What is mainline Linux? ===

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The Devuan base of Maemo Leste provides a variety of desktop environments and window managers. There are some issues at the moment with running these whilst Hildon is installed, however it has been proven that it is possible to run them after making a few minor hacks. For now, if you choose to do this, limited support will be provided, if any. Don't expect any alternatives to provide the same level of device integration and optimisation that Hildon provides.

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

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

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

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

Purism Librem5

2024-03-15T22:02:32Z

Sicelo: New device - Librem5

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

== Installation ==

[[Category:Device]]

Image Builder

2024-02-12T19:40:29Z

Sicelo: /* Maemo 7 Leste */

= How to build your own images =

== Maemo 7 Leste ==

'''[https://github.com/maemo-leste/image-builder Github]'''

1.) Install the following packages: <pre>debootstrap curl git wget qemu-user-static build-essential rsync gcc-arm-none-eabi gcc-multilib lib32z1 u-boot-tools device-tree-compiler lzop dosfstools vboot-utils vboot-kernel-utils libftdi-dev libfdt-dev swig libpython-dev bc bison flex libssl-dev zsh git</pre>

1.1) If you're using a distribution that is not Devuan, you will have to add a beowulf target to its scripts until the patch is merged upstream
<pre>
# wget -O /usr/share/debootstrap/scripts/ceres https://salsa.debian.org/installer-team/debootstrap/-/raw/e835c655006881af69de5476455ac0e7c824bcc4/scripts/ceres
# ln -s /usr/share/debootstrap/scripts/ceres /usr/share/debootstrap/scripts/chimaera
</pre>

2.) In your terminal, run the following commands:
$ git clone --recurse-submodules https://github.com/maemo-leste/image-builder.git
$ cd image-builder/arm-sdk
$ zsh -f
$ source sdk
$ load devuan DEVICE_NAME maemo
$ build_arm_dist

Note: replace <code>DEVICE_NAME</code> with your board name:

* n900
* n950
* n9
* droid4
* odroidxu
* odroidxu4
* ouya
* raspi1
* raspi2
* raspi3
* raspi4
* rock64
* pinephone-dontbeevil
* pinephone
* pinetab
* sunxi
* turbox-twister

Nokia N900

2023-09-04T09:45:14Z

Sicelo: /* 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 @850MHz
|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/WIP
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

Nokia N900 with Leste is stable using following scalable frequencies and is much, much faster:

250-500-600-720-850MHz

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:

<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 >;
};

opp6-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x02 >;
turbo-mode;
};
};</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:''' always use stock "Maemo Leste" in bootmenu before dist-upgrade / kernel update. (New uImageX must be created again and old uImageX must be removed))

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>

== Tips / Tweaks ==

=== SD Card ===

To avoid overall slowness, please only use SDHC Class 10 or better.

=== Social messaging ===

Conversations app is compatible with libpurple and irc/bitlbee server.

Twitter, Signal, Telegram, FB Messenger and others are working.

(most audio and video links are playable)

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

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: No

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

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

=== More SWAP ===

To create a simple swap file 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>

=== Web browsing ===

Links2 is currently the fastest and the most usable web browser on N900 -using few tweaks-

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

=== Retroarch ===

'''First things to do:'''

Edit <pre>/home/user/.config/retroarch/retroarch.cfg</pre>

menu_driver = "glui"

menu_show_core_updater = "true"

video_driver = "gl"

video_vsync = "true"

menu_unified_control = "true"

menu_core_enable = "true"

quick_menu_show_options = "true"

'''Some emulators are working well:
'''

- QuickNES (NES/Famicom)

- Snes9x 2005 (SNES/Super Famicom)

Others at 70-80% speed:

- Genesis Plus GX (SEGA MS/GG/MD/CD)

Go to Online Updater / Core Updater to download emulators

'''Retroarch recommended settings:'''

To avoid crashes, use only "glui" Menu Driver

'''Driver'''

Input driver "X", joypad driver "linuxraw", video driver "gl", audio driver "null", location driver "null"

'''Video'''

Aspect ratio "core provided", Integer scaler "no", Threaded Video "yes", Vertical Sync "yes", Hard gpu Sync "no",

'''Audio'''

Audio Enable "no"

'''Input''' (very important)

Unified Menu Controls "yes"

Input User 1 Binds (keyboard settings)

'''Directory''' (very important)

Core "/home/user"

'''Default keyboard keys'''

'''X''' validate/ok

'''C''' cancel/back

'''F''' fullscreen (never close Retroarch in fullscreen mode)

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.30 || 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
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), UCM support with Jack plug/unplug detection
|-
| 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 ofono and Conversations UI
|-
| Phone calls || Yes || Works well using ofono scripts, UCM support, some integration and bug fixing still remains with Sphone, sound is good. Works in 2G, 3G and 3.5G mode, low latency.
|-
| 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/WIP || TX only (hardware limitation). Works with specific dts parameters and pwm-ir-tx driver. Unstable
|-
| 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]]

Tweaking

2023-07-20T18:55:19Z

Sicelo: /* Switch clock display to 24h - no longer needed. UI supports */

Maemo Leste is very tweakable/hackable/versatile, this page lists some of the things you could change, hopefully grouped in a meaningful manner.

==== Prevent autoremoval of downloaded .deb files ====
The tool 'apt' as an alternative to apt-get uses different configuration.
To prevent apt from auto-deleting downloaded .deb packages do this:
<pre>echo 'Binary::apt::APT::Keep-Downloaded-Packages "true";' \ > /etc/apt/apt.conf.d/01keep-debs</pre>

===== GConf Settings =====

==== Show current gconf settings ====

<pre>gconftool-2 -R / |less</pre>
<pre>gconftool -S \* |less</pre>

==== Battery icon ====

You can change the animation of the charging icon to show the current charge capacity:
<pre>gconftool-2 -s /apps/osso/status-area-applet-battery/show_charge_charging -t bool true</pre> [edit] ''This doesn't do anything for me - clort''

==== Disable screen rotate ====

You can lock screen orientation to the current (disabling screen rotation) with
<pre>gconftool-2 -s /apps/osso/hildon-desktop/orientation_lock -t bool true</pre>

==== Prevent user rearranging of app menu ====

<pre>gconftool-2 -s /apps/osso/hildon-desktop/key-actions/disable_edit -t bool true</pre>

==== Hide toolbar at bottom of osso-xterm (to get more lines) ====

<pre>gconftool-2 -s /apps/osso/xterm/toolbar -t bool false</pre>

Virtual Machine

2023-07-20T18:54:00Z

Sicelo: /* VirtualBox */

{{Stub}}

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

Generic virtual machine target. This is particularly useful when doing development and testing.

== Installation ==

https://maedevu.maemo.org/images/virtual-machines/

There are three different types of images: VirtualBox (.box), QEMU (.qcow2, .vdi) and Vagrant. The VirtualBox image may be converted to a VMware VMDK image which has been reported to perform better and have good hardware acceleration.
Converting the qcow2 image to raw allows it to be used on real hardware.

=== VirtualBox ===

Download latest .vdi.xz image, unpack it with "xz -d" command.
Create new Virtual Machine, select "Debian (64-bit)" and 1024MB RAM. Use the downloaded file as virtual hard disk.
You are done!

==== Mouse ====

Since the UI is meant for touchscreens, it does not show the mouse by default. If it does not appear in the VM, you can change the Pointing Device to "USB Tablet" under "System > Motherboard" settings. Additionally, you may have to disable Virtualbox mouse integration

=== QEMU ===

In general something like:
qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024
should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].

To set up a port forward for SSH, add:
-nic user,hostfwd=tcp:127.0.0.1:7722-:22
And then log in like this (password: <code>toor</code>):
ssh root@localhost -p 7722

If the mouse pointer is grabbed and no cursor shows, you can add:
-usb -device usb-tablet
to the command line. Alternatively if that dose not work you can instead add:
-usb -device usb-mouse -machine vmport=off

If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:
sudo qemu-system-x86_64 -hda maemo-leste-1.0-amd64-virtual-20200324.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024 \
-nic user,hostfwd=tcp:127.0.0.1:7722-:22 \
-usb -device usb-ehci,id=ehci \
-device usb-host,bus=ehci.0,vendorid=0x0bdb,productid=0x193e

Or you can make a udev rule for your device. For example, with a Lenovo Ericsson N5321 gw you can create "/etc/udev/rules.d/45-n5321.rules" with this in it:
# Lenovo Ericsson N5321 gw simple udev rule
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bdb", ATTRS{idProduct}=="193e", \
MODE:="0666"

And then activate it by running these two commands as root:
# udevadm control --reload-rules
# udevadm trigger

Now you can run QEMU without the need for sudo!

=== virt-manager ===

Virt-manager can use multiple virtualisation backends via libvirt and its default is QEMU/KVM, allowing easy importing of the QEMU image.

The following tweaks need to be done when importing (before starting the instance) to ensure the qemu image works correctly.

* Change the disk driver from VirtIO to sata; there is an [https://github.com/maemo-leste/bugtracker/issues/291 outstanding bug] with how drives are mounted.
* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.
* Make sure you have a USB (not ps/2) mouse configured

When the screensaver kicks in, press the virt-manager power button to unlock.

== Initial configuration ==

On the first run you may want to generate ssh host keys and set the timezone. To do so open the "X Terminal" application and run:
sudo -i
dpkg-reconfigure openssh-server
dpkg-reconfigure tzdata

Make the system up-to-date:
apt update
apt upgrade
apt install linux-image-amd64
reboot

To get networking to work (at least in virtualbox), launch a shell and do
sudo ifconfig eth0 up
sudo dhclient eth0

A fresh Maemo VM image will also lock the device screen by default. In Qemu this means the only way to gain access to the VM again is either via SSH or by sending the power button command. This happens after 30 seconds of no activity on the device. We recommend disabling this behaviour by going to the settings and then open the "display" applet - uncheck "Lock screen automatically".

== Connectivity ==

If you have a modem exposed to QEMU, you still need to do some steps manually to get connectivity.

First off you need to add the development APT repository to your APT sources:
# echo 'deb https://maedevu.maemo.org/leste beowulf-devel main contrib non-free' >> /etc/apt/sources.list

Now update and upgrade:
# apt update && apt upgrade

Then you can install these things:
# apt install ofono libicd-network-ofono connui-iapsettings-gprs connui-statusbar-cellular connui-home-cellular connui-cellular-settings connui-conndlgs-cellular

We need mdbus2 to manipulate oFono:
# wget http://ftp.nl.debian.org/debian/pool/main/m/mdbus/mdbus2_2.3.3-2_amd64.deb
# dpkg -i mdbus2_2.3.3-2_amd64.deb

Then we can check if oFono finds our modem:
# mdbus2 -s org.ofono
/
/bluetooth
/bluetooth/profile
/bluetooth/profile/dun_gw
/bluetooth/profile/hfp_ag
/bluetooth/profile/hfp_hf
/mbm_0

Then can check our mbm_0 modem:
# mdbus2 -s org.ofono /mbm_0
[METHOD] org.freedesktop.DBus.Introspectable.Introspect() -> (s:xml)
[METHOD] org.ofono.Modem.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.Modem.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.Modem.PropertyChanged(s:name, v:value)

# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.GetProperties
({'Online': <false>, 'Powered': <false>, 'Lockdown': <false>, 'Emergency': <false>, 'SystemPath': <'/sys/devices/pci0000:00/0000:00:04.0/usb1/1-1'>, 'Interfaces': <@as []>, 'Features': <@as []>, 'Type': <'hardware'>},)

Power on the modem:
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.SetProperty Powered true
()
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.GetProperties
({'Online': <false>, 'Powered': <true>, 'Lockdown': <false>, 'Emergency': <false>, 'Manufacturer': <'Lenovo'>, 'Model': <'N5321 gw'>, 'Revision': <'R3C11'>, 'Serial': <'xxxxxxxxxxxx'>, 'SystemPath': <'/sys/devices/pci0000:00/0000:00:04.0/usb1/1-1'>, 'Interfaces': <['org.ofono.SimManager']>, 'Features': <['sim']>, 'Type': <'hardware'>},)

Check if we need to enter a pin:
# mdbus2 -s org.ofono /mbm_0 org.ofono.SimManager.GetProperties
({'Present': <true>, 'CardIdentifier': <'xxxxxx'>, 'FixedDialing': <false>, 'BarredDialing': <false>, 'SubscriberNumbers': <@as []>, 'LockedPins': <['pin']>, 'PreferredLanguages': <['de', 'en', 'fr']>, 'PinRequired': <'pin'>, 'Retries': <{'pin': byte 0x03, 'pin2': 0x03, 'puk': 0x0a, 'puk2': 0x0a}>, 'CardSlotCount': <uint32 1>, 'ActiveCardSlot': <uint32 1>},)

If PinRequired is 'pin' we need to enter a pin to unlock the sim:
# mdbus2 -s org.ofono /mbm_0 org.ofono.SimManager.EnterPin pin 1234
()

Then we can bring the modem online:
# mdbus2 -s org.ofono /mbm_0 org.ofono.Modem.SetProperty Online true
()

If we now redo the first mdbus2 command on /mbm_0:
# mdbus2 -s org.ofono /mbm_0
[METHOD] org.freedesktop.DBus.Introspectable.Introspect() -> (s:xml)
[METHOD] org.ofono.Modem.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.Modem.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.Modem.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.SimManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.SimManager.ChangePin(s:type, s:oldpin, s:newpin) -> ()
[METHOD] org.ofono.SimManager.EnterPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.ResetPin(s:type, s:puk, s:newpin) -> ()
[METHOD] org.ofono.SimManager.LockPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.UnlockPin(s:type, s:pin) -> ()
[METHOD] org.ofono.SimManager.GetIcon(y:id) -> (ay:icon)
[SIGNAL] org.ofono.SimManager.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.AllowedAccessPoints.GetAllowedAccessPoints() -> (as:apnlist)
[METHOD] org.ofono.SimAuthentication.GetApplications() -> (a{oa{sv}}:applications)
[METHOD] org.ofono.SimAuthentication.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimToolkit.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.SimToolkit.SelectItem(y:item, o:agent) -> ()
[METHOD] org.ofono.SimToolkit.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.SimToolkit.UnregisterAgent(o:path) -> ()
[SIGNAL] org.ofono.SimToolkit.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.RadioSettings.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.RadioSettings.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.RadioSettings.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.MessageManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.MessageManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.MessageManager.SendMessage(s:to, s:text) -> (o:path)
[METHOD] org.ofono.MessageManager.GetMessages() -> (a(oa{sv}):messages)
[SIGNAL] org.ofono.MessageManager.PropertyChanged(s:name, v:value)
[SIGNAL] org.ofono.MessageManager.IncomingMessage(s:message, a{sv}:info)
[SIGNAL] org.ofono.MessageManager.ImmediateMessage(s:message, a{sv}:info)
[SIGNAL] org.ofono.MessageManager.MessageAdded(o:path, a{sv}:properties)
[SIGNAL] org.ofono.MessageManager.MessageRemoved(o:path)
[METHOD] org.ofono.PushNotification.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.PushNotification.UnregisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.RegisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.UnregisterAgent(o:path) -> ()
[METHOD] org.ofono.SmartMessaging.SendBusinessCard(s:to, ay:card) -> (o:path)
[METHOD] org.ofono.SmartMessaging.SendAppointment(s:to, ay:appointment) -> (o:path)
[METHOD] org.ofono.LocationReporting.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.LocationReporting.Request() -> (h:fd)
[METHOD] org.ofono.LocationReporting.Release() -> ()
[SIGNAL] org.ofono.LocationReporting.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.SupplementaryServices.Initiate(s:command) -> (s:result_name, v:value)
[METHOD] org.ofono.SupplementaryServices.Respond(s:reply) -> (s:result)
[METHOD] org.ofono.SupplementaryServices.Cancel() -> ()
[METHOD] org.ofono.SupplementaryServices.GetProperties() -> (a{sv}:properties)
[SIGNAL] org.ofono.SupplementaryServices.NotificationReceived(s:message)
[SIGNAL] org.ofono.SupplementaryServices.RequestReceived(s:message)
[SIGNAL] org.ofono.SupplementaryServices.PropertyChanged(s:name, v:value)
[METHOD] org.ofono.CellBroadcast.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.CellBroadcast.SetProperty(s:property, v:value) -> ()
[SIGNAL] org.ofono.CellBroadcast.PropertyChanged(s:property, v:value)
[SIGNAL] org.ofono.CellBroadcast.IncomingBroadcast(s:message, q:channel)
[SIGNAL] org.ofono.CellBroadcast.EmergencyBroadcast(s:message, a{sv}:dict)
[METHOD] org.ofono.ConnectionManager.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.ConnectionManager.SetProperty(s:property, v:value) -> ()
[METHOD] org.ofono.ConnectionManager.AddContext(s:type) -> (o:path)
[METHOD] org.ofono.ConnectionManager.RemoveContext(o:path) -> ()
[METHOD] org.ofono.ConnectionManager.DeactivateAll() -> ()
[METHOD] org.ofono.ConnectionManager.GetContexts() -> (a(oa{sv}):contexts_with_properties)
[METHOD] org.ofono.ConnectionManager.ResetContexts() -> ()
[SIGNAL] org.ofono.ConnectionManager.PropertyChanged(s:name, v:value)
[SIGNAL] org.ofono.ConnectionManager.ContextAdded(o:path, a{sv}:properties)
[SIGNAL] org.ofono.ConnectionManager.ContextRemoved(o:path)
[METHOD] org.ofono.NetworkRegistration.GetProperties() -> (a{sv}:properties)
[METHOD] org.ofono.NetworkRegistration.Register() -> ()
[METHOD] org.ofono.NetworkRegistration.GetOperators() -> (a(oa{sv}):operators_with_properties)
[METHOD] org.ofono.NetworkRegistration.Scan() -> (a(oa{sv}):operators_with_properties)
[SIGNAL] org.ofono.NetworkRegistration.PropertyChanged(s:name, v:value)

[[Category:Device]]

Nokia N900

2023-04-10T21:34:08Z

Sicelo: /* 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
|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, no ucm, no speaker protection)
|sw_calls=WIP
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

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

Nokia N900 with Leste is stable using following scalable frequencies and is much, much faster:

250-500-600-720-850MHz

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:

<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 >;
};

opp6-720000000 {
opp-hz = < 0x00 0x2aea5400 >;
opp-microvolt = < 0x149970 0x149970 0x149970 >;
opp-supported-hw = < 0xffffffff 0x02 >;
turbo-mode;
};
};</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 5-18.9, your vmlinuz version is vmlinuz-5.18.9

In the next command, replace "vmlinuz-<version>" by yours (ie vmlinuz-5.18.9)

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

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>

== Tips / Tweaks ==

=== SD Card ===

To avoid overall slowness, please only use SDHC Class 10 or better.

=== Social messaging ===

Conversations app is compatible with libpurple and irc/bitlbee server.

Twitter, Signal, Telegram, FB Messenger and others are working.

(most audio and video links are playable)

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

Only unable Double buffering and Disable screensaver

- In Options / Preferences / Audio:

Output driver: pulse

Disable everything else

Channel by default: 2 (Stereo)

High speed playback: No

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

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

=== More SWAP ===

First method:

To create a simple swap file 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>

Second method:

To extand existing zswap you can install zram-tools from the repo, and edit <pre>/etc/default/zramswap</pre> as necessary. It's probably convenient to set allocation to 768 or 1024.

See Get Started Wiki.

=== Web browsing ===

Opera Mini 8 is a temporary solution.

To get it working, install openjdk from repo and microemulator-2.0.4 from the web (.jar)

Then from microemulator directory run:

<pre>java -jar microemulator-2.0.4.jar</pre>

On the main screen: / File / Open Midlet File and choose your Opera Mini jar file

Click Start (the first loading is quite long and an old Nokia smartphone will appear on the screen)

Once loaded and installed, click on resize button to fit to N900 screen.

(Be patient, first loading and settings are slow)

=== Retroarch ===

'''First thing to do:'''

Edit <pre>/home/user/.config/retroarch/retroarch.cfg</pre>

menu_driver = "glui"

menu_show_core_updater = "true"

video_driver = "gl"

video_vsync = "true"

menu_unified_control = "true"

menu_core_enable = "true"

quick_menu_show_options = "true"

'''Some emulators are working well:
'''

- QuickNES (NES/Famicom)

- Snes9x 2005 (SNES/Super Famicom)

Others at 70-80% speed:

- Genesis Plus GX (SEGA MS/GG/MD/CD)

Go to Online Updater / Core Updater to download emulators

'''Retroarch recommended settings:'''

To avoid crashes, use only "glui" Menu Driver

'''Driver'''

Input driver "X", joypad driver "linuxraw", video driver "gl", audio driver "null", location driver "null"

'''Video'''

Aspect ratio "core provided", Integer scaler "no", Threaded Video "yes", Vertical Sync "yes", Hard gpu Sync "no",

'''Audio'''

Audio Enable "no"

'''Input''' (very important)

Unified Menu Controls "yes"

Input User 1 Binds (keyboard settings)

'''Directory''' (very important)

Core "/home/user"

'''Default keyboard keys'''

'''X''' validate/ok

'''C''' cancel/back

'''F''' fullscreen (never close Retroarch in fullscreen mode)

== Status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 6.1.20 || 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
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G 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 ofono and Conversations UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes || Not really used in Leste at the moment, since UI rotation does not work
|-
| 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 || Broken || TX only (hardware limitation). Sending pulses causes a kernel oops
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~160mW / up to 30 hours || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Motorola Droid 4

2022-03-12T12:16:43Z

Sicelo: /* Torch = */

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

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

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

It may be necessary to run the follow commands as root in order to get the OK key to function correctly (see [https://github.com/maemo-leste/bugtracker/issues/510#issuecomment-815618591 here]):
udevadm hwdb --update
udevadm trigger

== Serial Cable ==

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

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

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

== Bluetooth ==

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

== Stuff to try ==

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

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

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

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

<pre>
15:04 < tmlind> Wizzup: i think the logo on droid4 can be flashed with fastboot flash logo logo.bin or something, can also be just written to logo partition from m-l
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
09:26 < xsetiadi> instead of flashing using command: fastboot flash logo.bin logo.bin i just flash it with command: fastboot flash logo logo.bin
</pre>

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

==== USSD ====

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

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

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

==== BT Audio headset ====

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

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

==== Torch ====

The Droid 4 has a TI LM3559 flash torch controller. This provides flash functionality when taking pictures, usage as a torch, and provides privacy indication (in this mode, the LED flashes in a fast heartbeat pattern). A driver for it exists in mainline, but it requires some DTS work, since it is tied to a camera device.

If you want to use it in the meantime, direct i2c access can be used as follows (since this is direct access, be careful about each of the commands below):

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

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

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

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

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

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

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

== Gallery ==

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

== Old status overview ==

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

[[Category:Device]]

Motorola Droid 4

2022-03-12T12:15:41Z

Sicelo: Removed manual modem/gps methods, wifi calibration, add torch

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

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

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

It may be necessary to run the follow commands as root in order to get the OK key to function correctly (see [https://github.com/maemo-leste/bugtracker/issues/510#issuecomment-815618591 here]):
udevadm hwdb --update
udevadm trigger

== Serial Cable ==

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

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

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

== Bluetooth ==

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

== Stuff to try ==

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

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

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

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

<pre>
15:04 < tmlind> Wizzup: i think the logo on droid4 can be flashed with fastboot flash logo logo.bin or something, can also be just written to logo partition from m-l
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
09:26 < xsetiadi> instead of flashing using command: fastboot flash logo.bin logo.bin i just flash it with command: fastboot flash logo logo.bin
</pre>

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

==== USSD ====

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

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

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

==== BT Audio headset ====

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

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

==== Torch =====

The Droid 4 has a TI LM3559 flash torch controller. This provides flash functionality when taking pictures, usage as a torch, and provides privacy indication (in this mode, the LED flashes in a fast heartbeat pattern). A driver for it exists in mainline, but it requires some DTS work, since it is tied to a camera device.

If you want to use it in the meantime, direct i2c access can be used as follows (since this is direct access, be careful about each of the commands below):

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

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

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

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

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

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

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

== Gallery ==

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

== Old status overview ==

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

[[Category:Device]]

Nokia N900

2022-03-12T11:52:21Z

Sicelo: /* Torch */

{{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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|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=300mW (needs kernel work)
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

=== 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 80mA, which is quite a lot. On a good battery this will last for about 15 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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Broken || TX only (hardware limitation). Sending pulses causes a kernel oops
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2022-03-12T11:42:58Z

Sicelo: /* Notes */

{{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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|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=300mW (needs kernel work)
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

=== 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 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 80mA, which is quite a lot. On a good battery this will last for about 15 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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Broken || TX only (hardware limitation). Sending pulses causes a kernel oops
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2022-02-27T15:24:44Z

Sicelo: /* Old 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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|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=300mW (needs kernel work)
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

=== 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 are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== 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 80mA, which is quite a lot. On a good battery this will last for about 15 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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.15 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Broken || TX only (hardware limitation). Sending pulses causes a kernel oops
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2022-02-27T15:24:03Z

Sicelo: /* Old 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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|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=300mW (needs kernel work)
|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:

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/

2. Download u-boot from https://maedevu.maemo.org/images/n900/tools/

3. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

4. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

=== 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 are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== 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 80mA, which is quite a lot. On a good battery this will last for about 15 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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Broken || TX only (hardware limitation). Sending pulses causes a kernel oops
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Motorola Droid 4

2022-01-07T15:06:21Z

Sicelo: /* Stuff to try */

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

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

=== Updating Android ===

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

=== Setting up kexecboot ===

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

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

It may be necessary to run the follow commands as root in order to get the OK key to function correctly (see [https://github.com/maemo-leste/bugtracker/issues/510#issuecomment-815618591 here]):
udevadm hwdb --update
udevadm trigger

== Serial Cable ==

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

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

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

== Bluetooth ==

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

== Stuff to try ==

==== Using a battery without built-in sensors ====

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

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

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

<pre>
15:04 < tmlind> Wizzup: i think the logo on droid4 can be flashed with fastboot flash logo logo.bin or something, can also be just written to logo partition from m-l
[snip]
09:24 < xsetiadi> https://github.com/xsetiadi/droid4-kexecboot/blob/master/logo.bin
09:25 < xsetiadi> becarefull, you can bootloop droid4 if you wrong flash partition
09:26 < xsetiadi> like i do last year
09:26 < xsetiadi> instead of flashing using command: fastboot flash logo.bin logo.bin i just flash it with command: fastboot flash logo logo.bin
</pre>

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

==== Wifi ====

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

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

==== Phone Call ====

These can be used to talk to the modem manually... But we really should have ofono and sphone GUI doing that job. [[Status/Phone]] mentions current status. Make sure there is a SIM in the phone.

Run this:

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

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

Connect to network:
<pre>
printf "AT+COPS=1\r" > /dev/motmdm1
</pre>

Print connected network:
</pre>
printf "AT+COPS?\r" > /dev/motmdm1

Turn off signal reporting:
<pre>
# printf "AT+SCRN=0\r" > /dev/motmdm1
</pre>

Dial a number:
<pre>
printf "ATD+1234567890\r" > /dev/motmdm1
</pre>

Hang up:
<pre>
printf "ATH\r" > /dev/motmdm1
</pre>

Answer incoming call:
<pre>
printf "ATA\r" > /dev/motmdm1
</pre>

Audio wise, in a pulsaudio of you choice switch to the make a phone call profile, and set the output device as desired.

==== 3G Internet ====

Using qmicli:

qmicli -d /dev/cdc-wdm0 --wds-follow-network --wds-start-network=apn=internet.t-mobile.cz
route del default
sudo ifconfig wwan0 up
dhclient wwan0

Alternatively if updated to devel icd2 and the maemo gui should allow 3g data connection, if the sim is unlocked and the relevant packages are installed.

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

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

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

==== USSD ====

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

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

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

==== BT Audio headset ====

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

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

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

A configured Droid4 Leste installation is unique to the device that it was calibrated on. Particularly the wlan firmware calibration will be incorrect if an existing Leste installation is transferred to a different device.

The wifi calibration script requires a system set to stock settings to calibrate-from. It cannot just be re-run on an already calibrated system.

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

== Gallery ==

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

== Old status overview ==

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

[[Category:Device]]

Getting Started

2021-06-16T16:23:20Z

Sicelo: Make cal issue clear

= Installation to SD Card =

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

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

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

Decompress and write the image to your microsd card device:

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

= Expand the root partition to fill SD card =

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

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

= (SSH) Login =

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

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

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

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

= Useful Bits =
== Lock Code (applies to N900 only) ==
* Default lockcode is "12345"
* Lockcode can only be changed/used on [[Nokia_N900|N900]], since the current implementation depends on a special "cal" partition. QEMU and all other Leste supported devices do not have it. (TODO: Confirm if N9 and N950 have it too)

= More RAM =

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

Remove it with:

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

= Tweaking =

See [[Tweaking]]

Nokia N900

2021-05-23T13:00:58Z

Sicelo:

{{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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|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=300mW (needs kernel work)
|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:

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Nokia N900

2021-05-23T12:51:06Z

Sicelo:

{{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
|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=5.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, no ucm, no speaker protection)
|sw_calls=WIP
|sw_sms=Yes, no UI
|sw_wifi=Yes, firmware required
|sw_ethernet=
|sw_irda=TX only
|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=300mW (needs kernel work)
|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:

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: <code>sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l</code>

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: <code>./0xFFFF -b</code>

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type <code>run sdboot</code>.

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

== Old status table ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

[[Category:Device]]

Development/Building Packages

2021-04-14T16:14:23Z

Sicelo: /* The git tag */

= Maintenance workflow =

Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.

Taking the https://github.com/maemo-leste/libcal/ package as an example - a valid repository contains at least two git branches:

# master
# maemo/beowulf

Ideally, the branches should have no difference, but sometimes this may vary.
Your git repository should contain your code, and a '''debian''' directory - which contains the debian package build logic.
The compat level of the package should be no less than '''9''' and preferably it should use '''debhelper'''.

Once you have your package ready and it builds locally on your Maemo Leste VM/device, there are just a couple more things to
do to make it ready for building on Jenkins:

== The git tag ==

In '''debian/changelog''' you should have your package version. It is very important to have a git tag that reflects this version
so Jenkins and jenkins-debian-glue can figure out which revision to build.

Keep in mind that the git tag should '''only''' contain the upstream version and no package revisions or epochs, for example if we have:

<code>libcal (0.3-2) unstable; urgency=medium</code>

Our git tag would be 0.3, and '''not''' 0.3-2

Once tagged, push the tag to git origin.

NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD, so there is no need to update the tag when changing the packaging (i.e. in debian directory). Tag shall be updated only when there are changes to the source files.

== gbp.conf ==

Your '''debian''' directory should contain a file called '''gbp.conf''' with the following contents:

<code>
[DEFAULT]

upstream-tag=%(version)s
</code>

Once all this is in place, make sure that you have a '''maemo/$codename''' branch containing all this ready and pushed.

= How you can build packages =

Building a packages is easier than one might think, it requires roughly the following steps:

#. Access to a Devuan/Debian system (you can use a [[Virtual_Machine|VM running Maemo Leste]] or a [[:Category:Device|Device running Maemo Leste]].
#. Source code of a package, obtain either via '''git''' or '''apt source <packagename>'''
#. Install build dependencies (run from source directory): '''sudo apt-get build-dep .'''
#. Build a package using '''dpkg-buildpackage -uc -b'''

You can now install the package you have just built with '''dpkg -i somename.deb'''

Also see: https://wiki.debian.org/HowToPackageForDebian

== Submitting changes ==

If you make changes to a package, please submit a pull request for the repository of that package, likely: https://github.com/maemo-leste/PACKAGENAME

For now, we will take care of updating tags and branches.

= How packages end up in the repository =

There are currently two repositories:

* The main repository: https://maedevu.maemo.org/leste
* The extras repository: https://maedevu.maemo.org/extras

The packages in the extras repository are not core, but useful applications nonetheless.

The codenames and an /etc/apt/sources.list file entry would look like the following:

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

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

Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup)

== How packages are built using Jenkins ==

Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)

All packages are hosted on https://github.com/maemo-leste and a current list of all the packages in Jenkins can be found here:

https://github.com/maemo-leste/jenkins-integration/blob/master/config.py

Every repository has a branch for each release, for example:

# maemo/beowulf - main branch for Devuan Beowulf target
# maemo/beowulf-devel - optional branch for Devuan Beowulf with unstable/testing version

See [[Development/Branches]] for more information on the usual branches flow.

= Maemo Leste Extras =

If you wish to maintain your own package in Maemo Leste, you can apply a package at https://github.com/maemo-leste-extras/bugtracker
Have a look at the README in that repository and open a ticket.

== Consideration for HAM ==
For packages built for extras to appear correctly in Hildon Application Manager, be aware that Maemo packaging system
included a few enhancements that HAM assumes. The most important one is that your application will '''only''' appear in HAM if the
<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through
<code>.desktop</code> files, while the former is done in <code>debian/control</code>.

== Adding an icon to the package in HAM ==

In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
Next, have your Build-Depends contain '''maemo-system-services-dev'''. maemo-system-services-dev will pull in the debhelper plugin.
Following this, in your '''debian/control''', under your '''Package''', add the following entry:

<pre>
XB-Maemo-Icon-26: ${maemo:icon26}
</pre>

And finally, in '''debian/rules''', assuming you're using debhelper, add this:

<pre>
override_dh_gencontrol:
dh_maemo_icon
dh_gencontrol
</pre>

Finally, if using quilt, add the icon in '''debian/source/include-binaries'''

<pre>$ echo debian/maemo-icon.png >> debian/source/include-binaries</pre>

Further reading: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections

Development/Building Packages

2021-04-14T16:02:25Z

Sicelo: /* The git tag */

= Maintenance workflow =

Each package in Maemo Leste uses a specific git-based workflow which makes it easy to track history and maintain in an easy way.

Taking the https://github.com/maemo-leste/libcal/ package as an example - a valid repository contains at least two git branches:

# master
# maemo/beowulf

Ideally, the branches should have no difference, but sometimes this may vary.
Your git repository should contain your code, and a '''debian''' directory - which contains the debian package build logic.
The compat level of the package should be no less than '''9''' and preferably it should use '''debhelper'''.

Once you have your package ready and it builds locally on your Maemo Leste VM/device, there are just a couple more things to
do to make it ready for building on Jenkins:

== The git tag ==

In '''debian/changelog''' you should have your package version. It is very important to have a git tag that reflects this version
so Jenkins and jenkins-debian-glue can figure out which revision to build.

Keep in mind that the git tag should '''only''' contain the upstream version and no package revisions or epochs, for example if we have:

<code>libcal (0.3-2) unstable; urgency=medium</code>

Our git tag would be 0.3, and '''not''' 0.3-2

Once tagged, push the tag to git origin.

NB: The tags are used to checkout the source code itself, the debian directory is always taken from git HEAD

== gbp.conf ==

Your '''debian''' directory should contain a file called '''gbp.conf''' with the following contents:

<code>
[DEFAULT]

upstream-tag=%(version)s
</code>

Once all this is in place, make sure that you have a '''maemo/$codename''' branch containing all this ready and pushed.

= How you can build packages =

Building a packages is easier than one might think, it requires roughly the following steps:

#. Access to a Devuan/Debian system (you can use a [[Virtual_Machine|VM running Maemo Leste]] or a [[:Category:Device|Device running Maemo Leste]].
#. Source code of a package, obtain either via '''git''' or '''apt source <packagename>'''
#. Install build dependencies (run from source directory): '''sudo apt-get build-dep .'''
#. Build a package using '''dpkg-buildpackage -uc -b'''

You can now install the package you have just built with '''dpkg -i somename.deb'''

Also see: https://wiki.debian.org/HowToPackageForDebian

== Submitting changes ==

If you make changes to a package, please submit a pull request for the repository of that package, likely: https://github.com/maemo-leste/PACKAGENAME

For now, we will take care of updating tags and branches.

= How packages end up in the repository =

There are currently two repositories:

* The main repository: https://maedevu.maemo.org/leste
* The extras repository: https://maedevu.maemo.org/extras

The packages in the extras repository are not core, but useful applications nonetheless.

The codenames and an /etc/apt/sources.list file entry would look like the following:

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

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

Packages in this repository get build by Jenkins, to which a select group of people has access. (Parazyd, Wizzup)

== How packages are built using Jenkins ==

Read only access to the http frontend: https://phoenix.maemo.org/ (write-access can be granted)

All packages are hosted on https://github.com/maemo-leste and a current list of all the packages in Jenkins can be found here:

https://github.com/maemo-leste/jenkins-integration/blob/master/config.py

Every repository has a branch for each release, for example:

# maemo/beowulf - main branch for Devuan Beowulf target
# maemo/beowulf-devel - optional branch for Devuan Beowulf with unstable/testing version

See [[Development/Branches]] for more information on the usual branches flow.

= Maemo Leste Extras =

If you wish to maintain your own package in Maemo Leste, you can apply a package at https://github.com/maemo-leste-extras/bugtracker
Have a look at the README in that repository and open a ticket.

== Consideration for HAM ==
For packages built for extras to appear correctly in Hildon Application Manager, be aware that Maemo packaging system
included a few enhancements that HAM assumes. The most important one is that your application will '''only''' appear in HAM if the
<code>debian/control</code> file has a correct <code>section</code> clause as explained on the [https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections|Maemo Packaging Wiki]. This wiki page also explains how to have HAM show your application's icon. Note that having an icon showing in HAM is a separate issue from having an icon show up in the application list (Hildon Home). The latter is done through
<code>.desktop</code> files, while the former is done in <code>debian/control</code>.

== Adding an icon to the package in HAM ==

In case you want to add an icon that is shown in HAM when listing the packages, we provide a debhelper plugin that can
handle this with a simple PNG file. In your package's debian directory, add your PNG icon as '''maemo-icon.png'''.
Next, have your Build-Depends contain '''maemo-system-services-dev'''. maemo-system-services-dev will pull in the debhelper plugin.
Following this, in your '''debian/control''', under your '''Package''', add the following entry:

<pre>
XB-Maemo-Icon-26: ${maemo:icon26}
</pre>

And finally, in '''debian/rules''', assuming you're using debhelper, add this:

<pre>
override_dh_gencontrol:
dh_maemo_icon
dh_gencontrol
</pre>

Finally, if using quilt, add the icon in '''debian/source/include-binaries'''

<pre>$ echo debian/maemo-icon.png >> debian/source/include-binaries</pre>

Further reading: https://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Packaging,_Deploying_and_Distributing#Sections

Packaging

2021-04-13T22:33:21Z

Sicelo: /* Workflow */

The packages we build for Maemo Leste are hosted on Github: https://github.com/maemo-leste

We use the Jenkins CI https://phoenix.maemo.org along with helper scripts that can be found at https://github.com/maemo-leste/jenkins-integration
The base logic of buildng Debian packages in Jenkins comes from https://jenkins-debian-glue.org

= Workflow =

Our workflow consists of having the packages in Git, along with respective branches.
The master branch in git should represent the latest development. When the sources are ready, we create a new branch called "maemo/ascii", which represents the Devuan suite we base it on.

Being git-based, our packages require the gbp.conf file inside the debian directory.

All of our packages contain the exact same gbp.conf, which is the following:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

This file is used by gbp, which in turn is used by jenkins-debian-glue.

The rest is standard Debian packaging.

= Initial packaging =

TODO

= Updating a package =

TODO

User:Sicelo/Snippets

2021-03-27T14:10:06Z

Sicelo:

Possible N900 USB host mode

echo 'force host full-speed' > /sys/kernel/debug/musb-hdrc.0.auto/testmode
echo host > /sys/bus/platform/devices/musb-hdrc.0.auto/mode
echo 1 > /sys/kernel/debug/musb-hdrc.0.auto/softconnect
echo disconnect > /sys/bus/platform/devices/musb-hdrc.0.auto/musb-hdrc.0.auto/soft_connect

Force N900 to stop charging while connected to power

echo off > /sys/class/power_supply/bq24150a-0/mode

N900 bluetooth

00:26 < sicelo> sre: hi. (this isn't too important compared to the task at hand, but) iirc getting N900 bluetooth working with mainline needed some serdev work. do you know what still
needs to be done?
00:28 < sre> enabling CONFIG_BT_HCIUART_NOKIA should give you a somewhat working bluetooth device. IIRC there were some issues that need to be debugged.

Application wishlist from Wizzup

<pre>
Maybe fun to port:

desktop:

battery-eye (in vm al)
catorise http://maemo.org/downloads/product/Maemo5/catorise/ (evt "Debian" category)
live wallpaper? http://maemo.org/downloads/product/Maemo5/live-wallpaper/
datetoday home widget http://maemo.org/downloads/product/Maemo5/datetoday-home-widget/
personal gprs monitor maemo.org/downloads/product/Maemo5/personal-gprs-mon/
humanity theme http://maemo.org/downloads/product/Maemo5/humanity-theme/
DONE personal ip address http://maemo.org/downloads/product/Maemo5/personal-ip-address/
custom operator name widget http://maemo.org/downloads/product/Maemo5/custom-operator-name-widget/
advanced clock http://maemo.org/downloads/product/Maemo5/advanced-clock-plugin/
app search widget http://maemo.org/downloads/product/Maemo5/app-search-widget/
qtlockscreen (?) and qtlockscreenconfig -- http://maemo.org/downloads/product/Maemo5/qtlockscreenconfig/
DONE http://maemo.org/downloads/product/Maemo5/miku-theme/

education:

dorian http://maemo.org/downloads/product/Maemo5/dorian/
evopedia http://maemo.org/downloads/product/Maemo5/evopedia/
e-book reader http://maemo.org/downloads/product/Maemo5/epubreader/
gtranslate? http://maemo.org/downloads/product/Maemo5/gtranslate/ - gtk/glib/espeak

games

smw - http://maemo.org/downloads/product/Maemo5/smw/
warmux - http://maemo.org/downloads/product/Maemo5/wormux/
battle gweled - http://maemo.org/downloads/product/Maemo5/battlegweled/
drnoksnes (!!!)
freecell4maemo ?
prboom
bullshit bingo http://maemo.org/downloads/product/Maemo5/bullshitbingo/
puzzles http://maemo.org/downloads/product/Maemo5/sgt-puzzles/
rocks n diamond shttp://maemo.org/downloads/product/Maemo5/rocksndiamonds/
uae4all goed laten werken
neverball - http://maemo.org/downloads/product/Maemo5/neverball/

graphics

mypaint (?)
raw viewer? http://maemo.org/downloads/product/Maemo5/mrawviewer/

multimedia

Boel coole/nuttige music players

qspot http://maemo.org/downloads/product/Maemo5/qspot/
recorder http://maemo.org/downloads/product/Maemo5/recorder/
qmidictl http://maemo.org/downloads/product/Maemo5/qmidictl/
maetronome http://maemo.org/downloads/product/Maemo5/maetronome/

location and navigation

modrana
marble? http://maemo.org/downloads/product/Maemo5/marble/
marble maps? http://maemo.org/downloads/product/Maemo5/marble-maps/
maep for sure http://maemo.org/downloads/product/Maemo5/maep/
gps track logger http://maemo.org/downloads/product/Maemo5/gps-data-logger/
OSM2Go - http://maemo.org/downloads/product/Maemo5/osm2go/
interessant http://maemo.org/downloads/product/Maemo5/snuggle/

internet and networking

google voice dialer written in Qt http://maemo.org/downloads/product/Maemo5/qgvdial/
meer google voice http://maemo.org/downloads/product/Maemo5/dialcentral/
twitter clienter http://maemo.org/downloads/product/Maemo5/khweeteur/
zoutube -- http://maemo.org/downloads/product/Maemo5/zoutube/
witter -- twitter client in python http://maemo.org/downloads/product/Maemo5/witter/
vncviewer -- http://maemo.org/downloads/product/Maemo5/vncviewer/
wifi eye http://maemo.org/downloads/product/Maemo5/wifieye/
qnetman -- http://maemo.org/downloads/product/Maemo5/qnetman/
xchat irc http://maemo.org/downloads/product/Maemo5/xchat/

office

xournal http://maemo.org/downloads/product/Maemo5/xournal/
quicknote http://maemo.org/downloads/product/Maemo5/quicknote/
mebook http://maemo.org/downloads/product/Maemo5/mebook/
portabase? http://maemo.org/downloads/product/Maemo5/portabase/

other

--

science

orrery -- http://maemo.org/downloads/product/Maemo5/orrery/
accdisplay http://maemo.org/downloads/product/Maemo5/accdisplay/

system

(lots of themes)

theme-customizer -- http://maemo.org/downloads/product/Maemo5/theme-customizer/
matrix theme -- http://maemo.org/downloads/product/Maemo5/matrix-pr12/
borg sounds -- http://maemo.org/downloads/product/Maemo5/borg-sounds/
okuda theme -- http://maemo.org/downloads/product/Maemo5/hildon-theme-okuda/
cellular modem control buttons -- http://maemo.org/downloads/product/Maemo5/cell-modem-ui/
qtlockscreen -- http://maemo.org/downloads/product/Maemo5/qtlockscreen/
maemeemo theme -- http://maemo.org/downloads/product/Maemo5/maemeemo-theme/

extra translations / languages
</pre>

Other stuff to do/test:
<pre>
- N900 flashlight
- WiFi direct (p2p) on N900 & Droid 4 - https://kasiviswanathanblog.wordpress.com/wifi-p2p-in-linux/
- WiFi monitor mode (N900 & Droid 4)
- WiFi hotspot (Droid 4)
</pre>

https://gavv.github.io/articles/pulseaudio-under-the-hood/ <-- might be handy for voice calls

IRC channel

2021-03-13T15:00:52Z

Sicelo: info for matrix users

We are on '''irc.freenode.net''' ; channel '''#maemo-leste'''

You can connect from your browser using the [https://webchat.freenode.net/ webchat]. However, a dedicated IRC client is recommended for long-term use.

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

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

Nokia N900

2021-01-29T16:19:23Z

Sicelo:

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 driver
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration and currently no ucm support
|-
| 2G/3G data || Yes || Works with ofono - UI is WIP, see https://github.com/maemo-leste/connui-cellular/
|-
| 4G data || N/A || no hardware
|-
| SMS || Yes || Works with ofono. Needs Leste UI
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, might require pulseaudio audio filters
|-
| Bluetooth || No || Driver needs some work
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No ||
|-
| Accelerometer || Yes ||
|-
| Compass || N/A || No hardware
|-
| Gyro || N/A|| No hardware
|-
| Proximity sensor || Yes || evdev interface not supported in mce
|-
| 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 || Works with gpsd but is not integrated yet, see [[#GPS|GPS]]
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || No || Needs complex v4l work, no leste integration
|-
| Idle power consumption || ~300mW || Device does not enter RET or OFF mode
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Nokia N900

2021-01-21T22:57:35Z

Sicelo: Make it clear that gpu driver isn't FOSS

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works, using proprietary PowerVR SGX blobs
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Development

2020-12-10T22:22:00Z

Sicelo: specify arch explicitly

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

== Communication and organising ==

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

== Task Summary ==

For current (semi) impactful tasks, see

[[Development/Tasks]]

== Codename ==

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

== Guides ==

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

== Technical ==

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

=== Jenkins ===

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

=== Developing on a device ===

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

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

=== Building a Maemo Leste image ===

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

=== 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 &&
sudo debootstrap --arch=armhf stretch $DIR http://deb.debian.org/debian &&
echo "strech_cross" | sudo tee $DIR/etc/debian_chroot &&
sudo systemd-nspawn --bind /usr/bin/qemu-arm-static -D $DIR

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

deb-src http://deb.debian.org/debian stretch main
deb-src http://maedevu.maemo.org/leste ascii main contrib non-free n900
deb-src http://maedevu.maemo.org/leste ascii-devel main contrib non-free n900
EOF
wget 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

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

Nokia N900

2020-11-27T21:23:22Z

Sicelo: /* Power Management */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

Power usage right now is reported to be about 80mA, which is quite a lot. On a good battery this will last for about 15 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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Nokia N900

2020-11-27T21:22:11Z

Sicelo: /* Notes */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Nokia N900

2020-11-27T21:21:57Z

Sicelo: /* Notes */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are possible concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

== Power Management ==

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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Nokia N900

2020-11-27T21:19:49Z

Sicelo: /* U-Boot setup */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

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

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

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

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are possible concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

Power usage right now is reported to be about 80mA, which is quite a lot, but on a good battery last for about 15 hours, this 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

== Power Management ==

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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

Nokia N900

2020-11-27T21:10:38Z

Sicelo: /* Status */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip and set frequency using: <code>v4l2-ctl -d /dev/radio0 -c mute=0,tune_power_level=120 -f <freq></code>
|-
| FM Receiver || No || [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

==== If you don't want to use/install Fremantle, or want to install quickly ====

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

To flash u-boot permanently, you can issue the following command '''(BE CAREFUL THOUGH, AS THIS WILL REPLACE THE EXISTING FREMANTLE KERNEL, ONLY DO THIS IF YOU DO NOT CARE ABOUT THE EXISTING MAEMO INSTALLATION)''':

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are possible concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

Power usage right now is reported to be about 80mA, which is quite a lot, but on a good battery last for about 15 hours, this 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

== Power Management ==

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.

This script can be used to decode idle states when this patch is applied: https://github.com/maemo-leste/n9xx-linux/blob/maemo/beowulf/debian/patches/0001_deeper_idle.patch

<pre>
$ cat idlest.py
"""
00001fff 48005020 (584be965) cm_idlest_per blocking bits: 0007e000
f7df3fb9 48004a20 (b32988a8) cm_idlest1_core blocking bits: 0020c046
0000000d 48004a28 (f7aa95e6) cm_idlest3_core
"""

# 31 to 0
cm_idlest1_core_bits = [
'RESERVED',
'ST_MMC3',
'ST_ICR',
'RESERVED',
'RESERVED',
'RESERVED',
'ST_MMC2',
'ST_MMC1',
'RESERVED',
'ST_HDQ',
'ST_MCSPI4',
'ST_MCSPI3',
'ST_MCSPI2',
'ST_MCSPI1',
'ST_I2C3',
'ST_I2C2',
'ST_I2C1',
'ST_UART2',
'ST_UART1',
'ST_GPT11',
'ST_GPT10',
'ST_MCBSP5',
'ST_MCBSP1',
'RESERVED',
'ST_MAILBOXES',
'ST_OMAPCTRL',
'ST_HSOTGUSB_IDLE',
'ST_HSOTGUSB_STDBY',
'RESERVED',
'ST_SDMA',
'ST_SDRC',
'RESERVED',
]

cm_idlest1_core_bits = list(reversed(cm_idlest1_core_bits))

#inp = '0020c046'
inp = '00208042' # after rmmod hci_nokia and hci_uart

v = int(inp, 16)

#print(v)
b= "{0:b}".format(v)
print((32-len(b))*'0' + b)

for i in range(0, 32):
is_set = (v & (1 << i)) >> i
if is_set:
print(cm_idlest1_core_bits[i])
</pre>

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

[[Category:Device]]

User:Sicelo/Snippets

2020-11-26T23:33:33Z

Sicelo: n900 bluetooth

Motorola Droid 4

2020-10-22T18:14:34Z

Sicelo: /* Updating */

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

== Status ==

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

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

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

== Notes ==

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

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

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

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

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

== Serial Cable ==

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

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

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

== Stuff to try ==

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

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

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

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

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

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

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

Connect to network:

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

Print connected network:

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

Not sure, do it anyway:

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

Dial a number:

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

Hang up:

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

Answer incoming call:

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

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

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

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

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

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

==== USSD ====

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

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
</gallery>

[[Category:Device]]

Calendar

2020-10-05T17:44:26Z

Sicelo:

= Calendar =

Data is stored in /home/user/.calendar/calendardb - in SQLite3 format.

== Qalendar ==

Qalendar is Qt5 implementation of the Maemo Calendar, source is here: https://github.com/maemo-leste/qalendar

It should mostly function as the Maemo calendar, see the feature comparison here: https://wiki.maemo.org/Qalendar

* cal-home-widget has also been ported

== Synchronising ==

(On maemo/beowulf-devel with a radicale server set up)

Install:

<pre>
apt install qalendar syncevolution
</pre>

Example URL is <pre>http://localhost:5223</pre> - using ssh tunneling to forward the remote radicale port to a local port. This is no by means required for operation - just pick any host that works for you.

For reference, this can be used to set up the ssh port forward if you're keen on using it (but again, just pick whatever host you want to use):

<pre>
ssh myhost -L 5223:localhost:5223
</pre>

OK, so let's configure syncevolution and do the initial sync:

<pre>
syncevolution --configure \
--template webdav \
username=USER \
password=PASS \
syncURL=http://localhost:5223/ \
target-config@radicale

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldavtodo \
target-config@radicale radicaletodo

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldavjournal \
target-config@radicale radicalejournal

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldav \
target-config@radicale radicalecal

syncevolution --configure \
--template SyncEvolution_Client \
sync=none \
syncURL=local://@radicale \
username= \
password= \
radicale

syncevolution --configure \
sync=two-way \
backend=maemo-tasks \
database= \
radicale radicaletodo

syncevolution --configure \
sync=two-way \
backend=maemo-notes\
database= \
radicale radicalejournal

syncevolution --configure \
sync=two-way \
backend=maemo-events \
database= \
radicale radicalecal

syncevolution --sync refresh-from-client radicale radicalejournal
syncevolution --sync refresh-from-client radicale radicaletodo
syncevolution --sync refresh-from-client radicale radicalecal
</pre>

And the next time you want to synchronise, just call:

<pre>
syncevolution --sync two-way radicale radicalecal
</pre>

== TODO ==

* port Syncevolution GUI

Random resources:

* https://www.mail-archive.com/syncevolution@syncevolution.org/msg03379.html
* https://wiki.maemo.org/Calendar_database
* https://wiki.maemo.org/Sync
* http://maemo.org/packages/source/view/fremantle_extras-devel_free_source/syncevolution-frontend/0.12/
* https://talk.maemo.org/showthread.php?t=75810

Calendar

2020-10-05T17:42:54Z

Sicelo: /* TODO */

= Calendar =

Data is stored in /home/user/.calendar/calendardb - in SQLite3 format.

== Qalendar ==

Qalendar is Qt5 implementation of the Maemo Calendar, source is here: https://github.com/maemo-leste/qalendar

It should mostly function as the Maemo calendar, see the feature comparison here: https://wiki.maemo.org/Qalendar

== Synchronising ==

(On maemo/beowulf-devel with a radicale server set up)

Install:

<pre>
apt install qalendar syncevolution
</pre>

Example URL is <pre>http://localhost:5223</pre> - using ssh tunneling to forward the remote radicale port to a local port. This is no by means required for operation - just pick any host that works for you.

For reference, this can be used to set up the ssh port forward if you're keen on using it (but again, just pick whatever host you want to use):

<pre>
ssh myhost -L 5223:localhost:5223
</pre>

OK, so let's configure syncevolution and do the initial sync:

<pre>
syncevolution --configure \
--template webdav \
username=USER \
password=PASS \
syncURL=http://localhost:5223/ \
target-config@radicale

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldavtodo \
target-config@radicale radicaletodo

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldavjournal \
target-config@radicale radicalejournal

syncevolution --configure \
database=http://localhost:5223/USER/UUID/ \
backend=caldav \
target-config@radicale radicalecal

syncevolution --configure \
--template SyncEvolution_Client \
sync=none \
syncURL=local://@radicale \
username= \
password= \
radicale

syncevolution --configure \
sync=two-way \
backend=maemo-tasks \
database= \
radicale radicaletodo

syncevolution --configure \
sync=two-way \
backend=maemo-notes\
database= \
radicale radicalejournal

syncevolution --configure \
sync=two-way \
backend=maemo-events \
database= \
radicale radicalecal

syncevolution --sync refresh-from-client radicale radicalejournal
syncevolution --sync refresh-from-client radicale radicaletodo
syncevolution --sync refresh-from-client radicale radicalecal
</pre>

And the next time you want to synchronise, just call:

<pre>
syncevolution --sync two-way radicale radicalecal
</pre>

* cal-home-widget has also been ported

== TODO ==

* port Syncevolution GUI

Random resources:

* https://www.mail-archive.com/syncevolution@syncevolution.org/msg03379.html
* https://wiki.maemo.org/Calendar_database
* https://wiki.maemo.org/Sync
* http://maemo.org/packages/source/view/fremantle_extras-devel_free_source/syncevolution-frontend/0.12/
* https://talk.maemo.org/showthread.php?t=75810

Development/Tasks

2020-08-16T10:44:46Z

Sicelo: /* Applications */

== Applications ==

This page lists some of the more important open issues for Maemo Leste. We have a complete list here, on github, but it's a bit hard to navigate: https://github.com/maemo-leste/bugtracker/issues

{| class="wikitable"
! Task
! Description
! Task Status
! User(s) working on task
! GH Bug
! URLs
! Notes
|-
| Monitor keyboard slide and attached state || Required on devices with a keyboard like [[Nokia_N900]] and [[Motorola_Droid_4]] to show specific parts of the virtual keyboard, or rotate || DONE || [[User:ThomasAH]], Spinal84 || https://github.com/maemo-leste/ke-recv/pull/2 ; https://github.com/maemo-leste/bugtracker/issues/17#issuecomment-528497018 || ke-recv part for slide monitoring is in place, we just need live keyboard-attached monitoring now. https://github.com/maemo-leste/mce/blob/master/event-input.c#L474 https://github.com/maemo-leste/ke-recv-extra/blob/master/src/input-device.c || mce has quite some usable code for this already, resulting code should probably go into ke-recv-extra (aka hulda). mer-core (sailfish/nemomobile) has keyboard monitoring integrated into mce, so we could also look at (using) that
|-
| Gtk3 port of theme and hildon widgets || Big task, port hildon widgets and theme from gtk2 to gtk3. Funding is available for this task || WIP/TODO || || https://github.com/maemo-leste/bugtracker/issues/261 || || Some work was done in the past
|-
| Qt5 of theme and hildon widgets || Big task, port hildon widgets and theme from qt4 to qt5. Funding is available for this task || WIP || [[User:freemangordon]] made a start, [[User:Wizzup]] picking up some of the work || || https://github.com/maemo-leste/qtstyleplugins/ || Mainly usable already!
|-
| Forward-port clutter patches from Nokia N900 clutter 0.8 to libclutter1.0 ? || *MAYBE* Required on devices with a PowerVR GPU like [[Nokia_N900]] and [[Motorola_Droid_4]] for hildon-desktop to work. In particular important for Droid 4 to get accelerated hildon-desktop || DONE (by staying at clutter 0.8) || || || https://github.com/spinal84/clutter-0.8/tree/blit/debian/patches ||
|-
| libicd-network-ofono should set up ipv4 (and ipv6) upon connect || Required to get usable cellular data. Provisioning is done, but the actual link itself is not yet set up. Once we have this, we should have usable cellular data on all devices with a supported modem. || TODO || || || ||
|-
| Extend ofono droid4 modem support || There is some ofono support in a branch, but it lacks a sim manager and some other interfaces required for maemo userspace || wIP || Tony, Pavel and [[User:Wizzup]] are working on this || || https://github.com/pavelmachek/ofono/commits/d4-v1.29 ||
|-
| Set up leste "extras" repository || A repository with non-core applications, games, etc would be very welcome || DONE || [[User:Wizzup]], [[User:Parazyd]] || || https://github.com/maemo-leste-extras ; https://maemo.org/downloads/score/Maemo5/25/ ||
|-
| Finish connui-cellular port to ofono || Porting of connui libraries, status and home applets, settings applets and pincode applets to ofono || WIP || [[User:Wizzup]] || https://github.com/maemo-leste/bugtracker/issues/256 || https://github.com/maemo-leste/connui-cellular ||
|-
| Test phone calls on the N900 || Figure out cmtspeechdata magic || WIP? || [[User:Wizzup]], [[User:Sicelo]], Pavel || || ||
|-
| Test phone calls on the droid4 || Phone calls should work, with audio, when alsamixer is set up properly, let's test it! || WORKS || [[User:Wizzup]], [[User:Sicelo]] || || ||
|-
| Create simple phone UI to test dialing/accepting phone calls using Telepathy || Would be good to test phone calls, can be simple/not-pretty, using telepathy is good, could be sip or real calls || WIP || ? || || ||
|-
|"hildonize" surf2 or create a simple "hildonized" gtk2 webkit browser || We'll need a basic browser. surf2 (in Debian) could be a good start, but the current package needs gtk3, and we only have a hildon (maemo ui) port for gtk2 right now. So let's make sure we can build something with webkit against gtk2. || WIP || [[User:Parazyd]] || || ||
|-
| Look at N900 power saving || We do not hit omap off modes nearly as much as we should (in fact, we never do), this should be looked at || WIP || [[User:Wizzup]], tmlind || || || Actually works quite well on the droid4. Let's do the same for Droid4. :)
|-
| osso-abook || We need osso-abook in place for all applications that need contacts (phone ui, sms ui, email ui, more) || WIP || [[User:freemangordon]] || ||https://github.com/maemo-leste/osso-abook || Making good progress
|-
| hildon-application-manager usable || We currently have HAM packaged, but it needs fixes for various compile issues we hacked around, cssu-specific parts need to be removed, and we need to figure out what we need to do for our repositories to make it work well || DONE || [[User:minicom]], [[User:Wizzup]], [[User:Parazyd]] || || || Goal is to have a usable app manager, so let's just use it, fix it, use it, etc.
|-
| Fix virtual keyboard rendering || On a screen that is not the same of the N900 (800x480), the virtual keyboard doesn't look very pretty. Lets just make it work on any display size || DONE || || || ||
|-
| Fix remaining hildon-desktop portait mode issues || The application launcher results in a black screen, and osso-xterm in portait mode is also resulting in a black screen || WIP? || [[User:freemangordon]] || || ||
|-
| Port all packages for maemo-leste to debhelper 9 or higher || Requires for us to migrate to a newer Debian (Buster) / Devuan (Beowulf) || DONE || [[User:Parazyd]], [[User:Wizzup]], [[User:meridion]], [[User:Spinal84]] || https://github.com/maemo-leste/bugtracker/issues/234 || ||
|-
|}

Motorola Droid 4

2020-08-16T10:30:51Z

Sicelo: /* Status */

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

== Status ==

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

== Installation ==

Hardware requirements:

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

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

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

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

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

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

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

Installation:

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

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

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

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

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

Now, flash the Maemo Leste image to your sdcard:

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

On Windows: Use Etcher

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

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

== Updating ==

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

== Notes ==

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

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

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

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

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

== Serial Cable ==

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

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

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

== Stuff to try ==

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

==== Make Audio Automaticaly set up (Temporary Solution) ====
Adding this in /etc/rc.local above the ''exit 0'' to make audio work from boot.
amixer cset numid=22 HiFi #set left speaker to HiFi
amixer cset numid=21 HiFi #set right speaker to HiFi
amixer cset numid=26 HiFi #set left headset to HiFi
amixer cset numid=25 HiFi #set right headset to HiFi
amixer cset numid=1 50% #set HiFi volumes to 50%

==== Wifi ====

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

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

==== Phone Call ====

Make sure there is a SIM in the phone.

Run this over SSH:

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

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

Connect to network:

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

Print connected network:

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

Not sure, do it anyway:

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

Dial a number:

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

Hang up:

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

Answer incoming call:

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

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

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

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

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

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

==== USSD ====

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

== Gallery ==

<gallery>
Motorola-Droid4-20200125.jpeg
Droid4-neofetch.JPG
Droid4_htop.jpg
Droid4_leste_logo.jpg
</gallery>

[[Category:Device]]

Nokia N900

2020-08-16T10:24:46Z

Sicelo: /* Status */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works fast(!)
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || Yes || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || Yes || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip 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 Bluetooth. [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

==== If you don't want to use/install Fremantle, or want to install quickly ====

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

To flash u-boot permanently, you can issue the following command '''(BE CAREFUL THOUGH, AS THIS WILL REPLACE THE EXISTING FREMANTLE KERNEL, ONLY DO THIS IF YOU DO NOT CARE ABOUT THE EXISTING MAEMO INSTALLATION)''':

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are possible concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

Power usage right now is reported to be about 80mA, which is quite a lot, but on a good battery last for about 15 hours, this 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

== Power Management ==

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.

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

[[Category:Device]]

Nokia N900

2020-08-16T10:21:46Z

Sicelo: /* Status */

{{Stub}}

{{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
|soc=TI OMAP 3430 @600MHz
|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=
}}

The Nokia N900.

== Status ==

{| class="wikitable"
! Feature
! Leste supported
! Notes
|-
| Kernel version || 5.1 || Mainline + PowerVR Patches: https://github.com/maemo-leste/n9xx-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 || Uses omapfb, not omapdrmfb yet
|-
| 3D Acceleration || Yes || Works fast(!)
|-
| Touchscreen || Yes || Resistive
|-
| Audio || Yes || Works (minus speaker protection), but requires complex alsa configuration
|-
| 2G/3G data || WIP || Works with ofono; UI under way: https://github.com/maemo-leste/connui-cellular ; see https://github.com/maemo-leste/bugtracker/issues/76
|-
| SMS || WIP || Works with ofono, will be implemented using telepathy-ring, no UI yet
|-
| Phone calls || WIP || Works, no UI, poor quality for upstream audio, not enabled by default (might require pulseaudio audio filters)
|-
| Bluetooth || No || Driver problems in mainline
|-
| FM Transmitter || Yes || Install <code>v4l-utils</code>, then enable chip 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 Bluetooth. [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/staging?id=757c2bf597a8e9f859f8efceda9c5108607fd98d Removed in Linux 5.4-rc1.]
|-
| Accelerometer || Yes || Available as input device, no integration yet. Needs MCE work
|-
| Compass || N/A || Missing in hardware
|-
| Proximity sensor || Yes || No integration yet
|-
| Ambient Light Sensor || Yes ||
|-
| Vibration Motor || Yes ||
|-
| HDMI-out || N/A || Missing in 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 || WIP || Works using gps3 and gpsd, needs integration still, and work on a-gps
|-
| Infrared || Yes || TX only (hardware limitation).
|-
| Camera || || Needs complex v4l work
|}

== 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] '''NB:''' Etcher does not warn you before starting the flashing operation, so please be extra careful that you choose the correct device to flash to

Then boot from the sd card using either 0xFFFF/flasher-3.5 or u-boot/bootmenu: http://talk.maemo.org/showthread.php?t=81613

=== U-Boot setup ===

==== If you don't want to use/install Fremantle, or want to install quickly ====

1. Download 0xFFFF and u-boot from https://maedevu.maemo.org/images/n900/tools/

2. Turn off Nokia N900, issue the following command on PC and connect Nokia N900 to the PC: '''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l'''

3. Open the keyboard slider on the N900, and then issue following command on PC to test boot: '''./0xFFFF -b'''

This should present u-boot from which you can select external SD card and boot to Maemo Leste. If you are presented with a menu, select the option to boot from External SD card. If you just get a command prompt, type '''run sdboot'''.

To flash u-boot permanently, you can issue the following command '''(BE CAREFUL THOUGH, AS THIS WILL REPLACE THE EXISTING FREMANTLE KERNEL, ONLY DO THIS IF YOU DO NOT CARE ABOUT THE EXISTING MAEMO INSTALLATION)''':

'''sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f'''

==== Existing Fremantle ====

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

=== Increase filesystem size ===
As of 2018/11, the latest pre-alpha image results in a 1.2GB root filesystem with about 100MB to spare. This can be extended, provided that your SD card is big enough.
Perform the following steps on a Linux machine with none of the SD card's partitions mounted:
* assumption: /dev/sda2 is Leste root partition
* e2fsck -f /dev/sda2
* use parted/gparted/cfdisk/... to enlarge /dev/sda2 to the desired size
* resize2fs -p /dev/sda2
* e2fsck -f /dev/sda2

The latest images have a script, <code>/etc/expandcard.sh</code> from https://github.com/maemo-leste/image-builder/blob/master/rootfs-overlay/common/etc/expandcard.sh

=== Serial ===

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

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

== Notes ==

* Speakers are enabled by default, but be careful of very high frequencies/levels - there are possible concerns regarding the possibility to blow them

Also see: https://elinux.org/N900

Power usage right now is reported to be about 80mA, which is quite a lot, but on a good battery last for about 15 hours, this 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

== Power Management ==

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.

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

[[Category:Device]]