Maemo Wiki Mirror - User contributions [en]

Bluetooth PBAP pre 0.46

2010-08-26T13:48:05Z

192.100.116.143: /* Via PBAP: */

The following is a summary of those two threads on talk.maemo.org:

* [http://talk.maemo.org/showthread.php?t=36272 "Car kit can not access contact information"]
* [http://talk.maemo.org/showthread.php?t=59114 Announce - Bluetooth PBAP and IrMC / Carkit support is coming to N900...].

For further information you might want to check these threads.

Please post to the second one to get support and share your experiences with this solution there as well!!!

== General Information ==

=== PBAP ===

The Bluetooth Phone Book Access Profile (PBAP) allows to exchange Phone Book objects between carkits and mobile devices. In other words, PBAP profile gives your car unit read access to your mobile phone book (to be exact: to both, the phonebook stored on SIM card and the phone book stored on internal memory. But for the N900 only second one is relevant).

Described in a more specific way, whenever a connection between your carkit and your PBAP enabled phone is established, your phone book will be transfered to your carkit automatically. What happens from now with the transfered phone book of course depends on the features of your carkit. Typical use cases are browse and dial (voice-dial if supported by carkit) your contacts and show caller names for incoming calls. With an integrated In-Car Infotainment/Phone/Navigation/Whatever system it is even possible to use the contacts addresses as target for the navigation system.

By default N900 does NOT support PBAP and thus the in-car use cases described above are either not possible or require manual workarounds as the in other threads described "Petrovich workaround" (manual sending of vCards via Bluetooth) or OPP (Object Push Profile - A Bluetooth profile that enables a Bluetooth device to transfer (push) an object (e.g. contact) to another Bluetooth device).

=== IrMC ===

This project also aims to provide IrMC support. IrMC is another method to transfer the phone book to e. g. a car kit via Bluetooth which is by default not supported by N900.

Here comes the good news:
<div style="text-align:center;">'''NOW YOU CAN HAVE PBAB and IrMC ON YOUR N900 !!!'''</div>

== Credits ==

Credits for the achieved so far go to those who contributed in the old thread [http://talk.maemo.org/showthread.php?t=36272 "Car kit can not access contact information"] as well as the new thread [http://talk.maemo.org/showthread.php?t=59114 Announce - Bluetooth PBAP and IrMC / Carkit support is coming to N900...]:

Especially the developers: drdrewusaf, tuxy, jarmo2, hschmitt, Ossman, mirakels..., but of course also all the others who helped with testing and troubleshooting!

== Disclaimer ==

'''!!! CAUTION !!!'''

This project is still in development stage, which means there are still some risks, downsides and issues to be solved before PBAB on N900 is ready for the average user...(see below).

Please read this summary carefully and evaluate the risks involved for yourself!
(Keep in mind that this can cause problems for the phone. Backup your data, backup your config (apps > system > backup) and know how to reflash)

'''Whatever you do, you are doing it at your own risk!'''

However, if you want to have PBAB / IrMC and want to help out here -

'''You are more than welcome as a tester or even developer.'''

Of course, before you start playing with your phone, you should check if your carkit does support PBAP / IrMC.

If it does not, this solution can not help you - Sorry!

(Note: Carkits older than 2007 probably do NOT support PBAP)

== Current Project Status: ==

===''' Supported Carkits '''===

So far, successful phonebook transfers were reported for the following carkits:

(If you are able to successfully transfer your phonebook to any carkit not listed here, please let us know or just add to following list!):

===='''Via PBAP:'''====

Built-In Carkits:

* 2010 Mini One
* 2008 BMW 120d
* 2010 BMW 1series
* 2008 BMW 318d
* 2008 BMW 320d with Business Navi
* 2011 BMW 335d (US with NAV / iDrive)
* 2008 BMW 535d Touring with Navigationsystem Professional
* 2009 BMW 5series
* 2010 BMW X1
* 2007 BMW X5 E70
* 2009 Audi A3 (facelift) with Radio Concert and bluetooth preparation
* 2010 Audi A3 with RNS-E and bluetooth preparation
* 2009 Audi with RNS-E
* 2010 Audi A4 with MMI (usable, BUT reads double entries, looks like phonebook is both on N900 and on SIM-card)
* 2009 Skoda Oktavia from 2009 (Model 2010)
* 2010 Skoda Octavia with built-in "Bolero" type radio/CD player and BT car kit
* 2010 Peugeot 5008 Connect Nav carkit
* 2009 Seat Exeo
* 2010 Toyota Prius MY
* 2007 Ford Mondeo Navigationsystem NX with Touchscreen
* 2010 Ford Galaxy Navigation with Touchscreen
* 2010 Ford Focus with Ford 6000CD
* Vauxhall (Model unknown)
* Citroen (Model unknown)
* 2007 Land Rover Discovery 3
* European Honda Accord 2009 HFT system with SatNav

Stand alone devices:

* Bury AD9060
* Bury CC9056
* Parrot MKi9100
* Parrot MKi9200
* Kenwood DNX6140
* Kenwood DNX9960
* Kenwood HD942U (with KCA-BT200 bluetooth module)
* Navigon 8410
* Alpine CDE-103BT (has an inbuilt parrot module)
* Parrot CK3100
* Parrot CK3200 LS-COLOR
* Parrot LG 3200
* Parrot LS 3200
* Pioneer AVH-3200BT
* Garmin nuvi 715

===='''Via IrMC'''====

Built-In Carkits:

* Citroen C4 hatch 2010
* Citroen C4 picasso
* Renault Megane Scenic 2010

Stand alone devices:

* Kenwood DNX6140
* Parrot MK6000

===''' Known issues / problems '''===

* <s>Broken PC Suite connectivity</s>
* <s>False Maemo 5 update announcement in App Manager</s> *)
* <s>In some cases broken file transfer via BT to certain devices</s>
* Sometimes contacts synced from other devices (e.g. using PC Suite) with special characters in names/details are not transferred (correctly). Recreating these contats on your N900 ''should'' solve this issue.
* Lists for outgoing/incoming/missed calls are not supported (some carkits maintain own lists)
* Installing/Removing requires manual steps in xTerm

'' *)
Please note, this problem is related to initial versions of the PBAP implementation. With the latest .deb-files this problem should be solved!

(The false Maemo5 update in app manager with early versions of PBAP/IrMC solution was related to the mp-fremantle-205-pr package.
Removing this package solved this problem, but removal of mp-fremantle-205-pr *might* cause trouble with future Maemo updates. Unfortunately keeping the package prevents uninstalling the initial PBAP implementation...(you might want to search the two threads for more information on this...).)
Any information on how to uninstall without removing the package or how to reinstall the package is very welcome!''

==''' Installation Guide '''==

Mirakels created two deb-files in order to make the installation more user friendly.
This installation is based on obexd-0.30 and provides
* PBAP support
* IrMC support
* PC Suite support
* Multiple phone numbers per contact
* Skip SIM contact requests (means contacts are not shown twice)
* vCards are separated correctly with CRLF between ENV:VCARD and BEGIN:VCARD.

=== Step 0 ===

In case you played with obex on your phone before / had previous versions of this project installed, please perform a downgrade to original version first by following the steps described in section [http://wiki.maemo.org/Bluetooth_PBAP#Downgrade_to_Original_State Downgrade to Original State]

=== Step 1 ===

Download these 2 .deb packages provided by mirakels:

[http://talk.maemo.org/attachment.php?attachmentid=12973&d=1281827814 libopenobex2_1.5_armel.deb]

[http://talk.maemo.org/attachment.php?attachmentid=12986&d=1281878114 obexd2_0.30-0maemo1_armel.deb]

=== Step 2 ===

Place them in a folder on the N900, say <code>/home/user/mypackages</code>

=== Step 3 ===

As root run (replace /home/user/mypackages with the path to the folder where you placed the files):

<source lang="bash">
cd /home/user/mypackages
dpkg -i *.deb</source>

=== Step 4 ===

Reboot the phone.
Test and ENJOY - hopefully ;-)

'''-> Please share your results !!!'''



=== Old/Obsolete Installation Guide ===

Note: The following installation steps are not necessary anymore and just kept for better understanding of what was going on so far.

Step 1

Download the following 3 files and copy them to your phone (provided by drdrewusaf):

* [http://ftp.us.debian.org/debian/pool/main/libo/libopenobex/libopenobex1_1.5-2_armel.deb Openobex 1.5-2 libraries]
* [http://ftp.us.debian.org/debian/pool/main/libo/libopenobex/openobex-apps_1.5-2_armel.deb Openobex 1.5-2 apps]
* [http://forums.internettablettalk.com/attachment.php?attachmentid=11779&stc=1&d=1278357528 obexd]

Step 2

Open a root terminal and navigate to the folder you saved the 3 files in (where "/path/to/files" is the real path to your downloaded files):

<source lang="bash">
cd /path/to/files
</source>

Step 3

Install the packages.
As root run:

<source lang="bash">
dpkg -i libopenobex1_1.5-2_armel.deb openobex-apps_1.5-2_armel.deb obexd_0.28-0maemo3_armel.deb
</source>

Step 4

Download the latest version of obexd zipped binary provided by mirakels from here

[http://talk.maemo.org/attachment.php?attachmentid=12612&d=1280519142 obex download]

This version provides:
* PBAP support (actually the plain PBAP that is in the 0.29 repo)
* IRMC sync support (only full phonebook retrieves)
* extra CR/LF between contacts
* support for multiple phone numbers per contact
* PC-Suite support (based on the patch test from hschmitt)

BUGS: pbap sends phonebook twice.

Step 5

Replace the current obexd in <code>/usr/lib/obex/obexd</code> with the new one from mirakels,
as root run:

<source lang="bash">
cd <where your new version is>
gunzip obexd.gz
mv obexd /usr/lib/obex/obexd
</source>

Make sure that it is excecutable

<source lang="bash">
chmod a+x /usr/lib/obex/obexd
</source>

Step 6

Edit the obex start command in ''/usr/share/dbus-1/services/obexd.service'':
* for PBAB include the option ''--pbap'' (already added after previous steps),
* for IRMC include the option ''--irmc'' (both is possible too),
* for PC Suite connection add ''--capability !/usr/bin/gen-obex-capability.sh''

Step 7

Reboot, test and ENJOY - hopefully ;-)

'''-> Please share your results !!!'''


== Troubleshooting ==

For troubleshooting install and use hcidump and/or syslog

=== Download and install hcidump ===

First you need to add the developer repository, see [[Documentation/devtools/maemo5#Installation the devtools installation instructions]].

After adding the repository, run the following command as root:

<source lang="bash">
apt-get install bluez-hcidump</source>

OR if the above fails, try the following steps:

# Download the deb-package containing hcidump from here: [http://repository.maemo.org/pool/fremantle/free/b/bluez-hcidump/bluez-hcidump_1.42-0maemo2_armel.deb hcidump download]
# Unpack it (alien on Linux, 7-zip on Windows)
# Copy <code>/usr/sbin/hcidump</code> to the N900
# In xTerm as root:<source lang="bash">chmod a+x /usr/sbin/hcidump</source>

=== Usage of hcidump ===

For testing/debugging with hcidump, run the following command (where "/some/path/somefilename" is a real path and any name you choose for your output file.)

<source lang="bash">
hcidump -w /some/path/somefilename
</source>

right before turning your head unit/car on. Then, do what you would normally do to get contacts to show up and wait for it to finish/fail. Then, press ctrl+c on the phone to exit hcidump. Finally, you can view the output/dump file with Wireshark or upload your dump files so we can see what's going on.

'''-> Please share your results !!!
'''

=== Install syslogd and enable obexd debug option ===

For further troubleshooting information you may also want to try to enable obexd syslog debugging messages:

Step 1)
Install syslogd. As root run <source lang="bash">apt-get install sysklogd</source>
Step 2)
Kill running obexd process. As root run <source lang="bash">killall obexd</source>
Step 3)
Restart obexd with enabled debug option. As root run:<source lang="bash">/usr/lib/obex/obexd --debug --opp --ftp --pcsuite --pbap --symlinks --root .obex-root --root-setup /usr/bin/obex-root-setup --capability !/usr/bin/gen-obex-capability.sh</source>
OR

Add the '''--debug''' option
in the ''/usr/share/dbus-1/services/obexd2.service'' file (for example just before the --nodaemon option).

Step 4)

Sysklogd will create a file <code>/var/log/syslog</code>

After your test copy this file to some other location (do not delete the original) and edit out the relevant part and post it [http://talk.maemo.org/showthread.php?t=59114 here].

== Downgrade to Original State ==

To reinstall the original packages:

=== Step 1 ===

Download these 2 .deb packages:

[http://repository.maemo.org/pool/fremantle/free/libo/libopenobex1/libopenobex1_1.4-0maemo3+0m5_armel.deb libopenobex1 1.4]

[http://repository.maemo.org/pool/fremantle/free/o/obexd/obexd_0.18-0maemo5+0m5_armel.deb obexd 0.18]

=== Step 2 ===

Place them in a folder on the N900, say <code>/home/user/mypackages</code>

=== Step 3 ===

As root run (replace /home/user/mypackages with the path to the folder where you placed the files):

<source lang="bash">
apt-get remove openobex-apps
cd /home/user/mypackages
dpkg -i *.deb</source>

=== Step 4 ===

Reboot the phone.

OR run as root

<source lang="bash">
apt-get install libopenobex1=1.4-0maemo3+0m5
apt-get install obexd=0.18-0maemo5+0m5
</source>

Reboot the phone.

OR run as root

<source lang="bash">
apt-get update
apt-get install --reinstall obexd libopenobex1 openobex-apps
</source>

Reboot the phone.

[[Category:N900]]
[[Category:Bluetooth]]

Mappero topomaps

2010-03-29T11:22:28Z

192.100.116.143: /* Finland */

Here are instructions to get topomaps to maemo-mapper.

== Step by step instructions ==

* Open maemo-mapper
* Tap title bar and select: Maps - Manage Tiles/Layers...
* Add new and set Name, UniqIDand and Cache Dir for example: NLS
* Paste correct address below to URL-field
* Set type according to information below
* Set image type according to information below
* Save settings

* Next tap title bar again and select: Maps - Manage Repositories...
* Add new and set name for example: NLS
* Select Min zoom: 5
* Select Max zoom: 20
* select zoom step: 1
* Select Tiles: NLS (or whatever name you set earlier for tiles)
* Then save repository

== Local repositories ==

=== Finland ===

http://tableteer.nokia.com:80 © NLS 20O8 …þ@topomaps.tableteer.nokia.com/_tTilesD/%0d/%d/%d.jpg

'''Repository settings for Mapper alpha 8(and newer)'''

Tile type: XYZ_INV
Image type: JPEG

[http://laimeasilli.wordpress.com/2009/12/27/maastokartat-toimivat-n900ssa/#comment-906]
[http://talk.maemo.org/showpost.php?p=564697&postcount=13]

[[Category:Beginners]]
[[Category:GPS]]

Qt4 hildon applications

2009-09-30T05:32:56Z

192.100.116.143: /* Image:TestingApp-icon32.png Tested Qt Applications */

==[[Image:Available-qtapps-32.png]] Ported Qt Applications==
These applications are already available in Maemo extras repositories.

These applications are tested also with Fremantle. If not, that should be mentioned. For Fremantle most applications need re-compiling/-packaging.

They live in extras if they are stable or extras-devel if they are not fully tested.

These entries should have at least:
* Application Name
* Short Description
* Website or link to the original sources
* Maemo website (If any)
* Bug reporting: Bug report tool link or author contact
* Repository: Extras and/or Extras-Devel

===Peg-E===
* Description: Peg-E is a peg solitaire game...
* Website: http://gottcode.org/peg-e/
* Maemo website: http://maemo.org/downloads/product/OS2008/peg-e
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Qt-Maemo-Example===
* Description: Simple text editor
* Website: http://www.trolltech.com
* Maemo website: http://maemo.org/downloads/product/OS2008/qt-maemo-example
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Simsu===
* Description: Sudoku game written in Qt
* Website: http://gottcode.org/simsu/
* Maemo website: http://maemo.org/downloads/product/OS2008/simsu/
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Shopper===
* Description: Shopping List application
* Website: http://shopper.garage.maemo.org/
* Maemo website: http://maemo.org/downloads/product/OS2008/shopper/
* Bug Reporting: http://bugs.maemo.org/enter_bug.cgi?product=shopper
* Repository: Extras

 
 

==[[Image:TestingApp-icon32.png]] Tested Qt Applications==
These applications are not yet in the Maemo extras repositories.

If you have tested a Qt application just for fun or because you are going to port an application that you haven't packaged for Maemo yet

then this is the right place to put some notes about it.

These applications are tested also with Fremantle. If not, that should be mentioned. For Fremantle most applications need re-compiling/-packaging.

The entries in this section should have at least:
* Application Name
* Short Description
* Website or link to the original sources
* Maemo tester contact
* TODO list

===RetroMessenger===

* Application Name: RetroMessenger
* Short Description
It is a server less and most secure Instant messenger based on QT and retroshare (http://retroshare.sf.net) having features of chat and Link-sharing and also available feature which can be included on requirement are Message, File sharing and Games.Further new implementation subject to available support in retroshare library is "VOIP".

* Website or link to the original sources
http://retromessenger.sf.net.
https://retromessenger.svn.sourceforge.net/svnroot/retromessenger/QTRS_retromessenger_mingw_SVN1139/retroshare/trunk/retroshare-gui/src/

* Maemo tester contact: panpaliamahen@gmail.com
* TODO list
(1)To test on target with "ARMEL" compile.
(2)Need to do packaging for Maemo (binary and used dlls are available, so
also require to make a debian package if required ).
(3)Need to take care of available maximum Memory uses and few user
interfaces are required to cutomize according to size of mobile screen.

===Arora===
* Description: http://code.google.com/p/arora/
* Website: http://code.google.com/p/arora/
* Tester: antonio.aloisio AT gmail.com
* TODO
** There are too much menu entries. Remove them.
** Adapt the debian package to Maemo
* Sceenshots/Videos:

===Minitube===
* Description: http://www.qt-apps.org/content/show.php/Minitube?content=104895
* Website: http://www.qt-apps.org/content/show.php/Minitube?content=104895
* Tester: eetu.lehmusvuo AT ixonos.com
* TODO
** Adapt the debian package to Maemo
* Sceenshots/Videos:
 
 

==[[Image:Ktip.png]] Proposed Qt Application to port/write==
If you are looking forward to see a specific Qt application in Maemo, then you can propose here to the Maemo Qt community to port/Write that app in/for Maemo.

The entries in this section must have at least:
* Application name (you can suggest a name if the app doesn't exist yet)
* Application description
* Applicant/s - if an application has been already requested and you really want to see that app in Maemo, then you can add your contact here next to the others.

===Blog client===
* Full featured blog client
** WYSIWYG editor
** Media upload support
* Applicant/s:
** antonio.aloisio AT gmail.com
** your.name AT mail.org

Qt4 hildon applications

2009-09-30T05:30:21Z

192.100.116.143: /* Image:Available-qtapps-32.png Ported Qt Applications */

==[[Image:Available-qtapps-32.png]] Ported Qt Applications==
These applications are already available in Maemo extras repositories.

These applications are tested also with Fremantle. If not, that should be mentioned. For Fremantle most applications need re-compiling/-packaging.

They live in extras if they are stable or extras-devel if they are not fully tested.

These entries should have at least:
* Application Name
* Short Description
* Website or link to the original sources
* Maemo website (If any)
* Bug reporting: Bug report tool link or author contact
* Repository: Extras and/or Extras-Devel

===Peg-E===
* Description: Peg-E is a peg solitaire game...
* Website: http://gottcode.org/peg-e/
* Maemo website: http://maemo.org/downloads/product/OS2008/peg-e
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Qt-Maemo-Example===
* Description: Simple text editor
* Website: http://www.trolltech.com
* Maemo website: http://maemo.org/downloads/product/OS2008/qt-maemo-example
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Simsu===
* Description: Sudoku game written in Qt
* Website: http://gottcode.org/simsu/
* Maemo website: http://maemo.org/downloads/product/OS2008/simsu/
* Bug Reporting: http://qt4.garage.maemo.org/bug.html
* Repository: Extras

===Shopper===
* Description: Shopping List application
* Website: http://shopper.garage.maemo.org/
* Maemo website: http://maemo.org/downloads/product/OS2008/shopper/
* Bug Reporting: http://bugs.maemo.org/enter_bug.cgi?product=shopper
* Repository: Extras

 
 

==[[Image:TestingApp-icon32.png]] Tested Qt Applications==
These applications are not yet in the Maemo extras repositories.

If you have tested a Qt application just for fun or because you are going to port an application that you haven't packaged for Maemo yet

then this is the right place to put some notes about it.

The entries in this section should have at least:
* Application Name
* Short Description
* Website or link to the original sources
* Maemo tester contact
* TODO list

===RetroMessenger===

* Application Name: RetroMessenger
* Short Description
It is a server less and most secure Instant messenger based on QT and retroshare (http://retroshare.sf.net) having features of chat and Link-sharing and also available feature which can be included on requirement are Message, File sharing and Games.Further new implementation subject to available support in retroshare library is "VOIP".

* Website or link to the original sources
http://retromessenger.sf.net.
https://retromessenger.svn.sourceforge.net/svnroot/retromessenger/QTRS_retromessenger_mingw_SVN1139/retroshare/trunk/retroshare-gui/src/

* Maemo tester contact: panpaliamahen@gmail.com
* TODO list
(1)To test on target with "ARMEL" compile.
(2)Need to do packaging for Maemo (binary and used dlls are available, so
also require to make a debian package if required ).
(3)Need to take care of available maximum Memory uses and few user
interfaces are required to cutomize according to size of mobile screen.

===Arora===
* Description: http://code.google.com/p/arora/
* Website: http://code.google.com/p/arora/
* Tester: antonio.aloisio AT gmail.com
* TODO
** There are too much menu entries. Remove them.
** Adapt the debian package to Maemo
* Sceenshots/Videos:

===Minitube===
* Description: http://www.qt-apps.org/content/show.php/Minitube?content=104895
* Website: http://www.qt-apps.org/content/show.php/Minitube?content=104895
* Tester: eetu.lehmusvuo AT ixonos.com
* TODO
** Adapt the debian package to Maemo
* Sceenshots/Videos:
 
 

==[[Image:Ktip.png]] Proposed Qt Application to port/write==
If you are looking forward to see a specific Qt application in Maemo, then you can propose here to the Maemo Qt community to port/Write that app in/for Maemo.

The entries in this section must have at least:
* Application name (you can suggest a name if the app doesn't exist yet)
* Application description
* Applicant/s - if an application has been already requested and you really want to see that app in Maemo, then you can add your contact here next to the others.

===Blog client===
* Full featured blog client
** WYSIWYG editor
** Media upload support
* Applicant/s:
** antonio.aloisio AT gmail.com
** your.name AT mail.org

Maemo Summit 2009/Submissions

2009-09-14T10:17:15Z

192.100.116.143: /* Test framework tool for Maemo devices */

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

=== BlueMaemo - Bluetooth HID mouse & keyboard for Maemo ===
*[http://maemo.org/profile/view/vdvsx/ Valério Valério]
*Intended audience: users
*Talk type: lightning talk
*Abstract/description
: BlueMaemo is a remote controller application that turns your Maemo device in a mixed Bluetooth keyboard-and-mouse device through the HID Bluetooth profile.
: This presentation will be a showcase of the application new UI, some new features that will be introduced in Fremantle will be shown as well.

*Author bio
: Valério is a MSc researcher at University of Évora, Portugal. During his free time he has actively participated in several open source community's and projects.

=== Qt 4.6: What is comming ===

* Authors: Anselmo Lacerda Silveira de Melo - anselmo.melo AT openbossa DOT org / Jesus Sanchez-Palencia jesus.palencia AT openbossa DOT org
* Intended audience: application developers
* Talk type: presentation
* Abstract/description

The next release of Qt is comming with brand new features, such as the State Machine Framework, the Animations API, S60 port, Scoped Pointers, Anchor Layout, performance optimizations in QGraphicsView, Multi-touch Gestures, Audio Services, GraphicsEffects, etc. The goal of the talk is to provide an overview of the benefits of each new feature and how they shall change the development of Qt applications.
Also, some applications will be shown, running on Maemo 5 and S60, demonstrating how cross-platform Qt can be and what is ready for the new generation of Maemo devices.

* Author bio
Anselmo is a GNU/Linux user since 2002, works with Linux on embedded devices since 2006. Works for INdT as a researcher at the openBossa open-source stream, where develops rich UIs features for Qt and is also part of the Qt Labs Americas initiative. Whenever possible, he likes hunting bugs with the KDE Bugsquad.

Jesus works with Maemo since 2007, besides other embedded Linux projects since 2006. Has contributions to the ERESI project (Elf Reverse Engineering Software Interface), and nowadays works at openBossa, INdT open-source stream, where develops rich UIs features for Qt and is also part of the Qt Labs Americas initiative.

=== Spreading Qt in the New World ===

* Author: Anselmo Lacerda Silveira de Melo - anselmo.melo AT openbossa DOT org
* Intended audience: Users / Application Developers
* Talk type: lightning talk
* Abstract/description

An introduction to Qt Labs Americas (http://qtlabs.openbossa.org), an initiative of openBossa stream of INdT aiming to spread Qt in the American continent, starting in Brazil. What have been done, what are the future plans and how the community can benefit from it.

* Author bio

GNU/Linux user since 2002, works with Linux on embedded devices since 2006. Works for INdT as a researcher at the openBossa open-source stream where develops rich UIs features for Qt and is also part of the Qt Labs Americas initiative. Whenever possible, he likes hunting bugs with the KDE Bugsquad.

=== Next generation layouts in Qt 4.6 ===

* Author: Caio Marcelo de Oliveira Filho - caio.oliveira AT openbossa.org
* Author: Eduardo M. Fleury - eduardo.fleury AT openbossa.org
* Intended audience: Users / Application Developers
* Talk type: presentation
* Abstract/description

With the release of N900, the first Maemo phone from Nokia, the
importance of developing rich UI applications is higher than ever.
As a consequence, new challenges are posed to both application
and framework developers.

One of these challenges is how to distribute items on the screen
in a flexible and dynamic way. This talk will present the next
generation layouts we have been developing, together with Qt
Development Frameworks, to fullfil such requirements

We will cover the new QGraphicsAnchorLayout, to be released in
Qt 4.6, including the use cases that drove us, its usage and
examples showing the benefits of such technology.

* Author bio

Caio Marcelo de Oliveira Filho graduated in computer engineering at
UNICAMP (in Brazil) and GNU/Linux user for more than a decade.
Contributed to the development of Canola2 and the Enlightenment
Foundation Libraries. Today works for Openbossa/INdT developing new
solutions for mobile applications using Qt framework and related
technologies.

Eduardo Fleury is Brazilian, graduated as Computer Engineer at Unicamp, in 2006. Since then has been working in Linux-related projects. Currently works at INdT (Nokia Institute of Technology) developing, among other projects, the Qt framework. Has been working on tools designed for the creation of rich interfaces, including AnchorLayout and animated Layouts.

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

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

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

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

=== N900 HW architecture overview & power management ===
*Author: Igor Stoppa - igor.stoppa@nokia.com
*Intended audience: application & platform developers
*Talk type: lightning talk
*Abstract/description:
overview of the system HW architecture, with focus on the OMAP processor and how to write power efficient code.
*Author bio:
Igor is project manager for the Core Team (kernel, X, production support, power management) and responsible for the overall use time; in the past he has been developing the power management solution for 770, n800 and n810.

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

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

=== Test framework tool for Maemo devices ===
*Author: Carlos Aguiar - carlos.aguiar@indt.org.br, Fabio Almeida - fabio.almeida@indt.org.br, Luiz Nagata - luiz.nagata@indt.org.br and Jyrki Sippola - jyrki.sippola@nokia.com
*Intended audience: users/platform developers
*Talk type: presentation/demo
*Abstract/description:
: Companies usually develop their own tools for test and monitoring consoles directly into their products but these applications tools, in general, do not go out of production place and are not deployed for platform developers and final consumers. These solutions are closed and just for company use. The open source community provides many tools to test different functionalities like keyboard, display, wi-fi and so on, but they do not work together as an integrated solution.
: The proposal is to integrate different functional tests into a test framework tool for Maemo devices. This framework will be able to communicate with different test applications, control them, gather information and report status results, helping developers and users to identify problems, perform reliability tests and gather statistics. Also, it will be possible to extend this framework to support new test types.
: For demo presentation purposes the framework will run the following functional tests: keyboard, camera, audio, display and wi-fi.
*Author bio:
: Carlos, Fábio and Luiz are software developers at Nokia Technology Institute (INdT) at Manaus/Brazil working with Linux, Maemo and device tests. Currently we are involved on project that aims to build software solutions to guarantee quality on devices. Jyrki is responsible for manufacturing test related research projects at Nokia.

OpenGL-ES

2009-03-26T13:14:15Z

192.100.116.143:

[[Category:Development]]
== OpenGL ES ==

Maemo OpenGL ES

=== Books about OpenGL ES ===

* [http://www.amazon.com/Mobile-3D-Graphics-Kaufmann-Computer/dp/0123737273/ref=sr_1_1?ie=UTF8&s=books&qid=1235944663&sr=8-1 Mobile 3D graphics with OpenGL ES and M3G]
* [http://www.amazon.com/OpenGL%20ES-2-0-Programming-Guide/dp/0321502795/ref=sr_1_1?ie=UTF8&s=books&qid=1235944783&sr=1-1 OpenGL ES 2.0 programming guide]

=== Other documentation ===

* [http://www.khronos.org/opengles/2_X/ Khronos OpenGL ES documentation and specifications]

=== Imagination Technologies SDK ===

* [http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp OpenGL ES SDK]

=== Other related documentation ===

* [http://blogs.forum.nokia.com//data/blogs/resources/300003/fremantle_bossa_2009.pdf Kate's presentation in Bossa 2009 conference] about Fremantle and section about OpenGL ES 2.0

=== OpenGL variants ===
[[image:Opengl.svg]]

* OpenGL 1.0 has fixed shaders and fixed function API to using them
* OpenGL 2.0 adds programmable shaders, but fixed function pipeline API is still there for backward compatibility
* OpenGL 3.1 removes support for old fixed function pipeline, so it is very similar to OpenGL ES 2.0

* OpenGL ES 1.0 is based on OpenGL 1.0 with extra redundant API's removed and fixed point (fractional integer) API added
* OpenGL ES 2.0 is based on OpenGL 2.0, so using programmable shaders is mandatory, since all old fixed function API's have been removed

=== Porting between OpenGL variants ===

* OpenGL 1.0 application works with OpenGL 2.0 but not vice versa
* OpenGL 1.0 application is possible to port to OpenGL ES 1.0, but needs work if it is using some of the removed API's
* OpenGL 2.0 application that only uses programmable shaders is possible to port OpenGL ES 2.0, but may still need some work
* Porting OpenGL 1.0 or OpenGL ES 1.0 applications to OpenGL ES 2.0 needs a rewrite to replace fixed function API usage with programmable shaders

What this means in paractice ?

Most of the desktop Linux OpenGL applications are written mostly using the OpenGL1.x style fixed pipeline API's including
extensive use of glBegin/glEnd and application level matrix transformation calls. OpenGL2.0 introduces programable shaders
that allows moving these tasks to Graphics processor ( GPU ) but does not force it. In OpenGL-ES2.0 the old fixed pipeline API's are removed and can't be used any more.
It is mandatory to use programable shaders and some code must be rewritten. The rewritten code can then also take advantage of
programable shaders in desktop OpenGL 2.x implementations. Other alternative with less rewriting is to use OpenGL-ES1.0 emulation
libraries in maemo. These libraries contain OpenGL-ES1.0 API and fixed OpenGL-ES1.0 emulating shader code.

=== Compiling under scratchbox ===

To compile OpenGL ES 2.0 applivations you need to have package "libgles2-dev" installed.
It is as standard, part of Fremantle aplha ARMEL but at the moment it is missing from x86 version.
We try to get x86 equivalent OpenGL ES2 emulation library available soon.

There is excellent way to familiarize yourself to OpenGL ES 2.0 by trying the
PoverVR tutorials that can be found form SDK under TrainingCouse directory.
The examples have their own Makefiles for Linux host but you can copy the files
to your own directory and try makefile below. Reason to use this own Makefile is
thet the makefiles coming with SDK compiles examples with x86 libraries part
of the SDK and not armel/x86 maemo libraries in scratchbox.

This Makefile at the moment supports the basic
and PvrShell examples (01..05) but not yet support PvrTools exaples ( 06 and above ).

To compile some of PoverVR tutorial examples, you can use following Makefile
<pre>
CC=g++

CPPFLAGS = -DBUILD_OGLES2
LDFLAGS=-lEGL -lX11 -lGLESv2

all:OGLES2Texturing OGLES2BasicTnL OGLES2IntroducingPVRTools OGLES2HelloTriangle_LinuxX11

OGLES2HelloTriangle_LinuxX11:OGLES2HelloTriangle_LinuxX11.o

OGLES2Texturing: PVRShellOS.o OGLES2Texturing.o PVRShell.o PVRShellAPI.o

OGLES2BasicTnL: PVRShellOS.o OGLES2BasicTnL.o PVRShell.o PVRShellAPI.o

OGLES2IntroducingPVRTools: PVRShellOS.o OGLES2IntroducingPVRTools.o PVRShell.o PVRShellAPI.o
</pre>

=== Using with QGLWidget ===

There is in Qt 4.5 ready made example hellogl_es2 that can be found from
examples/opengl/hellogl_es2 directory. There is also equivalent examples
for desktop opengl and opengl_es2 .

The example is also good showing what is different between OpenGL versions.
The hellogl uses plain desktop "glBegin / glEnd" functions with display lists. Hellogl_es2 uses vertex attribute pointers and shaders instead of glBegin/glEnd.
The helloes_gl2 is even more complicated because it uses programmable shaders
instead fixed pipeline in both of the previous exaples.

If you try compile yourself unmodified version of hellogl_es2 for maemo,
you need to add in void GLWidget::initializeGL ()

Line in beginning <pre>setlocale(LC_NUMERIC, "C"); // Reset locale for compilation</pre>
and after shaders has been compiled line <pre> setlocale(LC_ALL, ""); // restore locale</pre>
because locale affects in shader compilation even it should not do

OpenGL-ES

2009-03-26T13:12:27Z

192.100.116.143:

[[Category:Development]]
== OpenGL ES ==

Maemo OpenGL ES

=== Books about OpenGL ES ===

* [http://www.amazon.com/Mobile-3D-Graphics-Kaufmann-Computer/dp/0123737273/ref=sr_1_1?ie=UTF8&s=books&qid=1235944663&sr=8-1 Mobile 3D graphics with OpenGL ES and M3G]
* [http://www.amazon.com/OpenGL%20ES-2-0-Programming-Guide/dp/0321502795/ref=sr_1_1?ie=UTF8&s=books&qid=1235944783&sr=1-1 OpenGL ES 2.0 programming guide]

=== Other documentation ===

* [http://www.khronos.org/opengles/2_X/ Khronos OpenGL ES documentation and specifications]

=== Imagination Technologies SDK ===

* [http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp OpenGL ES SDK]

=== Other related documentation ===

* [http://blogs.forum.nokia.com//data/blogs/resources/300003/fremantle_bossa_2009.pdf Kate's presentation in Bossa 2009 conference] about Fremantle and section about OpenGL ES2.0

=== OpenGL variants ===
[[image:Opengl.svg]]

* OpenGL 1.0 has fixed shaders and fixed API to using them
* OpenGL 2.0 adds programable shaders but fixed pipeline api is still there for backward compatibility

* OpenGL ES 1.0 is based on OpenGL 1.0 with extra redundant API's removed and fixed point (fractional integer) API added
* OpenGL ES 2.0 is based on OpenGL 2.0, so using programmable shaders is mandatory, since all old fixed function API's have been removed

=== Porting between OpenGL variants ===

* OpenGL 1.0 application works with OpenGL 2.0 but not vice versa
* OpenGL 1.0 application is possible to port to OpenGL ES 1.0, but needs work if it is using some of the removed API's
* OpenGL 2.0 application that only uses programmable shaders is possible to port OpenGL ES 2.0, but may still need some work
* Porting OpenGL 1.0 or OpenGL ES 1.0 applications to OpenGL ES 2.0 needs a rewrite to replace fixed function API usage with programmable shaders

=== Compiling under scratchbox ===

To compile OpenGL ES 2.0 applivations you need to have package "libgles2-dev" installed.
It is as standard, part of Fremantle aplha ARMEL but at the moment it is missing from x86 version.
We try to get x86 equivalent OpenGL ES2 emulation library available soon.

There is excellent way to familiarize yourself to OpenGL ES 2.0 by trying the
PoverVR tutorials that can be found form SDK under TrainingCouse directory.
The examples have their own Makefiles for Linux host but you can copy the files
to your own directory and try makefile below. Reason to use this own Makefile is
thet the makefiles coming with SDK compiles examples with x86 libraries part
of the SDK and not armel/x86 maemo libraries in scratchbox.

This Makefile at the moment supports the basic
and PvrShell examples (01..05) but not yet support PvrTools exaples ( 06 and above ).

To compile some of PoverVR tutorial examples, you can use following Makefile
<pre>
CC=g++

CPPFLAGS = -DBUILD_OGLES2
LDFLAGS=-lEGL -lX11 -lGLESv2

all:OGLES2Texturing OGLES2BasicTnL OGLES2IntroducingPVRTools OGLES2HelloTriangle_LinuxX11

OGLES2HelloTriangle_LinuxX11:OGLES2HelloTriangle_LinuxX11.o

OGLES2Texturing: PVRShellOS.o OGLES2Texturing.o PVRShell.o PVRShellAPI.o

OGLES2BasicTnL: PVRShellOS.o OGLES2BasicTnL.o PVRShell.o PVRShellAPI.o

OGLES2IntroducingPVRTools: PVRShellOS.o OGLES2IntroducingPVRTools.o PVRShell.o PVRShellAPI.o
</pre>

=== Using with QGLWidget ===

There is in Qt 4.5 ready made example hellogl_es2 that can be found from
examples/opengl/hellogl_es2 directory. There is also equivalent examples
for desktop opengl and opengl_es2 .

The example is also good showing what is different between OpenGL versions.
The hellogl uses plain desktop "glBegin / glEnd" functions with display lists. Hellogl_es2 uses vertex attribute pointers and shaders instead of glBegin/glEnd.
The helloes_gl2 is even more complicated because it uses programmable shaders
instead fixed pipeline in both of the previous exaples.

If you try compile yourself unmodified version of hellogl_es2 for maemo,
you need to add in void GLWidget::initializeGL ()

Line in beginning <pre>setlocale(LC_NUMERIC, "C"); // Reset locale for compilation</pre>
and after shaders has been compiled line <pre> setlocale(LC_ALL, ""); // restore locale</pre>
because locale affects in shader compilation even it should not do

OpenGL-ES

2009-03-26T13:12:05Z

192.100.116.143:

[[Category:Development]]
== OpenGL ES ==

Maemo OpenGL ES

=== Books about OpenGL ES ===

* [http://www.amazon.com/Mobile-3D-Graphics-Kaufmann-Computer/dp/0123737273/ref=sr_1_1?ie=UTF8&s=books&qid=1235944663&sr=8-1 Mobile 3D graphics with OpenGL ES and M3G]
* [http://www.amazon.com/OpenGL ES-2-0-Programming-Guide/dp/0321502795/ref=sr_1_1?ie=UTF8&s=books&qid=1235944783&sr=1-1 OpenGL ES 2.0 programming guide]

=== Other documentation ===

* [http://www.khronos.org/opengles/2_X/ Khronos OpenGL ES documentation and specifications]

=== Imagination Technologies SDK ===

* [http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp OpenGL ES SDK]

=== Other related documentation ===

* [http://blogs.forum.nokia.com//data/blogs/resources/300003/fremantle_bossa_2009.pdf Kate's presentation in Bossa 2009 conference] about Fremantle and section about OpenGL ES2.0

=== OpenGL variants ===
[[image:Opengl.svg]]

* OpenGL 1.0 has fixed shaders and fixed API to using them
* OpenGL 2.0 adds programable shaders but fixed pipeline api is still there for backward compatibility

* OpenGL ES 1.0 is based on OpenGL 1.0 with extra redundant API's removed and fixed point (fractional integer) API added
* OpenGL ES 2.0 is based on OpenGL 2.0, so using programmable shaders is mandatory, since all old fixed function API's have been removed

=== Porting between OpenGL variants ===

* OpenGL 1.0 application works with OpenGL 2.0 but not vice versa
* OpenGL 1.0 application is possible to port to OpenGL ES 1.0, but needs work if it is using some of the removed API's
* OpenGL 2.0 application that only uses programmable shaders is possible to port OpenGL ES 2.0, but may still need some work
* Porting OpenGL 1.0 or OpenGL ES 1.0 applications to OpenGL ES 2.0 needs a rewrite to replace fixed function API usage with programmable shaders

=== Compiling under scratchbox ===

To compile OpenGL ES 2.0 applivations you need to have package "libgles2-dev" installed.
It is as standard, part of Fremantle aplha ARMEL but at the moment it is missing from x86 version.
We try to get x86 equivalent OpenGL ES2 emulation library available soon.

There is excellent way to familiarize yourself to OpenGL ES 2.0 by trying the
PoverVR tutorials that can be found form SDK under TrainingCouse directory.
The examples have their own Makefiles for Linux host but you can copy the files
to your own directory and try makefile below. Reason to use this own Makefile is
thet the makefiles coming with SDK compiles examples with x86 libraries part
of the SDK and not armel/x86 maemo libraries in scratchbox.

This Makefile at the moment supports the basic
and PvrShell examples (01..05) but not yet support PvrTools exaples ( 06 and above ).

To compile some of PoverVR tutorial examples, you can use following Makefile
<pre>
CC=g++

CPPFLAGS = -DBUILD_OGLES2
LDFLAGS=-lEGL -lX11 -lGLESv2

all:OGLES2Texturing OGLES2BasicTnL OGLES2IntroducingPVRTools OGLES2HelloTriangle_LinuxX11

OGLES2HelloTriangle_LinuxX11:OGLES2HelloTriangle_LinuxX11.o

OGLES2Texturing: PVRShellOS.o OGLES2Texturing.o PVRShell.o PVRShellAPI.o

OGLES2BasicTnL: PVRShellOS.o OGLES2BasicTnL.o PVRShell.o PVRShellAPI.o

OGLES2IntroducingPVRTools: PVRShellOS.o OGLES2IntroducingPVRTools.o PVRShell.o PVRShellAPI.o
</pre>

=== Using with QGLWidget ===

There is in Qt 4.5 ready made example hellogl_es2 that can be found from
examples/opengl/hellogl_es2 directory. There is also equivalent examples
for desktop opengl and opengl_es2 .

The example is also good showing what is different between OpenGL versions.
The hellogl uses plain desktop "glBegin / glEnd" functions with display lists. Hellogl_es2 uses vertex attribute pointers and shaders instead of glBegin/glEnd.
The helloes_gl2 is even more complicated because it uses programmable shaders
instead fixed pipeline in both of the previous exaples.

If you try compile yourself unmodified version of hellogl_es2 for maemo,
you need to add in void GLWidget::initializeGL ()

Line in beginning <pre>setlocale(LC_NUMERIC, "C"); // Reset locale for compilation</pre>
and after shaders has been compiled line <pre> setlocale(LC_ALL, ""); // restore locale</pre>
because locale affects in shader compilation even it should not do

OpenGL-ES

2009-03-26T13:11:11Z

192.100.116.143:

[[Category:Development]]
== OpenGL ES ==

Maemo OpenGL ES

=== Books about OpenGL ES ===

* [http://www.amazon.com/Mobile-3D-Graphics-Kaufmann-Computer/dp/0123737273/ref=sr_1_1?ie=UTF8&s=books&qid=1235944663&sr=8-1 Mobile 3D graphics with OpenGL ES and M3G"]
* [http://www.amazon.com/OpenGL ES-2-0-Programming-Guide/dp/0321502795/ref=sr_1_1?ie=UTF8&s=books&qid=1235944783&sr=1-1 OpenGL ES 2.0 programming guide]

=== Other documentation ===

* [http://www.khronos.org/opengles/2_X/ Khronos OpenGL ES documentation and specifications]

=== Imagination Technologies SDK ===

* [http://www.imgtec.com/powervr/insider/sdk/KhronosOpenGLES2xSGX.asp OpenGL ES SDK]

=== Other related documentation ===

* [http://blogs.forum.nokia.com//data/blogs/resources/300003/fremantle_bossa_2009.pdf Kate's presentaion in Bossa 2009 conference] about Fremantle and section about OpenGL ES2.0

=== OpenGL variants ===
[[image:Opengl.svg]]

* OpenGL 1.0 has fixed shaders and fixed API to using them
* OpenGL 2.0 adds programable shaders but fixed pipeline api is still there for backward compatibility

* OpenGL ES 1.0 is based on OpenGL 1.0 with extra redundant API's removed and fixed point (fractional integer) API added
* OpenGL ES 2.0 is based on OpenGL 2.0, so using programmable shaders is mandatory, since all old fixed function API's have been removed

=== Porting between OpenGL variants ===

* OpenGL 1.0 application works with OpenGL 2.0 but not vice versa
* OpenGL 1.0 application is possible to port to OpenGL ES 1.0, but needs work if it is using some of the removed API's
* OpenGL 2.0 application that only uses programmable shaders is possible to port OpenGL ES 2.0, but may still need some work
* Porting OpenGL 1.0 or OpenGL ES 1.0 applications to OpenGL ES 2.0 needs a rewrite to replace fixed function API usage with programmable shaders

=== Compiling under scratchbox ===

To compile OpenGL ES 2.0 applivations you need to have package "libgles2-dev" installed.
It is as standard, part of Fremantle aplha ARMEL but at the moment it is missing from x86 version.
We try to get x86 equivalent OpenGL ES2 emulation library available soon.

There is excellent way to familiarize yourself to OpenGL ES 2.0 by trying the
PoverVR tutorials that can be found form SDK under TrainingCouse directory.
The examples have their own Makefiles for Linux host but you can copy the files
to your own directory and try makefile below. Reason to use this own Makefile is
thet the makefiles coming with SDK compiles examples with x86 libraries part
of the SDK and not armel/x86 maemo libraries in scratchbox.

This Makefile at the moment supports the basic
and PvrShell examples (01..05) but not yet support PvrTools exaples ( 06 and above ).

To compile some of PoverVR tutorial examples, you can use following Makefile
<pre>
CC=g++

CPPFLAGS = -DBUILD_OGLES2
LDFLAGS=-lEGL -lX11 -lGLESv2

all:OGLES2Texturing OGLES2BasicTnL OGLES2IntroducingPVRTools OGLES2HelloTriangle_LinuxX11

OGLES2HelloTriangle_LinuxX11:OGLES2HelloTriangle_LinuxX11.o

OGLES2Texturing: PVRShellOS.o OGLES2Texturing.o PVRShell.o PVRShellAPI.o

OGLES2BasicTnL: PVRShellOS.o OGLES2BasicTnL.o PVRShell.o PVRShellAPI.o

OGLES2IntroducingPVRTools: PVRShellOS.o OGLES2IntroducingPVRTools.o PVRShell.o PVRShellAPI.o
</pre>

=== Using with QGLWidget ===

There is in Qt 4.5 ready made example hellogl_es2 that can be found from
examples/opengl/hellogl_es2 directory. There is also equivalent examples
for desktop opengl and opengl_es2 .

The example is also good showing what is different between OpenGL versions.
The hellogl uses plain desktop "glBegin / glEnd" functions with display lists. Hellogl_es2 uses vertex attribute pointers and shaders instead of glBegin/glEnd.
The helloes_gl2 is even more complicated because it uses programmable shaders
instead fixed pipeline in both of the previous exaples.

If you try compile yourself unmodified version of hellogl_es2 for maemo,
you need to add in void GLWidget::initializeGL ()

Line in beginning <pre>setlocale(LC_NUMERIC, "C"); // Reset locale for compilation</pre>
and after shaders has been compiled line <pre> setlocale(LC_ALL, ""); // restore locale</pre>
because locale affects in shader compilation even it should not do