Maemo Wiki Mirror - User contributions [en]

Talk:Swappolube

2010-10-18T15:29:00Z

192.100.124.218: New page: <code>echo "1" > /proc/sys/vm/oom_kill_allocating_task</code> Doesn't this mean that OOM-badness heuristics are ignored and things like X, D-BUS can get killed? If yes, that means you've...

<code>echo "1" > /proc/sys/vm/oom_kill_allocating_task</code>

Doesn't this mean that OOM-badness heuristics are ignored and things like X, D-BUS can get killed? If yes, that means you've just radically increased the likelyhood of device reboots...

Documentation/devtools/maemo5/oprofile

2010-06-16T10:47:12Z

192.100.124.218: /* Profiling with callgraphs */

{{Devtools}}

== Description ==

Oprofile is a low overhead system-wide profiler for linux. It can be used to find CPU usage bottlenecks in the whole system and within processes.

== Packages ==

'''source''': oprofile

'''binary''': oprofile

== Installing Oprofile ==

=== Configuring the device ===

In order to run oprofile on your device an extra module will need to be installed. The oprofile kernel module is found in the kernel-modules-debug package, that can be installed from the tools repository.

=== Installing oprofile to the device ===

Provided that you have the Fremantle tools repository in your APT sources.list, the easiest way to install oprofile and the required kernel module is using apt.

<pre>
Nokia-N900-40-12:~# apt-get install oprofile kernel-modules-debug
</pre>

This will also install binutils.

=== Installing debug symbols ===

In order to view any useful profiling information at functions level, you will have to install debugging symbols. Debugging symbols normallycome with debugging (-dbg) packages. The easiest way to install all dbg packages required for a given binary is to use debug-dep-install script which comes with the maemo-debug-scripts package:

<pre>
Nokia-N900-40-12:~# apt-get install maemo-debug-scripts
Nokia-N900-40-12:~# debug-dep-install /usr/bin/osso-xterm.launch
</pre>

== Usage ==

1. On the device, type:

<pre>
Nokia-N900-40-12:~# insmod /lib/modules/current/oprofile.ko
Nokia-N900-40-12:~# opcontrol --no-vmlinux
Nokia-N900-40-12:~# opcontrol --separate=kernel
Nokia-N900-40-12:~# opcontrol -c 8
Nokia-N900-40-12:~# opcontrol --init
</pre>

Like with the ''--separate=library'' option, the ''--separate=kernel'' option separates the collected statistics per process and their components. In most use-cases cases processes (implicitly) request other processes like X server and hildon-desktop to do work for them. To optimize the CPU usage, you need to see which processes need to use most CPU and in which of its components (binary/libraries) in the whole system. The ''--separate=kernel'' option will additionally assign CPU usage within kernel under the processes that caused it. The vmlinux binary name is used for this part. The ''-c 8'' option will make oprofile collect information about the call graph, till the depth of 8 function calls.

2. Start the usecase you are interested in and type:

<pre>
Nokia-N900-40-12:~# opcontrol --reset
Nokia-N900-40-12:~# opcontrol --start
</pre>

3. When you've finished, type:

<pre>
Nokia-N900-40-12:~# opcontrol --stop
</pre>

Now you've collected the data.

=== Viewing profile reports ===

To see basic per-process picture, type opreport:

<pre>
Nokia-N900-40-12:~# opreport
CPU: OMAP GPTIMER, speed 0 MHz (estimated)
Counted GPTIMER_CYCLES events (32KiHz timer clock cycles between interrupts) with a unit mask of 0x00 (No unit mask) count 16
GPTIMER_CYCLES:16|
samples| %|
------------------
43666 88.5972 no-vmlinux
2636 5.3484 maemo-launcher
GPTIMER_CYCLES:16|
samples| %|
------------------
491 18.6267 no-vmlinux
450 17.0713 libclutter-eglx-0.8.so.0.800.2
410 15.5539 libgobject-2.0.so.0.2000.3
342 12.9742 libGLESv2.so
275 10.4325 libglib-2.0.so.0.2000.3
138 5.2352 libpthread-2.5.so
134 5.0835 libc-2.5.so
55 2.0865 libdbus-1.so.3.4.0
50 1.8968 hildon-desktop.launch
45 1.7071 libpango-1.0.so.0.2400.2
42 1.5933 libgdk-x11-2.0.so.0.1400.7
32 1.2140 libX11.so.6.2.0
32 1.2140 libpulsecommon-0.9.15.so
28 1.0622 libgtk-x11-2.0.so.0.1400.7
27 1.0243 libgio-2.0.so.0.2000.3
...
</pre>

After you know which processes and components are taking most of CPU, you need to find out the bottleneck functions/functionality in them. For this you need to install debug symbols for them.

Note: If with the ''--separate=kernel'' option there's a lot of CPU activity for kernel that's not assigned under any process, it means that the system/kernel is idle. If your use-case is (unexpectedly) slow despite system idling a lot, usually these kind of issues are related to locking and other inter-process interaction issues that cannot be analyzed by looking at the CPU usage.

To see more detailed symbol analysis use opreport -l:

<pre>
Nokia-N900-40-12:~# opreport -l /usr/bin/Xorg | more
warning: /no-vmlinux could not be found.
CPU: OMAP GPTIMER, speed 0 MHz (estimated)
Counted GPTIMER_CYCLES events (32KiHz timer clock cycles between interrupts) with a unit mask of 0x00 (No unit mask) count 16
samples % image name symbol name
313 51.7355 no-vmlinux /no-vmlinux
153 25.2893 Xorg /usr/bin/Xorg
36 5.9504 libpixman-1.so.0.15.3 /usr/lib/libpixman-1.so.0.15.3
31 5.1240 libc-2.5.so /lib/libc-2.5.so
11 1.8182 libexa.so /usr/lib/xorg/modules/libexa.so
10 1.6529 fbdev_drv.so /usr/lib/xorg/modules/drivers/fbdev_drv.so
10 1.6529 librecord.so /usr/lib/xorg/modules/extensions/librecord.so
8 1.3223 libsrv_um.so /usr/lib/libsrv_um.so
7 1.1570 libdbus-1.so.3.4.0 /usr/lib/libdbus-1.so.3.4.0
7 1.1570 libpthread-2.5.so /lib/libpthread-2.5.so
6 0.9917 libfb.so /usr/lib/xorg/modules/libfb.so
5 0.8264 libdri2.so /usr/lib/xorg/modules/extensions/libdri2.so
5 0.8264 librt-2.5.so /lib/librt-2.5.so
2 0.3306 libpvr2d.so /usr/lib/libpvr2d.so
1 0.1653 evdev_drv.so /usr/lib/xorg/modules/input/evdev_drv.so
</pre>

Once you know what functionality is a bottleneck, you need to find out whether your process should be (indirectly) causing the use of that functionality in the first place, is it using it too much/often or should the bottleneck functionality itself be optimized. Analysis of this falls to the corresponding process developers as only they know what their application is trying to achieve, why & how and before this kind analysis it's too early to assign/report bugs for lower level components.

=== Profiling with callgraphs ===

If you have initialized opcontrol with the ''-c'' option as described before, you should now be able to get call graphs for your applications. The textual information reported by opreport in these cases is a bit difficult to read, but there are ways to generate nice graphs out of them:
<pre>
Nokia-N900-40-12:~# opreport -l /usr/bin/Xorg -c > oprofile.log
#...copy the oprofile.log to your PC...
myPC$ cat oprofile.log | python gprof2dot.py -f oprofile | dot -Tpng -o callgraph.png
</pre>

You need the [http://jrfonseca.googlecode.com/svn/trunk/gprof2dot/gprof2dot.py gprof2dot.py] script and the ''dot'' tool, which is part of the [http://www.graphviz.org/ Graphviz] software (which is in Ubuntu's ''graphviz'' package).

=== Viewing reports from a PC ===

opreport -l, and especially opreport -c -l can take quite a long time when fired up on the devices. Therefore, it often makes sense to run opreport in scratchbox.

# Configure scratchbox target in a way that its binaries and libraries 100% match the target's.
# Collect profiling data as usual
# Copy contents of /var/lib/oprofile from the device to the corresponding directory in scratchbox target.
# in scratchbox, apt-get install maemo-debug-scripts (this may not be omitted)
# install debug packages either with debug-dep-install or by hand

Note: the binaries and libraries in the scratchbox target must match what's in the device, otherwise you will get bogus results.

=== Oprofile with kcachegrind ===

kcachegrind is a useful GUI tool for viewing performance data interactively. It comes with many modern linux distros.

To use it:

# Get the callgraph oprofile data (see above) and install the same packages also to scratchbox.
# Copy the profile data to scratchbox session as described above.
# install kcachegrind-converters package on HOST (debian, ubuntu)
# in scratchbox: opreport -gdf | op2calltree (you might want to copy op2calltree script somewhere on target)
# the resulting files can now be opened with kcachegrind on host, provided you set it to display ALL files (extensions are wrong)

== Links ==

* [oprofile man page](/development/documentation/man_pages/oprofile.html)
* http://oprofile.sourceforge.net/about/
* http://oprofile.sourceforge.net/doc/controlling.html
* http://kcachegrind.sourceforge.net/cgi-bin/show.cgi

== See Also ==

[[Documentation/devtools/maemo5/oprofileui|oprofileui]]

[[Category:Fremantle]]

Documentation/Maemo 5 Final SDK Installation

2010-05-27T13:08:44Z

192.100.124.218: /* Modified mmap related instructions */

=Introduction=

The following document describes the installation of the Maemo 5 Final SDK. Maemo SDK uses Scratchbox as the cross compilation environment into which Maemo specific development files are installed.

Before we begin with the installation, have a look at the minimum system requirements. We officially support x86-32 Debian based distributions, mainly Debian and Ubuntu though it is possible to install the SDK on other flavours of Linux too.

Once you are sure that your development machine fulfils these requirements, you can proceed with the following guidelines:

Maemo 5 SDK comes with two command line installation scripts and GUI installer (beta) to ease the SDK installation.
*Scratchbox installer script which downloads and installs the required version of Scratchbox onto your host machine.
*Maemo SDK installer which sets up two targets (armel and x86) inside Scratchbox, downloads the minimal rootstraps for both targets, and installs the open source development files based on the user selection during the installation process.
*GUI installer which combines both Scratchbox and SDK installation.

Maemo 5 SDK also provides the essential Nokia proprietary binary packages needed for Maemo development and additional Nokia applications in an authenticated repository. In order to have access to this repository, you will need to accept the End User License Agreement (EULA).   For the complete functionality and usability of the Maemo SDK, it is required to install Nokia proprietary binary packages in addition to the open source packages.

==What is not included in the Maemo SDK?==
Xephyr X11 server software is needed on your host machine before you can run any applications in the Maemo SDK. It is an X11 server that provides a device screen for the developer so that you can see all the Maemo application windows and visuals on your host machine. This software is not included in the SDK mainly because it is available on most linux distributions.

If you choose to install Maemo SDK using the GUI installer on Debian based systems, it will provide an option to install Xephyr for you.

If not, you can manually install Xephyr as follows:

On Debian based linux systems, Xephyr can be installed outside Scratchbox environment using apt with root permission:

$ sudo apt-get install xserver-xephyr

On a Gentoo system you need to install xorg-server with the kdrive useflag. This builds the Xephyr binary.

=Installing Maemo 5 SDK using GUI Installer=

Maemo 5 SDK installation is now made easy with GUI installer. This
installer will install Scratchbox and Maemo 5 SDK on Debian based
systems. This installer will allow installation of nokia closed packages and
applications provided that EULA at [http://tablets-dev.nokia.com/eula/index.php this webpage] is accepted.

'''GUI Installer has following features:'''
* Install/Upgrade Scratchbox
* Installation of Maemo 5 SDK
* Installation of nokia-binaries
* Installation of nokia-apps
* Installation of Xephyr, if missing
* Can create a launcher for Xephyr on Desktop
* Can create a shortcut to Scratchbox home folder on Desktop
* Can create Maemo 5 info page on Desktop that contains useful links for developers
* Uninstallation of scratchbox & targets (debian-based distros only)

GUI installer offers standard and custom installation modes in a wizard. Standard installation will use default settings, while custom offers more choices. Please note that standard mode will overwrite any of the standard targets (FREMANTLE_X86, FREMANTLE_ARMEL) if present, but contents of Scratchbox home will be preserved. Please use the custom mode if you don't want to overwrite your targets.

The GUI installer Qt application requires python bindings for Qt. GUI installer can install the required packages if not already installed.

The installer will use http_proxy environment variable if available. If
your connection doesn't seem to work, you will be asked to manually
enter proxy settings.

GUI installer has been tested on Ubuntu Karmic and Debian Lenny, both 32bit and 64bit versions. The GUI installer needs to download Maemo SDK so it requires a working Internet connection. On 64bit kernel, you need to disable VDSO for 32bit applications manually.

'''Starting installation with GUI installer:'''

There is some missing options in this python script if you run from non-debian linux systems you got errors, because it will not automatically define the installation path of scratchbox, to correct this errors you must patch this script.

Also you must uncheck Xephyr checkbox and install it manually.

129c129
< SB_PATH = "/scratchbox"
---
> SB_PATH = "/opt/scratchbox"
2297a2298
> opt = opt + "-s /opt/scratchbox"
2351a2353
> cmd = cmd +" -s /opt/scratchbox"

wget http://repository.maemo.org/stable/5.0/maemo-sdk-install-wizard_5.0.py
chmod a+x maemo-sdk-install-wizard_5.0.py

$ Installer requires root privileges
Ubuntu
sudo ./maemo-sdk-install-wizard_5.0.py
Debian
su -c ./maemo-sdk-install-wizard_5.0.py

'''Limitations:'''
*As the installer will do package installation, you should quit all package managers before running it.
*Please note that detecting scratchbox is not perfect and it will detect only if it is installed in /scratchbox path.
*Please note that python-qt features used in this installer might not be available in older ubuntu and debian distros.
*Due to differences in versions of Python Qt bindings, certain parts of installation can work differently on different systems.
*Installer only shows required settings on 64-bit machines but does not add them automatically.
*Installer will always use DISPLAY :2, if you want to use a different value, you need to change it manually.
*GUI installer doesn't work on SUSE Linux. You can use command line installers instead.

=Installing Maemo 5 SDK on x86-32 Debian based distribution=

1. Download the scratchbox installer and the Maemo SDK installer scripts. These are the same scripts as are available through Forum Nokia: [http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Platforms/Maemo/ Maemo SDK at Forum Nokia].

$ wget http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

2. Set the permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

3. Run the scratchbox installer with root permission specifying the username to be added to scratchbox users group and sbox group. The username should be an existing user name from the host linux system. This will download about 420 MB of material from the web, which is not resumeable if interrupted.

$ sudo ./maemo-scratchbox-install_5.0.sh -u $USER

4. The installation script adds the specified user to ‘sbox’ user group. For the group membership to be effective in the current terminal session, run the following command:

Note: This command will change the existing group ID during the current login session to ‘sbox’. If you do not want this change, just logout and log back in again for the group membership to be effective.

$ newgrp sbox

At this step, you should have a working Scratchbox environment ready.

5. Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the scratchbox environment. Set permission for 'user'before runing script.

$ sudo chmod +x ./maemo-sdk-install_5.0.sh
$ ./maemo-sdk-install_5.0.sh

If you have installed Scratchbox in a path alternative to /scratchbox, you will need to specify the path with ‘-s PATH’ option. More information on available command line options can be found with --help option
Follow the instructions on the go.

6. Once the script has successfully completed its execution, you can login into Scratchbox.

$ /scratchbox/login

If you are not able to login, take a look at the [[#Limitations of Scratchbox|limitations of Scratchbox]].

7. Proceed further to accept the EULA in order to obtain the Nokia proprietary binary packages. These Nokia binaries are essential for the complete functionality of the Maemo SDK.

7.1. Accept the EULA on [http://tablets-dev.nokia.com/eula/index.php this webpage] 
7.2. Copy the sources.list entry given to you after the license acceptance to your Scratchbox x86 and armel target’s /etc/apt/sources.list file. Execute the commands below on the _ARMEL and _X86 targets.

[sbox-FREMANTLE_X86: ~] > sb-conf select FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install nokia-binaries nokia-apps

[sbox-FREMANTLE_ARMEL: ~] > sb-conf select FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install nokia-binaries nokia-apps

The above step installs all needed Nokia proprietary binary packages along with the open source binaries that have dependencies to Nokia proprietary binary packages.
With this, your Maemo 5 SDK environment is set up completely and ready for development.

=Installing Maemo 5 SDK on openSUSE=
There are instructions at [http://en.opensuse.org/Maemo5 opensuse.org].

=Installing Maemo 5 SDK on non-Linux operating systems=

If you do not have a Linux environment (Windows or Mac OS X), you can install a [[Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_SDK_Virtual_Images|Maemo SDK virtual machine image]]
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com].
[http://www.vmware.com/products/player/ VMPlayer is required].

=Starting/Shutting down the SDK UI=

Before starting the UI framework, ensure that you have installed the following:
*Xephyr X11 server on the host machine outside the Scratchbox environment
*The SDK as described above
*The Nokia proprietary binary packages

1. Now, run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

Ubuntu 10.04 users using the package in the repositories will have to run the same command without the -host-cursor and -kb, however the terminal window will have to stay open.

2. Login to Scratchbox X86 target

$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.

See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~]>

3. Set the DISPLAY variable to match the display setting given for the Xephyr server.

[sbox-FREMANTLE_X86: ~] >export DISPLAY=:2

4. Start the UI framework .

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh start

5. You will now see the UI framework up and running on the Xephyr window.

6. You can shut down the UI framework as follows:

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh stop

=Installation of x86-64 Debian based distributions=
Since Scratchbox only supports x86-32 bit Linux host systems, we need to force the installation of x86-32 Scratchbox packages on the x86-64 bit machines. Using the -F option with the Scratchbox installation script can do this.

==Installation procedure==

*Download the Scratchbox installer and the Maemo SDK installer scripts.

$ wget -c http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

*Set permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

*Run the Scratchbox installer script as 'root user' with -F option, specifying the username to be added to Scratchbox users group sbox group as follows:

$ sudo ./maemo-scratchbox-install_5.0.sh -F -u $USER

*If you are running squeeze or intrepid or later, read [[#Limitations_of_Scratchbox]] before continuing.

Upon successful installation of Scratchbox, continue to run the Maemo 5 Final SDK Installer as instructed in the x86-32 installation.

=Starting Scratchbox on non-Debian based systems=
If Scratchbox was installed from Debian packages, the /etc/init.d/scratchbox-core init script is installed and Scratchbox should start automatically when the system is rebooted. However, if you have installed Scratchbox from tarballs, then rebooting your machine will clear away all the mounts and binfmt_misc registrations that Scratchbox requires to work. To get your Scratchbox working again after reboot, you have to run the following command as root:

$ sudo /scratchbox/sbin/sbox_ctl start

Alternatively you can add sbox_ctl as an init script to the /etc/init.d directory and create the appropriate links at your system's runlevel directories. This procedure works on some systems:

$ ln -s /scratchbox/sbin/sbox_ctl /etc/init.d/scratchbox-core
$ /usr/sbin/update-rc.d scratchbox-core defaults

Refer to your system's documentation for the correct instructions.

=Upgrading from Maemo 5 Beta2 SDK=

A smooth upgrade from beta2 to Final SDK is unfortunately not possible. Hence it is advised to freshly install the Final SDK. Before you do so, read through the instructions below.

Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges. The -u option in the Scratchbox installer has been updated to create the necessary symlinks. Running the installer with -u option when the Scratchbox has been already installed will just add the user and create symlinks. Running it for already existing user will check for the symlink and create it if needed.

Run the command below to create the symlink for existing Scratchbox user:

$ sudo ./maemo-scratchbox-install_5.0.sh -u <EXISTING_USER>

Alternatively, you can create the symlinks manually as follows, if Scratchbox is installed in the default location:

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

The Final SDK installer additionally creates a directory /opt under /target/<target_name>/.
'''Reason:''' In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation, we have to manually check whether /targets/<target_name>/opt is a symlink and if it is, remove it and create a directory with the same name.

=Upgrading from Maemo 4.x/Diablo SDK=
Due to the fact that there are API breaks in Fremantle, we cannot upgrade Diablo SDK to Fremantle. We can however have Fremantle Scratchbox targets co-exist with Diablo targets.

For this, we need to first upgrade the Scratchbox installation on our host machine.

*Download the Maemo5 scratchbox installer.

*Set executable permissions and run it as follows:

$ chmod a+x ./maemo-scratchbox-install_5.0.sh
$ sudo ./maemo-scratchbox-install_5.0.sh -U -u <EXISTING_USER> -s /scratchbox

Once the Scratchbox installation is done, run the Maemo 5 Final SDK installer.

=Manual Installation=

'''On x86-32 Debian based systems:'''

*You can add the following line into your host machine's /etc/apt/sources.list file.

deb http://scratchbox.org/debian/ maemo5-sdk main

*Install the needed Scratchbox packages with root permission

$ sudo apt-get update
$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

'''On x86-64 Debian based systems:'''

*Download the Scratchbox packages from [http://scratchbox.org/download/files/sbox-releases/branches/apophis/r4/deb/ here].

*Force the installation of the x86-32 packages with root permission as follows:

$ sudo dpkg -i --force-architecture scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

The Scratchbox packages will be unpacked to /scratchbox directory and the installation procedure will ask you some questions about the group and user accounts. Default group to Scratchbox is 'sbox'.

*Users who will be using Scratchbox should be added using the following command with root permission:

$ sudo /scratchbox/sbin/sbox_adduser USER yes

It will automatically include the user to the Scratchbox group, create user directories under /scratchbox/users and mount several directories (/dev, /proc, /tmp) under the user directory.

*Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges.

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

*For the group membership to be effective in the current terminal session, run the following command:

$ newgrp sbox

'''Note:''' This command will change the existing group ID during the current login session to 'sbox'. If you do not want to change, simply logout and log back in for the group membership to be effective.

*Log-in to Scratchbox.

$ /scratchbox/login

*Configure the scratchbox x86 and armel targets as follows:

[sbox->:~]>sb-conf st FREMANTLE_X86 -c cs2007q3-glibc2.5-i486 -d perl:debian-etch:doctools:svn:git -t none
[sbox->:~]>sb-conf st FREMANTLE_ARMEL -c cs2007q3-glibc2.5-arm7 -d qemu:perl:debian-etch:doctools:svn:git -t qemu-arm-sb

*Download the minimal rootstraps.

[sbox->:~]> wget http://repository.maemo.org/stable/5.0/armel/maemo-sdk-rootstrap_5.0_armel.tgz http://repository.maemo.org/stable/5.0/i386/maemo-sdk-rootstrap_5.0_i386.tgz

*Switch to x86 target, install the devkits, etc and fakeroot into the target, install the minimal rootstrap and finally the Maemo development files.

[sbox->:~]> sb-conf se FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_i386.tgz

*Some users seem to have problems downloading all files with apt http pipelining enabled. If you want to make sure or you get download errors like "104 connection reset by peer" at the fakeroot steps below, then disable http pipelining with the next command:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*either way, continue here:
[sbox-FREMANTLE_X86: ~] > sb-conf in -edFL
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install maemo-sdk-debug

The meta-package 'maemo-sdk-debug' installs all needed open source runtime, development and debug pakcages into the target. Use maemo-sdk-runtime if you want only runtime packages to be installed or user maemo-sdk-dev if you want only the runtime + development packages to be installed.

*Accept the EULA from [http://tablets-dev.nokia.com/eula/index.php here] to obtain the URL to access the Nokia binaries repository.

*Add the URL thus obtained to the Scratchbox target's /etc/apt/sources.list and do the following:

[sbox-FREMANTLE_X86: ~] >apt-get update
[sbox-FREMANTLE_X86: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation,

[sbox-FREMANTLE_X86: ~] >rm /targets/FREMANTLE_X86/opt
[sbox-FREMANTLE_X86: ~] >mkdir /targets/FREMANTLE_X86/opt

*Execute similar steps on the armel target too to set it up:

[sbox-FREMANTLE_X86: ~]> sb-conf se FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_armel.tgz

*again,the next command disables http pipelining, if you like:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*pipelining disabled or not, here we go again...
[sbox-FREMANTLE_ARMEL: ~] > sb-conf in -edFL
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install maemo-sdk-debug

*Add the same URL obtained above to access the Nokia binaries repository under /etc/apt/sources.list file of the Scratchbox armel target.

[sbox-FREMANTLE_ARMEL: ~] >apt-get update
[sbox-FREMANTLE_ARMEL: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*Create the /opt directory.

[sbox-FREMANTLE_ARMEL: ~] >rm /targets/FREMANTLE_ARMEL/opt
[sbox-FREMANTLE_ARMEL: ~] >mkdir /targets/FREMANTLE_ARMEL/opt

With this, you must now have both the targets setup and ready to use.

[[#Starting/Shutting down the SDK UI|Start the UI framework]].

=Un-installation=

Make sure that you have no process running inside Scratchbox. Uninstalling Scratchbox will remove everything that is installed and saved inside Scratchbox. Please take a backup of your files from Scratchbox user home directory if needed.

On Debian based systems, do the following with root permissions:

$ sudo apt-get remove scratchbox-* --purge
$ sudo rm -rf /scratchbox

On non-Debian based systems, you need to stop scratchbox as follows before removing it.

$ sudo /scratchbox/sbin/sbox_ctl stop
$ sudo rm -rf /scratchbox

=Limitations of Scratchbox=

The following limitations have been noted in the usage of Scratchbox:

==VDSO support==
Scratchbox does not work when VDSO32 support is enabled in the host's kernel. We're working on making it possible, but at the moment there are some workarounds, which are presented here.

If your host has VDSO32 turned on you will get an error like this when trying to login to Scratchbox.

No directory, logging in with HOME=/
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *)
ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!

==x86-64 kernel==

x86-64 Linux kernels starting from version 2.6.25 enable VDSO32 by default. To temporarily disable VDSO32 execute

sysctl abi.vsyscall32=0

On Linux kernel 2.6.24 <= you can disable VDSO32 by executing

sysctl vm.vdso_enabled=0

or

sysctl kernel.vdso=0

The current setting of VDSO32 can be verified by using sysctl. Only values 0 and 2 are compatible with Scratchbox. In our examples we use 0 (disable). 2 enables compat mode.

You can set all of these permanently by adding the following lines to /etc/sysctl.conf

vm.vdso_enabled = 0
abi.vsyscall32 = 0
kernel.vdso = 0

Save the file and run the command:

$ sudo sysctl -p

Please note the correct line depends on your Linux kernel version. When you execute sysctl -p you may get a warning about unknown keys. You can safely ignore those warnings as long as one of the 3 settings works.

'''WARNING :''' You should try setting these values by echoing them to the given locations before adding them to sysctl.conf to see if they cause any problems. For example, in some Ubuntu Gutsy installations, it has been observed that changing the VDSO settings will hang the system and thus making permanent changes in sysctl.conf may, in these cases, make your system unbootable.

=Known Issues in the SDK=

*A list of issues and their solutions can be found in the [[Developer_FAQ#Maemo_SDK_and_Scratchbox|Developer FAQ]] article

*Unnecessary warnings and debugging messages are printed out when the hildon application framework is started.

*Armel target does not bring up the UI framework

*It has been noted that Xephyr dies with the application framework at times. The crash in question might even be Xephyr related since the application framework behaves differently with different versions/builds of Xephyr. The case seems to be worst on Xephyr that comes with Ubuntu Jaunty, there Xephyr will die when running any application that contains an input field and clicking on that field with a mouse to invoke the input method. On Fedora Code 10 the Xephyr does not mind the mouse clicks but dies when shutting down the application framework. On the other hand Xephyr on Ubuntu Intrepid or even the Intrepid version recompiled for Jaunty does not experience crashing in these situations.

A patch is already available for the Xephyr on Ubuntu Jaunty and can be found at http://bugs.freedesktop.org/show_bug.cgi?id=21591. Binaries packages for [http://launchpadlibrarian.net/30330126/xserver-xephyr_1.6.3-1ubuntu2_i386.deb xserver-xephyr] package and its dependencies ([http://launchpadlibrarian.net/27533744/libgpg-error0_1.6-1ubuntu1_i386.deb libgpg-error0] and [http://launchpadlibrarian.net/28623981/libgcrypt11_1.4.4-2ubuntu2_i386.deb libcrypt11]) can be download from Ubuntu Jaunty repositories.

*The performance of clutter can be improved by enabling hardware acceleration if not enabled already. In some cases, it would require installing restricted/proprietary drivers (Eg: on host machines with ATI or NVidia graphics card). Refer to [[Maemo5 clutter performance]] for more details.

*Running Xephyr with -kb option disables entry of “@” symbol. However, removing -kb option disables cursor keys.

*Running Xephyr with -host-cursor is causing Xephyr to crash in Ubuntu Lucid and Debian Squeeze when the Hildon Application Framework is closed.

*Xephyr in Ubuntu Lucid does not support the -kb option anymore. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/531872

*In order to run ARMEL binaries in scratchbox the mmap_min_address needs to be set to 4096 or lower. Normally the SDK installer warns about that, but in Ubuntu Lucid the /proc entry is visible only to root, so the SDK installer can not see it. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568844 This also prevents qemu from checking the value, in which case it's assumed to be 0. Because of this, until the bug is fixed, the value should be set to 0 on Lucid.

[[Category:Scratchbox]]

Documentation/Maemo 5 Final SDK Installation

2010-05-27T11:47:32Z

192.100.124.218: /* Few corrections to Installing Maemo 5 SDK using GUI Installer */

=Introduction=

The following document describes the installation of the Maemo 5 Final SDK. Maemo SDK uses Scratchbox as the cross compilation environment into which Maemo specific development files are installed.

Before we begin with the installation, have a look at the minimum system requirements. We officially support x86-32 Debian based distributions, mainly Debian and Ubuntu though it is possible to install the SDK on other flavours of Linux too.

Once you are sure that your development machine fulfils these requirements, you can proceed with the following guidelines:

Maemo 5 SDK comes with two command line installation scripts and GUI installer (beta) to ease the SDK installation.
*Scratchbox installer script which downloads and installs the required version of Scratchbox onto your host machine.
*Maemo SDK installer which sets up two targets (armel and x86) inside Scratchbox, downloads the minimal rootstraps for both targets, and installs the open source development files based on the user selection during the installation process.
*GUI installer which combines both Scratchbox and SDK installation.

Maemo 5 SDK also provides the essential Nokia proprietary binary packages needed for Maemo development and additional Nokia applications in an authenticated repository. In order to have access to this repository, you will need to accept the End User License Agreement (EULA).   For the complete functionality and usability of the Maemo SDK, it is required to install Nokia proprietary binary packages in addition to the open source packages.

==What is not included in the Maemo SDK?==
Xephyr X11 server software is needed on your host machine before you can run any applications in the Maemo SDK. It is an X11 server that provides a device screen for the developer so that you can see all the Maemo application windows and visuals on your host machine. This software is not included in the SDK mainly because it is available on most linux distributions.

If you choose to install Maemo SDK using the GUI installer on Debian based systems, it will provide an option to install Xephyr for you.

If not, you can manually install Xephyr as follows:

On Debian based linux systems, Xephyr can be installed outside Scratchbox environment using apt with root permission:

$ sudo apt-get install xserver-xephyr

On a Gentoo system you need to install xorg-server with the kdrive useflag. This builds the Xephyr binary.

=Installing Maemo 5 SDK using GUI Installer=

Maemo 5 SDK installation is now made easy with GUI installer. This
installer will install Scratchbox and Maemo 5 SDK on Debian based
systems. This installer will allow installation of nokia closed packages and
applications provided that EULA at [http://tablets-dev.nokia.com/eula/index.php this webpage] is accepted.

'''GUI Installer has following features:'''
* Install/Upgrade Scratchbox
* Installation of Maemo 5 SDK
* Installation of nokia-binaries
* Installation of nokia-apps
* Installation of Xephyr
* Can create a launcher for Xephyr on Desktop
* Can create a shortcut to Scratchbox home folder on Desktop
* Can create Maemo 5 info page on Desktop that contains useful links for developers
* Uninstallation of scratchbox & targets (debian-based distros only)

GUI installer offers standard and custom installation modes in a wizard. Standard installation will use default settings, while custom offers more choices. Please note that standard mode will overwrite any of the standard targets (FREMANTLE_X86, FREMANTLE_ARMEL) if present, but contents of Scratchbox home will be preserved. Please use the custom mode if you don't want to overwrite your targets.

The GUI installer Qt application requires python bindings for Qt. GUI installer can install the required packages if not already installed.

The installer will use http_proxy environment variable if available. If
your connection doesn't seem to work, you will be asked to manually
enter proxy settings.

GUI installer has been tested on Ubuntu Karmic and Debian Lenny, both 32bit and 64bit versions. The GUI installer needs to download Maemo SDK so it requires a working Internet connection. On 64bit kernel, you need to disable VDSO for 32bit applications manually.

'''Starting installation with GUI installer:'''

There is some missing options in this python script if you run from non-debian linux systems you got errors, because it will not automatically define the installation path of scratchbox, to correct this errors you must patch this script.

Also you must uncheck Xephyr checkbox and install it manually.

129c129
< SB_PATH = "/scratchbox"
---
> SB_PATH = "/opt/scratchbox"
2297a2298
> opt = opt + "-s /opt/scratchbox"
2351a2353
> cmd = cmd +" -s /opt/scratchbox"

wget http://repository.maemo.org/stable/5.0/maemo-sdk-install-wizard_5.0.py
chmod a+x maemo-sdk-install-wizard_5.0.py

$ Installer requires root preveliges
Ubuntu
sudo ./maemo-sdk-install-wizard_5.0.py
Debian
su -c ./maemo-sdk-install-wizard_5.0.py

'''Limitations:'''
*As the installer will do package installation, you should quit all package managers before running it.
*Please note that detecting scratchbox is not perfect and it will detect only if it is installed in /scratchbox path.
*Please note that python-qt features used in this installer might not be available in older ubuntu and debian distros.
*Due to differences in versions of Python Qt bindings, certain parts of installation can work differently on different systems.
*Installer only shows required settings on 64-bit machines but does not add them automatically.
*Installer will always use DISPLAY :2, if you want to use a different value, you need to change it manually.

=Installing Maemo 5 SDK on x86-32 Debian based distribution=

1. Download the scratchbox installer and the Maemo SDK installer scripts. These are the same scripts as are available through Forum Nokia: [http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Platforms/Maemo/ Maemo SDK at Forum Nokia].

$ wget http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

2. Set the permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

3. Run the scratchbox installer with root permission specifying the username to be added to scratchbox users group and sbox group. The username should be an existing user name from the host linux system. This will download about 420 MB of material from the web, which is not resumeable if interrupted.

$ sudo ./maemo-scratchbox-install_5.0.sh -u $USER

4. The installation script adds the specified user to ‘sbox’ user group. For the group membership to be effective in the current terminal session, run the following command:

Note: This command will change the existing group ID during the current login session to ‘sbox’. If you do not want this change, just logout and log back in again for the group membership to be effective.

$ newgrp sbox

At this step, you should have a working Scratchbox environment ready.

5. Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the scratchbox environment. Set permission for 'user'before runing script.

$ sudo chmod +x ./maemo-sdk-install_5.0.sh
$ ./maemo-sdk-install_5.0.sh

If you have installed Scratchbox in a path alternative to /scratchbox, you will need to specify the path with ‘-s PATH’ option. More information on available command line options can be found with --help option
Follow the instructions on the go.

6. Once the script has successfully completed its execution, you can login into Scratchbox.

$ /scratchbox/login

If you are not able to login, take a look at the [[#Limitations of Scratchbox|limitations of Scratchbox]].

7. Proceed further to accept the EULA in order to obtain the Nokia proprietary binary packages. These Nokia binaries are essential for the complete functionality of the Maemo SDK.

7.1. Accept the EULA on [http://tablets-dev.nokia.com/eula/index.php this webpage] 
7.2. Copy the sources.list entry given to you after the license acceptance to your Scratchbox x86 and armel target’s /etc/apt/sources.list file. Execute the commands below on the _ARMEL and _X86 targets.

[sbox-FREMANTLE_X86: ~] > sb-conf select FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install nokia-binaries nokia-apps

[sbox-FREMANTLE_ARMEL: ~] > sb-conf select FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install nokia-binaries nokia-apps

The above step installs all needed Nokia proprietary binary packages along with the open source binaries that have dependencies to Nokia proprietary binary packages.
With this, your Maemo 5 SDK environment is set up completely and ready for development.

=Installing Maemo 5 SDK on openSUSE=
There are instructions at [http://en.opensuse.org/Maemo5 opensuse.org].

=Installing Maemo 5 SDK on non-Linux operating systems=

If you do not have a Linux environment (Windows or Mac OS X), you can install a [[Documentation/Maemo_5_Developer_Guide/Development_Environment/Maemo_SDK_Virtual_Images|Maemo SDK virtual machine image]]
from [http://tablets-dev.nokia.com/maemo-dev-env-downloads.php tablets-dev.nokia.com].
[http://www.vmware.com/products/player/ VMPlayer is required].

=Starting/Shutting down the SDK UI=

Before starting the UI framework, ensure that you have installed the following:
*Xephyr X11 server on the host machine outside the Scratchbox environment
*The SDK as described above
*The Nokia proprietary binary packages

1. Now, run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

Ubuntu 10.04 users using the package in the repositories will have to run the same command without the -host-cursor and -kb, however the terminal window will have to stay open.

2. Login to Scratchbox X86 target

$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.

See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~]>

3. Set the DISPLAY variable to match the display setting given for the Xephyr server.

[sbox-FREMANTLE_X86: ~] >export DISPLAY=:2

4. Start the UI framework .

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh start

5. You will now see the UI framework up and running on the Xephyr window.

6. You can shut down the UI framework as follows:

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh stop

=Installation of x86-64 Debian based distributions=
Since Scratchbox only supports x86-32 bit Linux host systems, we need to force the installation of x86-32 Scratchbox packages on the x86-64 bit machines. Using the -F option with the Scratchbox installation script can do this.

==Installation procedure==

*Download the Scratchbox installer and the Maemo SDK installer scripts.

$ wget -c http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

*Set permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

Users of Ubuntu 10.04 LTS will need to do the following to fix the installation, note that this may reduce system security! [http://talk.maemo.org/showpost.php?p=636394&postcount=8]

$ sudo su
$ echo "vm.mmap_min_addr = 0" >> /etc/sysctl.conf
$ sysctl -p
$ exit #to go back to user

*Run the Scratchbox installer script as 'root user' with -F option, specifying the username to be added to Scratchbox users group sbox group as follows:

$ sudo ./maemo-scratchbox-install_5.0.sh -F -u $USER

*If you are running squeeze or intrepid or later, read [[#Limitations_of_Scratchbox]] before continuing.

Upon successful installation of Scratchbox, continue to run the Maemo 5 Final SDK Installer as instructed in the x86-32 installation.

=Starting Scratchbox on non-Debian based systems=
If Scratchbox was installed from Debian packages, the /etc/init.d/scratchbox-core init script is installed and Scratchbox should start automatically when the system is rebooted. However, if you have installed Scratchbox from tarballs, then rebooting your machine will clear away all the mounts and binfmt_misc registrations that Scratchbox requires to work. To get your Scratchbox working again after reboot, you have to run the following command as root:

$ sudo /scratchbox/sbin/sbox_ctl start

Alternatively you can add sbox_ctl as an init script to the /etc/init.d directory and create the appropriate links at your system's runlevel directories. This procedure works on some systems:

$ ln -s /scratchbox/sbin/sbox_ctl /etc/init.d/scratchbox-core
$ /usr/sbin/update-rc.d scratchbox-core defaults

Refer to your system's documentation for the correct instructions.

=Upgrading from Maemo 5 Beta2 SDK=

A smooth upgrade from beta2 to Final SDK is unfortunately not possible. Hence it is advised to freshly install the Final SDK. Before you do so, read through the instructions below.

Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges. The -u option in the Scratchbox installer has been updated to create the necessary symlinks. Running the installer with -u option when the Scratchbox has been already installed will just add the user and create symlinks. Running it for already existing user will check for the symlink and create it if needed.

Run the command below to create the symlink for existing Scratchbox user:

$ sudo ./maemo-scratchbox-install_5.0.sh -u <EXISTING_USER>

Alternatively, you can create the symlinks manually as follows, if Scratchbox is installed in the default location:

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

The Final SDK installer additionally creates a directory /opt under /target/<target_name>/.
'''Reason:''' In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation, we have to manually check whether /targets/<target_name>/opt is a symlink and if it is, remove it and create a directory with the same name.

=Upgrading from Maemo 4.x/Diablo SDK=
Due to the fact that there are API breaks in Fremantle, we cannot upgrade Diablo SDK to Fremantle. We can however have Fremantle Scratchbox targets co-exist with Diablo targets.

For this, we need to first upgrade the Scratchbox installation on our host machine.

*Download the Maemo5 scratchbox installer.

*Set executable permissions and run it as follows:

$ chmod a+x ./maemo-scratchbox-install_5.0.sh
$ sudo ./maemo-scratchbox-install_5.0.sh -U -u <EXISTING_USER> -s /scratchbox

Once the Scratchbox installation is done, run the Maemo 5 Final SDK installer.

=Manual Installation=

'''On x86-32 Debian based systems:'''

*You can add the following line into your host machine's /etc/apt/sources.list file.

deb http://scratchbox.org/debian/ maemo5-sdk main

*Install the needed Scratchbox packages with root permission

$ sudo apt-get update
$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

'''On x86-64 Debian based systems:'''

*Download the Scratchbox packages from [http://scratchbox.org/download/files/sbox-releases/branches/apophis/r4/deb/ here].

*Force the installation of the x86-32 packages with root permission as follows:

$ sudo dpkg -i --force-architecture scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

The Scratchbox packages will be unpacked to /scratchbox directory and the installation procedure will ask you some questions about the group and user accounts. Default group to Scratchbox is 'sbox'.

*Users who will be using Scratchbox should be added using the following command with root permission:

$ sudo /scratchbox/sbin/sbox_adduser USER yes

It will automatically include the user to the Scratchbox group, create user directories under /scratchbox/users and mount several directories (/dev, /proc, /tmp) under the user directory.

*Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges.

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

*For the group membership to be effective in the current terminal session, run the following command:

$ newgrp sbox

'''Note:''' This command will change the existing group ID during the current login session to 'sbox'. If you do not want to change, simply logout and log back in for the group membership to be effective.

*Log-in to Scratchbox.

$ /scratchbox/login

*Configure the scratchbox x86 and armel targets as follows:

[sbox->:~]>sb-conf st FREMANTLE_X86 -c cs2007q3-glibc2.5-i486 -d perl:debian-etch:doctools:svn:git -t none
[sbox->:~]>sb-conf st FREMANTLE_ARMEL -c cs2007q3-glibc2.5-arm7 -d qemu:perl:debian-etch:doctools:svn:git -t qemu-arm-sb

*Download the minimal rootstraps.

[sbox->:~]> wget http://repository.maemo.org/stable/5.0/armel/maemo-sdk-rootstrap_5.0_armel.tgz http://repository.maemo.org/stable/5.0/i386/maemo-sdk-rootstrap_5.0_i386.tgz

*Switch to x86 target, install the devkits, etc and fakeroot into the target, install the minimal rootstrap and finally the Maemo development files.

[sbox->:~]> sb-conf se FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_i386.tgz

*Some users seem to have problems downloading all files with apt http pipelining enabled. If you want to make sure or you get download errors like "104 connection reset by peer" at the fakeroot steps below, then disable http pipelining with the next command:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*either way, continue here:
[sbox-FREMANTLE_X86: ~] > sb-conf in -edFL
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install maemo-sdk-debug

The meta-package 'maemo-sdk-debug' installs all needed open source runtime, development and debug pakcages into the target. Use maemo-sdk-runtime if you want only runtime packages to be installed or user maemo-sdk-dev if you want only the runtime + development packages to be installed.

*Accept the EULA from [http://tablets-dev.nokia.com/eula/index.php here] to obtain the URL to access the Nokia binaries repository.

*Add the URL thus obtained to the Scratchbox target's /etc/apt/sources.list and do the following:

[sbox-FREMANTLE_X86: ~] >apt-get update
[sbox-FREMANTLE_X86: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation,

[sbox-FREMANTLE_X86: ~] >rm /targets/FREMANTLE_X86/opt
[sbox-FREMANTLE_X86: ~] >mkdir /targets/FREMANTLE_X86/opt

*Execute similar steps on the armel target too to set it up:

[sbox-FREMANTLE_X86: ~]> sb-conf se FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_armel.tgz

*again,the next command disables http pipelining, if you like:
[sbox-FREMANTLE_X86: ~] > echo 'Acquire::http::Pipeline-Depth "0";' >> /etc/apt/apt.conf.d/00maemo

*pipelining disabled or not, here we go again...
[sbox-FREMANTLE_ARMEL: ~] > sb-conf in -edFL
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install maemo-sdk-debug

*Add the same URL obtained above to access the Nokia binaries repository under /etc/apt/sources.list file of the Scratchbox armel target.

[sbox-FREMANTLE_ARMEL: ~] >apt-get update
[sbox-FREMANTLE_ARMEL: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*Create the /opt directory.

[sbox-FREMANTLE_ARMEL: ~] >rm /targets/FREMANTLE_ARMEL/opt
[sbox-FREMANTLE_ARMEL: ~] >mkdir /targets/FREMANTLE_ARMEL/opt

With this, you must now have both the targets setup and ready to use.

[[#Starting/Shutting down the SDK UI|Start the UI framework]].

=Un-installation=

Make sure that you have no process running inside Scratchbox. Uninstalling Scratchbox will remove everything that is installed and saved inside Scratchbox. Please take a backup of your files from Scratchbox user home directory if needed.

On Debian based systems, do the following with root permissions:

$ sudo apt-get remove scratchbox-* --purge
$ sudo rm -rf /scratchbox

On non-Debian based systems, you need to stop scratchbox as follows before removing it.

$ sudo /scratchbox/sbin/sbox_ctl stop
$ sudo rm -rf /scratchbox

=Limitations of Scratchbox=

The following limitations have been noted in the usage of Scratchbox:

==VDSO support==
Scratchbox does not work when VDSO32 support is enabled in the host's kernel. We're working on making it possible, but at the moment there are some workarounds, which are presented here.

If your host has VDSO32 turned on you will get an error like this when trying to login to Scratchbox.

No directory, logging in with HOME=/
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *)
ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!

==x86-64 kernel==

x86-64 Linux kernels starting from version 2.6.25 enable VDSO32 by default. To temporarily disable VDSO32 execute

sysctl abi.vsyscall32=0

On Linux kernel 2.6.24 <= you can disable VDSO32 by executing

sysctl vm.vdso_enabled=0

or

sysctl kernel.vdso=0

The current setting of VDSO32 can be verified by using sysctl. Only values 0 and 2 are compatible with Scratchbox. In our examples we use 0 (disable). 2 enables compat mode.

You can set all of these permanently by adding the following lines to /etc/sysctl.conf

vm.vdso_enabled = 0
abi.vsyscall32 = 0
kernel.vdso = 0

Save the file and run the command:

$ sudo sysctl -p

Please note the correct line depends on your Linux kernel version. When you execute sysctl -p you may get a warning about unknown keys. You can safely ignore those warnings as long as one of the 3 settings works.

'''WARNING :''' You should try setting these values by echoing them to the given locations before adding them to sysctl.conf to see if they cause any problems. For example, in some Ubuntu Gutsy installations, it has been observed that changing the VDSO settings will hang the system and thus making permanent changes in sysctl.conf may, in these cases, make your system unbootable.

=Known Issues in the SDK=

*A list of issues and their solutions can be found in the [[Developer_FAQ#Maemo_SDK_and_Scratchbox|Developer FAQ]] article

*Unnecessary warnings and debugging messages are printed out when the hildon application framework is started.

*Armel target does not bring up the UI framework

*It has been noted that Xephyr dies with the application framework at times. The crash in question might even be Xephyr related since the application framework behaves differently with different versions/builds of Xephyr. The case seems to be worst on Xephyr that comes with Ubuntu Jaunty, there Xephyr will die when running any application that contains an input field and clicking on that field with a mouse to invoke the input method. On Fedora Code 10 the Xephyr does not mind the mouse clicks but dies when shutting down the application framework. On the other hand Xephyr on Ubuntu Intrepid or even the Intrepid version recompiled for Jaunty does not experience crashing in these situations.

A patch is already available for the Xephyr on Ubuntu Jaunty and can be found at http://bugs.freedesktop.org/show_bug.cgi?id=21591. Binaries packages for [http://launchpadlibrarian.net/30330126/xserver-xephyr_1.6.3-1ubuntu2_i386.deb xserver-xephyr] package and its dependencies ([http://launchpadlibrarian.net/27533744/libgpg-error0_1.6-1ubuntu1_i386.deb libgpg-error0] and [http://launchpadlibrarian.net/28623981/libgcrypt11_1.4.4-2ubuntu2_i386.deb libcrypt11]) can be download from Ubuntu Jaunty repositories.

*The performance of clutter can be improved by enabling hardware acceleration if not enabled already. In some cases, it would require installing restricted/proprietary drivers (Eg: on host machines with ATI or NVidia graphics card). Refer to [[Maemo5 clutter performance]] for more details.

*Running Xephyr with -kb option disables entry of “@” symbol. However, removing -kb option disables cursor keys.

*Running Xephyr with -host-cursor is causing Xephyr to crash in Ubuntu Lucid and Debian Squeeze when the Hildon Application Framework is closed.

*Xephyr in Ubuntu Lucid does not support the -kb option anymore. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/531872

*In order to run ARMEL binaries in scratchbox the mmap_min_address needs to be set to 4096. Normally the SDK installer warns about that, but in Ubuntu Lucid the /proc entry is visible only to root, so the SDK installer can not see it. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568844

[[Category:Scratchbox]]

Easy Debian

2010-05-19T11:58:49Z

192.100.124.218: /* Install instructions: */

This package, when installed, will give you OpenOffice.org, Gimp, the LXDE Desktop Environment, Evince, Firefox (called Iceweasel in Debian) with Java and Flash support, printing support, and access to thousands of precompiled applications from [http://www.debian.org Debian] that can be easily browsed and downloaded. All these applications will be installed in an image file containing the Debian operation system without interfering with Maemo, but taking advantage of its infrastructure and connectivity.

This package will give you all of these applications without any need for installing dependencies or other applications, and it should work on all of the tablets.

== What you need: ==

* You need 2.5 GB free on one of your memory cards, although after installing, you will only need 2 GB.
* You need to keep your expectations reasonable. Big desktop applications like OpenOffice and Firefox run slowly on the tablet. They are power-hungry and designed for big, powerful CPUs. The [[Nokia N810|N8x0's]] processor is comparable to a Pentium II processor. Just imagine running these apps on your computer from the mid-90s (remember Windows 95?), and you'll get the idea. But sometimes, you really need something on the tablet that only these apps can provide, like MS Word compatibility or Java applets. On the [[Nokia N900|N900]], almost all applications run reasonably fast once loaded, but they often take somewhat long to launch.

== Install instructions: ==

* You need to install the easy-deb-chroot package. It can be found in the [[Extras]] repository. There may be a newer version in the "Extras-devel" repository. (Enabling Extras-devel is a dangerous area and you should disable it as soon as you are done installing Easy Debian, but Easy Debian is rather safe and it is optified.)

* Once installed several new shortcut icons will be available on the applications menu. You will need to first run the one called "Debian Image Installer". A terminal program will open and ask you where to place the image file (after decompression it will be a 2 GB file), either on the [[Nokia N900|N900's]] built in storage (under MyDocs), or on an external MicroSD card (if available). That will start the download of the compressed image (about 300 MB) and eventual extraction of the image file. It may take more than 15 minutes to download if you have fast Internet connection, and another 30 minutes or more to extract it on your tablet. Make sure that there are no other processes running and that the extraction is not interrupted.
: You can check for a successful download and extraction by typing "ls -l MyDocs/debian*" in XTerminal. The compressed image name has the ending .img.ext2.lmza; when decompressed the file name ends in .img.ext2 and it should have a file size of exactly 2147483648 bytes.

* This step is an alternate way to do the previous step: You can manually download the image file from [http://qole.org/files//debian-m5-v3d.img.ext2.lzma here]. Afterward you will have to copy it into <code>/home/user/MyDocs/</code> or into <code>/media/mmc1/</code> depending on whether you want it installed on the internal storage or on a removable storage. Then, when you run "Debian Image Installer" it will detect that you already have the file and proceed to extract it and set it up for you. If you have a faster computer with programs to unpack [http://en.wikipedia.org/wiki/Lzma lzma]-compressed files, you may also skip the Debian Image Installer by copying the uncompressed file by USB to the <code>/home/user/MyDocs/</code> folder.

* If you have more than one image file, you should edit /home/user/.chroot to select the one you want to load. Default is first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*

* Finally, when you get the "Congratulations!" message, REBOOT.

== Easy Debian application icons ==

Easy Debian installs the following shortcuts in the Application Manager:

; Close Debian : for unmounting the Debian image and shutting down all running Debian processes

; Deb Img Install : for the initial download and extraction of the Debian image. For installing a new version of the Debian image from http:qole.org/files, delete the old image (or move/rename it appropriately) and rerun Deb Img Install.

; Debian chroot : this runs "sudo debian" in XTerminal, which gives root access to the Debian image. This can be used for modifying the Debian image and installing further applications from the command line. The root file system of Maemo is not visible from within Debian chroot, except /home and /home/user/MyDocs, so you cannot ruin the Maemo firmware from here.

; Debian LXDE : this launches the [http://lxde.org Lightweight X11 Desktop Environment] from where you can start all installed Debian application. Alternatively, you can start Debian applications from XTerminal with "debbie" (see below).

; Fix LXDE kbd : fixing lost keyboard focus in LXDE (see below)

; GNOME ALSA mix : for configuring sound

; Iceweasel Web B : unbranded Debian version of the Firefox Web Browser

; OpenOffice : for starting OpenOffice without LXDE

; Set Deb HW Keys : additional useful keybindings (see below)

; Synaptic Pkg Mg : graphical interface for installing additional Debian applications (in the Debian image only, not Maemo proper)

== Using the LXDE Environment: ==

* To launch a session of LXDE (a light weight desktop environment) whith several applications already installed in it, including OpenOffice.org, simply click on the "Debian LXDE" icon shortcut on the application menu.
* LXDE's application menu is found at the top left corner of the screen.
* To momentarily go back into the Maemo environment, simply press Ctrl Backspace.
* Exiting LXDE: Log out, don't just close the window. Make sure to have LXDE closed properly before powering down the device, it will not function properly when started next time before doing the next proper shutdown.

=== Window is too big for the screen ===

Press Ctrl and the period key simultaneously. This will make the "Move Window" cursor appear (a cross with four arrows). Use the stylus to drag the window to expose the parts that are not visible.

=== LXDE Top Menu Disappears ===

The newest version of the Easy Debian image (m5-v3b) has a new LXDE version.

If you upgrade Easy Debian and your LXDE top menu disappears, you can do one of two things:
* Install the newest version (m5-v3d): Close Easy Debian (use the icon with the red arrow and box), delete the old image (use the File Manager to do this), and then use the "Deb Img Install" icon to download and extract the new image.
* Keep your old image, and fix the top menu manually. Start LXDE. Tap and hold on a blank area of the left-side bar. Choose "Create New Panel". Choose "Top" and "OK". Tap and hold on new top panel. In the ''General'' tab, set the following things: Alignment: Left, Width: 25, Height: 32, Properties: Uncheck "Reserve Space..." In the ''Panel Applets'' tab, Add "Menu", "Digital Clock", "System Tray" (check "Stretch" column), "Net status monitor" (use edit button and change eth0 to wlan0, then tap on icon and set to wlan0 there too), and "CPU Usage Monitor".

If after the upgrade some menu entries (e.g. Gimp) are missing, you can manually install them from the Debian chroot terminal by

xdg-desktop-menu install --novendor /usr/share/applications/gimp.desktop

In order to have the document viewer Evince show up in the LXDE menu, you would have to first set "NoDisplay=false" in /usr/share/applications/evince.desktop and then run xdg-desktop-menu similar to above.

=== Keyboard issues and tips ===

It may happen that the hardware keyboard stops working in LXDE. It can be restored by hitting the power button and then tapping outside the menu or also by using the "Fix LXDE keyboard" application icon (in the Hildon Application Manager, which can be reached - if Ctrl+Backspace still works - from the Task Manager). The power button trick is usually both quicker and more reliable.

==== Localization ====

The keyboard in LXDE is by default US. To get a different keyboard layout for the LXDE window manager, you have to modify the Debian image which requires root privileges.
For this,
launch the "Debian chroot" app (icon with red swirl symbol), which opens a terminal with root access to the Debian image (as well as to your home directory). The following instructions assume that you are working from that terminal and not from within the LXDE window manager.

For the task of configuring a special keyboard layout for LXDE (German in the following example), start an editor of your choice in the Debian chroot terminal (e.g., leafpad), and insert the appropriate keymap label in the following line of /etc/xdg/lxsession/LXDE/autostart according to:

@setxkbmap de

Available keymaps are: ch (Swiss), cz and cz_qwerty (Czech), dano (Danish/Norwegian), fise (Finnish/Swedish), nordic (Danish/Norwegian/Finnish/Swedish), de (German), fr (French), it (Italian), pl (Polish), ptes (Portuguese/Spanish), ru (Russian).

You may also wish to set the language environment under Debian to a non-US one so that system messages come in your native language. This can be done by issuing the command (again from within the Debian chroot terminal)

dpkg-reconfigure locales

and selecting from the list that is then displayed the UTF variant of the desired language, for example for German, de_DE.UTF-8.

With older Easy Debian images (up to v3b) and in languages other than da, de, en, fr, and sv, this breaks the script that starts LXDE, because $CHROOT/usr/bin/xephwm5 has a line

export TWOWIN=`wmctrl -l | grep -i Information | awk '{print $1}'`

and "Information" does not match any longer. If in your language "Information" begins with "Info...", you can fix this by shortening "Information" to "Info" in the above line of /usr/bin/xephwm5. If not, you should modify the script to match the string that appears as title of the window saying "Welcome to Easy Debian LXDE..." (Without the above fix, clicking on the OK button will hang the program. You should instead get to the task manager and kill LXDE from there.)
In the new image this is fixed (for all languages).

==== Set Deb HW Keys app and xbindkeys ====

The newest version of Easy Debian provides also a "Set Deb HW Keys" application which runs xbindkeys, mapping Fn+Shift+(upper row keys) of the hardware keyboard to function keys F1-F12. Here the Fn (blue arrow) key has to be pressed first, which is best done by pressing with the thumb and rolling down to also press the Shift key. The function keys are sometimes needed to get in and out of certain modes of programs in particular when started from the desktop (often F1 for help; F5 for presentation or navigator mode; F11 for "Styles and Formatting" in Openoffice.) Moreover, Ctrl+Up and Ctrl+Space provide full screen toggles.

Under LXDE, the Enter key is actually KP_Enter, while some application only accept ordinary "Return". For this eventuality, "Set Deb HW Keys" maps Shift+Enter to Return.

You can edit /home/user/.xbindkeysrc to include more key mappings that you might find desirable in the absence of the virtual keyboard (which on the N900 in Debian chroot is only accessible in the XTerminal). For example
<pre>
"xvkbd -xsendevent -text '\e'"
Shift + BackSpace
</pre>
maps Shift+BackSpace to Escape. (See e.g. http://linux.die.net/man/1/xbindkeys and http://linux.die.net/man/1/xvkbd for more possibilities.)

You can have xbindkeys started also automatically by including

@xbindkeys -f /home/user/.xbindkeysrc

in /etc/xdg/lxsession/LXDE/autostart.

Note that the relevant file /home/user/.xbindkeysrc does not reside in the Debian image but in the home directory. If you upgrade to new versions of Easy Debian, and this file already exists, it will not be overwritten, but the package will install instead a newer version in /home/user/.xbindkeysrc.dist.

It is then up to you to merge new additions to your existing /home/user/.xbindkeysrc file, or if you have not modified it to your needs, to simply take it over by typing in the XTerminal
cp .xbindkeysrc .xbindkeysrc.old
cp .xbindkeysrc.dist .xbindkeysrc

Another work-around for getting additional special characters is to [[Remapping_keyboard|remap your hardware keyboard]].

A known issue is that in national keyboards where Up and Down arrows are composed as Fn+Left/Right arrows, Up and Down do not work under LXDE. If applications cannot be used without Up and Down keys, those should better be started outside of LXDE with debbie.

==== sticky keys hack ====

In the v3b image, /etc/xdg/lxsession/LXDE/autostart includes a hack to have sticky Shift and Fn keys also in LXDE. You can activate this behavior also outside of LXDE by running "debbie stickykeys" (or "debbie stickykeys xx" where xx is a language code different from us). Note however that this also affects XTerminal applications in Maemo.

The sticky keys hack also makes Ctrl sticky and may have other unexpected effects with non-US keyboards. To disable this feature in LXDE, comment out (include #'s in the beginning of) the following two lines in /etc/xdg/lxsession/LXDE/autostart according to

#xkbset exp 60 =sticky =twokey =latchlock
#xkbset sticky -twokey latchlock

In the newest image (v3d), the sticky keys hack is not enabled by default. To enable it, remove the #'s.

== Using debbie ==

From XTerminal the following scripts are available:

; debbie : starts debian chroot shell as user (doesn't evaluate /home/user/.profile)

; debbie ''command'' : runs debian command as user (if ''command'' includes file names, those need to be given with absolute path)

; sudo debian : starts debian chroot shell as root (this is the command issued by the "Debian chroot" app)

; sudo debian ''command'' : runs debian command as root

The above scripts run with environment variables determined largely by those set in Maemo and with working directory / . Another option is to enforce login shell behavior as follows:

; sudo debian su - user : starts debian chroot shell as user with $CHROOT/etc/profile and /home/user/.profile evaluated and with working directory /home/user

; sudo debian su - user -c ''command'' : runs debian command as user with $CHROOT/etc/profile and /home/user/.profile evaluated and with working directory /home/user

In all of the above, ''command'' can be simple command-line commands with standard output or GUI programs to be run under a window manager, such as ooffice.

=== Creating desktop shortcuts in Maemo ===

The above scripts are particularly useful for creating shortcuts. For example, a file oowriter.desktop with content
<pre>
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=oowriter
Icon=ooo-writer
Exec=debbie oowriter
Type=Application
</pre>
that is put into
/usr/share/applications/hildon or (since fw 2009.51) /home/user/.local/share/applications/hildon allows one to start the OpenOffice writer
directly from the Maemo Applications Menu without having to launch LXDE first.
Unless you are re-using existing icon files, you can install icons files (.png) by putting them likewise either in /usr/share/icons/hicolor/scalable/hildon or /home/user/.local/share/icons/hicolor/scalable/hildon. You may need to create the .local folders first by
mkdir -p /home/user/.local/share/applications/hildon
mkdir -p /home/user/.local/share/icons/hicolor/scalable/hildon
Newly installed application icons usually need a reboot to become visible in the application manager.

== Startup scripts ==

If they exist, the following scripts (which need to be executable) serve as startup scripts as follows

; $CHROOT/var/run/onfirstchroot-ext.rc : This script will run commands as root in maemo the first time you "open" a chroot. So this is where you could force the processor to "performance mode" or some such thing.

; $CHROOT/var/run/onfirstchroot.rc : This script will run commands as root in the chroot the first time you "open" a chroot. For example, if you have installed ''cups'' within Easy Debian, this script should contain "/etc/init.d/cups restart".

; $CHROOT/var/run/onchroot-ext.rc : This script will run commands as root in maemo every time you run a chroot command.

; $CHROOT/var/run/onchroot.rc : This script will run commands as root in the chroot every time you run a chroot command.

Here $CHROOT is the mount point of the Debian system (to be omitted when aleady in chroot).

In order to run a command in one of these scripts as "user", preface the command with ''su user -c''

== Installing Applications ==

Applications can be installed using [http://www.debian.org/doc/manuals/debian-reference/ch02.en.html apt-get, aptitude] or [http://beginlinux.com/desktop_training/ubuntu/1102-synaptic-package-manager Synaptic]. Apt-get is a command-line tool, and aptitude a terminal-based frontend, both of which can be accessed from within the Debian chroot terminal app (red swirl icon in the Hildon Application Manager). Synaptic Package Manager is a graphical frontend that can be launched from another icon in the Hildon Application Manager. It cannot be started from the (misleadingly present) menu entry in the LXDE menu, because it is not in the standard path and requires root privileges. (In LXDE one can however start it from a terminal typing "sudo synaptic".)

Note that the image cannot be expected to have an up-to-date package list. It is important that you perform "apt-get update" or use Edit -> Reload Package Information within Synaptic before installing new packages. After such installs you can invoke "apt-get clean" to free your disk space from downloaded package files.

In the current image (v3d), only the stable Debian Lenny repository is activated, although the Easy Debian image also involves a number of packages from the newer Debian Squeeze (testing) repository. If you want to install additional packages specifically from Squeeze or even from Sid (unstable), you should uncomment the corresponding line in /etc/apt/sources.list by launching an editor in the Debian chroot terminal (app with red swirl icon), i.e., remove "#" in the beginning of the lines

#deb http://http.us.debian.org/debian squeeze main contrib non-free
#deb http://www.debian-multimedia.org squeeze main

After updating the package information, you can then install from this newer repository. However, heed the following warning:

----

Warning: Those of you familiar with Debian or other similar Linux distributions know that it is very easy to keep the distro up to date by means of the apt-get command. However, there is currently a problem with some of the central Easy Debian apps in the Debian Squeeze repositories. Therefore, it is recommended that for the moment you simply use the image as is. Do not perform a full upgrade (apt-get update is safe, though) when Squeeze (or even Sid) is enabled in /etc/apt/sources.list. This warning will be removed when this issue is resolved.

----

=== CUPS Installation Instructions ===

If you have a network printer that can be accessed by [http://encyclopedia.thefreedictionary.com/Common+Unix+Printing+System CUPS], the Common Unix Printing System, you can do so under Easy Debian, which has cups-client installed (since version v3c).

This allows you to access one CUPS server at a time, which can be specified alternatively by
* the option -h hostname[:port]
* the file client.conf in /etc/cups or ~/.cups (see "man client.conf")
* the environment variable CUPS_SERVER

You can then check for available printers by

lpstat -a

and print out files from your device by

lp -d printername filename

If a full CUPS installation is desired (which allows to schedule jobs to more than one CUPS server in the network, to scan for printers, and also to [http://www.debianadmin.com/howto-install-and-customize-cups-pdf-in-debian.html install cups-pdf], a PDF writer backend):
<pre>
apt-get install cups
apt-get clean
echo "/etc/init.d/cups restart" >> /var/run/onfirstchroot.rc
chmod a+x /var/run/onfirstchroot.rc
</pre>

The last two lines ensure that the CUPS server is started when Easy Debian is launched.

=== Other useful applications to install in addition ===

The following packages are also not part of the current image (v3d) but may be of wider interest:

; vpnc : The VPN client for accessing Cisco concentrators works well when started under Debian, while under Maemo vpnc is not yet available as a stable application. Install by "apt-get install vpnc" and configure through /etc/vpnc.conf .
:This works particularly well in WLAN connections. There even microB connects via vpn. With GPRS connections, however, a browser in Debian has to be used.

; openssh-client : To access the Debian system by ssh, one can of course use the ssh server under Maemo (which presumably every power user will have installed), for a login followed by "debian" or "debian su user". To initiate ssh connection from within the Debian system, installation of openssh-client is sufficient and does not conflict with ssh installations in Maemo.

; gftp : X/GTK+ FTP client. Works well when started outside of LXDE by "debbie gftp".

; djview4 : Provides a reader for djvu files

; flpsed : WYSIWYG PostScript and PDF annotator, useful for filling forms, adding notes etc. Works well when started outside of LXDE by "debbie flpsed".

; pdfchain : a graphical user interface (only in squeeze distribution) for the PDF Tool Kit (pdftk, the command line tool that is already available in the stable lenny distribution)

; abiword : Alternative to OpenOffice Writer. However, needs to be installed from the squeeze repository and does upgrade gconf2 to the squeeze version, which could break other things.

; kile : KDE Integrated LaTeX Environment. Works well when started outside of LXDE by "debbie kile".

; gnumeric : A leaner alternative to OpenOffice Calc. Works well when started outside of LXDE by "debbie gnumeric".

; xournal : GTK+ application for notetaking, sketching and keeping a journal using a stylus. It can also be used to add annotations to PDF files. Works well when started outside of LXDE by "debbie xournal". Richer interface than in the native Maemo application and available in newer version from squeeze.

; zim : [http://zim-wiki.org/ zim] is a desktop wiki application that is well suited for the N900 device (a Maemo version is under development, too). To get the newest version install this package from squeeze (but don't upgrade the rest of the packages). Start from XTerminal (or a self-made application icon, see above) by

sudo debian su - user -c zim

: The theme provided by the v3b image does not work well with this application, but can be changed by creating the file /home/user/.gtkrc-2.0.mine with content e.g.
gtk-theme-name="Raleigh"

; encfs : a user-space encrypted file system, which allows to encrypt entire folders, see http://www.arg0.net/encfs. Encfs requires the fuse kernel module, which is already available in the Maemo system, although normally not yet loaded. Because there is no group "fuse" under Maemo, it's best to change the group ownership of /dev/fuse to users, and have all that automated through the startup script $CHROOT/var/run/onfirstchroot-ext.rc (needs to be executable). Add the following lines to this script:
modprobe fuse
sleep 1
chown root.users /dev/fuse
:Install by running the following commands in the Debian chroot terminal:
apt-get update
apt-get install encfs
adduser user fuse
apt-get clean
:After that user (and not only root) can create and use encrypted file systems in Easy Debian. See http://www.arg0.net/encfs for how to use it.

; nicotine : graphical client for the SoulSeek peer-to-peer system

== FAQ ==

'''Q:''' I have started Openoffice (evince, ...) from the desktop, entered a certain mode (presentation, navigator, formatting, full screen, ...) and cannot get out of that again. 
'''A:''' See [[Easy_Debian#Set_Deb_HW_Keys_app_and_xbindkeys]]

'''Q:''' I chose Iceweasel, but nothing happened! 
'''A:''' Be patient. Iceweasel has no splash screen and a very long startup time. Use Epiphany for faster startup while retaining the ability to use Java and Flash plugins.

'''Q:''' How do I get to the OK button in the huge dialog box that just popped up? 
'''A:''' DIABLO/N8x0: If you choose the "Toggle Movable Windows" icon in the menu, you will switch to a patched version of the Matchbox Window Manager that lets you move the big dialog boxes used by some Debian apps so you can get to the OK button. When you want to go back to "Normal" OS2008 window behavior, select this menu item again. 
'''A:''' FREMANTLE/N900: You'll need to use LXDE to access the entire dialog. Use the Ctrl-. key combination to move windows with the stylus.

'''Q:''' How do I get the virtual keyboard to pop up in Debian Apps? 
'''A:''' DIABLO/N8x0: Select the "Set Debian HW Keys" menu item; wait a bit, then you can press the minus (-) hardware key followed by the menu hardware key to toggle the Matchbox Keyboard. Press the (-) key then the (+) key to toggle between normal and mini (one-line) keyboards. 
'''A:''' FREMANTLE/N900: There is no virtual keyboard in Maemo for Debian apps.

'''Q:''' How do I make Debian apps fullscreen? 
'''A:''' Select the "Set Debian HW Keys" menu item; wait a bit, then you can press (DIABLO/N8x0) the minus (-) hardware key followed by the "fullscreen" hardware key or (FREMANTLE/N900) Ctrl-Uparrow or Ctrl-Space to toggle fullscreen for any app.

'''Q:''' DIABLO/N8x0: How do I get the best turbo speed from OpenOffice, Firefox and other big apps? 
'''A:''' Make sure you have the maximum amount of virtual memory enabled in your Control Panel / Memory dialog. Then select the "Set CPU to Performance mode" menu item and launch your app. Remember to set the CPU to On-Demand mode when you're done using the big app, because Performance mode sucks your battery faster. But it still isn't as bad as the battery life of your average laptop...

'''Q:''' English isn't my first language. How do I change this to my language? 
'''A:''' Please click on the "Debian chroot" icon and type the following command:

dpkg-reconfigure locales

:Choose your language(s).

:DIABLO/N8x0: Note that you should choose the language with no period between the language and the iso code (eg. "en_CA ISO-8859-1"), and optionally, the utf-8 version, too (eg. "en_CA.UTF-8").
:FREMANTLE/N900: Choose the UTF-8 version.

'''Q:''' Under Debian the time zone is not the same as under Maemo. 
'''A:''' In the Debian chroot terminal run

dpkg-reconfigure tzdata

and select the time zone of your choice.

'''Q:''' How do I find the amount of space left for applications? 
'''A:''' From the prompt in Debian Chroot menu item:

df -h /

Look under AVAIL.

'''Q:''' I want to install more applications! How do I do that? 
'''A:''' First, you have to update the repository lists. From the prompt in Debian Chroot menu item:

apt-get update

:The image for the N900 has quite some free space for installing additional Debian packages.

:For DIABLO/N8x0, you must get some space back! There's almost no extra room in the image file.

apt-get install localepurge; localepurge

:This will get you at least 80MB back. You should probably do this first, before starting to install. Running out of space during an install in Debian is ugly.

:Also, when downloading packages, remember to frequently use "apt-get clean" to clear out old downloaded packages. That will help with free space.

:If you're comfortable with the command line, you can use the technique listed in this post to double your install space.

:Even with all of these tricks, you'll still run out of room fairly quickly. You'll probably have to uninstall packages in order to add new ones.

:More advanced users can put a minimal system into an empty image and build a custom set of apps using this post. The most advanced and best way: partition your SD card and put your Debian fs there.

'''Q:''' What's this "Iceweasel"? 
'''A:''' Iceweasel is the Debian name for Firefox. It's a long story, but in short, Mozilla and Debian had a philosophical disagreement that ended in Debian renaming Firefox to Iceweasel. 

'''Q:''' I would like to have a separate /home/user directory under Debian than under Maemo. Is that possible? 
'''A:''' /sbin/qchroot script does mountings; one option is to not mount /home/user at all by commenting out the corresponding line in that script, which is
mount /dev/mmcblk0p2 "$CHROOT/home"
for FREMANTLE/N900. Then /home/user/MyDocs will still get mounted, but you can keep a Debian home directory separately, in the chroot.

'''Q:''' How is this different than the [http://trac.tspre.org/projects/nit-debian Deblet project]? 
'''A:''' Easy Debian uses a fully installed Debian system to run applications inside of Maemo. The Deblet project helps you install a bootable Debian system from scratch; Deblet is mainly designed for booting to an alternate OS.

'''Q:''' I already have Debian in a partition, or I'm running Deblet. How can I use your package with my Debian? 
'''A:''' Edit the /home/user/.chroot file to point to your Debian partition or image file. Easy Debian will do the rest.

'''NOTE:''' If you are using Deblet, delete the /home/user/.synchroot file before running Easy Debian for the first time, so your Deblet config files don't get overwritten. Remember that you'll need to make a user called "user" in Deblet (with the proper ID) for things to work correctly. Also note that your maemo home directory will be used by default. This can also be changed in the .chroot file.

== Donations ==

If you feel overwhelmed by gratitude towards [http://talk.maemo.org/member.php?u=10410 qole] for bringing a full-fledged Debian OS to your device, consider donating at [http://qole.org qole.org]. [DISCLAIMER: This entry was inserted by a grateful user, not qole himself.]

[[Category:Users]]
[[Category:Power users]]

Easy Debian

2010-05-19T10:05:40Z

192.100.124.218: /* LXDE Top Menu Disappears */

This package, when installed, will give you OpenOffice.org, Gimp, the LXDE Desktop Environment, Evince, Firefox (called Iceweasel in Debian) with Java and Flash support, printing support, and access to thousands of precompiled applications from [http://www.debian.org Debian] that can be easily browsed and downloaded. All these applications will be installed in an image file containing the Debian operation system without interfering with Maemo, but taking advantage of its infrastructure and connectivity.

This package will give you all of these applications without any need for installing dependencies or other applications, and it should work on all of the tablets.

== What you need: ==

* You need 2.5 GB free on one of your memory cards, although after installing, you will only need 2 GB.
* You need to keep your expectations reasonable. Big desktop applications like OpenOffice and Firefox run slowly on the tablet. They are power-hungry and designed for big, powerful CPUs. The [[Nokia N810|N8x0's]] processor is comparable to a Pentium II processor. Just imagine running these apps on your computer from the mid-90s (remember Windows 95?), and you'll get the idea. But sometimes, you really need something on the tablet that only these apps can provide, like MS Word compatibility or Java applets. On the [[Nokia N900|N900]], almost all applications run reasonably fast once loaded, but they often take somewhat long to launch.

== Install instructions: ==

* You need to install the easy-deb-chroot package. It can be found in the [[Extras]] repository. There may be a newer version in the "Extras-devel" repository. (Enabling Extras-devel is a dangerous area and you should disable it as soon as you are done installing Easy Debian, but Easy Debian is rather safe and it is optified.)

* Once installed several new shortcut icons will be available on the applications menu. You will need to first run the one called "Debian Image Installer". A terminal program will open and ask you where to place the image file (after decompression it will be a 2 GB file), either on the [[Nokia N900|N900's]] built in storage (under MyDocs), or on an external MicroSD card (if available). That will start the download of the compressed image (about 300 MB) and eventual extraction of the image file. It will take more than a half hour to download if you have fast Internet connection, and another 30 minutes or more to extract it on your tablet. Make sure that there are no other processes running and that the extraction is not interrupted.
: You can check for a successful download and extraction by typing "ls -l MyDocs/debian*" in XTerminal. The compressed image name has the ending .img.ext2.lmza; when decompressed the file name ends in .img.ext2 and it should have a file size of exactly 2147483648 bytes.

* This step is an alternate way to do the previous step: You can manually download the image file from [http://qole.org/files//debian-m5-v3d.img.ext2.lzma here]. Afterward you will have to copy it into <code>/home/user/MyDocs/</code> or into <code>/media/mmc1/</code> depending on whether you want it installed on the internal storage or on a removable storage. Then, when you run "Debian Image Installer" it will detect that you already have the file and proceed to extract it and set it up for you. If you have a faster computer with programs to unpack [http://en.wikipedia.org/wiki/Lzma lzma]-compressed files, you may also skip the Debian Image Installer by installing the uncompressed file by USB.

* If you have more than one image file, you should edit /home/user/.chroot to select the one you want to load. Default is first in /home/user/MyDocs/debian*.img*, /media/mmc1/debian*.img*

* Finally, when you get the "Congratulations!" message, REBOOT.

== Easy Debian application icons ==

Easy Debian installs the following shortcuts in the Application Manager:

; Close Debian : for unmounting the Debian image and shutting down all running Debian processes

; Deb Img Install : for the initial download and extraction of the Debian image. For installing a new version of the Debian image from http:qole.org/files, delete the old image (or move/rename it appropriately) and rerun Deb Img Install.

; Debian chroot : this runs "sudo debian" in XTerminal, which gives root access to the Debian image. This can be used for modifying the Debian image and installing further applications from the command line. The root file system of Maemo is not visible from within Debian chroot, except /home and /home/user/MyDocs, so you cannot ruin the Maemo firmware from here.

; Debian LXDE : this launches the [http://lxde.org Lightweight X11 Desktop Environment] from where you can start all installed Debian application. Alternatively, you can start Debian applications from XTerminal with "debbie" (see below).

; Fix LXDE kbd : fixing lost keyboard focus in LXDE (see below)

; GNOME ALSA mix : for configuring sound

; Iceweasel Web B : unbranded Debian version of the Firefox Web Browser

; OpenOffice : for starting OpenOffice without LXDE

; Set Deb HW Keys : additional useful keybindings (see below)

; Synaptic Pkg Mg : graphical interface for installing additional Debian applications (in the Debian image only, not Maemo proper)

== Using the LXDE Environment: ==

* To launch a session of LXDE (a light weight desktop environment) whith several applications already installed in it, including OpenOffice.org, simply click on the "Debian LXDE" icon shortcut on the application menu.
* LXDE's application menu is found at the top left corner of the screen.
* To momentarily go back into the Maemo environment, simply press Ctrl Backspace.
* Exiting LXDE: Log out, don't just close the window. Make sure to have LXDE closed properly before powering down the device, it will not function properly when started next time before doing the next proper shutdown.

=== Window is too big for the screen ===

Press Ctrl and the period key simultaneously. This will make the "Move Window" cursor appear (a cross with four arrows). Use the stylus to drag the window to expose the parts that are not visible.

=== LXDE Top Menu Disappears ===

The newest version of the Easy Debian image (m5-v3b) has a new LXDE version.

If you upgrade Easy Debian and your LXDE top menu disappears, you can do one of two things:
* Install the newest version (m5-v3d): Close Easy Debian (use the icon with the red arrow and box), delete the old image (use the File Manager to do this), and then use the "Deb Img Install" icon to download and extract the new image.
* Keep your old image, and fix the top menu manually. Start LXDE. Tap and hold on a blank area of the left-side bar. Choose "Create New Panel". Choose "Top" and "OK". Tap and hold on new top panel. In the ''General'' tab, set the following things: Alignment: Left, Width: 25, Height: 32, Properties: Uncheck "Reserve Space..." In the ''Panel Applets'' tab, Add "Menu", "Digital Clock", "System Tray" (check "Stretch" column), "Net status monitor" (use edit button and change eth0 to wlan0, then tap on icon and set to wlan0 there too), and "CPU Usage Monitor".

If after the upgrade some menu entries (e.g. Gimp) are missing, you can manually install them from the Debian chroot terminal by

xdg-desktop-menu install --novendor /usr/share/applications/gimp.desktop

In order to have the document viewer Evince show up in the LXDE menu, you would have to first set "NoDisplay=false" in /usr/share/applications/evince.desktop and then run xdg-desktop-menu similar to above.

=== Keyboard issues and tips ===

It may happen that the hardware keyboard stops working in LXDE. It can be restored by hitting the power button and then tapping outside the menu or also by using the "Fix LXDE keyboard" application icon (in the Hildon Application Manager, which can be reached - if Ctrl+Backspace still works - from the Task Manager). The power button trick is usually both quicker and more reliable.

==== Localization ====

The keyboard in LXDE is by default US. To get a different keyboard layout for the LXDE window manager, you have to modify the Debian image which requires root privileges.
For this,
launch the "Debian chroot" app (icon with red swirl symbol), which opens a terminal with root access to the Debian image (as well as to your home directory). The following instructions assume that you are working from that terminal and not from within the LXDE window manager.

For the task of configuring a special keyboard layout for LXDE (German in the following example), start an editor of your choice in the Debian chroot terminal (e.g., leafpad), and insert the appropriate keymap label in the following line of /etc/xdg/lxsession/LXDE/autostart according to:

@setxkbmap de

Available keymaps are: ch (Swiss), cz and cz_qwerty (Czech), dano (Danish/Norwegian), fise (Finnish/Swedish), nordic (Danish/Norwegian/Finnish/Swedish), de (German), fr (French), it (Italian), pl (Polish), ptes (Portuguese/Spanish), ru (Russian).

You may also wish to set the language environment under Debian to a non-US one so that system messages come in your native language. This can be done by issuing the command (again from within the Debian chroot terminal)

dpkg-reconfigure locales

and selecting from the list that is then displayed the UTF variant of the desired language, for example for German, de_DE.UTF-8.

With older Easy Debian images (up to v3b) and in languages other than da, de, en, fr, and sv, this breaks the script that starts LXDE, because $CHROOT/usr/bin/xephwm5 has a line

export TWOWIN=`wmctrl -l | grep -i Information | awk '{print $1}'`

and "Information" does not match any longer. If in your language "Information" begins with "Info...", you can fix this by shortening "Information" to "Info" in the above line of /usr/bin/xephwm5. If not, you should modify the script to match the string that appears as title of the window saying "Welcome to Easy Debian LXDE..." (Without the above fix, clicking on the OK button will hang the program. You should instead get to the task manager and kill LXDE from there.)
In the new image this is fixed (for all languages).

==== Set Deb HW Keys app and xbindkeys ====

The newest version of Easy Debian provides also a "Set Deb HW Keys" application which runs xbindkeys, mapping Fn+Shift+(upper row keys) of the hardware keyboard to function keys F1-F12. Here the Fn (blue arrow) key has to be pressed first, which is best done by pressing with the thumb and rolling down to also press the Shift key. The function keys are sometimes needed to get in and out of certain modes of programs in particular when started from the desktop (often F1 for help; F5 for presentation or navigator mode; F11 for "Styles and Formatting" in Openoffice.) Moreover, Ctrl+Up and Ctrl+Space provide full screen toggles.

Under LXDE, the Enter key is actually KP_Enter, while some application only accept ordinary "Return". For this eventuality, "Set Deb HW Keys" maps Shift+Enter to Return.

You can edit /home/user/.xbindkeysrc to include more key mappings that you might find desirable in the absence of the virtual keyboard (which on the N900 in Debian chroot is only accessible in the XTerminal). For example
<pre>
"xvkbd -xsendevent -text '\e'"
Shift + BackSpace
</pre>
maps Shift+BackSpace to Escape. (See e.g. http://linux.die.net/man/1/xbindkeys and http://linux.die.net/man/1/xvkbd for more possibilities.)

You can have xbindkeys started also automatically by including

@xbindkeys -f /home/user/.xbindkeysrc

in /etc/xdg/lxsession/LXDE/autostart.

Note that the relevant file /home/user/.xbindkeysrc does not reside in the Debian image but in the home directory. If you upgrade to new versions of Easy Debian, and this file already exists, it will not be overwritten, but the package will install instead a newer version in /home/user/.xbindkeysrc.dist.

It is then up to you to merge new additions to your existing /home/user/.xbindkeysrc file, or if you have not modified it to your needs, to simply take it over by typing in the XTerminal
cp .xbindkeysrc .xbindkeysrc.old
cp .xbindkeysrc.dist .xbindkeysrc

Another work-around for getting additional special characters is to [[Remapping_keyboard|remap your hardware keyboard]].

A known issue is that in national keyboards where Up and Down arrows are composed as Fn+Left/Right arrows, Up and Down do not work under LXDE. If applications cannot be used without Up and Down keys, those should better be started outside of LXDE with debbie.

==== sticky keys hack ====

In the v3b image, /etc/xdg/lxsession/LXDE/autostart includes a hack to have sticky Shift and Fn keys also in LXDE. You can activate this behavior also outside of LXDE by running "debbie stickykeys" (or "debbie stickykeys xx" where xx is a language code different from us). Note however that this also affects XTerminal applications in Maemo.

The sticky keys hack also makes Ctrl sticky and may have other unexpected effects with non-US keyboards. To disable this feature in LXDE, comment out (include #'s in the beginning of) the following two lines in /etc/xdg/lxsession/LXDE/autostart according to

#xkbset exp 60 =sticky =twokey =latchlock
#xkbset sticky -twokey latchlock

In the newest image (v3d), the sticky keys hack is not enabled by default. To enable it, remove the #'s.

== Using debbie ==

From XTerminal the following scripts are available:

; debbie : starts debian chroot shell as user (doesn't evaluate /home/user/.profile)

; debbie ''command'' : runs debian command as user (if ''command'' includes file names, those need to be given with absolute path)

; sudo debian : starts debian chroot shell as root (this is the command issued by the "Debian chroot" app)

; sudo debian ''command'' : runs debian command as root

The above scripts run with environment variables determined largely by those set in Maemo and with working directory / . Another option is to enforce login shell behavior as follows:

; sudo debian su - user : starts debian chroot shell as user with $CHROOT/etc/profile and /home/user/.profile evaluated and with working directory /home/user

; sudo debian su - user -c ''command'' : runs debian command as user with $CHROOT/etc/profile and /home/user/.profile evaluated and with working directory /home/user

In all of the above, ''command'' can be simple command-line commands with standard output or GUI programs to be run under a window manager, such as ooffice.

=== Creating desktop shortcuts in Maemo ===

The above scripts are particularly useful for creating shortcuts. For example, a file oowriter.desktop with content
<pre>
[Desktop Entry]
Version=1.0
Encoding=UTF-8
Name=oowriter
Icon=ooo-writer
Exec=debbie oowriter
Type=Application
</pre>
that is put into
/usr/share/applications/hildon or (since fw 2009.51) /home/user/.local/share/applications/hildon allows one to start the OpenOffice writer
directly from the Maemo Applications Menu without having to launch LXDE first.
Unless you are re-using existing icon files, you can install icons files (.png) by putting them likewise either in /usr/share/icons/hicolor/scalable/hildon or /home/user/.local/share/icons/hicolor/scalable/hildon. You may need to create the .local folders first by
mkdir -p /home/user/.local/share/applications/hildon
mkdir -p /home/user/.local/share/icons/hicolor/scalable/hildon
Newly installed application icons usually need a reboot to become visible in the application manager.

== Startup scripts ==

If they exist, the following scripts (which need to be executable) serve as startup scripts as follows

; $CHROOT/var/run/onfirstchroot-ext.rc : This script will run commands as root in maemo the first time you "open" a chroot. So this is where you could force the processor to "performance mode" or some such thing.

; $CHROOT/var/run/onfirstchroot.rc : This script will run commands as root in the chroot the first time you "open" a chroot. For example, if you have installed ''cups'' within Easy Debian, this script should contain "/etc/init.d/cups restart".

; $CHROOT/var/run/onchroot-ext.rc : This script will run commands as root in maemo every time you run a chroot command.

; $CHROOT/var/run/onchroot.rc : This script will run commands as root in the chroot every time you run a chroot command.

Here $CHROOT is the mount point of the Debian system (to be omitted when aleady in chroot).

In order to run a command in one of these scripts as "user", preface the command with ''su user -c''

== Installing Applications ==

Applications can be installed using [http://www.debian.org/doc/manuals/debian-reference/ch02.en.html apt-get, aptitude] or [http://beginlinux.com/desktop_training/ubuntu/1102-synaptic-package-manager Synaptic]. Apt-get is a command-line tool, and aptitude a terminal-based frontend, both of which can be accessed from within the Debian chroot terminal app (red swirl icon in the Hildon Application Manager). Synaptic Package Manager is a graphical frontend that can be launched from another icon in the Hildon Application Manager. It cannot be started from the (misleadingly present) menu entry in the LXDE menu, because it is not in the standard path and requires root privileges. (In LXDE one can however start it from a terminal typing "sudo synaptic".)

Note that the image cannot be expected to have an up-to-date package list. It is important that you perform "apt-get update" or use Edit -> Reload Package Information within Synaptic before installing new packages. After such installs you can invoke "apt-get clean" to free your disk space from downloaded package files.

In the current image (v3d), only the stable Debian Lenny repository is activated, although the Easy Debian image also involves a number of packages from the newer Debian Squeeze (testing) repository. If you want to install additional packages specifically from Squeeze or even from Sid (unstable), you should uncomment the corresponding line in /etc/apt/sources.list by launching an editor in the Debian chroot terminal (app with red swirl icon), i.e., remove "#" in the beginning of the lines

#deb http://http.us.debian.org/debian squeeze main contrib non-free
#deb http://www.debian-multimedia.org squeeze main

After updating the package information, you can then install from this newer repository. However, heed the following warning:

----

Warning: Those of you familiar with Debian or other similar Linux distributions know that it is very easy to keep the distro up to date by means of the apt-get command. However, there is currently a problem with some of the central Easy Debian apps in the Debian Squeeze repositories. Therefore, it is recommended that for the moment you simply use the image as is. Do not perform a full upgrade (apt-get update is safe, though) when Squeeze (or even Sid) is enabled in /etc/apt/sources.list. This warning will be removed when this issue is resolved.

----

=== CUPS Installation Instructions ===

If you have a network printer that can be accessed by [http://encyclopedia.thefreedictionary.com/Common+Unix+Printing+System CUPS], the Common Unix Printing System, you can do so under Easy Debian, which has cups-client installed (since version v3c).

This allows you to access one CUPS server at a time, which can be specified alternatively by
* the option -h hostname[:port]
* the file client.conf in /etc/cups or ~/.cups (see "man client.conf")
* the environment variable CUPS_SERVER

You can then check for available printers by

lpstat -a

and print out files from your device by

lp -d printername filename

If a full CUPS installation is desired (which allows to schedule jobs to more than one CUPS server in the network, to scan for printers, and also to [http://www.debianadmin.com/howto-install-and-customize-cups-pdf-in-debian.html install cups-pdf], a PDF writer backend):
<pre>
apt-get install cups
apt-get clean
echo "/etc/init.d/cups restart" >> /var/run/onfirstchroot.rc
chmod a+x /var/run/onfirstchroot.rc
</pre>

The last two lines ensure that the CUPS server is started when Easy Debian is launched.

=== Other useful applications to install in addition ===

The following packages are also not part of the current image (v3d) but may be of wider interest:

; vpnc : The VPN client for accessing Cisco concentrators works well when started under Debian, while under Maemo vpnc is not yet available as a stable application. Install by "apt-get install vpnc" and configure through /etc/vpnc.conf .
:This works particularly well in WLAN connections. There even microB connects via vpn. With GPRS connections, however, a browser in Debian has to be used.

; openssh-client : To access the Debian system by ssh, one can of course use the ssh server under Maemo (which presumably every power user will have installed), for a login followed by "debian" or "debian su user". To initiate ssh connection from within the Debian system, installation of openssh-client is sufficient and does not conflict with ssh installations in Maemo.

; gftp : X/GTK+ FTP client. Works well when started outside of LXDE by "debbie gftp".

; djview4 : Provides a reader for djvu files

; flpsed : WYSIWYG PostScript and PDF annotator, useful for filling forms, adding notes etc. Works well when started outside of LXDE by "debbie flpsed".

; pdfchain : a graphical user interface (only in squeeze distribution) for the PDF Tool Kit (pdftk, the command line tool that is already available in the stable lenny distribution)

; abiword : Alternative to OpenOffice Writer. However, needs to be installed from the squeeze repository and does upgrade gconf2 to the squeeze version, which could break other things.

; kile : KDE Integrated LaTeX Environment. Works well when started outside of LXDE by "debbie kile".

; gnumeric : A leaner alternative to OpenOffice Calc. Works well when started outside of LXDE by "debbie gnumeric".

; xournal : GTK+ application for notetaking, sketching and keeping a journal using a stylus. It can also be used to add annotations to PDF files. Works well when started outside of LXDE by "debbie xournal". Richer interface than in the native Maemo application and available in newer version from squeeze.

; zim : [http://zim-wiki.org/ zim] is a desktop wiki application that is well suited for the N900 device (a Maemo version is under development, too). To get the newest version install this package from squeeze (but don't upgrade the rest of the packages). Start from XTerminal (or a self-made application icon, see above) by

sudo debian su - user -c zim

: The theme provided by the v3b image does not work well with this application, but can be changed by creating the file /home/user/.gtkrc-2.0.mine with content e.g.
gtk-theme-name="Raleigh"

; encfs : a user-space encrypted file system, which allows to encrypt entire folders, see http://www.arg0.net/encfs. Encfs requires the fuse kernel module, which is already available in the Maemo system, although normally not yet loaded. Because there is no group "fuse" under Maemo, it's best to change the group ownership of /dev/fuse to users, and have all that automated through the startup script $CHROOT/var/run/onfirstchroot-ext.rc (needs to be executable). Add the following lines to this script:
modprobe fuse
sleep 1
chown root.users /dev/fuse
:Install by running the following commands in the Debian chroot terminal:
apt-get update
apt-get install encfs
adduser user fuse
apt-get clean
:After that user (and not only root) can create and use encrypted file systems in Easy Debian. See http://www.arg0.net/encfs for how to use it.

; nicotine : graphical client for the SoulSeek peer-to-peer system

== FAQ ==

'''Q:''' I have started Openoffice (evince, ...) from the desktop, entered a certain mode (presentation, navigator, formatting, full screen, ...) and cannot get out of that again. 
'''A:''' See [[Easy_Debian#Set_Deb_HW_Keys_app_and_xbindkeys]]

'''Q:''' I chose Iceweasel, but nothing happened! 
'''A:''' Be patient. Iceweasel has no splash screen and a very long startup time. Use Epiphany for faster startup while retaining the ability to use Java and Flash plugins.

'''Q:''' How do I get to the OK button in the huge dialog box that just popped up? 
'''A:''' DIABLO/N8x0: If you choose the "Toggle Movable Windows" icon in the menu, you will switch to a patched version of the Matchbox Window Manager that lets you move the big dialog boxes used by some Debian apps so you can get to the OK button. When you want to go back to "Normal" OS2008 window behavior, select this menu item again. 
'''A:''' FREMANTLE/N900: You'll need to use LXDE to access the entire dialog. Use the Ctrl-. key combination to move windows with the stylus.

'''Q:''' How do I get the virtual keyboard to pop up in Debian Apps? 
'''A:''' DIABLO/N8x0: Select the "Set Debian HW Keys" menu item; wait a bit, then you can press the minus (-) hardware key followed by the menu hardware key to toggle the Matchbox Keyboard. Press the (-) key then the (+) key to toggle between normal and mini (one-line) keyboards. 
'''A:''' FREMANTLE/N900: There is no virtual keyboard in Maemo for Debian apps.

'''Q:''' How do I make Debian apps fullscreen? 
'''A:''' Select the "Set Debian HW Keys" menu item; wait a bit, then you can press (DIABLO/N8x0) the minus (-) hardware key followed by the "fullscreen" hardware key or (FREMANTLE/N900) Ctrl-Uparrow or Ctrl-Space to toggle fullscreen for any app.

'''Q:''' DIABLO/N8x0: How do I get the best turbo speed from OpenOffice, Firefox and other big apps? 
'''A:''' Make sure you have the maximum amount of virtual memory enabled in your Control Panel / Memory dialog. Then select the "Set CPU to Performance mode" menu item and launch your app. Remember to set the CPU to On-Demand mode when you're done using the big app, because Performance mode sucks your battery faster. But it still isn't as bad as the battery life of your average laptop...

'''Q:''' English isn't my first language. How do I change this to my language? 
'''A:''' Please click on the "Debian chroot" icon and type the following command:

dpkg-reconfigure locales

:Choose your language(s).

:DIABLO/N8x0: Note that you should choose the language with no period between the language and the iso code (eg. "en_CA ISO-8859-1"), and optionally, the utf-8 version, too (eg. "en_CA.UTF-8").
:FREMANTLE/N900: Choose the UTF-8 version.

'''Q:''' Under Debian the time zone is not the same as under Maemo. 
'''A:''' In the Debian chroot terminal run

dpkg-reconfigure tzdata

and select the time zone of your choice.

'''Q:''' How do I find the amount of space left for applications? 
'''A:''' From the prompt in Debian Chroot menu item:

df -h /

Look under AVAIL.

'''Q:''' I want to install more applications! How do I do that? 
'''A:''' First, you have to update the repository lists. From the prompt in Debian Chroot menu item:

apt-get update

:The image for the N900 has quite some free space for installing additional Debian packages.

:For DIABLO/N8x0, you must get some space back! There's almost no extra room in the image file.

apt-get install localepurge; localepurge

:This will get you at least 80MB back. You should probably do this first, before starting to install. Running out of space during an install in Debian is ugly.

:Also, when downloading packages, remember to frequently use "apt-get clean" to clear out old downloaded packages. That will help with free space.

:If you're comfortable with the command line, you can use the technique listed in this post to double your install space.

:Even with all of these tricks, you'll still run out of room fairly quickly. You'll probably have to uninstall packages in order to add new ones.

:More advanced users can put a minimal system into an empty image and build a custom set of apps using this post. The most advanced and best way: partition your SD card and put your Debian fs there.

'''Q:''' What's this "Iceweasel"? 
'''A:''' Iceweasel is the Debian name for Firefox. It's a long story, but in short, Mozilla and Debian had a philosophical disagreement that ended in Debian renaming Firefox to Iceweasel. 

'''Q:''' I would like to have a separate /home/user directory under Debian than under Maemo. Is that possible? 
'''A:''' /sbin/qchroot script does mountings; one option is to not mount /home/user at all by commenting out the corresponding line in that script, which is
mount /dev/mmcblk0p2 "$CHROOT/home"
for FREMANTLE/N900. Then /home/user/MyDocs will still get mounted, but you can keep a Debian home directory separately, in the chroot.

'''Q:''' How is this different than the [http://trac.tspre.org/projects/nit-debian Deblet project]? 
'''A:''' Easy Debian uses a fully installed Debian system to run applications inside of Maemo. The Deblet project helps you install a bootable Debian system from scratch; Deblet is mainly designed for booting to an alternate OS.

'''Q:''' I already have Debian in a partition, or I'm running Deblet. How can I use your package with my Debian? 
'''A:''' Edit the /home/user/.chroot file to point to your Debian partition or image file. Easy Debian will do the rest.

'''NOTE:''' If you are using Deblet, delete the /home/user/.synchroot file before running Easy Debian for the first time, so your Deblet config files don't get overwritten. Remember that you'll need to make a user called "user" in Deblet (with the proper ID) for things to work correctly. Also note that your maemo home directory will be used by default. This can also be changed in the .chroot file.

== Donations ==

If you feel overwhelmed by gratitude towards [http://talk.maemo.org/member.php?u=10410 qole] for bringing a full-fledged Debian OS to your device, consider donating at [http://qole.org qole.org]. [DISCLAIMER: This entry was inserted by a grateful user, not qole himself.]

[[Category:Users]]
[[Category:Power users]]

Bugs:Stock answers

2010-04-23T10:22:23Z

192.100.124.218: rewrite the CPU usage analysis instructions

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==

To find out what is causing the issue, first check "top" (preferably from SSH console to avoid X etc CPU usage happening when doing this from Xterm) to see which process/es are using most CPU. Provide this information in a corresponding bug with a detailed description on how to trigger the issue.

If others aren't able to reproduce the issue, more information is need. Depending on what is using the CPU, output from different tools may need to be added to the bug:
* If D-BUS server or Tracker is using noticeable amount of CPU, run "dbus-monitor --session" and "dbus-monitor --system" commands.
* If X server is using noticeable amount of CPU, install "xresponse"[1] and run "xresponse -w 0 -a '*'" (this must be done from SSH console) to see which applications are updating their windows.
* Otherwise install "strace"[1] and trace the syscalls from the CPU consuming process with "strace -f -p <PID>".
* If even strace isn't telling enough, install "oprofile"[1] and provide Oprofile data on the issue.

[1] You get these tools from the SDK tools repository, see: http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle).

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there error message when it crashes?

Can you please run Notes in a terminal window (Applications Menu -> Utilities > X Terminal, then enter the command "maemo-summoner /usr/bin/osso_notes.launch > log 2>&1" and hit the Enter key) and attach the resulting "log" file here after it has crashed?

Having a core dump could be even more useful. It requires installing the "sp-rich-core" package from the tools repository[1] and creating a "core-dumps" directory to the memory card with at least few megabytes of free space. You can get core dumps also without the rich-core package, but they are much less useful (and without it pre-installed applications core dumps are then named maemo-launcher-*).

[1] http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install ''sp-memusage'' package from the tools repository according to the instructions here: http://wiki.maemo.org/Documentation/devtools/maemo5.

''mem-smaps-private'' script from that package can be used to get most accurate values on process memory usage. ''mem-cpu-monitor'' tool can be used to track system and specified processes memory and CPU usage changes (most relevant values).

To track changes in usage of all device resources (not just memory) over longer period of time, install the ''sp-endurance'' package. The data its ''save-incremental-endurance-stats'' script stores, can be post-processed to a HTML report (with some bar graphs) using the ''parse-endurance-measurements'' script from the sp-endurance-postproc package.

Then attach the information provided by these tools to the corresponding bug.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox on how to analyze memory leaks using the x86 Scratchbox environment.

==Duplicate==
Thanks for reporting this.
This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find. Also feel encouraged to vote for the original bug report if interested.

Please feel free to search for existing reports first to avoid filing duplicates.

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
**Short cut: In most cases this command executed as root should give enough information (after running it you can attach the file sip.pcap to the bug).
For WiFi/Wlan:
tcpdump -n -w sip.pcap -s 1500 -i wlan0
For mobile data connections:
tcpdump -n -w sip.pcap -s 1500 -i gprs0
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX PUSH issues===
If you have time it would be useful to also get an HCI log of the issue.

This is done by installing the hcidump package and running "hcidump -XVt" as root when performing the transfer. Please start hcidump before making the Bluetooth connection to get proper parsing of the OBEX packets.

To enable obexd and bluetoothd syslog output execute
"killall -USR2 obexd" and "killall -USR2 bluetoothd" (as root).

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to
wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known
issues or any restrictions in place? (Like, traffic shaping of some sort)

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===Wifi/WLAN===

====Connection problems====
Could you please post the output of the command "dmesg" (in X Terminal) immediately after a connection failure?

====Misc====

Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:
* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:
* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
Virtual keyboard: When this happens please start X Terminal and provide the output of
gconftool-2 -g /system/osso/af/slide-open

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
<code>run-standalone.sh /usr/bin/hildon-desktop</code>
From [[Terminal|console]] you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Restarting the Desktop (in Fremantle)===
Run "killall hildon-home" if for example the device becomes unresponsive (high memory usage) and you suspect some Desktop widgets to be the root cause of this.

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch -s (in Maemo5) or
/usr/bin/maemo-summoner /usr/bin/modest.launch showui (in Maemo4)
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ (Diablo) or http://wiki.maemo.org/Documentation/devtools/maemo5 and http://wiki.maemo.org/Documentation/devtools/maemo5/strace (Fremantle) for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle). Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===MMC/SD card related (Product "System software/mmc-and-usb")===
Has this happened with any other card? What is your card manufacturer, model and size?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===Internet Tablet Video Converter===
AVI is just a container format, what matters is the codec. Can you please find out which codec your camera uses? You might want to check the camera manual. Thanks!
Are there any error messages when the crash happens?
Did the application install cleanly with no problems? Could you try to uninstall and reinstall again from a clean download please?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]
[[Category:Quality Assurance]]

Documentation/devtools/maemo5/syslog

2010-04-22T15:11:09Z

192.100.124.218: /* Usage */

{{Devtools}}

== Description ==

The syslogd daemon is responsible for providing logging of messages
received from programs and facilities on the local host as well as
from remote hosts.

The klogd daemon listens to kernel message sources and is responsible
for prioritizing and processing operating system messages. The klogd
daemon can run as a client of syslogd or optionally as a standalone
program.

== Packages ==

'''source''': sysklogd

'''binary''': sysklogd, klogd

To install these, run:
<pre>
sudo gainroot
apt-get install sysklogd
</pre>

== Usage ==

To start the klogd and syslog daemons:

<pre>
# start sysklogd
</pre>

Note that with time syslog can fill the root filesystem completely. When that's done by a root process like syslog, it can become so full that the device fails to boot. Several days or even couple of weeks shouldn't be a problem, but it depends on the device usage. So, '''after you don't anymore need syslog, remove it and <tt>rm /var/log/syslog*</tt>.'''

== Links ==

[http://maemo.org/development/documentation/man_pages/sysklogd/ sysklogd man page]

[http://maemo.org/development/documentation/man_pages/klogd/ klogd man page]

== See Also ==

-

[[Category:Fremantle]]

User:Tuminoid

2010-04-13T05:34:19Z

192.100.124.218: pr1.2 disclaimer

=Who am I?=

Known in web as [http://www.tumi.fi/ Tumi] or [http://maemo.org/profile/view/tuminoid/ Tuminoid]. In the real world I'm known as [http://www.tuomotanskanen.fi/ Tuomo Tanskanen], nice to meet you!

Employed by: [http://www.nomovok.com/ Nomovok Ltd] as Team Manager & Sr. Software Developer

Visit me: [http://www.tumi.fi/ Home], [http://maemo.org/profile/view/tuminoid/ Maemo.org], [https://garage.maemo.org/users/tuminoid/ Garage], [http://www.linkedin.com/in/tuomotanskanen LinkedIn], [http://www.facebook.com/tuomo.tanskanen Facebook], [http://stackoverflow.com/users/40657/tuminoid StackOverflow], [http://meego.com/users/tumi MeeGo]

=Maemo Projects=
My Maemo projects residing at Garage:

==CPU/Mem Applet==

CPU/Mem Applet, aka cpumem-applet, is a strip down of popular app load-applet by Jakub Paveled. Load-applet shows your the cpu/mem load as well, but also includes large, bulky and non-working screencapture and screenshot features. It was requested by many that CPU/Mem Load feature packaged alone and Screencasting would be another one, but it never happened by Jakub. So, I made a fork of Load applet and create CPU/Mem Applet, which is tiny (10kB) implementation of the most useful feature.

[http://maemo.org/downloads/product/Maemo5/cpumem-applet/ CPU/Mem Applet @ Extras]

[https://garage.maemo.org/projects/cpumem-applet/ CPU/Mem Applet @ Garage]

[http://maemo.org/packages/view/cpumem-applet/ cpumem-applet @ Package interface]

==Cellular Modem Control Buttons==

Cellular Modem Control Buttons, aka cell-modem-ui, is a toggle button interface residing in powerkeymenu allowing you to disable the cellular modem in your N900. To save battery and to allow you using Wifi connectivity but no cellular in certain places (hospitals, planes).

Currently in its third release to Extras, version 0.5-1 introduced full translation of application UI PLUS translated descriptions for the package, so you can find information about the app in AppMgr ''in your own language''!

[http://maemo.org/downloads/product/Maemo5/cell-modem-ui/ Cellular Modem Control Buttons @ Extras]

[https://garage.maemo.org/projects/cell-modem-ui/ Cellular Modem Control buttons @ Garage]

[http://maemo.org/packages/view/cell-modem-ui/ cell-modem-ui @ Package interface]

[http://www.transifex.net/projects/p/cell-modem-control/ Cellular Modem Control translation project @ Transifex.net]

==Now Playing Notifications==

'''In development - beta quality'''

Displays notifications similar to "new email" messages when currently playing song changes. See more information in Garage and/or Talk thread.

[https://garage.maemo.org/projects/nowplayingd/ Now Playing Notifications @ Garage], see [http://talk.maemo.org/showthread.php?p=548242#post548242 "brainstorm"]

[http://maemo.org/packages/view/nowplayingd/ nowplayingd @ Package Interface]

''Development has been delayed due PR1.2 issues''

==Custom Powerkeymenu==

My newest, pre-alpha stage project that will allow you to customize powerkeymenu.

[https://garage.maemo.org/projects/custom-pwkmenu/ Custom Powerkeymenu @ Garage]

----

=Events=

==MobileDevCamp Helsinki 2010==
I attended [http://mobiledevcamp.fi/ MobileDevCamp 2010] Feb 27th 2010 at Arcada, Helsinki, and had fun! Made some nice contacts and heard a lot of nice talks from folks by [http://www.forum.nokia.com Forum Nokia] / [http://mobiledevcamp.fi/speakers#SamiViitanen Sami Viitanen], [http://www.microsoft.fi Microsoft] / [http://mobiledevcamp.fi/speakers#Vesku Vesku Paananen] and [http://labs.ericsson.com/ Ericsson Labs] / http://mobiledevcamp.fi/speakers#Eriksson Vladimir Katardiev]. All those guys have an excellent taste of humour and self-irony, kudos to all!

Definitely gonna attend the event next year too, maybe I'd have time to attend the 48h coding competition as well and take one of the prize-phones home with me!

==TechDays Helsinki 2010==

I'll be attending [http://www.microsoft.com/finland/techdays/techdays2010/default.htm TechDays Helsinki 2010] at Messukeskus, Helsinki at 9-10.3.2010, as I won a ticket to there from MobileDevCamp!

Give me a holler if you'll be there too!

----

=Job offers=

==Jobs at Nomovok Ltd==

If you need more details about a position, please don't hesitate to contact me.

'''Linux Kernel Developer''' - urgent! The person can be located anywhere in the world, although Helsinki/Finland area is preferred. We can hire you directly to our staff, or even subcontract you if you have a company, or hire you as a freelancer. ''Offer expires at the end of March 2010.''

'''Linux Developer''' - good guys are always wanted! Send an open application to Nomovok, more details from me. ''This offer does not expire.''

Bugs:Stock answers

2010-03-02T10:42:41Z

192.100.124.218: /* Memory issues */

A quick collection for anybody triaging bug reports in [https://bugs.maemo.org maemo.org Bugzilla]. These stock answers are meant to be copied and pasted to bug reports that could be more useful. Please keep the product specific ones alphabetically sorted as per the Products structure in Bugzilla, and feel free to edit/enhance! -[[User:Andre]]

=General=

==Too vague or a generally bad report==

Hi there!

Thanks for reporting this, but unfortunately this report isn't very useful because it doesn't describe the issue well. If you have time and can still reproduce the bug, please read https://bugs.maemo.org/page.cgi?id=bug-writing.html and add a more useful description to this bug.

==Version number==

Hi there!

Thanks for reporting this. Can you please tell us exactly which version you are using (Control Panel > General > About product)? Please try to make sure that you are using the latest available release (2.2009.51-1 as of this writing). An update should be available through the Application Manager if you aren't up to date.

==Software hangs with 100% CPU==
Can you please:

* Either install "strace" from the tools repository[1] and "strace" the CPU consuming process, or
* install the "sp-rich-core" package from the tools repository[1] and creating a "core-dumps" directory to the memory card with at least few megabytes of free space.
* do "kill -6 <PID>" for the process that takes the CPU, and
* attach the resulting .rcore.lzo file from the core-dumps directory here?

[1] http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)

==Need a syslog==
Can you please provide a syslog? See http://wiki.maemo.org/Documentation/devtools/maemo5/syslog and http://wiki.maemo.org/Documentation/devtools/maemo5#Installation for more information.
If you are not used to Linux, after creating the syslog file you can copy the syslog file to those folders that are visible in the Maemo File Manager by:
* Starting X Terminal
* cp /var/log/syslog /home/user/MyDocs/.documents/
After that you can find the file in the Maemo File Manager by going to Nokia N900 > Documents.

==Need a crash coredump==
Can you please install Crash Reporter from the SDK Tools repository in order to send coredumps directly to Nokia?
See http://wiki.maemo.org/Extras-testing#Tools_for_testers for a how-to.
If you are offered to add a comment for sending the coredump file, please mention this bug number (like "see bugs.maemo.org bug number xxxx").
Also, a filename will be displayed after uploading the coredump. Please add the name of that file here in the bug report.

==Need a crash stacktrace (for Notes)==
Is there error message when it crashes?

Can you please run Notes in a terminal window (Applications Menu -> Utilities > X Terminal, then enter the command "maemo-summoner /usr/bin/osso_notes.launch > log 2>&1" and hit the Enter key) and attach the resulting "log" file here after it has crashed?

Having a core dump could be even more useful. It requires installing the "sp-rich-core" package from the tools repository[1] and creating a "core-dumps" directory to the memory card with at least few megabytes of free space. You can get core dumps also without the rich-core package, but they are much less useful (and without it pre-installed applications core dumps are then named maemo-launcher-*).

[1] http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle)
(also features information about valgrind and strace)

==Old Software version==
Hi there!

Thanks for reporting this. Can you please test this again running the latest available release? The latest release should be available through the Application Manager.

==Memory issues==
Please install ''sp-memusage'' package from the tools repository according to the instructions here: http://wiki.maemo.org/Documentation/devtools/maemo5.

''mem-smaps-private'' script from that package can be used to get most accurate values on process memory usage. ''mem-cpu-monitor'' tool can be used to track system and specified processes memory and CPU usage changes (most relevant values).

To track changes in usage of all device resources (not just memory) over longer period of time, install the ''sp-endurance'' package. The data its ''save-incremental-endurance-stats'' script stores, can be post-processed to a HTML report (with some bar graphs) using the ''parse-endurance-measurements'' script from the sp-endurance-postproc package.

Then attach the information provided by these tools to the corresponding bug.

For advanced users, see http://wiki.maemo.org/Using_Valgrind_and_gdb_in_Scratchbox on how to analyze memory leaks using the x86 Scratchbox environment.

==Duplicate==
Hi there!

Thanks for the bug report. This particular issue has already been reported in our bug tracking system, but please feel free to report any further bugs you find.

Thanks!

==One report for each bug==
Hi there!

Please remember to file a new report for each issue. Having only one issue per bug makes it much easier to track problems and makes it easier for them to be fixed.

Thanks!

==Incomplete (after moreinfo keyword set)==
Hi there!

Unfortunately, without more information, as requested in one of the last comments, we are unable to do anything more about this report. Until more information is available, I'm resolving the report as INVALID.

Please feel free to reopen this bug if you can provide the information asked for, or if you can still reproduce this.

Thanks!

==Become root==
To do this, you have to become root first. Please see http://wiki.maemo.org/Root_access for instructions.

==Untidy patch provided==
Thanks for the patch. Can you please clean it up and reattach it? See http://wiki.maemo.org/The_Good_Patch for more information.

=Potential Product specific answers=

==Browser==
===Maemo4 only===
* Can you please create a browser logfile? Enter about:config?prefname=browser.consolelogfile&prefvalue=/tmp/browserlog in the browser location bar, set that preference, reproduce the browser problem and post the content of the file /tmp/browserlog here (you can for example start the terminal application, run "more /tmp/browserlog" and copy the output to this bug report).

==Calendar==

==Chat & Call & SMS==

===Chat===
Please see http://telepathy.freedesktop.org/wiki/Debugging for information how to debug.

===Google Talk / XMPP===
To get logs from telepathy-gabble (the XMPP connection manager) you need to open X-Terminal and then run the following commands (one per line):
export GABBLE_PERSIST=1
export GABBLE_DEBUG=all
export LM_DEBUB=net
killall telepathy-gabble; /usr/lib/telepathy/telepathy-gabble >gabble.log 2>&1 &

===SIP/rtcom/Internet Call===
* Do you use NAT?
* If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account?
* A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from other hosts). Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
**Short cut: In most cases this command executed as root should give enough information (after running it you can attach the file sip.pcap to the bug):
tcpdump -n -w sip.pcap -s 1500 -i wlan0
* Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ for Maemo4 or http://wiki.maemo.org/Documentation/devtools/maemo5/syslog for Maemo5.

==Connectivity==

===Bluetooth and car sets (only in Fremantle)===
There are two different logs that would be useful. The first is bluetoothd debug logs and the second is a HCI-level trace.

For the first you'd need to:
1. install the klogd and sysklogd debian packages (and probably reboot the device afterwards)
2. after booting and before doing anything with bluetooth do "killall -USR2 bluetoothd" (as root) to enable bluetoothd debug logs
3. after reproducing the issue "grep bluetoothd /var/log/syslog > bluetoothd-log.txt" and attach the file here.

For a HCI trace do:
1. install the bluez-hcidump debian package
2. (as root) run "hcidump -B -w hci-trace.log while reproducing the issue
3. attach the hci-trace.log (or whatever filename you chose) here

See http://wiki.maemo.org/Documentation/devtools/maemo5 for more information on how to install the requested packages.

===Bluetooth DUN issues (Diablo only)===
Is there any error message displayed?
Could you provide a syslog and a hcidump (package "bluez-hcidump", also see http://maemo.org/development/tools/doc/diablo/bluez-hcidump/ , manual download at http://repository.maemo.org/pool/diablo/free/b/bluez-hcidump/ )?
For general information: http://www.cellular-store.com/categorybluetooth.aspx provides a list of Bluetooth Compatible Cell Phones Models.

===Bluetooth DUN issues (Fremantle only)===
This is not officially supported - see http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles for more information.

===Bluetooth OBEX (File transfer) issues (Maemo4 only)===
Are you sure that the phone supports OBEX File Transfer and not e.g. only OBEX Object Push? Can you e.g. discover it by doing "sdptool search --bdaddr <bt address of phone> FTP"?

===GPRS/3G issues===
* Do you see this with any other operator's SIM?
* Do you see this if you force the device to 2G? (Phone settings - you need to
wait until the dialog lets you to save the setting)
* Do you see this when tethering (Bluetooth DUN or USB cable) from a laptop, with a similar network usage pattern (web browsing, etc.)?
* Have you contacted the operator in question, whether they have any known
issues or any restrictions in place? (Like, traffic shaping of some sort)

====Cannot access any webpage (DNS issue from bug 8339)====
Is the H3G connection DNS server setting (Settings -> Internet connections -> Connections -> H3G -> Edit -> Next -> Next -> Advanced -> IP Addresses) correct?
Also, try the following:
1. Establish cellular IP connection.
2. Open terminal.
3. Run "cat /var/run/resolv.conf.gprs" and note the nameserver(s) listed there.
4. Run "nslookup www.google.it XXX.XXX.XXX.XXX" where XXX.XXX.XXX.XXX is one of the nameservers from step 3.
Does it resolve successfully when using the provider's servers directly?

===Wifi/WLAN===

====Connection problems====
Could you please post the output of the command "dmesg" (in X Terminal) immediately after a connection failure?

====Misc====

Does running "/etc/init.d/networking restart" update the list of networks?

Asking for more information:
* What router do you have?
** Make and model?
** Firmware version?
** Hardware revision?
** What are the encryption settings? (open/WEP/WPA/WPA2)
* How far are you from your router?
* How many WiFi access points do you have?

PSM problems:
* Does setting Power Saving to "Off" help? (Settings > Internet Connections > Connections > Edit > Next > Next > Next > Advanced > Other > Power saving)
* Router settings:
** What's the beacon interval?
** What's the DTIM period?

==Contacts==

==Core==

===Busybox===
Do you have a 3rd party version of Busybox installed?

===Charger issues===
Are you using the original Nokia charger or something else?
If you have another compatible charger, does the problem occur also with that?
Can you please start X Terminal and provide the output of the commands:
* cat /sys/devices/platform/musb_hdrc/mode
* cat /sys/devices/platform/musb_hdrc/charger
Can you please provide a syslog as described on
http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ?

===Power management===
https://maemo.org/community/wiki/poweranddevicemanagement/

Battery drain can have many potential reasons:
* bad 3rd party applet/application not idling when not used
* buggy WLAN access point (not implementing power management properly)
** setting device to offline mode when not in use helps
* Keeping device in RD mode
* Corrupted memory card
* Metalayer crawler related bugs (only currently known is about gstreamer/WMA)
* etc.

===Reboot related===
http://wiki.maemo.org/Troubleshooting_boot_issues

==Data==

===Meta Tracker===
Please provide the output of "tracker-stats" in X Terminal. It lists the number of documents by type on your device.

Please provide a log by setting the config verbosity (in $HOME/.config/tracker/*.cfg) or setting the verbosity when running commands with -v {0|1|2|3}
The logs are stored in $HOME/.local/share/tracker/ .

==Desktop platform==

===Application Menu===
Please check http://wiki.maemo.org/Troubleshooting_menu_issues and report back.

===Input Methods===
http://maemo.org/development/documentation/how-tos/4-x/extending_hildon_input_methods.html

==Desktop Widgets==
===Widgets/Applets (debugging)===
The easiest way to debug your applets is to run the hildon-desktop on scratchbox currently:
run-standalone.sh /usr/bin/hildon-desktop
From console you can see then the printouts. Debugging on the device is a bit harder.
For Python applets you might want to check pyphantom.

With Valgrind on x86-scratchbox one can debug applet problems (e.g. memory leaks):
af-sb-init.sh start
<wait until desktop starts>
kill $(pidof maemo_af_desktop)
export G_SLICE="always-malloc"
run-standalone.sh valgrind --tool=memcheck --num-callers=60 --leak-check=yes /usr/bin/maemo-summoner /usr/bin/maemo_af_desktop.launch

===Restarting the Desktop (in Fremantle)===
Run "killall hildon-home" if for example the device becomes unresponsive (high memory usage) and you suspect some Desktop widgets to be the root cause of this.

==Development Platform==

==Email==
Does starting
/usr/bin/maemo-summoner /usr/bin/modest.launch showui
provide some output?
===Debugging the connection to the mail server===
Can you please start an X Terminal window and enter
export "CAMEL_DEBUG"="all"
to enable the debug mode of the mail library, and after that
* Diablo:
/usr/bin/maemo-summoner /usr/bin/modest.launch showui > /home/user/MyDocs/.documents/log 2>&1

* Fremantle:
/usr/bin/maemo-summoner /usr/bin/modest.launch -s > /home/user/MyDocs/.documents/log 2>&1
to start the email application. Then try to connect to the mailserver.
Attach the logfile named "log" here which will be in your Home directory (please check for confidential data before attaching).

===Modest getting stuck (strace)===
Is Modest using any CPU?
What is the output if you strace it?
strace -p $(pidof modest|cut -d' ' -f1)
See http://maemo.org/development/tools/ and http://maemo.org/development/tools/doc/diablo/strace/ (Diablo) or http://wiki.maemo.org/Documentation/devtools/maemo5 and http://wiki.maemo.org/Documentation/devtools/maemo5/strace (Fremantle) for more information.

===Modest not exiting but eating CPU===
I assume you waited for 10 minutes to make sure that this wasn't any time taking resource freeing? Does this also happen if you are not using SSL?
A packet capture could help to clarify what causes the problem. tcpdump can be used on the Nokia device (Wireshark/Ethereal could be used from another host. Please take a look at http://maemo.org/development/documentation/man_pages/tcpdump.html for more information.
Can you kill the hanging process with signal=11 to provide us with a core dump?

==Flasher==
===Windows===
What are current versions (Control Panel/Add or Remove Programs) of WinFlasher+ (Nokia Internet Tablet Update Wizard) and Nokia Connectivity Cable Driver? What OS (XP, Windows 2000)? What is the exact error message you get? Is .NET 2.0 framework installed (Control Panel -> Add or Remove Programs)?

==Games==

==Images and Camera==

==Location==

==Map==

==Media player==

==Multimedia==

==Office Viewers==

==RSS feed reader==
* Can you please attach the contents of your device "/home/user/.osso_rss_feed_reader/" directory.
* Can you please install "strace" according to instructions here at http://maemo.org/development/tools/ (Diablo) / http://wiki.maemo.org/Documentation/devtools/maemo5 (Fremantle). Check with that what RSS feed reader does when/after it gets stuck and provide the output here: "strace -p $(pidof osso_rss_feed_reader|cut -d' ' -f1)" if it is already running, or "strace -f maemo-summoner /usr/bin/osso_rss_feed_reader.launch" to start it in strace.

==Settings and Maintenance==

===Application manager / Installing===
Hopefully some information will be in "Tools > Log" in the Application manager.
If you are familiar with apt you can also get a detailed error message by trying to install any package using "apt-get install" in the terminal window.

==Sharing==

==Statusbar Widgets==

==Synchronization==

===Mail for Exchange===
Can you please:
1) Check the "Known issues" section in http://wiki.maemo.org/Mail_for_Exchange
If this does not help:
2) Install syslog (see http://wiki.maemo.org/Documentation/devtools/maemo5/syslog ) and reboot
3) Open X Terminal
[optional steps begin]
3A. Enter "sudo gainroot" (to do that make sure that you have installed "rootfs" from the Application Manager)
3B. cat /dev/null > /var/log/syslog
[optional steps end]
4) Provide the output the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
5) Attach the file /var/log/syslog from the device to this bug (if needed, copy it first to the section that is visible in the File Manager: cp /var/log/syslog /home/user/MyDocs/.documents/ )

==System Analysis==

==System software==
===MMC/SD card related (Product "System software/mmc-and-usb")===
Has this happened with any other card? What is your card manufacturer, model and size?

==Telephony==

==Translations==

==UI Specification==

==User guide & Help content==

==Utilities==

==X-Graveyard (discontinued==
===Internet Tablet Video Converter===
AVI is just a container format, what matters is the codec. Can you please find out which codec your camera uses? You might want to check the camera manual. Thanks!
Are there any error messages when the crash happens?
Did the application install cleanly with no problems? Could you try to uninstall and reinstall again from a clean download please?

[[Category:Community]]
[[Category:maemo.org]]
[[Category:Bugzilla]]

Mail for Exchange

2010-02-25T08:43:52Z

192.100.124.218: /* How can I use my corporate address book (GAL) ? */

= Mail For Exchange (MfE) =

''For general informatipon on synchronising your N900 with a mail or calendar server, please see the [[sync]] page''

This page answers questions which are commonly asked by new N900 MfE users.
It is mostly based on the analysis of the [http://talk.maemo.org/showthread.php?t=35136 MfE support thread.]

The current version of the page addresses two versions of MfE:

* PR1.0, also known as "Sales release" (1.2009.42-11)
* PR1.1 (2.2009.51-1). [http://conversations.nokia.com/2010/01/14/nokia-n900-software-update-part-2/ Latest firmware update available from Nokia.]

See [[#How can I check what version of the software is installed in my N900?|How can I check what version of the software is installed in my N900?]] for steps to check what version of the software is installed in your device.

If you use PR1.0 (sales release) it is strongly advised to update to PR1.1.
See [http://wiki.maemo.org/Maemo_5/PR1.1 PR1.1 summary] for additional details and update instructions.

== Compatibility ==

=== What server versions are supported by N900 MfE client? ===

==== PR 1.0 ====

Microsoft Exchange 2007 with service packs on top. MS Exchange 2010 also works fine according to [http://talk.maemo.org/showthread.php?t=34981 users reports.]

In more technical terms, only EAS protocol 12.1 is supported and implementation is tested against MS Exchange 2007 servers. See [[#How can I check what versions of EAS protocol are supported by my server? |How can I check what versions of EAS protocol are supported by my server? ]] to check what EAS protocols are supported by your server.

==== PR 1.1 ====

* Microsoft Exchange 2007 with and without service packs on top. MS Exchange 2010 also works fine according to [http://talk.maemo.org/showthread.php?t=34981 users reports.]
* Microsoft Exchange 2003.

In more technical terms, EAS protocols 2.5, 12.0 and 12.1 are supported and implementation is tested against MS Exchange 2003 and 2007 servers. See [[#How can I check what versions of EAS protocol are supported by my server? |How can I check what versions of EAS protocol are supported by my server? ]] to check what EAS protocols are supported by your server.

=== What server versions are NOT supported by N900 MfE client? ===

==== PR 1.0 ====
* Microsoft Exchange 2003 is not supported.
* Microsoft Exchange 2007 without service packs is not supported.

The only way to get MfE working with these servers is to install PR.1.1 update which is [[#How can I check what version of the software is installed in my N900?|highly recommended.]]

==== PR 1.1 ====
* All non-MS services, although there has been [[Sync#Synchronising with Google | reported success]] synchronizing with Google and other non-MS services.

=== Why is feature XXX present in MfE for S60 but not for the N900? ===

S60 and Maemo MfE are different implementations.

The table below tries to summarize the most important differences between S60 and Maemo MfE implementations.

{| class="wikitable" border="1"
|-
! Feature
! S60 status
! Maemo status
|-
| ''E-Mail''
| YES, subfolders are not synced
| YES, subfolders are synced
|-
| ''Calendar''
| YES
| YES
|-
| ''Tasks''
| YES
| YES
|-
| ''Notes''
| ?
| NO
|-
| ''Meeting invitations replying''
| YES
| NO
|-
| ''Private appointments''
| YES
| NO
|-
| ''Corporate address book (GAL)''
| YES
| YES (*)
|-
| ''Exchange servers support''
| 2003, 2007
| 2003, 2007
|-
| ''Autodiscover''
| YES
| YES
|-
| ''Provisioning support''
| Partly YES
| NO
|-
|}

(*) This feature is supported in PR1.1 release but not in PR1.0 (sales release).

Lack of provisioning support in MfE for the N900 is the most common cause of problems with corporate Exchange servers in North America. See [[#Provisioning|Provisioning]] for additional details.

== Known issues ==

=== Provisioning ===

N900 is considered to be "non provisioning device" from Exchange server point of view. It basically means that it can not be managed from Exchange server - administrator can not wipe your device, request you to use autolock and so on. Basically, all the provisioning data received from the server is ignored and the server is informed that N900 MfE does not support this feature.

Exchange administrator can configure the server in 2 ways - he/she can allow to use non-provisioning devices or disallow. In the second case N900 MfE will not work as server will reject the connection.

[http://talk.maemo.org/showpost.php?p=350081&postcount=33 Post with Exchange server 2003 management console]

=== GAL support for Exchange 2003 ===

==== PR 1.1 ====
Corporate phone book support is broken for PR 1.1 release. Wait for the next MfE software update to fix it. It is broken only for Exchange 2003 servers (in more technical terms, for the EAS protocol 2.5).

=== SSL-related errors ===

The error message is displayed "Exchange server requires secure connection or account is disabled".

This infamous error message is caused by the fact that server certificate is untrusted from Maemo MfE client PoV.

Possible root causes and workarounds:

==== Server certificate is either self-signed or signed by the non-trusted authority (root certificate is not visible in N900 "Certificates" application).====

In this case, the server certificate shall be added to N900 certificate storage. Check [http://talk.maemo.org/showpost.php?p=401238&postcount=171 this message] and the thread after it for additional details.

Keep in mind - self-signed certificate shall have "CA" field. Otherwise, N900 certificate manager will not allow to install it. [http://talk.maemo.org/showpost.php?p=474320&postcount=871 This message] tells how to check does certificate has "CA" field or not.

Unfortunately, there is no way to disable certificates check at the client side in the current MfE releases (both PR1.0 and PR1.1).

==== PR1.0 ====

Disclaimer:

''The content of this section is applicable only for sales release (PR1.0). If you use this release, it is [[#How can I check what version of the software is installed in my N900?|highly recommended]] to upgrade the software to PR1.1 instead of following the advices below.''

* [http://talk.maemo.org/showpost.php?p=422732&postcount=312 Another important hint about importing certificates.]
* Server certificate is valid and trusted but MfE fails to sync. Check [https://bugs.maemo.org/show_bug.cgi?id=7357 this bug.]

=== HTML Messages ===

If you are using Exchange 2003 HTML messages will show as plain text. This is due to limitations of the ActiveSync protocol in this version of Exchange. The only way to get HTML support is to upgrade your server to Exchange 2007.

== Troubleshooting ==

=== How can I check what version of the software is installed in my N900? ===

* Open "Settings" view
* Scroll to the "General" section
* Open "About product" applet
* Check the "Version" string

Versions strings versus releases:

{| class="wikitable" border="1"
|-
! Version
! Release
|-
| 1.2009.42-11
| PR 1.0 (sales)
|-
| 2.2009.51-1
| PR 1.1
|-
|}

If you use PR1.0 (sales release) it is strongly advised to update to PR1.1.
See [http://wiki.maemo.org/Maemo_5/PR1.1 PR1.1 summary] for additional details and update instructions.

=== How can I check what versions of EAS protocol are supported by my server? ===

# Take the logs following the steps described in the section [[#How can I turn the logging ON or OFF?|How can I turn the logging ON or OFF?]]
# Grep (search) for "MS-ASProtocolVersions:" in the logs. It will contain the EAS protocol versions supported by your server.

=== How can I turn the logging ON or OFF? ===
Warning:

''Before sending the logs to somebody (including Nokia) or publishing them, check that the log files do not contain any data which you treat as private or confidentional!''

==== Turning the logging ON ====

# [http://wiki.maemo.org/Documentation/devtools/maemo5/syslog Install syslog] and reboot the device
# open terminal
# Execute the command: '''sudo gainroot'''
# Execute the command: '''cat /dev/null > /var/log/syslog'''
# Execute the following commands:
gconftool-2 -s --type=int /apps/activesync/AsDaemon/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/modest/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsProvider/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsBackup/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/asapplet/Syslog/MinLogLevel 0
gconftool-2 -s --type=int /apps/activesync/AsStatusApplet/Syslog/MinLogLevel 0
# Reboot the device
# Initiate the synchronization session

'''/var/log/syslog''' will contain the logs. In order to filter only activesync-specific logs the following command can be used:

grep activesync /var/log/syslog

In order to copy the activesync log to your computer follow the steps below:

# Make sure your N900 is not connected to any other device (including your desktop computer) through USB
# Open xterm (if it is not opened yet)
# Issue the command '''sudo gainroot''' (if it was not issued yet)
# Issue the command: '''grep activesync /var/log/syslog > /home/user/MyDocs/activesync.log'''
# Close xterm
# Connect your N900 to the computer through USB
# Wait while flash drive(s) will appear in your computer
# Find activesync.log in one of the disk drives
# Copy it to your computer
# Remove the file from N900
# (Safely) disconnect N900 from the computer

==== Turning the logging OFF ====

In order to turn the logs OFF, execute the following commands from xterm:

gconftool-2 -u /apps/activesync/AsDaemon/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/modest/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsProvider/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsBackup/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/asapplet/Syslog/MinLogLevel
gconftool-2 -u /apps/activesync/AsStatusApplet/Syslog/MinLogLevel

After device reboot the logs will not be collected.

==== Extended logging ====

There is the extended logging option for getting logged all data which are transmitted and received by ActiveSync protocol. This option requires as-daemon logging to be turned on as described above. Then, as-daemon process needs to receive USR2 signal. This also can be done from a device console:

$ ps ax | grep as-daemon

This command will produce output like this:

1503 user 25756 S /usr/sbin/as-daemon -D --pidfile=/var/lock/as-daemon

where 1503 is the <pid> value needed for the next command. The next command is kill -USR2 <pid>, so for this case, it is:

$ kill -USR2 1503

After that, extended logging is turned on and ready to be used. This option does not survive over reboots. It can be turned off by sending the same kill -USR2 <pid> command again.

Warning:

''Before sending the logs to somebody (including Nokia) or publishing them, check that the log files do not contain any data which you treat as private or confidentional!''

=== Pre-setting EAS protocol to be used on sync/ disable auto-negotiation ===

In certain scenarios it might be useful to disable MfE's built in auto-negotiation function on what sync protocol (EAS 2.5, 12.0 or 12.1) to be used during syncs and use a pre-defined default one instead. Some users report error messages/ fails in sync when trying to establish a connection with e.g. a Scalix Groupware server. For the time being (until solved on either side) a workaround has been established by presetting the sync protocol to EAS 2.5 manually. Scalix Groupware Server with Scalix-AS-1.0.2-addon has been reported working with EAS 2.5 on basic sync (calendar, contacts and email).
Before forcing MfE to use a specific protocol version make sure it is supported on the server-side.

To force MfE to use a particular protocol follow these steps:

# Start MfE configuration wizard entering the credentials on the first page and press "next". Do not enter the server address on page 2 yet!
# Open xterm and execute: '''sudo gainroot'''
# Execute the following commands:
##'''gconftool-2 -s --type=string /apps/activesync/ActiveSyncAccount1/use_version 2.5'''
##'''gconftool-2 -s --type=string /apps/activesync/ActiveSyncAccount1Temp/use_version 2.5'''
# Now continue MfE setup wizard and enter server address. Click next and follow the procedure to finish the wizard.

To check whether your changes have succesfully been submitted make sure you have [http://wiki.maemo.org/Documentation/devtools/maemo5/syslog syslog] installed and type in xterm:

sudo gainroot tail -f /var/log/syslog | grep "Created factory"

There won't be a output right away but when

* credentials are verified
* first sync started
* Wizard setup completed

you should be able to see *Created factory for version 2.5* on the terminal.
Pressing Ctrl+C will bring you back to the shell.

To disable the preset/ return to auto-negotiation it is recommended to delete the MfE-account and create a new one with the wizard from scratch.

Of course the above described way will also let you set EAS 12.0 or 12.1 as default protocols. Simply change the values on use_version in the respective gconftool commands.

=== Debugging possible certificate errors on self-signed certificates ===

You might experience an error message like "Either exchange server requires a secure connection or your account is disabled". This mostly occurs when syncing on secure connections by using a self-signed certificate and/or missing certificate authority (CA) tag in the respective field.

A quick way to check whether your certificate info gets rosolved properly by the maemo OS is a cli-tool called "cmcli".

Note: This is a system-wide certificate check - not a MfE-specific issue!

Please open terminal and type:

cmcli -T common-ca -v <your-server-dns-name-or-ip-address>:<port-number>
to check with one of the 118 pre-installed certificate authorities
or
cmcli -t ssl-ca -v <your-server-dns-name-or-ip-address>:<port-number>
when the chain of trust ends with a user-installed certificate. To be on the safe side, you can actually use both at the same time:
cmcli -T common-ca -t ssl-ca -v <your-server-dns-name-or-ip-address>:<port-number>

The missing tags have to be replaced with your personal server-address and respective port number (mostly 443 on SSL connections).

For instance: cmcli -T common-ca -v localhost:443

The output should read something like this:
0115e5345e4dd64855ed1e3d44060be25f26c2e6 nixu-jum
trust chain(1):
b5567d6c9eef05f07966d98eb2a85716bff4e80d Maemosec test CA
Verified OK

or

0115e5345e4dd64855ed1e3d44060be25f26c2e6 nixu-jum
Verification failed: self signed certificate

depending whether the verification succeeds or not.

If the verification fails and you want to see why, you can save the certificates the server sends by giving also the -s switch at the command line. Like this:

cmcli -T common-ca -sv <your-servers-dns-name-or-ip-address>:<port-number>

This will make the command to write the server certificates and possibly sent intermediate CA certificates into file(s) with the .pem-extension, where the name of each file is the SHA1 hash of the public key in hexadecimal. You can then study these file for instance with the command

openssl x509 -text -in <certificate-file>

== Miscellaneous ==

=== How can I use my corporate address book (GAL) ? ===

At first, [[#How can I check what version of the software is installed in my N900?|check that you use PR1.1 or later release of the software.]] If you use the release prior to PR1.1.1 check also [[#PR_1.1_3|the known problem of pre-PR1.1.1. Exchange 2003]] implementation.

It is possible to search for a contact in your corporate address book using "Contacts" application.

Follow these steps to add the contact from your corporate address book to the N900 address book:

* Open "Contacts" application
* Select "Get Contacts" option from the menu
* Choose "Import Mail Exch. contacts"
* Enjoy!

[[Category:HowTo]]
[[Category:Software]]
[[Category:Power users]]

Mobile Dev Camp 2010

2010-02-23T08:49:29Z

192.100.124.218: /* Participants list */

= Mobile Dev Camp 2010 =

[[Image: mdc.png]]

Nokia is one of the sponsors of this years' [http://mobiledevcamp.fi/ Mobile Dev-Camp] in Helsinki. Part of the engagement there is a developer competition. For the details please follow up on this page.

== Competition ==

Around the event there will be a competition and Nokia will organise one Category. Follow up in the Q&A what to expect and how you can participate:

=== What do I have to do? ===

Sign up, wait until the rules are out, have a brilliant idea, start coding, and present the application on the event. One thing, which we can say already:

* the application has to be written in Qt
* it has to work either on a Symbian device or the N900.

=== What can I win? ===

The winner-team of the competition gets:

* 1xN900 if your application runs on Maemo
* 1xN97 mini, if your application runs on Symbian
* 1xN900 '''AND''' 1xN97 mini if the application runs on both systems.

You can win if your application is implemented according to the rules, we release 48 hours before the event, and if it is selected as the best application by a jury.

=== What are the rules? ===

* You have '''48 hours''' to write an application!
* You will get basic support at the event itself and in the maemo MDC irc channel!
* We will publish the topic on Thursday before the event at 17:00 (UTC).

=== How can I prepare? ===

Check the information in the getting started section of this page. Further join the IRC channel on freenode (#nokia_MDC) to get support with the set-up.

=== How can I participate? ===

You can participate alone or as a group. Sign up by adding your data on the [[MDC#Participants_list | participants list]] or sending it to daniel[dot]wilms[at]nokia[dot]com! Check the topic out, when it will be published on Thursday. Start coding and present your idea at the event.

== Workshop at the event ==

People from Maemo Devices and Forum Nokia will be present in the Nokia workshop room during the entire event. Come around to ask questions, chat, ask for demonstrations and discuss about topics around the development environment. There won’t be a fixed schedule, but everything around your questions. Showing how to set-up the environment, small code-snippets, how to start developing for Nokia devices etc. The goal is to get the hands on Qt-development for mobile devices and have some fun. For the people who are working on applications for the competition, there will be support for all your questions.

== Getting Started ==

'''QtSDK'''

[http://qt.nokia.com/products/developer-tools QtCreator] is an easy to use cross-platform IDE. It includes QtDesigner, a powerful tool to create the UI. Further the QtSDK contains the libraries, which are necessary to compile and run your application in your native environment.

'''[http://qt.nokia.com/downloads Download the QtSDK for your system]'''

After downloading follow the installation instructions of the installer.

Special notes for Linux and Mac:
* Mac OS X: [http://developer.apple.com/tools/xcode/ XCode] required.
* Linux: GCC required.

'''MADDE'''

[[MADDE | MADDE]] is a command-line cross-compilation tool for Maemo 5. It offers a smooth way to compile your Qt application for the device. It is available for Windows, OS X and Linux.

'''[http://tablets-dev.nokia.com/MADDE.php Download MADDE]'''

=== Links ===

'''Qt'''

[http://doc.trolltech.com/4.5/index.html Qt documentation starting point]

[http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml Qt on Maemo 5 - Examples]

[http://wiki.maemo.org/Qt Qt on Maemo 5 - General information]

'''MADDE'''

[http://wiki.maemo.org/MADDE/Qt_Example Simple Qt example with MADDE]

[http://wiki.maemo.org/MADDE/Device_runtime How to test an application on Device]

[http://wiki.maemo.org/MADDE/FAQ MADDE FAQ]

[http://labs.trolltech.com/blogs/2010/02/15/qt-462-for-maemo-5-released/ Maemo, MADDE and Qt 4.6]

'''Maemo 5'''

[http://wiki.maemo.org/Documentation Maemo 5 documentation]

[http://wiki.maemo.org/Category:Development Development topics]

=== IRC ===

Join the channels on freenode:

'''#nokia_mdc'''

'''#qt-maemo'''

'''#maemo'''

[[Category:Mobile Dev Camp 2010]]

== Participants list ==

{| border=1 style="background:white"
|-
!style="width:300px;" | Name
!style="width:200px;" | Country
!style="width:300px;" | Number of team members
|-
|Team Tower
|Finland
|2
|-
|...
|...
|...
|}

Getting started with Maemo Garage

2010-02-02T10:42:23Z

192.100.124.218: fix typo

See [[Task:Using_garage.maemo.org]]

== About Garage ==

Garage is a software hosting platform for Maemo-related projects.

=== Services provided by Garage ===

* Website hosting
* Bugtracker
** Also includes a patch tracker, support tracker and feature request tracker
* Subversion hosting ([[Git_For_Garage|Git]] available on request)
** Web-based repository browsing
* Project file hosting (binary and source release archives)
** Ability to track number of downloads

== Creating a Garage project ==

=== Registering a Garage account ===

To create a Garage project you must have a Garage user account. The [https://garage.maemo.org/account/register.php Garage user registration page] can be found at the top of the [https://garage.maemo.org/ Garage home page].

=== Registering a project ===

The second step, after logging in, is to [https://garage.maemo.org/register/ register a project]. You will find this link at the [https://garage.maemo.org/my/ top of your developer's home page].

The list below shows requirements of a Garage project. You may be sucessful in acquiring project space if you remember the text on the [https://garage.maemo.org/ Garage home page], ‘This site is meant for hosting various software projects related to the maemo developer platform.’ Each project must determine these settings for themselves.

==== Project purpose and summary ====

The project purpose is perhaps one of the most important items on the list of requirements. The site administrator will approve your project primarily based on this statement.

==== License ====

Your project must have an open source license. Some suitable licenses are [http://opensource.org/licenses/category listed by the Open Source Initiative].

==== Project Public Description ====

Your project public description is your first communication with users, and so it is important to offer a concise outline of the project. However, the description can be revised at a later time.

==== Project Unix Name ====

The final requirement is the name that will be used for your project on the Garage servers. This name will be used in many tools and URLs, such as the project information page at <nowiki>https://garage.maemo.org/projects/unixprojectname</nowiki>, where ''unixprojectname'' is replaced with the selected name.

== Working with Subversion ==

{{main|Subversion}}


== Creating a website ==

To use Garage’s website hosting, a <code>www</code> directory containing a static website must be added as a toplevel directory in the Subversion (or Git) repository of the project. The index page should be named <code>index.html</code>, and be placed in the <code>www</code> directory. Changes to a project website must be made to the source code repository, like any source code changes, but are only visible on the project website after a delay of several minutes. A project website can be accessed from the project information page.

== Trackers and tasks ==

Trackers are provided for management of bugs, feature requests, patches and support discussion. A ‘Tracker’ link is available from the project information page if the tracker is enabled for a project. As an alternative to the Garage tracker, it is possible for a Garage project that has been uploaded to [[Extras]] to [[Bugs:Adding_Extra_products|request a component]] in [https://bugs.maemo.org/ maemo.org Bugzilla].

== Making releases ==

Source code and binary releases can be distributed with Garage with the ‘File’ link from the project information page. A release can be made with a changelog and release notes, so that users may read this information without having to download a release in full. A download count is provided for each release. Rather than distributing binary packages through Garage, it is recomended to upload packages to [[Extras]] to get the widest exposure and to make installation easier for users.

== External resources ==

* [http://gforge.org/ gForge] the project hosting software use by Garage
* [http://svnbook.red-bean.com/ Version control with Subversion book] a free online Subversion book, also available in print
* [http://tortoisesvn.tigris.org/ TortoiseSVN] a Windows SVN client

[[Category:Development]]

N900 FAQ

2010-01-19T09:43:01Z

192.100.124.218: /* Other Applications */

==This page is deprecated, don't add to it!==
The new [[FAQ|FAQ]] page is now live and incorporates a lot of what's in here, and will incorporate more as time goes on. Please add to that if you would like!

----

==== Hardware ====
The N900 is a pocketable computer with plenty of power (speed and memory) for running many demanding applications. The Nokia N900 hardware page can be found [[Nokia_N900|here]]

==== Operating System ====
The N900 runs the Maemo 5 Operating System. Maemo 5 is often referred to by its release name "Fremantle". You might be interested in gaming, or office applications, scientific applications, social media, movies or tunes. There will be specific Fremantle versions of your favorite applications.

If there's not an app yet, there almost certainly will be one at some point (you could also [http://maemo.org/development/ write it or port it yourself...]). Of course the N900 comes with a collection of built in applications that handle most mobile computing needs.

If you want an easy intro to many of Maemo5's features you might enjoy the videos on the [[Maemo5_101|Maemo5 101 page]]

====Applications====
Internet Tablets use the concept of software repositories, a concept carried over from Linux. You can tell your N900 where these repositories are via the Application Manager. The Application Manager automatically then presents you a list of available applications that can be installed on your device, and takes care of any dependancies that may be required.

There are multiple repositories available for the N900:

1.[http://maemo.nokia.com/maemo-select/applications/ovi-store/ Nokia's Ovi Store]

2. Commercial Application Vendors

3. [http://wiki.maemo.org/Installing_applications Community Applications]

The Application Manager also allows you to uninstall applications as well as keep you notified of updates to your installed applications.

You will also find One Click Install Applications on the web for instance in the [http://maemo.org/downloads/Maemo5/ Downloads] section of this web site.

If dont find the applciation that you want you can register you interest in [[Applications you wish were ported from other platforms]] on the wiki

====Emulators====
As well as native applications via the repositories Maemo also supports applications from a range of Emulators.

-Flash Games. As the N900 supports Flash 9 and has a hardware keyboard, many flash games should just work

-Garnet the Palm Emulator

-SNES Nintendo Emulation. nice video [http://www.youtube.com/watch?v=E0wbLaMXeu4 here]

====Other Applications====

How can I monitor my disk usage and how much space I have left?

Does n900 run Office files?

''N900 comes with datavz's Office 'Office to Go' reader, so you can read office files. It's not clear yet whether they will release a paid-for upgrade with editing facility. KOffice is available here'' (need link!) '' and will view Office files.''

Can I edit Office files?

'Editing has been disabled at least in the first release of KOffice for N900 due to round trip issues. However the source code for the UI is available for download and someone could easily it to allow editing.''

Does n900 view pdf files?

''Yes''

Does n900 have a book reader? Will it run Kindle?

Where do I find other applications and widgets for n900?

What do I do if the app I want isn’t there?

''First follow instructions from [[Downloading apps]] page. If not found, sign up to [http://talk.maemo.org/forumdisplay.php?f=44 Maemo Talk] and ask. If a few people are interested, or if a particular developer sees value in your idea, it's likely someone will write you an application to do what you want. And yes, that really does work.Or you can learn to program in Maemo or Qt yourself. There's a good set of tutorials [http://www.forum.nokia.com/Tools_Docs_and_Code/Documentation/Maemo.xhtml here, with a Hello world app too...]

====Battery====

Do I have to charge it fully before first use?

''No. It will come with some battery charge so you can play.''

Do I have to discharge it fully each time?

''No, n900 has a LIon battery, which doesn't need this. Older NiCad batteries did.''

Can I use the device while it’s charging?

''Yes.''

Is it safe to leave it charging overnight? Will it stop charging itself when it’s full?

''Yes''

====EMail====

''See the page on [[N900 Email Options]]''

====Games====

What games run on n900?

I’ve heard it can be used as a wiimote: how do I do that?

Will n900 play games from big companies?

What if I want a game not yet available?

All my previous phones have run java games: why can’t I play them on n900?

''Java is not currently available for the N900. You can follow the discussion [http://talk.maemo.org/showthread.php?t=31678 here]''

====GPS====

How good is the GPS on n900?

What’s the difference between GPS and a-GPS?

''GPS uses the Global Positioning Satellites to fix your devices location. A-GPS uses your network operators transmission towers to Assist the satellite signals to fix your devices location.A-GPS is coarse grained typically 100s of meters vs GPS sub Meter.
''

If I only use GPS (not a-GPS) will I still burn my data plan?

''Only if you have to download Map information''

What map programmes can I use?

''The N900 comes with Ovi Maps. Other map programs from third party developers will be available for download later. Nokia bought Navteq in 2007 and is the basis of OVi Maps ''

''As of October 2009, none of the "big names"--Garmin, Google, TomTom, etc.--have announced any plans to release software for the N900.''

Does n900 support google maps?

''You can use google maps directly from the browser, or you can try [http://talk.maemo.org/showthread.php?t=33645 MaeMaps]''

Can I download Ovi-maps when I’m on wifi, and store them for use so as not to burn my data plan? If so, how much space do they need?

See also...
''[http://talk.maemo.org/showthread.php?t=31273 here] and [http://talk.maemo.org/showthread.php?p=359714 here] and [http://talk.maemo.org/showthread.php?t=31897 here].''

====Internet====

Does n900 need a firewall?

''No.''

Does n900 need an anti-virus?

''No. The N900 runs Linux, an operating system for which few to no viruses exist. Beyond that, the N900 uses a processor (CPU) not used by desktop and notebook Linux machines. This means it's unlikely a (mostly theoretical) virus for desktop Linux could infect the N900.''

Can I block adverts?

''Adblock Plus is being developed for the Maemo browser on the N900 and will be available as a free download.''

Does n900 play YouTube?

''Yes.''

Does n900 play video from places other than YouTube?

Does n900 run BBC iplayer?

Does n900 have any ‘parental control’ settings?

====Media player====

Does n900 support itunes?

Will n900 play all my downloaded music? What if it has DRM?

How does n900 get the album art?

''The N900 Media Player supports ID3 Album art embedded in the MP3. Use your favourite Media Tagger application such as Media Monkey or our Own Maemo based [http://dz015.wordpress.com/2009/09/15/mussorgsky-0-3/ Mussorgsky]
''

What video codec does n900 support?

How do I rip a dvd for playing on n900?

How big a file would an hour of dvd be?

Can I download other video to play?

Are there ways of securing the video I’ve downloaded, so I can still give my n900 to others?

What connectors do I need to connect to a TV? What if my TV doesn’t have the right connections?

''The N900 comes with a cable to connect it to a composite input on a television. This connection is sometimes called an "RCA" connection and uses a yellow connector for video and a pair of connectors (red and white) for stereo audio.''

''The video out on the N900 may be switched between NTSC and PAL via "TV out" in the Settings application.''

''For televisions without a composite input, an adapter will be required. The specific adapter required for a given television will vary according to the input or inputs it accepts.''

What can I play over TV out? Will it only play video, or can I view whatever is on screen?

====MSN Messenger====

Please see [[MSN messenger]] -article.

====Phone use====

Does n900 have speed dial?

''You can put contact shortcuts on the desktop...

Does n900 have voice dialing?

''No.''

How do I access my carrier’s answering service - it used to be speed dial set in my old phone?

''If it is in the simcard, it should be imported in the abook, if it is not, then you probably want to copy it from your old phone manually.''

Does n900 log calls for length?

''Yes.''

Can I sort calls by received/sent/missed?

''No.''

I can use the phone in portrait mode: why can’t I use that for other things?

''N900 doesn't '''currently''' support portrait mode beyond the phone use. It is expected this will arrive in an update before the end of 2009, and some developers are working on applications that use portrait mode. '''Watch this space'''.''

====Texts====

I hear n900 doesn’t have MMS: is this true?

''N900 doesn't support MMS at release. This is because MMS uses the old 'WAP' form of connection, which n900 doesn't do. It only has GPRS internet connection. There are developers working on finding a work-around right now. '''Watch this space'''.''

Does n900 have message receipt?

''Conversations, the SMS and IM application, can optionally "Receive text message delivery reports". This option is disabled by default, but may be enabled in the Settings area of Conversations.''

Can I use an onscreen keyboard?

''An on-screen keyboard is available. It is disabled by default, but may enabled via "Text input" in the Settings application.''

''The on-screen keyboard is landscape in orientation and alphanumeric. Its layout is QWERTY, QWERTZ, etc. as is regionally appropriate.''

Is there a portrait mode keyboard?

''There is a portrait mode dialing pad for making calls. Beyond that no, there is no portrait mode keyboard. One or more third party developers may make add-on portrait mode keyboards available for download later.''

Is there T9 entry?

''No, though this could be added by a third party developer later.''

====Troubleshooting====

I installed something and now my n900 isn’t working right.

I installed something and now my n900 isn’t working at all.

''In case of trouble, you should start by reading article [[Troubleshooting]] through. It has both cases <bove covered. ''

There’s a light flashing on my n900
''Look at [[Maemo5 101]] for further info about what different colour and blinking means''

How often do I need to update? And why?

''N900 is 'updatable software', so it will go on getting better. Your device will check for updates once a day, and tell you when it needs to update by putting a little yellow icon on the screen. Then it will walk you through the update process. You can wait to update when you are somewhere where it's beter to download - for example your using your home netwrk rather than your data plan.''

[[Category:N900]]

Eclipse integration/Known issues

2010-01-04T14:11:36Z

192.100.124.218: /* Maemo PC Connectivity */

= Known Issues for Maemo Eclipse Integration Edition 2 Final release (R2.0.0) =

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.

Release Notes are here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.

== Product baselines ==

* N900 device with Maemo Fremantle 5.x platform releases
* Fremantle 5.0 SDK, the latest final release
* N8x0 devices with Maemo Diablo 4.1.x platform releases
* Diablo 4.1.2 SDK, the latest maintenance release

== Product configuration ==

* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications

* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC

* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC

== Maemo Mica plugin framework for Eclipse ==
* none (so far :)

== Maemo ESbox for Eclipse ==

* Hover help for Python does not work on ESBox because documentation has not been integrated.

* Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed.
** workaround is to restart the Maemo SDK binary installation until it goes through without errors.

* If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device.
** workaround is to select '''Project -> Validate Installed Packages''' from Eclipse IDE which verifies the integrity of installed development environments and re-installs missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.

* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

== Maemo PluThon for Eclipse ==

* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated

== Maemo PC Connectivity ==

* Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
** N900 will not support USB host mode
*** no workaround (N900 HW issue)
** N900 will not support IP Forwarding (iptable NAT kernel modules)
*** workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
** N900 will not support BlueTooth connections simultaneously with WLAN connections
*** no known workaround
** N900 will not support "USB Networking" with platform default USB applet but only "PC Suite" and "Mass Storage" mode (applet provided by PC Connectivity supports also USB Networking)
*** workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
*** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets
*** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change
** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
*** workaround is to use only SSHFS mounts with Cygwin
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server
*** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit)
** Fremantle SDK does not support CPU Transparency
*** workaround is to build and install new SBRSH client manually inside Scratchbox

* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems

* When creating a project and setting SBRSH as download method errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset).
** workaround is to restart Maemo device.

* WLAN connection may get broken if WLAN and USB Networking are used simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
** workaround is to re-flash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)

* Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported)
** Cygwin 1.7 beta installation may require manual configuration for Maemo
** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it
** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for Cygwin 1.7 SSHD service
*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.
* SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse"
** workaround is to add user account used to "fuse" group

== Maemo SDK Virtual Images ==

* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes

* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine)
** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image

* Changing network configuration after installation of VMWare, VirtualBox or QEMU and Maemo SDK Virtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK.
** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

== Maemo Flasher-3.5 Tool ==

* none (so far)

== Integration testing ==

* Some publicly available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

----
Feedback can be sent to eclipse-integration@maemo.org

[[Category:Eclipse]]

Eclipse integration/Known issues

2010-01-04T14:10:46Z

192.100.124.218: /* Maemo PC Connectivity */

= Known Issues for Maemo Eclipse Integration Edition 2 Final release (R2.0.0) =

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.

Release Notes are here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.

== Product baselines ==

* N900 device with Maemo Fremantle 5.x platform releases
* Fremantle 5.0 SDK, the latest final release
* N8x0 devices with Maemo Diablo 4.1.x platform releases
* Diablo 4.1.2 SDK, the latest maintenance release

== Product configuration ==

* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications

* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC

* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC

== Maemo Mica plugin framework for Eclipse ==
* none (so far :)

== Maemo ESbox for Eclipse ==

* Hover help for Python does not work on ESBox because documentation has not been integrated.

* Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed.
** workaround is to restart the Maemo SDK binary installation until it goes through without errors.

* If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device.
** workaround is to select '''Project -> Validate Installed Packages''' from Eclipse IDE which verifies the integrity of installed development environments and re-installs missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.

* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

== Maemo PluThon for Eclipse ==

* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated

== Maemo PC Connectivity ==

* Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
** N900 will not support USB host mode
*** no workaround (N900 HW issue)
** N900 will not support IP Forwarding (iptable NAT kernel modules)
*** workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
** N900 will not support BlueTooth connections simultaneously with WLAN connections
*** no known workaround
** N900 will not support "USB Networking" with platform default USB applet but only "PC Suite" and "Mass Storage" mode (applet provided by PC Connectivity supports also USB Networking)
*** workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
*** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets
*** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change
** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
*** workaround is to use only SSHFS mounts with Cygwin
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server
*** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit)
** Fremantle SDK does not support CPU Transparency
*** workaround is to build and install new SBRSH client manually inside Scratchbox

* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems

* When creating a project and setting SBRSH as download method errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset).
** workaround is to restart Maemo device.

* WLAN connection may get broken if WLAN and USB Networking are used simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
** workaround is to re-flash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)

* Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported)
** Cygwin 1.7 beta installation may require manual configuration for Maemo
** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it
** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for Cygwin 1.7 SSHD service
*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.
** SSHFS may not be usable for "normal" user account. This is because /dev/fuse is not writable by default for "normal" users. /dev/fuse is usually writable only for group "fuse"
*** workaround is to add user account used to "fuse" group

== Maemo SDK Virtual Images ==

* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes

* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine)
** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image

* Changing network configuration after installation of VMWare, VirtualBox or QEMU and Maemo SDK Virtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK.
** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

== Maemo Flasher-3.5 Tool ==

* none (so far)

== Integration testing ==

* Some publicly available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

----
Feedback can be sent to eclipse-integration@maemo.org

[[Category:Eclipse]]

Eclipse integration/Known issues

2010-01-04T10:39:25Z

192.100.124.218: /* Maemo PC Connectivity */

= Known Issues for Maemo Eclipse Integration Edition 2 Final release (R2.0.0) =

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

Detailed list of new features implemented to Maemo Eclipse Integration since previous PreFinal release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.

Release Notes are here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_final.

== Product baselines ==

* N900 device with Maemo Fremantle 5.x platform releases
* Fremantle 5.0 SDK, the latest final release
* N8x0 devices with Maemo Diablo 4.1.x platform releases
* Diablo 4.1.2 SDK, the latest maintenance release

== Product configuration ==

* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications

* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC

* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/) for VNC client to work on host PC

== Maemo Mica plugin framework for Eclipse ==
* none (so far :)

== Maemo ESbox for Eclipse ==

* Hover help for Python does not work on ESBox because documentation has not been integrated.

* Installing Nokia binaries may sometimes fail with exit code 100 when Maemo SDK gets installed.
** workaround is to restart the Maemo SDK binary installation until it goes through without errors.

* If during Maemo SDK installation to other than Debian based Linux operating systems the default options for Maemo SDK Virtual image installation wizard are chosen and Nokia binaries installation fails, wizard proceeds normally to end (installing Development Environments for C/C++, Python and Qt). If you choose to cancel the installation because failed Nokia binaries Development Environments are not installed properly to the Maemo SDK and Maemo device.
** workaround is to select '''Project -> Validate Installed Packages''' from Eclipse IDE which verifies the integrity of installed development environments and re-installs missing packages for C/C++, Python and Qt to the Maemo SDK and Maemo device.

* Maemo Diablo SDK has ARMEL debugging problems when using Ubuntu Karmic host PC. If Maemo Diablo SDK is installed to Ubuntu Karmic environment native-gdb script will not work but gives segment fault which prevents debugging operations on Maemo SDK ARMEL rootstrap.
** see more details from this bug report https://bugs.maemo.org/show_bug.cgi?id=7106

== Maemo PluThon for Eclipse ==

* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated

== Maemo PC Connectivity ==

* Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
** N900 will not support USB host mode
*** no workaround (N900 HW issue)
** N900 will not support IP Forwarding (iptable NAT kernel modules)
*** workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
** N900 will not support BlueTooth connections simultaneously with WLAN connections
*** no known workaround
** N900 will not support "USB Networking" with platform default USB applet but only "PC Suite" and "Mass Storage" mode (applet provided by PC Connectivity supports also USB Networking)
*** workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
*** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets
*** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change
** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
*** workaround is to use only SSHFS mounts with Cygwin
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server
*** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit)
** Fremantle SDK does not support CPU Transparency
*** workaround is to build and install new SBRSH client manually inside Scratchbox

* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems

* When creating a project and setting SBRSH as download method errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" may happen when SBRSH is used first time with Maemo device (for example after device flashing when SSH keys need to be reset).
** workaround is to restart Maemo device.

* WLAN connection may get broken if WLAN and USB Networking are used simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
** workaround is to re-flash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)

* Windows 7 (and Vista) support is only beta level because Cygwin 1.7 (first Cygwin release to support Windows 7 and Vista) is on beta level (Windows XP with Cygwin 1.5 is fully supported)
** Cygwin 1.7 beta installation may require manual configuration for Maemo
** Cygwin 1.7 beta X11 may crash when Maemo applications are run with it
** Host PC Connectivity does not install if Vista or Windows 7 machine is part of Windows Domain because it fails to create new user for Cygwin 1.7 SSHD service
*** workaround (but not recommended) is to try manual installation and configuration of Cygwin 1.5 also for Windows 7 (and Vista). Notice that Cygwin project does not support Windows 7 or Vista with Cygwin 1.5 version.

== Maemo SDK Virtual Images ==

* By default NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
** workaround is to update resolv.conf file for Scratchbox manually after Maemo SDK installation and/or after network changes

* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine)
** workround is to use VMWare Player version 2.5.x or use only Bridged network mode for Maemo SDK Virtual Image

* Changing network configuration after installation of VMWare, VirtualBox or QEMU and Maemo SDK Virtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK.
** workaround is to manually reconfigure network changes to the Virtualisation Environment and Maemo SDK. Log in to the Maemo SDK Virtual Image and invoke DHCP client with "sudo dhclient" to see network configuration or reconfigure network interfaces after network changes

== Maemo Flasher-3.5 Tool ==

* none (so far)

== Integration testing ==

* Some publicly available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

----
Feedback can be sent to eclipse-integration@maemo.org

[[Category:Eclipse]]

Talk:Opt Problem/Non-Optified packages

2009-12-29T14:46:44Z

192.100.124.218: what to optify and measure

I don't think it makes sense to optify SSH. SSH could be used to debug problem bootup problems and one of them may be /home (with opt) not getting mounted.

I would also recommend using LZO packed sizes of the package contents as the rootfs is compressed. Non-compressed package size, or the size reported by dpkg are bogus in regards to disk usage. Script attach to https://bugs.maemo.org/show_bug.cgi?id=5795 bug might help in estimating the compressed size.

Eclipse integration/Known issues

2009-12-14T11:39:34Z

192.100.124.218: /* Maemo ESbox plugin for Eclipse */

= Known Issues for Maemo Eclipse Integration Edition 2 Final release =

More detailed known issues lists can be found from Garage projects for each product https://garage.maemo.org/.

== Product baselines ==

* N900 device with Maemo Fremantle 5.x platform releases
* Fremantle 5.0 SDK, the latest final release
* N8x0 devices with Maemo Diablo 4.1.x platform releases
* Diablo 4.1.2 SDK, the latest maintenance release

== Product configuration ==

* Maemo SDK ARMEL rootstrap is meant to be used only for cross-compiling and it does not support running or debugging applications
* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Tablet for USB Networking to work with Windows host PC
* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Tablet from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/2nd_edition/main.html#SECTION00030000000000000000) for VNC client to work on host PC

== Maemo Mica plugin framework for Eclipse ==

== Maemo ESbox plugin for Eclipse ==

* When running or debugging SBRSH applications using sandbox mode, applications cannot be terminated from the UI.
* Hover help for Python does not work on ESBox because documentation has not been integrated.
* Maemo Qt 4.5 support for Fremantle is only for Fremantle SDK but not for N900 device because N900 device does not have development environment available (Qt 4.5 works fine with Dibalo SDK and N8x0 devices).

== Maemo PluThon plugin for Eclipse ==

* Hover help for Python for Maemo API documents does not work on Pluthon because documentation is not integrated
* Python installation package creation with N900 device does not work because Python for Maemo Fremantle does not install python-distutil package to the device. N8x0 devices work fine. See https://bugs.maemo.org/show_bug.cgi?id=6161

== Maemo PC Connectivity ==

* Maemo PC Connectivity functionality with N900 device and Fremantle is more limited than with N800/N810 device with Diablo
** N900 will not support USB host mode
*** no workaround (N900 HW issue)
** N900 will not support IP Forwarding (iptable NAT kernel modules)
*** workaround is to rebuild Fremantle kernel with NAT enabled and hack kernel symbols for NAT kernel modules
** N900 will not support BlueTooth connections simultaneously with WLAN connections
*** no known workaround
** N900 will not support "USB Networking" with platform default USB applet but only "PC Suite" and "Mass Storage" mode (applet provided by PC Connectivity supports also USB Networking)
*** workaround is to use ONLY configuration applet provided by PC Connectivity instead of default applet
*** Notice that USB mode changes are possible only if USB cable is plugged-out and plugged-in between mode changes with both applets
*** Notice that if both applets (platform default USB applet and PC Connectivity applet) are used for mode changes device may fail to change mode after first change
** Fremantle platform does not have libicd-dummy package available until final release and thus user cannot navigate to Internet through the browser using USB and BlueTooth. He/she will be able to navigate only using WLAN (standard behavior)
*** final PC Connectivity release will have libicd-dummy package
** Samba does not work with Fremantle platform and N900 causing disk mounts between N900 and Windows host PC to fail
*** will be (hopefully) fixed for final release
** Fremantle platform and SDK support ONLY 16-bit color depth for X Server
*** workaround is to configure host PC X Server (in Windows and Mac OS X) to use 16-bit depth instead of default one (if default does not happen to be 16-bit)
* Configuring connectivity to work between Maemo device and host PC after installation is still partly manual work on host PC side for all supported operating systems
* When creating a project and setting SBRSH as download method quite often errors like "sbrsh server: fuse: bad mount point" and "sbrsh server: Can't mount to point:" happens. As a workaround you need to restart SBRSHD (on Maemo device side) and restart ESBox (on host PC side)
* WLAN connection may get broken if using WLAN and USB Networking simultaneously. Connection problems may occur after some time (can take hours or days) when device is (re)started and WLAN tries to connect.
** when the problem occurs user gets "Internet connection failed. Unable to retrieve IP address from server" error
** workaround is to reflash Maemo device or manually assign IP number to the connection (which may cause problems with DHCP)
* If FileZilla has already been installed to the Mac OS X host PC, installation of Host PC Connectivity with default settings fails
** workaround is to move FileZilla first to trash and then reinstall Host PC Connectivity or select not to install FileZilla with Host PC Connectivity

== Maemo SDK Virtual Image ==

* NetworkManager is being started after Scratchbox, so the resolv.conf file used by Scratchbox may be invalid which causes network problems
* VMWare Player version 3.0 may have problems to keep ssh connection live in NAT mode (notice that VMWare Player 2.5 or Bridged mode works fine)
* Changing network configuration after installation of VMWare, VirtualBox or QEMu and Maemo SDK VIrtual Image may require reconfiguration of network also for the virtualisation environment and Maemo SDK. Usually, log in to the image and invoke "sudo dhclient".

== Maemo Flasher-3.5 Tool ==

* Flasher-3.5 for Mac OS X supports only Mac OS X 10.6 Snow Leopard. Flasher-3.5 binary built for 10.6 does not work with Mac OS X 10.5 Leopard but requires new build and new 10.5 binary to be added to the Mac installation package.
** will be fixed to the final release

== Integration testing ==

* Some publically available test suites (for Eclipse components and NFS mounts, for example) are run on Linux, Windows and Mac OS X during integration testing but frameworks and test sets are not yet ready to be published

* Test results (for unit tests and integration tests) for official releases are not yet ready to be published together with products

----
Feedback can be sent to eclipse-integration@maemo.org

[[Category:Eclipse]]

Documentation/devtools/maemo5

2009-12-09T15:36:25Z

192.100.124.218: Diablo->Fremantle

These tools are available in the official maemo 5 Fremantle tools repository at repository.maemo.org. Some of them may have already been available unofficially, but these versions are tested for functionality.

You can propose new tools by filing an enhancement request in Bugzilla.

Installation instructions are available [[#Installation | below]].

== Categories ==

The tools are arranged into different categories so that you can easily see what tools are available for specific kinds of tasks. The same tool can be present in multiple categories.

=== Code Analysis ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/doxygen | doxygen]] || a source code documentation generator tool
|-style="background:white"
| [[Documentation/devtools/maemo5/gtk-doc | gtk-doc]] || an API documentation generator
|}
=== Debugging ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/gdb | gdb]] || GDB is the GNU debugger
|-style="background:white"
| [[Documentation/devtools/maemo5/functracer | functracer]] || an allocation backtrace tool
|-style="background:white"
|[[Documentation/devtools/maemo5/functracer-postproc | functracer-postproc]] || a post-processing tool for functracer output data
|-style="background:white"
| [[Documentation/devtools/maemo5/latrace | latrace]] || display a program's dynamic library calls
|-style="background:white"
|[[Documentation/devtools/maemo5/ltrace | ltrace]] || a library call tracer
|-style="background:white"
| [[Documentation/devtools/maemo5/maemo-debug-scripts | maemo-debug-scripts]] || a set of scripts to help with debugging tasks
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-error-visualizer | sp-error-visualizer]] || displays log messages as banners
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-rich-core | sp-rich-core]] || a core dump data saver
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-response-time | sp-response-time]] || a library for monitoring UI response times
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-startup-time | sp-startup-time]] || a library for calculating application startup times
|-style="background:white"
| [[Documentation/devtools/maemo5/strace | strace]] || a system call tracer
|-style="background:white"
|[[Documentation/devtools/maemo5/syslog | syslog]] || a log message collecting service
|-style="background:white"
| [[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
|[[Documentation/devtools/maemo5/x11-utils | x11-utils]] || a collection of X Window System debugging tools; xev, xwininfo, xprop, xlsatoms and xlsclients.
|}

=== Miscellaneous ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/less | less]] || a text file viewer/pager
|-style="background:white"
| [[Documentation/devtools/maemo5/osso-xterm | osso-xterm]] || a terminal emulator
|-style="background:white"
|[[Documentation/devtools/maemo5/man-db | man-db]] || manual page infrastructure
|-style="background:white"
| [[Documentation/devtools/maemo5/screen | screen]] || provides access to detachable console sessions
|}
=== Editors ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/nano | nano]] || a friendly text editor
|-style="background:white"
| [[Documentation/devtools/maemo5/vi | vi]] || a text editor
|}
=== Graphics ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/screenshot-tool | screenshot-tool]] || a command line utility to take screenshots
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|-style="background:white"
|[[Documentation/devtools/maemo5/xresponse-visualize | xresponse-visualize]] || scripts for visualizing xresponse logs
|}
=== Networking ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/iputils | iputils]] || a collection of TCP/IP related utilities
|-style="background:white"
| [[Documentation/devtools/maemo5/netcat | netcat]] || a utility to read and write data across network connections
|-style="background:white"
|[[Documentation/devtools/maemo5/tcpdump | tcpdump]] || a network traffic capturing utility
|-style="background:white"
| [[Documentation/devtools/maemo5/traceroute | traceroute]] || print the route packets take to a network host
|-style="background:white"
|[[Documentation/devtools/maemo5/wget | wget]] || a utility to non-interactively download files from the Web
|}
=== Performance ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/oprofile | oprofile]] || a low overhead system wide profiler
|-style="background:white"
| [[Documentation/devtools/maemo5/oprofileui | oprofileui]] || a user interface to oprofile
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-startup-time | sp-startup-time]] || a library for calculating application startup times
|-style="background:white"
|[[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|-style="background:white"
|[[Documentation/devtools/maemo5/xresponse-visualize | xresponse-visualize]] || scripts for visualizing xresponse logs
|}

=== Resource Usage ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/functracer | functracer]] || an allocation backtrace tool
|-style="background:white"
| [[Documentation/devtools/maemo5/functracer-postproc | functracer-postproc]] || a post-processing tool for functracer output data
|-style="background:white"
|[[Documentation/devtools/maemo5/htop | htop]] || an interactive process viewer
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-endurance | sp-endurance]] || tools to collect system endurance related information
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-endurance-postproc | sp-endurance-postproc]] || postprocessing scripts to parse and generate a report from endurance measurement data
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-memusage | sp-memusage]] || a collection of memory usage monitoring tools and scripts
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-smaps-measure | sp-smaps-measure]] || utilities for taking snapshots of smaps memory information
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-smaps-visualize | sp-smaps-visualize]] || utilities for analyzing smaps memory information
|-style="background:white"
|[[Documentation/devtools/maemo5/sysstat | sysstat]] || tools for collecting and reporting system activity information
|-style="background:white"
| [[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
|[[Documentation/devtools/maemo5/xrestop | xrestop]] || shows X clients' X resource usage
|}
=== Test Automation ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/check | check]] || a unit test framework for C
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-stress | sp-stress]] || tools to create artificial system load
|-style="background:white"
|[[Documentation/devtools/maemo5/xnee | xnee]] || automate user actions under X11
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|}
=== Wireless Tools ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/bluez-hcidump | bluez-hcidump]] || a tool to monitor Bluetooth activity
|-style="background:white"
| [[Documentation/devtools/maemo5/wireless-tools | wireless-tools]] || tools for manipulating Linux Wireless Extensions
|}
== Installation ==

These tools can be installed in the device by activating the Fremantle tools repository in the Application manager. Developers can also install them to the device or in Scratchbox using the command line interface.

To activate the tools repository with the Application manager,
[http://mg.pov.lt/770/tools-repository.install open this single-click install file], or manually create a new catalogue like this:

{|
|-
|Catalogue name: || fremantle tools
|-
|Web address: || http://repository.maemo.org
|-
|Distribution: || fremantle/tools
|-
|Components: || free non-free
|-
|Disabled: || leave unchecked
|}

If you prefer to edit configuration files yourself instead of using the Application manager, add these lines to your ''/etc/apt/sources.list''

<pre>
# fremantle tools
deb http://repository.maemo.org fremantle/tools free non-free
# fremantle tools sources
deb-src http://repository.maemo.org fremantle/tools free non-free
</pre>

To install a binary package in Scratchbox:

<pre>
$ fakeroot apt-get install <bin pkg name>
</pre>

To install a binary package to the device (as root):

<pre>
$ apt-get install <bin pkg name>
</pre>

To install a source package in Scratchbox or to the device:

<pre>
$ apt-get source <src pkg name>
</pre>

Documentation/Maemo 5 Final SDK Installation

2009-12-04T12:25:33Z

192.100.124.218: /* Installation procedure */

=Introduction=

The following document describes the installation of the Maemo 5 Final SDK. Maemo SDK uses Scratchbox as the cross compilation environment into which Maemo specific development files are installed.

Before we begin with the installation, have a look at the minimum system requirements. We officially support x86-32 Debian based distributions, mainly Debian and Ubuntu though it is possible to install the SDK on other flavours of Linux too.

Once you are sure that your development machine fulfils these requirements, you can proceed with the following guidelines:

Maemo 5 SDK comes with two command line installation scripts and GUI installer (beta) to ease the SDK installation.
*Scratchbox installer script which downloads and installs the required version of Scratchbox onto your host machine.
*Maemo SDK installer which sets up two targets (armel and x86) inside Scratchbox, downloads the minimal rootstraps for both targets, and installs the open source development files based on the user selection during the installation process.
*GUI installer which combines both Scratchbox and SDK installation.

Maemo 5 SDK also provides the essential Nokia proprietary binary packages needed for Maemo development and additional Nokia applications in an authenticated repository. In order to have access to this repository, you will need to accept the End User License Agreement (EULA).   For the complete functionality and usability of the Maemo SDK, it is required to install Nokia proprietary binary packages in addition to the open source packages.

==What is not included in the Maemo SDK?==
Xephyr X11 server software is needed on your host machine before you can run any applications in the Maemo SDK. It is an X11 server that provides a device screen for the developer so that you can see all the Maemo application windows and visuals on your host machine. This software is not included in the SDK mainly because it is available on most linux distributions.

If you choose to install Maemo SDK using the GUI installer on Debian based systems, it will provide an option to install Xephyr for you.

If not, you can manually install Xephyr as follows:

On Debian based linux systems, Xephyr can be installed outside Scratchbox environment using apt with root permission:

$ sudo apt-get install xserver-xephyr

On a Gentoo system you need to install xorg-server with the kdrive useflag. This builds the Xephyr binary.

=Installing Maemo 5 SDK using GUI Installer=

Maemo 5 SDK installation is now made easy with GUI installer. This
installer will install Scratchbox and Maemo 5 SDK on Debian based
systems. This installer will allow installation of nokia closed packages and
applications provided that EULA[http://tablets-dev.nokia.com/eula/index.php this webpage] is accepted.

'''GUI Installer has following features:'''
* Install/Upgrade Scratchbox
* Installation of Maemo 5 SDK
* Installation of nokia-binaries
* Installation of nokia-apps
* Installation of Xephyr
* Creates a launcher for Xephyr on Desktop
* Creates a shortcut to Scratchbox home folder on Desktop
* Creates Maemo 5 info page on Desktop that contains useful links for developers

GUI installer offers standard and custom installation modes in a wizard. Standard installation will use default settings, while custom offers more choices. Please note that standard mode will overwrite any of the standard targets (FREMANTLE_X86, FREMANTLE_ARMEL) if present, but contents of Scratchbox home will be preserved. Please use the custom mode if you don't want to overwrite your targets.

The GUI installer Qt application requires python bindings for Qt. GUI installer can install the required packages if not already installed.

The installer will use http_proxy environment variable if available. If
your connection doesn't seem to work, you will be asked to manually
enter proxy settings.

GUI installer has been tested on Ubuntu Karmic and Debian Lenny, both 32bit and 64bit versions. The GUI installer needs to download Maemo SDK so it requires a working Internet connection.

'''Starting installation with GUI installer:'''

There is some missing options in this python script if you run from non-debian linux systems you got errors, because it will not automatically define the installation path of scratchbox, to correct this errors you must patch this script.

Also you must uncheck Xephyer checkbox and install it manually.

129c129
< SB_PATH = "/scratchbox"
---
> SB_PATH = "/opt/scratchbox"
2297a2298
> opt = opt + "-s /opt/scratchbox"
2351a2353
> cmd = cmd +" -s /opt/scratchbox"

$ wget http://repository.maemo.org/stable/5.0/maemo-sdk-install-wizard_5.0.py
$ chmod a+x maemo-sdk-install-wizard_5.0.py

$ Installer requires root preveliges
Ubuntu
sudo ./maemo-sdk-install-wizard_5.0.py
Debian
su -c ./maemo-sdk-install-wizard_5.0.py

'''Limitations:'''
*As the installer will do package installation, you should quit all package managers before running it.
*Please note that detecting scratchbox is not perfect and it will detect only if it is installed in /scratchbox path.
*Please note that python-qt features used in this installer might not be available in older ubuntu and debian distros.
*Installer only showss required settings on 64-bit machines but does not add them automatically.
*Installer will always use DISPLAY :2, if you want to use a different value, you need to change it manually.

=Installing Maemo 5 SDK on x86-32 Debian based distribution=

1. Download the scratchbox installer and the Maemo SDK installer scripts. These are the same scripts as are available through Forum Nokia: [http://www.forum.nokia.com/Tools_Docs_and_Code/Tools/Platforms/Maemo/ Maemo SDK at Forum Nokia].

$ wget http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

2. Set the permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

3. Run the scratchbox installer with root permission specifying the username to be added to scratchbox users group and sbox group. The username should be an existing user name from the host linux system. This will download about 420 MB of material from the web, which is not resumeable if interrupted.

$ sudo ./maemo-scratchbox-install_5.0.sh -u USER

4. The installation script adds the specified user to ‘sbox’ user group. For the group membership to be effective in the current terminal session, run the following command:

Note: This command will change the existing group ID during the current login session to ‘sbox’. If you do not want this change, just logout and log back in again for the group membership to be effective.

$ newgrp sbox

At this step, you should have a working Scratchbox environment ready.

5. Proceed further to run the Maemo SDK installer script. This script is run as 'user' outside the scratchbox environment.

$ ./maemo-sdk-install_5.0.sh

If you have installed Scratchbox in a path alternative to /scratchbox, you will need to specify the path with ‘-s PATH’ option. More information on available command line options can be found with --help option
Follow the instructions on the go.

6. Once the script has successfully completed its execution, you can login into Scratchbox.

$ /scratchbox/login

If you are not able to login, take a look at the [[#Limitations of Scratchbox|limitations of Scratchbox]].

7. Proceed further to accept the EULA in order to obtain the Nokia proprietary binary packages. These Nokia binaries are essential for the complete functionality of the Maemo SDK.

7.1. Accept the EULA on [http://tablets-dev.nokia.com/eula/index.php this webpage] 
7.2. Copy the sources.list entry given to you after the license acceptance to your Scratchbox x86 and armel target’s /etc/apt/sources.list file. Execute the commands below on the _ARMEL and _X86 targets.

[sbox-FREMANTLE_X86: ~] > sb-conf select FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install nokia-binaries nokia-apps

[sbox-FREMANTLE_ARMEL: ~] > sb-conf select FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > nano /etc/apt/sources.list # add deb line
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install nokia-binaries nokia-apps

The above step installs all needed Nokia proprietary binary packages along with the open source binaries that have dependencies to Nokia proprietary binary packages.
With this, your Maemo 5 SDK environment is set up completely and ready for development.

=Starting/Shutting down the SDK UI=

Before starting the UI framework, ensure that you have installed the following:
*Xephyr X11 server on the host machine outside the Scratchbox environment
*The SDK as described above
*The Nokia proprietary binary packages

1. Now, run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

2. Login to Scratchbox X86 target

$ /scratchbox/login

Welcome to Scratchbox, the cross-compilation toolkit!

Use 'sb-menu' to change your compilation target.

See /scratchbox/doc/ for documentation.

[sbox-FREMANTLE_X86: ~]>

3. Set the DISPLAY variable to match the display setting given for the Xephyr server.

[sbox-FREMANTLE_X86: ~] >export DISPLAY=:2

4. Start the UI framework .

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh start

5. You will now see the UI framework up and running on the Xephyr window.

6. You can shut down the UI framework as follows:

[sbox-FREMANTLE_X86: ~] >af-sb-init.sh stop

=Installation of x86-64 Debian based distributions=
Since Scratchbox only supports x86-32 bit Linux host systems, we need to force the installation of x86-32 Scratchbox packages on the x86-64 bit machines. Using the -F option with the Scratchbox installation script can do this.

==Installation procedure==

*Download the Scratchbox installer and the Maemo SDK installer scripts.

$ wget -c http://repository.maemo.org/stable/5.0/maemo-scratchbox-install_5.0.sh http://repository.maemo.org/stable/5.0/maemo-sdk-install_5.0.sh

*Set permissions to execute the scripts.

$ chmod a+x ./maemo-scratchbox-install_5.0.sh ./maemo-sdk-install_5.0.sh

*Run the Scratchbox installer script as 'root user' with -F option, specifying the username to be added to Scratchbox users group sbox group as follows:

$ sudo ./maemo-scratchbox-install_5.0.sh -F -u $USER

Upon successful installation of Scratchbox, continue to run the Maemo 5 Final SDK Installer as instructed in the x86-32 installation.

=Starting Scratchbox on non-Debian based systems=
If Scratchbox was installed from Debian packages, the /etc/init.d/scratchbox-core init script is installed and Scratchbox should start automatically when the system is rebooted. However, if you have installed Scratchbox from tarballs, then rebooting your machine will clear away all the mounts and binfmt_misc registrations that Scratchbox requires to work. To get your Scratchbox working again after reboot, you have to run the following command as root:

$ sudo /scratchbox/sbin/sbox_ctl start

Alternatively you can add sbox_ctl as an init script to the /etc/init.d directory and create the appropriate links at your system's runlevel directories. This procedure works on some systems:

$ ln -s /scratchbox/sbin/sbox_ctl /etc/init.d/scratchbox-core
$ /usr/sbin/update-rc.d scratchbox-core defaults

Refer to your system's documentation for the correct instructions.

=Upgrading from Maemo 5 Beta2 SDK=

A smooth upgrade from beta2 to Final SDK is unfortunately not possible. Hence it is advised to freshly install the Final SDK. Before you do so, read through the instructions below.

Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges. The -u option in the Scratchbox installer has been updated to create the necessary symlinks. Running the installer with -u option when the Scratchbox has been already installed will just add the user and create symlinks. Running it for already existing user will check for the symlink and create it if needed.

Run the command below to create the symlink for existing Scratchbox user:

$ sudo ./maemo-scratchbox-install_5.0.sh -u <EXISTING_USER>

Alternatively, you can create the symlinks manually as follows, if Scratchbox is installed in the default location:

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

The Final SDK installer additionally creates a directory /opt under /target/<target_name>/.
'''Reason:''' In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation, we have to manually check whether /targets/<target_name>/opt is a symlink and if it is, remove it and create a directory with the same name.

=Upgrading from Maemo 4.x/Diablo SDK=
Due to the fact that there are API breaks in Fremantle, we cannot upgrade Diablo SDK to Fremantle. We can however have Fremantle Scratchbox targets co-exist with Diablo targets.

For this, we need to first upgrade the Scratchbox installation on our host machine.

*Download the Maemo5 scratchbox installer.

*Set executable permissions and run it as follows:

$ chmod a+x ./maemo-scratchbox-install_5.0.sh
$ sudo ./maemo-scratchbox-install_5.0.sh -U -u <EXISTING_USER> -s /scratchbox

Once the Scratchbox installation is done, run the Maemo 5 Final SDK installer.

=Manual Installation=

'''On x86-32 Debian based systems:'''

*You can add the following line into your host machine's /etc/apt/sources.list file.

deb http://scratchbox.org/debian/ maemo5-sdk main

*Install the needed Scratchbox packages with root permission

$ sudo apt-get update
$ sudo apt-get install scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

'''On x86-64 Debian based systems:'''

*Download the Scratchbox packages from here.

*Force the installation of the x86-32 packages with root permission as follows:

$ sudo dpkg -i --force-architecture scratchbox-core scratchbox-libs scratchbox-devkit-qemu scratchbox-devkit-debian scratchbox-devkit-doctools scratchbox-devkit-perl scratchbox-toolchain-host-gcc scratchbox-toolchain-cs2007q3-glibc2.5-arm7 scratchbox-toolchain-cs2007q3-glibc2.5-i486 scratchbox-devkit-svn scratchbox-devkit-git scratchbox-devkit-apt-https

The Scratchbox packages will be unpacked to /scratchbox directory and the installation procedure will ask you some questions about the group and user accounts. Default group to Scratchbox is 'sbox'.

*Users who will be using Scratchbox should be added using the following command with root permission:

$ sudo /scratchbox/sbin/sbox_adduser USER yes

It will automatically include the user to the Scratchbox group, create user directories under /scratchbox/users and mount several directories (/dev, /proc, /tmp) under the user directory.

*Some of the Nokia applications shipped with the final SDK use a hard coded path for user home directory which presents a problem since the default username on the device differs from the username on the developer’s machine. To make these applications work, it is required to create a home directory that matches the hard coded value. This needs to be done outside scratchbox using root privileges.

$ sudo ln -s /scratchbox/users/<username>/home/<username> /scratchbox/users/<username>/home/user

*For the group membership to be effective in the current terminal session, run the following command:

$ newgrp sbox

'''Note:''' This command will change the existing group ID during the current login session to 'sbox'. If you do not want to change, simply logout and log back in for the group membership to be effective.

*Log-in to Scratchbox.

$ /scratchbox/login

*Configure the scratchbox x86 and armel targets as follows:

[sbox->:~]>sb-conf st FREMANTLE_X86 -c cs2007q3-glibc2.5-i486 -d perl:debian-etch:doctools:svn:git -t none
[sbox->:~]>sb-conf st FREMANTLE_ARMEL -c cs2007q3-glibc2.5-arm7 -d qemu:perl:debian-etch:doctools:svn:git -t qemu-arm-sb

*Download the minimal rootstraps.

[sbox->:~]> wget http://repository.maemo.org/stable/5.0/armel/maemo-sdk-rootstrap_5.0_armel.tgz http://repository.maemo.org/stable/5.0/i386/maemo-sdk-rootstrap_5.0_i386.tgz

*Switch to x86 target, install the devkits, etc and fakeroot into the target, install the minimal rootstrap and finally the Maemo development files.

[sbox->:~]> sb-conf se FREMANTLE_X86
[sbox-FREMANTLE_X86: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_i386.tgz
[sbox-FREMANTLE_X86: ~] > sb-conf in -edFL
[sbox-FREMANTLE_X86: ~] > apt-get update
[sbox-FREMANTLE_X86: ~] > fakeroot apt-get install maemo-sdk-debug

The meta-package 'maemo-sdk-debug' installs all needed open source runtime, development and debug pakcages into the target. Use maemo-sdk-runtime if you want only runtime packages to be installed or user maemo-sdk-dev if you want only the runtime + development packages to be installed.

*Accept the EULA from [http://tablets-dev.nokia.com/eula/index.php here] to obtain the URL to access the Nokia binaries repository.

*Add the URL thus obtained to the Scratchbox target's /etc/apt/sources.list and do the following:

[sbox-FREMANTLE_X86: ~] >apt-get update
[sbox-FREMANTLE_X86: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*In order to facilitate installing applications under /opt on the device, a symlink /opt has been created pointing to /home/opt. The SDK inherits this feature. Under Scratchbox, /opt points to /target/links/opt which in turn points to /targets/<target_name>/opt. Installing the rootstraps makes this point to /home/opt, which is not what we want, since we need /opt to be target specific. In order to resolve this situation,

[sbox-FREMANTLE_X86: ~] >rm /targets/FREMANTLE_X86/opt
[sbox-FREMANTLE_X86: ~] >mkdir /targets/FREMANTLE_X86/opt

*Execute similar steps on the armel target too to set it up:

[sbox-FREMANTLE_X86: ~]> sb-conf se FREMANTLE_ARMEL
[sbox-FREMANTLE_ARMEL: ~] > sb-conf rs maemo-sdk-rootstrap_5.0_armel.tgz
[sbox-FREMANTLE_ARMEL: ~] > sb-conf in -edFL
[sbox-FREMANTLE_ARMEL: ~] > apt-get update
[sbox-FREMANTLE_ARMEL: ~] > fakeroot apt-get install maemo-sdk-debug

*Add the same URL obtained above to access the Nokia binaries repository under /etc/apt/sources.list file of the Scratchbox armel target.

[sbox-FREMANTLE_ARMEL: ~] >apt-get update
[sbox-FREMANTLE_ARMEL: ~] >fakeroot apt-get install nokia-binaries nokia-apps

*Create the /opt directory.

[sbox-FREMANTLE_ARMEL: ~] >rm /targets/FREMANTLE_ARMEL/opt
[sbox-FREMANTLE_ARMEL: ~] >mkdir /targets/FREMANTLE_ARMEL/opt

With this, you must now have both the targets setup and ready to use.

[[#Starting/Shutting down the SDK UI|Start the UI framework]].

=Un-installation=

Make sure that you have no process running inside Scratchbox. Uninstalling Scratchbox will remove everything that is installed and saved inside Scratchbox. Please take a backup of your files from Scratchbox user home directory if needed.

On Debian based systems, do the following with root permissions:

$ sudo apt-get remove scratchbox-* --purge
$ sudo rm -rf /scratchbox

On non-Debian based systems, you need to stop scratchbox as follows before removing it.

$ sudo /scratchbox/sbin/sbox_ctl stop
$ sudo rm -rf /scratchbox

=Limitations of Scratchbox=

The following limitations have been noted in the usage of Scratchbox:

==VDSO support==
Scratchbox does not work when VDSO32 support is enabled in the host's kernel. We're working on making it possible, but at the moment there are some workarounds, which are presented here.

If your host has VDSO32 turned on you will get an error like this when trying to login to Scratchbox.

No directory, logging in with HOME=/
Inconsistency detected by ld.so: rtld.c: 1192: dl_main: Assertion `(void *)
ph->p_vaddr == _rtld_local._dl_sysinfo_dso' failed!

==x86-64 kernel==

x86-64 Linux kernels starting from version 2.6.25 enable VDSO32 by default. To temporarily disable VDSO32 execute

sysctl abi.vsyscall32=0

On Linux kernel 2.6.24 <= you can disable VDSO32 by executing

sysctl vm.vdso_enabled=0

or

sysctl kernel.vdso=0

The current setting of VDSO32 can be verified by using sysctl. Only values 0 and 2 are compatible with Scratchbox. In our examples we use 0 (disable). 2 enables compat mode.

You can set all of these permanently by adding the following lines to /etc/sysctl.conf

vm.vdso_enabled = 0
abi.vsyscall32 = 0
kernel.vdso = 0

Save the file and run the command:

$ sudo sysctl -p

Please note the correct line depends on your Linux kernel version. When you execute sysctl -p you may get a warning about unknown keys. You can safely ignore those warnings as long as one of the 3 settings works.

'''WARNING :''' You should try setting these values by echoing them to the given locations before adding them to sysctl.conf to see if they cause any problems. For example, in some Ubuntu Gutsy installations, it has been observed that changing the VDSO settings will hang the system and thus making permanent changes in sysctl.conf may, in these cases, make your system unbootable.

=Known Issues in the SDK=

*A list of issues and their solutions is http://wiki.maemo.org/Q%26A_-_SDK_and_Scratchbox

*Unnecessary warnings and debugging messages are printed out when the hildon application framework is started.

*Armel target does not bring up the UI framework

*It has been noted that Xephyr dies with the application framework at times. The crash in question might even be Xephyr related since the application framework behaves differently with different versions/builds of Xephyr. The case seems to be worst on Xephyr that comes with Ubuntu Jaunty, there Xephyr will die when running any application that contains an input field and clicking on that field with a mouse to invoke the input method. On Fedora Code 10 the Xephyr does not mind the mouse clicks but dies when shutting down the application framework. On the other hand Xephyr on Ubuntu Intrepid or even the Intrepid version recompiled for Jaunty does not experience crashing in these situations.

A patch is already available for the Xephyr on Ubuntu Jaunty and can be found at http://bugs.freedesktop.org/show_bug.cgi?id=21591. Binaries packages for [http://launchpadlibrarian.net/30330126/xserver-xephyr_1.6.3-1ubuntu2_i386.deb xserver-xephyr] package and its dependencies ([http://launchpadlibrarian.net/27533744/libgpg-error0_1.6-1ubuntu1_i386.deb libgpg-error0] and [http://launchpadlibrarian.net/28623981/libgcrypt11_1.4.4-2ubuntu2_i386.deb libcrypt11]) can be download from Ubuntu Jaunty repositories.

*The performance of clutter can be improved by enabling hardware acceleration if not enabled already. In some cases, it would require installing restricted/proprietary drivers (Eg: on host machines with ATI or NVidia graphics card). Refer to [[Maemo5 clutter performance]] for more details.

*Running Xephyr with -kb option disables entry of “@” symbol. However, removing -kb option disables cursor keys.

*Colours invert sometimes in some applications. (Browser and Photo's for example)

[[Category:Scratchbox]]

Maemo-Barcelona Long Weekend/UX meets Code

2009-12-02T07:18:14Z

192.100.124.218: /* Participants */

This wiki page is complemented by [http://talk.maemo.org/showthread.php?p=393329 this discussion thread]

About 50 community developers and user experience professionals work together during 3 days.

=== 3 goals ===

* Improve the usability and visual appeal of great Maemo apps.
* Improve the UX documentation for Maemo developers.
* Get a critical mass of people interested in pushing forward UX meets Code activities online and face to face.

=== Way of working ===

All the activity happens in a big room (official capacity for 70 people).

The group activity on a project can happen in one side and you can be doing your own thing on the other side if you prefer. Free flow!

You should be able to find some time during the day to get some opinions and help from one of the experts about specific details of your project.

Every day has a similar flexible structure:
* 9:00 - Starting with a briefing about the topic: presentation + Q&A.
* 11:00 - About 2h discussion and collaboration on a real project.
* 13:00 - Lunch
* 14:00 - 2nd real project.
* 16:00 - Everybody: hard work. Other projects feel free to share your plans and problems
* 18:00 - Recap
* 18:30-ish - Enjoy the city!

===Projects===

6 projects have been selected to get get special attention during the Long Weekend. The group will do its best to have a Before and After for them. Participants in the hackfest can join the discussion/work of a specific project or can you their time to work on their own projects.

{|width=100%
!width=10%|
!width=30% align=center style="background-color:#efe;"|Friday concepting
!width=30% align=center style="background-color:#fee;"|Saturday interaction
!width=30% align=center style="background-color:#eef;"|Sunday graphics
|-
|align=right style="padding:10px;"|11:00-12:00
|style="padding:10px;background-color:#efe;"|[http://www.youtube.com/watch?v=9rEZxWjVvGo liqbase Calendar]
|style="padding:10px;background-color:#fee;"|[[Maemo-Barcelona_Long_Weekend/UX_meets_Code/MaemoMapper|Mapper]]
|style="padding:10px;background-color:#eef;"|[http://maemo.org/downloads/product/Maemo5/gpodder/ gPodder]
|-
|align=right style="padding:10px;"|14:00-16:00
|style="padding:10px;background-color:#efe;"|Video editor
|style="padding:10px;background-color:#fee;"|[http://maemo.org/downloads/product/Maemo5/xournal/ Xournal]
|style="padding:10px;background-color:#eef;"|MaStory
|}

List here other projects with developers participants in the hackfest. Please provide links to the project and your thought on what would you like to improve and what do you plan to achieve during the whole weekend. Add your names!

* [http://maemo.org/downloads/product/Maemo5/fmradio/ FM Radio] - Martin Grimme - general UI overhaul for a better user experience
* [http://maemo.org/downloads/product/Maemo5/conboy/ Conboy] - Cornelius Hald - Fixing settings UI / Polishing synchronization work flow and dialogs / Making control file translatable / Getting ideas for next version
* [http://maemo.org/downloads/product/OS2008/diskusage/ DiskUsage], [http://maemo.org/downloads/product/OS2008/kandis/ Kandis], [http://maemo.org/downloads/product/OS2008/PackageView/ PackageView], [http://maemo.org/downloads/product/OS2008/weightjinni/ WeightJinni], [http://maemo.org/downloads/product/OS2008/wifiinfo/ WifiInfo], [http://maemo.org/downloads/product/OS2008/mathjinni/ MathJinni], [http://maemo.org/downloads/product/OS2008/dicejinni/ DiceJinni], [http://maemo.org/downloads/product/OS2008/findmine/ FindMine], [http://maemo.org/downloads/product/OS2008/pushit/ PushIt], [http://maemo.org/downloads/product/OS2008/givemefive/ GiveMeFive], [http://maemo.org/downloads/product/OS2008/gpsjinni/ GPSJinni] - Tim Teulings - Usage of tables with table headers and multiple columns vs. one table column with complex layout (general), general usability improvements (MathJinni, WeightJinni, DiceJinni, Kandis, GPSJinni) replacement suggestions for tree view (MathJinni), thumbable gaming interaction (FindMine, PushIt, GiveMeFive) and technical support for Gtk/hildon theming alignment and Qt know how (general) - all applications also available in maemo5 extras-devel!

=== Participants ===
Please add your names and a link to your maemo.org profile. Please edit your profile adding all the relevant info about you and links to your website, blog, etc.

* [http://maemo.org/profile/view/martin/ Martin Schuele] - Principal UI designer for N900
* [http://maemo.org/profile/view/msoini/ Mox Soini] - Interaction Designer, Concepting, Maemo-as-platform
* Steffen Halme - Graphic Designer specializing in icons
* [http://personal.inet.fi/koti/mgimpl/ Martin Gimpl] - Graphic Designer, Concepting, Transitions, Graphics
* [http://maemo.org/profile/view/asimula/ Adele Simula] - UX Graphic Designer, Concepting, Layout Design, Graphics
* Sanna Nordling - Interaction designer, Concepting, Application UX design
* [http://maemo.org/profile/view/jmaaniit/ Jussi Maaniitty] - UX Management, Concepting
* Juha Vartiainen - Interaction Design, Concepting, Application UI design
* Jaakko Viitanen - Interaction Design, Concepting, Application UI design
* [http://blogs.forum.nokia.com/blog/arabella-davids-forum-nokia-blog Arabella David], Design & User Experience Program Manager @ Forum Nokia
* Sanna Häivalainen, UX Specialist @ Forum Nokia
* [http://maemo.org/profile/view/tigert/ Tuomas Kuosmanen] - Senior Designer @ Nokia
* [http://maemo.org/profile/view/patifa/ Patricia Montenegro] - Lead User Experience Designer @ INdT
* [http://maemo.org/profile/view/allsomm/ Alysson Santos] - Senior Designer @ INdT - interested in the video editor
* Annu-Maaria Nivala
* Jan Krebber
* Kirsi Rönkkö
* Ulla Niemelä

===Help with specific technologies===

====Developers willing to help====
Please list technologies you are using and working with here. This makes it easier for other people to quickly find a person to ask specific technical questions.

* Thomas Perl: PyMaemo, GTK+, Hildon, PyGTK, Python
* [http://maemo.org/profile/view/andy80/ Andrea Grandi]: Pymaemo, Python, UI design concepts
* [http://maemo.org/profile/view/anidel/ Aniello Del Sorbo]: GTK, C, Debian packaging. Not an expert.
* Jesus Sanchez-Palencia: Qt 4.6, libqt4-maemo5 (Qt 4.6 for Maemo5)
* Zaheer Abbas Merali: GStreamer, Python, PyGTK
* [http://maemo.org/profile/view/vdvsx/ Valério Valério]: Python, C/C++, EFL, PyGTK, Qt (not an expert).
* [http://maemo.org/profile/view/mardy/ Alberto Mardegan]: GTK, Hildon, C/C++, Qt, Clutter (just basics).
* [http://maemo.org/profile/view/marcoil/ Marc Ordinas i Llopis]: C, Gtk+, Hildon, Hildon-desktop.
* [http://maemo.org/profile/view/pycage/ Martin Grimme]: PyMaemo, GDK, UPnP with Python, V4L2 in Python, controlling N800 & N900 FM receivers, D-Bus services with GObject (C)
* [http://maemo.org/profile/view/mikhas/ Michael Hasselmann]: Qt 4.6 for Maemo5 (novice), autotroll
* [http://maemo.org/profile/view/bilboed/ Edward Hervey]: Video Editing, GStreamer, PiTiVi, GStreamer Editing Services, GNonLin
* [http://maemo.org/profile/view/conny/ Cornelius Hald]: C, Gtk+, Hildon, Eclipse, transifex.net, hildon-extras
* ''<Your name here>: <Your technologies here>''

====How to get help====

# Look up developers who work with the technology you need help with in the list above
# Approach the developers and ask them for help/advice :)
# In the neighbor room there will be [[Maemo-Barcelona_Long_Weekend/Formaci%C3%B3n|a developer
training track]]. Feel free jumping there to ask questions, too!

=== Interested? ===

If you want to be invited please provide in [http://talk.maemo.org/showthread.php?t=33719 this thread]:

* Your [http://maemo.org/profile/list/ maemo.org profile] making sure that there one can find info about or links to your current projects and your interests in Code or UX.
* If you are more into Code, a link to the app hosted in maemo.org, either under [http://maemo.org/packages/ Fremantle packages] or [http://maemo.org/downloads/OS2008/ OS2008 Downloads].
* If you are more into UX, a link to wherever your work can be seen.

Forward this to your colleagues working on great stuff!

For budgeting and also practical purposes we will keep the number of participants around 50 people even if we get more requests. The criteria will be defined more or less by fast response, travel costs, community involvement and of course Maemo excellence in Code or UX.

Documentation/Maemo 5 Developer Guide/Development Environment/Maemo SDK

2009-11-16T11:28:59Z

192.100.124.218: /* Starting Virtual X Server (Xephyr) */

= Maemo SDK =

The following code examples are used in this chapter:

* [https://garage.maemo.org/svn/maemoexamples/trunk/support-libraries/helloworld.c helloworld.c]
* [https://garage.maemo.org/svn/maemoexamples/trunk/support-libraries/gtk_helloworld-1.c gtk_helloworld-1.c]

The development environment for Maemo running on the desktop is called '''Maemo SDK'''. You can only install Maemo SDK on a Linux operating system. Maemo SDK currently supports the following Linux distributions:
*Debian
*Ubuntu

However, you can also install Maemo SDK on other Linux distributions.

= Maemo Software Development Kit =

The Maemo SDK creates a sandboxed Maemo development environment on a GNU/Linux desktop system largely built on a tool called [http://scratchbox.org/ Scratchbox]. In most ways, this environment behaves like the operating system on the device, but with added development tools. This means that the development process is very similar to a normal desktop GNU/Linux, and the kinks of embedded development, such as cross-compiling, are handled transparently by Scratchbox.

==Hardware architectures==

Maemo SDK supports two architectures, ''X86'' and ''ARMEL'' and provides development environment for both. In Fremantle, ''X86'' environment is used for active development and has better tool support through native execution without the need for emulation. ''' ''ARMEL'' ''target'' is used only for cross-compilation of applications to work on the actual device'''. There are currently issues with the user mode qemu which prevent the UI framework from starting up in the ''ARMEL'' target which prevents running applications on this target.

When your application compiles, runs and behaves as expected on the ''X86'' ''target'', the next step is to compile it on the ''ARMEL'' ''target''. The process of compilation and packaging is exactly the same as in ''X86'', albeit a bit slower, because some of the required software is emulated. Scratchbox will handle cross-compilation, so the developers need not concern themselves with cross-compilation.

The applications thus compiled on the ''ARMEL'' target can be run directly on the device without further modifications. This is possible because of the emulation provided by the Maemo SDK. The emulation however is not complete, so the actual testing must be performed on the device. 

==Scratchbox==
Scratchbox is a specially packaged "sandbox" environment, providing the necessary tools and isolating the development efforts from the actual Linux system. Scratchbox also makes cross-compiling easy to perform: the software is built into a binary format that is executable on the target device.

The name "Scratchbox" comes from "Linux from scratch" + "chroot jail" (sandbox). This also explains its implementation and intended use. While working inside Scratchbox, programs will be running in a changed root environment (chroot). In Linux systems, it is possible to change the file paths that a process will see. Scratchbox uses this mechanism on startup to switch its root directory (/) to something other than the real root. This is part of the isolation technique used. Because of this, the environment is called a sandbox, a private area where it is possible to play around without disturbing the environment, and without all the mess that real sand would cause. The other parts of the isolation technique are library call diversions (using LD_PRELOAD), wrapping of compiler executables and other commands.

Scratchbox:

* Is a software package to implement development sandboxes (for isolation)
* Contains easy-to-use tools to assist cross-compilation
* Supports multiple developers using the same development system
* Supports multiple configurations for each developer
* Supports executing target executables on the hardware target, via a mechanism called sbrsh
* Supports running non-native binaries on the host system via instruction set emulators ([http://bellard.org/qemu Qemu] is used).

Besides these main features, it is possible to develop your own software packages that can be installed and used inside a Scratchbox environment. Scratchbox also includes some integration of Debian package management, so that once the source files are set up correctly and a couple of configuration files have been written, binary distribution packages can be created for various architectures (similar to .msi files in Windows, or .rpm files in Fedora Core, RHEL and SUSE). These tools are also used to provide the environment with a packaging database so that other development packages can be installed over the Internet when needed (by using standard Debian package management tools).

Fremantle also uses a similar packaging system, and this means that packages built using Scratchbox and the SDK can be installed on the real device.

Scratchbox is licensed under the GPL and it is open for outside contributions. For in-depth coverage on Scratchbox and its capabilities, please visit the [http://scratchbox.org project website].

This material discusses only the Scratchbox capabilities that are necessary to use the Maemo SDK.

===Scratchbox In-Depth===

Scratchbox is Maemo SDK's cross-compiling environment. The default Scratchbox installation works as-is under most conditions, but some details are good to know for more specialized usage.

The ''target'' inside Scratchbox contains a root file system. When you create a new target inside Scratchbox, specify the ''toolchain'' you will use to build applications. Examples of a ''target'' include X86 and ARMEL, provided by Maemo SDK on top of Scratchbox.

''Host tools'' are native to the host, provided for convenience and speed. They are always transparently preferred over target tools. For example, cross-compiling applications to the target architecture. Host tools consist of devkits and ''toolchains''.

A toolchain provides the minimal set of tools for compiling binaries for the target. Each scratchbox target must have one and only one toolchain selected.

''CPU transparency methods'' take care of running the applications on an emulator, target device or directly on the host transparently from the user's perspective. The available CPU transparency methods come from a special ''devkit'' called ''cputransp''. For each of Maemo SDK's pre-defined targets, a CPU transparency method is selected and defined.

A ''toolchain'' is a collection of tools used to produce binaries for the target environment. In addition to a compiler (''gcc''), the toolchain contains a linker (''ld'') and other ''binutils'', such as ''strip'', ''objdump'' and ''strings''.

A ''devkit'' is a collection of tools native to the host. A devkit can be selected or disabled for a target. An example of a devkit is the doctools devkit, which provides tools (like doxygen) for building documentation.

A ''rootstrap'' is a root file system for the target device. Maemo SDK provides root file systems for both targets (X86 and ARMEL) inside Scratchbox. Note that the user's home directory is shared for all targets. The ''/tmp'' directory is shared for all targets and also with the host.

From Scratchbox's point of view, Maemo SDK is a set of preconfigured ''targets'' and ''root file system''s. One set is provided for both ''X86'' and ''ARMEL'' architectures on top of a working Scratchbox installation.

==Development on Maemo SDK==
The Maemo SDK provides all of its development tools inside Scratchbox. Also the UI framework is started with a single command, ''af-sb-init'', run within Scratchbox. However, it needs a secondary X server of proper size and bit-depth to be displayed on.

As an exception to the rule, you must start the Xserver, such as [http://www.freedesktop.org/wiki/Software/Xephyr Xephyr] on the host Linux environment, not inside Scratchbox.

===Scratchbox Development Tools===
As the Scratchbox environment is practically a full GNU/Linux system, it includes the standard GNU/Linux development tools. Debugging is performed with tools like ''[http://sourceware.org/gdb/ gdb]'', ''[http://valgrind.org/ valgrind]'', ''ltrace'' and ''[http://sourceforge.net/projects/strace/ strace]''. Performance profiling can be performed with tools like ''[http://htop.sourceforge.net/ htop]'', ''[http://oprofile.sourceforge.net/ oprofile]'' and ''time''. Compiling is done with the GCC toolchain. Some of these tools offer graphical user interfaces, which can also be used. Naturally, this is not a comprehensive list of the tools, and if the tools shipped with the SDK do not suit your needs or personal preferences, most utilities can be easily run practically unchanged in Scratchbox.

===Other Programming Languages===
Currently C is the only official programming language for Maemo. But thanks to the community, Python scripting language also has a good support in the form of [http://pymaemo.garage.maemo.org/ pymaemo].

= Installing SDK =

Before continuing, review the [http://wiki.maemo.org/Documentation/Maemo5_Final_Installation installation instructions] of the Maemo SDK.

The kernel must support binfmt_misc-feature in order for the instruction emulator in Scratchbox to work properly. Because it is usually built as a module, verify that the module is loaded in Linux (no root access needed):

user@system:~$ lsmod | grep binfmt
binfmt_misc 12936 0

If you do not see a line of output, try to execute ''modprobe binfmt_misc'' as root (or with sudo). If this still does not work, either locate the module elsewhere, or recompile the kernel. Most Debian-based systems (Debian, Ubuntu) include the module, unless you have built your own kernel, you should encounter no problems. The feature may also be directly built inside the kernel instead of being a module.

Install a pseudo X server to act as an X client to the real system in order to run application developed after installing the SDK. You have a certain amount of freedom to choose the most suitable option to achieve this, but this material assumes that you are using Xephyr, a Kdrive-based X server/client that can emulate 16-color depth for its clients even while acting as a client to an 24-bit depth real X server. Xephyr also implements modern X protocol extensions.

The concept of having a program that is both X server and a client may seem weird, but it is a tested technology and works quite well.

To install Xephyr on a Debian-based Linux:

* Issue the command sudo apt-get install xserver-xephyr on your real Linux system.
* Verify installation status by issuing the command 'dpkg -l | grep xephyr' (as non-root).

As mentioned before, Maemo SDK uses Scratchbox as the cross-compilation environment. Therefore, you must install Scratchbox first before attempting to install the SDK. The preferred way to install scratchbox and SDK is to use the automated installation scripts though manual installation steps are also provided. Detailed instructions are found [http://maemo.org/development/sdks/maemo_5_beta_2_sdk_installation/ here].

= Testing SDK Installation =

== Testing Scratchbox ==
The following shows how to create a small non-graphical Hello World program to verify that the Scratchbox environment works: helloworld.c

<tt>''/**''
'' * helloworld.c''
'' *''
'' * This maemo code example is licensed under a MIT-style license,''
'' * that can be found in the file called "License" in the same''
'' * directory as this file.''
'' * Copyright (c) 2007-2008 Nokia Corporation. All rights reserved.''
'' *''
'' * Simple standard I/O (printf)-based Hello World that we can use to''
'' * test our toolchains.''
'' */''

'''<nowiki>#include</nowiki>''' <stdio.h> ''/* printf */''

''/* main implementation */''
int '''main'''(int argc, char<nowiki>**</nowiki> argv) {

'''printf'''("Hello world\n");

''/* In Linux, each process upon termination must set its exit code.''
'' Exit code 0 means success to whoever executed this program. It''
'' is routinely used inside scripts to test whether running some''
'' program succeeded or not. Other exit codes mean failure. Each''
'' program is free to use different non-zero codes to signify''
'' different kinds of failures. These are normally listed in the''
'' manual page for the program (since there is no standard). If you''
'' forget to set your exit code, it will be undefined. */''
'''return''' 0<nowiki>;</nowiki>
}</tt>

First, verify that the proper directory is chosen by using pwd (print working directory). At this point, the work directory should be your home directory:

[sbox-FREMANTLE_X86: ~] > pwd
/home/user

Then, start an editor and write a small hello world program (you may use the above code listing as a template if you wish):

[sbox-FREMANTLE_X86: ~] > nano helloworld.c

It is also possible to use vi (Visual Interactive) editor inside Scratchbox. You can install your own favourite editor inside sbox (with the debian-devkit), but the following examples will use nano, because it is the easiest to start with. If you want to learn vi, your best course of action is searching for "vi tutorial" with your favourite search engine. There are lots of them to be found. To understand why vi can be considered "strange", it is useful to know its history first. Using vi is fully optional.

[sbox-FREMANTLE_X86: ~] > gcc -Wall -g helloworld.c -o helloworld
[sbox-FREMANTLE_X86: ~] > ls -F hello*
helloworld* helloworld.c

GCC's -g option tells the compiler to add debugging symbols to the generated output file. -Wall will tell the compiler to enable most of the syntax and other warnings that the source code could trigger. -o helloworld tells gcc to output the resulting binary with the filename of helloworld.

The -F option to ls is mainly useful when working with a non-color terminal (for example paper) to indicate the type of different files. The asterisk after helloworld signifies that the file is executable. 

[sbox-FREMANTLE_X86: ~] > ./helloworld
Hello world

Running the binary should not produce any surprises.

[sbox-FREMANTLE_X86: ~] > file helloworld
helloworld: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.6.0, dynamically linked (uses shared libs), not stripped

The file tool is a generic utility that loads some bytes from the start of the given file and then uses its internal database to decode what type of file it is. In this case, it will correctly decode the file as a X86 format binary file.

[sbox-FREMANTLE_X86: ~] > ldd helloworld
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/libc.so.6 (0xb7e9f000)
/lib/ld-linux.so.2 (0xb7fd2000)
[sbox-FREMANTLE_X86: ~] > ls -l /lib/libc.so.6
lrwxrwxrwx 1 user user 11 Nov 12 15:52 /lib/libc.so.6 -> libc-2.5.so
[sbox-FREMANTLE_X86: ~] > ls -l /lib/libc-2.5.so
-rwxr-xr-x 1 user user 1213256 Sep 7 13:28 /lib/libc-2.5.so

On the left are the names of dynamic libraries that the executable uses, and on the right are the files where the libraries reside on the system when executing the program. Next use ls to check the exact version of the C library that the SDK uses with the "long listing format" -l option. Running these commands using the ARMEL target yields more or less the same results.
N.B. The linux-gate.so.1 is a so-called hack to support a certain way of doing system calls on the X86 architecture, and is not always present on newer systems.

When comparing the version of libc used on the real system with ls -l, it will probably show a difference (in version numbers). This means that the executables that were built inside Scratchbox use libraries that are also inside Scratchbox. This also means we have a stable development platform, which is very important, especially when working on a team where each member has their own Linux installation which they may or may not have customized. This might not seem very important at this stage, but when encountering all the different tools that are used in free software development, this feature of Scratchbox will come in handy.

Scratchbox does not contain any logic to emulate the kernel (or to use a different kernel for running programs inside Scratchbox). The only easy possibility for this is using the sbrsh CPU-transparency option.

===vi===
You can also use vi (Visual Interactive) editor inside sbox. You can install your own favorite editor inside Scratchbox (with the debian-devkit), but the following examples will use nano, since it is the easiest to start with. If you want to learn vi, search for "vi tutorial" with your favorite search engine. There are lots of them to be found. To understand why vi can be considered "strange", it is useful to know its history first. Using vi is fully optional. It is common for people who are new to vi to get stuck in it; if you find yourself in this situation, a way to exit (without writing the file) is to press type <escape>:qall!<enter>.

The vi that is commonly installed on Linux systems is really vim (VI iMproved), which is a more user-friendly version of vi, including syntax high-lighting and all kinds of improvements. sbox has a program called vimtutor installed to help you learn how to use vi interactively.

It is also fairly simple to use existing editors. /scratchbox/users/x/home/x/ is the home directory of user x when accessing it from the real Linux desktop. Ubuntu comes with Gedit, which is a fairly good graphical editor that also supports syntax highlighting and multiple tabs for editing multiple files at the same time.

And as a final note, emacs can also be used.

Here is how to do use it:

* Start emacs outside of Scratchbox
* In emacs, use M-x server-start
* Inside Scratchbox, use the emacsclient filename to open the file for editing in your emacs

==Writing GUI Hello World==
The following example shows how to write the first GUI program. Note that the example only uses the GTK+ library and does not utilise the widgets and coding style provided by the platform. That will be discussed later.

gtk_helloworld-1.c

<tt>''/**''
'' * gtk_helloworld-1.c''
'' *''
'' * This maemo code example is licensed under a MIT-style license,''
'' * that can be found in the file called "License" in the same''
'' * directory as this file.''
'' * Copyright (c) 2007-2008 Nokia Corporation. All rights reserved.''
'' *''
'' * A simple GTK+ Hello World. You need to use Ctrl+C to terminate''
'' * this program since it doesn't implement GTK+ signals (yet).''
'' */''

'''<nowiki>#include</nowiki>''' <stdlib.h> ''/* EXIT_* */''
''/* Introduce types and prototypes of GTK+ for the compiler. */''
'''<nowiki>#include</nowiki>''' <gtk/gtk.h>

int '''main'''(int argc, char<nowiki>**</nowiki> argv) {

''/* We'll have two references to two GTK+ widgets. */''
GtkWindow<nowiki>*</nowiki> window<nowiki>;</nowiki>
GtkLabel<nowiki>*</nowiki> label<nowiki>;</nowiki>

''/* Initialize the GTK+ library. */''
'''gtk_init'''(&argc, &argv);

''/* Create a window with window border width of 12 pixels and a''
'' title text. */''
window <nowiki>=</nowiki> '''g_object_new'''(GTK_TYPE_WINDOW,
"border-width", 12,
"title", "Hello GTK+",
NULL);

''/* Create the label widget. */''
label <nowiki>=</nowiki> '''g_object_new'''(GTK_TYPE_LABEL,
"label", "Hello World!",
NULL);

''/* Pack the label into the window layout. */''
'''gtk_container_add'''('''GTK_CONTAINER'''(window), '''GTK_WIDGET'''(label));

''/* Show all widgets that are contained by the window. */''
'''gtk_widget_show_all'''('''GTK_WIDGET'''(window));

''/* Start the main event loop. */''
'''g_print'''("main: calling gtk_main\n");
'''gtk_main'''();

''/* Display a message to the standard output and exit. */''
'''g_print'''("main: returned from gtk_main and exiting with success\n");

''/* The C standard defines this condition as EXIT_SUCCESS, and this''
'' symbolic macro is defined in stdlib.h (which GTK+ will pull in''
'' in-directly). There is also a counter-part for failures:''
'' EXIT_FAILURE. */''
'''return''' EXIT_SUCCESS<nowiki>;</nowiki>
}</tt>

Build your program:

[sbox-FREMANTLE_X86: ~] > gcc -Wall -g gtk_helloworld-1.c -o gtk_helloworld-1
gtk_helloworld-1.c:15:21: gtk/gtk.h: No such file or directory
gtk_helloworld-1.c: In function `main':
gtk_helloworld-1.c:20: error: `GtkWindow' undeclared (first use in this function)
gtk_helloworld-1.c:20: error: (Each undeclared identifier is reported only once
gtk_helloworld-1.c:20: error: for each function it appears in.)
gtk_helloworld-1.c:20: error: `window' undeclared (first use in this function)
gtk_helloworld-1.c:21: error: `GtkLabel' undeclared (first use in this function)
gtk_helloworld-1.c:21: error: `label' undeclared (first use in this function)
gtk_helloworld-1.c:24: warning: implicit declaration of function `gtk_init'
gtk_helloworld-1.c:28: warning: implicit declaration of function `g_object_new'
gtk_helloworld-1.c:28: error: `GTK_TYPE_WINDOW' undeclared (first use in this function)
gtk_helloworld-1.c:34: error: `GTK_TYPE_LABEL' undeclared (first use in this function)
gtk_helloworld-1.c:39: warning: implicit declaration of function `gtk_container_add'
gtk_helloworld-1.c:39: warning: implicit declaration of function `GTK_CONTAINER'
gtk_helloworld-1.c:39: warning: implicit declaration of function `GTK_WIDGET'
gtk_helloworld-1.c:42: warning: implicit declaration of function `gtk_widget_show_all'
gtk_helloworld-1.c:45: warning: implicit declaration of function `g_print'
gtk_helloworld-1.c:46: warning: implicit declaration of function `gtk_main'

This does not look at all promising. The source code started with #include, and you need to tell the compiler where to look for that critical GTK+ header file. The compiler probably also needs some special flags to be able to use the correct compilation settings for building GTK+ software.

To help you decide which flags to use we provide a tool called pkg-config, which is a simple program that provides a unified interface to output compiler, linker flags and library version numbers. Use pkg-config manually for the time being.

[sbox-FREMANTLE_X86: ~] > pkg-config --list-all | sort
.. listing cut to include only relevant libraries ..
dbus-glib-1 dbus-glib - GLib integration for the free desktop message bus
gconf-2.0 gconf - GNOME Config System.
gdk-2.0 GDK - GIMP Drawing Kit (x11 target)
gdk-pixbuf-2.0 GdkPixbuf - Image loading and scaling
glib-2.0 GLib - C Utility Library
gnome-vfs-2.0 gnome-vfs - The GNOME virtual file-system libraries
gtk+-2.0 GTK+ - GIMP Tool Kit (x11 target)
hildon-1 hildon - Hildon widgets library
hildon-fm-2 hildon-fm - Hildon file management widgets
pango Pango - Internationalized text handling
x11 X11 - X Library

pkg-config also has some other useful commands:

[sbox-FREMANTLE_X86: ~] > pkg-config --modversion gtk+-2.0
2.10.12

[sbox-FREMANTLE_X86: ~] > pkg-config --cflags gtk+-2.0
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/freetype2
-I/usr/include/libpng12

In this version of GTK+, all these commands are -I options that tell the compiler which additional directories to check for system header files in addition to the default ones.

[sbox-FREMANTLE_X86: ~] > pkg-config --libs gtk+-2.0
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm
-lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2
-ldl -lglib-2.0

When linking the application, the linker has to be told which libraries to link against. In fact, the whole program linking phase will fail (as shown below) without this information.

Now compile the software again, and this time use the compilation flags that pkg-config provides:

<nowiki>
[sbox-FREMANTLE_X86: ~] > gcc -Wall -g gtk_helloworld-1.c \
`pkg-config --cflags gtk+-2.0` -o gtk_helloworld-1
/var/tmp/ccQ14x4c.o: In function `main':/home/user/gtk_helloworld-1.c:24:
undefined reference to `gtk_init'
:/home/user/gtk_helloworld-1.c:28: undefined reference to `gtk_window_get_type'
:/home/user/gtk_helloworld-1.c:28: undefined reference to `g_object_new'
:/home/user/gtk_helloworld-1.c:34: undefined reference to `gtk_label_get_type'
:/home/user/gtk_helloworld-1.c:34: undefined reference to `g_object_new'
:/home/user/gtk_helloworld-1.c:39: undefined reference to `gtk_widget_get_type'
:/home/user/gtk_helloworld-1.c:39: undefined reference to `g_type_check_instance_cast'
:/home/user/gtk_helloworld-1.c:39: undefined reference to `gtk_container_get_type'
:/home/user/gtk_helloworld-1.c:39: undefined reference to `g_type_check_instance_cast'
:/home/user/gtk_helloworld-1.c:39: undefined reference to `gtk_container_add'
:/home/user/gtk_helloworld-1.c:42: undefined reference to `gtk_widget_get_type'
:/home/user/gtk_helloworld-1.c:42: undefined reference to `g_type_check_instance_cast'
:/home/user/gtk_helloworld-1.c:42: undefined reference to `gtk_widget_show_all'
:/home/user/gtk_helloworld-1.c:45: undefined reference to `g_print'
:/home/user/gtk_helloworld-1.c:46: undefined reference to `gtk_main'
:/home/user/gtk_helloworld-1.c:49: undefined reference to `g_print'
collect2: ld returned 1 exit status
</nowiki>

The command above may be new to you, if you have not used UNIX command shells. This is a backtick expansion, an operation where the shell starts another shell only to execute the text inside the backticks. In this case, start another shell to run ''`pkg-config --cflags gtk+-2.0`''. Normal output from the commands is then read into the main shell and the output is replaced into the location where the backticks were.
N.B. Use the backtick character (`) or falling accent. Do not use a rising accent (´) or a single quote or apostrophe ('). In some keyboard layouts, you can get the backtick character to appear by pressing first the backtic and then the space bar.

An alternative operation is $(pkg-config ..), which corresponds to the backtick but is less portable across antique UNIX shells. Choosing between these is a matter of taste.

GCC prints very different errors this time. These errors come from ld, which is the binary code linker in Linux systems and complains about missing symbols (the undefined references). Obviously something is still missing.

You must tell the linker where to find the missing symbols. Because this is the linker and not the compiler that we are talking aobut, the missing symbols are in the library files.

To fix the problem (again using backticks), pkg-config libs can be used:

[sbox-FREMANTLE_X86: ~] > gcc -Wall -g gtk_helloworld-1.c \
`pkg-config --cflags gtk+-2.0` -o gtk_helloworld-1 \
`pkg-config --libs gtk+-2.0`
[sbox-FREMANTLE_X86: ~] >

The order and placement of the pkg-config commands above is important: you must place the cflags as early as feasible and ensure that the libs must come last (this does matter in some problematic linking scenarios).

The next step is to repeat the basic commands that you used before with the non-GUI hello world:

[sbox-FREMANTLE_X86: ~] > ls -l gtk_helloworld-1
-rwxrwxr-x 1 user user 16278 Nov 20 00:22 gtk_helloworld-1
[sbox-FREMANTLE_X86: ~] > file gtk_helloworld-1
gtk_helloworld-1: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.6.0, dynamically linked (uses shared libs), not stripped
[sbox-FREMANTLE_X86: ~] > ldd gtk_helloworld-1
linux-gate.so.1 => (0xffffe000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb7c4c000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb7bc8000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb7bad000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xb7b97000)
libm.so.6 => /lib/libm.so.6 (0xb7b71000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xb7b68000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb7b2b000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb7ab5000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb7a7a000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb7a76000)
libdl.so.2 => /lib/libdl.so.2 (0xb7a71000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb79dd000)
libc.so.6 => /lib/libc.so.6 (0xb78b2000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb77bd000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb77b8000)
libXtst.so.6 => /usr/lib/libXtst.so.6 (0xb77b3000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb7788000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb777a000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7771000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb7769000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb7762000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb7759000)
/lib/ld-linux.so.2 (0xb7fc3000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb772b000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb76c6000)
libz.so.1 => /usr/lib/libz.so.1 (0xb76b7000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb7692000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb768f000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7689000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb7669000)

As you can see from the last ldd listing, this simple Hello World requires several other libraries to run. The program itself only requires GTK+, but GTK+ needs GDK and all the other libraries that were covered in the introduction. Those libraries in turn need other libraries and so on.

This is almost the full list of all required libraries to run. Modern UNIX systems (and Linux) can also load other libraries on demand (called runtime dynamic module loading).

Perhaps you are wondering why writing a simple Hello World is so demanding. It is actually much simpler in real life. This chapter simply introduces and solves various problems that you may encounter in actual situations.

You need all of these tools later on when starting the packaging of the software.

== Running GUI Hello World ==
Let's try to execute Hello World inside Scratchbox:

[sbox-FREMANTLE_X86: ~] > ./gtk_helloworld-1
gtk_helloworld-1[4759]: GLIB WARNING ** Gtk - cannot open display:
[sbox-FREMANTLE_X86: ~] > echo $DISPLAY

GTK+ seems unable to open connection to the X server. To verify this, display the contents of the DISPLAY environmental variable; indeed, the variable is empty. If the DISPLAY variable contains :0.0, the value originates in the graphical session and was copied into Scratchbox. Clients try to connect to the real X server and probably fail during authentication.

== Starting Virtual X Server (Xephyr) ==
Run Xephyr outside the scratchbox environment:

$ Xephyr :2 -host-cursor -screen 800x480x16 -dpi 96 -ac -kb &

== Directing Client to Virtual Server ==

Now that there is an X server running, switch back to Scratchbox.

The first step is to set the environmental variable so that X server knows to use a local domain socket, and tell all X clients to connect to Display number 2, since that is where Xephyr started:

<nowiki>
[sbox-FREMANTLE_X86: ~] > export DISPLAY=:2
[sbox-FREMANTLE_X86: ~] > ./gtk_helloworld-1
main: calling gtk_main
[[Ctrl+c]]
</nowiki>

Use Ctrl+C to terminate the program because it does not implement any graphical methods for closing.

''N.B.'' The DISPLAY needs to be set correctly on each Scratchbox login (or when switching targets).

Since you did not start a window manager for the X server, you cannot control Hello World with the mouse. Use Ctrl+C to terminate Hello World; you will start it again in a moment.

To quickly detach the foreground process from the shell and continue running the process in the background, press Ctrl+Z and then use the shell command bg. The process is "paused" between these two steps.

== Starting Application Framework ==

The next step is to have a graphical environment that will implement a nicer graphical screen. For this, a series of clients will be started, each of which have a specific role. These were introduced before.

To start the UI Framework, you can use a handy script that comes with the SDK:

[sbox-FREMANTLE_X86: ~] > af-sb-init.sh start

The start and stop parameters are used to start and stop the graphical environment. If everything works, it should show a screen resembling this one:

[[Image:UI-startup.png|400px]]

==Running Hello World in Application Framework ==
While the UI framework is running, the Hello World can be started again

[sbox-FREMANTLE_X86: ~] >./gtk_helloworld-1

[[Image:helloworld-without-theme.png|400px]]

Because there now is a window manager running, the client gets much larger window to draw in. GTK+ scales the widget accordingly (there is only one widget in the program).

The screen still looks a bit off. If the application is closed by pressing the X in the top-right corner, you can see that the Hello World disappears from the screen. Because no signals have been implemented yet and thus there is nothing to handle window destruction, the Hello World application is only hidden. It is still running (as can be seen in the sbox terminal emulator, since the shell does not display its prompt). Stop the Hello World program with Ctrl+C.

The next step shows how to use an SDK utility script called run-standalone.sh. Its job is to set up the correct environment variables for themes and communication for the command that is given to it as its command line parameter.

[sbox-FREMANTLE_X86: ~] >run-standalone.sh ./gtk_helloworld-1

[[Image:helloworld-with-theme.png|400px]]

The screen is still a bit off (there are no borders around the main GtkLabel widget), but already looks better. The text is scaled to be more in sync with the other text sizes and the color is also in sync with the platform color (it is not gray anymore).

Documentation/devtools/maemo5/xresponse-visualize

2009-11-13T16:01:49Z

192.100.124.218: update for Fremantle

== Description ==

xresponse-visualize is a set of scripts that can be used on the host/Scratchbox environment to visualize [[Documentation/devtools/maemo5/xresponse|xresponse]] log files.

* ''xresponse-convert'': create a series of images from xresponse logs highlighting the area of the screen where changes were detected.

* ''xresponse-visualize'': animates images create with xresponse-convert

== Packages ==

'''source''': xresponse-visualize

'''binary''': xresponse-visualize

== Usage Examples ==

-

== Notes ==

The recommended ''imagemagick'' dependency for xresponse-visualize is not (yet) provided with the maemo SDK, but are expected to be found from the user's host system. It's needed only by the animated GIF creation script, not by the visualization program itself.

== Links ==

[xresponse-convert man page](/development/documentation/man_pages/xresponse-convert.html)

[xresponse-visualize man page](/development/documentation/man_pages/xresponse-visualize.html)

== See Also ==

[[Documentation/devtools/maemo5/xresponse|xresponse]]

Documentation/devtools/maemo5

2009-11-13T11:59:46Z

192.100.124.218: /* Performance */

These tools are available in the official maemo 5 Fremantle tools repository at repository.maemo.org. Some of them may have already been available unofficially, but these versions are tested for functionality.

You can propose new tools by filing an enhancement request in Bugzilla.

Installation instructions are available [[#Installation | below]].

== Categories ==

The tools are arranged into different categories so that you can easily see what tools are available for specific kinds of tasks. The same tool can be present in multiple categories.

=== Code Analysis ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/doxygen | doxygen]] || a source code documentation generator tool
|-style="background:white"
| [[Documentation/devtools/maemo5/gtk-doc | gtk-doc]] || an API documentation generator
|}
=== Debugging ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/gdb | gdb]] || GDB is the GNU debugger
|-style="background:white"
| [[Documentation/devtools/maemo5/functracer | functracer]] || an allocation backtrace tool
|-style="background:white"
|[[Documentation/devtools/maemo5/functracer-postproc | functracer-postproc]] || a post-processing tool for functracer output data
|-style="background:white"
| [[Documentation/devtools/maemo5/latrace | latrace]] || display a program's dynamic library calls
|-style="background:white"
|[[Documentation/devtools/maemo5/ltrace | ltrace]] || a library call tracer
|-style="background:white"
| [[Documentation/devtools/maemo5/maemo-debug-scripts | maemo-debug-scripts]] || a set of scripts to help with debugging tasks
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-error-visualizer | sp-error-visualizer]] || displays log messages as banners
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-rich-core | sp-rich-core]] || a core dump data saver
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-startup-time | sp-startup-time]] || a library for calculating application startup times
|-style="background:white"
| [[Documentation/devtools/maemo5/strace | strace]] || a system call tracer
|-style="background:white"
|[[Documentation/devtools/maemo5/syslog | syslog]] || a log message collecting service
|-style="background:white"
| [[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
|[[Documentation/devtools/maemo5/x11-utils | x11-utils]] || a collection of X Window System debugging tools; xev, xwininfo, xprop, xlsatoms and xlsclients.
|}
=== Miscellaneous ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/less | less]] || a text file viewer/pager
|-style="background:white"
| [[Documentation/devtools/maemo5/osso-xterm | osso-xterm]] || a terminal emulator
|-style="background:white"
|[[Documentation/devtools/maemo5/man-db | man-db]] || manual page infrastructure
|-style="background:white"
| [[Documentation/devtools/maemo5/screen | screen]] || provides access to detachable console sessions
|}
=== Editors ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/nano | nano]] || a friendly text editor
|-style="background:white"
| [[Documentation/devtools/maemo5/vi | vi]] || a text editor
|}
=== Graphics ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/screenshot-tool | screenshot-tool]] || a command line utility to take screenshots
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|-style="background:white"
|[[Documentation/devtools/maemo5/xresponse-visualize | xresponse-visualize]] || scripts for visualizing xresponse logs
|}
=== Networking ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/iputils | iputils]] || a collection of TCP/IP related utilities
|-style="background:white"
| [[Documentation/devtools/maemo5/netcat | netcat]] || a utility to read and write data across network connections
|-style="background:white"
|[[Documentation/devtools/maemo5/tcpdump | tcpdump]] || a network traffic capturing utility
|-style="background:white"
| [[Documentation/devtools/maemo5/traceroute | traceroute]] || print the route packets take to a network host
|-style="background:white"
|[[Documentation/devtools/maemo5/wget | wget]] || a utility to non-interactively download files from the Web
|}
=== Performance ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/oprofile | oprofile]] || a low overhead system wide profiler
|-style="background:white"
| [[Documentation/devtools/maemo5/oprofileui | oprofileui]] || a user interface to oprofile
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-startup-time | sp-startup-time]] || a library for calculating application startup times
|-style="background:white"
|[[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|-style="background:white"
|[[Documentation/devtools/maemo5/xresponse-visualize | xresponse-visualize]] || scripts for visualizing xresponse logs
|}

=== Resource Usage ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/functracer | functracer]] || an allocation backtrace tool
|-style="background:white"
| [[Documentation/devtools/maemo5/functracer-postproc | functracer-postproc]] || a post-processing tool for functracer output data
|-style="background:white"
|[[Documentation/devtools/maemo5/htop | htop]] || an interactive process viewer
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-endurance | sp-endurance]] || tools to collect system endurance related information
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-endurance-postproc | sp-endurance-postproc]] || postprocessing scripts to parse and generate a report from endurance measurement data
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-memusage | sp-memusage]] || a collection of memory usage monitoring tools and scripts
|-style="background:white"
|[[Documentation/devtools/maemo5/sp-smaps-measure | sp-smaps-measure]] || utilities for taking snapshots of smaps memory information
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-smaps-visualize | sp-smaps-visualize]] || utilities for analyzing smaps memory information
|-style="background:white"
|[[Documentation/devtools/maemo5/sysstat | sysstat]] || tools for collecting and reporting system activity information
|-style="background:white"
| [[Documentation/devtools/maemo5/valgrind | valgrind]] || a suite of tools for debugging and profiling programs
|-style="background:white"
|[[Documentation/devtools/maemo5/xrestop | xrestop]] || shows X clients' X resource usage
|}
=== Test Automation ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/check | check]] || a unit test framework for C
|-style="background:white"
| [[Documentation/devtools/maemo5/sp-stress | sp-stress]] || tools to create artificial system load
|-style="background:white"
|[[Documentation/devtools/maemo5/xnee | xnee]] || automate user actions under X11
|-style="background:white"
| [[Documentation/devtools/maemo5/xresponse | xresponse]] || measures the time taken to update the screen after user action
|}
=== Wireless Tools ===
{| style="width:75%" border="1" cellpadding="2"
|-style="background:white"
|[[Documentation/devtools/maemo5/bluez-hcidump | bluez-hcidump]] || a tool to monitor Bluetooth activity
|-style="background:white"
| [[Documentation/devtools/maemo5/wireless-tools | wireless-tools]] || tools for manipulating Linux Wireless Extensions
|}
== Installation ==

These tools can be installed in the device by activating the Diablo tools repository in the Application manager. Developers can also install them to the device or in Scratchbox using the command line interface.

To activate the tools repository with the Application manager,
[http://mg.pov.lt/770/tools-repository.install open this single-click install file], or manually create a new catalogue like this:

{|
|-
|Catalogue name: || fremantle tools
|-
|Web address: || http://repository.maemo.org
|-
|Distribution: || fremantle/tools
|-
|Components: || free non-free
|-
|Disabled: || leave unchecked
|}

If you prefer to edit configuration files yourself instead of using the Application manager, add these lines to your ''/etc/apt/sources.list''

<pre>
# fremantle tools
deb http://repository.maemo.org fremantle/tools free non-free
# fremantle tools sources
deb-src http://repository.maemo.org fremantle/tools free non-free
</pre>

To install a binary package in Scratchbox:

<pre>
$ fakeroot apt-get install <bin pkg name>
</pre>

To install a binary package to the device (as root):

<pre>
$ apt-get install <bin pkg name>
</pre>

To install a source package in Scratchbox or to the device:

<pre>
$ apt-get source <src pkg name>
</pre>

Using Fremantle widgets

2009-11-12T09:27:31Z

192.100.124.218: /* Portrait Mode */

This document should help developers to port the user interface from [[Diablo]] to [[Fremantle]]. The document mirrors what was discussed on the mailing lists, forum and bug reports. It is based completely on the Fremantle Beta SDK which is the most recent SDK at the moment.
in addition, please check the growing [http://wiki.maemo.org/index.php?title=Documentation/Maemo_5_Developer_Guide/Human_Interface_Guidelines Human Interface Guidelines] and the official hildon documentation:
* [http://www.forum.nokia.com/info/sw.nokia.com/id/eb8a68ba-6225-4d84-ba8f-a00e4a05ff6f/Hildon_2_2_UI_Style_Guide.html Hildon 2.2 UI Style Guide]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/019c2b31-3777-49a0-9257-970d79580756/Hildon_2_2_Widget_UI_Specification.html Hildon 2.2 Widget UI Specification]
* [http://www.forum.nokia.com/info/sw.nokia.com/id/e778ba1f-2507-4672-be45-798359a3aea7/Fremantle_Master_Layout_Guide.html Fremantle Master Layout Guide]

Please feel totally free to add/update/change/remix this document. Many aspects are currently not discussed here but will hopefully be added by you!

Note: The casts of all code examples haven been removed for better readability.

= Toggle Buttons Vs. Radio Buttons =
The use of radio buttons in Fremantle is discouraged because they don't fit the visual style quite well. Instead you should use toggle buttons.

So if you need the behavior of radio buttons (which is that only one can be selected at a time) simply create them as usually and then call <code>gtk_toggle_button_set_mode()</code>. This will create a button that acts like a radio button, but is displayed as a toggle button.

Example:
<pre>
GtkWidget *b1 = gtk_radio_button_new_with_label("One");
GtkWidget *b2 = gtk_radio_button_new_with_label_from_widget(b1, "Two");
gtk_toggle_button_set_mode(b1, FALSE);
gtk_toggle_button_set_mode(b2, FALSE);
</pre>

[[Image:Fle_tut_radio_buttons.jpg|frame|Above you see how radio buttons are displayed in Fremantle. There is a bug in this screenshot, normally of course only one of the four options would be selected.]]

[[image:Fle_tut_toggle_buttons.jpg|frame|Here you can see four radio buttons which are displayed as toggle buttons using the <code>gtk_toggle_button_set_mode()</code> function mentioned above.]]

= Widget Sizes =
For some widgets there is now an enum which provides three different values: <code>HILDON_SIZE_FINGER_HEIGHT</code>, <code>HILDON_SIZE_THUMB_HEIGHT</code> and <code>HILDON_SIZE_AUTO_HEIGHT</code>. You can use them, for example, like that:
<pre>
GtkWidget but* = hildon_gtk_button_new(HILDON_SIZE_FINGER_HEIGHT);
</pre>
You should always use the finger or the thumb size, don't use HILDON_SIZE_AUTO_HEIGHT as the outcome is not totally clear (see below for screenshots).

If you have a button where you cannot provide a size with the constructor, for example, a stock button, then you can use <code>hildon_gtk_widget_set_theme_size()</code> to set the code afterwards. Like in this small example:
<pre>
GtkWidget *but = gtk_button_new_from_stock(GTK_STOCK_COPY);
hildon_gtk_widget_set_theme_size(but, HILDON_SIZE_THUMB_HEIGHT);
</pre>

Now to get a feeling for the different sizes here are some screenshots that show a HildonEntry together with a GtkButton using different sizes.

[[Image:Fle_tut_button_auto_finger.jpg|frame|A HildonEntry with HILDON_SIZE_AUTO_HEIGHT and a GtkButton with HILDON_SIZE_FINGER_HEIGHT. Looks inconsistent.]]

[[Image:Fle_tut_button_finger_finger.jpg|frame|Both widget with HILDON_SIZE_FINGER_HEIGHT. Looks more consistent now.]]

[[Image:Fle_tut_button_finger_thumb.jpg|frame|For comparison reasons the HildonEntry with HILDON_SIZE_FINGER_HEIGHT and the GtkButton with HILDON_SIZE_THUMB_HEIGHT.]]

= Window Menu =
In Fremantle it is not encouraged to use <code>GtkMenu</code> as window menu anymore. Instead you should use the <code>HildonAppMenu</code>. This new menu is really different from the old one so it´s worth taking a closer look. Here are the main features of the HildonAppMenu.
* It has big / finger friendly menu items.
* It holds a maximum of ten menu items.
* It does not support sub menues.
* The first row can be used for Filters. (Filters are explained in more details below.)
* In landscape mode the menu items are displayed in two rows.
* In portrait mode the menu items are automatically displayed in one row.
* There are no separators, so you cannot group your menu items.
* The menu items are GtkButtons and not GtkMenuItems.

The HildonAppMenu is meant to be displayed when the user clicks the title bar of the window, but it is possible to have several other HildonAppMenus in your application and activate them for example on button press.

As you can see the HildonAppMenu differs quite a lot from the old GtkMenu. The main difference is surely that you cannot have more then 10 menu items
inside the new menu. The Hildon HIG gives an overview on how to deal with that.

[[Image:Fle_tut_app_menu_with_filters.jpg‎|frame|A HildonAppMenu with two filters at the top and four buttons]]

== Using HildonAppMenu with GtkActions ==
As said earlier, the menu items are not GtkMenuItems anymore but instead they are normal GtkButtons. So you´re using GtkActions in your code, you´ll probably miss a replacement for <code>gtk_action_create_menu_item()</code>. There is no direct replacement, instead you just have to use standard gtk functions to connect the button as a proxy to the action. Here is an example:
<pre>
GtkButton *menu_item = gtk_button_new();
gtk_action_connect_proxy(action, menu_item);
</pre>
This is also possible with <code>GtkToggleAction</code> and <code>GtkRadioAction</code>. But remember that your GtkRadioButtons should look like GtkToggleButtons as mentioned above. So a complete example for a HildonAppMenu that should display three GtkRadioActions would look like this:

<pre>
GSList *group = NULL;
GtkAction *a1, *a2, *a3;
GtkWidget *b1, *b2, *b3;
GtkWidget *menu;

/* Create the actions */
a1 = gtk_radio_action_new("small", "Small", NULL, NULL, 0);
a2 = gtk_radio_action_new("normal", "Normal", NULL, NULL, 1);
a3 = gtk_radio_action_new("large", "Large", NULL, NULL, 2);

/* Build the radio action group */
gtk_radio_action_set_group(a1, group);
group = gtk_radio_action_get_group(a1);

gtk_radio_action_set_group(a2, group);
group = gtk_radio_action_get_group(a2);

gtk_radio_action_set_group(a3, group);
group = gtk_radio_action_get_group(a3);

/* Create the toggle buttons */
b1 = gtk_toggle_button_new();
b2 = gtk_toggle_button_new();
b3 = gtk_toggle_button_new();

/* Connect the buttons and the actions */
gtk_action_connect_proxy(a1, b1);
gtk_action_connect_proxy(a2, b2);
gtk_action_connect_proxy(a3, b3);

/* Create the menu */
menu = hildon_app_menu_new();

/* Add the buttons to the menu */
hildon_app_menu_append(menu, b1);
hildon_app_menu_append(menu, b2);
hildon_app_menu_append(menu, b3);
</pre>

= Finger Friendly GtkTreeView =
To get a finger friendly <code>GtkTreeView</code> it´s not enough to call <code>hildon_gtk_tree_view_new()</code> instead of <code>gtk_tree_view_new()</code> but you also have to put the tree view inside a <code>HildonPannableArea</code> to get finger friendly sizes. If you have your tree view inside a <code>GtkScrolledWindow</code> it will be displayed with stylus-style (like in Diablo).

Also if you´re displaying icons in your tree view you probably should use the 40x40 pixel version for Fremantle if you used the 26x26 pixel version in Diablo.

== Normal Vs. Edit Mode ==
There are now two different modes for the tree view. Those modes affect how the rows in a tree view react to finger taps.

You should use <code>HILDON_UI_MODE_NORMAL</code> if the user should only be able to activate one row of the text view. If the user taps a row in the tree view the <code>row-activated</code> is emitted. In standard Gtk+ this happens only if the user double clicks the row - a single click selects the row which is not possible with <code>HILDON_UI_MODE_NORMAL</code>.

If the user should be able to select or edit rows then you should use <code>HILDON_UI_MODE_EDIT</code>.

== Using Filters For Sorting ==
Most of you probably are using the tree view with a header row that displays column labels. Often this header row can also be used to sort the columns ascending or descending. If you're designing a finger friendly UI you will usually have a very limited number of visible columns - probably only one or two. In this case the column content is often self explanatory and the header row is only there for sorting. If that's the case for your UI, you might want to remove the header column completely and replace it with so called filters on the HildonAppMenu.

According to the HIG filters are meant to change how data is presented, but it should not affect the amount of data that is displayed. Sorting a tree view would be a possible use case. To do this, just have a look at the example:
<pre>
/* Remove the header row */
gtk_tree_view_set_headers_visible(view, FALSE);

/* Create two radio buttons for sorting */
GtkWidget *b1, *b2;
b1 = gtk_radio_button_new_with_label(NULL, "Sort By Title");
b2 = gtk_radio_button_new_with_label_from_widget(b1, "Sort By Date");

/* Draw them as toggle buttons not as radio buttons */
gtk_toggle_button_set_mode(b1, FALSE);
gtk_toggle_button_set_mode(b2, FALSE);

/* Add the buttons as filters to the menu */
hildon_app_menu_add_filter(menu, b1);
hildon_app_menu_add_filter(menu, b2);
</pre>

That is all for showing them on the window menu. Now only a callback is needed which gets activated whenever the user selects a filter. An example implementation might look like that:
<pre>
void on_sort_filter_clicked(GtkToggleButton *button, GtkTreeSortable *sortable)
{
if (gtk_toggle_button_get_active(button)) {
gtk_tree_sortable_set_sort_column_id(sortable, TITLE_COLUMN, GTK_SORT_ASCENDING);
}
}
</pre>

You can add as many filters as you like, but they will be displayed all in one row and there is no possibility to add another filter row. This means you have to select carefully what to put there and also have a look at the length of the strings.
If you, for example have two rows, one with a title and one with a date you could offer the user:
* Sort ascending by date
* Sort descending by date
* Sort ascending by title
* Sort descending by title
Those four strings will not fit into one row. Therefore you have to make a selection and include only the cases which will (hopefully) be most relevant to the user. In this case you should offer:
* Sort by title (which sorts by title ascending - A before B)
* Sort by date (which sorts by date descending - newest on top)
In the most recent version (not yet in Beta 2) the filter group has a fixed size which does not depend on the number of filters or the orientation of the device. So if your menu looks good in landscape mode it will look good in portrait mode.

[[Image:Fle_tut_tree_view.jpg‎|frame|A tree view without the title row. Sorting is now done with filters]]

[[Image:Fle_tut_tree_view_filter.jpg‎|frame|When clicking the title bar two filters are shown which let the user sort the tree view]]

[[Image:Fle_tut_filter_long_strings.jpg|frame|Long strings get truncated]]

= Context Menus =
To display finger friendly context menues there is a hildon helper function called <code>hildon_gtk_menu_new()</code>. Just call this instead of <code>gtk_menu_new()</code> and you´re done.
Example:
<pre>
GtkWidget *menu = hildon_gtk_menu_new();

GtkWidget *item1 = gtk_menu_item_new_with_label("Bla");
GtkWidget *item2 = gtk_menu_item_new_with_label("Blablabla");

gtk_menu_shell_append(GTK_MENU_SHELL(menu), item1);
gtk_menu_shell_append(GTK_MENU_SHELL(menu), item2);

gtk_widget_show_all(menu);
gtk_menu_popup(GTK_MENU(menu), NULL, NULL, NULL, NULL, 0,
gtk_get_current_event_time());
</pre>
''Note that in the Beta SDK there is a bug. If you´re using <code>GtkImageMenuItems</code> instead of <code>GtkMenuItems</code> the menu will have stylus-style. This bug is already fixed and a work around is available here: https://bugs.maemo.org/show_bug.cgi?id=4654 .''

[[Image:Fle_tut_context_menu.jpg‎|frame|Finger friendly context menu which is showing four stock items]]

= Panning =
Almost all of you will know the problems with scrollbars in Diablo. You can have small scrollbars which are not finger friendly or you can have large scrollbars which are using a lot of screen space and look ugly.

In Fremantle both kinds of scrollbars are still available, but there is also a third option. <code>HildonPannableArea</code> features kinetic panning using fingers. There is no scrollbar anymore, only a very small scroll indicator that indicates which part of the document you´re seeing right now.
<code>HildonPannableArea</code> can be used as a replacement for <code>GtkScrolledWindow</code> but there are things you have to keep in mind when doing so.

== GtkTextView Inside HildonPannableArea ==
Panning does not work with a <code>GtkTextView</code>. Instead you can use a <HildonTextView> which is a drop in replacement. The advantage is, that then panning is possible. The disadvantage is that selecting text is not possible anymore. The discussion about this is here: https://bugs.maemo.org/show_bug.cgi?id=4619

== GtkHtml Inside HildonPannableArea ==
When using <code>GtkHtml</code> inside a <code>HildonPannableArea</code> the panning is not smooth. The problem seems to be that GtkHtml provides some build in support for panning and that it conflicts with the panning offered by Hildon. See this bug report here: https://bugs.maemo.org/show_bug.cgi?id=4631

= Portrait Mode =
If your application should work in portrait mode you probably have to change the UI quite a bit. There are a couple of problems you'll might have:
* The toolbar is not wide enough to hold all items anymore.
* The columns of your tree view get too small.
* You cannot enter text because there´s no onscreen keyboard.
(Actually the FKB works perfectly, but it will switch to landscape
and then back to portrait when closed.)
* Dialogs are not shown correctly (see https://bugs.maemo.org/show_bug.cgi?id=4618 ).
* Probably more...

This means you have to listen to changes in the orientation and hide/show/change widgets to make the UI functional in portrait mode.

[[Image:Fle_tut_app_menu_portrait.jpg|frame|The HildonAppMenu with filters in portrait mode. The final version will cover the complete screen width, so there is a bit more space for the filters.]]

== Listening To Screen Orientation Changes ==
Basically here you´re not listening to changes in the devices orientation, but you check the height and width of the screen. So if width > height you are in landscape mode and if height > width you´re in portrait mode. This is supposed to work no matter why height and width changed. So it does not depend on hardware support like acceleratormeters it could also just be a software setting that rotates the screen.

<pre>
gboolean is_portrait()
{
GdkScreen *screen = gdk_screen_get_default();
int width = gdk_screen_get_width(screen);
int height = gdk_screen_get_height(screen);
if (width > height) {
return FALSE;
} else {
return TRUE;
}
}

void on_orientation_changed(GdkScreen *screen, GtkWidget *widget)
{
if (is_portrait()) {
gtk_widget_hide(widget);
/* Hide/Show other things */
} else {
gtk_widget_show(widget);
/* Hide/Show other things */
}
}
</pre>
Then inside your UI code you should listen to the <code>size-changed</code> signal of <code>GdkScreen</code>. For example:
<pre>
g_signal_connect(screen, "size-changed", on_orientation_changed, widget);
</pre>

== Testing Screen Orientation Changes In Scratchbox ==
For testing your code you can execute the following commands outside scratchbox:
<pre>
xrandr -display :2 -o left
xrandr -display :2 -o normal
</pre>

== Automatic Screen Rotation ==
Your application is not automatically rotated when the user rotates its device. Even if the hardware supports it. There are more things to do to make that happen. Basically you have to do two things:
* During startup of your application, or better shortly before showing the first window, you should check the orientation of the device and adjust your application.
* You have to listen to all changes in the devices orientation while your application is running and adapt accordingly.

Whether or not your application is rotated depends on a couple of things:
* There are two X window properties which you can set on your windows.
* Those tell the system what to do. The type of the value of the properties is <tt>XA_CARDINAL</tt> where 0 means "off", and 1 stands for "on". Other values may get other meaning in the future.
** <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> tells the system that your application can be rotated, so it won't prevent any other application from rotating.
** <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> tells the system that your application wants to be rotated.
* Rotation only happens when all visible windows are ok with being rotated.

That means that to get a rotated desktop all visible windows must have the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag set to 1 and at least one of them must have the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag set to true. The flags are inherited through the transiency chain, so you needn't set the SUPPORT flag on your transient dialogs for example, nor on all stackable windows.

It's important that you set the flags correctly on all windows that you open. If you or another application opens a window with the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag not set, the whole UI is rotated to landscape mode.

So here are the steps you have to do to make correct use of the portrait mode:
* On all windows that support portrait mode, set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag.
* During startup check the hardware orientation. If the hardware orientation is portrait mode, then set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag on at least one visible window.
* While running your application, listen to changes in the orientation of the device. If it is rotated to landscape mode set the <tt>HILDON_PORTRAIT_MODE_SUPPORT</tt> flag. If it's rotated to portrait mode set the <tt>HILDON_PORTRAIT_MODE_REQUEST</tt> flag.
It is not necessary to set 'request' together with 'support' as 'request' implies 'support', provided that 'support' is unset (as opposed to set to 0).

=== Finding Out The Current Hardware Orientation ===
In order to find out whether or not the device currently is in portrait you need to ask the MCE (Mode Control Entity) via DBus. The parameters of the call are the following and can be found as constants in 'mce/dbus-names.h'.

<pre>
Service: "com.nokia.mce"
Path: "/com/nokia/mce/request"
Iterface: "com.nokia.mce.request"
Member: "get_device_orientation"
</pre>

This method returns several values:
* gchar * portrait/landscape orientation (see mce/mode-names.h for valid portrait/landscape states)
* gchar * on/off stand (see mce/mode-names.h for valid stand states)
* gchar * face up/face down (see mce/mode-names.h for valid facing states)
* dbus_int32_t x axis (unit mG)
* dbus_int32_t y axis (unit mG)
* dbus_int32_t z axis (unit mG)

In our case we are only interested in the first return value which will be 'portrait' or 'landscape'. Because we only need to know the first value here we can use the <tt>osso_rpc_run_system()</tt> function for making this call to DBus. It's a convenience function provided by libosso for making DBus calls. The advantage is that our code gets shorter, the disadvantage is that it only return the first return value - which in our case is ok. So here is the code using libosso.

<pre>
#include <mce/dbus-names.h>
#include <mce-dev/mode-names.h

gboolean
device_is_portrait_mode(osso_context_t* ctx)
{
osso_rpc_t ret;
gboolean result = FALSE;

if (osso_rpc_run_system(ctx, MCE_SERVICE, MCE_REQUEST_PATH,
MCE_REQUEST_IF, MCE_DEVICE_ORIENTATION_GET, &ret, DBUS_TYPE_INVALID) == OSSO_OK) {
g_printerr("INFO: DBus said orientation is: %s\n", ret.value.s);

if (strcmp(ret.value.s, MCE_ORIENTATION_PORTRAIT) == 0) {
result = TRUE;
}

osso_rpc_free_val(&ret);

} else {
g_printerr("ERROR: Call do DBus failed\n");
}

return result;
}
</pre>

=== Listening To Hardware Orientation Changes ===

So now you know how to ask the device for its orientation. Now let's see how to connect a signal handler to listen to changes in the orientation.

First here is again the signature:
<pre>
Service: "com.nokia.mce"
Path: "/com/nokia/mce/signal"
Iterface: "com.nokia.mce.signal"
Member: "sig_device_orientation_ind"
</pre>

The signal transports three values:
* gchar * portrait/landscape orientation (see mce/mode-names.h for valid portrait/landscape states)
* gchar * on/off stand (see mce/mode-names.h for valid stand states)
* gchar * face up/face down (see mce/mode-names.h for valid facing states)

Again we are only interested in the first value which is 'portrait' or 'landscape'. Unfortunately there is no libosso convenience function for listening to DBus signals, so we have to use the raw DBus API.

<pre>
static DBusHandlerResult
dbus_handle_mce_message(DBusConnection *con, DBusMessage *msg, gpointer data)
{
DBusMessageIter iter;
const gchar *mode = NULL;

if (dbus_message_is_signal(msg, MCE_SIGNAL_IF, MCE_DEVICE_ORIENTATION_SIG)) {
if (dbus_message_iter_init(msg, &iter)) {
dbus_message_iter_get_basic(&iter, &mode);
g_printerr("INFO: New orientation is now: %s\n", mode);
}
}
return DBUS_HANDLER_RESULT_NOT_YET_HANDLED;
}
</pre>

Now we need to register this signal handler.

<pre>
#define MCE_MATCH_RULE "type='signal',interface='" MCE_SIGNAL_IF "',member='" MCE_DEVICE_ORIENTATION_SIG "'"

/* Get the system DBus connection */
DBusConnection *con = osso_get_sys_dbus_connection(osso_context);

/* Add the callback, which should be called, once the device is rotated */
dbus_bus_add_match(con, MCE_MATCH_RULE, NULL);
dbus_connection_add_filter(con, dbus_handle_mce_message, NULL, NULL);
</pre>

=== Listening To Hardware Orientation Changes (Python example) ===

This short snippet should get you started (you only need the gobject.MainLoop if you are writing a console application). "handler" will be called every time the orientation changes, and the first parameter is the important one (compare it to "landscape" and "portrait").

<pre>import dbus
import dbus.glib

# Again, this is only needed for console apps
import gobject
mainloop = gobject.MainLoop()

# Define some constants
MCE_SIGNAL_NAME = 'sig_device_orientation_ind'
MCE_SIGNAL_IFACE = 'com.nokia.mce.signal'
MCE_SIGNAL_PATH = '/com/nokia/mce/signal'

# Get the system bus
system_bus = dbus.Bus.get_system()

# Define a callback that gets called for orientation changes
def handler(orientation, stand, face, x, y, z):
print orientation

# Connect the "handler" to the orientation changed signal of mce
system_bus.add_signal_receiver(handler, signal_name=MCE_SIGNAL_NAME, \
dbus_interface=MCE_SIGNAL_IFACE, path=MCE_SIGNAL_PATH)

# Start the main loop - only needed for console apps
mainloop.run()</pre>

Do you want it even more comfortable? See [http://talk.maemo.org/showthread.php?p=330992 this forum post] for a link to an easy-to-use drop-in module that will take care of auto-rotation all your application windows.

== Testing Hardware Orientation In Scratchbox ==
Testing whether or not your DBus signal handler for device orientation change works is easy. Just run the following commands inside scratchbox while your application is running.

Device was rotated into portrait mode:
<pre>
run-standalone.sh dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'portrait'
</pre>

Device was rotated into landscape mode:
<pre>
run-standalone.sh dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'landscape'
</pre>

For testing the call to the MCE you first have to install the MCE because it's not part of the default SDK installation. Simply do:
<pre>fakeroot apt-get install mce</pre>
Now start it using the debug mode. It won't start without the '--debug-mode' flag. You'll get lots of debug output on the terminal, just ignore it:
<pre>mce --debug-mode</pre>

Now the DBus call to the MCE should return 'landscape'. It probably will always return 'landscape' when run inside the SDK as it is not possible to really rotated the "device" there.

= References =
In no particular order

* http://maemo.org/api_refs/5.0/beta/tutorial/html
* http://maemo.org/api_refs/5.0/beta/hig/html

* http://lists.maemo.org/pipermail//maemo-developers/2009-May/019368.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-May/019144.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-June/019426.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-June/019579.html
* http://lists.maemo.org/pipermail//maemo-developers/2009-August/020202.html

* https://bugs.maemo.org/show_bug.cgi?id=4617
* https://bugs.maemo.org/show_bug.cgi?id=4618
* https://bugs.maemo.org/show_bug.cgi?id=4619
* https://bugs.maemo.org/show_bug.cgi?id=4654
* https://bugs.maemo.org/show_bug.cgi?id=4637
* https://bugs.maemo.org/show_bug.cgi?id=4648

[[Category:Development]]
[[Category:Fremantle]]

Maemo Summit 2009/Day 3

2009-11-01T17:53:54Z

192.100.124.218:

= Maemo Summit day 3, Sunday 11 October =

=== Fremantle Stars showcase ===

Take a tour of the Fremantle Stars, the best of the best in Maemo community developed applications, featuring:
; liqbase
: Gary Birkett, liquid at gmail dot com, lcuk on #maemo
; [http://mauku.innologies.com Mauku]
: [http://www.henrikhedberg.net Henrik Hedberg]
; OSM2Go
: Till Harbaum
; OMWeather
: Vlad Vasilyev
; eCoach
: Sampo Savola

=== Maemo Browser for power users ===
*Author: Mikko Korpelainen, mikko.korpelainen at nokia dot com
*Intended audience: users
*Talk type: presentation
*Abstract/description
: Quick overview of the Maemo Browser design and capabilities. Followed by an in-depth explanation of the end user features and settings the Maemo Browser has.
*Author bio
: Mikko Korpelainen is a senior product manager @ Maemo for browser, FlashPlayer, maps and location.

=== Maemo Browser evolution ===
*Author: Oleg Romashin, oleg.romashin at nokia dot com
*Intended audience: developers
*Talk type: presentation
*Abstract/description
: Quick overview of the Maemo Browser improvement process, rendering architecture.
Link to presentation: http://docs.google.com/present/view?id=ajk2s2df9zhr_144fb8zrrck
*Author bio
: Oleg Romashin is a senior lead developer @ Maemo for browser.

=== Maemo Browser extension development ===
*Author: Sudarsana Nagineni, sudarsana.nagineni at nokia dot com
*Intended audience: developers
*Talk type: presentation - [http://docs.google.com/present/view?id=dct6z7j7_25zrcj3hs Slides]
*Abstract/description
: A tutorial on how to develop extensions for Maemo Browser.
*Author bio
: Sudarsana Nagineni is a senior developer at Maemo for browser.

=== [http://jammo.garage.maemo.org JamMo - Jamming mobile game for children] ===
* Author: Aapo Rantalainen (aapodotrantalainenatgmaildotcom)
* Intended audience: application developers
* Talk type: presentation
* Abstract/description
: JamMo is an educational music making game for children at age 3-12. It is targeted for Maemo 5 Fremantle. It uses GStreamer at music backend and Clutter toolkit for graphical user interface. In this talk we present the first version of the application and our experiences on underlying technologies. The development of JamMo is open to everyone who is interested to contribute in any way. For more information see http://jammo.garage.maemo.org/
* Additional Information
: Needed equipment: video projector, canvas, speakers.

* Author bio
: JamMo is a product of an EU funded [http://www.umsic.org/ UMSIC project]. Aapo Rantalainen is the head developer of JamMo.

=== Writing plugins for MAFW ===
*Author: Iago Toral - itoral at igalia dot com
*Intended audience: platform and application developers.
*Talk type: Presentation (Tutorial)
*Abstract/description
: A tutorial on how developers can write source and renderer plugins for the Media Application Framework (MAFW). The audience will learn how to develop new plugins that provide access to new sources of media content or implement different rendering backends and how they can use these plugins from their own media applications. The tutorial will also include an introduction to MAFW for those not familiar with the framework.
*Author bio
: I am a Software Engineer at Igalia and user of the Gnome Desktop and Linux OS for quite many years. Currently I am most interested in Multimedia, specially around MAFW, for which I am one of the main developers, and GStreamer.

=== Hackathon: Integrating Canola with Fremantle ===
*Author: [http://maemo.org/profile/view/etrunko Eduardo Lima (Etrunko)]
*Intended audience: Application Developers
*Talk type: Hands-on/Hackathon
*Abstract/description
: The idea of this session is to get a reasonable number of people interested in integrating Canola with the new technologies introduced in Fremantle, mostly Tracker and MAFW, together, so we can trace a plan and start getting our hands dirty.

: ''Why??''

: Some Canola components were conceived aiming to provide alternate solutions for some Nokia closed-source libraries and others that were not available by the time we started the project (mid-2007, back then we only had the N800 with Bora/Chinook). That's why we created our own media scanner (lightmediascanner+canolad) and media engine (atabake). Now I think it is time for us to evolve to the new and open solutions provided by Fremantle, yet keeping compatibility with "legacy" platforms, such as Diablo.

: People interested in developing plugins for Canola and/or developing using EFL/PyEFL are more than welcome to join us.
*Extra equipment
**<strike>''Guns, lots of guns.''</strike>
**Brave hacker souls
**Power outlets galore
**Internet Connection
**Whiteboard/Flipchart
**Coffe
*Author bio
: Open Source Software enthusiast, involved with Maemo since the very beginning (mid 2005), and had the opportunity to be part of the first Maemo Community Council. Started porting various GTK+/GNOME applications (Gnumeric, Evince, Abiword, Leafpad, Xournal, etc), to the platform. Worked on the first version of Carman, written in Python + GTK. After that, joined the team developing the Canola media player, coding and maintaining its packages for Maemo since then. Also maintains packages of the Enlightenment Foundation Libraries (EFL) for Maemo. Works for openBossa/INdT, where has been having the opportunity to present and talk about Maemo in events in Brazil and worldwide.

=== Maemo documentation co-creation ===

*Dave Neary, dneary at maemo dot org
*Intended audience: Users
*Talk type: Presentation
*Abstract/description
: The stated goal in the 2010 agenda for maemo.org is the co-creation of all Maemo documentation.
: This presentation will show the path we have traveled towards this goal so far, especially over the past year, the plans for Fremantle and Harmattan, and most importantly, a call to action showing how you can help out.

*Author bio
: Dave Neary has participated in many free software projects over the years. He was release manager of the GIMP, chairman of the GNOME Foundation, and community and product manager for the OpenWengo project. He is currently the maemo.org Docmaster, a role where he works to enable the Maemo community to do great work, and an independent consultant helping companies work with and create healthy communities.

=== Designing QT application for Maemo 5 and Maemo 6===
*Sergiy Dubovik <sergiy dot dubovik "at sign" nokia point com>, Ian Monroe <ian.monroe at collabora.co.uk>
*Intended audience: application developers
*Talk type: presentation
*Abstract/description

:How application developers should design their applications to work on Maemo 5 and Maemo 6 platforms? Which widgets will be supported? How to handle possible virtual keyboard? Where to store application settings? Which QT services will be available? These questions will be answered.

*Additional information on extra equipment you might need or something else goes here
:Just a projector

*Author bio
: Sergiy Dubovik is a senior software developer working in Nokia, designing and developing UI frameworks for Harmattan program.

: Ian is a software developer at Collabora Ltd where he works from home in Iowa City, Iowa USA. He has been a developer of the popular desktop music manager Amarok for four years. He is the maintainer of KDE's video player, Dragon Player.

=== Building for Mer ===
* [[User:lbt|David Greaves]]
* Intended audience: application & platform developers
* Talk type : Presentation/demo
* Abstract
: Since Fremantle Extras applications will eventually be submitted to the Mer builder it may be a good idea to introduce it. We use the openSuse Open Build Service; a GPL service that provides an emulated, pristine (yes, I'm looking at you autobuilder and scratchbox), dependency driven build environment. I'll talk about the processes around Mer builds, access controls, managing integration with our DVCS (git), acceleration tricks and generally how to make good use of things you find lying about on the web.

*Additional Information
: Live web link to OBS would be good.

*Author bio
: David is the Mer build mentor; he's been a solutions architect at a major telco for several years but still (kinda) knows how to code. He's a passionate believer in the commercial viability of OSS. Previous contributions include kick-starting the git documentation & establishing wikis for Linux RAID and MythTV. He runs linux everywhere.

=== Handheld Glom: Easy database applications ===
* Murray Cumming <murrayc at openismus dot com>
* Intended audience: application developers
* Talk type: Presentation
* Abstract/description:
: Many custom Maemo applications just need the user to navigate through some data and enter new information. Glom lets you quickly throw together a database structure and UI layout, providing a Maemo UI with no coding. You can then use Python for anything more complicated, though Glom itself already supports features such as related records, related fields, related choices, field lookups, calculated fields, and translated UIs.
*Author bio:
: Murray Cumming runs Openismus GmbH in Berlin and Munich. We work on Maemo's development platform and applications and maintain the GNOME C++ API (gtkmm). When we have extra time we work on Glom, gradually getting it ready for real-world use.

=== Towards painless and quality translations ===
* Dimitris Glezos (glezos _at_ indifex _dot_ com)
* Intended audience: developers, translators, docs writers, webmasters
* Talk type: Presentation
* Material: [http://media.indifex.com/other/maesum.pdf Slides (pdf)]
* Abstract/description
: Most developers agree: "Translations are hard". And while Maemo's localization is already in place, we've got a long way to maximize our efficiency in reaching a global audience. The challenges: lower the costs for developers, minimize maintenance overheads, provide the translators with an effective, easy-to-use interface for submitting translations to their favorite projects (even if they're hosted on git.. *especially* when they're hosted on git).
: Transifex is an open localization platform built for and used by communities similar to Maemo such as Moblin, Fedora and XFCE. This talk will present Transifex, discuss the test results by the Mer Project, and lay down the roadmap for the establishment of an infrastructure able to support the L10n process of Maemo.
*Additional Information
: The session will most likely turn into a BoF, bringing together application and platform developers, translators and webmasters/admins.
*Author bio
: Dimitris Glezos is the lead developer Transifex. He led Fedora re-engineer its globalization infrastructure allowing for an explosive growth of community translations. He currently serves as Fedora's Board member and Translation Leader. He works at Indifex, providing enterprise-level support on complex localization scenarios.

=== 10 Tips for Designing Mobile Widgets ===
*Author: [http://maemo.org/profile/view/rajeshlal Rajesh Lal], rajesh.lal at nokia dot com
*Intended audience: Widget Developers/Mobile Application Developers
*Talk type: Presentation

*Abstract/description
: Do you know why only 1 percent of Mobile Widgets are successful ? What makes some widgets thrive and used by millions, and others with equal functionality bite the dust ? Make no mistakes, design of a widget is not about graphics, color or fonts. This presentation will demystify this 'invisible' layer below the surface with 10 pragmatic tips. The tips will uncover some of the most useful, and often ignored standard design principles and how to apply them in a mobile context.

*Author bio
: Rajesh lal is a Designer, Author, Technology Evangelist, and a Senior Nokia Engineer with a decade of experience in Information Technology. He has been involved in Widget design and development for last 5 years and have authored multiple books on Gadgets and Widgets. He has experience in a variety of Mobile devices, namely Sony Mylo, Window's Mobile, Apple's Iphone, Nokia S60 and Maemo devices. His blog on design and user experience can be found at http://abcofdesign.com

=== Mobile Office based on KOffice Open Source Project===
*Suresh Chande, suresh.chande at nokia.com
*Intended audience: Application & Platform developers
*Talk type: Presentation
*Abstract/description
: We will present here Mobile Office project developed for Fremantle based on KOffice, a Qt based open source project.

*Additional Information (optional)
: We will demonstrate Mobile Office (KOffice) running on the N900.
: Blog Entry: http://labs.trolltech.com/blogs/2009/09/17/office-viewer-for-maemo5-based-on-koffice/

*Author bio
: Suresh Chande, works for Nokia in Device R&D(Maemo ) as Technical Product Owner for the Office Domain. Suresh has worked at Nokia Research Center for over 11 years focusing Mobile Business and Enterprise Application research. His vision is to have Office tools free for use by everybody.

=== Maemo Platform Security: Principles and Concepts ===

* Elena Reshetova - elena.reshetova@nokia.com
* Intended audience: users, application developers, platform developers
* Talk type: presentation - [http://www.slideshare.net/peterschneider/maemo-6-platform-security Slides]
* Abstract/description:

: The purpose of the Platform Security in the Maemo platform is to protect the owner of a Maemo-powered device from getting her personal, private data and passwords from being stolen and used for malicious purposes, to prevent a malware from misusing a device and incurring costs on user, to prevent a user from accidentally breaking the device and to make the platform meet the requirements set by such third party software that requires a safe execution environment.

: The main design goal is to have all this accomplished without any significant penalty in terms of performance or usability, by using established open standards and having as much of the implementation open-sourced as possible. Another goal is to minimize an entry barrier for 3rd party programmers by reusing the existing Linux programming environment and introducing only needed additional features.

: The presentation will cover the main principles and concepts of the Maemo Platform Security.

*Author bio
: Elena is a senior security engineer and representative of Maemo security team at the Maemo summit. The current task of the team is development of the Maemo Security FW.

=== Telepathy on Maemo ===
* Author: Marco Barisione, marco.barisione at collabora.co.uk
* Intended audience: application developers/platform developers
* Talk type: presentation

* Abstract/description:
The [http://telepathy.freedesktop.org/ Telepathy real-time communication framework] is a project to abstract messaging, presence, voice and video functionality, regardless of the underlying protocol. Amongst numerous benefits, this makes the connections available as a D-Bus service which can be shared between multiple applications, rather than limited to single monolithic jack-of-all-trades clients.

The talk will introduce the Telepathy framework, its basic concepts and current functionality. It will focus in particular on:
- The Telepathy architecture
- How Telepathy is used on Maemo 5 for chat, VOIP calls, telephony calls and SMS messages
- How to use Telepathy from your program

* Author bio:
Marco Barisione started to work on Telepathy implementing file transfer for a Google Summer of Code and for his University final project. After graduating he started to work for Collabora where he worked both on Telepathy and on the GTK+ port of WebKit and he spent the last year working on Telepathy-related components for Maemo.
Before falling in love with Telepathy he worked on various other GNOME projects, in particular adding regular expression support to GLib and implementing a new syntax highlighting engine for the GtkSourceView widget.

=== Extending the Hildon desktop ===
*Author: Marc Ordinas i Llopis ([[User:Marcoil|marcoil]]), marcoil at collabora dot co dot uk
*Intended audience: application developers/platform developers
*Talk type: presentation
*Abstract/description
: Developers can easily extend Maemo 5's desktop, giving users new ways to view and interact with the data in their mobile device. In this talk I'll describe the basic architecture and components of the desktop and show how to extend it.
*Author bio
: Marc is a programmer at Collabora and has been working on hildon-desktop for the last year.

=== What to do about /opt in Fremantle ===
Author: [[User:mvo|Marius Vollmer]]
*Intended audience: TBD
*Talk type: BoF
*Abstract/description
: For Fremantle, packages in the Extras repository are asked to install files into /opt to make better use of the available flash space.
This BoF is an opportunity to discuss everything related to this, immediate next steps and long term solutions, according to the interest of the participants.
*Author bio
: TBD

Documentation/Maemo 5 Developer Guide/Architecture/RTCOM

2009-10-29T12:47:50Z

192.100.124.218: /* Functionalities provided */

=Real Time Communications domain=
The RTCom domain provides both services and applications for real time Internet communications, such as Voice Over IP / Video calls and Instant Messaging, and also cellular/CS communications on Maemo platform. It also provides and distributes presence information within the system.
The architecture consists of a few major components; connection managers which abstract implementation details of different protocols to a common API, mission control to handle transient events and enforce system policies, and user interfaces to present information to the user. There is also a streaming server to handle actual media streaming communications. It is not conceptually a separate architectural element of the framework, but more like one UI implementation. Farsight interface is used to manage media pipelines.

==System decomposition view==
The diagram below shows the entities of the RTCOM subsystem, dependencies between them, provided interfaces and required external interfaces. The client applications are shown as packages without the fill-color.
Different UI components (Messaging, Call, Log Viewer, Desktop Elements, Control Panel Applets) provide user interface layer to the system.

On intermediate layer, there’s a Mission Control package, which handle transient events and enforce system policies, providing application logic services, and libtelepathy-glib component providing GObject-style access to the Telepathy DBUS interfaces.

On lowest level, there are Streaming Engine to handle actual media streaming communications, and Connection managers that abstract implementation details of different protocols to a common API. The interface is modular and platform includes Jabber (instant messaging) and SIP (voice and video calls).

The Telepathy framework is used to handle real time communication related signaling and abstracting all protocol dependencies to a single D-BUS interface.

Centralized addressbook is provided by the Contacts subsystem and used by the RTcom subsystem for all contact information storage and lookup purposes and it also stores transient contacts/states.

==RTCOM framework==

In Fremantle, RTCom framework provides the following functionality:
*Support for comprehensive logging
*SSO related components
*Support for heartbeat
*Device presence profiles
*Support for BT HFP
*Location support for presence

===telepathy-glib===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Provides GObject abstraction of Telepathy DBUS interfaces
|-
|'''Source packages'''||telepathy-glib, librtcom-telepathy-glib
|-
|'''Licenses'''||LGPL and Nokia Proprietary
|-
|'''Interfaces used'''||libglib, libdbus, libdbus-glib
|-
|'''Interfaces provided'''||libtelepathy-glib, librtcom-telepathy-glib
|}

===telepathy-mission-control===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Provides a way for “end user” applications to abstract some of the details of connection managers to provide a simple way to manipulate a bunch of connection managers at once and remove the need to have in each program the account definitions and credentials.
|-
|'''Source packages'''||telepathy-glib, librtcom-telepathy-glib
|-
|'''Licenses'''||LGPL and Nokia Proprietary
|-
|'''Interfaces used'''||libglib, libdbus, libdbus-glib
|-
|'''Interfaces provided'''||libtelepathy-glib, librtcom-telepathy-glib
|}

===osso-mission-control===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Mission control filters
|-
|'''Source packages'''||telepathy-mission-control
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces used'''||libmissioncontrol, libosso, libconic, libebook, libhildon1 (libhildon-desktop), mce, libxml2, librtcom-eventlogger, librtcom-eventlogger-plugins, libsignon-glib
|-
|'''Interfaces provided'''||None
|}

===osso-accounts===
{|cellspacing="0" border="1" width="70%"
|-'''Purpose'''||Provides a set of libraries, UIs and applets for account management.
|-
|'''Source packages'''||osso-accounts, osso-accounts-plugin-nokia-chat
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces used'''||libgtk2, libhildon1 (libhildon1, libhildonfm2, hildon-control-panel, libhildonmime, libhildonhelp), libosso-abook, libglade2, libconic, libmcclient
|-
|'''Interfaces provided'''||libaccounts, libaccounts-glade, libosso-rtcom-accounts
|}

===rtcom-eventlogger===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Provides general purpose event log database system.
|-
|'''Source packages'''||rtcom-eventlogger
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces used'''||libglib, libsqlite3, libdbus
|-
|'''Interfaces provided'''||librtcom-eventlogger
|}

===rtcom-eventlogger-plugins===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Provides plugins for the event logging system.
|-
|'''Source packages'''||rtcom-eventlogger-plugins
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces used'''||libglib, libsqlite3, librtcom-eventlogger
|-
|'''Interfaces provided'''||None
|}

==Connection Managers==
Connection managers can be thought of as a kind of protocol plugins of the system. They conform to Telepathy DBUS interface specification and provide DBUS interface abstraction of some protocol. Each connection manager usually provides support for one protocol. The provided interfaces depend on the capabilities of the connection manager and protocol.

Connection managers only signaling protocols. In case of a media streaming session, SDP or similar negotiation signaling is done in Connection Manager using the signaling protocol, but actual payload streaming is handled by Streaming Engine (Eg: telepathy-stream-engine).

===Functionalities provided===

*Support for Skype integrated into Telepathy framework

===sofia-sip===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||SIP-stack implementation
|-
|'''Source packages'''||sofia-sip
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libssl
|-
|'''Interfaces provided'''||libsofia-sip-ua, libsofia-sip-ua-glib
|}

===telepathy-sofiasip===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||SIP connection manager
|-
|'''Source packages'''||telepathy-sofiasip
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libdbus, libdbus-glib, libsofia-sip-ua, libsofia-sip-ua-glib, libtelepathy-glib, libssl
|-
|'''Interfaces provided'''||None
|}

===loudmouth===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||XMPP-stack implementation
|-
|'''Source packages'''||loudmouth
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libssl, libcertman (libcst)
|-
|'''Interfaces provided'''||libloudmouth
|}

===telepathy-gabble===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||XMPP connection manager
|-
|'''Source packages'''||telepathy-gabble
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libssl
|-
|'''Interfaces provided'''||libglib, libdbus, libdbus-glib, libloudmouth, libtelepathy-glib
|}

==Streaming Engines==
Media engines handle media streaming needs for multimedia communication methods like voice and video conversation. Generic telepathy-stream-engine provides voice and video streaming capabilities over RTP protocol. If there is a need for other kind of media streaming for some connection manager, it might be reasonable to provide separate media engine for that purpose.
Independent of possible other uses, libjingle is used to provide NAT traversal using STUN, GTalk relay and ICE technologies for the GTalk service. libnice provides fully standards compliant ICE implementation.

===Functionalities provided===

*Support for fully standards compliant ICE through libnice.
*Support for H.264
*Support for BT HFP.
*Support for Skype in Telepathy framework.

===gst-plugins-farsight===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||GStreamer plugins specific to Farsight.
|-
|'''Source packages'''||gst-plugins-farsight
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, gstreamer (libgstreamer-pligins-base), libjingle, libgonf2
|-
|'''Interfaces provided'''||None
|}

===farsight2===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||The Farsight project is an effort to create a framework to deal with all known audio/video conferencing protocols. On one side it offers a generic API that makes it possible to write plugins for different streaming protocols, on the other side it offers an API for clients to use those plugins. This package provides the core Farsight 2 library.
|-
|'''Source packages'''||farsight2
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, gstreamer (libgstreamer-plugins-base, libgstreamer-plugins-good, libgstreamer-plugins-bad), libnice, libnice-gstreamer, gupnp
|-
|'''Interfaces provided'''||libgstfarsight
|}

===telepathy-farsight===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Glue betweeen Telepathy and Farsight2
|-
|'''Source packages'''||telepathy-farsight
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libdbus (libdbus, libdbus-glib), libgstfarsight, libtelepathy-glib
|-
|'''Interfaces provided'''||libtelepathy-farsight
|}

===libnice===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||ICE NAT-traversal implementation
|-
|'''Source packages'''||libnice
|-
|'''Licenses'''||MPL / LGPL
|-
|'''Interfaces used'''||libglib, gstreamer (libgstreamer, libgstreamer-plugins-base)
|-
|'''Interfaces provided'''||libnice, libnice-gstreamer
|}

===telepathy-stream-engine===
{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Media streaming engine for Telepathy, mostly used for standard RTP-over-UDP streaming.
|-
|'''Source packages'''||telepathy-stream-engine
|-
|'''Licenses'''||LGPL
|-
|'''Interfaces used'''||libglib, libdbus (libdbus, libdbus-glib), libgstfarsight, gstreamer (libgstreamer-plugins-base), libtelepathy-farsight, libgtk2
|}

==telepathy-glib==
Telepathy Library’s role is to provide common GObject-based C-language API for applications. It wraps Telepathy DBUS interfaces to GObjects and also provides some utility functions for accessing and enumerating DBUS interfaces. It’s code is mostly autogenerated from DBUS interface spec.

{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||C API for Telepathy DBUS interfaces.
|-
|'''Responsibilties'''||Provides GObject based C-language API to the Telepathy DBUS interfaces along with some utility functions.
|-
|'''Notes'''||Most of Telepathy’s functionality is distributed as DBUS objects where the actual functionality doesn’t necessarily reside within any specific component, but as an abstract object in the DBUS network.''
|-
|'''License'''||LGPL
|}

'''Interfaces used by libtelepathy-glib'''
{|cellspacing="0" border="1" width="70%"
|'''Interface name'''||'''License'''||'''Dependency'''||'''Description'''
|-
|Telepathy||LGPL||glib, DBUS||RTCom Interface
|}

==Mission Control==
Communication system policies are usually dependent on application and environment, thus some method external to framework has to exist for handling those. Mission Control thus enforces communication system policies. It also handles configuration information storage, network connectivity from policy point of view and is thus responsible for starting and stopping connection managers and engines. While starting up connection managers and engines, it provides the configuration information.
In case of network side event like presence subscription or start of communication session, Mission Control handles these transient events based on system policy and possibly starts associated UI components.
Misson Control employs plugin methods to provide possibility to add special event handlers called “mission control filters”. These plugins can provide special device or system dependent function handling.

{|cellspacing="0" border="1" width="70%"

|'''Purpose'''||Enforces policies, handles startup/connectivity and transient events.
|-
|'''Responsibilities'''||Enforces system policies. Handles Connection Managers, Engines and UI startups. Also handles transient and network side events. Also responsible for connectivity management.
|-
|'''Packages'''||curlpp, osso-mission-control, osso-rtcom-oma, telepathy-mission-control
|-
|'''License'''||LGPL, Nokia Proprietary
|}

==User Interfaces==

===Messaging UI===

{|cellspacing="0" border="1" width="70%"
|'''Name'''||rtcom-messaging-ui
|-
|'''Purpose'''||Messaging application.
|-
|'''Source Packages'''||rtcom-messaging-ui
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used'''||libglib, libosso, libgtk2, libhildon1 (libhildon1, libhildon-mime, libhildonfm2), libgconf2, libtelepathy-glib, librtcom-telepathy-glib, libmcclient, libosso-abook, libebook, mce, maemo-launcher, librtcom-eventlogger, librtcom-eventlogger-ui, librtcom-eventlogger-plugins, browser-neteal
|}

Messaging UI is a user interface component for instant messaging sessions. It handles all kinds of non-media streaming communications like text chat.

===Event logger===
{|cellspacing="0" border="1" width="70%"
|'''Name'''||rtcom-eventlogger-ui
|-
|'''Purpose'''||Event logger widgets.
|-
|'''Source Packages'''||rtcom-eventlogger-ui
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used'''||libglib, libgtk, libdbus, librtcom-eventlogger, librtcom-eventlogger-plugins, libosso, libosso-abook, libhildon1, libmcclient
|-
|'''Interfaces Provided'''||librtcom-eventlogger-ui
|}

Logger is a database engine built into a library for logging all kinds of events. It’s particularly powerful for logging messages (optionally with attachments), calls and network events.

===Notification UI===
{|cellspacing="0" border="1" width="70%"
|'''Name'''||rtcom-notification-ui
|-
|'''Purpose'''||Notification UI, plugin for the Hildon Status Menu.
|-
|'''Source Packages'''||rtcom-notification-ui
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used'''||libglib, libosso, libgtk2, libhildon1 (libhildon1, libhildondesktop1, libhildonmime), mce, libtelepathy-glib, libosso-abook, libebook, librtcom-telepathy-glib
|}

This is a Hildon Status menu plugin for RTCom related notifications.

===Presence UI===
{|cellspacing="0" border="1" width="70%"
|'''Name'''||rtcom-presence-ui
|-
|'''Purpose'''||Accounts presence UI.
|-
|'''Source Packages'''||rtcom-presence-ui
|-
|'''License'''||Nokia
|-
|'''Interfaces Used'''||libglib, libosso, libgtk2, libhildon1 (libhildon1, libhildondesktop1), libmcclient, maemo-launcher, liblocation, libnavigation, libcanberra, libosso-abook
|}

This is the presence user interface.

==Single-Sign-On (SSO)==

SSO subsystem is a separate subsystem providing credential storage and a client library for applications. This way, user is not requested to login or enter credentials as he’s navigating between different service types within single service provider. In case of wide ticket-based system like OpenID (reference) , user can even use the same credential between different service providers as long as service provider accepts tickets from external providers.

{|cellspacing="0" border="1" width="70%"
|'''Purpose'''||Provides Single-Sign-On functionality.
|-
|'''Responsibilities'''||Provides authentication services and tokens for applications.
|}

{|cellspacing="0" border="1" width="70%"
|'''Name'''||libsignon-glib
|-
|'''Purpose'''||GObject interface to SSO functionality.
|-
|'''Source Packages'''||signon
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used'''||libglib, libxml2
|-
|'''Interfaces Provided'''||libsignon-glib
|}

{|cellspacing="0" border="1" width="70%"
|'''Name'''||libsignonui
|-
|'''Purpose'''||UI elements of the SSO functionality.
|-
|'''Source Packages'''||signon
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used||'''libglib, libgtk2, libhildon1, libaccounts, libosso-rtcom-accounts, libsignon-glib
|-
|'''Interfaces Provided'''||libsignonui
|}

{|cellspacing="0" border="1" width="70%"
|'''Name'''||signond
|-
|'''Purpose'''||SSO daemon, handling credential storate and authentication.
|-
|'''Source Packages'''||signon
|-
|'''Licenses'''||Nokia
|-
|'''Interfaces Used'''||libglib, libxml2, libcurl (libcurl3-openssl), libssl (libcrypto)
|-
|'''Interfaces Provided'''||signond (ipc)
|}

SSO-subsystem consists of server, here called “signond” and application libraries libsignon-glib and libsignonui.
Server stores credentials in optionally encrypted database. It is running under different user id than applications. Application library accesses the storage over IPC mechanism.

==Protocol Stack==
Realtime communication framework connects to services using protocol plugins. Currently, XMPP/Jabber and SIP are the officially supported protocols. There’s also support for media extension of Jabber called Jingle.
As described earlier, each of the protocol plugins create abstraction of some protocol to a common DBUS protocol.

GoogleTalk uses Jingle protocol to handle voice streaming.

Standard Jabber communication always goes through persistent TCP connection to the server.
SIP protocol uses either UDP or TCP protocol for signaling. UDP is older and established method, while TCP is more recommended nowadays, mainly due to some particular message size and NAT traversal problems associated with UDP use. Together with SIP, standard RTP is always used for the media.

Documentation/Maemo 5 Developer Guide/Using Connectivity Components/Maemo Connectivity

2009-10-23T13:02:09Z

192.100.124.218: /* Bluetooth DBUS UI dialogs */

= Maemo Connectivity =

==Introduction==
The maemo connectivity subsystem is implemented by using known Linux conventions. It resides in the user space of Linux, and relies on the Linux kernel through standard C libraries. GPRS or WLAN is the main channel to the Internet. The Bluetooth software of maemo is based on BlueZ, which is known as the de-facto implementation of Bluetooth for Linux. D-Bus is used for internal application level message exchange.

Even though the connectivity device drivers are closely related to this subsystem, they are considered to be outside of the scope of this manual.

===Components of the maemo connectivity architecture===
'''Maemo connectivity UI''' - User Interface parts of the connectivity. This includes Control Panel applets and several different dialogs.

'''Maemo connectivity daemon (ICd)''' - [http://maemo.org/api_refs/5.0/beta/libconic/ LibConIC] API works together with [http://maemo.org/api_refs/5.0/beta/icd2/ ICd], handling all Internet Access Points (IAPs). IC daemon handles both WLAN and GPRS connections.

'''OBEX wrapper''' - Interface to OBEX services. The primary target user of this library is the OBEX gnome-vfs module.

'''OpenOBEX''' - Open source implementation of the Object Exchange (OBEX) protocol. For more information on OpenOBEX, visit http://triq.net/obex/

'''BlueZ Bluetooth stack''' - The de-facto implementation of Bluetooth for Linux. For more information on BlueZ, visit [http://www.bluez.org/ http://www.bluez.org]

'''[http://git.kernel.org/?p=bluetooth/bluez.git;a=tree;f=doc;hb=HEAD BlueZ D-Bus API]''' - BlueZ accepts commands via D-Bus.

'''WLAN connectivity daemon''' - The daemon controlling WLAN connections.

'''WLAN device driver''' - mac80211 from Linux and wl12xx driver implemented by Nokia, licensed under GPLv2.

===Internet Access Points (IAP)===
The central concept for maemo Internet connections is the Internet Access Point (IAP), which represents a logical Internet (IP) connection that the user defines. An IAP has a unique name, usually in form of UUID). Among other things, it defines the radio bearer (e.g. WLAN, GPRS), and usually also the data transfer speed, username, password, proxy server, and the corresponding access point in the Internet or the telephone number of the service provider's modem.

==Connectivity Subsystem ==
This section describes the system decomposition of the Connectivity subsystem. Maemo applications can open Internet connections by using the LibConIC API. The Internet Access subsystem take care of the connection to the phone, if necessary, by using the services of the Phone Access subsystem. If an application needs to gain access to the phone's files, the File selector consults the Phone Access subsystem.

In offline mode, none of the radios must be active. The Device System Management Entity (DSME) of maemo provides information about the transitions to and from the offline mode.

<div align="CENTER">

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | Connectivity UI
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Provides the UI for managing phone and Internet connections. Available as a Control Panel applet, and from the Status Bar.
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Displaying active connections with statistics
* Updating status indicators
* Providing dialogs for changing and disconnecting connections
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | (N/A)
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | Phone Access
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Provides connections to phones with different Bluetooth profiles
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Searching for phones and inquiring their services
* Keeping phone register
* Providing status of the phone connections for Connectivity UI
* Binding RFCOMM devices to Bluetooth services on the phone
* Providing easy access to OpenOBEX
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Number of clients not limited by maemo. However, some phones may not support more than one Bluetooth profile at a time.
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | Internet Access
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Provides Internet connections over different bearers.
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Providing means for configuration and management of IAP settings
* Providing API for Internet connections over different bearers (e.g. WLAN, GPRS)
* Providing status of Internet connections for Connectivity UI
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Number of clients not limited, but only one connection to the Internet can exist at any given time
|}

</div>

Phone and Internet connections are quite different by nature and behavior. These are introduced in more detail in the following sections.

===Phone Access ===
Phone Access is the subsystem handling connections to a cellular phone. It offers a search utility for finding potential phones and inquiring the services they can offer. This is based on the standard Bluetooth service discovery mechanism. Phone Access also keeps a record of phones that have connected to the device in GConf, and provides a list of them for the user to choose from. Phone Access relies on the Linux Bluetooth implementation called BlueZ. BlueZ offers the Berkeley socket interface to the HCI and to the L2CAP protocol for the user space applications.

In principle, any cellular phone supporting Bluetooth Service Discovery Protocol (SDP) and File Transfer Profile (FTP) can connect to maemo. However, different mobile phones implement varying levels of file transfer services and OBEX. Some products limit access to the Inbox (Object Push), whereas more sophisticated ones make the Gallery and the memory card available. The recent products support the OBEX Capability request for retrieving more specific information about the file system on the phone.

Maemo connects to a phone on an on-demand basis, such as when an application requires a connection. For example, when the Internet browser is about to open a URL, it requests Phone Access to establish a connection to the phone. This causes Phone Access to bind an RFCOMM device to the requested service on the phone. In a similar fashion, the File Selector can set up a file transfer connection to the phone using another RFCOMM device. After binding to a service, the application in question can open the local RFCOMM device. Normal file selector access is performed with GnomeVFS layer to get transparent access to phone in the same way as internal flash and MMC are accessed.

The Bluetooth SIM Access (SAP) profile is also needed in maemo to perform WLAN authentication using the EAP-SIM authentication method. In this case, the EAP component asks the BT sap component to get session keys from a GSM/UMTS phone.

<div align="CENTER"></div><div align="CENTER">

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | General Bluetooth UI
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | User interface for managing all paired BT devices
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Keeping a list of all paired devices (not only phones)
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | N/A
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | BT search
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Searches for available Bluetooth devices
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Bluetooth inquiry
* Checking on offline mode state
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | N/A
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | BT service discovery
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Checks if a found Bluetooth device is sufficient
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Bluetooth service discovery (SDP)
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Not limited (but used by Phone selection UI and Phone connection daemon only)
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | GW OBEX library
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Provides access to OpenOBEX library for the File selector (Gnome VFS) on a higher abstraction level than OpenOBEX itself supports
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Handling OBEX requests
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Not limited
|}

 

</div><div align="CENTER"></div>

Maemo Bluetooth also supports HID (keyboard) and OPP (object push file transfer) profiles.

===Internet Access ===
The Internet Access subsystem manages connections to the Internet over different bearers and is also responsible for the configuration and management of Internet Access Points. Internet Access provides applications with TCP/IP connections. They can be established in the following ways:

* WLAN connection to a wireless access point.
* Bluetooth connection through phone using Point-to-Point Protocol (PPP) and a cellular modem (in the phone).

For Bluetooth connections, AT commands are applied to establish a PPP link to the cellular modem and the connection to the Internet.

<div align="CENTER"></div><div align="CENTER">

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | IC daemon
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | IC daemon establishes Internet connections over different bearers.
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Controlling that only one Internet connection (one active IAP) can exist at any given time
* Using WLAN or GPRS connection daemon for getting a network device and getting the connection authenticated
* Starting IP level services like PPP and DHCP
* Providing statistics about the usage of IAPs to any application
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Has multiple clients and limits the connections to one at a time
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | Internet Connectivity GUI
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Has GUI applications for configuring Internet Access Points and WLAN settings.
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Providing the UI for configuring an IAP
* Providing the UI for WLAN settings
* Scanning for available WLAN networks (on request)
* Saving IAP and WLAN settings (excluding EAP settings) to GConf
* Opening up dialogs and displaying notifications
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | N/A
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | WLAN connection daemon
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Manages WLAN network connections
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Starting WLAN driver with the settings provided; stopping WLAN
* Requesting authentication when necessary
* Relaying WLAN IAP settings from IC daemon to WLAN drivers and authentication requests to EAP
* Relaying WLAN events from WLAN drivers
* Providing WLAN status information
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | Not limited
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | EAP UI
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | User interface for EAP authentication
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Invoking a dialog for an authentication password
* Showing authentication status
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | N/A
|}

 

{| border="1" cellpadding="3"
| width="100" align="LEFT" valign="TOP" | Name
| width="350" align="LEFT" valign="TOP" | EAP
|-
| width="100" align="LEFT" valign="TOP" | Purpose
| width="350" align="LEFT" valign="TOP" | Provides WLAN security excluding basic WEP settings, which are in Wireless Extensions
|-
| width="100" align="LEFT" valign="TOP" | Responsibilities and additional requirements
| width="350" align="LEFT" valign="TOP" |
* Taking care of the authentication process for the active IAP
* Delivering progress events to IC daemon
* As a special case, controlling the EAP-SIM authentication using the SIM Access Profile
* Providing authentication status
|-
| width="100" align="LEFT" valign="TOP" | Concurrent usage
| width="350" align="LEFT" valign="TOP" | N/A
|}

 

</div><div align="CENTER"></div>

==Internet Connectivity Daemon ==
This section describes how the Internet Connectivity daemon works internally. The following subsections explain the behavior and the decomposition of this component in detail, also covering the interfaces that this component realizes.

===Decomposition ===
If the ICd receives a request to activate or deactivate an IAP, the ICd activates the IAP or, if no IAP has been defined as the default, shows a uI requesting the user to choose one. Depending on the type of the IAP, the ICd uses the appropriate network type plug-in to activate or deactivate specific network interface.

The ICd tracks the applications requesting IAPs by recording their D-Bus base service names. This allows the ICd to detect situations where processes using an IAP have aborted or crashed.

Maemo version 3.0 introduced the automatic connection creation feature in the Internet Connectivity Daemon. In other words, the device tries to connect automatically to the saved IAPs, and keep connected as long as possible. With this feature, applications like e-mail and RSS reader are always up to date. The device is also always ready for online use, for example, incoming VoIP calls or IM chat. In earlier versions, the Internet connection was automatically closed if no application was using it or when the connection was idle for the period of time defined by the idle timeout configuration parameter.

When the device is not connected, it scans for saved IAPs and tries to connect automatically, taking into account the value defined by the search interval configuration parameter. The search interval can be 5, 10, 30 or 60 minutes; all other values are automatically mapped to "Never". This setup switches off the automatic connection feature. In this case, the device behaves just like the former versions: Connections are created only when applications require it.

Because each application keeps its data updated and provides the always-online feature, the ICd is only responsible for creating connections.

While writing an application making use of the ICd system, keep the following in mind:

* The application must always use the existing available connection.
* As in former versions, if the device is not connected but a connection is required by user interaction, the application must require connection creation using LibConIC API.
* Ensure that the user is aware of updates and can see the time when the data was last updated.
* Ensure that the application registers via LibConIC and listens to signals emitted by the ICd (Connection Created, Lost and Changed), and react as follows:
** '''Connection Created'''<nowiki>: Use the connection and update all data. </nowiki>
** '''Connection Lost'''<nowiki>: Go to an idle state silently and wait until a new connection is created. </nowiki>
** '''Connection Changed'''<nowiki>: Use the new connection. </nowiki>
* Ensure that automatic data updates run in background and silently:
** Avoid alarming the user with unnecessary banners or dialogs.
** Ensure that usernames and passwords are saved so that automatic updates can be performed without prompts.
** During and after updates, ensure that no failures display error notifications.
* The connectivity infrastructure must take care of error situations in a centralized way.

You can switch off the automatic connection creation feature by using offline mode. While in this mode, the configuration parameter for allowing WLAN in offline mode is checked. Depending on the state of this configuration parameter, WLAN IAPs are either enabled or disabled in the offline mode. Also other radios like Bluetooth are normally disabled in the offline mode.

=== WLAN ===
For connecting to a WLAN, the ICd needs to associate with the network as well as enable EAP authentication and the DHCP client as needed. Independently of whether an active IAP using WLAN exists, the requested WLAN network is first scanned to ensure that it is available. If the requested network is found and the current IAP is using WLAN, the current IAP is deactivated. WLAN is activated according to the following procedure:

* If the network requires EAP authentication, the EAP authentication procedure is started. While performing the EAP authentication, the EAP software may show GUI dialogs relating to the EAP authentication procedure. When EAP authentication is complete, the EAP software sets security keys for the WLAN network, resulting in state change messages from wlancond. The ICd receives these messages but ignores them and waits for the reply from EAP authentication instead. If the EAP authentication fails, the ICd aborts with a D-Bus error message.
* After the EAP process starts, the ICd instructs wlancond to associate with the WLAN network. Any static security settings relating to pre-shared security keys are also supplied at this point. If it cannot establish a connection to the WLAN network, the ICd aborts with an error.
* Because the DHCP client is a stand-alone program, start it by using exec if the WLAN IAP requires dynamic IP address acquisition. When the DHCP client has obtained an IP address, it configures IP-related parameters, and sends a D-Bus signal to the ICd. If it cannot obtain the IP address lease, the ICd times out, stops the DHCP client and aborts with a D-Bus error message.

==LibConIC Library ==
Internet Connectivity API (in shorter form: Libconic) is an API for applications to manage internet connections on Maemo devices. It was introduced in the first IT OS 2007 release, deprecating the old OSSO IC API (osso-ic-lib). OSSO IC API was conclusively removed in the IT OS 2008 release. For more information on libconic interfaces, see [http://maemo.org/api_refs/4.1/libconic-0.16/index.html Internet Connectivity API]

Libconic is high level and stable object-oriented API suitable for the following purposes:

* requesting Internet connection
* listening for Internet connection status events
* receiving statistics of Internet connection
* getting proxy settings for the current connection
* getting a list of user-saved connections (IAPs)

 
'''Application Requirements'''
Before applications can use the Libconic API, they must meet the following requirements:

# use non-blocking sockets
# have the system D-BUS running
# ''g_type_init()'' has to be called
# employ no threading support in the Libconic API

If the application is a standard Hildon application, almost all of these requirements are already fulfilled. LibOSSO context initialization connects the application to both session and system D-BUS buses, ''g_type_init()'' is called as a part of ''gtk_init()'', and probably no extra threads are used.

'''Non-Blocking Sockets'''
Blocking sockets cannot be used because that would also block incoming Connectivity events. Non-blocking sockets should be used in order to receive the events properly. For example, GLib IO Channels with the ''G_IO_FLAG_NONBLOCK'' flag provide non-blocking way to use sockets.

With threads, blocking sockets can be used, although Libconic API itself is not thread safe.

'''System D-BUS'''
Libconic API uses internally system D-BUS for delivering messages to the Connectivity components. Applications must be running normal D-BUS dispatch, watch and timeout monitoring before using the Libconic API. If the GLib mainloop is used, this can be accomplished with ''dbus_connection_setup_with_g_main()''.

N.B. Setting up LibOSSO context connects the application to required D-BUS.

'''GType'''
Libconic API is GObject-basedm, so in order to get the API working, you must initialize GLib's GType properly. To do that, use ''g_type_init()''.

'''No Multiple Threads'''
Libconic API is not thread-safe. If the applications have threads, use Libconic API only from the same context where GMainloop is running.

===Libconic Usage ===

==== Requesting for Connection ====
Libconic is an asynchronous connection API, which heavily relies on GObject signals. Basically this means that GMainloop must be iterated in order to successfully execute connection requests. After the application is set up, use a ''ConIcConnection'' object to request a connection:

<tt> gboolean success <nowiki>=</nowiki> FALSE<nowiki>;</nowiki>
''/* Create connection object */''
ConIcConnection <nowiki>*</nowiki>connection <nowiki>=</nowiki> '''con_ic_connection_new'''();
''/* Connect signal to receive connection events */''
'''g_signal_connect'''('''G_OBJECT'''(connection), "connection-event",
'''G_CALLBACK'''(my_connection_handler), NULL);
''/* Request connection and check for the result */''
success <nowiki>=</nowiki> '''con_ic_connection_connect'''(connection, CON_IC_CONNECT_FLAG_NONE);
'''if''' (!success) '''g_warning'''("Request for connection failed");</tt>

At this point, the application does not yet have an Internet connection. A successful return from ''con_ic_connection_connect()'' means only that the request was successfully dispatched to the Internet Connectivity daemon. When the daemon has a connection ready, the application receives an event (as an GObject signal) indicating that the device is connected. If the connection attempt fails, the application receives a disconnected event with an error describing the reason for the failure.

The connection handler (''my_connection_handler()'' function registered in the previous snippet) could look like this:

<tt>'''static''' void '''my_connection_handler'''(ConIcConnection <nowiki>*</nowiki>connection,
ConIcConnectionEvent <nowiki>*</nowiki>event,
gpointer user_data)
{
ConIcConnectionStatus status <nowiki>=</nowiki> '''con_ic_connection_event_get_status'''(event);
ConIcConnectionError error<nowiki>;</nowiki>
'''const''' gchar <nowiki>*</nowiki>iap_id <nowiki>=</nowiki> '''con_ic_event_get_iap_id'''('''CON_IC_EVENT'''(event));
'''const''' gchar <nowiki>*</nowiki>bearer <nowiki>=</nowiki> '''con_ic_event_get_bearer_type'''('''CON_IC_EVENT'''(event));
'''switch'''(status) {
'''case''' CON_IC_STATUS_CONNECTED<nowiki>:</nowiki>
'''g_debug'''("Hey, we are connected to IAP %s with bearer %s!", iap_id, bearer);
'''break'''<nowiki>;</nowiki>
'''case''' CON_IC_STATUS_DISCONNECTING<nowiki>:</nowiki>
'''g_debug'''("We are disconnecting...");
'''break'''<nowiki>;</nowiki>
'''case''' CON_IC_STATUS_DISCONNECTED<nowiki>:</nowiki>
'''g_debug'''("And we are disconnected. Let's see what went wrong...");
error <nowiki>=</nowiki> '''con_ic_connection_event_get_error'''(event);
'''switch'''(error) {
'''case''' CON_IC_CONNECTION_ERROR_NONE<nowiki>:</nowiki>
'''g_debug'''("Libconic thinks there was nothing wrong.");
'''break'''<nowiki>;</nowiki>
'''case''' CON_IC_CONNECTION_ERROR_INVALID_IAP<nowiki>:</nowiki>
'''g_debug'''("Invalid (non-existing?) IAP was requested.");
'''break'''<nowiki>;</nowiki>
'''case''' CON_IC_CONNECTION_ERROR_CONNECTION_FAILED<nowiki>:</nowiki>
'''g_debug'''("Connection just failed.");
'''break'''<nowiki>;</nowiki>
'''case''' CON_IC_CONNECTION_ERROR_USER_CANCELED<nowiki>:</nowiki>
'''g_debug'''("User canceled the connection attempt");
'''break'''<nowiki>;</nowiki>
}
'''break'''<nowiki>;</nowiki>
'''default'''<nowiki>:</nowiki>
'''g_debug'''("Unknown connection status received");
}
}</tt>

====Listening for Connection Events ====
Sometimes the application does not actively start connections but needs to detect if the device is online. The Libconic "automatic events" feature, enabled with "automatic-events" GObject property, can achieve this:

<tt> ''/* Create connection object */''
ConIcConnection <nowiki>*</nowiki>connection <nowiki>=</nowiki> '''con_ic_connection_new'''();
''/* Connect signal to receive connection events */''
'''g_signal_connect'''('''G_OBJECT'''(connection), "connection-event",
'''G_CALLBACK'''(my_connection_handler), NULL);
''/* Set automatic events */''
'''g_object_set'''('''G_OBJECT'''(connection), "automatic-events", TRUE, NULL);</tt>

When automatic events are turned on, the application receives connected and disconnected events for all Internet connection changes. In addition to this, the application receives an event for the initial connection status. If the device is disconnected, ''ConIcConnectionEvent'' with status ''CON_IC_STATUS_DISCONNECTED'' is emitted. This event has NULL IAP ID and bearer, because there is no IAP getting disconnected, but the event indicates that the device is offline.

N.B. The main loop must be reiterated in order to receive the event. If you need the connection status information synchronously, you can iterate the main loop yourself:

<tt>'''static''' void '''connection_info'''(ConIcConnection <nowiki>*</nowiki>connection,
ConIcConnectionEvent <nowiki>*</nowiki>event,
gpointer user_data)
{
ConIcConnectionStatus status <nowiki>=</nowiki> '''con_ic_connection_event_get_status'''(event);
ConIcConnectionStatus <nowiki>*</nowiki>status_ptr <nowiki>=</nowiki> (ConIcConnectionStatus<nowiki>*)</nowiki>user_data<nowiki>;</nowiki>
<nowiki>*</nowiki>status_ptr <nowiki>=</nowiki> status<nowiki>;</nowiki>
}
''/* ... */''
''/* Create connection object and set on automatic events (see previous snippet) ... */''
'''static''' ConIcConnectionStatus status <nowiki>=</nowiki> 0xFFFF<nowiki>;</nowiki>
ConIcConnection <nowiki>*</nowiki>connection <nowiki>=</nowiki> '''con_ic_connection_new'''();
'''g_signal_connect'''('''G_OBJECT'''(connection), "connection-event",
'''G_CALLBACK'''(connection_info), &status);
'''g_object_set'''('''G_OBJECT'''(Connection), "automatic-events", TRUE, NULL);
''/* Iterate main loop for the first connection event */''
'''while''' (status <nowiki>==</nowiki> 0xFFFF) '''g_main_context_iteration'''(NULL, TRUE);
'''if''' (status <nowiki>==</nowiki> CON_IC_STATUS_CONNECTED)
'''g_debug'''("We are connected!");
'''else'''
'''g_debug'''("We are not connected!");</tt>

==== Receiving Statistics of Connection ====
To receive statistics of the current Internet connection, use the ''con_ic_connection_statistics()'' function and the corresponding event handler. You can retrieve statistics for a specified IAP or just for the current default connection. Note that currently the Internet Connectivity daemon provides only one Internet connection at a time, so the best option is to leave IAP ID NULL.

<tt>'''static''' void '''connection_statistics'''(ConIcConnection <nowiki>*</nowiki>connection,
ConIcStatisticsEvent <nowiki>*</nowiki>event,
gpointer user_data)
{
'''g_debug'''("Here are all kind of nice statistics about the connection:");
'''g_debug'''("Time active: %u, signal strength: %u, received packets: %llu, "
"sent packets: %llu, received bytes: %llu, sent bytes: %llu",
'''con_ic_statistics_event_get_time_active'''(event),
'''con_ic_statistics_event_get_signal_strength'''(event),
'''con_ic_statistics_event_get_rx_packets'''(event),
'''con_ic_statistics_event_get_tx_packets'''(event),
'''con_ic_statistics_event_get_rx_bytes'''(event),
'''con_ic_statistics_event_get_tx_bytes'''(event));
}
''/* ... */''
''/* ConIcConnection object named "connection" has already been created */''
'''g_signal_connect'''('''G_OBJECT'''(connection), "statistics",
'''G_CALLBACK'''(connection_statistics), NULL);
'''if''' (!'''con_ic_connection_statistics'''(connection ,NULL))
'''g_warning'''("Requesting connection statistics failed!");</tt>

==== Getting Proxy Settings ====
Libconic allows you to set up Internet connection proxy settings for various protocols. The first step is to discover the current proxy mode by using the ''con_ic_connection_get_proxy_mode()'' function. Next, use the following functions to get the actual proxy settings:

* If proxy mode is CON_IC_PROXY_MODE_NONE, do not use any proxies.
* If proxy mode is CON_IC_PROXY_MODE_MANUAL, use the following functions to query proxy settings:
** con_ic_connection_get_proxy_host() to get the proxy host
** con_ic_connection_get_proxy_port() to get the proxy port
** con_ic_connection_get_proxy_ignore_hosts() to get a list of hosts for which the proxy should not be used.
* If proxy mode is CON_IC_PROXY_MODE_AUTO, use con_ic_connection_get_proxy_autoconfig_url() to get a proxy auto configuration URL.
** Use of auto configuration URL is explained in [http://en.wikipedia.org/wiki/Proxy_auto-config Wikipedia]

In this example, the "connection-event" handler is modified to print HTTP proxy settings when establishing connection:

<tt>'''static''' void '''my_connection_handler'''(ConIcConnection <nowiki>*</nowiki>connection,
ConIcConnectionEvent <nowiki>*</nowiki>event,
gpointer user_data)
{
ConIcConnectionStatus status <nowiki>=</nowiki> '''con_ic_connection_event_get_status'''(event);
GSList <nowiki>*</nowiki>ignore_hosts<nowiki>;</nowiki>

'''if''' (status <nowiki>==</nowiki> CON_IC_STATUS_CONNECTED) {
'''g_debug'''("We are connected! \
Let's see what kind of settings we have for HTTP proxy...");

''/* Do things based on specified proxy mode */''
'''switch''' ('''con_ic_connection_get_proxy_mode'''(connection)) {

'''case''' CON_IC_PROXY_MODE_NONE<nowiki>:</nowiki>
'''g_debug'''("No proxies defined, it is direct connection");
'''break'''<nowiki>;</nowiki>

'''case''' CON_IC_PROXY_MODE_MANUAL<nowiki>:</nowiki>
'''g_debug'''("HTTP proxy %s:%d in use",
'''con_ic_connection_get_proxy_host'''(connection, CON_IC_PROXY_PROTOCOL_HTTP),
'''con_ic_connection_get_proxy_port'''(connection, CON_IC_PROXY_PROTOCOL_HTTP));

'''g_debug'''("List of hosts, for which proxy should not be used:");
ignore_hosts <nowiki>=</nowiki> '''con_ic_connection_proxy_ignore_hosts'''(connection);
'''for''' (GSList <nowiki>*</nowiki>iter <nowiki>=</nowiki> ignore_hosts<nowiki>;</nowiki> iter <nowiki>!=</nowiki> NULL<nowiki>;</nowiki> iter <nowiki>=</nowiki> '''g_slist_next'''(iter))
{
'''g_debug'''("%s", (gchar <nowiki>*)</nowiki>iter->data);
'''g_free'''(iter->data);
}
'''g_slist_free'''(ignore_hosts);
'''break'''<nowiki>;</nowiki>

'''case''' CON_IC_PROXY_MODE_AUTO<nowiki>:</nowiki>
'''g_debug'''("Proxy auto-config URL %s should be used",
'''con_ic_connection_get_proxy_autoconfig_url'''(connection));
'''break'''<nowiki>;</nowiki>
}
}
}</tt>

Proxy functions also exist for each individual protocol (like ''con_ic_connection_get_proxy_ftp_host()''), but these functions are deprecated. Avoid them in newly-written code.

====Getting List of User-Saved Connections ====
To query all user-saved connections (IAPs), use the ''con_ic_connection_get_all_iaps()'' function. The function returns simply a singly linked list of ConIcIap objects:

<tt> ''/* ConIcConnection object named "connection" has already been created */''
GSList <nowiki>*</nowiki>saved_iaps <nowiki>=</nowiki> '''con_ic_connection_get_all_iaps'''(connection);
'''g_debug'''("The following connections have been saved by the user:");
'''for''' (GSList <nowiki>*</nowiki>iter <nowiki>=</nowiki> saved_iaps<nowiki>;</nowiki> iter <nowiki>!=</nowiki> NULL<nowiki>;</nowiki> iter <nowiki>=</nowiki> '''g_slist_next'''(iter)) {
''/* Get IAP object and print some information about it */''
ConIcIap <nowiki>*</nowiki>iap <nowiki>=</nowiki> (ConIcIap <nowiki>*)</nowiki>iter->data<nowiki>;</nowiki>
'''g_debug'''("Connection %s called '%s' using bearer %s",
'''con_ic_iap_get_id'''(iap), '''con_ic_iap_get_name'''(iap),
'''con_ic_iap_get_bearer_type'''(iap));
''/* We unref the IAP object as we are not going to use it anymore */''
'''g_object_unref'''(iap);
}
'''g_slist_free'''(saved_iaps);</tt>

==== Porting Application from OSSO IC API to Libconic ====
* If the application does not have GType, GLib or D-BUS configured, set them up:
<tt> DBusConnection <nowiki>*</nowiki>system_dbus<nowiki>;</nowiki>
GMainloop <nowiki>*</nowiki>main_loop<nowiki>;</nowiki>
'''g_type_init'''();
main_loop <nowiki>=</nowiki> '''g_main_loop_new'''(NULL, FALSE);
system_dbus <nowiki>=</nowiki> '''dbus_bus_get'''(DBUS_BUS_SYSTEM, NULL);
'''dbus_connection_setup_with_g_main'''(system_dbus, NULL);</tt>
* Include the correct header file:
<tt>''' #include''' <osso-ic.h>
<nowiki>===></nowiki>
''' #include''' <conic.h></tt>
* Set up ''ConIcConnection'' object and "connection-event" handler instead of ''osso_iap_cb_t'' callback:
<tt> '''static''' void '''my_connection_cb'''('''struct''' iap_event_t <nowiki>*</nowiki>event, void <nowiki>*</nowiki>arg)
{
''/* ... */''
}
''/* ... */''
'''osso_iap_cb'''(my_connection_cb);
<nowiki>===></nowiki>
'''static''' void '''my_connection_cb'''(ConIcConnection <nowiki>*</nowiki>connection,
ConIcConnectionEvent <nowiki>*</nowiki>event,
gpointer user_data)
{
''/* ... */''
}
''/* ... */''
ConIcConnection <nowiki>*</nowiki>connection <nowiki>=</nowiki> '''con_ic_connection_new'''();
'''g_signal_connect'''('''G_OBJECT'''(connection), "connection-event",
'''G_CALLBACK'''(my_connection_cb), app_data);</tt>
* Manage connections through ''ConIcConnection'' API instead of ''osso_iap_connect()'' and ''osso_iap_disconnect()''<nowiki>: </nowiki>
<tt> '''osso_iap_connect'''(OSSO_IAP_ANY, OSSO_IAP_REQUESTED_CONNECT, app_data);
'''osso_iap_disconnect'''(iap_name, app_data);
<nowiki>===></nowiki>
'''con_ic_connection_connect'''(connection, CON_IC_CONNECT_FLAG_NONE);
'''con_ic_connection_disconnect'''(connection);</tt>
* Request statistics with ''con_ic_connection_statistics()'' instead of ''osso_iap_get_statistics()''.
* List all available IAPs with ''con_ic_connection_get_all_iaps()'' instead of ''osso_iap_get_configured_iaps()''.
* Configure autoconf to use Libconic instead of OSSO IC API:
<tt> PKG_CHECK_MODULES(OSSOIC, osso-ic)
AC_SUBST(OSSOIC_CFLAGS)
AC_SUBST(OSSOIC_LIBS)
<nowiki>===></nowiki>
PKG_CHECK_MODULES(CONIC, conic)
AC_SUBST(CONIC_CFLAGS)
AC_SUBST(CONIC_LIBS)</tt>
* In debian/control file "Build-Depends" section, depend on libconic0-dev instead of osso-ic-dev.

==Bluetooth Libraries ==
This section explains how maemo Bluetooth libraries work internally. The following subsections explain the behavior and the decomposition of the Bluetooth library components in detail.

=== Libgwobex ===
Libgwobex provides access to libopenobex functionality by providing a helper/wrapper interface. Libopenobex is explained in detail in the following section.

The interface to libgwobex is available at [http://maemo.org/api_refs/4.1/osso-gwobex-0.60/index.html GW OBEX Library Documentation].

===Creating Connection ===
The connection with libgwobex is established using the gw_obex_setup_dev function, setting up the connection. gw-obex.h

<tt>'''<nowiki>#define</nowiki>''' OBEX_FTP_UUID \
"\xF9\xEC\x7B\xC4\x95\x3C\x11\xD2\x98\x4E\x52\x54\x00\xDC\x9E\x09"
'''<nowiki>#define</nowiki>''' OBEX_FTP_UUID_LEN 16

''/* ... */''

GwObex<nowiki>*</nowiki> '''gw_obex_setup_dev''' ('''const''' gchar <nowiki>*</nowiki> device, '''const''' gchar <nowiki>*</nowiki> uuid, gint uuid_len,
GMainContext <nowiki>*</nowiki> context, gint <nowiki>*</nowiki> error )</tt>

The following code snippet illustrates how to open a handle using gw_obex_setup_dev.

<tt>'''if''' (ctx->rfcomm_dev) {
'''if''' (ctx->use_ftp)
ctx->obex <nowiki>=</nowiki> '''gw_obex_setup_dev'''(ctx->rfcomm_dev,
OBEX_FTP_UUID, OBEX_FTP_UUID_LEN,
NULL, &err);
'''else'''
ctx->obex <nowiki>=</nowiki> '''gw_obex_setup_dev'''(ctx->rfcomm_dev, NULL,
0, NULL, &err);

'''if''' (ctx->obex <nowiki>==</nowiki> NULL)
'''printf'''("OBEX setup failed: %s\n", '''response_to_string'''(err));
}</tt>

In this example, ctx->rfcomm_dev points to a string containing the device node name (e.g. /dev/rfcomm0). ctx->use_ftp dictates whether to set up standard folder browsing services. If use_ftp is untrue, then INBOX is connected.

===Closing Connection ===
To close a gwobex connection, use the following function: gw-obex.h

<tt>void '''gw_obex_close''' ( GwObex <nowiki>*</nowiki> ctx );</tt>

The following code demonstrates this usage.

<tt>'''if''' (ctx->obex) {
'''gw_obex_close'''(ctx->obex);
ctx->obex <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
}</tt>

If ctx->obex is not NULL, it is simply passed as an argument to gw_obex_close().

===Using Connection ===
The libgwobex library provides general file handling functionality, including reading directory structure, browsing in different folders and getting files.

To read entries from an opened directory, use the following function: gw-obex.h

<tt>gboolean '''gw_obex_read_dir''' (GwObex <nowiki>*</nowiki> ctx,
'''const''' gchar <nowiki>*</nowiki> dir,
gchar <nowiki>**</nowiki> buf,
gint <nowiki>*</nowiki> buf_size,
gint <nowiki>*</nowiki> error );</tt>

gw_obex_read_dir reads an entry from the selected folder and returns the result in the buf argument given to the function.

<tt>gboolean ret<nowiki>;</nowiki>
''/* ... */''
ret <nowiki>=</nowiki> '''gw_obex_read_dir'''(ctx->obex, dir, buf, buf_size, err);</tt>

This reads an entry from the directory dir (char *) and returns it in buf (char **).

To change the current directory, use the following function: gw-obex.h

<tt>gboolean '''gw_obex_chdir''' (GwObex <nowiki>*</nowiki> ctx, '''const''' gchar <nowiki>*</nowiki> dir, gint <nowiki>*</nowiki> error );</tt>

which changes the directory of the FTP connection. Below is a code example using this function.

<tt>''/* Ignore parent dir pointers */''
'''if''' ('''g_str_equal'''(name, ".."))
'''return''' TRUE<nowiki>;</nowiki>

'''if''' (!'''gw_obex_chdir'''(ctx->obex, name, err)) {
'''printf'''("Could not chdir to %s\n", name);
'''return''' FALSE<nowiki>;</nowiki>
}</tt>

To retrieve files over the OBEX connection, use the gw_obex_get_file function: gw-obex.h

<tt>gboolean '''gw_obex_get_file''' (GwObex <nowiki>*</nowiki> ctx,
'''const''' gchar <nowiki>*</nowiki> local,
'''const''' gchar <nowiki>*</nowiki> remote,
'''const''' gchar <nowiki>*</nowiki> type,
gint <nowiki>*</nowiki> error);
</tt>

gw_obex_get_file uses the ctx context for retrieving the remote file to local file.

<tt>gboolean ret<nowiki>;</nowiki>
ret <nowiki>=</nowiki> '''gw_obex_get_file'''(ctx->obex, name, name, err);</tt>

Using the libwobex wrapper directly allows you to perform many more functions. For more information, see the [hhttp://maemo.org/api_refs/5.0/beta/osso-gwobex/ API document].

===Libopenobex ===
The LibOpenOBEX library implements a generic OBEX Session Protocol, but not the OBEX Application Framework. OBEX is a protocol designed to allow data interchanging between different kinds of connections (e.g. Bluetooth, IrDA). For more information on the OBEX protocol, see [http://www.irda.org/ http://www.irda.org]<nowiki>; select the Developer->Specifications category. OBEX resembles the HTTP protocol, expect for a few differences: </nowiki>

* Transports: While HTTP is normally layered above a TCP/IP connection, OBEX is usually transported over IrLAP/IrLMP/Tiny TP (on IrDA) or over Baseband/Link Manager/L2CAP/RFCOMM (on Bluetooth).
* Binary transmissions: OBEX communicates using binary transmissions, as HTTP is transmitted in a human-readable XML-based format.
* Session support: HTTP is stateless, while OBEX maintains the connection.

For more information on OBEX, see the summary available at http://en.wikipedia.org/wiki/OBEX.

For libopenobex code samples, see http://openobex.triq.net/downloads<nowiki>; the samples are in the example apps package. </nowiki>

===Using BlueZ D-Bus API ===
The BlueZ system exports a D-Bus API that can be employed instead of OSSO Bluetooth tools. See the following documents:

* [http://git.kernel.org/?p=bluetooth/bluez.git;a=tree;f=doc;hb=HEAD BlueZ D-Bus API documentation]

==Connectivity UI ==

===UI Components ===
Connectivity UI contains various dialogs and other components used to control the connectivity. The different UI parts are:

* Connectivity UI
* Connectivity dialogs
* Status bar applets
* Control panel applet
* Bluetooth UIs

The connectivity dialogs are invoked by D-Bus method calls, so for example the ICd is using these D-Bus method calls for showing dialogs when they are needed. The next section specifies the D-Bus API of maemo connectivity UI.

===D-Bus Connectivity UI Interface ===
If the user must provide information about the IAP that the system is about to connect to, you can use the following method:

<div class="graybox">

Service: com.nokia.icd_ui
Interfaces: com.nokia.icd_ui
Object paths: /com/nokia/icd_ui

</div>

The Internet Connectivity UIs implement the following D-Bus API used by the ICd and EAP.

<div class="graybox">

Method: show_conn_dlg
Parameters: 1. boolean When TRUE the dialog is requested because
there were no saved connections (i.e. auto
connect was tried before invoking the dialog)
Return parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown
Description: Shows the Connect Dialog where the user can choose an IAP.

</div>

<div class="graybox">

Method: show_disconnect_dlg
Parameters: none

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows the disconnect dialog.

</div>

<div class="graybox">

Method: show_retry_dlg
Parameters: 1. string Bluetooth address of the device used with SAP
2. string Name of the connection attempt error which
selects the retry dialog type.

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows the retry dialog.

</div>

<div class="graybox">

Method: show_change_dlg
Parameters: 1. string Name of the currently active IAP
2. string Name of the IAP to be activated

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows the Change IAP Dialog

</div>

<div class="graybox">

Method: show_passwd_dlg
Parameters: 1. string Username supplied by ICd
2. string Password supplied by ICd
3. string Name of the IAP

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows the username/password dialog.

</div>

<div class="graybox">

Method: show_gtc_dlg
Parameters: 1. string GTC challenge string

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows EAP GTC challenge dialog.

</div>

<div class="graybox">

Method: show_mschap_change_dlg
Parameters: 1. string Supplied username
2. string Old password that is to be changed
3. string Name of the IAP

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows EAP MSCHAPv2 change password dialog.

</div>

<div class="graybox">

Method: show_private_key_passwd_dlg
Parameters: 1. byte array Certificate ID

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows EAP private key password dialog

</div>

<div class="graybox">

Method: show_server_cert_dlg
Parameters: 1. string Certificate name
2. string Certificate serial
3. boolean TRUE if certificate is expired, FALSE otherwise
4. boolean TRUE if root CA is unknown or self-signed
certificate, FALSE otherwise

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows server certificate error and expiration dialogs.
If both boolean arguments are false, the error dialog is
shown. If either or both boolean arguments are TRUE, the
expiration dialog is shown instead.

</div>

<div class="graybox">

Method: strong_bt_req
Parameters: 1. string Bluetooth address of the device to pair with
2. boolean TRUE if strong authentication enabled, FALSE
if strong authentication is disabled

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Requests strong (16 digit) BT PIN dialog for a BT device

</div>

<div class="graybox">

Method: show_sim_pin_dlg
Parameters: 1. string Bluetooth address of the device used with SAP
2. boolean TRUE if PIN was incorrect and retry dialog
should be displayed before asking PIN. FALSE
if this is the first PIN request.

Return Parameters: none
Errors: com.nokia.icd_ui.error.flight_mode:
Flight mode enabled, dialog not shown

Description: Shows SIM PIN dialog

</div>

The code example for the application to show the connect dialog using show_conn_dlg is following. Note the use of the macro.

<tt>'''<nowiki>#include</nowiki>''' <osso-ic-ui-dbus.h>
''/* ... */''
''/* in our code somewhere, where we need the Connect Dialog*/''
DBusMessage <nowiki>*</nowiki>uimsg<nowiki>;</nowiki>
''/* construct the message for Connect Dialog request*/''
uimsg <nowiki>=</nowiki>
'''dbus_message_new_method_call'''(ICD_UI_DBUS_SERVICE,
ICD_UI_DBUS_PATH,
ICD_UI_DBUS_INTERFACE,
''/*macro for show_conn_dlg */''
ICD_UI_SHOW_CONNDLG_REQ);
''/* send the message */''
reply <nowiki>=</nowiki>
'''dbus_connection_send_with_reply_and_block'''(connection,
uimsg,
reply_timeout,
&error);
'''if''' (reply <nowiki>==</nowiki> NULL) {
'''DLOG_ERR'''("Failed to show connect dialog: %s", uierror.message);
'''dbus_error_free'''(&uierror);
}
'''dbus_message_unref'''(uimsg);
'''dbus_message_unref'''(reply);
''/* ... */''</tt>

The signals emitted from com.nokia.icd_ui interface are listed below.

<div class="graybox">

Signal: disconnect
Parameters: 1. boolean TRUE if "disconnect" pressed, FALSE if "cancel"

Description: Signal emitted from UI when disconnect dialog has been closed.

</div>

<div class="graybox">

Signal: retry
Parameters: 1. string The IAP that is to be retried
2. boolean TRUE if "retry" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the retry dialog has been closed.

</div>

 

<div class="graybox">

Signal: change
Parameters: 1. string Old IAP to change from
2. string New IAP to change to
3. boolean Change to the new IAP If TRUE, keep old if FALSE

Description: Signal emitted from UI when change connection dialog has
been closed.

</div>

<div class="graybox">

Signal: passwd
Parameters: 1. string Username supplied or modified by the user
2. string Password supplied or modified by the user
3. string IAP name
4. boolean TRUE if "ok" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the username/password dialog has
been closed

</div>

<div class="graybox">

Signal: gtc_response
Parameters: 1. string Response to the given challenge or empty string
if cancelled
2. boolean TRUE if "ok" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the EAP GTC challenge dialog has
been closed.

</div>

<div class="graybox">

Signal: mschap_change
Parameters: 1. string Supplied username
2. string The new password or empty string if cancelled
3. string IAP name
4. boolean TRUE if "ok" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the MSCHAPv2 password has been
changed

</div>

<div class="graybox">

Signal: private_key_passwd
Parameters: 1. byte array Certificate ID
2. string Password for the private key or empty string if none
3. boolean TRUE if "ok" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the private key password dialog
has been closed

</div>

<div class="graybox">

Signal: server_cert
Parameters: 1. boolean TRUE if strong PIN entered, FALSE if strong
PIN dialog was canceled

Description: Signal emitted from UI when the server certificate error
dialog has been closed

</div>

 

<div class="graybox">

Signal: strong_bt
Parameters: 1. boolean TRUE if strong PIN entered, FALSE if strong
PIN dialog was cancelled

Description: Signal emitted from UI when the strong (16 digit) BT PIN
has been entered

</div>

<div class="graybox">

Signal: sim_pin
Parameters: 1. string SIM PIN code or empty string if cancelled
2. boolean TRUE if "ok" pressed, FALSE if "cancel"

Description: Signal emitted from UI when the SIM PIN has been entered.

</div>

===Bluetooth DBUS UI dialogs ===

conbtdialogs-dbus.h

<tt>''/** ''
'' Example of use (command line):''
'' ''
'' dbus-send --system --print-reply \''
'' --dest='com.nokia.icd_ui' /com/nokia/bt_ui \''
'' com.nokia.bt_ui.show_send_file_dlg \''
'' array:string:''file:///home/user/MyDocs/.documents/testing.txt
'' ''
'' dbus-send --system --print-reply \''
'' --dest=com.nokia.bt_ui /com/nokia/bt_ui ''
'' com.nokia.bt_ui.show_search_dlg \''
'' string: string: array:string: string:''
''<nowiki>*/</nowiki>''

'''<nowiki>#ifndef</nowiki>''' CONBTDIALOGS_DBUS_H
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_DBUS_H

'''<nowiki>#ifdef</nowiki>''' __cplusplus
'''extern''' "C" {
'''<nowiki>#endif</nowiki>'''

''/** Conbtdialogs service, resides in system dbus */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_DBUS_SERVICE "com.nokia.bt_ui"
''/** Conbtdialogs interface */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_DBUS_INTERFACE "com.nokia.bt_ui"
''/** Conbtdialogs path */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_DBUS_PATH "/com/nokia/bt_ui"

''/** ''
'' Show send file dialog''
'' ''
'' Arguments:''
'' ''
'' uris: DBUS_TYPE_ARRAY Array of strings representing the URIs of the''
'' files to send.''
'' ''
'' Returns:''
'' ''
'' DBUS_TYPE_BOOLEAN TRUE, if dialog was shown successfully.''
'' */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_SEND_FILE_REQ "show_send_file_dlg"

''/** ''
'' File sending result signal''
'' ''
'' Arguments:''
'' ''
'' success: DBUS_TYPE_BOOLEAN TRUE, if all files were sent successfully or''
'' FALSE, if error occurred or sending was ''
'' canceled.''
'' */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_SEND_FILE_SIG "send_file"

''/** ''
'' Show BT device search dialog''
'' ''
'' Arguments:''
'' ''
'' major_class: DBUS_TYPE_STRING To set filtering based on major_class or''
'' "". Possible major class values are:''
'' ''
'' "miscellaneous", "computer", "phone", ''
'' "access point", "audio/video", ''
'' "peripheral", "imaging", "wearable",''
'' "toy" and "uncategorized".''
'' ''
'' minor_class: DBUS_TYPE_STRING To set filtering based on minor_class or "".''
'' Possible minor class values are:''
'' ''
'' - Minor classes for "computer": ''
'' "uncategorized", "desktop", "server",''
'' "laptop", "handheld", "palm", "wearable"''

'' - Minor classes for "phone": "uncategorized",''
'' "cellular", "cordless", "smart phone",''
'' "modem", "isdn"''
'' ''
'' service_classes: DBUS_TYPE_ARRAY To set filtering based on service classes.''
'' Supported classes include "positioning", ''
'' "networking", "rendering", "capturing",''
'' "object transfer", "audio", "telephony", ''
'' "information". Can be empty list, when no''
'' service class filtering is performed.''
'' ''
'' bonding: DBUS_TYPE_STRING Bonding mode for found and selected device:''
'' ''
'' "require" for requiring a bonding from a''
'' selected device (i.e. bond device if it has not''
'' been bonded before). ''
'' ''
'' "force" to always bond (i.e. device will be''
'' bonded even if bonded before).''
'' ''
'' Any other string will allow to search and''
'' select device without bonding it.''
'' ''
'' Returns:''
'' ''
'' DBUS_TYPE_BOOLEAN TRUE, if dialog was shown successfully.''
'' */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_SEARCH_REQ "show_search_dlg"

''/** ''
'' Bluetooth search result signal''
'' ''
'' Arguments:''
'' ''
'' address: DBUS_TYPE_STRING Bluetooth address of the selected device, or ""''
'' if search dialog was cancelled.''
'' ''
'' name: DBUS_TYPE_STRING Name of the device.''
'' ''
'' icon: DBUS_TYPE_STRING Logical name for the icon describing the ''
'' device.''
'' ''
'' major_class: DBUS_TYPE_STRING Major class of the device.''
'' ''
'' minor_class: DBUS_TYPE_STRING Minor class of the device.''
'' ''
'' trusted: DBUS_TYPE_BOOLEAN Defines whether the device is marked as a trusted device.''
'' ''
'' services: DBUS_TYPE_ARRAY List of strings describing the service classes''
'' and SDP-based services provided by the device.''
'' */''
'''<nowiki>#define</nowiki>''' CONBTDIALOGS_SEARCH_SIG "search_result"
</tt>

 

<tt>''/**''
'' Bluetooth UI Library for maemo''

'' Copyright (C) 2006 Nokia. All rights reserved.''
'' ''
'' This sample demonstrates the use of conbtdialogs API and especially ''
'' send_file function. Compile the program with conbtdialogs and dbus:''
'' ''
'' gcc -Wall `pkg-config -libs -cflags dbus-glib-1 conbtdialogs` \''
''-o send_file conbtdialogs_send_file.c''
'' ''
'' Run with list of URLS:''
'' ''
'' ./send_file ''file:///home/user/MyDocs/.sounds/Everyday.mp3
''<nowiki>*/</nowiki>''

'''<nowiki>#define</nowiki>''' DBUS_API_SUBJECT_TO_CHANGE

'''<nowiki>#include</nowiki>''' <glib.h>
'''<nowiki>#include</nowiki>''' <conbtdialogs-dbus.h>
'''<nowiki>#include</nowiki>''' <dbus/dbus.h>
'''<nowiki>#include</nowiki>''' <dbus/dbus-glib.h>

DBusGConnection <nowiki>*</nowiki>connection <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
GMainLoop <nowiki>*</nowiki>mainloop <nowiki>=</nowiki> NULL<nowiki>;</nowiki>

'''static''' gboolean '''initialize'''(void)
{
GError <nowiki>*</nowiki>error <nowiki>=</nowiki> NULL<nowiki>;</nowiki>

'''g_type_init''' ();

''/* Create main loop */''
mainloop <nowiki>=</nowiki> '''g_main_loop_new'''(NULL, TRUE);
'''if''' ( mainloop <nowiki>==</nowiki> NULL ) '''return''' FALSE<nowiki>;</nowiki>

''/* Create DBUS connection */''
connection <nowiki>=</nowiki> '''dbus_g_bus_get'''(DBUS_BUS_SYSTEM, &error);

'''if''' (connection <nowiki>==</nowiki> NULL )
{
'''g_print''' ("Error: %s\n", error->message);
'''g_clear_error''' (&error);
'''return''' FALSE<nowiki>;</nowiki>
}

'''return''' TRUE<nowiki>;</nowiki>
}

'''static''' gboolean '''uninitialize'''(void)
{
''/* Quit main loop and unref it */''
'''if''' (mainloop <nowiki>!=</nowiki> NULL)
{
'''g_main_loop_quit'''(mainloop);
'''g_main_loop_unref'''(mainloop);
}

'''return''' TRUE<nowiki>;</nowiki>
}

'''static''' DBusHandlerResult '''file_sent_signal''' ( DBusConnection <nowiki>*</nowiki>connection,
DBusMessage <nowiki>*</nowiki>message,
void <nowiki>*</nowiki>data )
{
gboolean success <nowiki>=</nowiki> FALSE<nowiki>;</nowiki>

''/* check signal */''
'''if''' (!'''dbus_message_is_signal'''(message,
CONBTDIALOGS_DBUS_INTERFACE,
CONBTDIALOGS_SEND_FILE_SIG))
'''return''' DBUS_HANDLER_RESULT_NOT_YET_HANDLED<nowiki>;</nowiki>

''/* get args */''
'''if''' ( <nowiki>!</nowiki>'''dbus_message_get_args''' ( message, NULL,
DBUS_TYPE_BOOLEAN, &success,
DBUS_TYPE_INVALID ) )
'''return''' DBUS_HANDLER_RESULT_NOT_YET_HANDLED<nowiki>;</nowiki>

''/* print if file sending was success or failure */''
'''g_print''' ( "File sending was a " );

'''if''' (success) '''g_print'''("success\n"); '''else''' '''g_print'''("failure\n");
'''dbus_connection_close'''(connection);
'''uninitialize'''();

'''return''' DBUS_HANDLER_RESULT_HANDLED<nowiki>;</nowiki>
}

gint '''main'''(gint argc, gchar <nowiki>**</nowiki>argv)
{
GError <nowiki>*</nowiki>error <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
gchar <nowiki>**</nowiki>files <nowiki>=</nowiki> NULL<nowiki>;</nowiki>
gint idx <nowiki>=</nowiki> 0<nowiki>;</nowiki>
DBusGProxy <nowiki>*</nowiki>proxy<nowiki>;</nowiki>
DBusConnection <nowiki>*</nowiki>sys_conn<nowiki>;</nowiki>
gchar <nowiki>*</nowiki>filter_string <nowiki>=</nowiki> NULL<nowiki>;</nowiki>

'''if''' (argc < 2) '''return''' 1<nowiki>;</nowiki>

'''if''' ('''initialize'''() <nowiki>==</nowiki> FALSE) {
'''uninitialize'''();
'''return''' 1<nowiki>;</nowiki>
}

''/* Copy urls to GLib compatible char array */''
files <nowiki>=</nowiki> '''g_new0'''(gchar<nowiki>*,</nowiki> argc);

'''for''' (idx <nowiki>=</nowiki> 1<nowiki>;</nowiki> idx < argc<nowiki>;</nowiki> idx++)
files[idx-1] <nowiki>=</nowiki> '''g_strdup'''(argv[idx]);

files[argc-1] <nowiki>=</nowiki> NULL<nowiki>;</nowiki>

''/* Open connection for btdialogs service */''
proxy <nowiki>=</nowiki> '''dbus_g_proxy_new_for_name'''(connection,
CONBTDIALOGS_DBUS_SERVICE,
CONBTDIALOGS_DBUS_PATH,
CONBTDIALOGS_DBUS_INTERFACE);

''/* Send send file request to btdialogs service */''
'''if''' (!'''dbus_g_proxy_call'''(proxy, CONBTDIALOGS_SEND_FILE_REQ,
&error,
G_TYPE_STRV, files, G_TYPE_INVALID,
G_TYPE_INVALID))
{
'''g_print'''("Error: %s\n", error->message);
'''g_clear_error'''(&error);
'''g_strfreev''' (files);
'''g_object_unref'''('''G_OBJECT'''(proxy));
'''uninitialize'''();
'''return''' 1<nowiki>;</nowiki>
}
'''g_strfreev''' (files);
files <nowiki>=</nowiki> NULL<nowiki>;</nowiki>

'''g_object_unref'''('''G_OBJECT'''(proxy));

''/* Now wait for file sent signal, use low level bindings as glib ''
'' bindings require signal marshaller registered */''
sys_conn <nowiki>=</nowiki> '''dbus_bus_get'''(DBUS_BUS_SYSTEM, NULL);
'''g_assert'''('''dbus_connection_add_filter'''(sys_conn,
file_sent_signal,
NULL,
NULL ));
filter_string <nowiki>=</nowiki>
'''g_strdup_printf''' ("type='signal',interface='%s'", CONBTDIALOGS_DBUS_INTERFACE);

'''dbus_bus_add_match'''(sys_conn, filter_string, NULL);
'''dbus_connection_unref'''(sys_conn);

''/* Run mainloop */''
'''g_main_loop_run'''(mainloop);

'''return''' 0<nowiki>;</nowiki>
}</tt>

Maemo Summit 2009

2009-10-19T07:40:00Z

192.100.124.218: /* Friday, October 9 */

<div style="font-weight:bold;">October 9-10-11, 2009- [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] - Amsterdam</div>
[[Image:Westergas.png‎]]

== Conference archive ==
Videos, slides and other materials related to the sessions. Feel free to update your own.

=== Thursday, October 8 ===

17:00 - 19:00 Registration at the Community Room (Zuiveringshal Oost). '''Early registrations encouraged to avoid queues and stress on Friday morning!'''

19:00 - 00:00 The official get together on Thursday will be [http://www.indewildeman.nl/indexe.html In de Wildeman], a beer house ([http://maps.google.nl/maps?f=q&source=s_q&hl=en&geocode=&q=Kolksteeg+3+1012+PT+Amsterdam&sll=52.377171,4.897242&sspn=0.005803,0.016512&ie=UTF8&hq=&hnear=Kolksteeg+3,+1012+Amsterdam,+North+Holland&t=h&z=16 Map]).

=== [[/Schedule/Day 1 | Friday, October 9]] ===

9:00 Registration at the Community Room (Zuiveringshal Oost). '''Come early: you won't get to the conference without your badge.'''

10:00 '''Programme starts at N900 (Transformatorhuis)'''

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Maemo_5_and_the_N900 Maemo 5 and the Nokia N900] by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia [http://www.slideshare.net/peterschneider/maemo-and-the-nokia-n900 (slides)]

11:00 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Changing_PC_.26_Mobile_Landscape.3B_Why_Linux_will_play_a_Critical_Role Changing PC & Mobile Landscape; Why Linux will play a Critical Role]''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Nokia_Nseries_Devices_on_Maemo Nokia Nseries Devices on Maemo]''' by Jose-Luis Martinez Merino, VP, Marketing @ Nokia [http://www.slideshare.net/peterschneider/nokia-nseries-and-maemo-6 (slides)]

12:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Harmattan_Highlights_-_Developer_Opportunities Harmattan Highlights - Developer Opportunities]''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia [http://www.slideshare.net/peterschneider/maemo-5-developer-offering (Maemo 5 slides)] - [http://www.slideshare.net/peterschneider/maemo-6-technology-highlights (Maemo 6 slides)]

13:00 '''Lunch - Maemo Expo opens'''

14:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Why_the_Maemo_Community_matters_to_Nokia Why the Maemo Community matters to Nokia]''' - Alan "[http://maemo.org/profile/view/qole/ qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! N900 - ''chair: John Loughney''
! N810 - ''chair: Anthony Fabbricino''
! N800 - ''chair: Quim Gil''
|-

|-
| 15:00 - 15:25
| rowspan="2" | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#UX_panel UX Panel]'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| '''UI design of Maemo 5 apps'''
''Annu-Maaria Nivala, UX team, Digia'' [http://www.slideshare.net/annumaaria/ui-design-of-maemo-5-apps-digia (slides)]
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Cross-platform_with_Qt_-_live Cross-platform with Qt - live]'''
''Ariya Hidayat, Software Engineer, Nokia''
|-
| 15:30 - 15:55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developing_widgets_on_Maemo_5_-_showcase_Foreca_Weather Developing widgets on Maemo 5 - showcase Foreca Weather]'''
''Juha Järvi, Software Designer, Foreca''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Mer_-_how_the_community_innovates Mer - how the community innovates]'''
''Carsten Munk, Lead Developer, Mer project'' [http://www.slideshare.net/carstenmunk/mer-how-the-community-innovates (slides)]
|-
| 16.00 - 16.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Firefox_on_Maemo Firefox on Maemo]'''
''Stuart Parmenter, Director of Engineering, Mozilla''

| '''Developing apps with Qt for Maemo5'''
''Kate Alhola, Forum Nokia, Chief Guru on Maemo
| | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Your_foundation_for_open-source_innovation:_TI.E2.80.99s_OMAP_processor-based_Zoom_platform Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform]'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Present_and_future_of_Maemo_digital_marketing Present andd future of Maemo digital marketing]'''
''Isko Salminen, Production Manager, Activeark & Jussi Mäkinen, Maemo Marketing, Nokia'''
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Feedservice and plug-ins development in Maemo 5'''
''Mikko Levonmaa, Ixonos''
|-
| 17.00 - 17.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Biz_apps_on_Maemo Biz apps on Maemo]'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''[http://www.slideshare.net/jtukkine/maemo-6-harmattan-architecture-overview Harmattan Architecture Overview]'''
''Juha Tukkinen, Principal Engineer, Maemo Devices, Nokia''
|-
| 17.30 - 18.00
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Skype_on_Maemo Skype on Maemo]'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developer_Support_for_Maemo_by_Forum_Nokia Developer Support for Maemo by Forum Nokia]'''
''Matt Collins, Director, Forum Nokia Marketing''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Porting_an_OpenGL_game_to_GL_ES Porting an OpenGL game to GL ES]'''
''Oliver Mcfadden, Software Engineer, Nokia''
|-
|}

20:00 '''Maemo Party in FlexBar''' DJ's [http://valeriecherie.blogspot.com/2008/02/from-britain-with-love.html Russ Chimes] & [http://www.trashmenagerie.com/mixes/2008/04/01/grums-nllr-mixtape/ Grum] (check the mixtapes!) visuals by [http://www.xploitec.org/blog/?page_id=103 Xploitec VJ's]. coordinated by Jussi Mäkinen. It's a public bar and the doors are open to anybody. Our ''program'' will go until 23h or so, but the bar is open until really late with good music. Special cocktail hour sponsored by the lovely Skype people. Don't forget the Saturday schedule, though. :)

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="4" align="center" | '''Welcome to Community days''' ''Maemo Community Council'' ([http://www.youtube.com/watch?v=6Mm-OS__8V0 Video])
|-
| 10.15 - 10:45
| colspan="4" align="center" | '''Keynote: Ton Roosendaal, the Blender Foundation'''
|-
| 10.45 - 11:00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 2#Designing_UI_for_Maemo_5 | '''Designing UI for Maemo 5''']] 
''Mox Soini'' ([http://www.slideshare.net/moximillian/soini-designing-ui-for-maemo-5 Slides])
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa'' ([http://www.slideshare.net/guestb404461/pyqt-application-development-on-maemo Slides], [http://web.atombiztos.hu/pyqt_on_maemo.zip .odp with demo videos])
|rowspan="2" | [[/Day 2#Getting_started_session | '''Getting started session''']] ''Daniel Wilms and others''
| ------
|-
| 11.30 - 11.55
| [[/Day 2#Personalizing_your_Maemo_5_device | '''Personalizing your Maemo 5 device''']] ''Hartti Suomela''
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| ------
|-
| 12.00 - 12.25
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day_2#Introducing_the_Harmattan_UI_framework | '''Introducing the Harmattan UI framework''']] 
''Tomas Junnonen''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
| rowspan="2" | [[/Day 2#Extras.2Fautobuilder.2Finterfaces_round-table | '''Extras/autobuilder/interfaces round-table''']]
|-
| 12.30 - 12.55
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster'' 
[http://www.slideshare.net/miahfost/packaging-for-the-maemo-platform (slides)]
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Feedhandler_-_Integrating_RSS_newsreaders_with_the_browser | '''Feedhandler - Integrating RSS newsreaders with the browser''']] - ''Thomas Perl''
# [[/Lightning talks#python-mafw:_MAFW_framework_for_Python_developers | '''python-mafw: MAFW framework for Python developers''']] - ''Andrea Grandi'' - [http://www.slideshare.net/andy80/pythonmafw-intoduction-at-maemo-summit-2009 (Slides)]
# [[/Lightning talks#DVCS.3F_git.3F_-_How_does_that_work_then.3F | '''DVCS? git? - How does that work then?''']] - ''David Greaves'' - [http://www.slideshare.net/mrlbt/git-how-does-that-work-then (Slides)]
# [[/Lightning_talks#BlueMaemo_-_Bluetooth_HID_mouse_.26_keyboard_for_Maemo | '''BlueMaemo - Bluetooth HID mouse & keyboard for Maemo''']] - ''Valério Valério'' [http://www.slideshare.net/VDVsx/bluemaemo-bluetooth-hid-mouse-keyboard-for-maemo (Slides)]
# [[/Lightning_talks#Continous_Integration_with_CruiseControl_and_Scratchbox | '''Continous Integration with CruiseControl and Scratchbox''']] - ''Jani Mikkonen''
# [[/Lightning_talks#Conboy.2C_Tomboy_and_Snowy | '''Conboy, Tomboy and Snowy''']] - ''Cornelius Hald''
# [[/Lightning_talks#Ogg_support_status | '''Ogg support status''']] - ''Tuomas Kulve''
# [[/Lightning_talks#Maemo_Platform_Security | '''Maemo Platform Security''']] - ''Elena Reshetova''
|-
| 15:25 - 15:45
| colspan="4" align="center" | Break
|-
| 15.45 - 16.10
| [[/Day 2#GUPnP_and_Rygel:_The_UPnP.2FDLNA_solution_for_Maemo | '''GUPnP and Rygel: The UPnP/DLNA solution for Maemo''']] 
''Zeeshan Ali''
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha'' [http://www.slideshare.net/j_rocha/adapting-gnome-applications-to-maemo-fremantle (slides)]
| [[/Day 2#Contributing_with_Git_.26_Gitorious | '''Contributing with Git & Gitorious''']] Johan Sørensen
| [[/Day_2#High-resolution_image_processing_on_Maemo_devices | '''High-resolution image processing on Maemo devices''']] 
''Alexander Bokovoy''
|-
| 16.15 - 16.40
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk'' [http://www.slideshare.net/carstenmunk/mer-a-year-after (slides)]
| [[/Day_2#Intelligent_Usage_of_Fremantle_Location_Framework_For_Location-aware_Applications | '''Intelligent Usage of Fremantle Location Framework For Location-aware Applications''']] 
''Quanyi Sun''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
| rowspan="2" | [[/Day_2#Git_hands-on_workshop | '''Git hands-on workshop''']] 
''David Greaves''
|-
| 16.45 - 17.10
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper'' [http://home.arcor.de/ak-47/en/linux/maemosummit2009.pdf (slides)]
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| [[/Day_2#Tracker:_Dial_M_for_Metadata | '''Tracker: Dial M for Metadata''']] 
''Ivan Frade, Iridian Kiiskinen''
|-
| 17.10 - 17.30
| colspan="4" align="center" | Break
|-
| 17.30 - 17.55
| [[/Day 2#Canola:_Beyond_the_media_playback | '''Canola: Beyond the media playback''']] ''Eduardo Lima''
| [[/Day 2#Hands-on_development_with_Nokia_Web_Runtime | '''Hands-on development with Nokia Web Runtime''']] 
''Oren Levine'' [http://www.slideshare.net/olevine/handson-development-with-nokia-web-runtime (Slides)] [http://www.forum.nokia.com/Technology_Topics/Web_Technologies/Web_Runtime/ (More information)]
| [[/Day 2#The_Qt_Mobility_Project | '''The Qt Mobility Project''']] ''Alex Luddy''
| [[/Day_2#Hacking_officially_unsupported_Bluetooth_profiles_to_work_in_Fremantle | '''Hacking officially unsupported Bluetooth profiles to work in Fremantle''']] 
''Johan Hedberg''
|-
| 18.00 - 18.25
| [[/Day_2#The_Maemo_5_Address_Book | '''The Maemo 5 Address Book''']] 
''Mathias Hasselmann, Travis Reiter''
| [[/Day 2#Publishing_your_software_through_maemo.org | '''Publishing your software through maemo.org''']] ''Niels Breet''
| [[/Day_2#Maemo_and_oFono | '''Maemo and oFono''']] 
''Aki Niemi, Rémi Denis-Courmont''
| [[/Day_2#The_future_of_GTK.2B.2FHildon_in_Maemo_Harmattan | '''The future of GTK+/Hildon in Maemo Harmattan''']] 
''Alberto Garcia, Claudio Saavedra''
|-
| 18.45 - 20.30
| colspan="4" align="center" | Maemo Drinks in N900 room
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.45
| colspan="4" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, [http://mauku.innologies.com Mauku], OMWeather [http://www.slideshare.net/vasvlad/omweather-in-maemo-summit-2009 (Slides+notes)], eCoach and more.
|-
| 10.45 - 11.00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 3#Maemo_Browser_for_power_users | '''Maemo Browser for power users''']] ''Mikko Korpelainen'' - [http://www.slideshare.net/mtkorpel/maemo-browser (presentation content)]
 [[/Day 3#Maemo_Browser_evolution | ''Maemo Browser evolution'']] ''Oleg Romashin''
 
 [[/Day 3#Maemo_Browser_extension_development | ''Maemo Browser extension development'']] ''Sudarsana Nagineni''

| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| [[/Day_3#Building_for_Mer | '''Building for Mer''']] ''David Greaves'' - [http://www.slideshare.net/mrlbt/building-for-mer (Slides+notes)] [[Mer/Build | (see also Mer Build page)]]
| rowspan="2" | [[/Day 3#Hackathon:_Integrating_Canola_with_Fremantle | '''Canola Fremantle Hackathon''']]
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| [[/Day_3#Designing_QT_application_for_Maemo_5_and_Maemo_6 | '''Designing Qt application for Maemo 5 and Maemo 6''']] ''Sergiy Dubovik, Ian Monroe''
| [[/Day 3#Writing_plugins_for_MAFW | '''Writing plugins for MAFW ''']] ''Iago Toral'' [http://blogs.igalia.com/itoral/2009/10/11/writing-mafw-plugins-talk-maemo-summit/ (blog post with slides and source code examples)]
|-
| 12.00 - 12.25
| [[/Day_3#Mobile_Office_based_on_KOffice_Open_Source_Project | '''Mobile Office based on KOffice Open Source Project''']] 
''Suresh Chande'' [http://sureshchande.blogspot.com/2009/10/mobile-office-based-on-koffice-for.html (blog post + video demo)]
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| [[/Day_3#Maemo_Platform_Security:_Principles_and_Concepts | '''Maemo Platform Security: Principles and Concepts''']] 
''Elena Reshetova''
|[[/Day_3#Extending_the_Hildon_desktop | '''Extending the Hildon desktop ''']] 
''Marc Ordinas i Llopis''
|-
| 12.30 - 12.55
| [[/Day 3#Towards_painless_and_quality_translations | '''Towards painless and quality translations''']] Dimitris Glezos ([http://media.indifex.com/other/maesum.pdf slides])
| [[/Day_3#10_Tips_for_Designing_Mobile_Widgets | '''10 Tips for Designing Mobile Widgets''']] 
''Rajesh Lal'' ([http://www.slideshare.net/rajeshlal/ten-tips-for-designing-mobile-widgets-2009-q3-maemo-summit-v1 slideshare], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pdf pdf], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.ppt ppt], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pps pps])
| [[/Day_3#Telepathy_on_Maemo | '''Telepathy on Maemo''']] 
''Marco Barisione''
| [[/Day_3#What_to_do_about_.2Fopt_in_Fremantle | '''What to do about /opt in Fremantle''']] 
''Marius Vollmer''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Issues_on_adapting_Maemo_4_application_to_Maemo_5 | '''Issues on adapting Maemo 4 application to Maemo 5''']] - ''Aniello del Sorbo'' - [http://www.slideshare.net/anidel/issues-on-adapting-maemo-4-applications-to-maemo-5-2229255 (Slides)]
# [[/Lightning talks#How_to_speed_up_your_Maemo_application_development | '''How to speed up your Maemo application development''']] - ''Raul Herbster''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# [[/Lightning talks#GSoC_presentation:_BitTorrent_plugin_for_Canola | '''GSoC presentation: BitTorrent plugin for Canola''']] - ''Lauri Võsandi''
# [[/Lightning talks#GSoC_Project_presentation:_Picasa_plugin_for_Canola | '''GSoC Project presentation: Picasa plugin for Canola''']] - ''Andrei Mirestean''
# [[/Lightning talks#Behaviour-Driven_Development_on_Maemo | '''Behaviour-Driven Development on Maemo''']] - ''Jose Teixeira''
# [[/Lightning_talks#N900_HW_architecture_overview_.26_power_management | '''N900 HW architecture overview & power management''']] - ''Igor Stoppa''
# [[/Lightning talks#From_corporations_to_communities:_responsible_and_effective_engagement | '''From corporations to communities: responsible and effective engagement''']] - ''Randall "Texrat" Arnold''
# [[/Lightning talks#Mer_from_a_user.27s_perspective | '''Mer from a user's perspective''']] - ''Tomasz Dominikowski'' - [http://www.slideshare.net/guest8106d9c/mer-from-users-perspective (Slides)]
# [[/Lightning talks#Nokia_PUSH_N900_Project_Showcase | '''Nokia PUSH N900 Project Showcase''']] - ''Ben Mason and Gary Birkett''
|-
| 15.30 - 16.00
| colspan="4" align="center" | Grand Finale
|}

== News ==
Link here Summit related news that made it to the homepage of recognized media.
* Made it to homepage of slideshare.net as Spotlight: Maemo Summit 2009, Amsterdam in the right navigation

== User-created content ==

===Tagged===

Please use the tag "maesum" (or hashtag "#maesum" on Identi.ca/Twitter) to tag your content.

Here are some helpful links to search for Maemo Summit content:

* [http://www.flickr.com/photos/tags/maesum/interesting/ maesum on Flickr]
* [http://picasaweb.google.com/lh/view?q=maesum&psc=G maesum on Picasa]
* [http://search.twitter.com/search?q=maesum maesum on Twitter]
* [http://identi.ca/tag/maesum maesum on Identi.ca]
* [http://www.youtube.com/results?search_query=+%22maesum%22 maesum on YouTube]
* [http://technorati.com/search/maesum maesum on Technorati]
* [http://www.slideshare.net/event/maemo-summit-2009 maesum on Slideshare]
* [http://vimeo.com/tag:maesum maesum on Vimeo]

===Blogs===

See [http://planet.maemo.org Planet Maemo] for some additional posts.

* [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Day 1], [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-2/ Day 2], [http://freebirdbr.wordpress.com/2009/10/13/maemo-summit-2009-dia-3/ Day 3] and two special posts on [http://freebirdbr.wordpress.com/2009/10/09/mitos-do-n900-n900-roda-mesmo-quake-iii/ Quake III on Maemo] and [http://freebirdbr.wordpress.com/2009/10/13/maemo-co-creation-workshop/ Co-creation workshop] at [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Free Bird] ('''''in portuguese'''''); automatic translations (by Google Translate) [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-1%2F&sl=&tl=en Day 1], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-2%2F&sl=&tl=en Day 2], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-summit-2009-dia-3%2F&sl=&tl=en Day 3], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F09%2Fmitos-do-n900-n900-roda-mesmo-quake-iii%2F&sl=&tl=en Quake III on Maemo] and [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-co-creation-workshop%2F&sl=&tl=en Co-creation workshop]
* Live blogging at [http://maemotalk.com/ Maemo Talk]: [http://maemotalk.com/2009/10/09/maemo-summit-2009-day-1/ Day 1], [http://maemotalk.com/2009/10/10/maemo-summit-2009-day-2/ Day 2], [http://maemotalk.com/2009/10/11/maemo-summit-2009-day-3/ Day 3]
* [http://blog.bdesmet.be/?p=228 biertie's blogpost]
* Add a link to your blog post here

===Videos===

Please add videos that have been taken directly at the Summit (Talks, Interviews, etc..).

* [http://www.youtube.com/watch?v=n7a2Vz9msq4 Quake 3 Presentation]
* [http://www.youtube.com/watch?v=-xzD7UrrP9w Intro Video (N900 room, Friday morning)]
* [http://vimeo.com/7109463 Mer: how the community innovates]
* [http://vimeo.com/7059150 Summit Finale]
* Add a link to your video here

===Photos===

Please add links to your photos, either as a Flickr photoset, Picasa album or personal website.

* [http://www.flickr.com/photos/63684846@N00/sets/72157622451059219/ thp's photos on Flickr]
* [http://www.flickr.com/photos/43614522@N08/ rajesh lal's photos on Flickr]
* Add a link to your photos here

== Old ==

<div style="font-size: 1em;">
<div class="sections">
<div class="column">
<div class="section">
<h2>Schedule</h2>
<ul class="document">{{Summit 2009 Schedule}}
</ul></div>
<div class="section">
<h2>Location</h2>
<ul class="help">{{Summit 2009 Location}}
</ul></div>
<div class="section">
<h2>Attendees</h2>
<ul class="help">{{Summit 2009 Attendees}}</ul>
* [[Maemo_Summit_2009/Speakers|Information for Speakers]]
</div>
<div class="column">
<div class="section">
<h2>Organization</h2>
<ul class="help">{{Summit 2009 Organization}}
</ul></div>
</div></div>
</div>

=== Latest News ===
<rss title="off" desc="off" number="10" time="3600">http://search.twitter.com/search.rss?q=%23maesum</rss>

[[Category:Community|Mer]]

Maemo Summit 2009/Schedule/Day 1

2009-10-19T07:38:19Z

192.100.124.218: /* Harmattan Architecture Overview */

=== Maemo 5 and the Nokia N900 ===
* Presenter: Ari Jaaksi, VP Maemo Devices, Nokia

* Abstract: Maemo 5 is a major milestone of the evolution of Maemo. Maemo 5 delivers computer experiences to pocket-sized devices. It is about six weeks ago that the Nokia N900 was launched and it is time to take a look where we are now with the N900. For newcomers in the community, Ari will summarize the evolution of Maemo. He will tell how we built the N900, together with the community, giving insight to what happened behind the scenes in the last 18 months. Ari will outline on what we focused on when we redesigned the user experience from Maemo 4 to Maemo 5.

=== Changing PC & Mobile Landscape; Why Linux will play a Critical Role ===
* Presenter: Jim Zemlin, Executive Director of the Linux Foundation

* Abstract: Jim Zemlin will discuss how the PC and mobile market are merging and how Linux is ideally suited for the new range of devices that are coming to a converged world.
: In addition he will speak about how the PC and mobile device industry is switching towards a service economy and how utilizing open source allows organizations to reap profits in a range of services. Finally, he will address the kind of user experiences that Linux is ideal for enabling. He will cover the need for social networking API's to be mapped out by the community on a region by region basis in order to enable a better web experience on Linux devices and how the web can be integrated into a native UI with Linux and provide an entirely new take on how we define the PC.

=== Nokia Nseries Devices on Maemo===
* Presenter: Jose-Luis Martinez Merino, VP, Marketing, Nokia

* Abstract: Jose-Luis will explain which role Maemo-based Nseries devices play in Nokia's portfolio.

=== Harmattan Highlights - Developer Opportunities ===
* Presenter: Janne Heikkinen, Director Maemo Product Planning, Nokia

* Abstract: Janne will go through what developer opportunities do exist for Maemo 5 and the N900. He will explain what tools are available and which means there are to get innovations to consumers. He will explain which key platform technologies the Harmattan release will include giving application and platform developers an insight on how to contribute to and benefit from the Harmattan release.

=== Why the Maemo Community matters to Nokia ===
* Inteviewer: Alan "qole" Bruce of the 2nd & 3rd Maemo Community Councils
* Interviewee: Ari Jaaksi, VP Maemo Devices, Nokia

* Abstract: This relaxed, informal interview will focus on how Nokia sees the current community contribution and engagement with Maemo Devices evolving in the next years. Questions on what could work better and what the community needs from Nokia will spice up this interview.

=== UI design of Maemo 5 apps ===
* Presenter: Annu-Maaria Nivala, Project Manager, User Experience, Digia

* Abstract: Digia's User Experience Team's experiences of what makes a good UI design for Maemo 5 apps. Ten most critical issues listed in order to help identifying potential usability problems in UI design of Maemo applications.

=== Developing widgets on Maemo 5 - showcase Foreca Weather ===
* Presenter: Juha Järvi, Software Designer, Foreca

* Abstract: This talk will go over some of the design considerations, development process and testing methodology for a Fremantle desktop widget and other software communicating with it. As an example, Foreca's desktop weather widget has been ported from Diablo to Fremantle with a new more complicated underlying architecture. Several parts need to communicate reacting to settings changes and receiving online data. Particularly power usage, certain regional settings and keeping all parts synchronized were new challenges. Some problems and solutions are shared for others to also learn from the experience.

=== Developing apps with Qt for Maemo5 ===
* Presenter: Kate Alhola, Forum Nokia, Chief Guru on Maemo

* Abstract: coming soon

=== Developing apps with Qt on Harmattan ===
* Presenter: Ville Lavonius, Product Manager Developer Offering, Nokia

* Abstract: coming soon

=== Developing apps with Nokia Web Runtime ===
* Presenter: Santtu Ahonen, Head of Developer Offering, Nokia

* Abstract: coming soon

=== Developer Support for Maemo by Forum Nokia ===
* Presenter: Matt Collins, Director, Forum Nokia Marketing

* Abstract: Forum Nokia is the world's largest mobile developer community; and is now embarking on a new and exciting transformation. Nokia is introducing Qt to both Symbian and Maemo platforms and, in addition, strengthening its leading Web Runtime (WRT) offering through Ovi services. Maemo developers will hear how Forum Nokia wikis, discussion boards, blogs and programs such as Champions and Launchpad will provide them the resources to learn Qt and also publish their applications to Ovi Store. This presentation will outline Forum Nokia's offerings, and our promise to developers for fostering an open cross-platform ecosystem.

=== UX panel ===
* Moderator: Tim Samoff, 2nd Maemo Community Council
* Panelists: Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5

* Abstract: An interactive panel, discussing the User Experience in general, as well as User Experience on Maemo. Harri and Martin will discuss the goals of Maemo5 UI, and comment on the future UI directions for Maemo.

* Tim Samoff: Tim is an award-winning filmmaker and designer who has been working in various industries for almost 20 years. He's produced computer games, created brand identities, participated in several open source software projects, and designed innumerable websites. He has also played with several bands and has recorded three CDs, one that became the number one electronic album on mp3.com. Tim came to Maemo sometime between the 770 and the N800 and quickly became involved in helping users and developers in a variety of tablet-related issues. His first major contribution to the community was a document entitled, "An Unofficial Guide to Creating a Most Excellent Maemo User Interface." Since then, he has designed icons, logos, and user interfaces for Maemo-related projects. He also served two terms as a Maemo Community Council member.

* Harri Kiljander is leading the user experience design team in Maemo Devices in Nokia. Harri is a computer scientist who then moved into information visualization and human-computer interaction. Prior to this role, Harri has been responsible for Nokia's corporate user experience strategy, and working in various UX design management and research positions in Nokia's internet services, research and development, and brand management teams in Finland and in the USA. In Maemo, Harri has been driving the bridging of agile software development with human-centered design in product creation. Harri holds a Master's degree in Computer Science and a Ph.D. in Interactive Digital Media from Helsinki University of Technology, and he is a co-editor of the book "Mobile Usability: How Nokia Changed the Face of the Mobile Phone".

* Martin Schüle is the Principal Designer of Maemo5 User Interface. He is a creative lead with more than 10 years of experience in multidisciplinary design like user interface design, interaction design, industrial design, graphical design and exhibition design; from target settings up to final deliverables. Prior to joining Nokia in 2003 Martin worked in Design agencies in Germany as well as in Finland. During his career Martin received several Design Awards, as well as Nokia internal awards and has been number one User Interface inventor in Nokia Devices based on the patent filings during the 1st half 2009. Martin holds a degree in Industrial Design

=== Firefox on Maemo ===
* Presenter: Stuart Parmenter, Director of Engineering, Mozilla

* Abstract: coming soon

=== Present and future of Maemo digital marketing ===
* Presenter: Isko Salminen, Production Manager, Activeark and Jussi Mäkinen, Maemo Marketing, Nokia

* Abstract: coming soon

* Isko Salminen works as a Production Manager at Activeark Ltd. (activeark.com). For the past year I’ve been working on Project maemo.nokia.com as Lead Technical Architect.
Contact:
@isko (twitter)
isko.salminen@activeark.com (email)

=== Biz apps on Maemo ===
* Presenter: Kari Pikkarainen, Product Manager Productivity, Nokia

* Abstract: This talk covers some business use cases that can be done conveniently with Maemo 5 based Nokia N900. Email, calendar and office tool allow users to work while out of office. Presenter talks about his typical working day and goes through some Nokia N900 highlights.

*Kari Pikkarainen: Kari has worked with Maemo and Internet Tablets since first Nokia 770 Internet Tablet. Before that he was software engineer. Today he product manages email, calendar and office tool applications.

=== Skype on Maemo ===
* Presenter: Mark Douglas, Mobile Product Manager, Skype

* Abstract: coming soon

=== Cross-platform with Qt - live ===
* Presenter: Ariya Hidayat, Software Engineer, Nokia

Ariya is a software engineer at Nokia, Qt Development Frameworks in Oslo. He is an open-source advocate for almost a decade, his code can be found in various projects such as KDE, WebKit, and of course Qt.

* Abstract:
As a powerful framework, Qt offers tons of modules and classes for building your applications. This talk highlight few practical cross-platform examples of what Qt can do with a fairly few lines of code, ranging from kinetic scrolling, weather service, OpenStreetMap, parallax effect, flight tracking, WYSIWYG HTML editor, and many more. All examples will be accompanied with corresponding '''live demos'''.

=== Mer - how the community innovates ===
* Presenter: Carsten Munk, Lead Developer, Mer project

* Abstract: As well as being a Fremantle backport for Nokia N8x0, Mer has been a project where we have tried to develop an organization inside the community with the aim of making the community an equal part in developing the Maemo platform. This talk will be about the methods used, challenges had and results made in creating this organization as well as how to motivate developers to contribute and keeping them motivated. Future role of Mer will also be discussed and suggestions how to step up the cooperation.

=== Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform ===
* Presenter: Ameet Suri, Marketing Manager, OMAP™ Mobile Communication and Computing Business Line, Wireless Business Unit, Texas Instruments.

As a marketing manager for the Texas Instruments Incorporated (TI) OMAP™ mobile communications and computing business line, Ameet Suri manages efforts surrounding TI’s OMAP processor strategy for the mobile communication and computing spaces. Suri and his team identify key trends to better define TI’s OMAP processors’ leading presence in a broad range of markets, including smartphones, mobile Internet devices (MIDs), tablets, net-tops and netbooks.

TI’s broad product portfolio provides the full range of power-optimized tools required to achieve success in the emerging mobile communication and computing markets – from applications processors, mobile connectivity solutions and analog components, to software solutions that deliver a compelling user experience. Suri and the OMAP processor team help customers best utilize those tools to deliver complete, differentiated products.

Suri began his career with TI in 2003. Recruited for his rich graphics expertise, he established the graphics software team for OMAP technologies at the beginning of his time with the company. In this position, Suri worked in OMAP software research and development, and contributed to the development of 3D software solutions for OMAP processors.

Suri previously held engineering positions at Samsung and Mastech. At these companies, he gained experience developing and architecting various software technologies for handsets.

Suri earned a bachelor’s degree in computer science from MGM College of Engineering and Technology in India.

* Abstract: As consumers increasingly demand “no-compromise” mobile Internet experiences and feature-packed devices, the role of the operating system continues to grow in importance, as does the presence of open architectures that spur innovative thinking. The Maemo platform continues to show itself as a solid, open foundation for this innovation, answering consumers’ demands for top-notch mobile experiences.

In this session, TI’s Ameet Suri will discuss Maemo’s presence in the open source world, and how TI’s Zoom OMAP34x-II Mobile Development Platform is a strong foundation for creating Maemo-based features and applications. Suri will also highlight the full tool set needed to reduce risks and grow investments with Maemo, and will touch on TI’s unique relationship with the Maemo community.

=== Feedservice and plug-ins development in Maemo 5 ===
* Presenter: Mikko Levonmaa, Ixonos

* Abstract: Present the feedservice ecosystem and how it will enable efficient authoring of home screen widgets for social networks feeds and other information sources that exist in the internet. The framework provides an abstraction layer for the plugins and utility services for the most common functionality. From the device point of view it will provide a single point of control for the feeds, it will determine, with the help from a plugin, when a feed should be run. The feedservice will also monitor the device states, such as network connection and screen activity. This enables the feedservice to optimize the user experience in terms of up-to-date feeds and power managemet.

=== Harmattan Architecture Overview ===
* Presenter: Juha Tukkinen, Principal Engineer, Maemo Devices, Nokia
* Presentation: [http://www.slideshare.net/jtukkine/maemo-6-harmattan-architecture-overview Maemo 6 "Harmattan" Architecture Overview] on slideshare.net

=== Porting an OpenGL game to GL ES ===
* Presenter: Oliver Mcfadden, Software Engineer, Nokia

* Abstract: Presentation focusing on the challenges of porting OpenGL games to GL ES, including challenges above and beyond merely porting and optimizing the rendering engine. Quake 3 will be used as an example.

Maemo Summit 2009

2009-10-18T12:37:07Z

192.100.124.218: /* Sunday, October 11 */

<div style="font-weight:bold;">October 9-10-11, 2009- [http://www.westergasfabriek.nl/english/engels_welcome.php WesterGasFabriek] - Amsterdam</div>
[[Image:Westergas.png‎]]

== Conference archive ==
Videos, slides and other materials related to the sessions. Feel free to update your own.

=== Thursday, October 8 ===

17:00 - 19:00 Registration at the Community Room (Zuiveringshal Oost). '''Early registrations encouraged to avoid queues and stress on Friday morning!'''

19:00 - 00:00 The official get together on Thursday will be [http://www.indewildeman.nl/indexe.html In de Wildeman], a beer house ([http://maps.google.nl/maps?f=q&source=s_q&hl=en&geocode=&q=Kolksteeg+3+1012+PT+Amsterdam&sll=52.377171,4.897242&sspn=0.005803,0.016512&ie=UTF8&hq=&hnear=Kolksteeg+3,+1012+Amsterdam,+North+Holland&t=h&z=16 Map]).

=== [[/Schedule/Day 1 | Friday, October 9]] ===

9:00 Registration at the Community Room (Zuiveringshal Oost). '''Come early: you won't get to the conference without your badge.'''

10:00 '''Programme starts at N900 (Transformatorhuis)'''

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Maemo_5_and_the_N900 Maemo 5 and the Nokia N900] by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia [http://www.slideshare.net/peterschneider/maemo-and-the-nokia-n900 (slides)]

11:00 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Changing_PC_.26_Mobile_Landscape.3B_Why_Linux_will_play_a_Critical_Role Changing PC & Mobile Landscape; Why Linux will play a Critical Role]''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Nokia_Nseries_Devices_on_Maemo Nokia Nseries Devices on Maemo]''' by Jose-Luis Martinez Merino, VP, Marketing @ Nokia [http://www.slideshare.net/peterschneider/nokia-nseries-and-maemo-6 (slides)]

12:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Harmattan_Highlights_-_Developer_Opportunities Harmattan Highlights - Developer Opportunities]''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia [http://www.slideshare.net/peterschneider/maemo-5-developer-offering (Maemo 5 slides)] - [http://www.slideshare.net/peterschneider/maemo-6-technology-highlights (Maemo 6 slides)]

13:00 '''Lunch - Maemo Expo opens'''

14:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Why_the_Maemo_Community_matters_to_Nokia Why the Maemo Community matters to Nokia]''' - Alan "[http://maemo.org/profile/view/qole/ qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! N900 - ''chair: John Loughney''
! N810 - ''chair: Anthony Fabbricino''
! N800 - ''chair: Quim Gil''
|-

|-
| 15:00 - 15:25
| rowspan="2" | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#UX_panel UX Panel]'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| '''UI design of Maemo 5 apps'''
''Annu-Maaria Nivala, UX team, Digia'' [http://www.slideshare.net/annumaaria/ui-design-of-maemo-5-apps-digia (slides)]
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Cross-platform_with_Qt_-_live Cross-platform with Qt - live]'''
''Ariya Hidayat, Software Engineer, Nokia''
|-
| 15:30 - 15:55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developing_widgets_on_Maemo_5_-_showcase_Foreca_Weather Developing widgets on Maemo 5 - showcase Foreca Weather]'''
''Juha Järvi, Software Designer, Foreca''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Mer_-_how_the_community_innovates Mer - how the community innovates]'''
''Carsten Munk, Lead Developer, Mer project'' [http://www.slideshare.net/carstenmunk/mer-how-the-community-innovates (slides)]
|-
| 16.00 - 16.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Firefox_on_Maemo Firefox on Maemo]'''
''Stuart Parmenter, Director of Engineering, Mozilla''

| '''Developing apps with Qt for Maemo5'''
''Kate Alhola, Forum Nokia, Chief Guru on Maemo
| | '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Your_foundation_for_open-source_innovation:_TI.E2.80.99s_OMAP_processor-based_Zoom_platform Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform]'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Present_and_future_of_Maemo_digital_marketing Present andd future of Maemo digital marketing]'''
''Isko Salminen, Production Manager, Activeark & Jussi Mäkinen, Maemo Marketing, Nokia'''
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Feedservice and plug-ins development in Maemo 5'''
''Mikko Levonmaa, Ixonos''
|-
| 17.00 - 17.25
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Biz_apps_on_Maemo Biz apps on Maemo]'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''Harmattan Architecture Overview'''
''Juha Tukkinen, Principal Engineer, Architecture and Sys, Nokia''
|-
| 17.30 - 18.00
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Skype_on_Maemo Skype on Maemo]'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Developer_Support_for_Maemo_by_Forum_Nokia Developer Support for Maemo by Forum Nokia]'''
''Matt Collins, Director, Forum Nokia Marketing''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Porting_an_OpenGL_game_to_GL_ES Porting an OpenGL game to GL ES]'''
''Oliver Mcfadden, Software Engineer, Nokia''
|-
|}

20:00 '''Maemo Party in FlexBar''' DJ's [http://valeriecherie.blogspot.com/2008/02/from-britain-with-love.html Russ Chimes] & [http://www.trashmenagerie.com/mixes/2008/04/01/grums-nllr-mixtape/ Grum] (check the mixtapes!) visuals by [http://www.xploitec.org/blog/?page_id=103 Xploitec VJ's]. coordinated by Jussi Mäkinen. It's a public bar and the doors are open to anybody. Our ''program'' will go until 23h or so, but the bar is open until really late with good music. Special cocktail hour sponsored by the lovely Skype people. Don't forget the Saturday schedule, though. :)

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="4" align="center" | '''Welcome to Community days''' ''Maemo Community Council'' ([http://www.youtube.com/watch?v=6Mm-OS__8V0 Video])
|-
| 10.15 - 10:45
| colspan="4" align="center" | '''Keynote: Ton Roosendaal, the Blender Foundation'''
|-
| 10.45 - 11:00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 2#Designing_UI_for_Maemo_5 | '''Designing UI for Maemo 5''']] 
''Mox Soini'' ([http://www.slideshare.net/moximillian/soini-designing-ui-for-maemo-5 Slides])
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa'' ([http://www.slideshare.net/guestb404461/pyqt-application-development-on-maemo Slides], [http://web.atombiztos.hu/pyqt_on_maemo.zip .odp with demo videos])
|rowspan="2" | [[/Day 2#Getting_started_session | '''Getting started session''']] ''Daniel Wilms and others''
| ------
|-
| 11.30 - 11.55
| [[/Day 2#Personalizing_your_Maemo_5_device | '''Personalizing your Maemo 5 device''']] ''Hartti Suomela''
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| ------
|-
| 12.00 - 12.25
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day_2#Introducing_the_Harmattan_UI_framework | '''Introducing the Harmattan UI framework''']] 
''Tomas Junnonen''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
| rowspan="2" | [[/Day 2#Extras.2Fautobuilder.2Finterfaces_round-table | '''Extras/autobuilder/interfaces round-table''']]
|-
| 12.30 - 12.55
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster'' 
[http://www.slideshare.net/miahfost/packaging-for-the-maemo-platform (slides)]
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Feedhandler_-_Integrating_RSS_newsreaders_with_the_browser | '''Feedhandler - Integrating RSS newsreaders with the browser''']] - ''Thomas Perl''
# [[/Lightning talks#python-mafw:_MAFW_framework_for_Python_developers | '''python-mafw: MAFW framework for Python developers''']] - ''Andrea Grandi'' - [http://www.slideshare.net/andy80/pythonmafw-intoduction-at-maemo-summit-2009 (Slides)]
# [[/Lightning talks#DVCS.3F_git.3F_-_How_does_that_work_then.3F | '''DVCS? git? - How does that work then?''']] - ''David Greaves'' - [http://www.slideshare.net/mrlbt/git-how-does-that-work-then (Slides)]
# [[/Lightning_talks#BlueMaemo_-_Bluetooth_HID_mouse_.26_keyboard_for_Maemo | '''BlueMaemo - Bluetooth HID mouse & keyboard for Maemo''']] - ''Valério Valério'' [http://www.slideshare.net/VDVsx/bluemaemo-bluetooth-hid-mouse-keyboard-for-maemo (Slides)]
# [[/Lightning_talks#Continous_Integration_with_CruiseControl_and_Scratchbox | '''Continous Integration with CruiseControl and Scratchbox''']] - ''Jani Mikkonen''
# [[/Lightning_talks#Conboy.2C_Tomboy_and_Snowy | '''Conboy, Tomboy and Snowy''']] - ''Cornelius Hald''
# [[/Lightning_talks#Ogg_support_status | '''Ogg support status''']] - ''Tuomas Kulve''
# [[/Lightning_talks#Maemo_Platform_Security | '''Maemo Platform Security''']] - ''Elena Reshetova''
|-
| 15:25 - 15:45
| colspan="4" align="center" | Break
|-
| 15.45 - 16.10
| [[/Day 2#GUPnP_and_Rygel:_The_UPnP.2FDLNA_solution_for_Maemo | '''GUPnP and Rygel: The UPnP/DLNA solution for Maemo''']] 
''Zeeshan Ali''
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha'' [http://www.slideshare.net/j_rocha/adapting-gnome-applications-to-maemo-fremantle (slides)]
| [[/Day 2#Contributing_with_Git_.26_Gitorious | '''Contributing with Git & Gitorious''']] Johan Sørensen
| [[/Day_2#High-resolution_image_processing_on_Maemo_devices | '''High-resolution image processing on Maemo devices''']] 
''Alexander Bokovoy''
|-
| 16.15 - 16.40
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk'' [http://www.slideshare.net/carstenmunk/mer-a-year-after (slides)]
| [[/Day_2#Intelligent_Usage_of_Fremantle_Location_Framework_For_Location-aware_Applications | '''Intelligent Usage of Fremantle Location Framework For Location-aware Applications''']] 
''Quanyi Sun''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
| rowspan="2" | [[/Day_2#Git_hands-on_workshop | '''Git hands-on workshop''']] 
''David Greaves''
|-
| 16.45 - 17.10
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper'' [http://home.arcor.de/ak-47/en/linux/maemosummit2009.pdf (slides)]
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| [[/Day_2#Tracker:_Dial_M_for_Metadata | '''Tracker: Dial M for Metadata''']] 
''Ivan Frade, Iridian Kiiskinen''
|-
| 17.10 - 17.30
| colspan="4" align="center" | Break
|-
| 17.30 - 17.55
| [[/Day 2#Canola:_Beyond_the_media_playback | '''Canola: Beyond the media playback''']] ''Eduardo Lima''
| [[/Day 2#Hands-on_development_with_Nokia_Web_Runtime | '''Hands-on development with Nokia Web Runtime''']] 
''Oren Levine'' [http://www.slideshare.net/olevine/handson-development-with-nokia-web-runtime (Slides)] [http://www.forum.nokia.com/Technology_Topics/Web_Technologies/Web_Runtime/ (More information)]
| [[/Day 2#The_Qt_Mobility_Project | '''The Qt Mobility Project''']] ''Alex Luddy''
| [[/Day_2#Hacking_officially_unsupported_Bluetooth_profiles_to_work_in_Fremantle | '''Hacking officially unsupported Bluetooth profiles to work in Fremantle''']] 
''Johan Hedberg''
|-
| 18.00 - 18.25
| [[/Day_2#The_Maemo_5_Address_Book | '''The Maemo 5 Address Book''']] 
''Mathias Hasselmann, Travis Reiter''
| [[/Day 2#Publishing_your_software_through_maemo.org | '''Publishing your software through maemo.org''']] ''Niels Breet''
| [[/Day_2#Maemo_and_oFono | '''Maemo and oFono''']] 
''Aki Niemi, Rémi Denis-Courmont''
| [[/Day_2#The_future_of_GTK.2B.2FHildon_in_Maemo_Harmattan | '''The future of GTK+/Hildon in Maemo Harmattan''']] 
''Alberto Garcia, Claudio Saavedra''
|-
| 18.45 - 20.30
| colspan="4" align="center" | Maemo Drinks in N900 room
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! N900
! N810
! N800
! 770
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.45
| colspan="4" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, [http://mauku.innologies.com Mauku], OMWeather [http://www.slideshare.net/vasvlad/omweather-in-maemo-summit-2009 (Slides+notes)], eCoach and more.
|-
| 10.45 - 11.00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 3#Maemo_Browser_for_power_users | '''Maemo Browser for power users''']] ''Mikko Korpelainen'' - [http://www.slideshare.net/mtkorpel/maemo-browser (presentation content)]
 [[/Day 3#Maemo_Browser_evolution | ''Maemo Browser evolution'']] ''Oleg Romashin''
 
 [[/Day 3#Maemo_Browser_extension_development | ''Maemo Browser extension development'']] ''Sudarsana Nagineni''

| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| [[/Day_3#Building_for_Mer | '''Building for Mer''']] ''David Greaves'' - [http://www.slideshare.net/mrlbt/building-for-mer (Slides+notes)] [[Mer/Build | (see also Mer Build page)]]
| rowspan="2" | [[/Day 3#Hackathon:_Integrating_Canola_with_Fremantle | '''Canola Fremantle Hackathon''']]
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| [[/Day_3#Designing_QT_application_for_Maemo_5_and_Maemo_6 | '''Designing Qt application for Maemo 5 and Maemo 6''']] ''Sergiy Dubovik, Ian Monroe''
| [[/Day 3#Writing_plugins_for_MAFW | '''Writing plugins for MAFW ''']] ''Iago Toral'' [http://blogs.igalia.com/itoral/2009/10/11/writing-mafw-plugins-talk-maemo-summit/ (blog post with slides and source code examples)]
|-
| 12.00 - 12.25
| [[/Day_3#Mobile_Office_based_on_KOffice_Open_Source_Project | '''Mobile Office based on KOffice Open Source Project''']] 
''Suresh Chande'' [http://sureshchande.blogspot.com/2009/10/mobile-office-based-on-koffice-for.html (blog post + video demo)]
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| [[/Day_3#Maemo_Platform_Security:_Principles_and_Concepts | '''Maemo Platform Security: Principles and Concepts''']] 
''Elena Reshetova''
|[[/Day_3#Extending_the_Hildon_desktop | '''Extending the Hildon desktop ''']] 
''Marc Ordinas i Llopis''
|-
| 12.30 - 12.55
| [[/Day 3#Towards_painless_and_quality_translations | '''Towards painless and quality translations''']] Dimitris Glezos ([http://media.indifex.com/other/maesum.pdf slides])
| [[/Day_3#10_Tips_for_Designing_Mobile_Widgets | '''10 Tips for Designing Mobile Widgets''']] 
''Rajesh Lal'' ([http://www.slideshare.net/rajeshlal/ten-tips-for-designing-mobile-widgets-2009-q3-maemo-summit-v1 slideshare], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pdf pdf], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.ppt ppt], [http://irajesh.com/files/10TipsForDesigningMobileWidgets.pps pps])
| [[/Day_3#Telepathy_on_Maemo | '''Telepathy on Maemo''']] 
''Marco Barisione''
| [[/Day_3#What_to_do_about_.2Fopt_in_Fremantle | '''What to do about /opt in Fremantle''']] 
''Marius Vollmer''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Issues_on_adapting_Maemo_4_application_to_Maemo_5 | '''Issues on adapting Maemo 4 application to Maemo 5''']] - ''Aniello del Sorbo'' - [http://www.slideshare.net/anidel/issues-on-adapting-maemo-4-applications-to-maemo-5-2229255 (Slides)]
# [[/Lightning talks#How_to_speed_up_your_Maemo_application_development | '''How to speed up your Maemo application development''']] - ''Raul Herbster''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# [[/Lightning talks#GSoC_presentation:_BitTorrent_plugin_for_Canola | '''GSoC presentation: BitTorrent plugin for Canola''']] - ''Lauri Võsandi''
# [[/Lightning talks#GSoC_Project_presentation:_Picasa_plugin_for_Canola | '''GSoC Project presentation: Picasa plugin for Canola''']] - ''Andrei Mirestean''
# [[/Lightning talks#Behaviour-Driven_Development_on_Maemo | '''Behaviour-Driven Development on Maemo''']] - ''Jose Teixeira''
# [[/Lightning_talks#N900_HW_architecture_overview_.26_power_management | '''N900 HW architecture overview & power management''']] - ''Igor Stoppa''
# [[/Lightning talks#From_corporations_to_communities:_responsible_and_effective_engagement | '''From corporations to communities: responsible and effective engagement''']] - ''Randall "Texrat" Arnold''
# [[/Lightning talks#Mer_from_a_user.27s_perspective | '''Mer from a user's perspective''']] - ''Tomasz Dominikowski'' - [http://www.slideshare.net/guest8106d9c/mer-from-users-perspective (Slides)]
# [[/Lightning talks#Nokia_PUSH_N900_Project_Showcase | '''Nokia PUSH N900 Project Showcase''']] - ''Ben Mason and Gary Birkett''
|-
| 15.30 - 16.00
| colspan="4" align="center" | Grand Finale
|}

== News ==
Link here Summit related news that made it to the homepage of recognized media.
* Made it to homepage of slideshare.net as Spotlight: Maemo Summit 2009, Amsterdam in the right navigation

== User-created content ==

===Tagged===

Please use the tag "maesum" (or hashtag "#maesum" on Identi.ca/Twitter) to tag your content.

Here are some helpful links to search for Maemo Summit content:

* [http://www.flickr.com/photos/tags/maesum/interesting/ maesum on Flickr]
* [http://picasaweb.google.com/lh/view?q=maesum&psc=G maesum on Picasa]
* [http://search.twitter.com/search?q=maesum maesum on Twitter]
* [http://identi.ca/tag/maesum maesum on Identi.ca]
* [http://www.youtube.com/results?search_query=+%22maesum%22 maesum on YouTube]
* [http://technorati.com/search/maesum maesum on Technorati]
* [http://www.slideshare.net/event/maemo-summit-2009 maesum on Slideshare]
* [http://vimeo.com/tag:maesum maesum on Vimeo]

===Blogs===

See [http://planet.maemo.org Planet Maemo] for some additional posts.

* [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Day 1], [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-2/ Day 2], [http://freebirdbr.wordpress.com/2009/10/13/maemo-summit-2009-dia-3/ Day 3] and two special posts on [http://freebirdbr.wordpress.com/2009/10/09/mitos-do-n900-n900-roda-mesmo-quake-iii/ Quake III on Maemo] and [http://freebirdbr.wordpress.com/2009/10/13/maemo-co-creation-workshop/ Co-creation workshop] at [http://freebirdbr.wordpress.com/2009/10/12/maemo-summit-2009-dia-1/ Free Bird] ('''''in portuguese'''''); automatic translations (by Google Translate) [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-1%2F&sl=&tl=en Day 1], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F12%2Fmaemo-summit-2009-dia-2%2F&sl=&tl=en Day 2], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-summit-2009-dia-3%2F&sl=&tl=en Day 3], [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F09%2Fmitos-do-n900-n900-roda-mesmo-quake-iii%2F&sl=&tl=en Quake III on Maemo] and [http://translate.google.com/translate?u=http%3A%2F%2Ffreebirdbr.wordpress.com%2F2009%2F10%2F13%2Fmaemo-co-creation-workshop%2F&sl=&tl=en Co-creation workshop]
* Live blogging at [http://maemotalk.com/ Maemo Talk]: [http://maemotalk.com/2009/10/09/maemo-summit-2009-day-1/ Day 1], [http://maemotalk.com/2009/10/10/maemo-summit-2009-day-2/ Day 2], [http://maemotalk.com/2009/10/11/maemo-summit-2009-day-3/ Day 3]
* [http://blog.bdesmet.be/?p=228 biertie's blogpost]
* Add a link to your blog post here

===Videos===

Please add videos that have been taken directly at the Summit (Talks, Interviews, etc..).

* [http://www.youtube.com/watch?v=n7a2Vz9msq4 Quake 3 Presentation]
* [http://www.youtube.com/watch?v=-xzD7UrrP9w Intro Video (N900 room, Friday morning)]
* [http://vimeo.com/7109463 Mer: how the community innovates]
* [http://vimeo.com/7059150 Summit Finale]
* Add a link to your video here

===Photos===

Please add links to your photos, either as a Flickr photoset, Picasa album or personal website.

* [http://www.flickr.com/photos/63684846@N00/sets/72157622451059219/ thp's photos on Flickr]
* [http://www.flickr.com/photos/43614522@N08/ rajesh lal's photos on Flickr]
* Add a link to your photos here

== Old ==

<div style="font-size: 1em;">
<div class="sections">
<div class="column">
<div class="section">
<h2>Schedule</h2>
<ul class="document">{{Summit 2009 Schedule}}
</ul></div>
<div class="section">
<h2>Location</h2>
<ul class="help">{{Summit 2009 Location}}
</ul></div>
<div class="section">
<h2>Attendees</h2>
<ul class="help">{{Summit 2009 Attendees}}</ul>
</div>
<div class="column">
<div class="section">
<h2>Organization</h2>
<ul class="help">{{Summit 2009 Organization}}
</ul></div>
</div></div>
</div>

=== Latest News ===
<rss title="off" desc="off" number="10" time="3600">http://search.twitter.com/search.rss?q=%23maesum</rss>

[[Category:Community|Mer]]

Maemo Summit 2009/Day 3

2009-10-18T12:25:36Z

192.100.124.218:

= Maemo Summit day 3, Sunday 11 October =

=== Fremantle Stars showcase ===

Take a tour of the Fremantle Stars, the best of the best in Maemo community developed applications, featuring:
; liqbase
: Gary Birkett, liquid at gmail dot com, lcuk on #maemo
; [http://mauku.innologies.com Mauku]
: [http://www.henrikhedberg.net Henrik Hedberg]
; OSM2Go
: Till Harbaum
; OMWeather
: Vlad Vasilyev
; eCoach
: Sampo Savola

=== Maemo Browser for power users ===
*Author: Mikko Korpelainen, mikko.korpelainen at nokia dot com
*Intended audience: users
*Talk type: presentation
*Abstract/description
: Quick overview of the Maemo Browser design and capabilities. Followed by an in-depth explanation of the end user features and settings the Maemo Browser has.
*Author bio
: Mikko Korpelainen is a senior product manager @ Maemo for browser, FlashPlayer, maps and location.

=== Maemo Browser evolution ===
*Author: Oleg Romashin, oleg.romashin at nokia dot com
*Intended audience: developers
*Talk type: presentation
*Abstract/description
: Quick overview of the Maemo Browser improvement process, rendering architecture.
Link to presentation: http://docs.google.com/present/view?id=ajk2s2df9zhr_144fb8zrrck
*Author bio
: Oleg Romashin is a senior lead developer @ Maemo for browser.

=== Maemo Browser extension development ===
*Author: Sudarsana Nagineni, sudarsana.nagineni at nokia dot com
*Intended audience: developers
*Talk type: presentation
*Abstract/description
: A tutorial on how to develop extensions for Maemo Browser.
*Author bio
: Sudarsana Nagineni is a senior developer at Maemo for browser.

=== [http://jammo.garage.maemo.org JamMo - Jamming mobile game for children] ===
* Author: Aapo Rantalainen (aapodotrantalainenatgmaildotcom)
* Intended audience: application developers
* Talk type: presentation
* Abstract/description
: JamMo is an educational music making game for children at age 3-12. It is targeted for Maemo 5 Fremantle. It uses GStreamer at music backend and Clutter toolkit for graphical user interface. In this talk we present the first version of the application and our experiences on underlying technologies. The development of JamMo is open to everyone who is interested to contribute in any way. For more information see http://jammo.garage.maemo.org/
* Additional Information
: Needed equipment: video projector, canvas, speakers.

* Author bio
: JamMo is a product of an EU funded [http://www.umsic.org/ UMSIC project]. Aapo Rantalainen is the head developer of JamMo.

=== Writing plugins for MAFW ===
*Author: Iago Toral - itoral at igalia dot com
*Intended audience: platform and application developers.
*Talk type: Presentation (Tutorial)
*Abstract/description
: A tutorial on how developers can write source and renderer plugins for the Media Application Framework (MAFW). The audience will learn how to develop new plugins that provide access to new sources of media content or implement different rendering backends and how they can use these plugins from their own media applications. The tutorial will also include an introduction to MAFW for those not familiar with the framework.
*Author bio
: I am a Software Engineer at Igalia and user of the Gnome Desktop and Linux OS for quite many years. Currently I am most interested in Multimedia, specially around MAFW, for which I am one of the main developers, and GStreamer.

=== Hackathon: Integrating Canola with Fremantle ===
*Author: [http://maemo.org/profile/view/etrunko Eduardo Lima (Etrunko)]
*Intended audience: Application Developers
*Talk type: Hands-on/Hackathon
*Abstract/description
: The idea of this session is to get a reasonable number of people interested in integrating Canola with the new technologies introduced in Fremantle, mostly Tracker and MAFW, together, so we can trace a plan and start getting our hands dirty.

: ''Why??''

: Some Canola components were conceived aiming to provide alternate solutions for some Nokia closed-source libraries and others that were not available by the time we started the project (mid-2007, back then we only had the N800 with Bora/Chinook). That's why we created our own media scanner (lightmediascanner+canolad) and media engine (atabake). Now I think it is time for us to evolve to the new and open solutions provided by Fremantle, yet keeping compatibility with "legacy" platforms, such as Diablo.

: People interested in developing plugins for Canola and/or developing using EFL/PyEFL are more than welcome to join us.
*Extra equipment
**<strike>''Guns, lots of guns.''</strike>
**Brave hacker souls
**Power outlets galore
**Internet Connection
**Whiteboard/Flipchart
**Coffe
*Author bio
: Open Source Software enthusiast, involved with Maemo since the very beginning (mid 2005), and had the opportunity to be part of the first Maemo Community Council. Started porting various GTK+/GNOME applications (Gnumeric, Evince, Abiword, Leafpad, Xournal, etc), to the platform. Worked on the first version of Carman, written in Python + GTK. After that, joined the team developing the Canola media player, coding and maintaining its packages for Maemo since then. Also maintains packages of the Enlightenment Foundation Libraries (EFL) for Maemo. Works for openBossa/INdT, where has been having the opportunity to present and talk about Maemo in events in Brazil and worldwide.

=== Maemo documentation co-creation ===

*Dave Neary, dneary at maemo dot org
*Intended audience: Users
*Talk type: Presentation
*Abstract/description
: The stated goal in the 2010 agenda for maemo.org is the co-creation of all Maemo documentation.
: This presentation will show the path we have traveled towards this goal so far, especially over the past year, the plans for Fremantle and Harmattan, and most importantly, a call to action showing how you can help out.

*Author bio
: Dave Neary has participated in many free software projects over the years. He was release manager of the GIMP, chairman of the GNOME Foundation, and community and product manager for the OpenWengo project. He is currently the maemo.org Docmaster, a role where he works to enable the Maemo community to do great work, and an independent consultant helping companies work with and create healthy communities.

=== Designing QT application for Maemo 5 and Maemo 6===
*Sergiy Dubovik <sergiy dot dubovik "at sign" nokia point com>, Ian Monroe <ian.monroe at collabora.co.uk>
*Intended audience: application developers
*Talk type: presentation
*Abstract/description

:How application developers should design their applications to work on Maemo 5 and Maemo 6 platforms? Which widgets will be supported? How to handle possible virtual keyboard? Where to store application settings? Which QT services will be available? These questions will be answered.

*Additional information on extra equipment you might need or something else goes here
:Just a projector

*Author bio
: Sergiy Dubovik is a senior software developer working in Nokia, designing and developing UI frameworks for Harmattan program.

: Ian is a software developer at Collabora Ltd where he works from home in Iowa City, Iowa USA. He has been a developer of the popular desktop music manager Amarok for four years. He is the maintainer of KDE's video player, Dragon Player.

=== Building for Mer ===
* [[User:lbt|David Greaves]]
* Intended audience: application & platform developers
* Talk type : Presentation/demo
* Abstract
: Since Fremantle Extras applications will eventually be submitted to the Mer builder it may be a good idea to introduce it. We use the openSuse Open Build Service; a GPL service that provides an emulated, pristine (yes, I'm looking at you autobuilder and scratchbox), dependency driven build environment. I'll talk about the processes around Mer builds, access controls, managing integration with our DVCS (git), acceleration tricks and generally how to make good use of things you find lying about on the web.

*Additional Information
: Live web link to OBS would be good.

*Author bio
: David is the Mer build mentor; he's been a solutions architect at a major telco for several years but still (kinda) knows how to code. He's a passionate believer in the commercial viability of OSS. Previous contributions include kick-starting the git documentation & establishing wikis for Linux RAID and MythTV. He runs linux everywhere.

=== Handheld Glom: Easy database applications ===
* Murray Cumming <murrayc at openismus dot com>
* Intended audience: application developers
* Talk type: Presentation
* Abstract/description:
: Many custom Maemo applications just need the user to navigate through some data and enter new information. Glom lets you quickly throw together a database structure and UI layout, providing a Maemo UI with no coding. You can then use Python for anything more complicated, though Glom itself already supports features such as related records, related fields, related choices, field lookups, calculated fields, and translated UIs.
*Author bio:
: Murray Cumming runs Openismus GmbH in Berlin and Munich. We work on Maemo's development platform and applications and maintain the GNOME C++ API (gtkmm). When we have extra time we work on Glom, gradually getting it ready for real-world use.

=== Towards painless and quality translations ===
* Dimitris Glezos (glezos _at_ indifex _dot_ com)
* Intended audience: developers, translators, docs writers, webmasters
* Talk type: Presentation
* Material: [http://media.indifex.com/other/maesum.pdf Slides (pdf)]
* Abstract/description
: Most developers agree: "Translations are hard". And while Maemo's localization is already in place, we've got a long way to maximize our efficiency in reaching a global audience. The challenges: lower the costs for developers, minimize maintenance overheads, provide the translators with an effective, easy-to-use interface for submitting translations to their favorite projects (even if they're hosted on git.. *especially* when they're hosted on git).
: Transifex is an open localization platform built for and used by communities similar to Maemo such as Moblin, Fedora and XFCE. This talk will present Transifex, discuss the test results by the Mer Project, and lay down the roadmap for the establishment of an infrastructure able to support the L10n process of Maemo.
*Additional Information
: The session will most likely turn into a BoF, bringing together application and platform developers, translators and webmasters/admins.
*Author bio
: Dimitris Glezos is the lead developer Transifex. He led Fedora re-engineer its globalization infrastructure allowing for an explosive growth of community translations. He currently serves as Fedora's Board member and Translation Leader. He works at Indifex, providing enterprise-level support on complex localization scenarios.

=== 10 Tips for Designing Mobile Widgets ===
*Author: [http://maemo.org/profile/view/rajeshlal Rajesh Lal], rajesh.lal at nokia dot com
*Intended audience: Widget Developers/Mobile Application Developers
*Talk type: Presentation

*Abstract/description
: Do you know why only 1 percent of Mobile Widgets are successful ? What makes some widgets thrive and used by millions, and others with equal functionality bite the dust ? Make no mistakes, design of a widget is not about graphics, color or fonts. This presentation will demystify this 'invisible' layer below the surface with 10 pragmatic tips. The tips will uncover some of the most useful, and often ignored standard design principles and how to apply them in a mobile context.

*Author bio
: Rajesh lal is a Designer, Author, Technology Evangelist, and a Senior Nokia Engineer with a decade of experience in Information Technology. He has been involved in Widget design and development for last 5 years and have authored multiple books on Gadgets and Widgets. He has experience in a variety of Mobile devices, namely Sony Mylo, Window's Mobile, Apple's Iphone, Nokia S60 and Maemo devices. His blog on design and user experience can be found at http://abcofdesign.com

=== Mobile Office based on KOffice Open Source Project===
*Suresh Chande, suresh.chande at nokia.com
*Intended audience: Application & Platform developers
*Talk type: Presentation
*Abstract/description
: We will present here Mobile Office project developed for Fremantle based on KOffice, a Qt based open source project.

*Additional Information (optional)
: We will demonstrate Mobile Office (KOffice) running on the N900.
: Blog Entry: http://labs.trolltech.com/blogs/2009/09/17/office-viewer-for-maemo5-based-on-koffice/

*Author bio
: Suresh Chande, works for Nokia in Device R&D(Maemo ) as Technical Product Owner for the Office Domain. Suresh has worked at Nokia Research Center for over 11 years focusing Mobile Business and Enterprise Application research. His vision is to have Office tools free for use by everybody.

=== Maemo Platform Security: Principles and Concepts ===

* Elena Reshetova - elena.reshetova@nokia.com
* Intended audience: users, application developers, platform developers
* Talk type: presentation - [http://www.slideshare.net/peterschneider/maemo-6-platform-security Slides]
* Abstract/description:

: The purpose of the Platform Security in the Maemo platform is to protect the owner of a Maemo-powered device from getting her personal, private data and passwords from being stolen and used for malicious purposes, to prevent a malware from misusing a device and incurring costs on user, to prevent a user from accidentally breaking the device and to make the platform meet the requirements set by such third party software that requires a safe execution environment.

: The main design goal is to have all this accomplished without any significant penalty in terms of performance or usability, by using established open standards and having as much of the implementation open-sourced as possible. Another goal is to minimize an entry barrier for 3rd party programmers by reusing the existing Linux programming environment and introducing only needed additional features.

: The presentation will cover the main principles and concepts of the Maemo Platform Security.

*Author bio
: Elena is a senior security engineer and representative of Maemo security team at the Maemo summit. The current task of the team is development of the Maemo Security FW.

=== Telepathy on Maemo ===
* Author: Marco Barisione, marco.barisione at collabora.co.uk
* Intended audience: application developers/platform developers
* Talk type: presentation

* Abstract/description:
The [http://telepathy.freedesktop.org/ Telepathy real-time communication framework] is a project to abstract messaging, presence, voice and video functionality, regardless of the underlying protocol. Amongst numerous benefits, this makes the connections available as a D-Bus service which can be shared between multiple applications, rather than limited to single monolithic jack-of-all-trades clients.

The talk will introduce the Telepathy framework, its basic concepts and current functionality. It will focus in particular on:
- The Telepathy architecture
- How Telepathy is used on Maemo 5 for chat, VOIP calls, telephony calls and SMS messages
- How to use Telepathy from your program

* Author bio:
Marco Barisione started to work on Telepathy implementing file transfer for a Google Summer of Code and for his University final project. After graduating he started to work for Collabora where he worked both on Telepathy and on the GTK+ port of WebKit and he spent the last year working on Telepathy-related components for Maemo.
Before falling in love with Telepathy he worked on various other GNOME projects, in particular adding regular expression support to GLib and implementing a new syntax highlighting engine for the GtkSourceView widget.

=== Extending the Hildon desktop ===
*Author: Marc Ordinas i Llopis ([[User:Marcoil|marcoil]]), marcoil at collabora dot co dot uk
*Intended audience: application developers/platform developers
*Talk type: presentation
*Abstract/description
: Developers can easily extend Maemo 5's desktop, giving users new ways to view and interact with the data in their mobile device. In this talk I'll describe the basic architecture and components of the desktop and show how to extend it.
*Author bio
: Marc is a programmer at Collabora and has been working on hildon-desktop for the last year.

=== What to do about /opt in Fremantle ===
Author: [[User:mvo|Marius Vollmer]]
*Intended audience: TBD
*Talk type: BoF
*Abstract/description
: For Fremantle, packages in the Extras repository are asked to install files into /opt to make better use of the available flash space.
This BoF is an opportunity to discuss everything related to this, immediate next steps and long term solutions, according to the interest of the participants.
*Author bio
: TBD

Maemo Summit 2009/Day 2

2009-10-15T08:24:55Z

192.100.124.218: /* Maemo and oFono */ presentation link

== Maemo Summit day 2, Saturday 10 October ==

=== Designing UI for Maemo 5 ===
* Mox Soini, mox.soini at movial.com
* Intended audience: Platform/Application Developers, users
* Talk type: presentation
* Slides: [http://www.slideshare.net/moximillian/soini-designing-ui-for-maemo-5 Available online at slideshare]
* Abstract/description:
: How to make the applications work together as an integrated whole?

: This talk will discuss the UI Design of the Maemo 5 product as an "application portfolio". Design patterns as well as application specific designs are presented, and the reasoning for the design decisions.

: Design of the pre-installed applications in the Maemo 5 product is discussed, highlighting the UI flows, common user experience solutions and power user features. Throughout the application walk-through, the structure and "look and feel" of the applications is categorized, resulting in a conceptual design tool for 3rd party application designers and developers.

* Author bio:
: Mox Soini, Interaction Designer at Movial, is one of the core people who designed the UI Style and UI Framework for the Maemo 5 product. His work additionally includes application design and occasional code patches. He contributes to open source community also in some other projects. Soini strives for a design process that engages collaboration, out of the box thinking and dedication to the fit and finish.

=== PyQt application development on Maemo ===
*Author: Attila Csipa, attila77 at talk.maemo.org
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: A complete walkthrough of creating applications for the Maemo platform with Python and Qt. The presentation would contain two segments, the first being the 'why' - introduction to underlying technologies, the rationale of using Python and Qt as a development platform on Maemo and a short demo of a few projects built with these tools. Comparison of different bindings (PyQt vs PySide)
: The second segment of the presentation focuses on the 'how' in a nutshell: How to setup up a proper PyQt/PySide development environment, how to develop most efficiently, how to debug, how to profile and optimize, platform caveats and gotchas, packaging considerations.
*Author bio
: Attila Csipa is an Open Source programmer and advocate from Serbia. His Open Source involvements include being a core contributor to web2py, a python based web framework, and contributions to other high profile projects like Mapserver, OpenLayers and NSLU2-linux.

=== Getting started session ===
* Daniel Wilms, ... (others will be announced later)
* Intended audience: developers
* Length: 2 slots (approx. 55 min)
* Talk type: demo

*Abstract/description
: The getting started session gives a practical introduction into the environment, which is needed for the development on Maemo. Starting with a short introduction of the Maemo.org infrastructure and the development environment, a step-by-step demonstration of the various tools will be given. Responsibles of each area will explain and demonstrate, how to start from scratch with the development using their tools. The session will end with a demonstration of a download client for 3rd party applications, which are hosted in the Maemo.org repository.

: '''Introduction:'''
: - The Maemo.org infrastructure (components, documentation, community)
: - Introduction development environment (SDK, SDK+, Eclipse, Qt)

: '''Demonstrations:'''
: - Setting up SDK
: - Setting up SDK+
: - Development with Eclipse
: - Development in Qt
: - Download client for Maemo.org

*Author bio
: Started as a trainee in NRC Bochum, I am working now for over 2 years for Nokia. In March I came to Maemo and my main task is the technical support of the Maemo.org community developers.

=== Personalizing your Maemo 5 device ===
* Hartti Suomela (hartti dot suomela at nokia dot com)
* Intended audience: users
* Talk type: presentation
* Abstract/description
An overview and demo about how you can personalize your Maemo 5 device, including backgrounds, themes, sounds, etc. The talk provides personalization tips for users (what can be done through the device settings), power users (how to add new backgrounds, themes, etc.) and "heavy" power users (e.g. how to change the system sounds).
*Author bio
Currently Hartti Suomela works at Nokia in the Maemo User Experience group. In his previous positions he has worked in the Nokia developer support and in Nokia Reserach Center's software laboratory for example managing university collaborations in U.S.

=== Go-to market opportunities for mobile application developers ===
*Author: Boaz Zilberman, co-founder and Chief Architect of fring.
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: I will be happy to present the go-to-market activities fring is doing to publish our application on the many platforms we work on - Linux, WinMobile, Symbian, Android, J2ME and iPhone. My intention is to stimulate an open discussion so we, as a community, can provide better ways to promote the platform benefits to ordinary users rather than the early adopters.
*Author bio
: Boaz Zilberman is a co-founder of fring - a VoIP and IM mobile service with million of active users worldwide. I am responsible for product definition and relations with terminal vendors.

=== Canola application and framework for rich GUI ===
*Gustavo Sverzut Barbieri (http://blog.gustavobarbieri.com.br/contact/)
*Intended audience: Application Developers
*Talk type: presentation
*Slides: http://talks.gustavobarbieri.com.br/maemo_summit/oct-2009/presentation.pdf
*Abstract/description
: Canola is a fancy media center, with a rich graphical user interface designed with touch screen in mind. More than a great application, it is a great framework as well, enabling extending Canola or creating similarly rich programs like Carman or your own! Initially developed by Instituto Nokia de Tecnologia (INdT) in Brazil it was released as GPLv3 and community start to build around it. Today we have more companies supporting the development, the software was ported to other platforms like Ubuntu and OpenMoko SHR. Moreover, 5 of 10 Maemo's Google Summer of Code projects are around Canola, from media extensions like Picasa integration to non-media related as Remember the Milk (To Do list) and Bittorrent.
: The framework behind Canola is called Python-Terra, which will be presented simultaneously. A brief overview of its components, followed by explanation of its plugin system will serve as base of understanding of Canola application. Real examples of extensions and new application will be demonstrated as result.
*Author bio
: Gustavo lead the development of Canola1 and designed and implemented Canola2 together with co-workers at INdT. Now he runs a company that does software development and services, among them Canola2 development.

=== Maemo Co-creation ===
* Organiser: Jussi Mäkinen
* Intended audience: Users
* Talk type: Presentation and Workshop
* Abstract/description
: Maemo co-creation workshops are annual sessions where selected [http://en.wikipedia.org/wiki/Lead_user lead users] + Maemo product managers, designers and marketeers together imagine the future use-cases for Maemo Devices.
: Maemo co-creation 2009 will now open up for the Maemo community by presenting the workshop results on the Saturday showcase and crafting the ideas forward with anyone willing to participate on our Sunday working session.
* Organizer bio
: [http://twitter.com/luovanto Jussi Mäkinen] is responsible for lead consumer marketing & co-creation activities @ Maemo Devices.

=== Maemomm: Maemo with C++ and a Gtkmm flavour ===
*Author: David King, davidk at openismus dot com, amigadave on IRC, http://amigadave.blogspot.com
*Intended audience: application developers/platform developers
*Talk type: presentation
*Slides: [http://amigadave.com/presentations/maemo_summit_2009.pdf Available as PDF]
*Abstract/description
: Maemomm is a set of C++ bindings for Maemo libraries. With the bindings, C++ programmers can use the language features that they are familiar with, and combine them with the underlying features of GTK+ and Maemo. Maemomm allows greater type-safety, use of C++'s object-orientation features and simpler reference-counting semantics.
: The advantages of the C++ API will be discussed, and demonstrated with short code examples. Comparisons to the underlying C API will be made, as well as to other toolkits. For more information see https://garage.maemo.org/projects/maemomm/
*Author bio
: David began working as a software developer for Openismus at the start of 2009. He works on Maemomm development, as well as other projects that are too exciting to talk about.

=== Extras/autobuilder/interfaces round-table ===
*Author: Ed Bartosh, Alexander Kanevskiy, Niels Breet
*Intended audience: application and platform developers
*Talk type: round-table
*Room: Oostelijk Meterhuis
*Duration: 1 hour
*Abstract/description
:The purpose of this round-table is to discuss future features that can be added to autobuilder and all Extras related services. We want to gather opinions and see what the needs of developers are. Suggestions about enhancements or new features are appreciated.
*Author bio
: Ed Bartosh and Alexander Kanevskiy both work at Nokia, in their spare time they work on the autobuilder for Extras. Niels Breet is the maemo.org webmaster, working on web services available at maemo.org.

=== GUPnP and Rygel: The UPnP/DLNA solution for Maemo ===
*Author: Zeeshan Ali, Lead-Developer at Maemo Devices, Nokia.
*Intended audience: everyone
*Talk type: presentation
*Abstract/description
: I will be introducing the work we have been putting up for the past two and half years to provide a complete well-documented solution for UPnP needs of Maemo and GNOME (Mobile) in general. Also included in the talk will be some cool demos of both of these projects in action.
*Author bio
: Zeeshan Ali is a Lead Developer at Nokia Maemo Devices in Helsinki, Finland and a GNOME developer. He started as a GStreamer plugin and application developer and got his first share of fame in the GNOME community for his video-whale project. For the past two year, he had been obsessed with UPnP/DLNA and in turn the GUPnP and Rygel projects. Thanks to Nokia, he now work full-time on Rygel and GUPnP.

=== Contributing with Git & Gitorious ===
*Johan Sørensen (johan at shortcut.no)
*Maemo devs and application developers
*Talk type - Presentation
*Abstract/description
: Gitorious.org is an open sourced application and site, that provides infrastructure for managing projects using Git. It hosts thousands of projects, among those Qt. This talk provides an overview of what Gitorious is and what it can do for your project.
*Author bio
: Johan Sørensen is the original developer of Gitorious, which is now driven by Shortcut AS, a company he co-founded.

=== Hildon toolkit for Fremantle ===
*Authors: Alberto Garcia, Claudio Saavedra
*Intended audience: Platform/Application Developers
*Talk type presentation
*Abstract/description
: This talk will describe all widgets introduced in Hildon 2.2, explaining all the new features and use cases, the reasons why some standard GTK+ widgets are not particularly suited to small devices and the solutions that Hildon 2.2 brings to solve these problems.

: This is a major upgrade of the toolkit. Among several style changes, this Hildon release is for the first time specifically designed to be finger friendly, introducing a panning container (kinetic scrolling) and a new range of selectors among other things.
*Author bio
: Alberto Garcia loves computers since he got his first Sinclair ZX Spectrum. In the late 90s he began using GNU/Linux and in 2001 he co-founded Igalia, a Galicia-based free software company. He's currently working on the new version of the Hildon toolkit for the new release of Maemo, codenamed 'Fremantle'. Besides programming, Alberto also loves cinema, music and going to the beach.
: Claudio Saavedra is a chilean Computer Engineer, working at Igalia since 2008. He got involved in the GNOME project back in 2005 and is one of the developers of the Eye of GNOME Image viewer. Currently, he is also working in Maemo 5, codenamed 'Fremantle', developing the Hildon library and also maintaining other parts of the toolkit stack.

=== Developments in The Qt WebKit Integration ===
*Author: Kenneth Rohde Christiansen kenneth.christiansen at openbossa dot org
*Intended audience: Application/Platform Developers
*Talk type: Presentation
*Abstract/description
: The Qt WebKit Integration provides a powerful framework to seamlessly integrate web technologies into future Maemo applications, where web content can interact with Qt components. This presentation introduces the QtWebKit APIs, the underlying engine and new features coming in future releases.
*Author bio
: Kenneth Christiansen has many years experience with opensource software, and worked on projects such as GNOME, intltools, Canola, and Colligo. He also organized the 2001 GUADEC conference in Copenhagen. Today Kenneth works at the OpenBossa labs at the Nokia Technology Institute in Brazil, where he is currently involved with developing next generation userfaces as well as working with web technologies as part of the Qt WebKit team.

=== Modest, email client for Fremantle ===
*Authors: Sergio Villar, Jose Dapena
*Intended audience: users, application developers
*Talk type: presentation
*Slides: [http://www.slideshare.net/jdapena/modest-maemo-summit-09 Modest Maemo summit 2009 slides at slideshare]
*Abstract/description
: Modest is a modern e-mail client designed for mobile and embedded devices, that focuses on providing a simple user interface, even when it offers advanced e-mail functionality. It's the default e-mail client for the Nokia N810 device.

: In this presentation we will show the new Hildon 2.2 frontend, and talk about the interesting challenges faced to improve the user experience of Modest using the new Maemo 5 platform. How we tried to simplify the UI overhead in the old N810 Maemo frontend, splitting Modest in multiple views and aggressively simplifying the actions exposed to user.

*Author bio
: José, who holds a degree in Computer Engineering from the University of A Coruña, is one of the founding members of Igalia. Now he is involved in the development of projects using Gtk/Gnome technologies and, in particular, Tinymail. He is also one of the initiators of Gnome Build Brigade. Currently, he's a member of Modest development team, and also a regular contributor to Tinymail.

: Sergio joined Igalia in 2003 after getting his Degree in Computer Engineering, and is now a proud stakeholder of the company. He has been involved in Gnome/Maemo developments since then. Sergio is currently co-maintainer of the Modest email client along with José. After more than two years of contributions to Tinymail, he became a co-maintainer of the project in 2009.

=== Mer: A year after ===
*Carsten Valdemar Munk (carsten.munk at gmail dot com , also known as Stskeeps)
*Intended audience: Users, application developers, platform developers
*Talk type: Presentation
*Abstract/description
: October'09 is a year after the thought of reconstructing Maemo was first proposed. The thoughts manifested themselves in the Mer project - originally only a proof of concept project, but with the announcement that Nokia would not bring Fremantle to the Nokia N8x0s the project got stronger community support. This talk is about the challenges and the accomplishments we've had in the project in the last year. It will also include thoughts on the future of Mer and a call for both community and Nokia to take a radical approach with Harmattan in terms of community involvement.
*Author bio
: Carsten (Stskeeps) is known as the primary facilitator of the Mer project and has successfully brought together developers, testers, artists, translators and other groups within both maemo.org and other device communities, to create Mer, a Fremantle community variant. He is currently finalizing his masters degree in computer science and has also been involved in other projects within the community such as Deblet, a Debian port.

=== maemo.org Bug Management ===
*Andre Klapper, aklapper at openismus dot com, andre__ in #maemo
*Intended audience: Everyone (Users, Developers, Non-coders, ...)
*Talk type: Presentation (and discussion/BoF after that?)
*Abstract/description
: Provide an overview of the current situation in maemo.org Bugzilla and Brainstorm (stats, numbers, success cases), its people (Bugsquad), workflows, problems (especially with regard to Nokia & community participation). Inform how to participate (report in bugzilla / brainstorm; bugsquad) and how it can help Nokia developers&managers and the maemo.org community to be more productive in the Maemosphere.
*Additional Information
: I always fail to convince my laptop to work with beamers at conferences. Be warned. ;-)
*Author bio
: Andre Klapper is the maemo.org Bugmaster and works for Openismus GmbH. He is also part of the GNOME Release Team & Bugsquad.

=== Adapting GNOME applications to Maemo Fremantle ===
*Author: Joaquim Rocha, jrocha at igalia dot com
*Intended audience: Application Developers
*Talk type: presentation
*Abstract/description
: Porting GNOME applications to Maemo Fremantle is not just recompiling and make it run on the device. For many applications, a considerable adaptation in they're UI is needed.

: I'm proposing a presentation having as its base the port of the Eye of GNOME for Maemo, explaining the intentions behind each change and the usage of Hildon 2.2 widgets to accomplish those.

*Author bio
: Joaquim Rocha has worked from web programming to OCR, desktop and mobile programming and is a proud Open Source an Linux advocate. He's now doing all this while working for Igalia. When he's not coding he's listening to metal, watching movies, playing console games or having a nice cold beer if the weather demands so.

=== Tracker: Dial M for Metadata ===
*Ivan Frade <ifrade@gnome.org>, Iridian Kiiskinen <ext dash iridian dot kiiskinen at nokia dot com>
*Intended audience: application developers/platform developers
*Presentation
*Abstract/description
: Tracker is a freedesktop project (with GNOME roots) included in the maemo platform for the first time in maemo5. In fremantle it is a simple index engine with support for basic metadata. For harmattan Tracker takes a great leap forward becoming a central storage for *user information*. The important data for the user (contacts, messages, multimedia, ...) will not only be stored in an application independent way, but also in a "linkable" format. This enables a new user experience: it makes it possible to integrate contacts everywhere, mix IM/email/twitter history of a contact, and so on.

In this presentation, Application developers can see how data is linked and obtained from Tracker to enrich their applications; platform contributors can learn how to integrate new information sources.

*Author bio
: Ivan Frade is an open source enthusiast who works in nokia building a data management solution for maemo based on tracker. On his free time, helps the world to tag properly their Mp3s with his pet-project.
: Iridian Kiiskinen started working in Nokia Maemo group since end of 2008, and is a newly enthusiastic open source developer migrating from the academic world.

=== Canola: Beyond the media playback ===
*Author: [http://maemo.org/profile/view/etrunko Eduardo Lima (Etrunko)]
*Intended audience: Users
*Talk type: Presentation/Round Table
*Abstract/description
: The first half of this session, will give a quick presentation of some "advanced" features of Canola and the various possibilities of expanding the software and most importantly, the user experience. The second part will be dedicated to an open discussion with the audience about missing/wished features, critics and suggestions.
*Author bio
: Open Source Software enthusiast, involved with Maemo since the very beginning (mid 2005), and had the opportunity to be part of the first Maemo Community Council. Started porting various GTK+/GNOME applications (Gnumeric, Evince, Abiword, Leafpad, Xournal, etc), to the platform. Worked on the first version of Carman, written in Python + GTK. After that, joined the team developing the Canola media player, coding and maintaining its packages for Maemo since then. Also maintains packages of the Enlightenment Foundation Libraries (EFL) for Maemo. Works for openBossa/INdT, where has been having the opportunity to present and talk about Maemo in events in Brazil and worldwide.

=== Hands-on development with Nokia Web Runtime ===
* Oren Levine, < oren dot levine at nokia.com >
* Intended audiences: application developers and advanced users
* Talk type: presentation
* Abstract/description
: Live demonstration of Nokia Web Runtime (WRT) widget development using the WRT plug-in to Aptana Studio, a popular free Web development tool based on Eclipse. I'll show how WRT lets you use standard HTML JavaScript, and CSS to create lightweight applications quickly at low cost. If you have a device that supports the WRT, you can leave the session with a new widget!

*Author bio
: Oren Levine is a Senior Technology Marketing Manager in Nokia's Devices organization, responsible for promoting Nokia’s Web developer offering. Oren worked for over 10 years as a software engineer and architect before joining Nokia in 2001, gaining experience in many areas including 3D graphics, machine translation, Web application development and database design.

=== The Qt Mobility Project ===
*Author: Alex Luddy, alexander.luddy at nokia dot com
*Intended audience: application and platform developers
*Talk type: presentation
*Abstract/description
: The Qt Mobility project is developing new Qt APIs. These APIs will greatly improve the Qt developer offering, particularly for developers targetting mobile platforms such as Maemo. The APIs cover areas such as Location, Contacts, Messaging and Bearer Management. Usage of cross-platform Qt APIs makes it easy to port applications to other platforms supported by Qt
: The purpose of this presentation is to fuel your own ideas for how the new APIs can be used in your own projects. An overview of all the APIs planned for the first release shall be presented. The Location and Service Framework APIs will be demonstrated in detail through an example application.
*Author bio
: Alex Luddy is a product manager at the Australian office of Qt Development Frameworks. He has also been a software engineer and a professional services consultant during his 4 years with the organization. His main focus is embedded development. Alex Luddy has a Bachelor of Software Engineering from the Australian National University.

=== Publishing your software through maemo.org===
*Author: Niels Breet
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: This talk will give developers an overview of what services are available for them to publish their application through maemo.org. Going from autobuilder, package interfaces, community QA to Downloads and Extras.
*Author bio
: Niels Breet is the maemo.org webmaster, working on web services available at maemo.org.

=== Introducing the Harmattan UI framework ===
*Author: Tomas Junnonen - tomas.junnonen at nokia.com
*Intended audience: application developers
*Talk type: presentation
*Abstract/description:
: The transition from Fremantle to Harmattan will bring a new UI style to Maemo. The demand for fluid, animated user interfaces and new interaction mechanisms are putting new demands on the type of frameworks offered to application developers.
: This presentation gives a sneak peek at what's currently cooking in Harmattan. We will share our initial thoughts and plans regarding the future of the Maemo application framework.
*Author bio:
: Tomas has been working in Maemo since the original Nokia 770. Today he is the architect of the application framework, designing the next generation Maemo user interface framework.

=== Creating packages for the Maemo platform ===

* Jeremiah C. Foster <jeremiah at maemo dot org>
* Intended audience -> application developers and platform developers
* Talk type -> presentation
* This talk will go through packaging from beginning to end providing a template to use. While one cannot go into every corner case, we can cover the entire process for the average package. In this case we will describe the process for packaging a python app since those are quite common on the maemo platform.

* Author Bio

: I am the current "debmaster" at maemo.org and have been working with the debian perl team for several years now. I have been using debian for nearly a decade.

=== Intelligent Usage of Fremantle Location Framework For Location-aware Applications ===

*Quanyi Sun
*Intended audience: users/application developers/platform developers
*Talk type: presentation
*Abstract/description
: Abstract:
Location API is part of the Maemo 5 (Fremantle) API offerings. The location API for the first time now has introduced concept of hybrid locationing methods, i.e., supports of multiple locationing technologies seemlessly in a transparent way. In addition to the benefits of hybrid locationing methods, there are some issues, e.g., power consumption, that must be handled properly in order to maximize the benefits.

This presentation intends to hightlight the major issues when using location API, and provides best recommendations for developing location-aware applications in Maemo 5.

*Author bio:
Quanyi Sun has been working for Maemo as technical product owner in location area, with 13+ years of industrial experiences, e.g., in mission-critical realtime onboard software project in my early days.

=== The Maemo 5 Address Book ===
*Author: Travis Reiter travis dot reitter AT collabora dot co dot uk, Mathias Hasselmann mathias AT openismus dot com
*Intended audience: users and application developers
*Talk type: presentation
*Abstract/description

In Maemo 5, contacts are handled by several components that make up the
Address Book. In its first part, this talk will provide an overview of
the components in the new system, as well changes in the interface and
functionality of the Contacts application. A lot has changed since the
last major release, so this talk has a lot of interesting bits to cover!

The second part of this talk will focus on developers who want to
incorporate contacts in their applications. Address Book 5 includes a
powerful high-level library for accessing contacts on the system. If
your application needs to present all contacts on the system, find
specific ones, watch changes to the contacts, pick out avatars, start
conversations, or much more, it's all here. And this library,
libosso-abook, has become the ideal way to access contacts, so we'll
provide some tips on porting older Maemo applications based directly on
Evolution Data Server to libosso-abook.

*Author bio
Travis Reiter is a software developer at Collabora, Mathias Hasselmann is software developer at Openismus. Both spent alot of time on improving GNOME. For the last two years they worked on improving Maemo's Address Book.

=== Maemo and oFono ===

* By Rémi Denis-Courmont (remi dot denis-courmont at nokia dot com) and Aki Niemi (aki dot niemi at nokia dot com)
* For platform developers
* Presentation (could be shortened to lightning talk but...)
* oFono is an open source telephony stack for Linux. It provides an easy-to-use D-Bus interface and has support for a variety of cellular modem hardware, including Nokia cellular modems. The project is a joint effort between Intel and Nokia.

:How is it different from earlier attempts? What is it all about? What can you do with Ofono and Nokia N900?

* For demoing purpose, the presenter will need to use his own laptop and Nokia devices.

* Rémi Denis-Courmont currently works for Nokia, where he maintains the Phonet stack for the Linux kernel, the Maemo platform and the Ofono project. Outside Nokia, he's also been involved in the VideoLAN project.

[http://www.remlab.net/op/maemo2009.pdf Presentation material]

=== The future of GTK+/Hildon in Maemo Harmattan ===
* Alberto Garcia (_berto_) and Claudio Saavedra (csaavedra)
* Intended audience: developers
* Talk type: BoF
* Abstract/description:
: Nokia has recently announced that GTK+/Hildon, the official Maemo toolkit since the beginning of the project, will be replaced by Qt in the future Harmattan release.
: However, Nokia has also shown interest in the availability of a community-maintained version of GTK+/Hildon for this next Maemo release, so existing applications can be ported to the new devices and developers more familiar with this toolkit can write new applications for Harmattan.
: In this BoF we'll discuss the current situation of GTK+/Hildon in Fremantle, its future in the hands of the community and the challenges to overcome in order to create a decent release for Maemo Harmattan.
* Author bio
: Alberto Garcia loves computers since he got his first Sinclair ZX Spectrum. In the late 90s he began using GNU/Linux and in 2001 he co-founded Igalia, a Galicia-based free software company. He's currently working on the new version of the Hildon toolkit for the new release of Maemo, codenamed 'Fremantle'. Besides programming, Alberto also loves cinema, music and going to the beach.
: Claudio Saavedra is a chilean Computer Engineer, working at Igalia since 2008. He got involved in the GNOME project back in 2005 and is one of the developers of the Eye of GNOME Image viewer. Currently, he is also working in Maemo 5, codenamed 'Fremantle', developing the Hildon library and also maintaining other parts of the toolkit stack.

=== High-resolution image processing on Maemo devices ===
*Author: Alexander Bokovoy - alexander dot bokovoy AT nokia dot com
*Intended audience: application developers/platform developers
*Talk type: presentation
*Abstract/description

N900 is the first Maemo device with high resolution camera. While making photos with camera is an obvious use for it, resulted images are stored on the device and can be used by applications for other purposes as well. Mobile devices like N900 are quite constrained for image processing needs and special work is needed to minimize consumption of memory and processing resources.

The talk will cover camera application development in Maemo 5 and plans for common set of image editing functionality for high-resolution pictures in Maemo 6. We hope to create open and extensible platform-wide solution which can help all developers to better utilize constrained resources on mobile devices.

*Author bio

Alexander Bokovoy is a Senior Architect for Media Experience applications in Maemo Devices, Nokia. Prior joining Maemo he worked with IBM Linux Technology Center on data sharing projects, including high performance networking file systems. He is member of Samba Team since 2003.

=== Hacking officially unsupported Bluetooth profiles to work in Fremantle ===
*Johan Hedberg - johan.hedberg at nokia.com
*Intended audience: users,application developers,platform developers
*Talk type: presentation
*Abstract/description
: Fremantle doesn't come with out-of-the-box support of several Bluetooth profiles that are could in theory be supported with upstream components. These include e.g. DUN, HID and PAN. The presentation intends to be a hands-on session demonstrating how to enable support for these profiles through the act of changing config files and random hacking.
*Author bio
: Johan has been a software developer in the Maemo team ever since the first Maemo device, the 770 came out. His main responsibility area is Bluetooth and through active upstream involvement he has become a co-maintainer of BlueZ.

=== Git hands-on workshop ===
*Author name and contact details
*Intended audience (users/application developers/platform developers)
*Talk type (presentation/lightning talk)
*Abstract/description
: Abstract goes here. A two paragraph overview of the proposed talk content is sufficient.
*Additional Information (optional)
: Additional information on extra equipment you might need or something else goes here
*Author bio
: A short (1 paragraph) note about who the author is goes here

Documentation

2009-10-12T10:31:49Z

192.100.124.218: /* Maemo 5 */

= Maemo 5 =
* Documentation in the wiki:
**[[{{PAGENAME}}/Maemo_5_Developer_Guide|Maemo 5 Developer Guide]]
**[[{{PAGENAME}}/Maemo_5_Final_SDK|Maemo 5 Final SDK]]
**[[{{PAGENAME}}/devtools/maemo5| Maemo 5 Developer Tools]]
**[[{{PAGENAME}}/Maemo 5 Final SDK Installation | Maemo 5 Final SDK Installation Instructions]]
* Further information:
**[http://maemo.org/development/sdks/maemo_5_beta_sdk/ Maemo Beta SDK]
**[[Task:Maemo_roadmap/Fremantle|Fremantle roadmap]]
**[http://maemo.org/development/sdks/maemo_5_api_documentation/ Maemo 5 API reference]
** [http://wiki.maemo.org/Maemo5_clutter_performance Maemo 5 Clutter Performance]
* Maemo 5 Final SDK release source code - http://repository.maemo.org/pool/maemo5.0/free/

Maemo Summit 2009/Accommodation

2009-10-08T08:05:12Z

192.100.124.218: /* Shared Room Allocations */

We should offer people a range of accommodation options, from low-cost youth hostel beds to cheap hotels. Encourage people to stay close together.

== Checklist ==

* Draft recommended hotel & hostel list
** [http://www.hostelworld.com HostelWorld]: a reliable website where you can find cheap hostel. You can see on the map where they're placed so you can choose one close to the Summit.
**[http://www.ibishotel.com/gb/hotel-1556-ibis-amsterdam-centre/index.shtml Ibis Amsterdam Center Hotel]: for the sponsored participants and the big bunch of people happy with a price of ~146 €/night inc breakfast for a double room with twin beds (may be cheaper for single room).
**[http://www.westcordhotels.nl/hotels/Art-Hotel-Amsterdam**** Art Hotel Amsterdam]: recommended to those more interested in a 4 star hotel.
**[http://www.ibishotel.com/gb/hotel-5140-ibis-amsterdam-city-west/index.shtml Ibis Amsterdam City West Hotel]: A cheaper option, but further out. Price around 65€/night for a double room. I ordered via accorhotels.com and got the price 69/59/59 € for 3 nights starting at Thursday ([http://wiki.maemo.org/User:Asys3 asys3])

* Block book and/or obtain group rates
** Requires visiting hotel, asking for accommodation manager, and negotiating a group price.
** Sell the conference as important, high visibility, and argue that being a recommended hotel being a benefit for the hotel

* Put hotel list online
* Book hotel rooms pre-paid for sponsored attendees, maybe?

== Shared Room Allocations ==

We have 40 rooms booked for sponsored participants and special Nokia-related cases at [http://www.ibishotel.com/gb/hotel-1556-ibis-amsterdam-centre/index.shtml Hotel Ibis Amsterdam Centre].

* '''If you would like to share a double room with someone, please add your name to the table below.'''
* If you find yourself rooming with someone who's not your best choice, just remove yourself from the room and add it somewhere else. '''''No hurt feelings please. This will all work out.'''''

* '''The rooms are only booked for 3 nights(Thur-Sat), those how want to stay more nights should contact the hotel asap, and pay for the extra nights.'''

{| border="5"
! Room #
! Roommate 1
! Roommate 2
! Special Notes/Considerations
|-
| 1
| [[User:timsamoff|Tim Samoff]]
| [[User:sjgadsby|Stephen Gadsby]]
|
|-
| 2
| [[User:texrat|Randall Arnold]]
| [[User:eipi|Sanjeev Visvanatha]]
| Looking for new roomie-- zerojay can't make it :(
snoring not an issue. I'm no zerojay - will try to be a good roomie :)
|-
| 3
| [[User:Jaffa|Andrew Flegg]]
| [[User:andy80|Andrea Grandi]]
| Non-smoking
|-
| 4
| [[User:Lbt|David Greaves]]
| [[User:fiferboy|Andrew Olmsted]]
|
|-
| 5
| [[User:framstag|Tim Teulings]]
| [[User:glezos|Dimitris Glezos]]
| Non-Smoking
|-
| 6
| [[User:qole|Alan Bruce]]
| [[User:achipa|Attila Csipa]]
|
|-
| 7
| [[User:conny|Cornelius Hald]]
| [[User:thp|Thomas Perl]]
|
|-
| 8
| [[User:bundyo|Kamen Bundev]]
| [[User:frethop|Mike Jipping]]
| (I'm a snorer, beware :-P)
|-
| 9
| [http://maemo.org/profile/view/mike_morrison mike morrison]
| [[User:khertan|Benoît HERVIER]]
| non-smoking.
|-
| 10
| [[User:vdvsx|Valério Valério]]
|
|
|-
| 11
| [http://maemo.org/profile/view/plastun/ Max Usachev]
| [http://maemo.org/profile/view/vasvlad/ Vlad Vasiliev]
| Non-smoking
|-
| 12
| Aapo Rantalainen
| [[User:hhedberg|Henrik Hedberg]]
| Non-smoking
|-
| 13
| [[User:johnx|John Bloom]]
| [[User:rm_you|Adam Harwell]]
| Non-smoking
|-
| 14
| [[User:aikipy|Raluca Pataliu]]
| [[User:azbuky|Iulian Blajut]]
|
|-
| 15
| [[User:Tomaszd|Tomasz Dominikowski]]
| [[User:stskeeps|Carsten Munk]]
|
|-
| 16
| [[User:andrei1089|Andrei Mirestean]]
| [[User:apopelo|Andrey Popelo]]
|
|-
| 17
| [[User:mikkov|Mikko Vartiainen]] (Thu-Sat)
| [[User:edgar2|Thomas Pakalén]]
|
|-
| 18
| [[User:etrunko|Eduardo Lima (Etrunko)]]
| [[User:kenneth|Kenneth Rohde Christiansen]]
| Leaving on Tue 13th Oct
|-
| 19
| [[User:aboaboit|Andrea Borgia]]
| [[User:Matteone|Matteo Nerozzi]]
| Leaving on Tue 13th Oct... will decide later for extra nights!
|-
| 20
| [[User:ukki|Janne Mäkinen]]
| [[User:onion|Kaj-Michael Lang]]
|
|-
| 21
| [[User:n8willis|Nathan Willis]] (Fri-Mon)
| [[User:segphault|Ryan Paul]]
|
|-
| 22
| [[User:vudentz|Luiz Augusto von Dentz]]
| [[User:barbieri|Gustavo Sverzut Barbieri]]
|
|-
| 23
| [[User:fms|Marat Fayzullin]]
| [http://maemo.org/profile/view/twaelti/ Tom Waelti]
|
|-
| 24
| [[User:thenokiablog|Mark Guim]]
|
| wife is w/ me. if possible, requesting if we can be only ones in the room.
|-
| 25
| Brecht Fourneau
| Miquël Vermeulen
| Mobilejuice
|-
| 26
| Lennart Poettering
| Marc-Andre Lureau
|
|-
| 27
| Sampo Savola(Thu-Sun)
| Lauri Võsandi
|
|-
| 28
| Tuomas Kulve
| Aino Kulve
| wife is w/ me.
|-
| 29
|[[User:baloo|Jamie Bennett]]
|[[User:rsperberg|Roger Sperberg]]
|RogerS staying Sunday night also.
|-
| 30
| Till Harbaum
| [[User:raul|Raul Herbster]]
|
|-
| 31
| Dieter Plaetinck
| Bert Desmet
|
|-
| 32
| Marijn Kruisselbrink
| Gary Birkett(Wed-Mon)
|
|-
| 33
| [[User:b0unc3|Daniele Maio]]
| [[User:skler|Mauro Foti]]
|
|-
| 34
| Naba Kumar
| Nokia
|
|-
| 35
| Yan Minagawa
| Jim Cognito
|
|-
| 36
| [http://maemo.org/profile/view/nnod.html Donn Morrison]
|[http://maemo.org/profile/view/jeninfanti.html Jennifer Infanti]
| Small bricks
|-
| 37
| Oliver Mcfadden
| Nokia
|
|-
| 38
| Ed Bartosh
| Nokia
|
|-
| 39
| Igor Stoppa
| Nokia
|
|-
| 40
| [[User:juarezjunior|Juarez Junior]]
| Nokia
| Non-smoking
|}

*'''Please don't add more lines in the table, we only have 40 rooms booked'''

== Who needs a room? ==

Please say if you prefer a hotel (or are happy with a hostel), if you need a double room (i.e. because you're bringing your wife/gf) or a single (if you don't want to share) or shared (if you're happy to share).

* '''If you would like to share a double room with someone, please add your name to the [[#Shared_Room_Allocations|Shared Room Allocations]] section above.'''

{| border="5"
! Name
! Hotel/hostel/other
! Type of room
! Arriving
! Leaving
! Sponsorship?
|-
| [[User:edgar2|Thomas Pakalen]]
| hotel
| Single/Shared
| Fri 9th October
| Sun 11th October
| not applied
|-
| [[User:twaelti|Thomas Waelti]]
| hotel/hostel/whatever
| Single/Shared
| Thu 8th October
| Sun 11th October
| not applied
|-
| [[User:harbaum|Till Harbaum]]
| Hotel
| Single
| Oct 8
| Oct 12
| Approved
|-
| [[User:vdvsx|Valerio Valerio]]
| Hotel/hostel/whatever
| Single/Shared
| October 7,
| October 12, 2009
| Approved
|-
| [[User:juarezjunior|Juarez Junior]]
| Hotel/hostel/whatever
| Single/Shared
| October 7th,
| October 11th, 2009
| Approved
|-
| [[User:barbieri|Gustavo Barbieri]]
| Hotel/hostel/whatever
| Single/Shared
| October 8th (from Sao Paulo KL792),
| October 11th (to Paris)
| Approved
|-
| [[User:texrat|Randall Arnold]]
| Hotel/hostel/whatever
| Single/Shared
| Thur 8th October
| Mon 12th October
| Approved
|-
| [[User:nirave|Nirave Gondhia]] *
| Hotel
| Single room
| Thur 8th October
| Mon 12th October
| Applied for
|-
| [[User:andy80|Andrea Grandi]]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [[User:lcuk|Gary Birkett]]
| Hotel
| Single/Shared at a push (late night coding..)
| October 7,
| October 12, 2009
| Approved
|-
| [[User:achipa|Attila Csipa]]
| Hotel/hostel
| Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [[User:timsamoff|Tim Samoff]]
| Hotel
| Single/Shared
| Wed 7th Oct
| Tues 13th Oct
| Approved
|-
| [[User:sjgadsby|Stephen Gadsby]]
| Hotel
| Single/Shared
| tbd
| tbd
| Approved
|-
| [[User:Generalantilles|Ryan Abel]]
| Hotel
| Single/Shared
| tbd
| tbd
| Approved
|-
| [[User:conny|Cornelius Hald]]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [[User:stskeeps|Carsten Munk]]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [[User:qole|Alan Bruce]]
| Hotel
| Single/Shared
| Wed Oct 6
| Tue Oct 13
| Approved
|-
| [[User:bundyo|Kamen Bundev]]
| Hotel/Hostel
| Single preferred but shared okay
| October 9, 2009
| October 11, 2009
| Approved
|-
| [[User:thenokiablog|Mark Guim]]
| Hotel
| Double w. wife
| October 8, 2009
| October 12, 2009
| Approved
|-
| [[User:ukki|Janne Mäkinen]]
| Hotel/hostel
| Single/shared
| October 8, 2009
| October 11, 2009
| Approved
|-
| [[User:eipi|Sanjeev Visvanatha]]
| Hotel
| Single/shared
| Oct 9 (7am)
| Oct 11
| Approved
|-
| [[User:thp|Thomas Perl]]
| Hotel
| Single/shared
| October 8, 2009
| October 11, 2009
| Approved
|-
| [[User:fiferboy|Andrew Olmsted]]
| Hotel
| Single/shared
| October 8, 2009
| October 12, 2009
| Approved
|-
| [http://maemo.org/profile/view/plastun/ Max Usachev]
| Hotel/Hostel
| Shared
| October 8, 2009
| October 12, 2009
| Approved
|-
| [[User:Hhedberg|Henrik Hedberg]]
| Hotel/Hostel
| Shared
| October 8, 2009
| October 11, 2009
| Approved
|-
| Aapo Rantalainen
| Hotel/Hostel
| Shared
| October 8, 2009
| October 11, 2009
| Approved
|-
| [http://maemo.org/profile/view/vasvlad/ Vlad Vasiliev]
| Hotel/Hostel
| Shared
| October 8, 2009
| October 12, 2009
| Approved
|-
| [http://maemo.org/profile/view/baloo/ Jamie Bennett]
| Hotel
| Single (other commitments may require me to return funky hours).
| tbd
| tbd
| Approved
|-
| [http://maemo.org/profile/view/glezos/ Dimitris Glezos]
| Hotel/Hostel
| Shared
| October 8, 2009
| October 11, 2009
| Approved
|-
| [http://maemo.org/profile/view/khertan/ Benoît HERVIER]
| Hotel/Hostel
| Shared
| October 9, 2009
| October 11, 2009
| Approved
|-
| [http://maemo.org/profile/view/andrei1089/ Andrei Mirestean]
| Hotel/Hostel
| Shared
| October 8, 2009
| October 12, 2009
| Approved
|-
| [http://maemo.org/profile/view/tomaszd/ Tomasz Dominikowski]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [http://maemo.org/profile/view/fms/ Marat Fayzullin]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [http://maemo.org/profile/view/mike_morrison mike morrison]
| Hotel/Hostel
| Single/Shared
| Thur 8th October
| Mon 12th October
| Approved
|-
| [http://maemo.org/profile/view/sampp Sampo Savola]
| Hotel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [http://maemo.org/profile/view/onion Kaj-Michael Lang]
| Hostel
| Single/Shared
| Thur 8th October
| Sun 11th October
| Approved
|-
| [[User:etrunko|Eduardo Lima (Etrunko)]]
| Hotel
| Single/Shared
| Thur 8th October
| Tue 13th October
| Approved
|-
| [[User:kenneth|Kenneth Rohde Christiansen (kenneth)]]
| Hotel
| Single/Shared
| Thur 8th October
| Tue 12th October
| Approved
|-
| [[User:Detronizator|Ivan De Marino (detro)]]
| Hotel
| Single/Shared
| Thur 8th Oct evening
| Mon 12th Oct morning (to confirm)
| Approved
|-
| [[User:n8willis|Nathan Willis]]
| Hotel
| Single preferred, to write stories at night
| Fri 9th Oct
| Mon 12th Oct
| Approved
|-
| [[User:vudentz|Luiz Augusto von Dentz (Vudentz)]]
| Hotel
| Single/Shared
| Thur 8th Oct evening
| Tue 13th Oct
| Approved
|-
| [[User:b0unc3|Daniele Maio (b0unc3)]]
| Hotel
| Single/Shared
| Thur 8th Oct
| Mon 12th Oct
| no
|-
| [http://maemo.org/profile/view/apopelo/ Andrey Popelo]
| Hotel/Hostel
| Single/Shared
| October 8, 2009
| October 12, 2009
| Approved
|-
| Lennart Poettering
| Hotel
| Single/Shared
| Thu 8th Oct
| Sun 11th Oct
| Approved
|-
| Ryan Paul
| Hotel
| Single
| October 8
| October 12
| Approved
|-
| Marc-Andre Lureau
| Hotel
| Single/Shared
| Thu 8th Oct
| Sun 11th Oct
| not applied
|-
| [[User:rsperberg|Roger Sperberg]]
| Hotel
| Single/Shared
| Thu 8th October
| Mon 12th October
| Approved
|}

(*) - Not registered

== Who's staying where? ==
{| border="5"
! Name
! Hotel
! Arriving
! Leaving
! Cost
! Sponsorship?
! Notes (e.g. spare place, etc.)
|-
| [[User:lardman|Simon Pickering]]
| Hotel Ibis Amsterdam Centre
| Thur 8th October
| Mon 12th October
| 510.30 Euros for 4 nights (w/out breakfast)
| Applied for
| Staying with my wife
|-
| [[User:mgedmin|Marius Gedminas]]
| Hotel Arts (Golden Tulip Amsterdam Art)
| Thur 8th October
| Mon 12th October
| 440 Euros for 4 nights (w/out breakfast)
| No
| free wifi!
|-
| [[User:gcobb|Graham Cobb]]
| Hotel Arts
| Thur 8th October
| Sun 11th October
| 310 Euros for 3 nights (w/out breakfast)
| No
| Single room
|-
| [[User:riussi|Juha Ristolainen]]
| Hem Hotel Amsterdam
| Thur 8th October
| Sun 11th October
| 313 Euros for 3 nights (w/out breakfast)
| No
| double room with two attendees
|-
| [[User:jeremiah|Jeremiah C. Foster]]
| Hotel Arts
| Thur 8th October
| Sun 11th October
| 387 Euros for 3 nights (w/out breakfast)
| No.
| My wife will be with me.
|-
| [[User:anidel|Aniello Del Sorbo]]
| A whole house in Bethanienstraat
| Sat 10th October
| Tue 13th October
| 270€ Euros for 3 nights (w/out breakfast)
| Applied for/Accepted
| Staying with my partner (sharing the house with a couple of friends)
|-
| [[User:lma|Lucas Maneos]]
| Hotel Arts
| Thur 8th October
| Sun 11th October
|
| No.
|
|-
| [[User:Detronizator|Ivan De Marino]]
| Hotel Arts (Golden Tulip Amsterdam Art)
| Thur 8th October
| Mon 12th October
|
| No
| Would be great to hook up after the Summit to take a walk around Amsterdam. Anyone?
|
|-
| [[User:dneary|Dave Neary]]
| Ibis Centrum
| Thur 8th October
| Sun 11th October
|
| No.
|
|-
| [[User:gosia|Malgorzata Ciesielska]]
| Ibis Amsterdam Centre
| Thur 8th October
| Sun 11th October
|
| No
|
|-
| [[User:rsuplido|Reggie Suplido]]
| Renaissance Amsterdam
| Thur 8th October
| Mon 12th October
| 243€ for 4 nights (wife discount) (w/o breakfast)
| Yes
| Staying with wife
|}

Documentation/Maemo 5 Developer Guide/Using Data Sharing/Sharing Plug-in

2009-10-06T12:06:35Z

192.100.124.218: /* Sharing Internals */

=Sharing Plug-in Creation=
Maemo 5 introduces a new library for handling Sharing related information and services. This chapter will walk you through the process of creating a sharing plug-in using a template plug-in as example. Basic knowledge of debian development and working in scratchbox environment is needed in order to follow these guides.

Plugin example is located here [https://garage.maemo.org/svn/maemoexamples/trunk/data-sharing-plugin/ Data Sharing Plugin example]

Detailed API documentation is available in sharing-plugin-doc package in gtk-doc format.

==Sharing User Interfaces==
Sharing application abstracts the file sharing and implements common parts needed for file sharing application. Sharing Application service support can be extended by using Sharing Plug-ins. These plug-ins can be created by any 3rd party developer. The plug-ins should implement the Sharing Plug-in API functions and define some parameters to service definition XML file.

Figure 1 below shows Sharing accounts dialog opened from the control panel. With the Sharing accounts, you can create a new Sharing account or edit an existing one. If you install a custom Sharing plug-in, you can see the service it provides in the "Select service list" when creating a new Sharing account.

[[Image:SharingAccounts.png]]

''Figure 1: Sharing Accounts''

Figure 2 shows the Sharing Dialog user interface that is used to share images to the selected account on some service. The images displayed can come for example from Photos application or from the device camera. You can choose the account created for your service from the "Account" combo box which holds all existing Sharing accounts.

[[Image:SharingDialogInterface.png]]

''Figure 2: Sharing Dialog User Interface''

==Getting Familiar With Target Service API==
Many web services provide APIs that are available for 3rd party developers. In this tutorial, we focus on services that provide APIs for image and video uploads. It is possible to give title, description and tags for the images using the common service API.
Sharing supports image scaling and meta data filtering as common options for any service. Sharing Plug-ins can have service specific options, like privacy. These settings can be accessed through Options dialog (in Figure 2.)

==Getting Your Dummy Plugin To Sharing Menus==
As a pre-requisite, you will need a working Maemo 5 SDK to continue further.
We will first install the Sharing Plug-in template:
*Obtain the template source code ''sharing-plugin-template-0.1.tar.gz'' from <URL HERE>. It contains a good start up file structure for the plug-in creation.
*Extract and build the package from the folder using command:
./autogen.sh; dpkg-buildpackage -rfakeroot -d
*Install the package built to your Scratchbox environment or to device if it was build with ARM target.
*The template dummy service should be now visible in the Sharing account when creating new accounts.

<div style="border: 2px solid rgb(255, 215, 0); background-color: rgb(252, 233, 79); margin-left: 25px; margin-right: 25px; padding: 2px"> N.B: Note that this template plug-in does not send any data before you write the implementation for it. </div>

=Editing Template Plug-in=
In this section, we peek under the hood by opening the files found from the template plug-in and get familiar with Sharing classes that are used in the Sharing Plugin API functions.

==Sharing Internals==
Figure 3 shows the general overview of how Sharing Plug-in connects to Sharing Application using the Sharing Plug-in API. The basic plug-in components are the service definition file and the plug-in library. The Application Sharing-Dialog is used to create ''SharingEntries'' that are shared by ''SharingManager''. Sharing Account Manager implements the Sharing Accounts. Libsharing is library for all common Sharing functionality.

[[Image:SharingPluginAPI.jpg]]

''Figure 3: Sharing Plugin API''

Figure 4 shows the common ''Sharing'' classes found in ''libsharing'' that you would use while creating the plug-in.
''SharingTransfer'' is the object that contains all the data of sharing task, overall status of the transfer process for one set of shared files.
''SharingEntry'' contains the the ''SharingEntryMedia'' that are the selected files. It also knows the ''SharingAccount'' that is the target of sharing.
''SharingAccount'' contains the username and password along with other parameters that you have to save for your service's accounts. It also has the information about ''SharingService'' which is registered to the ''SharingAccount''.

[[Image:LibSharingClasses.jpg]]

''Figure 4: Libsharing classes''

To see more detail the sharing classes you can browse to [https://garage.maemo.org/svn/maemoexamples/trunk/data-sharing-plugin/ Sharing plugin example]

==Service XML File==
Service definition file, data/template.service.xml.in is the starting point for plug-in loading. It defines the library that implements Sharing Plug-in API functions, the sign up URL for totally new account creation by using web browser, service name, icon file names and some basic information from plug-in.

<?xml version="1.0" encoding="UTF-8"?>
<service plugin="libtemplate.so" provider="Me">

<accounts plugInSetup="0" plugInEdit="0">
<signup>www.maemo.org</signup>
<password maxlen="32"/>
</accounts>

<ui>
<name>Template</name>
<icon type="post">@servicesdir@/template-post.png</icon>
<icon type="setup">@servicesdir@/template-setup.png</icon>
<options>
<option id="privacy" type="enumeration" default="private">
<caption domain="osso-sharing-ui" key="share_bd_options_privacy"/>
<value id="private" domain="osso-sharing-ui" key="share_fi_options_privacy_private"/>
<value id="public" domain="osso-sharing-ui" key="share_fi_options_privacy_public"/>
</option>
</option>
</ui>
</service>

''File 1: Example service definition XML file''

The prefix of name "template.service.xml.in", "template" in this case, defines the id of the plugin. The "plugin" value in the service definition defines the library that implements the Sharing Plug-in API. In this example file the library is libtemplate.so in the above example. "Provider" is the developer name, nick etc. In "accounts", you define the plug-in account setup and edit flows described more in detail in the coming sections. Sign up URL is the URL that is opened in the browser when a new account is being created for a service.

==Account Setup User Interface Flow==
Sharing accounts can either create a default flow where "username" and "password" parameters are set to the account or an optional custom flow. In File 1, the "accounts" tag has a parameter "plugInSetup". If it is set to "1", Sharing Accounts will call the Sharing Plugin API function "sharing_plugin_interface_account_setup" to create UI flow; it will use the default flow.
You can see the difference between UI flows when creating Flickr and Ovi account. Ovi uses the default flow and Flickr uses it's own UI flow.

<tt>SharingPluginInterfaceAccountSetupResult sharing_plugin_interface_account_setup (GtkWindow* parent, SharingService* service, SharingAccount** worked_on, osso_context_t* osso)</tt>

If you decide to create your own account setup flow, please try to keep the same UI look as in other Sharing dialogs.

==Account Validation==
Account validation is needed to reduce error cases in actual sending process. Of course you can use the dummy function at template plug-in, but for better user experience this function is recommended to be implemented so that Sharing Account account information is really validated against the service when new account is created.

Next function is called after sharing_plugin_interface_account_setup call ends or when default account setup flow is done (=when "Validate" button is pressed).

<tt>
SharingPluginInterfaceAccountValidateResult sharing_plugin_interface_account_validate (SharingAccount* account, ConIcConnection* con, gboolean *cont, gboolean* dead_mans_switch)</tt>

In the last phase of account creation, the account must be validated. Sharing Plug-in API ''sharing_plugin_interface_test_account'' is the function called in the validation phase of the account creation flow.
Usually web services have a phase in account creation where you have put the needed information from your account, only then you get the actual credentials to upload images if your account information is valid. This is the phase that is implemented in the Sharing Plug-in API function.

==Account Editing User Interface Flow==

Sharing Accounts support here too either default flow where “username” and “password” parameters are edited or optional custom edit UI flow. The wanted flow can be set by setting the parameter "plugInEdit" from the service definition file either to "0" or to "1" where "0" means the default flow and "1" plug-in flow.

The default flow can be used when you need only username and password to get needed information for sending. The plug-in flow is used when you need more than this or customised account validation flow. You can see the difference between UI flows here too when editing Flickr and Ovi accounts.

Next function must be implemented only when plug-in account setup is used (when "plugInSetup" is set to "1"):
<tt>SharingPluginInterfaceEditAccountResult sharing_plugin_interface_edit_account (GtkWindow* parent, SharingAccount* account, ConIcConnection* con, gboolean* dead_mans_switch)</tt>

==Sending Functionality==

<tt>SharingPluginInterfaceSendResult sharing_plugin_interface_send (SharingTransfer* transfer, ConIcConnection* con, gboolean* dead_mans_switch)</tt>

After pressing the 'Share' button in Sharing dialog (Figure 2.), the data is put into the Sharing Outbox (can be seen under /home/user/MyDocs/.sharing/outbox/). Sharing manager process is started and the status menu gets the icon to process the new Sharing Entry.
''SharingHTTP'' provides an API to create common HTTP requests.
In order to create a better user experience following things are good to be implemented after you get the basic functionality working in your plug-in:
*Set progress of sending with sharing_transfer_set_progress between 0 and 1 to estimate the current transfer time / total transfer time.
*Set sent to ''SharingEntryMedia'' with ''sharing_entry_media_set_sent'' when file sending is done and check the send value with ''sharing_entry_media_get_sent'' to prevent sending same files multiple times for example in reboot scenarios.
*Poll cancel flag time to time, for example in curl or ''SharingHTTP'' progress function to end transferring when needed. Use ''sharing_transfer_continue'' to get the continue flag bit.
*If you are using ''libcurl'' instead of ''SharingHTTP'', please listen to ''conic'' events to disconnect transfer when no connection available. It returns with 'no connection' return value in this case.

Next some example source for common tasks found in usual sending functionality:
==== Example sending loop ====

When you process SharingEntryMedias from the SharingEntry you propably end up with loop where you go the list of SharingEntryMedias through. Here is a raw example, where some example lines commented out with "//".
<tt>

for (GSList* p = sharing_entry_get_media (entry); p != NULL; p = g_slist_next(p)) {
SharingEntryMedia* media = p->data;
/* Process media */
if (!sharing_entry_media_get_sent (media)) {
/* Post media */
//guint result = my_send_task_post_function (my_send_task, media);
/* Process post result */
if (result == 0 /* EXAMPLE: MY_SEND_RESULT_SUCCESS */) {
/* If success mark media as sent */
sharing_entry_media_set_sent (media, TRUE);
/* And mark process to your internal data structure */
//my_send_task->upload_done += sharing_entry_media_get_size (media);
} else {
/* We have sent the file in last sharing-manager call */
//my_send_task->upload_done += sharing_entry_media_get_size (media);
}
}
}

</tt>

==== Example tags string ====
Usually services accept the tags in their API to be added to images. Here is example source to create nice string about tag information to be put where ", " string used as separator. If service supports also geo tagging you should develop this source further by checking the tag type also.
<tt>

static gchar* create_tags_str (const GSList* tags)
{
gchar* ret = NULL;
for (const GSList* p = tags; p != NULL; p = g_slist_next (p)) {
SharingTag* tag = (SharingTag*)(p->data);
const gchar* tmp = sharing_tag_get_word (tag);
if (tmp != NULL) {
gchar* new_ret = NULL;
if (ret != NULL) {
new_ret = g_strdup_printf ("%s, %s", ret, tmp);
g_free (ret); /* old return is freed */
} else {
new_ret = g_strdup (tmp);
}
ret = new_ret;
}
}
return ret;
}
gchar* tags = create_tags_str (sharing_entry_media_get_tags (media));
</tt>

==== SharingHTTP example ====
SharingHTTP is ment to be used for HTTP transfers. It is probably easier to use this than libcurl and libconic straightly in common cases. Give it a try at least if you are not familiar with libcurl!

<tt>
SharingHTTP * http = sharing_http_new ();
SharingHTTPRunResponse res;
res = sharing_http_run (http, "http://example.com/post");
if (res == SHARING_HTTP_RUNRES_SUCCESS) {
g_print ("Got response (%d): %s\n", sharing_http_get_res_code (http),
sharing_http_get_res_body (http, NULL));
} else {
g_printerr ("Couldn't get stuff from service\n");
}
sharing_http_unref (http);
</tt>

==Uninstallation==
Libsharing provides sharing-account-remover binary that can be used to clean Sharing Accounts created for your plugin. This binary is run by debian/ dir's prerm script. Prerm scripts are run just before the package is uninstalled. Change the plugin id from sharingplugintemplate to match your plug-in id in the script. Your plug-in's id is the service definitions files prefix. For template.service.xml, the prefix is "template".

Example prerm script:
<tt>
#!/bin/sh
# You can use sharing-account-remover to remove the accounts at plugin
# uninstallation
if [ "$1" = "remove" ]; then
/usr/bin/sharing-account-remover template
fi
</tt>

=Testing your plugin=
After setting up your scratchbox environment you can start using and testing your own plugin.

Sharing framework consists following packages:

libsharing-plugin-dev
libsharing0
sharing-manager
sharing-account-manager
sharing-dialog

All the needed packages should be installed along with nokia-binaries.

'''Important:''' When testing inside scratchbox remember to start the signond daemon after the desktop is started. Signond is used for storing the account information and it's needed in order to get Sharing framework working properly

[sbox] > signond &

Also remember to install the debian .deb package build from your sources.

Creating sharing account is started from setting.

settings -> Sharing accounts -> New

Select your service and create new account. After one account is created you can use ImageViewer for sharing images and MediaPlayer for sharing video files.

=Sharing your plugin with others=
Maemo Extras repository is the best place for your plug-in if you want to get users for it. More information on how you can upload packages to Extras repository can be found [[http://wiki.maemo.org/Uploading_to_Extras here]].

Before uploading plugin to public repositories make sure you have updated the debian configuration files to match your information under ./debian folder.

Also make sure that the section is set to user/other. This way the package will be installable by application manager. Below example version of debian control file.

Source: sharing-plugin-template
Section: user/other
Priority: optional
Maintainer: Maemo Team <xxxx@maemo.org>
Build-Depends: debhelper (>= 5.0.0),
libgtk2.0-dev, libglib2.0-dev,
libconic0-dev, libosso-dev,
libsharing-plugin-dev
Standards-Version: 3.8.0

Documentation/Maemo 5 Developer Guide/Using Data Sharing/Sharing Plug-in

2009-10-06T12:05:04Z

192.100.124.218: /* Testing your plugin */

=Sharing Plug-in Creation=
Maemo 5 introduces a new library for handling Sharing related information and services. This chapter will walk you through the process of creating a sharing plug-in using a template plug-in as example. Basic knowledge of debian development and working in scratchbox environment is needed in order to follow these guides.

Plugin example is located here [https://garage.maemo.org/svn/maemoexamples/trunk/data-sharing-plugin/ Data Sharing Plugin example]

Detailed API documentation is available in sharing-plugin-doc package in gtk-doc format.

==Sharing User Interfaces==
Sharing application abstracts the file sharing and implements common parts needed for file sharing application. Sharing Application service support can be extended by using Sharing Plug-ins. These plug-ins can be created by any 3rd party developer. The plug-ins should implement the Sharing Plug-in API functions and define some parameters to service definition XML file.

Figure 1 below shows Sharing accounts dialog opened from the control panel. With the Sharing accounts, you can create a new Sharing account or edit an existing one. If you install a custom Sharing plug-in, you can see the service it provides in the "Select service list" when creating a new Sharing account.

[[Image:SharingAccounts.png]]

''Figure 1: Sharing Accounts''

Figure 2 shows the Sharing Dialog user interface that is used to share images to the selected account on some service. The images displayed can come for example from Photos application or from the device camera. You can choose the account created for your service from the "Account" combo box which holds all existing Sharing accounts.

[[Image:SharingDialogInterface.png]]

''Figure 2: Sharing Dialog User Interface''

==Getting Familiar With Target Service API==
Many web services provide APIs that are available for 3rd party developers. In this tutorial, we focus on services that provide APIs for image and video uploads. It is possible to give title, description and tags for the images using the common service API.
Sharing supports image scaling and meta data filtering as common options for any service. Sharing Plug-ins can have service specific options, like privacy. These settings can be accessed through Options dialog (in Figure 2.)

==Getting Your Dummy Plugin To Sharing Menus==
As a pre-requisite, you will need a working Maemo 5 SDK to continue further.
We will first install the Sharing Plug-in template:
*Obtain the template source code ''sharing-plugin-template-0.1.tar.gz'' from <URL HERE>. It contains a good start up file structure for the plug-in creation.
*Extract and build the package from the folder using command:
./autogen.sh; dpkg-buildpackage -rfakeroot -d
*Install the package built to your Scratchbox environment or to device if it was build with ARM target.
*The template dummy service should be now visible in the Sharing account when creating new accounts.

<div style="border: 2px solid rgb(255, 215, 0); background-color: rgb(252, 233, 79); margin-left: 25px; margin-right: 25px; padding: 2px"> N.B: Note that this template plug-in does not send any data before you write the implementation for it. </div>

=Editing Template Plug-in=
In this section, we peek under the hood by opening the files found from the template plug-in and get familiar with Sharing classes that are used in the Sharing Plugin API functions.

==Sharing Internals==
Figure 3 shows the general overview of how Sharing Plug-in connects to Sharing Application using the Sharing Plug-in API. The basic plug-in components are the service definition file and the plug-in library. The Application Sharing-Dialog is used to create ''SharingEntries'' that are shared by ''SharingManager''. Sharing Account Manager implements the Sharing Accounts. Libsharing is library for all common Sharing functionality.

[[Image:SharingPluginAPI.jpg]]

''Figure 3: Sharing Plugin API''

Figure 4 shows the common ''Sharing'' classes found in ''libsharing'' that you would use while creating the plug-in.
''SharingTransfer'' is the object that contains all the data of sharing task, overall status of the transfer process for one set of shared files.
''SharingEntry'' contains the the ''SharingEntryMedia'' that are the selected files. It also knows the ''SharingAccount'' that is the target of sharing.
''SharingAccount'' contains the username and password along with other parameters that you have to save for your service's accounts. It also has the information about ''SharingService'' which is registered to the ''SharingAccount''.

[[Image:LibSharingClasses.jpg]]

''Figure 4: Libsharing classes''

To see more detail the sharing classes you can browse to: <PUT URL TO Sharing plug-in dev TO HERE>.

==Service XML File==
Service definition file, data/template.service.xml.in is the starting point for plug-in loading. It defines the library that implements Sharing Plug-in API functions, the sign up URL for totally new account creation by using web browser, service name, icon file names and some basic information from plug-in.

<?xml version="1.0" encoding="UTF-8"?>
<service plugin="libtemplate.so" provider="Me">

<accounts plugInSetup="0" plugInEdit="0">
<signup>www.maemo.org</signup>
<password maxlen="32"/>
</accounts>

<ui>
<name>Template</name>
<icon type="post">@servicesdir@/template-post.png</icon>
<icon type="setup">@servicesdir@/template-setup.png</icon>
<options>
<option id="privacy" type="enumeration" default="private">
<caption domain="osso-sharing-ui" key="share_bd_options_privacy"/>
<value id="private" domain="osso-sharing-ui" key="share_fi_options_privacy_private"/>
<value id="public" domain="osso-sharing-ui" key="share_fi_options_privacy_public"/>
</option>
</option>
</ui>
</service>

''File 1: Example service definition XML file''

The prefix of name "template.service.xml.in", "template" in this case, defines the id of the plugin. The "plugin" value in the service definition defines the library that implements the Sharing Plug-in API. In this example file the library is libtemplate.so in the above example. "Provider" is the developer name, nick etc. In "accounts", you define the plug-in account setup and edit flows described more in detail in the coming sections. Sign up URL is the URL that is opened in the browser when a new account is being created for a service.

==Account Setup User Interface Flow==
Sharing accounts can either create a default flow where "username" and "password" parameters are set to the account or an optional custom flow. In File 1, the "accounts" tag has a parameter "plugInSetup". If it is set to "1", Sharing Accounts will call the Sharing Plugin API function "sharing_plugin_interface_account_setup" to create UI flow; it will use the default flow.
You can see the difference between UI flows when creating Flickr and Ovi account. Ovi uses the default flow and Flickr uses it's own UI flow.

<tt>SharingPluginInterfaceAccountSetupResult sharing_plugin_interface_account_setup (GtkWindow* parent, SharingService* service, SharingAccount** worked_on, osso_context_t* osso)</tt>

If you decide to create your own account setup flow, please try to keep the same UI look as in other Sharing dialogs.

==Account Validation==
Account validation is needed to reduce error cases in actual sending process. Of course you can use the dummy function at template plug-in, but for better user experience this function is recommended to be implemented so that Sharing Account account information is really validated against the service when new account is created.

Next function is called after sharing_plugin_interface_account_setup call ends or when default account setup flow is done (=when "Validate" button is pressed).

<tt>
SharingPluginInterfaceAccountValidateResult sharing_plugin_interface_account_validate (SharingAccount* account, ConIcConnection* con, gboolean *cont, gboolean* dead_mans_switch)</tt>

In the last phase of account creation, the account must be validated. Sharing Plug-in API ''sharing_plugin_interface_test_account'' is the function called in the validation phase of the account creation flow.
Usually web services have a phase in account creation where you have put the needed information from your account, only then you get the actual credentials to upload images if your account information is valid. This is the phase that is implemented in the Sharing Plug-in API function.

==Account Editing User Interface Flow==

Sharing Accounts support here too either default flow where “username” and “password” parameters are edited or optional custom edit UI flow. The wanted flow can be set by setting the parameter "plugInEdit" from the service definition file either to "0" or to "1" where "0" means the default flow and "1" plug-in flow.

The default flow can be used when you need only username and password to get needed information for sending. The plug-in flow is used when you need more than this or customised account validation flow. You can see the difference between UI flows here too when editing Flickr and Ovi accounts.

Next function must be implemented only when plug-in account setup is used (when "plugInSetup" is set to "1"):
<tt>SharingPluginInterfaceEditAccountResult sharing_plugin_interface_edit_account (GtkWindow* parent, SharingAccount* account, ConIcConnection* con, gboolean* dead_mans_switch)</tt>

==Sending Functionality==

<tt>SharingPluginInterfaceSendResult sharing_plugin_interface_send (SharingTransfer* transfer, ConIcConnection* con, gboolean* dead_mans_switch)</tt>

After pressing the 'Share' button in Sharing dialog (Figure 2.), the data is put into the Sharing Outbox (can be seen under /home/user/MyDocs/.sharing/outbox/). Sharing manager process is started and the status menu gets the icon to process the new Sharing Entry.
''SharingHTTP'' provides an API to create common HTTP requests.
In order to create a better user experience following things are good to be implemented after you get the basic functionality working in your plug-in:
*Set progress of sending with sharing_transfer_set_progress between 0 and 1 to estimate the current transfer time / total transfer time.
*Set sent to ''SharingEntryMedia'' with ''sharing_entry_media_set_sent'' when file sending is done and check the send value with ''sharing_entry_media_get_sent'' to prevent sending same files multiple times for example in reboot scenarios.
*Poll cancel flag time to time, for example in curl or ''SharingHTTP'' progress function to end transferring when needed. Use ''sharing_transfer_continue'' to get the continue flag bit.
*If you are using ''libcurl'' instead of ''SharingHTTP'', please listen to ''conic'' events to disconnect transfer when no connection available. It returns with 'no connection' return value in this case.

Next some example source for common tasks found in usual sending functionality:
==== Example sending loop ====

When you process SharingEntryMedias from the SharingEntry you propably end up with loop where you go the list of SharingEntryMedias through. Here is a raw example, where some example lines commented out with "//".
<tt>

for (GSList* p = sharing_entry_get_media (entry); p != NULL; p = g_slist_next(p)) {
SharingEntryMedia* media = p->data;
/* Process media */
if (!sharing_entry_media_get_sent (media)) {
/* Post media */
//guint result = my_send_task_post_function (my_send_task, media);
/* Process post result */
if (result == 0 /* EXAMPLE: MY_SEND_RESULT_SUCCESS */) {
/* If success mark media as sent */
sharing_entry_media_set_sent (media, TRUE);
/* And mark process to your internal data structure */
//my_send_task->upload_done += sharing_entry_media_get_size (media);
} else {
/* We have sent the file in last sharing-manager call */
//my_send_task->upload_done += sharing_entry_media_get_size (media);
}
}
}

</tt>

==== Example tags string ====
Usually services accept the tags in their API to be added to images. Here is example source to create nice string about tag information to be put where ", " string used as separator. If service supports also geo tagging you should develop this source further by checking the tag type also.
<tt>

static gchar* create_tags_str (const GSList* tags)
{
gchar* ret = NULL;
for (const GSList* p = tags; p != NULL; p = g_slist_next (p)) {
SharingTag* tag = (SharingTag*)(p->data);
const gchar* tmp = sharing_tag_get_word (tag);
if (tmp != NULL) {
gchar* new_ret = NULL;
if (ret != NULL) {
new_ret = g_strdup_printf ("%s, %s", ret, tmp);
g_free (ret); /* old return is freed */
} else {
new_ret = g_strdup (tmp);
}
ret = new_ret;
}
}
return ret;
}
gchar* tags = create_tags_str (sharing_entry_media_get_tags (media));
</tt>

==== SharingHTTP example ====
SharingHTTP is ment to be used for HTTP transfers. It is probably easier to use this than libcurl and libconic straightly in common cases. Give it a try at least if you are not familiar with libcurl!

<tt>
SharingHTTP * http = sharing_http_new ();
SharingHTTPRunResponse res;
res = sharing_http_run (http, "http://example.com/post");
if (res == SHARING_HTTP_RUNRES_SUCCESS) {
g_print ("Got response (%d): %s\n", sharing_http_get_res_code (http),
sharing_http_get_res_body (http, NULL));
} else {
g_printerr ("Couldn't get stuff from service\n");
}
sharing_http_unref (http);
</tt>

==Uninstallation==
Libsharing provides sharing-account-remover binary that can be used to clean Sharing Accounts created for your plugin. This binary is run by debian/ dir's prerm script. Prerm scripts are run just before the package is uninstalled. Change the plugin id from sharingplugintemplate to match your plug-in id in the script. Your plug-in's id is the service definitions files prefix. For template.service.xml, the prefix is "template".

Example prerm script:
<tt>
#!/bin/sh
# You can use sharing-account-remover to remove the accounts at plugin
# uninstallation
if [ "$1" = "remove" ]; then
/usr/bin/sharing-account-remover template
fi
</tt>

=Testing your plugin=
After setting up your scratchbox environment you can start using and testing your own plugin.

Sharing framework consists following packages:

libsharing-plugin-dev
libsharing0
sharing-manager
sharing-account-manager
sharing-dialog

All the needed packages should be installed along with nokia-binaries.

'''Important:''' When testing inside scratchbox remember to start the signond daemon after the desktop is started. Signond is used for storing the account information and it's needed in order to get Sharing framework working properly

[sbox] > signond &

Also remember to install the debian .deb package build from your sources.

Creating sharing account is started from setting.

settings -> Sharing accounts -> New

Select your service and create new account. After one account is created you can use ImageViewer for sharing images and MediaPlayer for sharing video files.

=Sharing your plugin with others=
Maemo Extras repository is the best place for your plug-in if you want to get users for it. More information on how you can upload packages to Extras repository can be found [[http://wiki.maemo.org/Uploading_to_Extras here]].

Before uploading plugin to public repositories make sure you have updated the debian configuration files to match your information under ./debian folder.

Also make sure that the section is set to user/other. This way the package will be installable by application manager. Below example version of debian control file.

Source: sharing-plugin-template
Section: user/other
Priority: optional
Maintainer: Maemo Team <xxxx@maemo.org>
Build-Depends: debhelper (>= 5.0.0),
libgtk2.0-dev, libglib2.0-dev,
libconic0-dev, libosso-dev,
libsharing-plugin-dev
Standards-Version: 3.8.0

Maemo Summit 2009

2009-09-30T11:58:08Z

192.100.124.218: /* Friday, October 9 */

Content will be the second most important aspect of the conference, after the social aspect of getting the Maemo community together.

== Schedule ==

=== Friday, October 9 ===

[[9:00 Registration at the Community Room (Zuiveringshal Oost)]]

10:00 '''Programme starts at N900 (Transformatorhuis)'''

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Maemo_5_and_the_N900 Maemo 5 and the Nokia N900] by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia

11:00 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Changing_PC_.26_Mobile_Landscape.3B_Why_Linux_will_play_a_Critical_Role Changing PC & Mobile Landscape; Why Linux will play a Critical Role]''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Nokia_Nseries_Devices_on_Maemo Nokia Nseries Devices on Maemo]''' by Jose-Luis Martinez Merino, VP, Marketing @ Nokia

12:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Harmattan_Highlights_-_Developer_Opportunities Harmattan Highlights - Developer Opportunities]''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia

13:00 '''Lunch - Maemo Expo opens'''

14:15 '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Why_the_Maemo_Community_matters_to_Nokia Why the Maemo Community matters to Nokia]''' - Alan "[http://maemo.org/profile/view/qole/ Qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! Track 1 - ''chair: Anthony Fabbricino''
! Track 2 - ''chair: John Loughney''
! Track 3 - ''chair: Quim Gil''
|-

|-
| 15:00 - 15:25
| '''UI design of Maemo 5 apps'''
''Annu-Maaria Nivala, UX team, Digia''
| rowspan="2" |'''UX panel'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| '''Cross-platform with Qt - live'''
''Ariya Hidayat, Software Engineer, Nokia''
|-
| 15:30 - 15:55
| '''Developing widgets on Maemo 5 - showcase Foreca Weather'''
''Juha Järvi, Software Designer, Foreca''
| '''[http://wiki.maemo.org/Maemo_Summit_2009/Schedule/Day_1#Mer_-_how_the_community_innovates Mer - how the community innovates]'''
''Carsten Munk, Lead Developer, Mer project''
|-
| 16.00 - 16.25
| '''Developing apps with Qt for Maemo5'''
''Kate Alhola, Forum Nokia, Chief Guru on Maemo
| '''Firefox on Maemo'''
''Stuart Parmenter, Director of Engineering, Mozilla''
| | '''Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Present and future of Maemo digital marketing'''
''Isko Salminen, Production Manager, Activeark
''and Jussi Mäkinen, Maemo Marketing, Nokia'''''
| '''Feedservice and plug-ins development in Maemo 5'''
''Mikko Levonmaa, Ixonos''
|-
| 17.00 - 17.25
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''Biz apps on Maemo'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| '''Harmattan Architecture Overview'''
''Juha Tukkinen, Principal Engineer, Architecture and Sys, Nokia''
|-
| 17.30 - 18.00
| '''Developer Support for Maemo by Forum Nokia'''
''Matt Collins, Director, Forum Nokia Marketing''
| '''Skype on Maemo'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''Porting an OpenGL game to GL ES'''
''Oliver Mcfadden, Software Engineer, Nokia''
|-
|}

20:00 '''Maemo Party''' coordinated by Jussi Mäkinen.

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
! BOFs/Workshops
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="4" align="center" | '''Welcome to Community days''' ''Maemo Community Council''
|-
| 10.15 - 10:45
| colspan="4" align="center" | '''Keynote: Ton Roosendaal, the Blender Foundation'''
|-
| 10.45 - 11:00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 2#Designing_UI_for_Maemo_5 | '''Designing UI for Maemo 5''']] 
''Mox Soini''
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa''
|rowspan="2" | [[/Day 2#Getting_started_session | '''Getting started session''']] ''Daniel Wilms and others''
| BOF
|-
| 11.30 - 11.55
| [[/Day 2#Personalizing_your_Maemo_5_device | '''Personalizing your Maemo 5 device''']] ''Hartti Suomela''
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| BOF
|-
| 12.00 - 12.25
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day_2#Introducing_the_Harmattan_UI_framework | '''Introducing the Harmattan UI framework''']] 
''Tomas Junnonen''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
| rowspan="2" | [[/Day 2#Extras.2Fautobuilder.2Finterfaces_round-table | '''Extras/autobuilder/interfaces round-table''']]
|-
| 12.30 - 12.55
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster''
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# [[/Lightning talks#Feedhandler_-_Integrating_RSS_newsreaders_with_the_browser | '''Feedhandler - Integrating RSS newsreaders with the browser''']] - ''Thomas Perl''
# [[/Lightning talks#python-mafw:_MAFW_framework_for_Python_developers | '''python-mafw: MAFW framework for Python developers''']] - ''Andrea Grandi''
# [[/Lightning talks#DVCS.3F_git.3F_-_How_does_that_work_then.3F | '''DVCS? git? - How does that work then?''']] - ''David Greaves''
# [[/Lightning_talks#BlueMaemo_-_Bluetooth_HID_mouse_.26_keyboard_for_Maemo | '''BlueMaemo - Bluetooth HID mouse & keyboard for Maemo''']] - ''Valério Valério''
# [[/Lightning_talks#Continous_Integration_with_CruiseControl_and_Scratchbox | '''Continous Integration with CruiseControl and Scratchbox''']] - ''Jani Mikkonen''
# [[/Lightning_talks#Conboy.2C_Tomboy_and_Snowy | '''Conboy, Tomboy and Snowy''']] - ''Cornelius Hald''
|-
| 15:25 - 15:45
| colspan="4" align="center" | Break
|-
| 15.45 - 16.10
| [[/Day 2#GUPnP_and_Rygel:_The_UPnP.2FDLNA_solution_for_Maemo | '''GUPnP and Rygel: The UPnP/DLNA solution for Maemo''']] 
''Zeeshan Ali''
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha''
| [[/Day 2#Contributing_with_Git_.26_Gitorious | '''Contributing with Git & Gitorious''']] Johan Sørensen
| [[/Day_2#High-resolution_image_processing_on_Maemo_devices | '''High-resolution image processing on Maemo devices''']] 
''Alexander Bokovoy''
|-
| 16.15 - 16.40
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk''
| [[/Day_2#Intelligent_Usage_of_Fremantle_Location_Framework_For_Location-aware_Applications | '''Intelligent Usage of Fremantle Location Framework For Location-aware Applications''']] 
''Quanyi Sun''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
| rowspan="2" | [[/Day_2#Git_hands-on_workshop | '''Git hands-on workshop''']] 
''David Greaves''
|-
| 16.45 - 17.10
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper''
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| [[/Day_2#Tracker:_Dial_M_for_Metadata | '''Tracker: Dial M for Metadata''']] 
''Ivan Frade, Iridian Kiiskinen''
|-
| 17.10 - 17.30
| colspan="4" align="center" | Break
|-
| 17.30 - 17.55
| [[/Day 2#Canola:_Beyond_the_media_playback | '''Canola: Beyond the media playback''']] ''Eduardo Lima''
| [[/Day 2#Hands-on_development_with_Nokia_Web_Runtime | '''Hands-on development with Nokia Web Runtime''']] 
''Oren Levine''
| [[/Day 2#The_Qt_Mobility_Project | '''The Qt Mobility Project''']] ''Alex Luddy''
| [[/Day_2#Hacking_officially_unsupported_Bluetooth_profiles_to_work_in_Fremantle | '''Hacking officially unsupported Bluetooth profiles to work in Fremantle''']] 
''Johan Hedberg''
|-
| 18.00 - 18.25
| [[/Day_2#The_Maemo_5_Address_Book | '''The Maemo 5 Address Book''']] 
''Mathias Hasselmann, Travis Reiter''
| [[/Day 2#Publishing_your_software_through_maemo.org | '''Publishing your software through maemo.org''']] ''Niels Breet''
| [[/Day_2#Maemo_and_oFono | '''Maemo and oFono''']] 
''Aki Niemi, Rémi Denis-Courmont''
| [[/Day_2#The_future_of_GTK.2B.2FHildon_in_Maemo_Harmattan | '''The future of GTK+/Hildon in Maemo Harmattan''']] 
''Alberto Garcia, Claudio Saavedra''
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
! BOFs/Workshops
|-
| align="right" | 9.00
| colspan="4" align="center" | Doors Open
|-
| 10.00 - 10.45
| colspan="4" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, Mauku, OMWeather, eCoach and more.
|-
| 10.45 - 11.00
| colspan="4" align="center" | Coffee-break
|-
| 11.00 - 11.25
| [[/Day 3#Maemo_Browser_for_power_users | '''Maemo Browser for power users''']] ''Mikko Korpelainen''
| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| [[/Day_3#Building_for_Mer | '''Building for Mer''']] ''David Greaves''
| rowspan="2" | [[/Day 3#Hackathon:_Integrating_Canola_with_Fremantle | '''Canola Fremantle Hackathon''']]
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| [[/Day_3#Designing_QT_application_for_Maemo_5_and_Maemo_6 | '''Designing QT application for Maemo 5 and Maemo 6''']] ''Sergiy Dubovik, Ian Monroe''
| [[/Day 3#Writing_plugins_for_MAFW | '''Writing plugins for MAFW ''']] ''Iago Toral''
|-
| 12.00 - 12.25
| [[/Day_3#Mobile_Office_based_on_KOffice_Open_Source_Project | '''Mobile Office based on KOffice Open Source Project''']] 
''Suresh Chande''
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| [[/Day_3#Maemo_Platform_Security:_Principles_and_Concepts | '''Maemo Platform Security: Principles and Concepts''']] 
''Elena Reshetova''
|[[/Day_3#Extending_the_Hildon_desktop | '''Extending the Hildon desktop ''']] 
''Marc Ordinas i Llopis''
|-
| 12.30 - 12.55
| [[/Day 3#Towards_painless_and_quality_translations | '''Towards painless and quality translations''']] Dimitris Glezos
| [[/Day_3#10_Tips_for_Designing_Mobile_Widgets | '''10 Tips for Designing Mobile Widgets''']] 
''Rajesh Lal''
| [[/Day_3#Telepathy_on_Maemo | '''Telepathy on Maemo''']] 
''Marco Barisione''
| [[/Day_3#What_to_do_about_.2Fopt_in_Fremantle | '''What to do about /opt in Fremantle''']] 
''Marius Vollmer''
|-
| 13.00 - 14.30
| colspan="4" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="4" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Issues_on_adapting_Maemo_4_application_to_Maemo_5 | '''Issues on adapting Maemo 4 application to Maemo 5''']] - ''Aniello del Sorbo''
# [[/Lightning_talks#How_to_speed_up_your_Maemo_application_development | '''How to speed up your Maemo application development''']] - ''Raul Herbster''
# [[/Lightning talks#GSoC_presentation:_BitTorrent_plugin_for_Canola | '''GSoC presentation: BitTorrent plugin for Canola''']] - ''Lauri Võsandi''
# [[/Lightning talks#GSoC_Project_presentation:_Picasa_plugin_for_Canola | '''GSoC Project presentation: Picasa plugin for Canola''']] - ''Andrei Mirestean''
# [[/Lightning_talks#Behaviour-Driven_Development_on_Maemo | '''Behaviour-Driven Development on Maemo''']] - ''Jose Teixeira''
# [[/Lightning_talks#N900_HW_architecture_overview_.26_power_management | N900 HW architecture overview & power management]] - ''Igor Stoppa''
# [[/Lightning_talks#From_corporations_to_communities:_responsible_and_effective_engagement | '''From corporations to communities: responsible and effective engagement''']] - ''Randall "Texrat" Arnold''
# [[/Lightning talks#Mer_from_a_user.27s_perspective | '''Mer from a user's perspective''']] - ''Tomasz Dominikowski''
|-
| 15.30 - 16.00
| colspan="4" align="center" | Grand Finale
|}

See [[../Submissions | the submission queue]] for current proposals under consideration.

== Registration ==

[http://maemo.org/news/events/registrations/register/e840196271eb11deb15535a00f6d72187218 Register for the summit]:

Free entrance! Registration needed to grant you food, drinks, a maemo.org shirt and a seat.

300 participants expected: developers and engaged users, community members and curious newcomers, from many countries.

=== Principles for defining the schedule ===
* Defaulting to three tracks for Users (Transformatorhuis - big), App Developers (Machinegebow - medium) and Platform Developers (De Kapel - small). Exceptions can be made of course but the idea is that each profile should have a suggested session to go at any time.
* Keynotes and Lightning Sessions are organized in Transformatorhuis without other activities at the same time.
* The tiny lovely Oostelijk Meterhuis is available for longer sessions with 25 people or less e.g. a 2h workshop. De Kapel can also serve that purpose if needed.

Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Programming Environments

2009-09-11T06:57:01Z

192.100.124.218: QT -> Qt

= Maemo Programming Environments =

This is place holder for Maemo Programming Environments documentation

Current official high level Diablo documentation for Python and C/C++ environments is available from maemo.org [http://maemo.org/development/documentation/programming_languages/ Maemo Programming Languages] page. This page is still valid also for Fremantle.

Current "under development" versions of the documentation can be found from these Garage projects:
* [http://pymaemo.garage.maemo.org/ Maemo Python support]
* [http://maemomm.garage.maemo.org/ Maemo C++ support]
* [http://qt4.garage.maemo.org/ Maemo Qt 4.5 support]
** [http://wiki.maemo.org/Qt4Hildon#Getting_started Getting Started]
** [http://wiki.maemo.org/Qt4Hildon/Maemo_differences_from_QT4.5 Maemo 5.0 Differences from Standard Qt 4.5 (new document to be created)]
** [http://wiki.maemo.org/Qt4Hildon#Porting_a_Qt_application_in_Maemo Porting Qt Application to Maemo]
** [http://wiki.maemo.org/Packaging_a_Qt_application Packaging Qt Application]
** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Programming Environments/Using accelerometer by Qt application | Using accelerometer by Qt application]]

Eclipse integration/ReleaseNotes prefinal

2009-09-10T07:18:15Z

192.100.124.218: Release notes for prefinal

= Release Notes for Maemo Eclipse Integration Edition 2 PreFinal release =

This Maemo Eclipse Integration Edition 2 PreFinal release supports Maemo Diablo 4.1.2 development environment with N800, N810 and N810 Wimax Edition devices and Maemo Fremantle 5.0 Beta 2 development environment N900 device.

Possible feedback can be sent to eclipse-integration@maemo.org.

== Release Information ==

* Project: Maemo Eclipse Integration Edition 2
* Version: PreFinal
* Baselines: Maemo Diablo 4.1.2 SDK and Maemo Fremantle 5.0 SDK Beta 2
* Date: 2009-09-11

== General Information ==

Eclipse Integration components now support the latest Debian based Linuxes, Windows XP SP3, Windows Vista SP2 and Mac OS X 10.5 Leopard all with x86/32bit architectures.

Support for other than above listed operating systems has not been tested but should be possible if operating system supports Eclipse IDE, if equal functionality to Host PC Connectivity is available (for example most Linuxes have) and if operating system is able to run Maemo SDK Virtual Image (in practise supports either QEmu, VMWare or VirtualBox).

Maemo Eclipse Integration includes the following parts:

* Eclipse 3.4.2 IDE (Ganymede SP2) for C/C++ Developers (official release from eclipse.org)
* Maemo PC Connectivity (Diablo extras-devel and Fremantle extras-devel repository versions)
* Host PC Connectivity for Linux, Windows XP/Vista and Mac OS X (PC Connectivity Garage project versions)
* Maemo ESbox plugin for Eclipse v2.0.0M6 (Esbox Garage project version)
* Maemo Pluthon plugin for Eclipse v2.0.0M6 (Pluthon Garage project version)
* Maemo Mica plugin framework for Eclipse v2.0.0M6 (Mica Garage project version)
* Maemo SDK Virtual Images v0.11 (to support other than Debian based Linuxes)
* Maemo C/C++ and Python programming language support (Diablo extras and Fremantle extras-devel repository versions)
* Maemo Flasher-3.5 Tool Beta versions

Detailed list of new features implemented to Maemo Eclipse Integration since previous Beta 2 release together with feature plan for final release is here http://wiki.maemo.org/Eclipse_integration.

Known issues for this PreFinal release are here http://wiki.maemo.org/Eclipse_integration/KnownIssues_prefinal.

This Release Notes file is here http://wiki.maemo.org/Eclipse_integration/ReleaseNotes_prefinal.

Basic product information and installation instructions for all PreFinal components can be found from their http://garage.maemo.org projects.

== Operating Systems Supported ==

* full support for same x86 32-bit Linux Ubuntu distributions that Maemo SDK releases support (Ubuntu Intrepid fully tested)
* good support for x86 32-bit Windows XP with SP3 and Vista with SP2, Cygwin used as Linux porting framework
* good support for x86 32-bit Mac OS X 10.5 Leopard, MacPorts used as Linux porting framework
* see instructions how to setup and configure different operating system support: http://pc-connectivity.garage.maemo.org/2nd_edition/installation.html and http://esbox.garage.maemo.org/2nd_edition/virtual_machines.html

== Eclipse IDE for C/C++ Developers ==

* product information: http://www.eclipse.org/
* Eclipse download if separate download wanted: http://www.eclipse.org/downloads/
* list of generic Eclipse components included: http://mica.garage.maemo.org/2nd_edition/documentation.html
* ESbox and Pluthon installation packages available from Garage include all needed Eclipse components for the release, including Eclipse 3.4.2 IDE itself (recommended installation method for this Beta 2 release)
** http://esbox.garage.maemo.org/2nd_edition/installation_product.html
** http://pluthon.garage.maemo.org/2nd_edition/installation_product.html
* For already installed Eclipse 3.4.2 IDE ESBox and Pluthon environments can be upgraded using Maemo Eclipse Update Site (not fully tested or supported installation method for Beta 2 release)
** http://esbox.garage.maemo.org/2nd_edition/installation_update_site.html
** http://pluthon.garage.maemo.org/2nd_edition/installation_update_site.html

== Maemo PC Connectivity ==

* product information: http://pc-connectivity.garage.maemo.org/2nd_edition
* installation instructions for Maemo device and Linux, Windows and Mac OS X host PCs: http://pc-connectivity.garage.maemo.org/2nd_edition/installation.html
* documentation and configuration instructions: http://pc-connectivity.garage.maemo.org/2nd_edition/documentation.html
* main features:
** support for Linux (Debian based), Windows (XP and Vista) and Mac OS X (Leopard)
** connectivity support with USB, BlueTooth and WLAN for Linux, Windows and Mac OS X
** SSH, SFTP, VNC and RSYNC support for Linux, Windows and Mac OS X host PCs
** NFS and SSHFS mount support (with Linux and Mac OS X) and Samba disk mount support (with Windows) between Maemo device and host PC
** IP Forwarding support between Maemo device and host PC
** ZeroConf support with Avahi to automatically configure connectivity between host PC and Maemo device
** support for configuring Maemo device with control panel applet and status bar plugin
** support for easy storing, restoring and switching connectivity environments/configurations
** support for both Diablo and Fremantle SDK environments
** support for VNC clients (native and Eclipse VNC plugin clients)
** native SBRSH (Scratchbox Remote Shell) support for Linux, Win and Mac OS X to launch applications from SDK to run on Maemo device
** SFTP support to access Maemo device file system with host PC GUI clients
** support for installing Host PC Connectivity components for Linux, Windows and Mac OS X host PCs
** easy installation using either single click installation or apt-tool in Maemo device to install from Maemo Diablo or Fremantle extras-devel repository
** specific applet can be used to easily switch between predefined connectivity environments/configuration
** Maemo PC Connectivity functionality is independent from Eclipse IDE e.g. usable also without installing Eclipse IDE
** Maemo PC Connectivity environment settings can be backed up with osso-backup application (for example before reflashing Maemo device)

== Maemo ESBox plugin for Eclipse ==

* product information: http://esbox.garage.maemo.org/2nd_edition
* installation and configuration instructions for Maemo device and Linux, Windows and Mac OS X host PCs: http://esbox.garage.maemo.org/2nd_edition/installation.html
* main features:
** easy PC-Device connectivity with Maemo PC Connectivity
** C, C++ and Python programming language support
** templates for the most common type of Maemo applications
** full support for Linux and good support for Windows and Mac OS X host PCs
** full connectivity support for Maemo device with SSH, RSE and SBRSH from Linux, Windows and Mac OS X
** support for both Diablo and Fremantle SDKs
** import Eclipse projects from Maemo SDK and Debian packages
** C/C++ debug/optimized configuration support
** support for P2 update site for ESbox
** installation wizard for Scratchbox, Diablo SDK and Fremantle SDK
** installation wizard for Maemo SDK development environments (like Python, C/C++, Flasher-3.5, OProfile, ...)
** build application with x86 target
** launch and test application on x86 target
** debug application on x86 target
** search for memory leaks using Valgrind on x86 target
** cross-compile application with ARMEL target
** debug application on the Maemo device using GDB or GDB Server
** performance test on Maemo device using OProfile
** Maemo installation package creation wizard
** Maemo Flasher-3.5 tool wizard

== Maemo Pluthon plugin for Eclipse ==

* product information: http://pluthon.garage.maemo.org/2nd_edition
* installation and configuration instructions for Maemo device and Linux, Windows and Mac OS X host PCs: http://pluthon.garage.maemo.org/2nd_edition/installation.html
* main features:
** easy PC-Device connectivity with Maemo PC Connectivity
** Python programming language support
** templates for the most common type of Maemo applications
** develop application directly on the Maemo device
** debug application on the Maemo device using pyDev
** full support for Linux, Windows and Mac OS X host PCs
** full connectivity support for Maemo device with SSH, RSE and SBRSH from Linux, Windows and Mac OS X
** support for P2 update site for Pluthon
** installation wizard to setup Python development environment for host PC and Maemo device
** Maemo installation package creation wizard
** Maemo Flasher-3.5 tool wizard
** Updated Fremantle Python tutorial and manual http://pymaemo.garage.maemo.org/documentation_fremantle.html

== Maemo Mica plugin framework for Eclipse ==

* product information: http://mica.garage.maemo.org/2nd_edition
* documentation for developers who want to develop their own Maemo plugins using Mica: http://mica.garage.maemo.org/2nd_edition/documentation.html
* main features:
** general framework for Maemo Eclipse plugin development
** uses latest stable Eclipse components (compatible with Eclipse Ganymede SR2)
** Scratchbox 1 installer wizard and SDK installer wizard
** support for both Diablo and Fremantle SDK
** supports SSH, RSE and SBRSH for Linux, Windows and Mac OS X
** Flasher-3.5 wizard for flashing Maemo device from Eclipse IDE
** support for P2 update site
** Mica Garage site releases, documentation and services usable for plugin developers

== Maemo SDK Virtual Image ==

* product information: http://maemovmware.garage.maemo.org/2nd_edition
* installation and configuration instructions: http://maemovmware.garage.maemo.org/2nd_edition/installation.html
* images can be downloaded from here: http://tablets-dev.nokia.com/maemo-dev-env-downloads.php
* instructions how to upgrade Ubuntu Desktop images from Beta 1 to Beta 2 level are here: http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
* main features:
** Ubuntu Intrepid Server based Maemo SDK Virtual Image for Linux, Windows and Mac OS X
*** full support for VMWare and QEMU virtualization technologies
*** do-it-yourself support for VirtualBox
*** server image includes basic Ubuntu Intrepid Server and Host PC Connectivity environment preconfigured and Maemo Diablo and Fremantle Development Environments can be installed with Eclipse installation wizard automatically
*** server image does not include installers for GuestAdditions (for VirtualBox) and OpenVMTools (for VMWare) but they can be installed separatelly is needed as instructed here http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
** Ubuntu Intrepid Desktop based Maemo SDK Virtual Image for Linux, Windows and Mac OS X
*** out-of-the-box ready Ubuntu Intrepid Desktop based image
*** desktop image includes fully configured Maemo Diablo Development Environment for Eclipse and Fremantle Development Environment can be installed with Eclipse installation wizard automatically
*** desktop image preinstalled ESbox Beta 1 environment can be updated to Beta 2 level with these instructions http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
*** desktop image includes installers for GuestAdditions (for VirtualBox) and OpenVMTools (for VMWare)
** installer/tool to configure Maemo SDK Virtual Images for VirtualBox usage
** instructions how to use SDK Virtual Images with Eclipse IDE on different operating systems: http://esbox.garage.maemo.org/2nd_edition/virtual_machines.html

== Maemo C++ and Python programming language support ==

* product information: http://maemo.org/development/documentation/programming_languages/
* C++ documentation: http://maemomm.garage.maemo.org/docs/
* Python documentation: http://pymaemo.garage.maemo.org/

* By default, the Maemo development environment supports C programming language but you may add support for other programming languages. Instructions how to install Maemo support for C++ and Python application development can be found from here http://maemo.org/development/documentation/programming_languages/.

* The Maemo development environment defines helpful meta packages that install all the components and tools for C++ and Python development for the for Maemo SDK and Maemo device. Maemo Eclipse Integration will install these meta packages automatically into your environment if you have not done it already when you create your first C++ or Python project.

== Known Issues ==

* latest version for Beta 2 known issues is here http://wiki.maemo.org/Eclipse_integration/KnownIssues_beta2 (feel free to update this wiki page)
* Diablo 4.1.2 device requires kernel patch from here http://tablets-dev.nokia.com/maemo-dev-env-downloads.php to be flashed to the Maemo device for USB Networking to work with Windows host PC
* Diablo 4.1.2 device requires hildon-desktop patch to be installed to the Maemo device from pc-connectivity Garage repository (see instructions from here http://pc-connectivity.garage.maemo.org/beta1/installation.html) for VNC client to work on host PC
* Ubuntu Desktop based Maemo SDK Virtual Image (out-of-the-box ready development environment) includes Beta 1 level Eclipse and PC Connectivity environment but can be easily updated to Beta 2 level with these instructions http://maemovmware.garage.maemo.org/2nd_edition/update_maemo_vm.html
* Updating process from Eclipse Update Site (update from beta 1 to beta 2) may not work for some plug-ins

== Installation Notices ==

'''Notice 1''': If only Maemo Pluthon plugin for Eclipse is used for Python on device development it does not reguire Maemo SDK installation on host PC.

'''Notice 2''': All configurations require Maemo PC Connectivity to be installed and configured to work to the Maemo device and Host PC Connectivity to the host PC BEFORE installation of Eclipse components can be started.

'''Notice 3''': All Eclipse components can be installed from ESbox or Pluthon garage projects, PC Connectivity from Diablo extras-devel or Fremantle extras-devel repository and SDK Virtual Images and Flasher-3.5 tool from maemo development environment download page http://tablets-dev.nokia.com/maemo-dev-env-downloads.php

'''Notice 4''': Eclipse 3.4.2 IDE for C/C++ Developers and all needed generic Eclipse plugins and ESbox and Pluthon plugins can be installed together with installation packages available from ESbox and Pluthon garage projects.

----
Feedback can be sent to eclipse-integration@maemo.org

Maemo Summit 2009/Submissions

2009-09-09T15:38:39Z

192.100.124.218: /* Talk submissions for Maemo Summit 2009 */

= Talk submissions for Maemo Summit 2009 =

Please add your submission to this page at the bottom. Have a look at the [[../Call for content| Call for content]] for some guidelines.

Please follow the template for each presentation that you would like to submit. Thanks!

''Maemo Summit community content committee:
* Dave Neary
* Jamie Bennett
* Valério Valério
''
== Submission template ==

Copy & paste the following template, and fill in the details specific to your presentation.

=== Talk Title Goes Here ===
*Author name and contact details
*Intended audience (users/application developers/platform developers)
*Talk type (presentation/lightning talk)
*Abstract/description
: Abstract goes here. A two paragraph overview of the proposed talk content is sufficient.
*Additional Information (optional)
: Additional information on extra equipment you might need or something else goes here
*Author bio
: A short (1 paragraph) note about who the author is goes here

-----

== Talk Submissions ==

=== PySide: Python for Qt And Automatic Bindings Generation ===

* Marcelo Lira dos Santos - marcelo.lira@openbossa.org - setanta on #maemo
* Intended audience: application developers/platform developers
* Talk type: presentation
* Abstract/description:
: The Python bindings for the Maemo Platform provided by PyMaemo are an all-time favorite among the Maemo developer community. Python must keep up with the recent addition of Qt to the Nokia offering for Maemo developers.
: PySide are the Python bindings for Qt framework developed by INdT (Instuto Nokia de Tecnologia) [http://www.indt.org.br], and recently released under a LGPL license. The PySide [http://www.pyside.org] bindings target not only the desktop but were conceived to provide Qt for Python on the Maemo platform.
: Qt being a huge library, the task of creating bindings for any high level language must be automated as much as possible, while retaining the developer ability to adjust details to satisfy the particular target language demands. To tackle this problem, a binding generator for Python was developed based on QtScript Generator from Qt Development Frameworks. Developers of bindings for other Qt-based libraries could also benefit of this automated generation scheme.
: This talk will present PySide, describe its characteristics, show its current status on Maemo Platform and where the project is headed to. The binding generation tool will also be explained, as well as the common problems that arise when wrapping C++ libraries to high level languages such as Python.

*Author bio
: Marcelo is an active developer of PySide and PyMaemo projects at INdT and has been involved with Maemo apps development since N800. Nowadays he is working with automatic binding generation for C++ based libraries, like Qt.

=== From corporations to communities: responsible and effective engagement ===
*Randall "Texrat" Arnold, fabricator at cynicalsigns dot com, http://tabulacrypticum.wordpress.com
*Intended audience is Nokia PR; Nokia Maemo team; Maemo developer, tester and superuser community; other interested parties
*Talk type : best practice/lessons learned presentation
*Abstract/description
: The presentation covers the following subject areas: general best practices in the area of corporate/community relations and how they apply to Maemo, as well as possibly a post mortem of lessons learned vis a vis community outreach from both Maemo and user perspectives (via interviews).

: This will not be a "what Nokia did wrong" as much as it is a clear, appropriate guide for future public relations in the murky world of commercial enterprise meets open source development; a path forward
.
*Author bio
: I am a former Nokia employee (Alliance factory and DSNM trade customer logistics) who was a principal on the US launch team for the N800. As Quality Engineer I managed the delivery of 200 devices to CES 2007 and ensured quality on devices delivered until their production relocation to Mexico. I became one of the first Nokia employees to reach out to the new community of tablet software developers and have continued in a voluntary representative role. I also tested internal applications such as the enterprise support suite (including VPN) and field tested the N810 WiMAX Edition tablet. I also developed a prototype mobile auditing solution using the internet tablets. Today I still cover the internet tablets and their applications at http://tabulacrypticum.wordpress.com

=== Midgard2: Content repository for your tablet and the web ===
*Author: Henri Bergius, henri.bergius at iki dot fi
*Intended audience: Application Developers
*Talk type: presentation
*Abstract/description
: Midgard2 is an Open Source Content Repository providing an objectified view to the data and services surrounding it. At the basic level it abstracts the database access (SQLite, MySql, PostgreSQL) but this is only where it all starts. Serialization & replication, managing own storage objects, multi-process access to data are all covered. The fully object-oriented (GObject-oriented) API allows you to focus on the data, not the database syntax, regardless of what programming language you are working with. Midgard's content repository services allow you to easily write applications that keep their data synchronized between tablets, web and user's desktop computers.

*Author bio
: Henri Bergius is a former Viking based in the Nordic country of Finland. When he is not exploring the cave cities of Georgia or running with bulls in Pamplona, Bergie works on web services built on top of the Midgard toolkit. His company Nemein provides web solutions for several major companies in Finland and abroad. After half decade of regular web development, Henri got involved with free software in 1999 when he coordinated the public release of the Midgard content management system. Since then he has been actively working on integrating standards like RSS and Microformats into the system and traveling the world advocating for interoperation between open source CMSs. Henri's current passion is combining web services, mobile applications and socially produced geographical data together to build useful tools for travelers and mobile companies. To this end he is working on the GeoClue library that allows mobile Linux applications to easily become geo-aware. When duties allow, Bergie escapes the crunch to explore the hills of Lapland or rides his classic motorcycle. He is also an amateur pilot.

=== Developing applications using Plasma ===
* Artur Duque de Souza - asouza AT kde DOT org / morpheuz AT gmail DOT com
* Intended audience: application developers
*Talk type: presentation
*Abstract/description

: KDE4 brought a new concept of desktop called "Plasma" where everything is a "live object". To achieve this, a library called libplasma was created and this is a very powerful library that enables any application to create modular and rich UIs. During this presentation I'll talk more about libplasma and how it can help the developer to create more attractive and rich UIs easily.

*Author bio

: Linux user since 1997, MoRpHeUz (a.k.a. Artur de Souza) worked for IBM (Linux Technology Center) and currently is working for INdT as a researcher at the openBossa stream, developing open-source solutions for mobile devices. One of the main core developers of Canola 2, now he works on bringing rich UIs to Qt applications.

=== Extras/autobuilder/interfaces round-table ===
*Author: Ed Bartosh, Alexander Kanevskiy, Niels Breet
*Intended audience: application and platform developers
*Talk type: round-table
*Room: Oostelijk Meterhuis
*Duration: 1 hour
*Abstract/description
:The purpose of this round-table is to discuss future features that can be added to autobuilder and all Extras related services. We want to gather opinions and see what the needs of developers are. Suggestions about enhancements or new features are appreciated.
*Author bio
: Ed Bartosh and Alexander Kanevskiy both work at Nokia, in their spare time they work on the autobuilder for Extras. Niels Breet is the maemo.org webmaster, working on web services available at maemo.org.

=== Designing Emulators for Mobile Devices ===
*Marat Fayzullin - RST38h on #maemo
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: Computer system emulation has been known for years. Recent revolution in mobile hardware makes it possible to run usable emulators on mobile devices, but some problems still remain. Limited performance, lack of proper controls, and widely varying screen sizes make it difficult to provide users with proper experience. This presentation will describe how the above problems can be worked around.
*Author bio
: Marat Fayzullin is an independent application developer specializing in software emulation of computer hardware. He has authored and maintains eight different emulators (some free, others commercial) for multiple platforms, from MSDOS to Maemo and Symbian. See http://fms.komkon.org/ for details.

=== WebKit Community: How It Works ===
*Ariya Hidayat, ariya dot hidayat at nokia dot com
*Intended audience: application developers
*Talk type: introduction and workshop
*Abstract/description
: WebKit has evolved over time into one of the most compelling HTML rendering engine currently in use. As an open-source project it stands out because of its size and because of the special collaboration between volunteer developers and companies.
: This presentation is not so much a presentation in the classic sense but planned as an introduction to the team rules of the WebKit project, e.g. how to create patches, ask for review, get in contact with the developer, etc. It will be followed by an extended question and answers session that should cover the most important and mots common questions.

*Author bio
: Ariya is a software engineer at Nokia, Qt Development Frameworks in Oslo. He is an open-source advocate for almost a decade, writing code for projects like KDE, WebKit and of course Qt. He posts lots of examples for Qt Labs Blogs on a biweekly basis, under the pretext of attracting more developers to use Qt (and hopefully grabbing the Most Prolific Blogger award). Ariya obtained his PhD in the field of high-speed optical communications. He speaks English with an Asian accent and cannot play any musical instruments.

=== 10 Tips for Designing Mobile Widgets ===
*Author: [http://maemo.org/profile/view/rajeshlal Rajesh Lal], rajesh.lal at nokia dot com
*Intended audience: Widget Developers/Mobile Application Developers
*Talk type: Presentation

*Abstract/description
: Do you know why only 1 percent of Mobile Widgets are successful ? What makes some widgets thrive and used by millions, and others with equal functionality bite the dust ? Make no mistakes, design of a widget is not about graphics, color or fonts. This presentation will demystify this 'invisible' layer below the surface with 10 pragmatic tips. The tips will uncover some of the most useful, and often ignored standard design principles and how to apply them in a mobile context.

*Author bio
: Rajesh lal is a Designer, Author, Technology Evangelist, and a Senior Nokia Engineer with a decade of experience in Information Technology. He has been involved in Widget design and development for last 5 years and have authored multiple books on Gadgets and Widgets. He has experience in a variety of Mobile devices, namely Sony Mylo, Window's Mobile, Apple's Iphone, Nokia S60 and Maemo devices. His blog on design and user experience can be found at http://abcofdesign.com

=== Conboy, Tomboy and Snowy ===
*[http://maemo.org/profile/view/conny Cornelius Hald]
*Intended audience: users and application developers
*Talk type: lightning talk
*Abstract/description
: Short introduction to Conboy and the new (not yet released) features, which are online synchronization with Tomboy/Gnote via the Snowy web service and plug-in support. Could include a demo if wanted.

*Author bio
: I'm a computer science student looking for distraction while writing my final thesis.

=== Behaviour-Driven Development on Maemo ===
*[http://wiki.maemo.org/User:Japolinario Jose Teixeira]
*Intended audience: Application developers & platform developers
*Talk type: Kightning talk
*Abstract/description
: '''What''' is Behaviour-Driven Development (BDD)? '''Why''' BDD matters to Maemo developers? And '''How''' to setup and open-source BDD tool-chain for Maemo ? And, finally '''How''' to make BDD funnier on a N810 device with [http://www.ruby-lang.org Ruby], [http://rspec.info/ Rspec], [http://cukes.info/ Cucumber] and [http://doc.trolltech.com/4.5/qtscript.html QtScript].
* I already made a deep dive in the subject. I try now to capture the attention of others to follow.
*Author bio
: [http://wiki.maemo.org/User:Japolinario Jose Teixeira] participated in the development of the Maemo Application Framework as Nokia trainer. Right now, he his a full-time researcher, teaching IT in a Finnish university as well. On his free-time, he contributes to open-source projects and incite many others to to the same.

=== Maemo and oFono ===

* By Rémi Denis-Courmont (remi dot denis-courmont at nokia dot com) and Aki Niemi (aki dot niemi at nokia dot com)
* For platform developers
* Presentation (could be shortened to lightning talk but...)
* oFono is an open source telephony stack for Linux. It provides an easy-to-use D-Bus interface and has support for a variety of cellular modem hardware, including Nokia cellular modems. The project is a joint effort between Intel and Nokia.

:How is it different from earlier attempts? What is it all about? What can you do with Ofono and Nokia N900?

* For demoing purpose, the presenter will need to use his own laptop and Nokia devices.

* Rémi Denis-Courmont currently works for Nokia, where he maintains the Phonet stack for the Linux kernel, the Maemo platform and the Ofono project. Outside Nokia, he's also been involved in the VideoLAN project.

=== Maemo Platform Security: Consepts, Architecture, Implementation ===

* Elena Reshetova - elena.reshetova@nokia.com
* Intended audience: users, application developers, platform developers
* Talk type: presentation
* Abstract/description:

: The purpose of the Platform Security in the Maemo platform is to protect the owner of a Maemo-powered device from getting her personal, private data and passwords from being stolen and used for malicious purposes, to prevent a malware from misusing a device and incurring costs on user, to prevent a user from accidentally breaking the device and to make the platform meet the requirements set by such third party software that requires a safe execution environment.

: The main design goal is to have all this accomplished without any significant penalty in terms of performance or usability, by using established open standards and having as much of the implementation open-sourced as possible. Another goal is to minimize an entry barrier for 3rd party programmers by reusing the existing Linux programming environment and introducing only needed additional features.

: The presentation will cover the main concepts, architecture choices and implementation of the Maemo Platform Security.

*Author bio
: Elena is a senior security engineer and representative of Maemo security team at the Maemo summit. The current task of the team is development of the Maemo Security FW.

=== Hacking officially unsupported Bluetooth profiles to work in Fremantle ===
*Johan Hedberg - johan.hedberg at nokia.com
*Intended audience: users,application developers,platform developers
*Talk type: presentation
*Abstract/description
: Fremantle doesn't come with out-of-the-box support of several Bluetooth profiles that are could in theory be supported with upstream components. These include e.g. DUN, HID and PAN. The presentation intends to be a hands-on session demonstrating how to enable support for these profiles through the act of changing config files and random hacking.
*Author bio
: Johan has been a software developer in the Maemo team ever since the first Maemo device, the 770 came out. His main responsibility area is Bluetooth and through active upstream involvement he has become a co-maintainer of BlueZ.

=== Continous Integration with CruiseControl and Scratchbox ===
*Jani Mikkonen, ext dash jani dot mikkonen at nokia dot com, rasjani @ #mer
*Application developers / QA People
*Lightning talk / Can extend to presentation if interest demands
*Abstract/description
: Topic is about how to harness Cruisecontrol to full build / packaging / testing and repository update cycle for development teams big and small.
*Additional Information (optional)
: Projector for showing live demostration and own laptop.
*Author bio
: Jani has been working with Maemo since Diablo/N800 on various tasks from maintenance to testing and is a long time linux user with developer & bofh background.

=== Intelligent Usage of Fremantle Location Framework For Location-aware Applications ===

*Quanyi Sun
*Intended audience: users/application developers/platform developers
*Talk type: presentation
*Abstract/description
: Abstract:
Location API is part of the Maemo 5 (Fremantle) API offerings. The location API for the first time now has introduced concept of hybrid locationing methods, i.e., supports of multiple locationing technologies seemlessly in a transparent way. In addition to the benefits of hybrid locationing methods, there are some issues, e.g., power consumption, that must be handled properly in order to maximize the benefits.

This presentation intends to hightlight the major issues when using location API, and provides best recommendations for developing location-aware applications in Maemo 5.

*Author bio:
Quanyi Sun has been working for Maemo as technical product owner in location area, with 13+ years of industrial experiences, e.g., in mission-critical realtime onboard software project in my early days.

=== Tracker: Dial M for Metadata ===
*Ivan Frade <ifrade@gnome.org>
*Intended audience: application developers/platform developers
*Presentation
*Abstract/description
: Tracker is a freedesktop project (with GNOME roots) included in the maemo platform for the first time in maemo5. In fremantle it is a simple index engine with support for basic metadata. For harmattan Tracker takes a great leap forward becoming a central storage for *user information*. The important data for the user (contacts, messages, multimedia, ...) will not only be stored in an application independent way, but also in a "linkable" format. This enables a new user experience: it makes it possible to integrate contacts everywhere, mix IM/email/twitter history of a contact, and so on.

In this presentation, Application developers can see how data is linked and obtained from Tracker to enrich their applications; platform contributors can learn how to integrate new information sources.

*Author bio
: Ivan Frade is an open source enthusiast who works in nokia building a data management solution for maemo based on tracker. On his free time, helps the world to tag properly their Mp3s with his pet-project.

=== Mobile Office based on KOffice Open Source Project===
*Suresh Chande, suresh.chande at nokia.com
*Intended audience: Application & Platform developers
*Talk type: Presentation
*Abstract/description
: We will present here Mobile Office project developed for Fremantle based on KOffice, a QT based open source project.

*Additional Information (optional)
: We will demonstrate Mobile Office (KOffice) running on the N900.

*Author bio
: Suresh Chande, works for Nokia in Device R&D(Maemo ) as Technical Product Owner for the Office Domain. Suresh has worked at Nokia Research Center for over 11 years focusing Mobile Business and Enterprise Application research. His vision is to have Office tools free for use by everybody.

=== Designing QT application for Maemo 5 and Maemo 6===
*Sergiy Dubovik, sergiy dot dubovik "at sign" nokia point com
*Intended audience: application developers
*Talk type: presentation
*Abstract/description

:How application developers should design their applications to work on Maemo 5 and Maemo 6 platforms? Which widgets will be supported? How to handle possible virtual keyboard? Where to store application settings? Which QT services will be available? These questions will be answered.

*Additional information on extra equipment you might need or something else goes here
:Just a projector

*Author bio
:Sergiy Dubovik is a senior software developer working in Nokia, designing and developing UI frameworks for Harmattan program.

=== MicroB browser, why it fastest "Mozilla based" browser, features, extensions for MicroB ===
*Oleg Romashin, oleg dot romashin at nokia dot com / Nagineni Sudarsana
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: Maemo 5, MicroB browser currently is fastest "Mozilla based" browser available on mobile platform.
: This presentation is some sort of description of architecture and principles of MicroB browser, why it so fast, what is difference between MicroB and Fennec browser.
: Also some description about how to write extensions for MicroB browser.

=== ContextKit - context awareness for Maemo and everybody else ===
*Author: Marius Vollmer <marius.vollmer@nokia.com>
*Intended audience: application developers/platform developers)
*Type: presentation
*Abstract
A lot of information is available from sensors and other sources that can make applications more 'aware' of the situation that a mobile device is in. The current location is an obvious example.

A new ContextKit collects these information about the environment of a device, combines many of them into something more abstract and exports it all in the form of simple key/value pairs to applications and other consumers. A long list of 'standard' properties is defined.

This presentation introduces the ContextKit to application and platform developers.

*Author bio:
Marius moved to Helsinki some uncounted years ago to work for Nokia on the Maemo platform. Now he has to re-learn C++ and compensates for this by finally learning Perl as well.

Maemo Summit 2009/Submissions

2009-09-08T13:23:41Z

192.100.124.218: Add oFono presentation proposal

= Talk submissions for Maemo Summit 2009 =

Please add your submission to this page at the bottom. Have a look at the [[../Call for content| Call for content]] for some guidelines.

Please follow the template for each presentation that you would like to submit. Thanks!

''Maemo Summit community content committee:
* Dave Neary
* Jamie Bennett
* Valério Valério
''
== Submission template ==

Copy & paste the following template, and fill in the details specific to your presentation.

=== Talk Title Goes Here ===
*Author name and contact details
*Intended audience (users/application developers/platform developers)
*Talk type (presentation/lightning talk)
*Abstract/description
: Abstract goes here. A two paragraph overview of the proposed talk content is sufficient.
*Additional Information (optional)
: Additional information on extra equipment you might need or something else goes here
*Author bio
: A short (1 paragraph) note about who the author is goes here

-----

== Talk Submissions ==

=== Hacking officially unsupported Bluetooth profiles to work in Fremantle ===
*Johan Hedberg - johan.hedberg at nokia.com
*Intended audience: users,application developers,platform developers
*Talk type: presentation
*Abstract/description
: Fremantle doesn't come with out-of-the-box support of several Bluetooth profiles that are could in theory be supported with upstream components. These include e.g. DUN, HID and PAN. The presentation intends to be a hands-on session demonstrating how to enable support for these profiles through the act of changing config files and random hacking.
*Author bio
: Johan has been a software developer in the Maemo team ever since the first Maemo device, the 770 came out. His main responsibility area is Bluetooth and through active upstream involvement he has become a co-maintainer of BlueZ.

=== Harmattan Platform Security: Consepts, Architecture, Implementation ===
*Elena Reshetova - elena.reshetova@nokia.com
*Intended audience: users, application developers, platform developers
*Talk type: presentation
*Abstract/description

: The presentation will cover the main concepts, architecture choices and implementation of the Harmattan Platform Security.

*Author bio
: Elena is a Senior Security Engineer at Nokia and representative of the Maemo Security team at the Maemo Summit. The current activity of the team is developing the Security Framework for the Harmattan Program.

=== PySide: Python for Qt And Automatic Bindings Generation ===

* Marcelo Lira dos Santos - marcelo.lira@openbossa.org - setanta on #maemo
* Intended audience: application developers/platform developers
* Talk type: presentation
* Abstract/description:
: The Python bindings for the Maemo Platform provided by PyMaemo are an all-time favorite among the Maemo developer community. Python must keep up with the recent addition of Qt to the Nokia offering for Maemo developers.
: PySide are the Python bindings for Qt framework developed by INdT (Instuto Nokia de Tecnologia) [http://www.indt.org.br], and recently released under a LGPL license. The PySide [http://www.pyside.org] bindings target not only the desktop but were conceived to provide Qt for Python on the Maemo platform.
: Qt being a huge library, the task of creating bindings for any high level language must be automated as much as possible, while retaining the developer ability to adjust details to satisfy the particular target language demands. To tackle this problem, a binding generator for Python was developed based on QtScript Generator from Qt Development Frameworks. Developers of bindings for other Qt-based libraries could also benefit of this automated generation scheme.
: This talk will present PySide, describe its characteristics, show its current status on Maemo Platform and where the project is headed to. The binding generation tool will also be explained, as well as the common problems that arise when wrapping C++ libraries to high level languages such as Python.

*Author bio
: Marcelo is an active developer of PySide and PyMaemo projects at INdT and has been involved with Maemo apps development since N800. Nowadays he is working with automatic binding generation for C++ based libraries, like Qt.

=== From corporations to communities: responsible and effective engagement ===
*Randall "Texrat" Arnold, fabricator at cynicalsigns dot com, http://tabulacrypticum.wordpress.com
*Intended audience is Nokia PR; Nokia Maemo team; Maemo developer, tester and superuser community; other interested parties
*Talk type : best practice/lessons learned presentation
*Abstract/description
: The presentation covers the following subject areas: general best practices in the area of corporate/community relations and how they apply to Maemo, as well as possibly a post mortem of lessons learned vis a vis community outreach from both Maemo and user perspectives (via interviews).

: This will not be a "what Nokia did wrong" as much as it is a clear, appropriate guide for future public relations in the murky world of commercial enterprise meets open source development; a path forward
.
*Author bio
: I am a former Nokia employee (Alliance factory and DSNM trade customer logistics) who was a principal on the US launch team for the N800. As Quality Engineer I managed the delivery of 200 devices to CES 2007 and ensured quality on devices delivered until their production relocation to Mexico. I became one of the first Nokia employees to reach out to the new community of tablet software developers and have continued in a voluntary representative role. I also tested internal applications such as the enterprise support suite (including VPN) and field tested the N810 WiMAX Edition tablet. I also developed a prototype mobile auditing solution using the internet tablets. Today I still cover the internet tablets and their applications at http://tabulacrypticum.wordpress.com

=== Midgard2: Content repository for your tablet and the web ===
*Author: Henri Bergius, henri.bergius at iki dot fi
*Intended audience: Application Developers
*Talk type: presentation
*Abstract/description
: Midgard2 is an Open Source Content Repository providing an objectified view to the data and services surrounding it. At the basic level it abstracts the database access (SQLite, MySql, PostgreSQL) but this is only where it all starts. Serialization & replication, managing own storage objects, multi-process access to data are all covered. The fully object-oriented (GObject-oriented) API allows you to focus on the data, not the database syntax, regardless of what programming language you are working with. Midgard's content repository services allow you to easily write applications that keep their data synchronized between tablets, web and user's desktop computers.

*Author bio
: Henri Bergius is a former Viking based in the Nordic country of Finland. When he is not exploring the cave cities of Georgia or running with bulls in Pamplona, Bergie works on web services built on top of the Midgard toolkit. His company Nemein provides web solutions for several major companies in Finland and abroad. After half decade of regular web development, Henri got involved with free software in 1999 when he coordinated the public release of the Midgard content management system. Since then he has been actively working on integrating standards like RSS and Microformats into the system and traveling the world advocating for interoperation between open source CMSs. Henri's current passion is combining web services, mobile applications and socially produced geographical data together to build useful tools for travelers and mobile companies. To this end he is working on the GeoClue library that allows mobile Linux applications to easily become geo-aware. When duties allow, Bergie escapes the crunch to explore the hills of Lapland or rides his classic motorcycle. He is also an amateur pilot.

=== Developing applications using Plasma ===
* Artur Duque de Souza - asouza AT kde DOT org / morpheuz AT gmail DOT com
* Intended audience: application developers
*Talk type: presentation
*Abstract/description

: KDE4 brought a new concept of desktop called "Plasma" where everything is a "live object". To achieve this, a library called libplasma was created and this is a very powerful library that enables any application to create modular and rich UIs. During this presentation I'll talk more about libplasma and how it can help the developer to create more attractive and rich UIs easily.

*Author bio

: Linux user since 1997, MoRpHeUz (a.k.a. Artur de Souza) worked for IBM (Linux Technology Center) and currently is working for INdT as a researcher at the openBossa stream, developing open-source solutions for mobile devices. One of the main core developers of Canola 2, now he works on bringing rich UIs to Qt applications.

=== Extras/autobuilder/interfaces round-table ===
*Author: Ed Bartosh, Alexander Kanevskiy, Niels Breet
*Intended audience: application and platform developers
*Talk type: round-table
*Room: Oostelijk Meterhuis
*Duration: 1 hour
*Abstract/description
:The purpose of this round-table is to discuss future features that can be added to autobuilder and all Extras related services. We want to gather opinions and see what the needs of developers are. Suggestions about enhancements or new features are appreciated.
*Author bio
: Ed Bartosh and Alexander Kanevskiy both work at Nokia, in their spare time they work on the autobuilder for Extras. Niels Breet is the maemo.org webmaster, working on web services available at maemo.org.

=== Hackathon: Integrating Canola with Fremantle ===
*Author: [http://maemo.org/profile/view/etrunko Eduardo Lima (Etrunko)]
*Intended audience: Application Developers
*Talk type: Hands-on/Hackathon
*Duration: All Saturday/Sunday long
*Abstract/description
: The idea of this session is to get a reasonable number of people interested in integrating Canola with the new technologies introduced in Fremantle, mostly Tracker and MAFW, together, so we can trace a plan and start getting our hands dirty.

: ''Why??''

: Some Canola components were conceived aiming to provide alternate solutions for some Nokia closed-source libraries and others that were not available by the time we started the project (mid-2007, back then we only had the N800 with Bora/Chinook). That's why we created our own media scanner (lightmediascanner+canolad) and media engine (atabake). Now I think it is time for us to evolve to the new and open solutions provided by Fremantle, yet keeping compatibility with "legacy" platforms, such as Diablo.

: People interested in developing plugins for Canola and/or developing using EFL/PyEFL are more than welcome to join us.
*Extra equipment
**<strike>''Guns, lots of guns.''</strike>
**Brave hacker souls
**Power outlets galore
**Internet Connection
**Whiteboard/Flipchart
**Coffe
*Author bio
: Open Source Software enthusiast, involved with Maemo since the very beginning (mid 2005), and had the opportunity to be part of the first Maemo Community Council. Started porting various GTK+/GNOME applications (Gnumeric, Evince, Abiword, Leafpad, Xournal, etc), to the platform. Worked on the first version of Carman, written in Python + GTK. After that, joined the team developing the Canola media player, coding and maintaining its packages for Maemo since then. Also maintains packages of the Enlightenment Foundation Libraries (EFL) for Maemo. Works for openBossa/INdT, where has been having the opportunity to present and talk about Maemo in events in Brazil and worldwide.

=== Designing Emulators for Mobile Devices ===
*Marat Fayzullin - RST38h on #maemo
*Intended audience: application developers
*Talk type: presentation
*Abstract/description
: Computer system emulation has been known for years. Recent revolution in mobile hardware makes it possible to run usable emulators on mobile devices, but some problems still remain. Limited performance, lack of proper controls, and widely varying screen sizes make it difficult to provide users with proper experience. This presentation will describe how the above problems can be worked around.
*Author bio
: Marat Fayzullin is an independent application developer specializing in software emulation of computer hardware. He has authored and maintains eight different emulators (some free, others commercial) for multiple platforms, from MSDOS to Maemo and Symbian. See http://fms.komkon.org/ for details.

=== WebKit Community: How It Works ===
*Ariya Hidayat, ariya dot hidayat at nokia dot com
*Intended audience: application developers
*Talk type: introduction and workshop
*Abstract/description
: WebKit has evolved over time into one of the most compelling HTML rendering engine currently in use. As an open-source project it stands out because of its size and because of the special collaboration between volunteer developers and companies.
: This presentation is not so much a presentation in the classic sense but planned as an introduction to the team rules of the WebKit project, e.g. how to create patches, ask for review, get in contact with the developer, etc. It will be followed by an extended question and answers session that should cover the most important and mots common questions.

*Author bio
: Ariya is a software engineer at Nokia, Qt Development Frameworks in Oslo. He is an open-source advocate for almost a decade, writing code for projects like KDE, WebKit and of course Qt. He posts lots of examples for Qt Labs Blogs on a biweekly basis, under the pretext of attracting more developers to use Qt (and hopefully grabbing the Most Prolific Blogger award). Ariya obtained his PhD in the field of high-speed optical communications. He speaks English with an Asian accent and cannot play any musical instruments.

===Preparing your Qt Application for Fremantle and Harmattan===
*Ian Monroe <ian.monroe at collabora.co.uk>
*Intended audience: application developers
*Talk type: Presentation/BoF
*Abstract/description
:An initial short presentation about Qt on Fremantle, what the Qt platform might look like on Harmattan and the status of the QtMobility project will be followed by a guided audience discussion.

The group discussion will be about the unique issues of developing on this new Qt platform, and the challenges and feasiblity of porting existing desktop applicaitons.
*Integrating with Tracker
:*Telepathy
:*...and other (traditionally Gnome) parts of the Maemo stack.
*How much existing desktop GUI (if any) can be used on the small touch-screen device?
*Core/UI separation
*Developing touch screen UIs
*Additional Information
: Non-fixed chairs so that they can be put in a circular fashion (which is best for a BoF when possible).
*Author bio
: Ian is a software developer at Collabora Ltd where he works from home in Iowa City, Iowa USA. He has been a developer of the popular desktop music manager Amarok for four years. He is the maintainer of KDE's video player, Dragon Player.

=== 10 Tips for Designing Mobile Widgets ===
*Author: [http://maemo.org/profile/view/rajeshlal Rajesh Lal], rajesh.lal at nokia dot com
*Intended audience: Widget Developers/Mobile Application Developers
*Talk type: Presentation

*Abstract/description
: Do you know why only 1 percent of Mobile Widgets are successful ? What makes some widgets thrive and used by millions, and others with equal functionality bite the dust ? Make no mistakes, design of a widget is not about graphics, color or fonts. This presentation will demystify this 'invisible' layer below the surface with 10 pragmatic tips. The tips will uncover some of the most useful, and often ignored standard design principles and how to apply them in a mobile context.

*Author bio
: Rajesh lal is a Designer, Author, Technology Evangelist, and a Senior Nokia Engineer with a decade of experience in Information Technology. He has been involved in Widget design and development for last 5 years and have authored multiple books on Gadgets and Widgets. He has experience in a variety of Mobile devices, namely Sony Mylo, Window's Mobile, Apple's Iphone, Nokia S60 and Maemo devices. His blog on design and user experience can be found at http://abcofdesign.com

=== Conboy, Tomboy and Snowy ===
*[http://maemo.org/profile/view/conny Cornelius Hald]
*Intended audience: users and application developers
*Talk type: lightning talk
*Abstract/description
: Short introduction to Conboy and the new (not yet released) features, which are online synchronization with Tomboy/Gnote via the Snowy web service and plug-in support. Could include a demo if wanted.

*Author bio
: I'm a computer science student looking for distraction while writing my final thesis.

=== Behaviour-Driven Development on Maemo ===
*[http://wiki.maemo.org/User:Japolinario Jose Teixeira]
*Intended audience: Application developers & platform developers
*Talk type: Kightning talk
*Abstract/description
: '''What''' is Behaviour-Driven Development (BDD)? '''Why''' BDD matters to Maemo developers? And '''How''' to setup and open-source BDD tool-chain for Maemo ? And, finally '''How''' to make BDD funnier on a N810 device with [http://www.ruby-lang.org Ruby], [http://rspec.info/ Rspec], [http://cukes.info/ Cucumber] and [http://doc.trolltech.com/4.5/qtscript.html QtScript].
* I already made a deep dive in the subject. I try now to capture the attention of others to follow.
*Author bio
: [http://wiki.maemo.org/User:Japolinario Jose Teixeira] participated in the development of the Maemo Application Framework as Nokia trainer. Right now, he his a full-time researcher, teaching IT in a Finnish university as well. On his free-time, he contributes to open-source projects and incite many others to to the same.

=== Maemo and oFono ===

* By Rémi Denis-Courmont (remi.denis-courmont@nokia.com) and Aki Niemi (aki.niemi@nokia.com)
* For platform developers
* Presentation (could be shortened to lightning talk but...)
* oFono is an open source telephony stack for Linux. It provides an easy-to-use D-Bus interface and has support for a variety of cellular modem hardware, including Nokia cellular modems. The project is a joint effort between Intel and Nokia.

:How is it different from earlier attempts? What is it all about? What can you do with Ofono and Nokia N900?

* For demoing purpose, the presenter will need to use his own laptop and Nokia devices.

* Rémi Denis-Courmont currently works for Nokia, where he maintains the Phonet stack for the Linux kernel, the Maemo platform and the Ofono project. Outside Nokia, he's also been involved in the VideoLAN project.

Maemo.org Sprints/August 09

2009-09-01T11:30:14Z

192.100.124.218: /* Tasks */

== August 2009 Sprint planning ==

* [http://bleb.org/software/maemo/maemo-meeting-2009-08-04.txt Planning meeting]: [http://www.timeanddate.com/worldclock/fixedtime.html?month=8&day=4&year=2009&hour=13&min=30&sec=0 Tuesday, 4th August 13:30 UTC] in [[IRC|#maemo-meeting]].
* Follows [[maemo.org Sprints/July 09|July 09]]. Precedes [[maemo.org Sprints/September 09|September 09]].
* Main themes: September council election; October summit

== Tasks ==
[[:Category:Ongoing|Ongoing]] tasks carried here from the previous sprint + New tasks committed by their owners in the sprint meeting. They come from the tasks in the [[Maemo.org_backlog|Backlog]] and the [[Maemo.org_proposals|Proposals]].

{| class="wikitable"
| style="background:LightGreen" | Completed
| style="background:LightBlue" | Good progress
| Just standing
| style="background:Orange" | Some help needed!
| style="background:Tomato" | Really stuck/delayed
|}

{| class="wikitable sortable"
|-
! Task ID
! Task
! Sprint priority
! Owner
! Percentage complete
! Notes
|- style=""
| 9.08-01
| Get "Nokia patches" cleanly into Bugzilla .4 test install, dropping as many deltas as possible
| Must
| Ferenc
| 0%
|- style="background:LightGreen"
| 9.08-02
| [https://bugs.maemo.org/show_bug.cgi?id=3692 #3692] Re-import discussion karma
| Must
| Ferenc
| Done
| The dev list import has completed.
|- style="background:LightGreen"
| 9.08-03
| Fix any other logged karma issues
| Must
| Ferenc
| Done
| Checked all bugs that refer to "karma". There is no outstanding issue which should not be solved by re-importing the mailing lists.
|- style=""
| 9.06-05
| Package promotion/repository management/community QA interface
| Must
| [http://maemo.org/profile/view/xfade/ X-Fade]
| 90%
| Basic interface is in place, most tests look promising.
|- style="background:LightBlue"
| 9.08-04
| Integrate minimae into package promotion to get infrastructure & UI in place
| Must
| [http://maemo.org/profile/view/jeremiah/ Jeremiah]
| 90%
|[http://wiki.maemo.org/Extras-testing#Maemian.2FMinimae_checks_after_builds minimae checks implemented this sprint] [https://garage.maemo.org/plugins/ggit/browse.php/?p=maemian;a=blob;f=minimae;h=b0e3b3a3da646fe3e6f4e91fbf698c28798d8c30;hb=HEAD minimae in git] Have a working hook into the build system, but need to modify it.
|- style=""
| 9.06-07
| [http://bugs.maemo.org/show_bug.cgi?id=2179 Karma for applications - get agreement on formula]
| Must
| [http://maemo.org/profile/view/indeyets/ indeyets]
| 25%
| This sprint ''must'': get data, come up with proposals, communicate to -community/developers and push for consensus.
|- style=""
| 9.07-01
| Setup [[Task:Single_sign-on|SSO]]-integration (GForge)
| Must
| [http://maemo.org/profile/view/danielwilms/ danielwilms]
| 60%
|
|- style="background: LightGreen"
| 9.08-05
| Identify/communicate to tmo users about upcoming election
| Must
| [http://maemo.org/profile/view/jaffa/ Jaffa]
| 100%
| Email sent to 1,599 tmo users giving them instructions on how to link accounts
|- style="background:Tomato"
| 9.08-06
| Produce [[Maemo Summit 2009]] budget v0.99
| Must
| [http://maemo.org/profile/view/qgil/ qgil]
| 0%
| Haven't done it but the main areas are well resourced with minimum budgets committed (infra, sponsorship, merchandising and party). Planning to have the final budget ready by Sep 15.
|- style="background: LightGreen"
| 9.08-07
| Drive [[Community Council|election process]]
| Must
| [http://maemo.org/profile/view/jaffa/ Jaffa]
| 100%
| Announcements [http://lists.maemo.org/pipermail/maemo-community/2009-August/002665.html have] [http://maemo.org/community/council/maemo_community_council-election_announcement/ been] [http://talk.maemo.org/showthread.php?p=310976 published]. List of tmo users from 9.08-05 passed on to dneary.
|- style="background:LightBlue"
| 9.08-08
| Co-ordinate summit council responsibilities
| Must
| [http://maemo.org/profile/view/timsamoff/ timsamoff]
| 60%
| Merchandising/accomodation etc.
|- style="background:LightGreen"
| 9.08-09
| Promote summit & buzz/communication plan
| Must
| [http://maemo.org/profile/view/vdvsx/ VDVsx]
| Done
|[[Maemo_Summit_2009/Marketing]], [http://www.valeriovalerio.org/?p=251 Call for help] and [https://twitter.com/#search?q=%23maesum Twitter buzz]
|- style="background:Tomato"
| 9.08-10
| Draft [http://wiki.maemo.org/Extras_repository_process_definition#Quality_Assurance quality guidelines] for extras-testing to extras promotion
| Should
| [http://maemo.org/profile/view/qgil/ qgil]
| 10%
| Drafting at [[Extras-testing#Quality_criteria|Extras-testing Quality_criteria]] + [http://talk.maemo.org/showthread.php?t=30541 tmo discussion]. Well started but not concluded. Will do in this sprint, rather soon since it's needed to define 100% the promotion to Extras.
|- style="background:LightGreen"
| 9.06-12
| [https://bugs.maemo.org/show_bug.cgi?id=4405 #4405]: [[Task:Proof-read Human Interface Guidelines]]
| Should
| [http://maemo.org/profile/view/dneary/ dneary]
| DONE
| Changes are merged into official docs and are in wiki at [[Documentation/Maemo 5 Developer Guide/Human Interface Guidelines]]
|- style=""
| 9.04-05
| [[Task:Implement new maemo.org layout and style|Implement new maemo.org layout and style - Bugzilla]]
| Should
| [http://maemo.org/profile/view/andre/ Andre]
| 80%
| Rough version in place.
|- style=""
| 9.08-11
| Document & communicate packages interface to testers
| Should
| [http://maemo.org/profile/view/jaffa/ Jaffa]
| 0%
|
|- style=""
| 9.06-09
| [[Vendor Hardware Repositories]] - decide on sub-tasks for next sprint
| Should
| [http://maemo.org/profile/view/stskeeps/ Stskeeps]
| 0%
|
|- style="background:Tomato"
| 9.06-14
| Plan for the OMAP2 acceleration [[Drivers justification|drivers]]
| Could
| [http://maemo.org/profile/view/qgil/ qgil]
| 10%
| TI contact has resources ready. They are getting access to the source code from TI and maemo in order to start the work. Maybe completed during the September sprint?
|- style=""
| 9.08-12
| Improve reporting feed appearance on sprint page
| Could
| Ferenc
| 0%
| To liaise with [http://maemo.org/profile/view/jaffa/ Jaffa]
|- style=""
| 9.04-08
| [[ITP]] process/workflow around [http://test.maemo.org/cgi-bin/itp.cgi prototype]
|Could
| [http://maemo.org/profile/view/jeremiah/ Jeremiah]
| 90%
|
|}

== Actions ==
* [http://maemo.org/profile/view/jaffa/ Jaffa]: <s>try and get some UI love for 9.06-05</s> [http://talk.maemo.org/showthread.php?p=308799 done]
* [http://maemo.org/profile/view/timsamoff/ timsamoff]: to talk to [http://maemo.org/profile/view/keesj/ keesj] about accomodation and merchandise production in Amsterdam as part of 9.08-08.
*[http://maemo.org/profile/view/vdvsx/ VDVsx]: 9.08-09 done for this sprint, I'll continue with the task in the next sprint.

== Activity log ==
Latest activity report goes on top. Activity will be reported here, [http://www.qaiku.com/channels/show/maemork/ Qaiku #maemork channel] ([http://www.qaiku.com/feeds/channels/maemork Atom feed]) or talk.maemo.org.

<rss title="off" desc="off" number="40" time="3600">http://pipes.yahoo.com/pipes/pipe.run?_id=mvdCJrB_3hGfIDijIDfpSg&_render=rss</rss>

[[Category:Community]]
[[Category:maemo.org]]

Maemo Summit 2009

2009-08-19T05:27:08Z

192.100.124.218: /* Friday, October 9 */

Content will be the second most important aspect of the conference, after the social aspect of getting the Maemo community together.

== DRAFT Schedule ==

=== Friday, October 9 ===

9:30 Doors open

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''Maemo – Designed for Mobile Computing Experience''' by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia

11:00 '''The Changing PC & Mobile Landscape; Why Linux will play a Critical Role''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''Nokia Nseries Devices on Maemo ''' by J-P. Sipponen, Director - Maemo Products @ Nokia

12:15 '''Harmattan Highlights - Developer Opportunities ''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia

13:00 '''Lunch - Maemo 5 Experience Area opens'''

14:15 '''Why the Maemo Community matters to Nokia ''' - Alan "[http://maemo.org/profile/view/qole/ Qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-

|-
| 15:00 - 15:25
| '''UI design of Maemo 5 apps'''
''Digia/User Experience Team''

| rowspan="2" |'''UX panel'''
''Moderated by: [http://maemo.org/profile/view/timsamoff Tim Samoff], Maemo Council,''
''with Harri Kiljander, Director Maemo UX Design and Martin Schüle, Principal Designer Maemo 5''
| Platform Developers 1
|-
| 15:30 - 15:55
| '''Developing widgets on Maemo 5 - showcase Foreca Weather'''
''Juha Järvi, Software Designer, Foreca''
| '''Mer - how the community innovates'''
''Carsten Munk, Lead Developer, Mer project''
|-
| 16.00 - 16.25
| App developers 3
| '''Firefox on Maemo'''
''Stuart Parmenter, Director of Engineering, Mozilla''
| | '''Your foundation for open-source innovation: TI’s OMAP processor-based Zoom platform'''
''Ameet Suri, Texas Instruments''
|-
| 16.30 - 16.55
| '''Developing apps with Qt on Harmattan'''
''Ville Lavonius, Product Manager Developer Offering, Nokia''
| '''Making of maemo.nokia.com'''
''Isko Salminen, Production Manager, Activeark
''and Jussi Mäkinen, Maemo Marketing, Nokia'''''
| Platform developers 4
|-
| 17.00 - 17.25
| '''Developing apps with Nokia Web Runtime'''
''Santtu Ahonen, Head of Developer Offering, Nokia''
| '''Biz apps on Maemo'''
''Kari Pikkarainen, Product Manager Productivity, Nokia''
| Platform developers
|-
| 17.30 - 18.00
| '''Developer Support for Maemo by Forum Nokia'''
''Srikanth Raju, Director, Forum Nokia Marketing''
| '''Skype on Maemo'''
''Mark Douglas, Mobile Product Manager, Skype''
| '''Developing apps with Open GL ES 2.0'''
''Kate Ahola, Forum Nokia, Chief Guru on Maemo''
|-
| colspan="3" |
|}

18:00 '''Maemo 5 Experience Area opens again'''

20:00 '''Maemo Party''' coordinated by Jussi Mäkinen.

=== [[/Day 2 | Saturday, October 10]] ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.15
| colspan="3" align="center" | '''Welcome to Community days''' ''Maemo Community Council''
|-
| 10.15 - 11:00
| colspan="3" align="center" | Keynote 1
|-
| 11.00 - 11.25
| Users 1
| [[/Day 2#PyQt_application_development_on_Maemo | '''PyQt application development on Maemo''']] 
''Attila Csipa''
| Platform developers 1
|-
| 11.30 - 11.55
| Users 2
| [[/Day 2#Canola_application_and_framework_for_rich_GUI | '''Canola application and framework for rich GUI''']] 
''Gustavo Sverzut Barbieri''
| [[/Day 2#Maemomm:_Maemo_with_C.2B.2B_and_a_Gtkmm_flavour | '''Maemomm: Maemo with C++ and a Gtkmm flavour''']] 
''David King''
|-
| 12.00 - 12.25
| [[/Day_2#Maemo_Co-creation | '''Maemo Co-Creation Showcase''']] 
''Jussi Mäkinen''
|
| [[/Day 2#Developments_in_The_Qt_WebKit_Integration | '''Developments in The Qt WebKit Integration''']] 
''Kenneth Rohde Christiansen''
|-
| 12.30 - 12.55
| [[/Day 2#Modest.2C_email_client_for_Fremantle | '''Modest, email client for Fremantle''']] 
''Sergio Villar, Jose Dapena''
| [[/Day 2#Creating_packages_for_the_Maemo_platform | '''Creating packages for the Maemo platform''']] 
''Jeremiah Foster''
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Mobile_web_apps_on_tablets_:_the_web2py_framework_revisited | '''Mobile web apps on tablets : the web2py framework revisited''']] - ''Fred Pacquier''
# [[/Lightning talks#Giving_Great_Presentations | '''Giving Great Presentations''']] - ''Dave Neary''
# [[/Lightning talks#Development_Nirvana:_How_Maemo_Application_Development_Should_Be | '''Development Nirvana: How Maemo Application Development Should Be''']] - ''Andrew Flegg''
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 15.55
| Users 5
| [[/Day 2#Adapting_GNOME_applications_to_Maemo_Fremantle | '''Adapting GNOME applications to Maemo Fremantle''']] 
''Joaquim Rocha''
| Platform developers 5
|-
| 16.00 - 16.25
| [[/Day 2#Mer:_A_year_after| '''Mer: A year after''']] 
''Carsten Valdemar Munk''
| [[/Day 2#Money_for_nothing:_Making_money_off_free_software | '''Money for nothing: Making money off free software''']] 
''Dave Neary''
| [[/Day 2#Hildon_toolkit_for_Fremantle | '''Hildon toolkit for Fremantle''']] 
''Alberto Garcia, Claudio Saavedra''
|-
| 16.30 - 16.55
| [[/Day 2#maemo.org_Bug_Management | '''maemo.org Bug Management''']] 
''Andre Klapper''
| [[/Day 2#Go-to_market_opportunities_for_mobile_application_developers | '''Go-to market opportunities for mobile application developers''']] 
''Boaz Zilberman''
| Platform developers 7
|-
| 17.00 - 17.25
| Users 8
| App developers 8
| Platform developers 8
|-
| 17.30 - 17.55
| Users 9
| App developers 9
| Platform developers 9
|}

=== [[/Day 3 | Sunday, October 11]] ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.55
| colspan="3" align="center" | [[/Day 3#Fremantle_Stars_showcase | '''Fremantle Stars showcase''']] Including liqbase, OSM2Go, Mauku, OMWeather and more.
|-
| 11.00 - 11.25
| Users 1
| [[/Day 3#JamMo_-_Jamming_mobile_game_for_children | '''JamMo - Jamming mobile game for children''']] 
''Aapo Rantalainen''
| Platform developers 1
|-
| 11.30 - 11.55
| [[/Day 3#Maemo_documentation_co-creation | '''Maemo documentation co-creation ''']] 
''Dave Neary''
| App developers 2
| Platform developers 2
|-
| 12.00 - 12.25
|rowspan="2" | [[/Day 2#Maemo_Co-creation | '''Maemo Co-Creation Working Session''']] ''Jussi Mäkinen''
| [[/Day 3#Handheld_Glom:_Easy_database_applications | '''Handheld Glom: Easy database applications''']] 
''Murray Cumming''
| Platform developers 3
|-
| 12.30 - 12.55
| App developers 4
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 16.30
| colspan="3" align="center" | Final Session (round table ???)
|}

See [[../Submissions | the submission queue]] for current proposals under consideration.

=== Principles for defining the schedule ===
* Defaulting to three tracks for Users (Transformatorhuis - big), App Developers (Machinegebow - medium) and Platform Developers (De Kapel - small). Exceptions can be made of course but the idea is that each profile should have a suggested session to go at any time.
* Keynotes and Lightning Sessions are organized in Transformatorhuis without other activities at the same time.
* The tiny lovely Oostelijk Meterhuis is available for longer sessions with 25 people or less e.g. a 2h workshop. De Kapel can also serve that purpose if needed.

== Timeline ==

* Decide on conference infrastructure and put it in place: DONE: Using Wiki
* Decide on process for getting content: DONE: Call for content + committee to choose presentations
* Issue call for content if necessary: DONE: Call for content issued, we need to do some more communication work & get proposals
* Deadline for content proposals: September 13
* Presenters notified: On going

== Suggestions ==
:I think that 2009 will be Fremantle year, so I expect a summit focused on:
:* New technologies showcase (i.e., what can be done with clutter?)
:* New hardware features
:And I would add one or two roundtables to talk and discuss:
:* What's next?
:* What about past hardware? What about third party development?
:* Would you like a Maemo App Store?
:—[[user:jsmanrique|jsmanrique]]

: Mer would like to talk about bringing as much of Fremantle as possible to older devices and how it works with Nokia and the community. Would there be interest in:
:* Talks about Mer?
:* Mer's development SDK/processes?
:* Hands-on Mer development sessions?
:* Mer/Maemo/Garage/Nokia integration (although this is already a fast moving target)
:-- [[User:lbt|lbt]] 21:04, 17 June 2009 (UTC)

: Please, do not put similar themes overlapping on simultaneous tracks. For example, UI Design, UX panel and OpenGL would have the same audience although the presentations are from different point of view. (As an application developer, I would participate in all of those!) Try to organize the themes more sequentially.
: --[[User:hhedberg|hhedberg]] 06:29, 2 July 2009 (UTC)

Maemo Summit 2009/Submissions

2009-08-05T06:49:57Z

192.100.124.218:

Maemo Summit 2009/Schedule/MaemoCoCreation

2009-07-01T12:56:21Z

192.100.124.218: Maemo co-creation

'''About'''

Maemo co-creation workshops are annual sessions where selected [http://en.wikipedia.org/wiki/Lead_user lead users] + Maemo product managers, designers and marketeers together imagine the future use-cases for Maemo Devices.

Maemo co-creation 2009 will now open up for the Maemo community by presenting the workshop results on the Saturday showcase and crafting the ideas forward with anyone willing to participate on our Sunday working session.

Organizer:

[http://twitter.com/luovanto Jussi Mäkinen] is responsible for consumer marketing & co-creation activities @ Maemo Devices. Cool stuff to put it shortly.

Maemo Summit 2009

2009-07-01T12:55:25Z

192.100.124.218: /* Sunday 11 */

Content will be the second most important aspect of the conference, after the social aspect of getting the Maemo community together.

== DRAFT Schedule ==

=== Friday 9 ===

9:30 Doors open

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''Maemo – Designed for Mobile Computing Experience''' by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia

11:00 '''Linux Foundation view''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''Nokia Nseries Devices on Maemo ''' by J-P. Sipponen, Director - Maemo Products @ Nokia

12:15 '''Harmattan Highlights - Developer Opportunities ''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia

13:00 '''Lunch - Maemo 5 Experience Area opens'''

14:15 '''Why the Maemo Community matters to Nokia ''' - Alan "[http://maemo.org/profile/view/qole/ Qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-

|-
| 15:00 - 15:25
| '''UI design of Maemo 5 apps'''
''Digia/User Experience Team''

| Power users 1
| '''Developing apps with Open GL ES 2.0'''
''Kate Ahola, Forum Nokia, Chief Guru on Maemo''
|-
| 15:30 - 15:55
| App developers 2
| Power users 2
| Platform developers 2
|-
| 16.00 - 16.25
| App developers 3
| Power users 3
| Platform developers 3
|-
| 16.30 - 17.55
| App developers 4
| '''Making of Maemo digital marketing - maemo.nokia.com'''
''Isko Salminen, Production Manager, Activeark
''and Jussi Mäkinen, Maemo Marketing, Nokia''''''
| Platform developers 4
|-
| colspan="3" |
|}

18:00 '''Maemo 5 Experience Area opens again'''

20:00 '''Maemo Party''' coordinated by Jussi Mäkinen

=== Saturday 10 ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.55
| colspan="3" align="center" | Keynote 1
|-
| 11.00 - 11.25
| Users 1
| [[/Day 2#PyQt_application_development_on_Maemo | PyQt application development on Maemo (attila77)]]
| Platform developers 1
|-
| 11.30 - 11.55
| Users 2
| App developers 2
| Platform developers 2
|-
| 12.00 - 12.25
| Users 3
| App developers 3
| Platform developers 3
|-
| 12.30 - 12.55
| Users 4
| App developers 4
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Mobile_web_apps_on_tablets_:_the_web2py_framework_revisited | Mobile web apps on tablets : the web2py framework revisited]]
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 15.55
| Users 5
| App developers 5
| Platform developers 5
|-
| 16.00 - 16.25
| Users 6
| App developers 6
| Platform developers 6
|-
| 16.30 - 16.55
| Users 7
| App developers 7
| Platform developers 7
|-
| 17.00 - 17.25
| Users 8
| App developers 8
| Platform developers 8
|-
| 17.30 - 17.55
| [[/MaemoCoCreation | '''Maemo Co-Creation Showcase''']]
| App developers 9
| Platform developers 9
|}

=== Sunday 11 ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.55
| colspan="3" align="center" | Keynote 1
|-
| 11.00 - 11.25
| Users 1
| App developers 1
| Platform developers 1
|-
| 11.30 - 11.55
| Users 2
| App developers 2
| Platform developers 2
|-
| 12.00 - 12.25
| [[/MaemoCoCreation | '''Maemo Co-Creation Working Session''']]
| App developers 3
| Platform developers 3
|-
| 12.30 - 12.55
| [[/MaemoCoCreation | '''Maemo Co-Creation Working Session''']]
| App developers 4
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''Lightning talks''', 5 min each
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 16.30
| colspan="3" align="center" | Final Session (round table ???)
|}

See [[../Submissions | the submission queue]] for current proposals under consideration.

=== Principles for defining the schedule ===
* Defaulting to three tracks for Users (Transformatorhuis - big), App Developers (Machinegebow - medium) and Platform Developers (De Kapel - small). Exceptions can be made of course but the idea is that each profile should have a suggested session to go at any time.
* Keynotes and Lightning Sessions are organized in Transformatorhuis without other activities at the same time.
* The tiny lovely Oostelijk Meterhuis is available for longer sessions with 25 people or less e.g. a 2h workshop. De Kapel can also serve that purpose if needed.

== Timeline ==

* Decide on conference infrastructure and put it in place: DONE: Using Wiki
* Decide on process for getting content: DONE: Call for content + committee to choose presentations
* Issue call for content if necessary: DONE: Call for content issued, we need to do some more communication work & get proposals
* Deadline for content proposals: September 13
* Presenters notified: On going

== Suggestions ==
:I think that 2009 will be Fremantle year, so I expect a summit focused on:
:* New technologies showcase (i.e., what can be done with clutter?)
:* New hardware features
:And I would add one or two roundtables to talk and discuss:
:* What's next?
:* What about past hardware? What about third party development?
:* Would you like a Maemo App Store?
:—[[user:jsmanrique|jsmanrique]]

: Mer would like to talk about bringing as much of Fremantle as possible to older devices and how it works with Nokia and the community. Would there be interest in:
:* Talks about Mer?
:* Mer's development SDK/processes?
:* Hands-on Mer development sessions?
:* Mer/Maemo/Garage/Nokia integration (although this is already a fast moving target)
:-- [[User:lbt|lbt]] 21:04, 17 June 2009 (UTC)

Maemo Summit 2009

2009-07-01T12:45:49Z

192.100.124.218: /* Saturday 10 */

Content will be the second most important aspect of the conference, after the social aspect of getting the Maemo community together.

== DRAFT Schedule ==

=== Friday 9 ===

9:30 Doors open

10:00 '''Welcome - Opening of Summit ''' by [http://maemo.org/profile/view/peterschneider.html Peter Schneider], Head of Maemo Marketing @ Nokia

10:15 '''Maemo – Designed for Mobile Computing Experience''' by [http://maemo.org/profile/view/jaaksi/ Ari Jaaksi], VP - Maemo Devices @ Nokia

11:00 '''Linux Foundation view''' by Jim Zemlin, Executive Director @ Linux Foundation

11:30 '''Break'''

11:45 '''Nokia Nseries Devices on Maemo ''' by J-P. Sipponen, Director - Maemo Products @ Nokia

12:15 '''Harmattan Highlights - Developer Opportunities ''' by Janne Heikkinen, Director - Maemo Product Planning @ Nokia

13:00 '''Lunch - Maemo 5 Experience Area opens'''

14:15 '''Why the Maemo Community matters to Nokia ''' - Alan "[http://maemo.org/profile/view/qole/ Qole]" Bruce of [[Community Council|Maemo Community Council]] interviewing Ari Jaaksi, VP - Maemo Devices @ Nokia

15:00 '''Expert streams'''

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-

|-
| 15:00 - 15:25
| '''UI design of Maemo 5 apps'''
''Digia/User Experience Team''

| Power users 1
| '''Developing apps with Open GL ES 2.0'''
''Kate Ahola, Forum Nokia, Chief Guru on Maemo''
|-
| 15:30 - 15:55
| App developers 2
| Power users 2
| Platform developers 2
|-
| 16.00 - 16.25
| App developers 3
| Power users 3
| Platform developers 3
|-
| 16.30 - 17.55
| App developers 4
| '''Making of Maemo digital marketing - maemo.nokia.com'''
''Isko Salminen, Production Manager, Activeark
''and Jussi Mäkinen, Maemo Marketing, Nokia''''''
| Platform developers 4
|-
| colspan="3" |
|}

18:00 '''Maemo 5 Experience Area opens again'''

20:00 '''Maemo Party''' coordinated by Jussi Mäkinen

=== Saturday 10 ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.55
| colspan="3" align="center" | Keynote 1
|-
| 11.00 - 11.25
| Users 1
| [[/Day 2#PyQt_application_development_on_Maemo | PyQt application development on Maemo (attila77)]]
| Platform developers 1
|-
| 11.30 - 11.55
| Users 2
| App developers 2
| Platform developers 2
|-
| 12.00 - 12.25
| Users 3
| App developers 3
| Platform developers 3
|-
| 12.30 - 12.55
| Users 4
| App developers 4
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''[[/Lightning talks | Lightning talks]]''', 5 min each
# [[/Lightning talks#Mobile_web_apps_on_tablets_:_the_web2py_framework_revisited | Mobile web apps on tablets : the web2py framework revisited]]
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 15.55
| Users 5
| App developers 5
| Platform developers 5
|-
| 16.00 - 16.25
| Users 6
| App developers 6
| Platform developers 6
|-
| 16.30 - 16.55
| Users 7
| App developers 7
| Platform developers 7
|-
| 17.00 - 17.25
| Users 8
| App developers 8
| Platform developers 8
|-
| 17.30 - 17.55
| [[/MaemoCoCreation | '''Maemo Co-Creation Showcase''']]
| App developers 9
| Platform developers 9
|}

=== Sunday 11 ===

{| class="wikitable" border="2"
|-
! Time
! Track 1
! Track 2
! Track 3
|-
| align="right" | 9.00
| colspan="3" align="center" | Doors Open
|-
| 10.00 - 10.55
| colspan="3" align="center" | Keynote 1
|-
| 11.00 - 11.25
| Users 1
| App developers 1
| Platform developers 1
|-
| 11.30 - 11.55
| Users 2
| App developers 2
| Platform developers 2
|-
| 12.00 - 12.25
| Users 3
| App developers 3
| Platform developers 3
|-
| 12.30 - 12.55
| Users 4
| App developers 4
| Platform developers 4
|-
| 13.00 - 14.30
| colspan="3" align="center" | Lunch
|-
| 14.30 - 15.25
| colspan="3" | '''Lightning talks''', 5 min each
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
# Lightning talk
|-
| 15.30 - 16.30
| colspan="3" align="center" | Final Session (round table ???)
|}

See [[../Submissions | the submission queue]] for current proposals under consideration.

=== Principles for defining the schedule ===
* Defaulting to three tracks for Users (Transformatorhuis - big), App Developers (Machinegebow - medium) and Platform Developers (De Kapel - small). Exceptions can be made of course but the idea is that each profile should have a suggested session to go at any time.
* Keynotes and Lightning Sessions are organized in Transformatorhuis without other activities at the same time.
* The tiny lovely Oostelijk Meterhuis is available for longer sessions with 25 people or less e.g. a 2h workshop. De Kapel can also serve that purpose if needed.

== Timeline ==

* Decide on conference infrastructure and put it in place: DONE: Using Wiki
* Decide on process for getting content: DONE: Call for content + committee to choose presentations
* Issue call for content if necessary: DONE: Call for content issued, we need to do some more communication work & get proposals
* Deadline for content proposals: September 13
* Presenters notified: On going

== Suggestions ==
:I think that 2009 will be Fremantle year, so I expect a summit focused on:
:* New technologies showcase (i.e., what can be done with clutter?)
:* New hardware features
:And I would add one or two roundtables to talk and discuss:
:* What's next?
:* What about past hardware? What about third party development?
:* Would you like a Maemo App Store?
:—[[user:jsmanrique|jsmanrique]]

: Mer would like to talk about bringing as much of Fremantle as possible to older devices and how it works with Nokia and the community. Would there be interest in:
:* Talks about Mer?
:* Mer's development SDK/processes?
:* Hands-on Mer development sessions?
:* Mer/Maemo/Garage/Nokia integration (although this is already a fast moving target)
:-- [[User:lbt|lbt]] 21:04, 17 June 2009 (UTC)

Maemo Summit 2009/Schedule/MaemoCoCreation

2009-07-01T12:40:30Z

192.100.124.218: Maemo Co-Creation Showcase

'''About'''

Maemo co-creation workshops are annual sessions where selected [http://en.wikipedia.org/wiki/Lead_user lead users] + Maemo product managers, designers and marketeers together imagine the future use-cases for Maemo Devices.

Maemo Co-Creation 2009 will now open up for the Maemo community by presenting the workshop results on the Saturday showcase and crafting the ideas forward with anyone willing to participate on our Sunday working session.

Organizer:

[http://twitter.com/luovanto Jussi Mäkinen] is responsible for consumer marketing & co-creation activities @ Maemo Devices. Cool stuff to put it shortly.