Maemo Wiki Mirror - User contributions [en]

User:Jebba/Mer

2010-07-14T01:25:44Z

94.10.155.86: /* Disable watchdog */

=N900 Install=
Note, this is still in a *very* rough state. Currently, you can't recharge the battery while using Mer, nor even draw power when plugged in, so developing on it means you have to reboot just to recharge your battery. No phone calls are possible yet. Grabbing binaries of the proprietary crock from Nokia requires rebuilding packages and jumping through hoops. On the positive side, it boots. :)

You can do this without erasing your main install, FYI...

* [[Mer/Documentation/Installation|Mer installation]]

* [http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html More recent blog post about installing Mer 0.17testing10]

==Mer Image==
The latest release as of this post is 0.17testing4.

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# you need an ext3 formated MicroSD card.
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3/

wget http://stskeeps.subnetmask.net/mer/0.17testing4/mer-armel-generic-image-v0.17testing4.tar.gz

# Untar it verbosely to see the majick.
# Note this will create dirs like ./usr and ./lib etc, so you don't want stuff pre-existing in those dirs.
tar zxvf mer-armel-generic-image-v0.17testing4.tar.gz

# sync and live free!
sync

==bootmenu==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

You need to have getbootstate version 1.0.35+0m5 or greater for this to work.

dpkg -l getbootstate

(As a side note, [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate is closed software]. Please vote for this bug and/or clamour for it to be released as free software.)

* [http://talk.maemo.org/showpost.php?p=372885&postcount=22 discussion on t.m.o]

# Grab this package:
wget http://www.daimi.au.dk/~cvm/bootmenu_1.6_armel.deb

# Be root
sudo gainroot

# Install bootmenu
dpkg -i bootmenu_1.6_armel.deb

Then tappy tap tap the bootmenu install icon and answer yes.

Now you need to set up Mer in the menu for bootmenu. See also: [[Mer/Documentation/Bootmenu| Mer bootmenu docs]].

I put everything on the third partition on an ext3 formatted "external" MicroSD card (the one that's right next to the camera).

# edit/create this file to create a boot menu item for Mer:
vim /etc/bootmenu.d/mer.ext.item

# Make it look justa lika thisa:

ITEM_NAME="Mer (external SD, partition 3)"
ITEM_ID="mer"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"

(Note: why jbd module needed?)

Then shutoff the phone and reboot with KEYBOARD SLID OUT, so you get the bootmenu.

==Disable watchdog==

You have to disable the watchdog with the flasher tool or the system will just shut down on bootup:

./flasher-3.5 --set-rd-flags=no-omap-wd

./flasher-3.5 --set-rd-flags=no-ext-wd

./flasher-3.5 --enable-rd-mode
'''
''If you want to revert back and disbale R%D mode, do:
./flasher-3.5 --disable-rd-mode''

==0.17testing4 fixes for N900==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# root does all
sudo gainroot

# mount up the MicroSD
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3

===Missing dir needed at boot===
# create a missing directory
mkdir mnt/initfs

===Need modules from kernel===

# copy over modules from main OS:
cp -a /lib/modules/* /media/mmc3/lib/modules/

===Fix touchscreen===
I STILL DON'T HAVE THIS WORKING.

====auto-startx====
To get the touchscreen working you have to edit this file: /media/mmc3/etc/init.d/auto-startx. Patch it ala:

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

Note to self: I have a copy of this in /home/user/MyDocs/Mer, so when copying back over be sure to chmod because VFAT loses perms gah:

chmod +x /media/mmc3/etc/init.d/auto-startx

====remove synaptics driver====

sudo gainroot

chroot /media/mmc3 /bin/bash

dpkg --remove \
xserver-xorg-input-synaptics \
xserver-xorg-input-all

====Add xserver-xorg-input-tslib====

sudo gainroot

apt-get update

apt-get install xserver-xorg-input-tslib

===upgrade===
Note sure if it's needed, but:

chroot /media/mmc3 /bin/bash
apt-get update
apt-get upgrade

This got me new updates:
hildon-input-method libclutter-0.8-0 libetpan13 libhildon-im-ui3

The first one sounds helpful.

===Set root password===
Might as well set one in the chroot. I had X not come up once, but couldn't log in.

sudo gainroot
chroot /media/mmc3 /bin/bash
passwd

==Misc==
When you are booted up into Fremantle, it wouldn't hurt to fsck your MicroSD too....

umount /dev/mmcblk1p3 && fsck.ext3 -vvv /dev/mmcblk1p3

=Automated install=
Ok, here's dodgy scripts to automatically do lots of the above. I set these up because in the process of doing this I corrupted the filesystem on the MicroSD card enough times that I kept having to do this. If you don't understand what these scripts are doing, don't run them. Ah, and I use sudo lots, so you probably want do add this to /etc/sudoers:

user ALL = NOPASSWD: ALL

==freemoe-mer-install==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

#!/bin/sh

set -x

echo "this is going to format your microsd, take care!"

echo "EARLIER VERSIONS OF THIS SCRIPT USED PARTITION 1"
echo "IT IS NOW USING PARITION 3! BEWARE AND UPDATE YOUR SCRIPT AS NEEDED!"

read ok
read ok
exit 0 # you get this right?

echo

sudo umount /dev/mmcblk1p3

sudo mkfs.ext3 -j -m1 /dev/mmcblk1p3

sudo fsck -vvv /dev/mmcblk1p3

sudo mount -o noatime /dev/mmcblk1p3 /media/mmc3/

cd /media/mmc3/

sudo tar zxf /home/user/MyDocs/Mer/mer-armel-generic-image-v0.17testing4.tar.gz

sudo mkdir mnt/initfs

sudo cp -a /lib/modules/* /media/mmc3/lib/modules/

echo "WARNING WARNING WARNING!!!!"
echo "Copying over NON-FREE FIRMWARE"
echo "PAY PENANCE!!!!"
sudo cp -a /lib/firmware/* /media/mmc3/lib/firmware/

sudo patch -p0 < /home/user/MyDocs/Mer/auto-startx-n900.patch

# not needed
sudo chmod +x etc/init.d/auto-startx

sudo cp -p /home/user/MyDocs/Mer/mer-setup-in-chroot ./

sudo chmod +x mer-setup-in-chroot

#echo "add . to root's PATH to help with debugging"
#sudo cp -p /home/user/MyDocs/Mer/root-bashrc /media/mmc3/root/.bashrc

#echo "copy over some scripts to help with debug"
#sudo cp -p /home/user/MyDocs/Mer/root/* /media/mmc3/root/

#echo "WARNING: this leaves /root with less-than-optimal perms"
#sudo chmod -R +x /media/mmc3/root/

sudo cp -p /etc/apt/auth /media/mmc3/etc/apt/

sync

echo
echo "now run ./mer-setup-in-chroot after you enter the chroot"
echo "this is convenient too:"
echo "export HOME=/root"
echo

sudo chroot /media/mmc3 /bin/bash

==mer-setup-in-chroot==

#!/bin/sh

# run this chrooted

set -x

apt-get update

apt-get upgrade

apt-get remove xserver-xorg-input-synaptics xserver-xorg-input-all

apt-get install xserver-xorg-input-tslib

sync

==auto-startx-n900.patch==

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

=Installing Fremantle Packages=
Mer is missing some key parts, such as charging from battery and making phone calls. The first is killer, the second is a major drawback... Nokia decided to keep these parts proprietary which makes Mer on the N900 pretty pointless actually. Gar.

So I thought I would try to install (most begrudgingly) their proprietary Fremantle battery and cell phone applications under Mer. I was able to get the battery applet and some of the hal stuff going, but I don't think it was actually *doing* andything. I then installed the cell phone application, which pretty much screwed up the install.

So, in sum, the following doesn't work, but is a possible starting point for getting battery charging working under Mer.

I didn't have access to the original .debs, so I decided to just reconstruct them from the ones already installed under fremantle. It's a bit out there, but this is how I did it:

# boot into Mer

# We'll use dpkg-repack to rebuild the .debs
apt-get install dpkg-repack

# set up nice working space:
mkdir -p /mnt/fremantle

# umount the read/write of the NAND since we crash all the time and run out of battery
umount /mnt/initfs

# Remount it read-only some place nicer
mount -o ro -t ubifs ubi0:rootfs /mnt/fremantle/

# And put /home and the infamous /opt there too
mount -o ro /dev/mmcblk1p2 /mnt/fremantle/home/

# ...and MyDocs under that
mount -o ro /dev/mmcblk1p1 /mnt/fremantle/home/user/MyDocs/

# Set up stupid symlink for the /opt mess
cd /home
ln -s /mnt/fremantle/home/opt .

# create a nice place to put the .debs we'll create
mkdir /root/REPACKS

# go hence
cd /root/REPACKS

# take a look all those fremantle applications
dpkg -l --root=/mnt/fremantle/

# Repack some random single package
dpkg-repack --root=/mnt/fremantle/ burgerspace

# rebuild the local repo
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# Add this to /etc/apt/sources.list and perhaps comment out all the others
deb file:///root/REPACKS ./

# update from our new local repo
apt-get update

# and see that it works
apt-cache search burgerspace

# if that works, you can do them one at a time, or repack all of the
# fremantle debs with this:
for i in `dpkg -l --root=/mnt/fremantle/ |grep ii | cut -f 3 -d " "` ;
do echo $i
dpkg-repack --root=/mnt/fremantle/ $i
done

# Then re-run the archiverthinger
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# update
apt-get update

# now install whatever
apt-get install foo

# This will get you a battery applet. It appears in the notification
# area, but I'm not sure if it is working or not. Perhaps try rebooting
# after installing it, and don't install other stuff which may pooch it
apt-get install hald-addon-bme bme-rx-51 status-area-applet-battery

# After I installed this, I had a mess
apt-get install rtcom-call-ui

Oh, and I guess I should also point out, that all of this needs to be done because nokia is doing something funky with apt-transport-https. I tried rebuilding theirs and using it under Mer, but it barfed on libraries. I tried using the Ubuntu one but that didn't work with the Nokia repos, even after copying over /etc/apt/auth.

Another way to do this would perhaps be to apt-get mirror the repos, if possible or a --download-only type approach. I didn't have apt-transport-https working so I just did this. Time for bed.

=Build Packages=
Packages are built using OpenSUSE's Build Service

* [http://en.opensuse.org/Build_Service Build Service]

* [http://en.wikipedia.org/wiki/OpenSUSE_Build_Service wikipedia on OBS]

* [http://en.opensuse.org/Build_Service/Tutorial Build Service Tutorial]

* [http://forge.novell.com/modules/xfmod/project/?opensuse Build Service source]

* Sign up for account on OBS: jebbajeb

* [https://build.opensuse.org/]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer Maemo Community distribution (Maemo:Mer)]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer%3ADevel%3AHW%3AN900%3ADevel Development repository (Maemo:Mer:Devel:HW:N900:Devel)]

User:Jebba/Mer

2010-07-14T01:11:35Z

94.10.155.86: /* Disable watchdog */

=N900 Install=
Note, this is still in a *very* rough state. Currently, you can't recharge the battery while using Mer, nor even draw power when plugged in, so developing on it means you have to reboot just to recharge your battery. No phone calls are possible yet. Grabbing binaries of the proprietary crock from Nokia requires rebuilding packages and jumping through hoops. On the positive side, it boots. :)

You can do this without erasing your main install, FYI...

* [[Mer/Documentation/Installation|Mer installation]]

* [http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html More recent blog post about installing Mer 0.17testing10]

==Mer Image==
The latest release as of this post is 0.17testing4.

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# you need an ext3 formated MicroSD card.
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3/

wget http://stskeeps.subnetmask.net/mer/0.17testing4/mer-armel-generic-image-v0.17testing4.tar.gz

# Untar it verbosely to see the majick.
# Note this will create dirs like ./usr and ./lib etc, so you don't want stuff pre-existing in those dirs.
tar zxvf mer-armel-generic-image-v0.17testing4.tar.gz

# sync and live free!
sync

==bootmenu==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

You need to have getbootstate version 1.0.35+0m5 or greater for this to work.

dpkg -l getbootstate

(As a side note, [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate is closed software]. Please vote for this bug and/or clamour for it to be released as free software.)

* [http://talk.maemo.org/showpost.php?p=372885&postcount=22 discussion on t.m.o]

# Grab this package:
wget http://www.daimi.au.dk/~cvm/bootmenu_1.6_armel.deb

# Be root
sudo gainroot

# Install bootmenu
dpkg -i bootmenu_1.6_armel.deb

Then tappy tap tap the bootmenu install icon and answer yes.

Now you need to set up Mer in the menu for bootmenu. See also: [[Mer/Documentation/Bootmenu| Mer bootmenu docs]].

I put everything on the third partition on an ext3 formatted "external" MicroSD card (the one that's right next to the camera).

# edit/create this file to create a boot menu item for Mer:
vim /etc/bootmenu.d/mer.ext.item

# Make it look justa lika thisa:

ITEM_NAME="Mer (external SD, partition 3)"
ITEM_ID="mer"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"

(Note: why jbd module needed?)

Then shutoff the phone and reboot with KEYBOARD SLID OUT, so you get the bootmenu.

==Disable watchdog==

You have to disable the watchdog with the flasher tool or the system will just shut down on bootup:

./flasher-3.5 --set-rd-flags=no-omap-wd

./flasher-3.5 --set-rd-flags=no-ext-wd

./flasher-3.5 --enable-rd-mode
'''
(It should be mentioned how to undo the above aswell)'''

==0.17testing4 fixes for N900==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# root does all
sudo gainroot

# mount up the MicroSD
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3

===Missing dir needed at boot===
# create a missing directory
mkdir mnt/initfs

===Need modules from kernel===

# copy over modules from main OS:
cp -a /lib/modules/* /media/mmc3/lib/modules/

===Fix touchscreen===
I STILL DON'T HAVE THIS WORKING.

====auto-startx====
To get the touchscreen working you have to edit this file: /media/mmc3/etc/init.d/auto-startx. Patch it ala:

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

Note to self: I have a copy of this in /home/user/MyDocs/Mer, so when copying back over be sure to chmod because VFAT loses perms gah:

chmod +x /media/mmc3/etc/init.d/auto-startx

====remove synaptics driver====

sudo gainroot

chroot /media/mmc3 /bin/bash

dpkg --remove \
xserver-xorg-input-synaptics \
xserver-xorg-input-all

====Add xserver-xorg-input-tslib====

sudo gainroot

apt-get update

apt-get install xserver-xorg-input-tslib

===upgrade===
Note sure if it's needed, but:

chroot /media/mmc3 /bin/bash
apt-get update
apt-get upgrade

This got me new updates:
hildon-input-method libclutter-0.8-0 libetpan13 libhildon-im-ui3

The first one sounds helpful.

===Set root password===
Might as well set one in the chroot. I had X not come up once, but couldn't log in.

sudo gainroot
chroot /media/mmc3 /bin/bash
passwd

==Misc==
When you are booted up into Fremantle, it wouldn't hurt to fsck your MicroSD too....

umount /dev/mmcblk1p3 && fsck.ext3 -vvv /dev/mmcblk1p3

=Automated install=
Ok, here's dodgy scripts to automatically do lots of the above. I set these up because in the process of doing this I corrupted the filesystem on the MicroSD card enough times that I kept having to do this. If you don't understand what these scripts are doing, don't run them. Ah, and I use sudo lots, so you probably want do add this to /etc/sudoers:

user ALL = NOPASSWD: ALL

==freemoe-mer-install==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

#!/bin/sh

set -x

echo "this is going to format your microsd, take care!"

echo "EARLIER VERSIONS OF THIS SCRIPT USED PARTITION 1"
echo "IT IS NOW USING PARITION 3! BEWARE AND UPDATE YOUR SCRIPT AS NEEDED!"

read ok
read ok
exit 0 # you get this right?

echo

sudo umount /dev/mmcblk1p3

sudo mkfs.ext3 -j -m1 /dev/mmcblk1p3

sudo fsck -vvv /dev/mmcblk1p3

sudo mount -o noatime /dev/mmcblk1p3 /media/mmc3/

cd /media/mmc3/

sudo tar zxf /home/user/MyDocs/Mer/mer-armel-generic-image-v0.17testing4.tar.gz

sudo mkdir mnt/initfs

sudo cp -a /lib/modules/* /media/mmc3/lib/modules/

echo "WARNING WARNING WARNING!!!!"
echo "Copying over NON-FREE FIRMWARE"
echo "PAY PENANCE!!!!"
sudo cp -a /lib/firmware/* /media/mmc3/lib/firmware/

sudo patch -p0 < /home/user/MyDocs/Mer/auto-startx-n900.patch

# not needed
sudo chmod +x etc/init.d/auto-startx

sudo cp -p /home/user/MyDocs/Mer/mer-setup-in-chroot ./

sudo chmod +x mer-setup-in-chroot

#echo "add . to root's PATH to help with debugging"
#sudo cp -p /home/user/MyDocs/Mer/root-bashrc /media/mmc3/root/.bashrc

#echo "copy over some scripts to help with debug"
#sudo cp -p /home/user/MyDocs/Mer/root/* /media/mmc3/root/

#echo "WARNING: this leaves /root with less-than-optimal perms"
#sudo chmod -R +x /media/mmc3/root/

sudo cp -p /etc/apt/auth /media/mmc3/etc/apt/

sync

echo
echo "now run ./mer-setup-in-chroot after you enter the chroot"
echo "this is convenient too:"
echo "export HOME=/root"
echo

sudo chroot /media/mmc3 /bin/bash

==mer-setup-in-chroot==

#!/bin/sh

# run this chrooted

set -x

apt-get update

apt-get upgrade

apt-get remove xserver-xorg-input-synaptics xserver-xorg-input-all

apt-get install xserver-xorg-input-tslib

sync

==auto-startx-n900.patch==

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

=Installing Fremantle Packages=
Mer is missing some key parts, such as charging from battery and making phone calls. The first is killer, the second is a major drawback... Nokia decided to keep these parts proprietary which makes Mer on the N900 pretty pointless actually. Gar.

So I thought I would try to install (most begrudgingly) their proprietary Fremantle battery and cell phone applications under Mer. I was able to get the battery applet and some of the hal stuff going, but I don't think it was actually *doing* andything. I then installed the cell phone application, which pretty much screwed up the install.

So, in sum, the following doesn't work, but is a possible starting point for getting battery charging working under Mer.

I didn't have access to the original .debs, so I decided to just reconstruct them from the ones already installed under fremantle. It's a bit out there, but this is how I did it:

# boot into Mer

# We'll use dpkg-repack to rebuild the .debs
apt-get install dpkg-repack

# set up nice working space:
mkdir -p /mnt/fremantle

# umount the read/write of the NAND since we crash all the time and run out of battery
umount /mnt/initfs

# Remount it read-only some place nicer
mount -o ro -t ubifs ubi0:rootfs /mnt/fremantle/

# And put /home and the infamous /opt there too
mount -o ro /dev/mmcblk1p2 /mnt/fremantle/home/

# ...and MyDocs under that
mount -o ro /dev/mmcblk1p1 /mnt/fremantle/home/user/MyDocs/

# Set up stupid symlink for the /opt mess
cd /home
ln -s /mnt/fremantle/home/opt .

# create a nice place to put the .debs we'll create
mkdir /root/REPACKS

# go hence
cd /root/REPACKS

# take a look all those fremantle applications
dpkg -l --root=/mnt/fremantle/

# Repack some random single package
dpkg-repack --root=/mnt/fremantle/ burgerspace

# rebuild the local repo
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# Add this to /etc/apt/sources.list and perhaps comment out all the others
deb file:///root/REPACKS ./

# update from our new local repo
apt-get update

# and see that it works
apt-cache search burgerspace

# if that works, you can do them one at a time, or repack all of the
# fremantle debs with this:
for i in `dpkg -l --root=/mnt/fremantle/ |grep ii | cut -f 3 -d " "` ;
do echo $i
dpkg-repack --root=/mnt/fremantle/ $i
done

# Then re-run the archiverthinger
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# update
apt-get update

# now install whatever
apt-get install foo

# This will get you a battery applet. It appears in the notification
# area, but I'm not sure if it is working or not. Perhaps try rebooting
# after installing it, and don't install other stuff which may pooch it
apt-get install hald-addon-bme bme-rx-51 status-area-applet-battery

# After I installed this, I had a mess
apt-get install rtcom-call-ui

Oh, and I guess I should also point out, that all of this needs to be done because nokia is doing something funky with apt-transport-https. I tried rebuilding theirs and using it under Mer, but it barfed on libraries. I tried using the Ubuntu one but that didn't work with the Nokia repos, even after copying over /etc/apt/auth.

Another way to do this would perhaps be to apt-get mirror the repos, if possible or a --download-only type approach. I didn't have apt-transport-https working so I just did this. Time for bed.

=Build Packages=
Packages are built using OpenSUSE's Build Service

* [http://en.opensuse.org/Build_Service Build Service]

* [http://en.wikipedia.org/wiki/OpenSUSE_Build_Service wikipedia on OBS]

* [http://en.opensuse.org/Build_Service/Tutorial Build Service Tutorial]

* [http://forge.novell.com/modules/xfmod/project/?opensuse Build Service source]

* Sign up for account on OBS: jebbajeb

* [https://build.opensuse.org/]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer Maemo Community distribution (Maemo:Mer)]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer%3ADevel%3AHW%3AN900%3ADevel Development repository (Maemo:Mer:Devel:HW:N900:Devel)]

User:Jebba/Mer

2010-07-14T01:06:24Z

94.10.155.86: /* Disable watchdog */

=N900 Install=
Note, this is still in a *very* rough state. Currently, you can't recharge the battery while using Mer, nor even draw power when plugged in, so developing on it means you have to reboot just to recharge your battery. No phone calls are possible yet. Grabbing binaries of the proprietary crock from Nokia requires rebuilding packages and jumping through hoops. On the positive side, it boots. :)

You can do this without erasing your main install, FYI...

* [[Mer/Documentation/Installation|Mer installation]]

* [http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html More recent blog post about installing Mer 0.17testing10]

==Mer Image==
The latest release as of this post is 0.17testing4.

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# you need an ext3 formated MicroSD card.
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3/

wget http://stskeeps.subnetmask.net/mer/0.17testing4/mer-armel-generic-image-v0.17testing4.tar.gz

# Untar it verbosely to see the majick.
# Note this will create dirs like ./usr and ./lib etc, so you don't want stuff pre-existing in those dirs.
tar zxvf mer-armel-generic-image-v0.17testing4.tar.gz

# sync and live free!
sync

==bootmenu==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

You need to have getbootstate version 1.0.35+0m5 or greater for this to work.

dpkg -l getbootstate

(As a side note, [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate is closed software]. Please vote for this bug and/or clamour for it to be released as free software.)

* [http://talk.maemo.org/showpost.php?p=372885&postcount=22 discussion on t.m.o]

# Grab this package:
wget http://www.daimi.au.dk/~cvm/bootmenu_1.6_armel.deb

# Be root
sudo gainroot

# Install bootmenu
dpkg -i bootmenu_1.6_armel.deb

Then tappy tap tap the bootmenu install icon and answer yes.

Now you need to set up Mer in the menu for bootmenu. See also: [[Mer/Documentation/Bootmenu| Mer bootmenu docs]].

I put everything on the third partition on an ext3 formatted "external" MicroSD card (the one that's right next to the camera).

# edit/create this file to create a boot menu item for Mer:
vim /etc/bootmenu.d/mer.ext.item

# Make it look justa lika thisa:

ITEM_NAME="Mer (external SD, partition 3)"
ITEM_ID="mer"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"

(Note: why jbd module needed?)

Then shutoff the phone and reboot with KEYBOARD SLID OUT, so you get the bootmenu.

==Disable watchdog==

You have to disable the watchdog with the flasher tool or the system will just shut down on bootup:

./flasher-3.5 --set-rd-flags=no-omap-wd

./flasher-3.5 --set-rd-flags=no-ext-wd

./flasher-3.5 --enable-rd-mode

(It should be mentioned how to undo the above aswell)

==0.17testing4 fixes for N900==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# root does all
sudo gainroot

# mount up the MicroSD
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3

===Missing dir needed at boot===
# create a missing directory
mkdir mnt/initfs

===Need modules from kernel===

# copy over modules from main OS:
cp -a /lib/modules/* /media/mmc3/lib/modules/

===Fix touchscreen===
I STILL DON'T HAVE THIS WORKING.

====auto-startx====
To get the touchscreen working you have to edit this file: /media/mmc3/etc/init.d/auto-startx. Patch it ala:

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

Note to self: I have a copy of this in /home/user/MyDocs/Mer, so when copying back over be sure to chmod because VFAT loses perms gah:

chmod +x /media/mmc3/etc/init.d/auto-startx

====remove synaptics driver====

sudo gainroot

chroot /media/mmc3 /bin/bash

dpkg --remove \
xserver-xorg-input-synaptics \
xserver-xorg-input-all

====Add xserver-xorg-input-tslib====

sudo gainroot

apt-get update

apt-get install xserver-xorg-input-tslib

===upgrade===
Note sure if it's needed, but:

chroot /media/mmc3 /bin/bash
apt-get update
apt-get upgrade

This got me new updates:
hildon-input-method libclutter-0.8-0 libetpan13 libhildon-im-ui3

The first one sounds helpful.

===Set root password===
Might as well set one in the chroot. I had X not come up once, but couldn't log in.

sudo gainroot
chroot /media/mmc3 /bin/bash
passwd

==Misc==
When you are booted up into Fremantle, it wouldn't hurt to fsck your MicroSD too....

umount /dev/mmcblk1p3 && fsck.ext3 -vvv /dev/mmcblk1p3

=Automated install=
Ok, here's dodgy scripts to automatically do lots of the above. I set these up because in the process of doing this I corrupted the filesystem on the MicroSD card enough times that I kept having to do this. If you don't understand what these scripts are doing, don't run them. Ah, and I use sudo lots, so you probably want do add this to /etc/sudoers:

user ALL = NOPASSWD: ALL

==freemoe-mer-install==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

#!/bin/sh

set -x

echo "this is going to format your microsd, take care!"

echo "EARLIER VERSIONS OF THIS SCRIPT USED PARTITION 1"
echo "IT IS NOW USING PARITION 3! BEWARE AND UPDATE YOUR SCRIPT AS NEEDED!"

read ok
read ok
exit 0 # you get this right?

echo

sudo umount /dev/mmcblk1p3

sudo mkfs.ext3 -j -m1 /dev/mmcblk1p3

sudo fsck -vvv /dev/mmcblk1p3

sudo mount -o noatime /dev/mmcblk1p3 /media/mmc3/

cd /media/mmc3/

sudo tar zxf /home/user/MyDocs/Mer/mer-armel-generic-image-v0.17testing4.tar.gz

sudo mkdir mnt/initfs

sudo cp -a /lib/modules/* /media/mmc3/lib/modules/

echo "WARNING WARNING WARNING!!!!"
echo "Copying over NON-FREE FIRMWARE"
echo "PAY PENANCE!!!!"
sudo cp -a /lib/firmware/* /media/mmc3/lib/firmware/

sudo patch -p0 < /home/user/MyDocs/Mer/auto-startx-n900.patch

# not needed
sudo chmod +x etc/init.d/auto-startx

sudo cp -p /home/user/MyDocs/Mer/mer-setup-in-chroot ./

sudo chmod +x mer-setup-in-chroot

#echo "add . to root's PATH to help with debugging"
#sudo cp -p /home/user/MyDocs/Mer/root-bashrc /media/mmc3/root/.bashrc

#echo "copy over some scripts to help with debug"
#sudo cp -p /home/user/MyDocs/Mer/root/* /media/mmc3/root/

#echo "WARNING: this leaves /root with less-than-optimal perms"
#sudo chmod -R +x /media/mmc3/root/

sudo cp -p /etc/apt/auth /media/mmc3/etc/apt/

sync

echo
echo "now run ./mer-setup-in-chroot after you enter the chroot"
echo "this is convenient too:"
echo "export HOME=/root"
echo

sudo chroot /media/mmc3 /bin/bash

==mer-setup-in-chroot==

#!/bin/sh

# run this chrooted

set -x

apt-get update

apt-get upgrade

apt-get remove xserver-xorg-input-synaptics xserver-xorg-input-all

apt-get install xserver-xorg-input-tslib

sync

==auto-startx-n900.patch==

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

=Installing Fremantle Packages=
Mer is missing some key parts, such as charging from battery and making phone calls. The first is killer, the second is a major drawback... Nokia decided to keep these parts proprietary which makes Mer on the N900 pretty pointless actually. Gar.

So I thought I would try to install (most begrudgingly) their proprietary Fremantle battery and cell phone applications under Mer. I was able to get the battery applet and some of the hal stuff going, but I don't think it was actually *doing* andything. I then installed the cell phone application, which pretty much screwed up the install.

So, in sum, the following doesn't work, but is a possible starting point for getting battery charging working under Mer.

I didn't have access to the original .debs, so I decided to just reconstruct them from the ones already installed under fremantle. It's a bit out there, but this is how I did it:

# boot into Mer

# We'll use dpkg-repack to rebuild the .debs
apt-get install dpkg-repack

# set up nice working space:
mkdir -p /mnt/fremantle

# umount the read/write of the NAND since we crash all the time and run out of battery
umount /mnt/initfs

# Remount it read-only some place nicer
mount -o ro -t ubifs ubi0:rootfs /mnt/fremantle/

# And put /home and the infamous /opt there too
mount -o ro /dev/mmcblk1p2 /mnt/fremantle/home/

# ...and MyDocs under that
mount -o ro /dev/mmcblk1p1 /mnt/fremantle/home/user/MyDocs/

# Set up stupid symlink for the /opt mess
cd /home
ln -s /mnt/fremantle/home/opt .

# create a nice place to put the .debs we'll create
mkdir /root/REPACKS

# go hence
cd /root/REPACKS

# take a look all those fremantle applications
dpkg -l --root=/mnt/fremantle/

# Repack some random single package
dpkg-repack --root=/mnt/fremantle/ burgerspace

# rebuild the local repo
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# Add this to /etc/apt/sources.list and perhaps comment out all the others
deb file:///root/REPACKS ./

# update from our new local repo
apt-get update

# and see that it works
apt-cache search burgerspace

# if that works, you can do them one at a time, or repack all of the
# fremantle debs with this:
for i in `dpkg -l --root=/mnt/fremantle/ |grep ii | cut -f 3 -d " "` ;
do echo $i
dpkg-repack --root=/mnt/fremantle/ $i
done

# Then re-run the archiverthinger
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# update
apt-get update

# now install whatever
apt-get install foo

# This will get you a battery applet. It appears in the notification
# area, but I'm not sure if it is working or not. Perhaps try rebooting
# after installing it, and don't install other stuff which may pooch it
apt-get install hald-addon-bme bme-rx-51 status-area-applet-battery

# After I installed this, I had a mess
apt-get install rtcom-call-ui

Oh, and I guess I should also point out, that all of this needs to be done because nokia is doing something funky with apt-transport-https. I tried rebuilding theirs and using it under Mer, but it barfed on libraries. I tried using the Ubuntu one but that didn't work with the Nokia repos, even after copying over /etc/apt/auth.

Another way to do this would perhaps be to apt-get mirror the repos, if possible or a --download-only type approach. I didn't have apt-transport-https working so I just did this. Time for bed.

=Build Packages=
Packages are built using OpenSUSE's Build Service

* [http://en.opensuse.org/Build_Service Build Service]

* [http://en.wikipedia.org/wiki/OpenSUSE_Build_Service wikipedia on OBS]

* [http://en.opensuse.org/Build_Service/Tutorial Build Service Tutorial]

* [http://forge.novell.com/modules/xfmod/project/?opensuse Build Service source]

* Sign up for account on OBS: jebbajeb

* [https://build.opensuse.org/]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer Maemo Community distribution (Maemo:Mer)]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer%3ADevel%3AHW%3AN900%3ADevel Development repository (Maemo:Mer:Devel:HW:N900:Devel)]

User:Jebba/Mer

2010-07-14T01:06:06Z

94.10.155.86: /* Disable watchdog */

=N900 Install=
Note, this is still in a *very* rough state. Currently, you can't recharge the battery while using Mer, nor even draw power when plugged in, so developing on it means you have to reboot just to recharge your battery. No phone calls are possible yet. Grabbing binaries of the proprietary crock from Nokia requires rebuilding packages and jumping through hoops. On the positive side, it boots. :)

You can do this without erasing your main install, FYI...

* [[Mer/Documentation/Installation|Mer installation]]

* [http://mer-project.blogspot.com/2010/01/dual-booting-mer-on-nokia-n900.html More recent blog post about installing Mer 0.17testing10]

==Mer Image==
The latest release as of this post is 0.17testing4.

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# you need an ext3 formated MicroSD card.
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3/

wget http://stskeeps.subnetmask.net/mer/0.17testing4/mer-armel-generic-image-v0.17testing4.tar.gz

# Untar it verbosely to see the majick.
# Note this will create dirs like ./usr and ./lib etc, so you don't want stuff pre-existing in those dirs.
tar zxvf mer-armel-generic-image-v0.17testing4.tar.gz

# sync and live free!
sync

==bootmenu==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

You need to have getbootstate version 1.0.35+0m5 or greater for this to work.

dpkg -l getbootstate

(As a side note, [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate is closed software]. Please vote for this bug and/or clamour for it to be released as free software.)

* [http://talk.maemo.org/showpost.php?p=372885&postcount=22 discussion on t.m.o]

# Grab this package:
wget http://www.daimi.au.dk/~cvm/bootmenu_1.6_armel.deb

# Be root
sudo gainroot

# Install bootmenu
dpkg -i bootmenu_1.6_armel.deb

Then tappy tap tap the bootmenu install icon and answer yes.

Now you need to set up Mer in the menu for bootmenu. See also: [[Mer/Documentation/Bootmenu| Mer bootmenu docs]].

I put everything on the third partition on an ext3 formatted "external" MicroSD card (the one that's right next to the camera).

# edit/create this file to create a boot menu item for Mer:
vim /etc/bootmenu.d/mer.ext.item

# Make it look justa lika thisa:

ITEM_NAME="Mer (external SD, partition 3)"
ITEM_ID="mer"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"

(Note: why jbd module needed?)

Then shutoff the phone and reboot with KEYBOARD SLID OUT, so you get the bootmenu.

==Disable watchdog==

You have to disable the watchdog with the flasher tool or the system will just shut down on bootup:

./flasher-3.5 --set-rd-flags=no-omap-wd

./flasher-3.5 --set-rd-flags=no-ext-wd

./flasher-3.5 --enable-rd-mode

(It should be mentioned how to undo the following aswell)

==0.17testing4 fixes for N900==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

# root does all
sudo gainroot

# mount up the MicroSD
mount -o noatime /dev/mmcblk1p3 /media/mmc3/

# go hence
cd /media/mmc3

===Missing dir needed at boot===
# create a missing directory
mkdir mnt/initfs

===Need modules from kernel===

# copy over modules from main OS:
cp -a /lib/modules/* /media/mmc3/lib/modules/

===Fix touchscreen===
I STILL DON'T HAVE THIS WORKING.

====auto-startx====
To get the touchscreen working you have to edit this file: /media/mmc3/etc/init.d/auto-startx. Patch it ala:

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

Note to self: I have a copy of this in /home/user/MyDocs/Mer, so when copying back over be sure to chmod because VFAT loses perms gah:

chmod +x /media/mmc3/etc/init.d/auto-startx

====remove synaptics driver====

sudo gainroot

chroot /media/mmc3 /bin/bash

dpkg --remove \
xserver-xorg-input-synaptics \
xserver-xorg-input-all

====Add xserver-xorg-input-tslib====

sudo gainroot

apt-get update

apt-get install xserver-xorg-input-tslib

===upgrade===
Note sure if it's needed, but:

chroot /media/mmc3 /bin/bash
apt-get update
apt-get upgrade

This got me new updates:
hildon-input-method libclutter-0.8-0 libetpan13 libhildon-im-ui3

The first one sounds helpful.

===Set root password===
Might as well set one in the chroot. I had X not come up once, but couldn't log in.

sudo gainroot
chroot /media/mmc3 /bin/bash
passwd

==Misc==
When you are booted up into Fremantle, it wouldn't hurt to fsck your MicroSD too....

umount /dev/mmcblk1p3 && fsck.ext3 -vvv /dev/mmcblk1p3

=Automated install=
Ok, here's dodgy scripts to automatically do lots of the above. I set these up because in the process of doing this I corrupted the filesystem on the MicroSD card enough times that I kept having to do this. If you don't understand what these scripts are doing, don't run them. Ah, and I use sudo lots, so you probably want do add this to /etc/sudoers:

user ALL = NOPASSWD: ALL

==freemoe-mer-install==

'''NOTE: Earlier versions of this "howto" used partition 1. I now have everything on partition 3!!!! Update your scripts as needed!'''

#!/bin/sh

set -x

echo "this is going to format your microsd, take care!"

echo "EARLIER VERSIONS OF THIS SCRIPT USED PARTITION 1"
echo "IT IS NOW USING PARITION 3! BEWARE AND UPDATE YOUR SCRIPT AS NEEDED!"

read ok
read ok
exit 0 # you get this right?

echo

sudo umount /dev/mmcblk1p3

sudo mkfs.ext3 -j -m1 /dev/mmcblk1p3

sudo fsck -vvv /dev/mmcblk1p3

sudo mount -o noatime /dev/mmcblk1p3 /media/mmc3/

cd /media/mmc3/

sudo tar zxf /home/user/MyDocs/Mer/mer-armel-generic-image-v0.17testing4.tar.gz

sudo mkdir mnt/initfs

sudo cp -a /lib/modules/* /media/mmc3/lib/modules/

echo "WARNING WARNING WARNING!!!!"
echo "Copying over NON-FREE FIRMWARE"
echo "PAY PENANCE!!!!"
sudo cp -a /lib/firmware/* /media/mmc3/lib/firmware/

sudo patch -p0 < /home/user/MyDocs/Mer/auto-startx-n900.patch

# not needed
sudo chmod +x etc/init.d/auto-startx

sudo cp -p /home/user/MyDocs/Mer/mer-setup-in-chroot ./

sudo chmod +x mer-setup-in-chroot

#echo "add . to root's PATH to help with debugging"
#sudo cp -p /home/user/MyDocs/Mer/root-bashrc /media/mmc3/root/.bashrc

#echo "copy over some scripts to help with debug"
#sudo cp -p /home/user/MyDocs/Mer/root/* /media/mmc3/root/

#echo "WARNING: this leaves /root with less-than-optimal perms"
#sudo chmod -R +x /media/mmc3/root/

sudo cp -p /etc/apt/auth /media/mmc3/etc/apt/

sync

echo
echo "now run ./mer-setup-in-chroot after you enter the chroot"
echo "this is convenient too:"
echo "export HOME=/root"
echo

sudo chroot /media/mmc3 /bin/bash

==mer-setup-in-chroot==

#!/bin/sh

# run this chrooted

set -x

apt-get update

apt-get upgrade

apt-get remove xserver-xorg-input-synaptics xserver-xorg-input-all

apt-get install xserver-xorg-input-tslib

sync

==auto-startx-n900.patch==

--- etc/init.d/auto-startx.orig 2009-10-20 12:39:30.000000000 -0300
+++ etc/init.d/auto-startx 2009-12-31 13:46:06.000000000 -0300
@@ -8,6 +8,7 @@
start)
if [ ! -f /etc/default/autologin ] ; then
if [ -x /usr/sbin/first-boot-wizard.sh ] ; then
+ TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate
/usr/bin/xinit /usr/sbin/first-boot-wizard.sh 2>&1 > /var/log/first-boot-wizard.log
else
echo -n "No user specified for auto login. Creating..."

=Installing Fremantle Packages=
Mer is missing some key parts, such as charging from battery and making phone calls. The first is killer, the second is a major drawback... Nokia decided to keep these parts proprietary which makes Mer on the N900 pretty pointless actually. Gar.

So I thought I would try to install (most begrudgingly) their proprietary Fremantle battery and cell phone applications under Mer. I was able to get the battery applet and some of the hal stuff going, but I don't think it was actually *doing* andything. I then installed the cell phone application, which pretty much screwed up the install.

So, in sum, the following doesn't work, but is a possible starting point for getting battery charging working under Mer.

I didn't have access to the original .debs, so I decided to just reconstruct them from the ones already installed under fremantle. It's a bit out there, but this is how I did it:

# boot into Mer

# We'll use dpkg-repack to rebuild the .debs
apt-get install dpkg-repack

# set up nice working space:
mkdir -p /mnt/fremantle

# umount the read/write of the NAND since we crash all the time and run out of battery
umount /mnt/initfs

# Remount it read-only some place nicer
mount -o ro -t ubifs ubi0:rootfs /mnt/fremantle/

# And put /home and the infamous /opt there too
mount -o ro /dev/mmcblk1p2 /mnt/fremantle/home/

# ...and MyDocs under that
mount -o ro /dev/mmcblk1p1 /mnt/fremantle/home/user/MyDocs/

# Set up stupid symlink for the /opt mess
cd /home
ln -s /mnt/fremantle/home/opt .

# create a nice place to put the .debs we'll create
mkdir /root/REPACKS

# go hence
cd /root/REPACKS

# take a look all those fremantle applications
dpkg -l --root=/mnt/fremantle/

# Repack some random single package
dpkg-repack --root=/mnt/fremantle/ burgerspace

# rebuild the local repo
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# Add this to /etc/apt/sources.list and perhaps comment out all the others
deb file:///root/REPACKS ./

# update from our new local repo
apt-get update

# and see that it works
apt-cache search burgerspace

# if that works, you can do them one at a time, or repack all of the
# fremantle debs with this:
for i in `dpkg -l --root=/mnt/fremantle/ |grep ii | cut -f 3 -d " "` ;
do echo $i
dpkg-repack --root=/mnt/fremantle/ $i
done

# Then re-run the archiverthinger
cd /root/REPACKS
dpkg-scanpackages . /dev/null | gzip -9c > Packages.gz

# update
apt-get update

# now install whatever
apt-get install foo

# This will get you a battery applet. It appears in the notification
# area, but I'm not sure if it is working or not. Perhaps try rebooting
# after installing it, and don't install other stuff which may pooch it
apt-get install hald-addon-bme bme-rx-51 status-area-applet-battery

# After I installed this, I had a mess
apt-get install rtcom-call-ui

Oh, and I guess I should also point out, that all of this needs to be done because nokia is doing something funky with apt-transport-https. I tried rebuilding theirs and using it under Mer, but it barfed on libraries. I tried using the Ubuntu one but that didn't work with the Nokia repos, even after copying over /etc/apt/auth.

Another way to do this would perhaps be to apt-get mirror the repos, if possible or a --download-only type approach. I didn't have apt-transport-https working so I just did this. Time for bed.

=Build Packages=
Packages are built using OpenSUSE's Build Service

* [http://en.opensuse.org/Build_Service Build Service]

* [http://en.wikipedia.org/wiki/OpenSUSE_Build_Service wikipedia on OBS]

* [http://en.opensuse.org/Build_Service/Tutorial Build Service Tutorial]

* [http://forge.novell.com/modules/xfmod/project/?opensuse Build Service source]

* Sign up for account on OBS: jebbajeb

* [https://build.opensuse.org/]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer Maemo Community distribution (Maemo:Mer)]

* [https://build.opensuse.org/project/show?project=Maemo%3AMer%3ADevel%3AHW%3AN900%3ADevel Development repository (Maemo:Mer:Devel:HW:N900:Devel)]

User:Jebba/Fedora

2010-07-14T00:14:57Z

94.10.155.86: /* freemoe-fedora-install */ Notice to change partition numbers in script.

I have installed Fedora 12 on my Nokia N900.

[[Image:N900-fedora-f12.jpg|left|thumb|alt=Jebba's N900 Fedora 12|Fedora 12 on N900]]

Screen reads:

Fedora release 12 (Constantine)
Kernel 2.6.28-omap1-jebba5 on an arm7l (tty1)

fedora-arm login: _

=HOWTO Install Fedora 12 on Nokia N900=
It boots up happily. No GUI, no phonecalls, no battery charging support, etc. Wifi works. Testing xorg RSN.

==Kernel==
You will need to install a kernel that has a framebuffer console. You can use your own or use mine. See: [[User:Jebba/Kernel#Installing_my_custom_kernel | Installing my custom kernel]] if you would like to use mine. Version 2.6.28-omap1-jebba5 is known to "work".

==bootmenu==
You need to have getbootstate version 1.0.35+0m5 or greater for this to work. These docs are basically the same as installing [[User:Jebba/Mer | Mer]].

dpkg -l getbootstate

(As a side note, [https://bugs.maemo.org/show_bug.cgi?id=7019 getbootstate is closed software]. Please vote for this bug and/or clamour for it to be released as free software.)

* [http://talk.maemo.org/showpost.php?p=372885&postcount=22 discussion on t.m.o]

I have four partitions on my MicroSD card. The first one is 100M of VFAT just to shut up fremantle. The second is 1G of swap. The third is 7G of space for fremantle. The remaining space is around 7G of space for Fedora. You can install it in far less space, but I have a 16G card, so that's what I did. These docs assume you use my partitioning.

# Boot up into Maemo / Fremantle

# Grab this package:
wget http://www.daimi.au.dk/~cvm/bootmenu_1.6_armel.deb

# Be root
sudo gainroot

# Install bootmenu
dpkg -i bootmenu_1.6_armel.deb

Then tappy tap tap the bootmenu install icon and answer yes.

Now you need to set up Fedora in the menu for bootmenu. See also: [[Mer/Documentation/Bootmenu| Mer bootmenu docs]].

I put everything on the forth partition on an ext3 formatted "external" MicroSD card (the one that's right next to the camera).

# edit/create this file to create a boot menu item for Fedora:
vim /etc/bootmenu.d/fedora.ext.item

# Make it look justa lika thisa:

ITEM_NAME="Fedora 12 (external SD, partition 4)"
ITEM_ID="fedora"
ITEM_DEVICE="${EXT_CARD}p4"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,rw"

Then shutoff the phone and reboot with KEYBOARD SLID OUT, so you get the bootmenu.

==rootfs==

Boot into your system like "normal" into Maemo fremantle.

Set up and download the needed files:

# This will be a nice place to keep things
mkdir -p /home/user/MyDocs/Fedora/rootfs

# go hence
cd /home/user/MyDocs/Fedora/rootfs

# grab the root image
wget http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/rootfs-f12.tar.bz2

===fedora-setup-in-chroot===
Make this file and put it here:
/home/user/MyDocs/Fedora/fedora-setup-in-chroot

Note, in future revisions, I will have more in this script, this is just a starting point for now.

#!/bin/sh

set -x

echo "uh, set a root password!"
passwd

===freemoe-fedora-install===
Make & run this script; adjust the partition numbers to match your own setup.

#!/bin/sh

set -x

echo "this is going to format your microsd, take care!"

echo "THIS FORMATS PARTITION 4 ON YOUR MICROSD"

read ok
read ok
exit 0 # you get this i hope

echo

sudo umount /dev/mmcblk1p4

sudo mkfs.ext3 -j -m1 /dev/mmcblk1p4

sudo fsck -vvv /dev/mmcblk1p4

sudo mkdir -p /media/mmc4

sudo mount -o noatime /dev/mmcblk1p4 /media/mmc4/

cd /media/mmc4/

bzcat /home/user/MyDocs/Fedora/rootfs/rootfs-f12.tar.bz2 | sudo tar x

sudo mv rootfs-f12/* .
sudo rmdir rootfs-f12

sudo cp -a /lib/modules/* /media/mmc4/lib/modules/

echo "WARNING WARNING WARNING!!!!"
echo "Copying over NON-FREE FIRMWARE"
echo "PAY PENANCE!!!!"
sudo cp -a /lib/firmware/* /media/mmc4/lib/firmware/

sudo cp -p /home/user/MyDocs/Fedora/fedora-setup-in-chroot ./

sudo chmod +x fedora-setup-in-chroot

sync

echo
echo "now run ./fedora-setup-in-chroot after you enter the chroot"
echo "this is convenient too:"
echo "export HOME=/root"
echo

sudo chroot /media/mmc4 /bin/bash

==Disable watchdog==
You have to disable the watchdog with the flasher tool or the system will just shut down on bootup:

./flasher-3.5 --set-rd-flags=no-omap-wd

./flasher-3.5 --set-rd-flags=no-ext-wd

./flasher-3.5 --enable-rd-mode

=Wifi=

You'll also need to add "." to root's PATH or put that somewhere it root's PATH.

[root@fedora-arm ~]# tail -1 /root/.bashrc

Here's a crufty crappy script to get wifi and net:

# cat wlanon
#!/bin/sh

WLAN=`iwconfig |grep wlan | cut -f 1 -d " "`
echo "$WLAN"

ifconfig $WLAN down
sleep 1
iwconfig $WLAN mode managed
sleep 1
ifconfig $WLAN up
sleep 1
iwconfig $WLAN essid consume
sleep 1
ifconfig $WLAN 10.0.0.3 netmask 255.255.255.0 up

iwconfig $WLAN
sleep 2
ifconfig $WLAN

route add default gw 10.0.0.2

==OLD==

(Will add this to script later)

I got wifi going by writing a simple script that I can run at boot. Can't use many of the keys, so no "0", "/" etc. I used iwconfig which I yum installed in the chroot, but this could easily be done with the more modern "iw" which comes installed.

[root@fedora-arm ~]# cat startiwconfig
#!/bin/sh

iwconfig wlan0 essid consume
dhclient wlan0

PATH=$PATH:.

# cat /etc/sysconfig/network-scripts/ifcfg-wlan0
# WLAN Interface
DEVICE=wlan0
#HWADDR=00:00:00:00:00:00
ONBOOT=no
BOOTPROTO=dhcp
TYPE=Wireless
NM_CONTROLLED=no
USERCTL=yes
PEERDNS=yes
IPV6INIT=no
#MODE=Master
RATE=auto
ESSID=consume
CHANNEL=

Note: I had wifi working fine, then I installed a bunch of apps and network config broke and can't find the device anymore. :(

Note 2: If you reboot without powering off or perhaps yanking the battery, your device may appear as wlan2 or wlan3 etc.

=X.org=
X is up and running with XFCE & openbox. I have the touchscreen working. I can do touchscreen calibration.

# as root, I did this via ssh when networking was working
yum groupinstall Base-X

# grab a desktop. No openbox or lxde available at the moment for ARM.
yum groupinstall XFCE

# Screen config.
yum install tslib xorg-x11-apps

# fix /etc/hosts to this so XFCE doesn't complain:
127.0.0.1 localhost localhost.localdomain fedora-arm

# since keyboard isn't working you have to set up this script from
# chroot or ssh in:
echo "TSLIB_TSDEVICE=/dev/input/event3 TSLIB_CONFFILE=/etc/ts.conf ts_calibrate" > /root/ts
chmod +x /root/ts

# then next time you boot up, log in as root and run "ts" to calibrate.

# Uncomment this line in /etc/ts.conf:
module_raw input

=Misc=

In a chroot I wanted to do a `yum update` and installs. Did a `mount -a` and needed to create a device:

cd /dev
MAKEDEV urandom

yum update
yum install wireless-tools openssh-clients git

route add default gw 192.168.1.1

* disable /etc/sysconfig/network-scripts/ifcfg-eth0

* Have lame network startup script run at boot.

* stop startup stuff

chkconfig abrtd off
chkconfig auditd off
chkconfig ip6tables off
chkconfig iptables off
chkconfig netconsole off
chkconfig netfs off
chkconfig restorecond off

* Build tools:

yum groupinstall --skip-broken "Development Tools"

yum install -y vim-enhanced file gqview xorg-x11-apps xterm

* Auto login, edit /etc/gdm/custom.conf
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=jebba

* Edit /etc/inittab to set default runlevel to 5.

To get X pointer and keyboard working:

* Mount up Maemo root partition:

mkdir -p /mnt/maemo
mount -t ubifs ubi0:rootfs /mnt/maemo

* /usr/share/hal/fdi/* stuff from maemo to get touchscreen working in X. Copy it to /etc/hal/...

* Copy over xkb stuff to get numbers etc from keyboard working:

mv /usr/share/X11/xkb /usr/share/X11/xkb.f12
cp -a /mnt/maemo/usr/share/X11/xkb /usr/share/X11/xkb

* ofono

yum -y install glib2-devel dbus-devel libudev-devel

To initialize modem, you need to run this non-free command:

/mnt/initfs/sbin/phonet -a 0x6C -i phonet0
ifconfig phonet0 up # or:
ip link set dev phonet0 up

* misc misc misc

yum -y install openbox rxvt-unicode alsa-utils sox

=Battery?=
Copying over the script from Mer to get the battery working appears to run, not certain how it is working yet.

cp -p /mnt/mer/etc/init.d/n900-support /etc/init.d/
# edit n900-support, adding this line:
# chkconfig: - 58 74
chkconfig --level 35 n900-support on

=watchdog=
To disable R&D mode, try this:

yum -y install watchdog
wget http://atorkhov.fedorapeople.org/n900_wd-1-1.noarch.rpm
rpm -Uvh n900_wd-1-1.noarch.rpm

==kludge up symlinks==

chroot /mnt/initfs/
ln -s /f12/tmp/bme-dbus-socket /tmp/bme-dbus-socket

Outside chroot:
ln -s /mnt/initfs/tmp/dsmesock /tmp/
sudo ln -s /mnt/initfs/tmp/.bmesrv /tmp/

cp -p /mnt/initfs/usr/lib/libbmeipc.so.0 /usr/lib
cp -p /mnt/initfs/usr/lib/hal/hald-addon-bme /usr/libexec/hald-addon-bme
cp -p /mnt/initfs/usr/share/hal/fdi/policy/10osvendor/10-bme.fdi /etc/hal/fdi/policy/10osvendor/

==watchdog other==
Here's some scripts that I got from somewhere, i think another fedora/n900 user. :) It is another way to disable the watchdog without having to enter R&D mode.

===n900_wd===
#!/bin/sh
#
# chkconfig: 12345 01 99
# description: N900 watchdog kicker
#

# Source function library.
. /etc/rc.d/init.d/functions

[ -x /usr/sbin/wd_keepalive ] || exit 0

RETVAL=0
prog=wd_keepalive
pidfile=/var/run/wd_keepalive.pid
lockfile=/var/lock/subsys/n900_wd

start() {
echo -n $"Starting $prog: "
/usr/sbin/${prog} -c /etc/watchdog-omap.conf
RETVAL=$?
[ $RETVAL -ne 0 ] && (echo_failure; echo; return $RETVAL)
/usr/sbin/${prog} -c /etc/watchdog-twl4030.conf
RETVAL=$?
[ $RETVAL -eq 0 ] && touch $lockfile
[ $RETVAL -eq 0 ] && echo_success
[ $RETVAL -ne 0 ] && echo_failure
echo
return $RETVAL
}

stop() {
rm -f $lockfile $pidfile
}

case "$1" in
start)
start
;;
stop)
stop
;;
status)
status $prog
RETVAL=$?
;;
*)
echo $"Usage: $0 {start|status}"
exit 1
esac

===watchdog-twl4030.conf===

watchdog-device = /dev/twl4030_wdt
interval = 10
realtime = yes
priority = 1

===watchdog-omap.conf===

watchdog-device = /dev/watchdog
interval = 10
realtime = yes
priority = 1

=See also=

* [http://talk.maemo.org/showthread.php?t=38987 Thread about Fedora 12 on talk.maemo.org]

* [http://fedoraproject.org/wiki/Architectures/ARM ARM at Fedora wiki]

* [http://fedora-arm.blogspot.com/ Fedora ARM blog]

* [https://www.redhat.com/archives/fedora-arm/ Fedora ARM mailing list archives]

* [https://bugzilla.redhat.com/show_bug.cgi?id=ARMTracker Fedora ARM bug tracker]

* [http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/?C=M;O=D Fedora ARM roots]

* [[User:Jebba/Mer | My docs on installing Mer, which is similar procedure]]

* [http://alexeytorkhov.blogspot.com/2010/02/running-fedora-arm-on-nokia-n900.html Another N900/Fedora user]

Customizing Maemo

2010-07-13T22:46:24Z

94.10.155.86: /* Where are the slider screen files located? */ In /opt/usr not /usr ?

{{Expand}}

This article will someday describe how everybody can customize Maemo 5 to make it as personal as possible. Discussion on t.m.o concerning customization in [http://talk.maemo.org/showthread.php?t=32845 this thread].

== Editing home ==

Through the Edit mode of the Home screen it is possible to:
* Add/move/delete widgets/shortcuts/contacts/bookmarks on the desktop
* Change the the number of desktop home views (1-4 views are available)
* Change background of the home (either for individual view or for all home views simultaneously through wallpaper sets)
* Change active theme of the device (out of the themes available/installed on the device)
Entering the edit mode happens by long tapping the home screen or by tapping the home screen background once and then tapping the Edit mode button which slides down at the top right corner of the home screen.

== Themes ==

Available themes can be installed straight from Application Manager. If you want to make your own theme, see below. See also article [[Themes]].

== Wallpapers ==

There is already [http://www.n900wallpapers.com/ n900wallpapers.com] for wallpapers. Unfortunately, you need a .desktop-file if you want to configure panoramic wallpapers for now.

There will be an application for wallpaper handling to be released (hopefully) soon. See [http://www.n900wallpapers.com/prismic Prismic wallpaper manager]

Also see [[Customizing_Maemo#Wallpapers_2]]

== Advanced customization ==
'''DISCLAIMER: Following instructions are only for [[:Category:Power_users|Power users]], and operations are potentially dangerous. Please see [[General precautions]] for further information.'''

=== Same Shortcut on multiple desktops ===

Use the same shortcut twice on the desktops can be useful. In order to do it, you have to manually modify appropiate .desktop file by adding the "X-Multiple=true" entry into the file. See [[Desktop file format]] for further information.

=== Welcome screen ===

It is possible to edit hildon-welcome. A howto is available [http://talk.maemo.org/showpost.php?p=347925&postcount=9 here]. Examples: [http://talk.maemo.org/showpost.php?p=347794&postcount=1 "Open source. Open heart. Open future."], [http://talk.maemo.org/showpost.php?p=350710&postcount=1 "The Power of Open."]

To insert your own video follow these instructions (from the link above thanks to VDVsx):

# Copy the video you want to play to /usr/share/hildon-welcome/media
# Go to /etc/hildon-welcome.d/ and edit the default.conf file or create a similar one (the videos will play by the alphabetic order of the .conf files)

=== LED notifications ===

Detailed description for modifying LED -notifications can be found in [[LED patterns]] -article.

=== Themes ===

There is an application for making themes to Maemo OS2008. This will be updated as soon as possible to cover also N900 and Maemo5. See article [[Making themes]].

=== Wallpapers ===

If you want to make panoramic wallpapers of your own, you need to create a .desktop -file and put it to same directory where your pictures are.

Example of a .desktop -file:
[Desktop Entry]
Type=Background Image
Name=Deers
Hidden=true

X-File1=/home/user/MyDocs/.images/deer1.png
X-File2=/home/user/MyDocs/.images/deer2.png
X-File3=/home/user/MyDocs/.images/deer3.png
X-File4=/home/user/MyDocs/.images/deer4.png

X-Order=01

====How to change a certain wall paper in terminal?====
gconftool -s --type string /apps/osso/hildon-desktop/views/1/bg-image $PATHTOIMAGE

Replace number "1" with the number of the desktop that you'd like change.<ref>http://talk.maemo.org/showpost.php?p=483028&postcount=2</ref>

====Where are the slider screen files located?====
The background image is lockslider.png and goes in /opt/usr/share/themes/alpha/backgrounds/

The other images (LockSliderTop.png, LockSliderThumbPortrait.png, LockSliderThumb.png, LockSliderRight.png, LockSliderLeft.png, LockSliderBottom.png) go in /opt/usr/share/themes/alpha/images

===Using the same widget on multiple desktops===

The folder /usr/share/applications/hildon contains files that contain info about installed programs. Duplicating these files will result in duplicating them in the shortcut list. However, this will result in a side effect causing the program to show multiple times the programs in the "More.." folder.

=== Contents of power key menu ===

Information on how to add reboot button to power key menu, add new keyboard shortcuts [http://talk.maemo.org/showthread.php?t=39565 N900 MODs]

Instructions on how to add the reboot key (from the link above thanks to f2thak):

# Open xterm and type sudo gainroot to enable root access
# Navigate to /etc/systemui
# Create a backup copy of the systemui file by typing cp systemui.xml systemui.xml.bak
# Edit the systemui file by typing vi systemui.xml
# At the bottom of the file you will notice that part of it (consisting of three ... entries) is disabled within the "comment" marks
# Move the "comment" marks mentioned above "<! --" without the space between ! and - (e.g. by deleting and re-typing them in other place) so that the two remaining entries ("Soft poweroff" and "Top in XTerm") are still within them but the "Reboot" entry gets outside of them. To do this, hit the key "i" to begin editing and the Esc button in xterm to stop (once you are done editing "dd" will delete any line you created by accident). Type :wq to save and edit after being done editing
# Close X-Terminal and reboot the device. After the N900 reboots, you should see the new "Reboot" option in the Menu

=== Transitions ===

Transition Control is an application which allows you to change various transition effects of the phone. Another approach is to edit the
/usr/share/hildon-desktop/transitions.ini file (root access is needed)

===Keyboard characters===

[[Remapping keyboard]]

[[Special_characters_view]]

====Keyboard Sym on auto hold====
PR1.2 brought a change in behaviour where holding a key will now result in the SYM for that key being inserted.

Maemo Bug 5421 details this change.
https://bugs.maemo.org/show_bug.cgi?id=5421

to re-enable the old autorepeat behaviour:

gconftool-2 -s /apps/osso/inputmethod/ext_kb_repeat_enabled --type boolean true

===Application Menu===

[[Application Menu]]

===Camera Sound===

In /usr/share/sounds the files camera_snd_title_1, 2 and 3 (1 is the camera shutter sound, 2 is the video recording sound and 3 is the focus sound) just replace them with any working wav sound file OR for a SILENT CAMERA just rename or delete these files! <ref name="camsnd">[http://talk.maemo.org/showthread.php?p=462484 Silent Camera Hack ]</ref>

===Editing SMS and Chat templates===
You can change the way you read SMS and chat conversations by editing the html files in /usr/share/rtcom-messaging-ui/html.<ref>http://talk.maemo.org/showthread.php?t=36618</ref>

===Slide to Unlock Screen===
You can edit the "Slide to Unlock" screen that appears upon pressing the power button while the phone is locked. You can do this by editing the png files found in /usr/share/themes/alpha/backgrounds/ <ref>http://talk.maemo.org/showpost.php?p=491060&postcount=403</ref>

===Status Icons===
====Editing The Status Icons====
You can edit the status icons by editing the files found in /usr/share/icons/hicolor <ref>http://talk.maemo.org/showpost.php?p=481662&postcount=252</ref>
====Reordering The Status Icons====
You can reorder the status icons that display on top of your desktop by editing /ect/hildon-desktop/status-menu.plugins<ref>http://talk.maemo.org/showpost.php?p=485678&postcount=334</ref>

Change the number(s) for the "X-Status-Menu-Position" section. The higher number, the lower the priority.

=== Icons ===

you can install them into ~/.local/share/icons/hicolor/scalable/hildon and they'll override the system icons, but leave them in place. [Does this apply to all icons and images??]

*/usr/share/icons/hicolor/scalable/hildon
**Signal images
**Battery1 images
<pre>
statusarea_battery_full13.png
statusarea_battery_full25.png
statusarea_battery_full38.png
statusarea_battery_full50.png
statusarea_battery_full63.png
statusarea_battery_full75.png
statusarea_battery_full88.png
statusarea_battery_full100.png
</pre>

*/usr/share/icons/hicolor/48x48/hildon/
** Battery2 images
** Availability images

*/usr/share/icons/hicolor/16x16/hildon
** Availability (Small) images

To install the bootup icons place the icons here (make sure you backup the original icons first!): /usr/share/icons/hicolor/scalable/hildon/

<pre>
indicator_update1.png
indicator_update2.png
indicator_update3.png
indicator_update4.png
indicator_update5.png
indicator_update6.png
indicator_update7.png
indicator_update8.png
</pre>

===Sound Effects===
You can edit the UI sound effects by editing the sound files found in /usr/share/sounds <ref>http://talk.maemo.org/showpost.php?p=486875&postcount=346</ref>

===Disabling Auto Updates Check===
You may want to disable the automatic software updates checks that occur upon internet connection, in order to consume less bandwidth when using 2G/3G connections. You can do so by editing the gconf file found in /var/lib/gconf/apps/hildon/update-notifier and changing the check interval from 1440(24 hours) to a much larger value. The value must not exceed 4,294,967,295:
gconftool -s --type int /apps/hildon/update-notifier/check_interval NEW_VALUE

== Resources & Links ==

Advanced Tweaks: [http://talk.maemo.org/showthread.php?t=39948 Collection of Low-Level Config-Files / Tools]

[https://garage.maemo.org/projects/powatool/ Powatool]

[http://wiki.maemo.org/Maemo_Summit_2009/Day_2#Personalizing_your_Maemo_5_device Personalizing your Maemo 5 device] presentation ([http://www.slideshare.net/hartti/n900-personalization slides]) at Maemo Summit 2009.

==References==

<references />

[[Category:Power_users]]
[[Category:N900]]