Maemo Wiki Mirror - User contributions [en]

Mer/Documentation/Installation

2009-10-24T18:05:06Z

80.220.238.64: /* Touch Book (Experimental) */

This article sums up the different ways to install Mer on different types of computers (VMWare, chroot, on device, etc.). Please feel free to add/edit. The original information is taken from [[Mer/Releases/0.9]].

Replace "<your version>" with the version you are going to install, e.g. "0.9".

== Installation in VirtualBox ==

# Unzip zip file
# Open VirtualBox, create new machine (click New):
#* Name: Mer ''<your version>''
#* OS type: Linux
#* Version: Ubuntu
#* RAM: 128MB (at least)
#* Disk: click "existing", find the mer-x86-generic-image-v''<your version>''.vmdk file, select, select
#* Next
# Finish
# Start the newly created virtual machine
# Installing all the needed packages for installing VirtualBox additions:
#* I had to install the following packages by:
#* sudo apt-get install build-essential linux-headers-*kernel-version*-generic
#*(replace *kernel-version* with the currently installed kernel-version on the virtual machine)
#*(you can simply find out which kernel-version you have, by executing "uname -r" in Mer's XTerminal)
# Installing the additions:
#*First of all you have to mount the CD-Image with the additions emulated as a cdrom-device into the virtual machine running mer.
#* Mount the VboxAdditions.iso by: Devices -> mount CD-ROM image -> select VboxGuestAdditions.iso
#* Create a new folder with root rights by:
#*sudo mkdir /media/cdrom
#* and mount the virtual device's filesystem to the new mountpoint by:
#*sudo mount /dev/scd0 /media/cdrom
#* If no errors are appearing you can install the additions by:
#*sudo /media/cdrom/VBoxLinuxAdditions-x86.run
# Rebooting the virtual machine:
#* Now, when the installation of the additions has finished, you can reboot the vm simply by:
#*sudo init 6
# Finished

== Installation (chroot) ==

<pre>
mkdir mer-<your version>
cd mer-<your version> && sudo tar xzf mer-x86-generic-image-v<your version>.tar.gz
sudo mkdir -p tmp/.X11-unix home/$USER/.osso
sudo mv usr/bin/maemo-invoker usr/bin/maemo-invoker.real
echo -e '#!/bin/sh\nPROG="$1"\nshift\nexec "$PROG" "$@"' | sudo tee usr/bin/maemo-invoker
sudo chmod 755 usr/bin/maemo-invoker
echo 'nameserver <mynameresolver>' | sudo tee -a etc/resolv.conf
</pre>

=== Start-up (from within <code>mer-''<your version>''</code> directory) ===

<pre>
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite 2>/dev/null 1>&2 &
sudo mount --bind /tmp/.X11-unix tmp/.X11-unix
sudo mount --bind /dev/pts dev/pts
sudo mount -t proc proc proc
sudo mount -t sysfs sysfs sys
sudo chroot .
export DISPLAY=:2.0
/etc/init.d/dbus start
start-hildon
</pre>

== x86 Install ==

See [[Mer/Documentation/Making_x86_Mer_Bootable|Making x86 Mer Bootable]]

== N8x0 Install ==

=== The Installer ===

The developers of Mer implemented an installer, which leads through all the steps of installation. In order to use the installer you need to open:
[http://trac.tspre.org/merinstaller.install .install file] with your device, which will prompt you to install the file (about 2.5MB) and add the Extras, Extras-devel and tspre.org repositories if they were not added already.

After the download and the installation go to Settings -> Application Manager -> Utilities -> Browse Installable Applications -> Other and system and you will find a program "Install Bootmenu" and "Merinstaller". If you did not install those by pressing "OK" before, do it now.

The Simple Install will create a bootmenu entry for you. However, for more advanced installations - eg if you already have multiple booting OSes - you might want to read about its [[Mer/Documentation/Bootmenu|configuration]] - you may need to make a .item if you have a clone-to-SD copy of Maemo or Deblet. You can also find out how to change the default boot menu item and other bootmenu tricks.

Assuming you created all the .item files you wanted, go ahead, and start the bootmenu installer from Utilities -> Install Bootmenu. Its advised to close all other applications and network connections, but the installer will tell you all relevant information.

* "Are you sure to continue?" - yes
* "Create backup of current initfs" - yes/no
* "Remove unneeded extra (and factory testing) stuff?" - yes
* "install telnet server for network recovery?" - yes/no
* "install dropbear ssh server for advanced network recovery?" - yes/no
* "/etc/bootmenu.conf found, do you want to add it to initfs?" - yes
* "Ready for flashing this image?" - yes/no

After a successfull flash, the device will reboot and you should see the bootmenu, where you can select the partition you want to boot. Choose the operating system where you just installed the installer for Mer and boot it.

Now start the Merinstaller via Utilities -> Install Mer. Follow the instructions. When prompted for the URL= you can point it to any rootfs image you want. Check at [[Mer/Releases]] or ask at #mer.

Once the installer puts the extracted rootfs to your device you can reboot and chose the partition where you put Mer. Please contribute by filing bugs on [https://bugs.maemo.org/ bugs.maemo.org]

=== Flashable Image ===

'''NOTE: Very experimental, because it doesn't use the Maemo initfs; only install if you want to help test it.'''

Grab a kernel and rootfs image of Mer and flash them directly to the device by: 
<code>
./flasher-3.0-static -k mer-armel-n8x0-kernel-v<your version>.zImage -r mer-armel-n8x0-image-v<your version>.jffs2 -f -R
</code>

You might want a MMC card swap partition.

== 770 Install ==

'''(these instructions need testing)'''

You will need at least a 1gb MMC, and these instructions are based on OS2008HE kernel. 48mhz kernel is highly recommended

Partition MMC to:

*p1: Large ext3 partition first
*p2: 256 MB swap partition second

Grab http://packages.tspre.org/pool/user/b/bootmenu/bootmenu_1.5-2_armel.deb and install it.

* Open the main menu and tap Utilities -> Install Bootmenu to start the bootmenu install process.
** If nothing happens, install xterm
** If window appears and then goes away, gainroot is not installed
*** Alternative method with dropbear client / server installed, start xterm, run dbclient root@0, password 'rootme', run /usr/sbin/install_bootmenu
* First, say yes to removing "unneeded extra (and factory testing) stuff"
* say yes to including bootmenu.conf (important). Reboot when done flashing.
* This is a special boot menu where boot menu items are made in /etc/bootmenu.d/*.item and refresh_bootmenu.d will flash this to initfs. '''If you are cloning or booting other OS'es, you'll need to make such .item files'''. See [[Mer/Documentation/Bootmenu]]

Grab e2fsprogs and install it - grab gnutar as well

*From x-terminal, root: insmod /mnt/initfs/lib/modules/current/mbcache.ko
*insmod /mnt/initfs/lib/modules/current/jbd.ko
*insmod /mnt/initfs/lib/modules/current/ext3.ko
*mkfs.ext3 /dev/mmcblk0p1
*mkswap /dev/mmcblk0p2
*swapon /dev/mmcblk0p2
*mkdir -p /mnt/mer
*mkdir -p /etc/bootmenu.d
*mount -t ext3 /dev/mmcblk0p1 /mnt/mer
*cd /mnt/mer; wget <nowiki>http://stskeeps.subnetmask.net/mer/<your version>/mer-armel-770-image-v<your version>.tar.gz</nowiki>
*tar pzxvf mer-armel-770-image-v<your version>.tar.gz
*rm mer-armel-770-image-v<your version>.tar.gz
*umount /mnt/mer
*Make /etc/bootmenu.d/mer.item with the following contents:

<pre>
ITEM_NAME="Mer"
ITEM_ID="mer"
ITEM_DEVICE="mmcblk0p1"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"
ITEM_LINUXRC="linuxrc"
</pre>
*refresh_bootmenu.d (say yes to reflashing, no to backup of initfs. reboot)
*Hold down Menu key when prompted while booting and select Mer in the boot menu.

== BeagleBoard port ==

* Make sure you are running a RECENT uBoot, and you have USB input devices like keyboard or mouse, if you don't own a touchscreen..
* Make a SD card, partitioned with 50mb FAT as first partition, extract boot fs on this, and the rest Linux partition, format this as ext3, and extract rootfs on this.
* In uBoot, use the following commands (you may have to adjust video= parameter to match your display screen:

'''Note: The format of the video bootargs parameter has changed for the new 2.6.28 kernel in 0.9. You'll likely have to update the bootargs line.'''

<pre>
setenv bootcmd 'mmcinit; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000'
setenv bootargs 'console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait omapfb.video_mode=1024x768MR16@60'
saveenv
boot
</pre>

* The tablet should output kernel output on serial and on video, and on HDMI out it will eventually start X and show the First Boot Wizard. Good luck.

== Pocket Loox 720 port (experimental) ==

* Set up a SD card with a logical partition, and inside this logical partition, make a 50mb or so FAT partition (p5), and put the zImage file on this filesystem, name it zImage. After the logical partition, make a ext3 partition (p2), and untar rootfs on it.
* Grab [http://www.handhelds.org/moin/moin.cgi/HaRET HaRET] and put it on the FAT partition, HaRET.exe.
* Make a file, startup.txt, with the following contents:

<pre>
set kernel "zImage"
set mtype "617"
set RAMADDR "0xa8000000"
set cmdline "mem=128M rootdelay=1 root=b302 rw console=tty0"
boot
</pre>

* Unmount all filesystems, insert SD card into Pocket Loox, boot by running HaReT.exe. If HaRET stops with "Jumping to kernel..." then grab [http://dl.free.fr/dZ75nlNFA/loox_boot.tgz HaRET] from www.postnuklear.de/linuxloox.
* Experimental release, if you want to play with this - come hang out on #mer on irc.freenode.net and we'll try to guide you along. It is a 640x480 screen so our theme won't fit.

* For using ssh between loox and desktop box :
- You need to grab an ssh enabled [http://www.daimi.au.dk/~cvm/loox.tar.gz rootfs].

- extract it on your sd card (ext3 partition)

- connect the Loox with the sync cable to your desktop box. And power on loox.

- on your desktop box check for USB network interface (usualy usb0) with : ifconfig

- configure the USB network interface : sudo ifconfig usb0 192.168.2.1

- ssh to loox : ssh root@192.168.2.2

- root password is 'rootme'

* If touchscreen is not calibrated MER v0.11:
- download [http://ports.ubuntu.com/pool/main/t/tslib/libts-bin_1.0-4ubuntu2_armel.deb tslib-bin] to your desktop box.

- scp the deb file to loox : scp libts-bin_1.0-4ubuntu2_armel.deb root@192.168.2.2:/root

- on loox : dpkg -i libts-bin*.deb

- run ts_calibrate (all in one line) :
<pre>
TSLIB_CONFFILE=/etc/ts.conf TSLIB_TSDEVICE=/dev/input/event0 TSLIB_FBDEVICE=/dev/fb0 TSLIB_CONSOLEDEVICE=none TSLIB_CALIBFILE=/etc/pointercal ts_calibrate
</pre>
- you can test your touchscreen with ts_test

* If touchscreen is not working under Xorg MER v0.11 :
remove xorg synaptics driver
<pre>
apt-get remove xserver-xorg-input-synaptics
</pre>

* Internet on Loox
- Configure MASQUERADE on you desktop
<pre>
iptables -A FORWARD -s 192.168.2.0/24 -j ACCEPT
iptables -A FORWARD -d 192.168.2.0/24 -j ACCEPT
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.2.0/24 -j MASQUERADE
echo 1 >/proc/sys/net/ipv4/ip_forward
</pre>

== Touch Book (Experimental) ==

'''Until there's a Touch Book image, use SmartQ5 image.'''

First, make sure your SD card's geometry is 63 / 255 . Otherwise the Touch Book won't recognice it. To set the correct geometry, put the SD in your host-computers card-reader and open up a terminal. Type:
<pre>
bash:$ sudo fdisk /dev/<yoursdcard>

Command (m for help): [x]

Expert command (m for help): [s]
Number of sectors : [63]

Expert command (m for help): [h]
Number of heads : [255]

Expert command (m for help): [w]
</pre>

'''Formatting the SD card:'''

* The first partition needs to be formatted as FAT32 ''and have the boot flag''. 30Mb size is fine.
* Format the second partition as ext3, at least 512Mb size.
* If you want, you can also create one more partition for swap.

This is easy to do with linux host-computer.
GParted is easy to use graphical Partition Editor.

'''Installation'''

Download Mer image and this package:
[http://trac.tspre.org/meiz/touchbook-kernel.tar.gz]
It contains the original AIOS kernel and modules.

Unpack both in the ext3 partition of the SD-card and copy the uImage (in /boot of the kernel package) to the first fat partition.

To get the wlan working you have to copy /etc/Wireless over from the AIOS.

== SmartQ ==
Dual booting doesn't seem to work at the moment.

You'll need an SD card with a FAT32 as the first partition and more than 140MB free.

Download the correct firmware image and rootfs image from the Released Images table. Copy both of them to the root of the FAT32 partition on the SD card.

Rename the firmware image to either 'SmartQ5' or 'SmartQ7' according to your device.

You may also want to download some additional software to our SD card for after Mer is installed. 
To use Wifi, you'll need the Marvell Wifi Firmware blobs
* Browse [http://www.marvell.com/drivers/driverDisplay.do?driverId=203 here to agree the download license] and get a zip file
* Extract the downloaded zip file, then extract SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar within it. Extract the FwImage folder to your PC.
* Inside there are two files, helper_sd.bin and sd8686.bin. Rename helper_sd.bin to sd8686_helper.bin and copy to your SD card

The commands to extract and copy it might look like this:
cd /tmp
unzip SD-8686-LINUX26-SYSKT-9.70.3.p24-26409.P45-GPL.zip
tar xf SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar
cp FwImage/helper_sd.bin /path_to_SD_CARD/sd8686_helper.bin
cp FwImage/sd8686.bin /path_to_SD_CARD/sd8686.bin

Wifi WPA2 fix
* Download the [http://www.daimi.au.dk/~cvm/kernel-smartq5-modules_2.6.24.7-smartq5-050509_all.deb SmartQ5] or [http://download.opensuse.org/repositories/Maemo://Mer:/Devel:/HW:/SmartQ:/Devel/MerDevel_Ubuntu_9.04/all/kernel-smartq7-modules_2.6.24.7-smartq7-20090729_all.deb SmartQ7] WPA2-fixed driver to your SD card.

Now unmount the SD card and eject it.

Power off the SmartQ totally (wait for the LED to go out) and insert the SD card.

===SmartQ5===
Press and hold the + button and insert the charger.
The device will begin to boot; the LED will be green/yellow.
A series of chinese characters will appear ending with '...' if all is going well. Once you see them, you can release the + button. Next there will be
a progress bar. Once it completes, the device will automatically reboot.

===SmartQ7===
Press and hold the 'menu' key (bottom key on front) and insert the charger.
The device will begin to boot; the LED will be a different colour - green/yellow. You can release the menu key. Some chinese symbols appear and then a progress bar ticks (slowly) up to 100%. Once it completes, the device will automatically reboot.

===both===
After this a calibration screen will appear and shortly after you are in Mer.

If you have connected it to a computer via USB, it will be accessible over USB networking on IP 192.168.2.15 ([http://wiki.maemo.org/USB_networking#Host_USB_Network_Configuration see instructions here]) with a SSH server, login root, password rootme

It will not show a splash screen, but it will after darkness then make the screen white, and eventually, show the Mer background and first boot wizard.

=== To mount your SD card ===
In Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
<pre>
$ sudo mount -t vfat /dev/mmcblk1p1 /media
</pre>
When prompted for a password, enter the one you set when you first started.
Note that the above device name has one lower-case L character and then two number one characters (these can look quite similar in some fonts).

=== To get wireless networking (including WPA2) to work===

In order to get wireless networking to work, you are going to have to install the Marvell firmware you copied onto your SD card, and to get WPA2 working, you'll also need to install the .deb. The first step is to mount your SD card (see the section just above this, if you haven't already mounted it).

So, in Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
<pre>
$ sudo cp /media/sd8686.bin /lib/firmware/
(if prompted, the password is the one you set when you first started)
$ sudo cp /media/sd8686_helper.bin /lib/firmware/
</pre>
And then either, for the SmartQ5 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q5.]
<pre>
$ sudo dpkg -i /media/kernel-smartq5-modules_2.6.24.7-smartq5-*_all.deb
</pre>
or for the SmartQ7 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q7.]
<pre>
$ sudo dpkg -i /media/kernel-smartq7-modules_2.6.24.7-smartq7-*_all.deb
</pre>

Now that you've enabled networking, you should close the gaping security hole which is part of the default configuration by changing the root password from its default, which is "rootme".
<pre>
$ sudo passwd
Password: (enter your user password)
Enter new UNIX password: (enter any hard to guess password you want)
Retype new UNIX password: (same one again)
</pre>

Next you should reboot.
<pre>
$ sudo /sbin/reboot
</pre>

Once it reboots, you should be able to see wireless networks on the menu and select them.

=== Booting from SD card ===
(this was taken from [http://alone-in-the-light.zenvoid.org/2009/06/boot-smartq-5-from-sd-card.html zenvoid's blog])

In order to boot from the SD card, it is simply a matter of creating a partition on the SD card large enough to hold the mer distribution, but leaving enough unpartitioned space at the end of the card for the bootloader to sit.

* Download install-smartq-qi.sh, qi-smartq-20090612.bin from http://zenvoid.org/software/qi-smartq

* Create at least one ext2/ext3 Partition your SD card (and optionally a swap partition), but always '''remember to reserve 1 MiB of free, unpartitioned space at the end of the SD card'''. To be precise, at least the last 2048 blocks (512 bytes each) must be reserved.
* Untar (tar --numeric-owner -zxvf) the rootfs for your device onto the partition you created on your SD card (make sure it isn't mounted with any no* options, e.g. nodev, noexec, ..)
* Rename or copy the kernel file (/boot/zImage<something>) to /boot/linux-SMDK6410.bin
* Run
<pre>
./install-smartq-qi.sh /dev/SD_CARD_DEVICE qi-smartq-20090612.bin
</pre>

To boot from the SD card, keep the "move"/fullscreen button (Q5) or right-hand-most button on the top which looks like a target symbol (Q7) pressed and then press the "power" button.

Q5 Boot stages:
* Red LED: First stage - bootloader is loading itself into memory.
* Yellow LED: Second stage - bootloader running, trying to locate and loading a kernel image.
* Green LED: Linux kernel loaded and running.
* Blinking yellow LED: A critical error while reading from the SD card.
* Blinking green LED: No kernel found.

Q7 Boot:

Keep in mind that the LEDs colours are reversed on the Q7, i.e. a green LED on the Q5 is a red one on the Q7 (the list above is for the Q5)

There is no battery check at the moment.

==== Alternate SD booting method using the OF bootloader ====
(as desribed on the Smartqmid forum:
http://www.smartqmid.com/phpBB3/viewtopic.php?f=2&t=150)

'''works only with OF installed on the device'''

in short:
*the first partition must be fat32 and the other primary partitions must be ext3
*on the first (fat) partition must be a folder named boot, that contains a menu.lst file and the kernel image (zimage)
*the menu.lst should be formated like this:
<pre>
title sdcard # name of the entry
kernel /boot/zimage # kernel image location
param root=/dev/mmcblk1p2 rootwait # location of the root fs, this is
# the second primary partition on SD
# the internal memory is mmcblk0,
# first internal partition = mmcblk0p1

</pre>

With all this in place, the device shows a simple boot menu when turned on wit the SD card inside, you can select the entry with +,- buttons on the left and booting is triggered with middle button on the upper left.

Theoretically you can multiboot up to 5 different systems (internal + on the fat partition + three ext3 partitions, '''not tested''').

[[Category:Mer]]

Mer/Documentation/Installation

2009-10-20T14:02:27Z

80.220.238.64: /* Touch Book */

This article sums up the different ways to install Mer on different types of computers (VMWare, chroot, on device, etc.). Please feel free to add/edit. The original information is taken from [[Mer/Releases/0.9]].

Replace "<your version>" with the version you are going to install, e.g. "0.9".

== Installation in VirtualBox ==

# Unzip zip file
# Open VirtualBox, create new machine (click New):
#* Name: Mer ''<your version>''
#* OS type: Linux
#* Version: Ubuntu
#* RAM: 128MB (at least)
#* Disk: click "existing", find the mer-x86-generic-image-v''<your version>''.vmdk file, select, select
#* Next
# Finish
# Start the newly created virtual machine
# Installing all the needed packages for installing VirtualBox additions:
#* I had to install the following packages by:
#* sudo apt-get install build-essential linux-headers-*kernel-version*-generic
#*(replace *kernel-version* with the currently installed kernel-version on the virtual machine)
#*(you can simply find out which kernel-version you have, by executing "uname -r" in Mer's XTerminal)
# Installing the additions:
#*First of all you have to mount the CD-Image with the additions emulated as a cdrom-device into the virtual machine running mer.
#* Mount the VboxAdditions.iso by: Devices -> mount CD-ROM image -> select VboxGuestAdditions.iso
#* Create a new folder with root rights by:
#*sudo mkdir /media/cdrom
#* and mount the virtual device's filesystem to the new mountpoint by:
#*sudo mount /dev/scd0 /media/cdrom
#* If no errors are appearing you can install the additions by:
#*sudo /media/cdrom/VBoxLinuxAdditions-x86.run
# Rebooting the virtual machine:
#* Now, when the installation of the additions has finished, you can reboot the vm simply by:
#*sudo init 6
# Finished

== Installation (chroot) ==

<pre>
mkdir mer-<your version>
cd mer-<your version> && sudo tar xzf mer-x86-generic-image-v<your version>.tar.gz
sudo mkdir -p tmp/.X11-unix home/$USER/.osso
sudo mv usr/bin/maemo-invoker usr/bin/maemo-invoker.real
echo -e '#!/bin/sh\nPROG="$1"\nshift\nexec "$PROG" "$@"' | sudo tee usr/bin/maemo-invoker
sudo chmod 755 usr/bin/maemo-invoker
echo 'nameserver <mynameresolver>' | sudo tee -a etc/resolv.conf
</pre>

=== Start-up (from within <code>mer-''<your version>''</code> directory) ===

<pre>
Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -extension Composite 2>/dev/null 1>&2 &
sudo mount --bind /tmp/.X11-unix tmp/.X11-unix
sudo mount --bind /dev/pts dev/pts
sudo mount -t proc proc proc
sudo mount -t sysfs sysfs sys
sudo chroot .
export DISPLAY=:2.0
/etc/init.d/dbus start
start-hildon
</pre>

== x86 Install ==

See [[Mer/Documentation/Making_x86_Mer_Bootable|Making x86 Mer Bootable]]

== N8x0 Install ==

=== The Installer ===

The developers of Mer implemented an installer, which leads through all the steps of installation. In order to use the installer you need to open:
[http://trac.tspre.org/merinstaller.install .install file] with your device, which will prompt you to install the file (about 2.5MB) and add the Extras, Extras-devel and tspre.org repositories if they were not added already.

After the download and the installation go to Settings -> Application Manager -> Utilities -> Browse Installable Applications -> Other and system and you will find a program "Install Bootmenu" and "Merinstaller". If you did not install those by pressing "OK" before, do it now.

The Simple Install will create a bootmenu entry for you. However, for more advanced installations - eg if you already have multiple booting OSes - you might want to read about its [[Mer/Documentation/Bootmenu|configuration]] - you may need to make a .item if you have a clone-to-SD copy of Maemo or Deblet. You can also find out how to change the default boot menu item and other bootmenu tricks.

Assuming you created all the .item files you wanted, go ahead, and start the bootmenu installer from Utilities -> Install Bootmenu. Its advised to close all other applications and network connections, but the installer will tell you all relevant information.

* "Are you sure to continue?" - yes
* "Create backup of current initfs" - yes/no
* "Remove unneeded extra (and factory testing) stuff?" - yes
* "install telnet server for network recovery?" - yes/no
* "install dropbear ssh server for advanced network recovery?" - yes/no
* "/etc/bootmenu.conf found, do you want to add it to initfs?" - yes
* "Ready for flashing this image?" - yes/no

After a successfull flash, the device will reboot and you should see the bootmenu, where you can select the partition you want to boot. Choose the operating system where you just installed the installer for Mer and boot it.

Now start the Merinstaller via Utilities -> Install Mer. Follow the instructions. When prompted for the URL= you can point it to any rootfs image you want. Check at [[Mer/Releases]] or ask at #mer.

Once the installer puts the extracted rootfs to your device you can reboot and chose the partition where you put Mer. Please contribute by filing bugs on [https://bugs.maemo.org/ bugs.maemo.org]

=== Flashable Image ===

'''NOTE: Very experimental, because it doesn't use the Maemo initfs; only install if you want to help test it.'''

Grab a kernel and rootfs image of Mer and flash them directly to the device by: 
<code>
./flasher-3.0-static -k mer-armel-n8x0-kernel-v<your version>.zImage -r mer-armel-n8x0-image-v<your version>.jffs2 -f -R
</code>

You might want a MMC card swap partition.

== 770 Install ==

'''(these instructions need testing)'''

You will need at least a 1gb MMC, and these instructions are based on OS2008HE kernel. 48mhz kernel is highly recommended

Partition MMC to:

*p1: Large ext3 partition first
*p2: 256 MB swap partition second

Grab http://packages.tspre.org/pool/user/b/bootmenu/bootmenu_1.5-2_armel.deb and install it.

* Open the main menu and tap Utilities -> Install Bootmenu to start the bootmenu install process.
** If nothing happens, install xterm
** If window appears and then goes away, gainroot is not installed
*** Alternative method with dropbear client / server installed, start xterm, run dbclient root@0, password 'rootme', run /usr/sbin/install_bootmenu
* First, say yes to removing "unneeded extra (and factory testing) stuff"
* say yes to including bootmenu.conf (important). Reboot when done flashing.
* This is a special boot menu where boot menu items are made in /etc/bootmenu.d/*.item and refresh_bootmenu.d will flash this to initfs. '''If you are cloning or booting other OS'es, you'll need to make such .item files'''. See [[Mer/Documentation/Bootmenu]]

Grab e2fsprogs and install it - grab gnutar as well

*From x-terminal, root: insmod /mnt/initfs/lib/modules/current/mbcache.ko
*insmod /mnt/initfs/lib/modules/current/jbd.ko
*insmod /mnt/initfs/lib/modules/current/ext3.ko
*mkfs.ext3 /dev/mmcblk0p1
*mkswap /dev/mmcblk0p2
*swapon /dev/mmcblk0p2
*mkdir -p /mnt/mer
*mkdir -p /etc/bootmenu.d
*mount -t ext3 /dev/mmcblk0p1 /mnt/mer
*cd /mnt/mer; wget <nowiki>http://stskeeps.subnetmask.net/mer/<your version>/mer-armel-770-image-v<your version>.tar.gz</nowiki>
*tar pzxvf mer-armel-770-image-v<your version>.tar.gz
*rm mer-armel-770-image-v<your version>.tar.gz
*umount /mnt/mer
*Make /etc/bootmenu.d/mer.item with the following contents:

<pre>
ITEM_NAME="Mer"
ITEM_ID="mer"
ITEM_DEVICE="mmcblk0p1"
ITEM_MODULES="mbcache jbd ext3"
ITEM_FSTYPE="ext3"
ITEM_FSOPTIONS="noatime,ro"
ITEM_LINUXRC="linuxrc"
</pre>
*refresh_bootmenu.d (say yes to reflashing, no to backup of initfs. reboot)
*Hold down Menu key when prompted while booting and select Mer in the boot menu.

== BeagleBoard port ==

* Make sure you are running a RECENT uBoot, and you have USB input devices like keyboard or mouse, if you don't own a touchscreen..
* Make a SD card, partitioned with 50mb FAT as first partition, extract boot fs on this, and the rest Linux partition, format this as ext3, and extract rootfs on this.
* In uBoot, use the following commands (you may have to adjust video= parameter to match your display screen:

'''Note: The format of the video bootargs parameter has changed for the new 2.6.28 kernel in 0.9. You'll likely have to update the bootargs line.'''

<pre>
setenv bootcmd 'mmcinit; fatload mmc 0:1 0x80300000 uImage; bootm 0x80300000'
setenv bootargs 'console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait omapfb.video_mode=1024x768MR16@60'
saveenv
boot
</pre>

* The tablet should output kernel output on serial and on video, and on HDMI out it will eventually start X and show the First Boot Wizard. Good luck.

== Pocket Loox 720 port (experimental) ==

* Set up a SD card with a logical partition, and inside this logical partition, make a 50mb or so FAT partition (p5), and put the zImage file on this filesystem, name it zImage. After the logical partition, make a ext3 partition (p2), and untar rootfs on it.
* Grab [http://www.handhelds.org/moin/moin.cgi/HaRET HaRET] and put it on the FAT partition, HaRET.exe.
* Make a file, startup.txt, with the following contents:

<pre>
set kernel "zImage"
set mtype "617"
set RAMADDR "0xa8000000"
set cmdline "mem=128M rootdelay=1 root=b302 rw console=tty0"
boot
</pre>

* Unmount all filesystems, insert SD card into Pocket Loox, boot by running HaReT.exe. If HaRET stops with "Jumping to kernel..." then grab [http://dl.free.fr/dZ75nlNFA/loox_boot.tgz HaRET] from www.postnuklear.de/linuxloox.
* Experimental release, if you want to play with this - come hang out on #mer on irc.freenode.net and we'll try to guide you along. It is a 640x480 screen so our theme won't fit.

* For using ssh between loox and desktop box :
- You need to grab an ssh enabled [http://www.daimi.au.dk/~cvm/loox.tar.gz rootfs].

- extract it on your sd card (ext3 partition)

- connect the Loox with the sync cable to your desktop box. And power on loox.

- on your desktop box check for USB network interface (usualy usb0) with : ifconfig

- configure the USB network interface : sudo ifconfig usb0 192.168.2.1

- ssh to loox : ssh root@192.168.2.2

- root password is 'rootme'

* If touchscreen is not calibrated MER v0.11:
- download [http://ports.ubuntu.com/pool/main/t/tslib/libts-bin_1.0-4ubuntu2_armel.deb tslib-bin] to your desktop box.

- scp the deb file to loox : scp libts-bin_1.0-4ubuntu2_armel.deb root@192.168.2.2:/root

- on loox : dpkg -i libts-bin*.deb

- run ts_calibrate (all in one line) :
<pre>
TSLIB_CONFFILE=/etc/ts.conf TSLIB_TSDEVICE=/dev/input/event0 TSLIB_FBDEVICE=/dev/fb0 TSLIB_CONSOLEDEVICE=none TSLIB_CALIBFILE=/etc/pointercal ts_calibrate
</pre>
- you can test your touchscreen with ts_test

* If touchscreen is not working under Xorg MER v0.11 :
remove xorg synaptics driver
<pre>
apt-get remove xserver-xorg-input-synaptics
</pre>

* Internet on Loox
- Configure MASQUERADE on you desktop
<pre>
iptables -A FORWARD -s 192.168.2.0/24 -j ACCEPT
iptables -A FORWARD -d 192.168.2.0/24 -j ACCEPT
iptables -t nat -A POSTROUTING -o eth0 -s 192.168.2.0/24 -j MASQUERADE
echo 1 >/proc/sys/net/ipv4/ip_forward
</pre>

== Touch Book (Experimental) ==

'''Until there's a Touch Book image, use SmartQ5 image.'''

First, make sure your SD card's geometry is 63 / 255 . Otherwise the Touch Book won't recognice it. To set the correct geometry, put the SD in your host-computers card-reader and open up a terminal. Type:
<pre>
bash:$ sudo fdisk /dev/<yoursdcard>

Command (m for help): [x]

Expert command (m for help): [s]
Number of sectors : [63]

Expert command (m for help): [h]
Number of heads : [255]

Expert command (m for help): [w]
</pre>

'''Formatting the SD card:'''

* The first partition needs to be formatted as FAT32 ''and have the boot flag''. 30Mb size is fine.
* Format the second partition as ext3, at least 512Mb size.
* If you want, you can also create one more partition for swap.

This is easy to do with linux host-computer.
GParted is easy to use graphical Partition Editor.

'''Installation'''

Download Mer image and this package:
[http://trac.tspre.org/meiz/touchbook-kernel.tar.gz]
It contains the original AIOS kernel modules and kernel by Stskeeps.

Unpack both in the ext3 partition of the SD-card and copy the uImage (in /boot of the kernel package) to the first fat partition.

== SmartQ ==
Dual booting doesn't seem to work at the moment.

You'll need an SD card with a FAT32 as the first partition and more than 140MB free.

Download the correct firmware image and rootfs image from the Released Images table. Copy both of them to the root of the FAT32 partition on the SD card.

Rename the firmware image to either 'SmartQ5' or 'SmartQ7' according to your device.

You may also want to download some additional software to our SD card for after Mer is installed. 
To use Wifi, you'll need the Marvell Wifi Firmware blobs
* Browse [http://www.marvell.com/drivers/driverDisplay.do?driverId=203 here to agree the download license] and get a zip file
* Extract the downloaded zip file, then extract SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar within it. Extract the FwImage folder to your PC.
* Inside there are two files, helper_sd.bin and sd8686.bin. Rename helper_sd.bin to sd8686_helper.bin and copy to your SD card

The commands to extract and copy it might look like this:
cd /tmp
unzip SD-8686-LINUX26-SYSKT-9.70.3.p24-26409.P45-GPL.zip
tar xf SD-8686-FEDORA26FC6-SYSKT-GPL-9.70.3.p24-26409.P45.tar
cp FwImage/helper_sd.bin /path_to_SD_CARD/sd8686_helper.bin
cp FwImage/sd8686.bin /path_to_SD_CARD/sd8686.bin

Wifi WPA2 fix
* Download the [http://www.daimi.au.dk/~cvm/kernel-smartq5-modules_2.6.24.7-smartq5-050509_all.deb SmartQ5] or [http://download.opensuse.org/repositories/Maemo://Mer:/Devel:/HW:/SmartQ:/Devel/MerDevel_Ubuntu_9.04/all/kernel-smartq7-modules_2.6.24.7-smartq7-20090729_all.deb SmartQ7] WPA2-fixed driver to your SD card.

Now unmount the SD card and eject it.

Power off the SmartQ totally (wait for the LED to go out) and insert the SD card.

===SmartQ5===
Press and hold the + button and insert the charger.
The device will begin to boot; the LED will be green/yellow.
A series of chinese characters will appear ending with '...' if all is going well. Once you see them, you can release the + button. Next there will be
a progress bar. Once it completes, the device will automatically reboot.

===SmartQ7===
Press and hold the 'menu' key (bottom key on front) and insert the charger.
The device will begin to boot; the LED will be a different colour - green/yellow. You can release the menu key. Some chinese symbols appear and then a progress bar ticks (slowly) up to 100%. Once it completes, the device will automatically reboot.

===both===
After this a calibration screen will appear and shortly after you are in Mer.

If you have connected it to a computer via USB, it will be accessible over USB networking on IP 192.168.2.15 ([http://wiki.maemo.org/USB_networking#Host_USB_Network_Configuration see instructions here]) with a SSH server, login root, password rootme

It will not show a splash screen, but it will after darkness then make the screen white, and eventually, show the Mer background and first boot wizard.

=== To mount your SD card ===
In Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
<pre>
$ sudo mount -t vfat /dev/mmcblk1p1 /media
</pre>
When prompted for a password, enter the one you set when you first started.
Note that the above device name has one lower-case L character and then two number one characters (these can look quite similar in some fonts).

=== To get wireless networking (including WPA2) to work===

In order to get wireless networking to work, you are going to have to install the Marvell firmware you copied onto your SD card, and to get WPA2 working, you'll also need to install the .deb. The first step is to mount your SD card (see the section just above this, if you haven't already mounted it).

So, in Mer on SmartQ, open X-Terminal and type (tab-completion is your friend):
<pre>
$ sudo cp /media/sd8686.bin /lib/firmware/
(if prompted, the password is the one you set when you first started)
$ sudo cp /media/sd8686_helper.bin /lib/firmware/
</pre>
And then either, for the SmartQ5 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q5.]
<pre>
$ sudo dpkg -i /media/kernel-smartq5-modules_2.6.24.7-smartq5-*_all.deb
</pre>
or for the SmartQ7 [Note: The following step may not be necessary as the 0.16-5 firmware automatically installs the most current file from the SD card during bootup. The confirmation message is "wifi firmware installation successful". Verified on Q7.]
<pre>
$ sudo dpkg -i /media/kernel-smartq7-modules_2.6.24.7-smartq7-*_all.deb
</pre>

Now that you've enabled networking, you should close the gaping security hole which is part of the default configuration by changing the root password from its default, which is "rootme".
<pre>
$ sudo passwd
Password: (enter your user password)
Enter new UNIX password: (enter any hard to guess password you want)
Retype new UNIX password: (same one again)
</pre>

Next you should reboot.
<pre>
$ sudo /sbin/reboot
</pre>

Once it reboots, you should be able to see wireless networks on the menu and select them.

=== Booting from SD card ===
(this was taken from [http://alone-in-the-light.zenvoid.org/2009/06/boot-smartq-5-from-sd-card.html zenvoid's blog])

In order to boot from the SD card, it is simply a matter of creating a partition on the SD card large enough to hold the mer distribution, but leaving enough unpartitioned space at the end of the card for the bootloader to sit.

* Download install-smartq-qi.sh, qi-smartq-20090612.bin from http://zenvoid.org/software/qi-smartq

* Create at least one ext2/ext3 Partition your SD card (and optionally a swap partition), but always '''remember to reserve 1 MiB of free, unpartitioned space at the end of the SD card'''. To be precise, at least the last 2048 blocks (512 bytes each) must be reserved.
* Untar (tar --numeric-owner -zxvf) the rootfs for your device onto the partition you created on your SD card (make sure it isn't mounted with any no* options, e.g. nodev, noexec, ..)
* Rename or copy the kernel file (/boot/zImage<something>) to /boot/linux-SMDK6410.bin
* Run
<pre>
./install-smartq-qi.sh /dev/SD_CARD_DEVICE qi-smartq-20090612.bin
</pre>

To boot from the SD card, keep the "move"/fullscreen button (Q5) or right-hand-most button on the top which looks like a target symbol (Q7) pressed and then press the "power" button.

Q5 Boot stages:
* Red LED: First stage - bootloader is loading itself into memory.
* Yellow LED: Second stage - bootloader running, trying to locate and loading a kernel image.
* Green LED: Linux kernel loaded and running.
* Blinking yellow LED: A critical error while reading from the SD card.
* Blinking green LED: No kernel found.

Q7 Boot:

Keep in mind that the LEDs colours are reversed on the Q7, i.e. a green LED on the Q5 is a red one on the Q7 (the list above is for the Q5)

There is no battery check at the moment.

==== Alternate SD booting method using the OF bootloader ====
(as desribed on the Smartqmid forum:
http://www.smartqmid.com/phpBB3/viewtopic.php?f=2&t=150)

'''works only with OF installed on the device'''

in short:
*the first partition must be fat32 and the other primary partitions must be ext3
*on the first (fat) partition must be a folder named boot, that contains a menu.lst file and the kernel image (zimage)
*the menu.lst should be formated like this:
<pre>
title sdcard # name of the entry
kernel /boot/zimage # kernel image location
param root=/dev/mmcblk1p2 rootwait # location of the root fs, this is
# the second primary partition on SD
# the internal memory is mmcblk0,
# first internal partition = mmcblk0p1

</pre>

With all this in place, the device shows a simple boot menu when turned on wit the SD card inside, you can select the entry with +,- buttons on the left and booting is triggered with middle button on the upper left.

Theoretically you can multiboot up to 5 different systems (internal + on the fat partition + three ext3 partitions, '''not tested''').

[[Category:Mer]]

Mer/Releases/0.16testing

2009-08-22T10:12:12Z

80.220.238.64: /* Bugs in 0.16testing3 */

Mer/Releases/0.16testing

2009-08-17T14:14:09Z

80.220.238.64: /* Bugs in 0.16testing2 */

Mer/Documentation/N8x0 Skype

2009-08-03T12:05:47Z

80.220.238.64: /* How to install Skype on Nokia n8x0 running Mer. */

== How to install Skype on Nokia n8x0 running Mer. ==

'''These instructions are tested to be working on Mer 0.15, n810. But note that you will fail to login due to Skype thinking there's no network available.'''

First you'll have to add needed repositories:

In XTerminal:

sudo nano /etc/apt/sources.list.d/tableteer.list

copy/paste in following:

deb http://catalogue.tableteer.nokia.com/updates/diablo-3/ /
deb http://catalogue.tableteer.nokia.com/certified/ diablo user

Press Ctrl+x to close the editor and click "y" when it asks if you want to save changes.

Next, update repos:

sudo apt-get update

Then Install the skype:

sudo apt-get install skype

You'll face a bunch of problems, so a little dpkg --forcing is needed.

Run this: (one big command, don't split it)

sudo dpkg -i --force-overwrite /var/cache/apt/archives /libjinglebase0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/libjinglep2p0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/gstreamer0.10-plugins-farsight_0.12.10-2_armel.deb /var/cache/apt/archives/libfarsight0.1-3_0.1.28-2_armel.deb

Finalize the install:

sudo apt-get install -f

and

sudo apt-get install skype

You can also remove the repository file to avoid future package conflicts:

sudo rm /etc/apt/sources.list.d/tableteer.list

'''That's it!
Skype should be installed now, if it doesn't show up in the application menu yet, you can start it from terminal or reboot (Menu item should appear after reboot)'''

Mer/Documentation/N8x0 Skype

2009-08-03T11:59:56Z

80.220.238.64: /* How to install Skype on Nokia n8x0 running Mer. */

== How to install Skype on Nokia n8x0 running Mer. ==

'''This is tested to be working on Mer 0.15, n810'''

First you'll have to add needed repositories:

In XTerminal:

sudo nano /etc/apt/sources.list.d/tableteer.list

copy/paste in following:

deb http://catalogue.tableteer.nokia.com/updates/diablo-3/ /
deb http://catalogue.tableteer.nokia.com/certified/ diablo user

Press Ctrl+x to close the editor and click "y" when it asks if you want to save changes.

Next, update repos:

sudo apt-get update

Then Install the skype:

sudo apt-get install skype

You'll face a bunch of problems, so a little dpkg --forcing is needed.

Run this: (one big command, don't split it)

sudo dpkg -i --force-overwrite /var/cache/apt/archives /libjinglebase0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/libjinglep2p0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/gstreamer0.10-plugins-farsight_0.12.10-2_armel.deb /var/cache/apt/archives/libfarsight0.1-3_0.1.28-2_armel.deb

Finalize the install:

sudo apt-get install -f

and

sudo apt-get install skype

You can also remove the repository file to avoid future package conflicts:

sudo rm /etc/apt/sources.list.d/tableteer.list

'''That's it!
Skype should be installed now, if it doesn't show up in the application menu yet, you can start it from terminal or reboot (Menu item should appear after reboot)'''

Mer/Documentation

2009-08-03T11:58:24Z

80.220.238.64: added skype

* [[Mer/Documentation/SDK|Software Development Kit]]
* [[Mer/Documentation/Getting_your_package_included|Getting your package included in repository]]
* [[Mer/Documentation/Making_x86_Mer_Bootable|Making x86 Mer bootable]]
* [[Mer/Documentation/Imager|Imager]]
* [[Mer/Documentation/Straightjacket_Packages|Straightjacket_Packages]]
* [[Mer/Documentation/Maemo_Compatible|Compatible closed source packages from Maemo]]
* [[Mer/Documentation/BME_Protocol]]
* [[Mer/Documentation/Bootmenu|Configuring own Boottargets]]
* [[Mer/Documentation/Installation|Installing Mer]]
* [[Mer/Documentation/AppCompat|Software Compatibility]]
* [[Mer/Documentation/Common_Packages|Common Packages]]
* [[Mer/Documentation/Creating_new_themes|Creating new themes for Mer]] (Unfinished)
* [[Mer/Documentation/USB_Networking]]
* [[Mer/Documentation/Sound]]
* [[Mer/Documentation/ARM CPU]]
* [[Mer/Documentation/Mer Package Patch Handling]]
* [[Mer/Documentation/N810_GPS|N810 GPS Instructions]]
* [[Mer/Documentation/Fluxbox|N810 Fluxbox how-to]]
* [[Mer/Documentation/Vala_control_panel|Control Panel applets in Vala]]
* [[Mer/Documentation/N8x0_Skype|Skype for Nokia n8x0]]
[[Category:Mer|Documentation]]

Mer/Documentation/N8x0 Skype

2009-08-03T11:56:15Z

80.220.238.64: Instructions to install skype

== How to install Skype on Nokia n8x0running Mer. ==

This is tested to be working on Mer 0.15, n810

First you'll have to add needed repositories:

In XTerminal:

sudo nano /etc/apt/sources.list.d/tableteer.list

copy/paste in following:

deb http://catalogue.tableteer.nokia.com/updates/diablo-3/ /
deb http://catalogue.tableteer.nokia.com/certified/ diablo user

Press Ctrl+x to close the editor and click "y" when it asks if you want to save changes.

Next, update repos:

sudo apt-get update

Then Install the skype:

sudo apt-get install skype

You'll face a bunch of problems, so a little dpkg --forcing is needed.

Run this: (one big command, don't split it)

sudo dpkg -i --force-overwrite /var/cache/apt/archives /libjinglebase0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/libjinglep2p0.3-0_0.3.12-3ubuntu1_armel.deb /var/cache/apt/archives/gstreamer0.10-plugins-farsight_0.12.10-2_armel.deb /var/cache/apt/archives/libfarsight0.1-3_0.1.28-2_armel.deb

Finalize the install:

sudo apt-get install -f

You can also remove the repository file to avoid future package conflicts:

sudo rm /etc/apt/sources.list.d/tableteer.list

That's it!
Skype should be installed now, if it doesn't show up in the application menu yet, you can start it from terminal or reboot (Menu item should appear after reboot)

Mer/Status

2009-07-18T15:44:06Z

80.220.238.64: /* Application Support */

== Hardware Support ==

Please help us to fill in this page.

{|class="wikitable"
!colspan="2"| Key
|-
| Y || Works
|-
| N || Doesn't work
|-
| ? || Unknown (Please help fill in these values)
|-
| - || Device doesn't have this
|}

{|class="wikitable"
|-
! Feature !! [[/770|770]] !! [[/N8x0|N800]] || [[/N8x0|N810]] || [[/SmartQ5|SmartQ5]] || [[/SmartQ7|SmartQ7]] || [[/FreeRunner|FreeRunner]] || [[/Loox|Loox]]
|-
!colspan="8"| Display
|-
|[[/X|X Display]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/3D|2D/3D Acceleration]] || ? || ? || ? || ? || ? || ? || ?
|-
|[[/Brightness|Brightness]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Ambient|Ambient light sensor]] || - || - || N || - || - || - || -
|-
|[[/Touch events|Touch events]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/LEDs|LEDs]] || ? || ? || ? || ? || ? || N || ?

|-
!colspan="8"| Buttons/Switches
|-
|[[/Headphone detect|Headphone detect]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Headset switch events|Headset switch events (via dbus)]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Keyboard|Keyboard]] || - || - || Y || - || - || - || ?
|-
|[[/Flaps|Battery cover/SD door events]] || ? || ? || ? || - || - || ? || -
|-
|[[/HW Buttons|HW Buttons (zoom,fullscreen, etc)]] || ? || Y || Y || ? || ? || N || ?
|-
|[[Pointing Device (D-Pad, etc)]] || ? || ? || ? || ? || ? || - || ?
|-
|[[/Power Button|Power Button]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Camera eject|Camera eject]] || - || ? || ? || - || - || - || -
|-
!colspan="8"|Ancillary Devices
|-
|[[/Sound|Sound]] || ? || Y || Y || ? || Y || ? || ?
|-
|[[/Wifi|Wifi]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Bluetooth|Bluetooth]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/USB|USB]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/GPS|GPS]] || - || - || ? || - || - || N || -
|-
|[[/Camera|Camera]] || - || ? || ? || - || - || - || ?
|-
|[[/Battery|Battery]] || ? || Y || Y || 50% || 50% || N || ?
|-
|[[/Power control|Power control]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/MMC reader|MMC reader]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/FM Radio|FM Radio]] || - || ? || - || - || - || - || -
|-
|[[/TV-OUT|TV-OUT]] || - || - || - || N || ? || - || ?
|}

== Application Support ==

{|class="wikitable"
|-
! Key Application !! Provided by
|-
|browser || Tear
|-
|email client || claws (or modest if anyone ports it)
|-
|book reader || fbreader
|-
|media player || gpodder or canola
|-
|text editor || maemopad+ etc
|-
|photo viewer || mirage
|-
|calendar || gpe-calendar (for now)
|-
|address book || gpe-contacts (for now)
|-
|file manager || finefm but it needs improvement, possibly pcmanfm?
|-
|instant messenger || pidgin (or empathy)
|-
|feed reader || rss-reader
|-
|alarm clock || alarm-clock from alarm-clock.pl ?

|}

[[Category:Mer]]

Mer/Status

2009-07-18T15:42:57Z

80.220.238.64: /* Application Support */

== Hardware Support ==

Please help us to fill in this page.

{|class="wikitable"
!colspan="2"| Key
|-
| Y || Works
|-
| N || Doesn't work
|-
| ? || Unknown (Please help fill in these values)
|-
| - || Device doesn't have this
|}

{|class="wikitable"
|-
! Feature !! [[/770|770]] !! [[/N8x0|N800]] || [[/N8x0|N810]] || [[/SmartQ5|SmartQ5]] || [[/SmartQ7|SmartQ7]] || [[/FreeRunner|FreeRunner]] || [[/Loox|Loox]]
|-
!colspan="8"| Display
|-
|[[/X|X Display]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/3D|2D/3D Acceleration]] || ? || ? || ? || ? || ? || ? || ?
|-
|[[/Brightness|Brightness]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Ambient|Ambient light sensor]] || - || - || N || - || - || - || -
|-
|[[/Touch events|Touch events]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/LEDs|LEDs]] || ? || ? || ? || ? || ? || N || ?

|-
!colspan="8"| Buttons/Switches
|-
|[[/Headphone detect|Headphone detect]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Headset switch events|Headset switch events (via dbus)]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Keyboard|Keyboard]] || - || - || Y || - || - || - || ?
|-
|[[/Flaps|Battery cover/SD door events]] || ? || ? || ? || - || - || ? || -
|-
|[[/HW Buttons|HW Buttons (zoom,fullscreen, etc)]] || ? || Y || Y || ? || ? || N || ?
|-
|[[Pointing Device (D-Pad, etc)]] || ? || ? || ? || ? || ? || - || ?
|-
|[[/Power Button|Power Button]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Camera eject|Camera eject]] || - || ? || ? || - || - || - || -
|-
!colspan="8"|Ancillary Devices
|-
|[[/Sound|Sound]] || ? || Y || Y || ? || Y || ? || ?
|-
|[[/Wifi|Wifi]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Bluetooth|Bluetooth]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/USB|USB]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/GPS|GPS]] || - || - || ? || - || - || N || -
|-
|[[/Camera|Camera]] || - || ? || ? || - || - || - || ?
|-
|[[/Battery|Battery]] || ? || Y || Y || 50% || 50% || N || ?
|-
|[[/Power control|Power control]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/MMC reader|MMC reader]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/FM Radio|FM Radio]] || - || ? || - || - || - || - || -
|-
|[[/TV-OUT|TV-OUT]] || - || - || - || N || ? || - || ?
|}

== Application Support ==

{|class="wikitable"
|-
! Key Application !! Provided by
|-
|browser || Tear
|-
|email client || claws (or modest if anyone ports it)
|-
|book reader || fbreader
|-
|media player || gpodder or canola
|-
|text editor || maemopad+ etc
|-
|photo viewer || mirage
|-
|calendar || gpe-calendar (for now)
|-
|address book || gpe-contacts (for now)
|-
|file manager || finefm but it needs improvement, possibly pcmanfm?
|-
|instant messenger || pidgin
|-
|feed reader || rss-reader
|-
|alarm clock || alarm-clock from alarm-clock.pl ?

|}

[[Category:Mer]]

Mer/Status

2009-07-18T15:41:31Z

80.220.238.64: /* Hardware Support */

== Hardware Support ==

Please help us to fill in this page.

{|class="wikitable"
!colspan="2"| Key
|-
| Y || Works
|-
| N || Doesn't work
|-
| ? || Unknown (Please help fill in these values)
|-
| - || Device doesn't have this
|}

{|class="wikitable"
|-
! Feature !! [[/770|770]] !! [[/N8x0|N800]] || [[/N8x0|N810]] || [[/SmartQ5|SmartQ5]] || [[/SmartQ7|SmartQ7]] || [[/FreeRunner|FreeRunner]] || [[/Loox|Loox]]
|-
!colspan="8"| Display
|-
|[[/X|X Display]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/3D|2D/3D Acceleration]] || ? || ? || ? || ? || ? || ? || ?
|-
|[[/Brightness|Brightness]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Ambient|Ambient light sensor]] || - || - || N || - || - || - || -
|-
|[[/Touch events|Touch events]] || Y || Y || Y || Y || Y || Y || ?
|-
|[[/LEDs|LEDs]] || ? || ? || ? || ? || ? || N || ?

|-
!colspan="8"| Buttons/Switches
|-
|[[/Headphone detect|Headphone detect]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Headset switch events|Headset switch events (via dbus)]] || ? || ? || ? || ? || Y || ? || ?
|-
|[[/Keyboard|Keyboard]] || - || - || Y || - || - || - || ?
|-
|[[/Flaps|Battery cover/SD door events]] || ? || ? || ? || - || - || ? || -
|-
|[[/HW Buttons|HW Buttons (zoom,fullscreen, etc)]] || ? || Y || Y || ? || ? || N || ?
|-
|[[Pointing Device (D-Pad, etc)]] || ? || ? || ? || ? || ? || - || ?
|-
|[[/Power Button|Power Button]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Camera eject|Camera eject]] || - || ? || ? || - || - || - || -
|-
!colspan="8"|Ancillary Devices
|-
|[[/Sound|Sound]] || ? || Y || Y || ? || Y || ? || ?
|-
|[[/Wifi|Wifi]] || ? || Y || Y || ? || ? || N || ?
|-
|[[/Bluetooth|Bluetooth]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/USB|USB]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/GPS|GPS]] || - || - || ? || - || - || N || -
|-
|[[/Camera|Camera]] || - || ? || ? || - || - || - || ?
|-
|[[/Battery|Battery]] || ? || Y || Y || 50% || 50% || N || ?
|-
|[[/Power control|Power control]] || ? || Y || Y || ? || ? || ? || ?
|-
|[[/MMC reader|MMC reader]] || ? || Y || Y || Y || Y || ? || ?
|-
|[[/FM Radio|FM Radio]] || - || ? || - || - || - || - || -
|-
|[[/TV-OUT|TV-OUT]] || - || - || - || N || ? || - || ?
|}

== Application Support ==

{|class="wikitable"
|-
! Key Application !! Provided by
|-
|browser || Tear (probably)
|-
|email client || claws (or modest if anyone ports it)
|-
|book reader || fbreader
|-
|media player || gpodder or canola
|-
|text editor || maemopad+ etc
|-
|photo viewer || mirage
|-
|calendar || gpe-calendar (for now)
|-
|address book || gpe-contacts (for now)
|-
|file manager || finefm but it needs improvement, possibly pcmanfm?
|-
|instant messenger || pidgin
|-
|feed reader || rss-reader
|-
|alarm clock || alarm-clock from alarm-clock.pl ?

|}

[[Category:Mer]]

Mer/Releases/0.15testing9

2009-07-17T09:14:39Z

80.220.238.64: /* Bugs in testing9 */

By using these testing images, you're '''morally obligated to test them''' and to edit this page and report -every single bug you find-, no matter if they're theme flaws, quirks, bugs or crashes. You can optionally also use [https://bugs.maemo.org/enter_bug.cgi?product=Mer bugzilla] , use version 0.15.

IF YOU SEE ANY MISSING TRANSLATIONS, PLEASE REPORT THEM IMMEDIATELY.

'''Please send the bug report urls to mer-chatter (see [[Mer/Awareness]] ) as well and share your bugs, testing experiences.'''

Test master is Meizirkki, and can be found in #mer on irc.freenode.net usually and you can ask him if there's some specialized areas that need testing. Take [http://guest:guest@trac.tspre.org:9010 the "Completed" things first]. If you are testing, go to #mer anyway. Good place to be.

These images will not be the only ones this week. In N8x0 installer, when it asks for URL=, write URL=http://the.image.intended. Instructions on [[Mer/Documentation/Installation]] still apply.

These images may potentially turn your device into a insane machine bent on removing humanity from this earth and may potentially brick your device, so, NO WARRANTY.

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-x86-generic-image-v0.15testing9.vmdk.zip Mer X86 VMDK]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-x86-generic-image-v0.15testing9.tar.gz Mer X86 rootfs version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-n8x0-standard-v0.15testing9.zImage Mer N8x0 kernel, not for JFFS version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-n8x0-image-v0.15testing9.tar.gz Mer N8x0, rootfs version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-n8x0-image-v0.15testing9.jffs2 Mer N8x0, JFFS version, use with JFFS kernel]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-n8x0-flashrootfs-v0.15testing9.zImage Mer N8x0 kernel, JFFS version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-smartq5-image-v0.15testing9.SmartQ5 Mer SmartQ5, firmware version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-smartq7-image-v0.15testing9.SmartQ7 Mer SmartQ7, firmware version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-smartq5-rootfs-v0.15testing9.tar.gz Mer SmartQ5, rootfs version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-smartq7-rootfs-v0.15testing9.tar.gz Mer SmartQ7, rootfs version]

[http://stskeeps.subnetmask.net/mer/0.15testing9/mer-armel-freerunner-rootfs-v0.15testing9.tar.gz Mer Freerunner, rootfs version, kernel in /boot]

For use with QEMU & KVM, download the Mer X86 VMDK version, unzip, and convert to a ''qcow2'' image with the ''qemu-img convert'' command.

<pre>
MD5sums:

a0db6ede7fba51e32ce514c50865be0f mer-armel-n8x0-flashrootfs-v0.15testing9.zImage
53541811f4b8d04d9a21ab59828e0d58 mer-armel-freerunner-rootfs-v0.15testing9.tar.gz
a0db6ede7fba51e32ce514c50865be0f mer-armel-n8x0-flashrootfs-v0.15testing9.zImage
2ae4d404623ed8bd2fd447e89cbbe54f mer-armel-n8x0-image-v0.15testing9.jffs2
f0f5d515073684d71fc3eed8ecf51662 mer-armel-n8x0-image-v0.15testing9.jffs2.raw
48013ddf8c99dd906a91e70037253126 mer-armel-n8x0-image-v0.15testing9.tar.gz
ff2ae5a7328c9ae668ae2b2b466b7e07 mer-armel-n8x0-standard-v0.15testing9.zImage
2cf1941fe0272d2de409ae6ebdb14402 mer-armel-smartq5-rootfs-v0.15testing9.tar.gz
61d34cf1bb6a95044db2e89782c86456 mer-armel-smartq5.SmartQ5
c995fd936a213af15313d2d34248792c mer-armel-smartq7-rootfs-v0.15testing9.tar.gz
ec9d30bb9cc0233f578d48dcbc0823c2 mer-armel-smartq7.SmartQ7
764e43e920b798c7dc43b586d587e601 mer-x86-generic-image-v0.15testing9.tar.gz
ec11a053063a2cc1b878a425e3742079 mer-x86-generic-image-v0.15testing9.vmdk.zip

</pre>

== Bugs in 0.15testing6 ==

* (in progress of getting fixed) - Chinese translations are broken.
* N8x0: Xorg acts weird
* N8x0: hald-addon-bme has "batery.reporing.last_full"
* Missing translations for default locale (En_US) mainly in Application manager (ai_ti_main, ai_li_size_100kb, ai_li_size_max_99kb, aibddetailsclose, ai_ia_select_location, ai_fi_select_location_application, ai_fi_select_location_location, aibdselectlocationok, aibdselectlocationcancel, ai_ni_install_sucessful) , but also in Settings ("tncpa_ap_tn_sb", "tncpa_ti_tnsb_title", "tncpa_fi_tnsb_applications", "tncpa_bv_tnsb_organise", basically most if not *all* that beging with "tncpa_", there is too many to retype here, almost nothing is translated there, apart from some names of applets)
* FineFileManager installed from Application Manager does not display any files nor directories and has missing icon in the bottom toolbar.
* Tear has missing "home" icon in bottom toolbar
* The "Are you sure you wish to reboot?" window is broken. It appears in the upper-left corner, without decoration, the left and top sides of the window are cut off. The strings for Yes and No buttons are missing ("wdgtbdyes" and "wdgtbdno"). By the way, this goes against many user interface guidelines. The buttons should say "Reboot" and "Cancel" instead of "Yes" and "No".
* The same issue as above applies to confirming shutdown and offline mode. Obviously, the buttons should be "Shut down/Cancel" and "Go Offline/Cancel", respectively.
* Cannot click on links while browsing with tear under Vmware image (vm bug or tear bug?)
* Mirage installed from Application Manager does not launch. Crashes on ImportError: No module named osso in /usr/share/mirage/mirage.py line 35 "import osso"
** Issue is due to python-osso not supporting python2.5 (stskeeps)
** Tested with launching using python2.6 instead of python2.5 (epage)
*** Mirage seems to not have any major compatibility issues between python versions
*** python-osso dependency then gets satisfied and the world is a happy place
* Missing icons in Terminal bottom toolbar [http://img219.imageshack.us/img219/6971/screenshot02.png Screenshot]
* Settings app entry should have an icon (not just the default one); [http://img44.imageshack.us/img44/7066/screenshot03r.png Screenshot]
* Inconsistency in icon size and style. Example: tear should have a bigger icon. Mer project should define a standard size for icons so that packagers know what icons they should pack in their app. [http://img44.imageshack.us/img44/6417/screenshot01y.png Screenshot]
* Installing (through app manager) an app shorcut to any other folder than "extras" has no effect. The app entry always end up in extras (I tried to install Tear in "Internet" -> ends up in "extras". Same for several apps).
* HomeIP applet installed from Application Manager, cannot be selected to show on homescreen (selecting it has no effect).
** python-hildondesktop broken?
* hildon-desktop-env needs dependancy on hildon-application-manager-l10n-public-enus1 hildon-common-strings-l10n-public-enus1 hildon-control-panel-l10n-public-enus1 hildon-fm-l10n-public-enus1 hildon-input-method-l10n-public-enus1 hildon-libs-l10n-public-enus1 ke-recv-l10n-public-enus1 maemo-af-desktop-l10n-public-enus1 osso-games-l10n-public-enus1 osso-system-lock-l10n-public-enus1 osso-uri-l10n-public-enus1

== Added strings to en_US ==

<pre>

In hildon-application-manager:

# This is the name of the top bar in HAM
msgid "ai_ti_main"
msgstr "Home"

msgid "ai_li_size_max_99kb"
msgstr "%d kB"

msgid "ai_li_size_100kb_10mb"
msgstr "%.1f MB"

msgid "ai_li_size_10mb_1gb"
msgstr "%d MB"

msgid "ai_li_size_larger_than_1gb"
msgstr "%.1f GB"

msgid "ai_li_de_size_max_999kb"
msgstr "%d kB"

msgid "ai_li_de_size_1mb_10mb"
msgstr "%.2f MB"

msgid "ai_li_de_size_10mb_1gb"
msgstr "%.1f MB"

msgid "ai_li_de_size_larger_than_1gb"
msgstr "%.2f GB"

msgid "ai_bd_details_close"
msgstr "Close"

msgid "ai_ia_select_location"
msgstr "Select location for application"

msgid "ai_fi_select_location_application"
msgstr "Application:"

msgid "ai_fi_select_location_location"
msgstr "Location"

msgid "ai_bd_select_location_ok"
msgstr "OK"

msgid "ai_bd_select_location_change_folder"
msgstr "Change folder"

msgid "ai_ni_install_successful"
msgstr "%s installed"

msgid "tncpa_li_plugin_update_notifier"
msgstr "Software Updates"

### From 20090711:

msgid "ai_ti_select_location"
msgstr "Select location"

In hildon-libs:

In hildon-input-method:

msgid "inpu_nc_common_menu_tools"
msgstr "Tools"

msgid "inpu_nc_common_menu_edit_cut"
msgstr "Cut"

msgid "inpu_nc_common_menu_edit_copy"
msgstr "Copy"

msgid "inpu_nc_common_menu_edit_paste"
msgstr "Paste"

msgid "inpu_nc_common_menu_tools_help"
msgstr "Help"

In hildon-fm: From 20090711

msgid "ckdg_bd_change_folder_ok"
msgstr "OK"

</pre>

== Bugs in testing7 ==

Mark if previous bugs were fixed in this version as well.

* The default terminal cannot be scrolled in any way. No scrollbar, does not react to touch.
* The strings still have "Nokia" and "Maemo" in them. They should be replaced with "Mer".
* At least for N8x0, it would be reasonable to double the backlight timeouts (60 for fade, 120 to disable). The device is just too slow for some actions to complete (especially in the terminal) within 30 seconds, making the default setup irritating.
* In the panel for changing brightness and volume, the volume icon is repeated in a grid. There should be only one icon there, not four.
* When a reboot or shutdown procedure is taking place, all the applets that change their state show up briefly on the screen, making the process look unpolished and ugly. There's also a blinking cursor showing through if you leave the terminal open while shutting down or rebooting. Basically, if there is anything on the screen during a reboot or shutdown that changes its state, it shows up.
* "Authorizations" menu element should be hidden. It's of no use to normal users.
* "Drag Lock" should be renamed to "Lock applets" or a similar, less confusing name.
* Erratic dialog window behaviour. Open up the terminal and hit the Menu key a few times to open the menu and close it repeatedly. It'll open left-aligned or centered, depending on your luck.
* Error dialog windows (banners on the bottom of the screen with a "stop sign" icon) cannot be dismissed in any other way than hitting the hardware "Back" button.
* Disable grab in gksu for n800/non-kbd users - it asks for password in locale settings.
* Chinese strings now working
* [Nokia n8x0]NetworkManager not working. NM-applet says "Device not ready".
* [Nokia n810]Fn-key not working. (Install x11-xkb-utils to fix)
** Added to imager (stskeeps)
* [Nokia n8x0]Powerlaunch dialog is not popping up when pressing power button.
(Note: if this is the "Device mode" dialog window then it works fine for me with an N810. Short press = Device mode appears. Long press = soft poweroff - TomaszD)
* [Nokia n8x0] Going to soft poweroff by pressing and holding the power button for about two seconds results in: backlight turns off, comes back for a second, then goes away and soft poweroff is completed. Same thing happens when coming back from soft poweroff, the screen softly "blinks" at the user. Blinking does not occur when going into soft poweroff when the option is chosen from the Device mode dialog, however it does happen every time when the device comes back from this mode.
* [Nokia n8x0] If going to soft poweroff is done by pushing and holding a button for two seconds, then it stands to reason that the same action should turn the device back into normal mode. This is not the case - only a short push of the button brings it back to life.
* Maemopad: Missing translations = maemopad_save_changes_made, maemopadyes, maemopadno. Open files menu is screwed up. Dialog to confirm saving is displayed on top left of screen instead of center.
** Maemopad has no en_US translation. https://stage.maemo.org/svn/maemo/projects/tools/trunk/maemo_testing/maemopad/po/en_GB.po is a possible basis. (Stskeeps)
* Missing text: Settings -> About -> License button
* Desktop Menu Issues
** Calibrate Screen menu item non-functional
** Help menu item non-functional
* NetworkManager Applet 0.7.0.97
** Clicking "NetworkManager Website" errors with "Failed to show url Failed to execute child process "xdg-open" (No such file or directory)"
** Clicking OK Button on above error message is non-functional
* statusbarapplets misses hook to CPA
* statusbarapplets tries to read $HOME.osso/hildon-desktop/statusbar.conf, not $HOME/.osso/hildon-desktop/statusbar.conf
* statusbarapplets title needs to be better and less upper cased.
* blueman does not install correctly - errors
* qtablet does not install correctly - errors
* Display issues
** Editing DSL Connection -> PPP Settings tab -> "Available to all users" has the letters "Av" garbled.
** Display issue: Editing DSL Connection -> PPP Settings tab -> Options below Available to all users" is not displayed on the screen.
** Display issue: Editing DSL Connection -> IPv4 Settings -> Button for "Editing IPv4 routes" is not fully displayed on the screen.
* Installed Applications not launching from the Main Menu
** File Manager (Fine File Manager alternative does launch)
** Help Application
** Address Book
** RSS News Reader
** PDF Viewer
** Global Search
*** Not sure how to diagnose for error messages... ideas? (mtc)

=== Bugs in testing7 - Localization Issues ===
* en_GB
** Virtual Keyboard Menu: "inpu_nc_common_menu_tools"
** Settings Menu: "tncpa_ap_tn_sb"
** Settings Menu, Title bar for above menu item: "tncpa_ti_tnsb_title"
** Settings Menu, Tab title: "tncpa_ti_tnsb_statusbar"
** Settings Menu, Marquee tab, First item: "tncpa_fi_tnsb_applications"
** Settings Menu, Marquee tab, First item, Button: " ... "
** Settings Menu, Marquee tab, First item, Button selected, Title bar: "tncpa_ti_of_title"
** Settings Menu, Marquee tab, First item, Button selected, All buttons...
** Application Manager, Title Bar: "ai_ti_main"
** Application Manager, Installed Applications, Size Column: "ai_li_size_100kb_10" and "ai_li_size_max_99kb"
** Application Manager, Available Applications, Size Column: "ai_li_size_100kb_10" and "ai_li_size_max_99kb"
** Application Manager, Available Applications, Install Error (or Update Error), Close Button: "ainibdclose"

== Bugs in testing9 ==
*
* apt-get complains with the error "ValueError: /usr/bin/python does not match the python default version. It must be reset to point to python2.6" when trying to install screen (and possibly other packages). This can be fixed by making /usr/bin/python point to python2.6 rather than /etc/alternatives/python, which ultimately points to python-launcher.
* Without the fix above, packages like python-gst0.10, python-pygame, python-numeric are broken. Probably most of python stuff is broken. To quickly fix python in testing9: sudo rm /usr/bin/python && sudo ln -s python2.6 /usr/bin/python
* The panel is limited to 4 icons. When there are more than 4 icons on the panel (nm-applet, blueman, advanced-power, advanced backlight, loadapplet), then the last one dissappears. You can click to the right of the last icon to bring up the menu with the rest of the icons, but there should be an icon in and of itself to indicate that some of the panel icons are hidden away.
* [n8x0] Fn key now works!
** The Fn key doesn't work while in the username/password/hostname wizard.
** The Fn key and dpad will stop working if layout is changed (setxkbmap)
* [n8x0] Power button (still?) doesn't work. Detected, but does not bring up the menu

* Application Manager - missing string - "ai_ti_select_location" (window title of selecting where in the menu to put the application icon).
** Added
* Application Manager - missing string - "ckdg_bd_change_folder_ok" (button confirming the change of the folder where to put the application icon).
** Added
* Blueman bluetooth manager works, but you have to click and hold to keep the main menu open, a tap simply opens it up and closes it immidiately.

* [n8x0] Tapping input fields with stylus doesn't bring up the keyboard. It work when tapping with a finger though. One fix is to bring up the control panel by entering "controlpanel" in a terminal. Then choose "Text Input Settings". From there you pick "On-Screen". If you here set "Launch finger keyboard" to never, you can use the stylus in most applications to bring up the keyboard.
SmartQ7 - User account generation at first boot doesn't show onscreen keyboard for "Confirm Password" dialogue box, continued blank OK
:white_gecko - I can't confirm this, on my freerunner the onscreenkeyboard appears for the password confirm dialog.

* [n8x0] Missing icons from advanced power buttons http://imgur.com/JB7xt

Q7 - Changing input settings/onscreen/launchfingerboaurd=with finger and stylus causes keyboard loss in xterm
* [Q7] Authorizations app layout flows text offscreen on details pane
* WPA networks are still greyed out.
* Xterm missing scrollbars
* Onscreenkeyboard has no cursor keys
* Hardware power button not mapped
* Application manager - Installed app dialogue box has no "OK" button
* Application Manager - Installed apps default to Extras Menu regardless of settings
* Maemopad - Open File dialogue blank, no text no icons
* Disconnecting external power freezes X (sometimes)
* ts_calibrate fails with "ts_open: No such file or directory"
* [n8x0] bootreason: charger will cause instability! (booting the device by plugging in charger)

* [SmartQ7] Application Manager freezes after installing an application or removing an application - success window notification stays on screen and application list does not reload. Have to halt application to continue.
* [SmartQ7] Menu System Problem - Several applications included in the image show up in the Extras menu and should be in other first tier menus instead (example: Network Connections should be in Communications, Tear should be in Internet)
* [SmartQ7] Installing an application results in the new application always being placed in the Extras menu.
* [SmartQ7] SD Card does not mount automatically - needed to add code to /etc/fstab (/dev/mmcblk1p1 /media/sd vfat defaults 0 0) to get it working - please consider adding to image
* [SmartQ7] Arrow keys on the face of the device (up/down) aren't turning pages in FBReader. Created vim.mod in user home directory with added lines of keycode 73 = Page_Up and keycode 74 = Page_Down. Then created 62xmodap file in /etc/start-hildon.d/ with code - #!/bin/sh on first line and xmodmap vim.mod on second line. This allows keys to work after boot. Hopefully this or another more elegant solution can be added to the image.
* [SmartQ7] Applications trying to access the file system have issues unless the SD card is mounted correctly.
* [SmartQ7] No method of power off seems to exist

Mer/About

2009-07-16T11:19:51Z

80.220.238.64: /* Screenshots */

__NOTOC__
<imagemap>Image:Mer-logo.png|left|160px
rect 0 0 160 136 [[Mer]]
desc none
</imagemap>
<div style="clear: left"></div>
== Background ==
Mer is a new operating system for small, mobile touch-screen devices.

It is Linux based and layers the best open-source elements of Nokia's Maemo platform over a modern Ubuntu base.

The goals of Mer include:
* Integrate the best solutions for a wide variety of small form-factor devices
* Encourage wider access to device capabilities through the Vendor Social Contract
* Demonstrably provide an easy route to market for vendors
* Dramatically reduce costs to vendors of supporting EOL hardware
* Focus, harness and support community contributions to the platform
* Encourage and ease migration of existing applications
* Support experimentation, innovation and development

== Mission ==
Mer platform development will be done in the open, with public SCM repository, bugtrackers, and Wiki-based blueprint discussion.

We should stop seeing the tablets as strictly under-powered embedded systems, and see them for what they really are: powerful, power-efficient, economical handheld computers.

==Frequently Asked Questions==
* What is Mer?
You did read the bit above? Oh, OK... from a user's point of view Mer aims to be a replacement for Maemo/Diablo.... but better! Note that we don't think it's there yet :)

* What can I do with it?
Ideally you could install and run any app that runs on Ubuntu or Maemo extras.
Of course some apps just need too much resource, or need a mouse or are closed; but most apps will run.

You can't do that in Maemo/Diablo.

* Does it run inside Diablo?
No. Mer runs instead of Diablo - but don't panic, you can dual boot from one to the other; so if Mer isn't good enough just yet you can switch back to Diablo. Eventually we hope you won't need Diablo at all :)

* Can I install it on an internal/external SD card? (how big?)
Yes! It needs about 1Gb of space. The simplest thing is to use an empty 2Gb card.

* How do I install it?
Go to the [[Mer/Documentation/Installation|installation page]]

== Status ==
Mer is new and [[Mer/Releases|constantly developing]] so the [[Mer/Status|status]] of support for hardware and applications is steadily improving.

== History ==
Mer has evolved from discussion around [[Maemo_Reconstructed|reconstructing Maemo]] and a desire to make a proof of concept system of these thoughts. The M-R PoC developed into Mer after it was realised that it was - indeed - a viable environment for both developers and end-users.

== Screenshots ==

Mer 0.14 Screenshots [[Mer/Releases/0.14#Screenshots|here]]

Mer/About

2009-07-16T11:17:45Z

80.220.238.64: /* Screenshots */

__NOTOC__
<imagemap>Image:Mer-logo.png|left|160px
rect 0 0 160 136 [[Mer]]
desc none
</imagemap>
<div style="clear: left"></div>
== Background ==
Mer is a new operating system for small, mobile touch-screen devices.

It is Linux based and layers the best open-source elements of Nokia's Maemo platform over a modern Ubuntu base.

The goals of Mer include:
* Integrate the best solutions for a wide variety of small form-factor devices
* Encourage wider access to device capabilities through the Vendor Social Contract
* Demonstrably provide an easy route to market for vendors
* Dramatically reduce costs to vendors of supporting EOL hardware
* Focus, harness and support community contributions to the platform
* Encourage and ease migration of existing applications
* Support experimentation, innovation and development

== Mission ==
Mer platform development will be done in the open, with public SCM repository, bugtrackers, and Wiki-based blueprint discussion.

We should stop seeing the tablets as strictly under-powered embedded systems, and see them for what they really are: powerful, power-efficient, economical handheld computers.

==Frequently Asked Questions==
* What is Mer?
You did read the bit above? Oh, OK... from a user's point of view Mer aims to be a replacement for Maemo/Diablo.... but better! Note that we don't think it's there yet :)

* What can I do with it?
Ideally you could install and run any app that runs on Ubuntu or Maemo extras.
Of course some apps just need too much resource, or need a mouse or are closed; but most apps will run.

You can't do that in Maemo/Diablo.

* Does it run inside Diablo?
No. Mer runs instead of Diablo - but don't panic, you can dual boot from one to the other; so if Mer isn't good enough just yet you can switch back to Diablo. Eventually we hope you won't need Diablo at all :)

* Can I install it on an internal/external SD card? (how big?)
Yes! It needs about 1Gb of space. The simplest thing is to use an empty 2Gb card.

* How do I install it?
Go to the [[Mer/Documentation/Installation|installation page]]

== Status ==
Mer is new and [[Mer/Releases|constantly developing]] so the [[Mer/Status|status]] of support for hardware and applications is steadily improving.

== History ==
Mer has evolved from discussion around [[Maemo_Reconstructed|reconstructing Maemo]] and a desire to make a proof of concept system of these thoughts. The M-R PoC developed into Mer after it was realised that it was - indeed - a viable environment for both developers and end-users.

== Screenshots ==

You can see the current release screenshots [[Mer/Releases/0.14#Screenshots|here]]

<gallery>
Image:Mer-screenshot-meiz-home.png
Image:Mer-screenshot-meiz-wifi.png
Image:Mer-screenshot-jaffa-ham.png
Image:Mer-screenshot-meiz-xchat.png
Image:Mer-screenshot-meiz-midori.png
</gallery>
[[Category:Mer|About]]