Andrea Grandi

Introduction

My name's Andrea Grandi, I'm italian and I'm a Maemo user/lover/contributor since the Nokia 770. I love Python as development language and few months ago I also gave some contributions to the PyMaemo project.

In these days I had the idea to start writing a Twitter client for Maemo with a precise direction in my mind. I'll try to explain all my reasons here. First of all I've to thank the author of Mauku client. I use it since its first version and I'm quite happy with it. Then, why do I want to write another one?

1. Maemo (MeeGo) is moving to Qt and for this reason I'm going to use Qt, while Mauku uses Gtk.
2. I'm learning Qt and what is better than writing a complete (but not too complex) application to learn better?
3. Mauku is not free as lot of people could think. Reading the source codeyou find this "You are NOT allowed to modify or redistribute the source code.", while I want to write a client and release it under GPL2 or GPL3 license.
4. Mauku is not updated since some months and we have no news about it.
5. I love Python and I like to write free software in this language.
6. I want to give to Maemo a stronger contribute.

My request for help

Before lot of people start writing their own client resulting in 4-5 twitter clients for Maemo, why don't we join our strength and work to a common project? I'm not a Python expert nor a Qt one, but I've some experience as project/team leader and since this is not a complex project, I would be glad to lead it. So, I'm looking for Python developers, Qt developers, UI designers and whoever want to contribute to this project. I still have to find a good name and logo for this application.

Who want to help me?

Few days ago I published some notes about my personal experience with PR 1.1.1 firmware upgrade in Nokia N900. In particular my device got an infinite reboot loop after upgrading the firmware and I had to flash the firmware image from scratch to fix the problem. Today I was kindly contacted by Max Waterman (I suppose he works for Nokia) and he explained me what was the problem. It was caused by a little bug in Harmattan UI demo and they fixed it (the fix is already available in extras-devel).

No surprise for me: extras-devel contains unstable packages and if user enables it, he does at his own risk. The most important thing is the fact that the official firmware without any unstable application doesn't suffer of this problem at all. The thing that really impressed me so much (in a positive sense) it's that I was contacted privately by a Nokia developer apologizing for the bug (no problem man, it's part of the game if someone want to test extras-devel software) and explaining that they already fixed it.

This is what I like of Maemo (or should I already call it MeeGo?), I really feel to be a part of it!

I don't know if it's just a case or if I'm the only one who had these problems, but I'll report them anyway, maybe somebody had my same problem and we could try to prepare a proper bug report to make the Maemo team fix them.

Infinite boot loop after upgrade

First of all I have to say that before upgrading to PR 1.1.1 I checked if I had enough space on the rootfs. I only had 27 Mb and so I decided to remove some unused applications, deleted some *.deb in /var/cache/apt/archives and disabled extras repositories. Of course I also did a backup of all my configuration. After the cleaning operation I had near 60 Mb free on rootfs, enough to install the upgrade.

I closed all running applications, started the application manager and began the upgrade. After the upgrade was completed, the device did a reboot... then another one, then again, again.... until I had to remove the battery to stop it.

Conclusion: I had to re-flash the device with the latest image to make it work again.

mafw-dbus-wrapper taking all the CPU

I was watching a video (using subtitles) and after some minutes the whole UI became unresponsive. Strange because I already did this before without having any problem. I tried to check the problem using "top" utility from terminal and I saw that there was a mafw process (mafw-dbus-wrapper) that was taking 80-90% of CPU. My fault is that normally there are at least 3-4 , mafw-dbus-wrapper processes and I didn't check which one was causing the problem. Anyway I made a screenshot, just in case it can help.

I hope this short report can be useful to help Maemo team to fix or at least investigate what happened. Just leave a comment or contact me if you need more informations.

Nokia has published a demo application for N900, available in extras-devel repository, that shows a preview of Maemo 6 (Harmattan) user interface. Here there are some screenshots of the demo:

Demo application main window

Question dialog

Text entry dialog

Progress indicator

Information banner

Event banner

You can find more pictures in my Flickr album. Please note that installing this demo will also install Qt 4.6.2 on the N900 and about 52 Mb are required.

Introduction

As many of you already know, Fon is a spanish company that some years ago had the interesting idea of creating a wifi community to share the Internet connection. The idea is quite simple: each "fonero" buy a Fonera (the router sold by Fon), register it on the Fon system and get a username/password. If the fonero travels around the world he's able to connect to wifi signal of other foneras and browse the web for free.

When I bought my first fonera few years ago, I was one of the first people in my city. I bought it because I was really beliving in this project. During these years Fon produced new models of fonera and I bought each of them (the WRT54 router, Fonera, Fonera+, Fonera 2.0g, Fonera 2.0n ecc....). Since first year, the Fon community has grown a lot and now there are a lot of foneros around the world.

Actual situation

Few months ago Fon launched a very interesting product: Fonera 2.0g. Thats's not only a router. Fonera 2 is capable of managing torrents, rapidshare downloads, uploading photo on Facebook and Flickr, and much more. Whats's wrong with this product? It's very unstable! There are a lot of users that bought this router when it was anounced and they're still waiting for a lot of bugs to be fixed by Fon developers team (composed by only ONE person!). Why users had to wait so long?

Simple! They were working to Fonera 2.0n! Wow! Faster router, more RAM, 4 ethernet port, wonderful! But... another very unstable router! And with unstable I mean: it disconnects/reboots often, connection is unstable, applications don't work ecc.... I'm talking about a 79€ router, not about something that users had as preview product. Me and other users were still waiting for an uograde when... Fon announced a new product! Yes, another one!

Fon priority is not to fix a product that thousand of users have already bought. Fon priority is to produce and sell a new product!

Conclusion

It could be only my opinion, but I don't trust you anymore Fon! I'm really disappointed about your behaviour you had with your customers. I've already spent (wasted) a lot of money with your not-working products and I'm not going to buy your products anymore! I'm tired of being illuded by your promises: how long are you going to play tricks on users?

Being one of the developers who received the discount to buy a N900, during these days I contacted the DDP customer care to have more informations and details. I'll publish here both my original question and the official reply.

1) The price of N900 is 250€ and I've read of people who paid it this price. Anyway here you say that the VAT is not included:
https://pro.forum.nokia.com/site/global/tech_resources/discounted_devices/l_ddp.jsp
so it should costs 300€ not 250€, right?

The VAT applies only for Finnish developers, for the others the price is the price they see in the eStore, no VAT is added to that.

So, all non-finnish european people, will pay 250€ for the N900.

2) How much time can I wait before ordering it? In this moment I'm in Valencia (Spain) and I won't come back to Italy before Christmas. I'd like the order to be shipped to my home in Italy (I registered as italian user and I want italian keyboard layout), but I'd like to wait to order it, because since there's no warranty and I need to tell you about any problem within a week, if I order it now I will be able to check it only at the end of december when I'll come back to Italy.

I guess this should not be a problem.

This part is not confirmed yet, since Quim told us to hurry up to buy it.

3) How many devices can I buy at that price? Here you say I can buy two:
https://pro.forum.nokia.com/site/global/tech_resources/discounted_devices/l_ddp.jsp
but here you say I can buy one: https://pro.forum.nokia.com/showProduct.do?product_id=5096

I don't want two devices, but another friend of mine, who help me in a project for the Maemo Community, would like to be able to buy one for the same price (he wasn't able to get the discount because his karma is still low).

As far as I know, you can only purchase 1x device per person, regarding MAEMO N900.

4) Where can we find the new firmware? In the FAQ you say: DDP does not flash devices. It's ok, I can do it, but there's no public firmware for N900 at the moment.

To update N900, can possibly be using NSU. Nokia software updater.

5) Is it possible to have a device with localized keyboard (for example italian one) ?

All N900 will have EURO variant, Italian language is one option.

Note: even these replies come from the official customer care, I don't assume any responsability if they shouldn't be all exact. If you have any doubt, please contact them directly at DDP.program@nokia.com

Quim Gil just confirmed the UX hackfest in Barcelona for 4, 5, 6 december: http://talk.maemo.org/showthread.php?t=33719

What is UX hackfest?
It's a three days meeting for Maemo developers, UX experts and people who want to learn about designing good user interfaces.

When?
On 4, 5, 6 december 2009

Where?
Barcelona, Spain. The exact location has still to be confirmed, but it should be http://citilab.eu

How many people invited?
About 50 people invited (Maemo developers, UX experts, ecc....)

If you are a Maemo developer and you have good user interface designer skills, this is the place for you.

If you are a Maemo developer and you are not a UX expert, this IS anyway the place for you: you'll have the possibility to talk with experts and improve your knowledge about UI design.

Anyone interested, please join the discussion here: http://talk.maemo.org/showthread.php?t=33719

Update 3/11/2009 - 16:00: a wiki page with all information has been created here: http://wiki.maemo.org/Maemo-Barcelona_Long_Weekend
please add your name/data to the page if you requested to join the UX hackfest.

During next Maemo Summit we will have at least 2 hours (one on saturday and another one on sunday) of lightning talks, about 20 talks where people will try to explain or present something in just 5 minutes.

Last year, during Maemo Summit 2008, I did a lightning talk too and I must admit: even if I knew a lot about the subject of my talk and even if I had already done many other talks, I think it wasn't so good as I expected.

This year I've been selected again (more details will follow) to give a 5 minutes talk and with this great news the kind Dave Neary also suggested me a link with an article about some best practices when giving lightning talks. I'll try to resume the most important points, hoping this will be useful for people who is going to give a short presentation at Summit.

Go straight to the point: five minutes finish sooner than you can expect. You have to talk about the main topic of your talk within the two first minutes, else you risk to talk too much about the rest and you couldn't have the time for the most important thing.

Leave details away: people will never remember too many details explained in so little time. It's better to leave them away and put them in a more detailed blog post that you can link within your slides.

Slides: for a five minute talk you can avoid preparing slides, but if this can help you to concentrate on points you have to talk about, please prepare them. Two or three slides can be useful to introduce yourself, to write any reference of what you're talking about many other things. Another important thing, make sure your slides are ready before starting your presentation: people don't want to wait 20-30 seconds it takes to start Open Office or any other similar application.

Consider any eventuality: the presentation file could be damaged (be sure to have a copy of it, better in PDF format), your laptop could have no more battery (make sure you've a copy of your slides in a USB key), aliens could take you away, ecc... (ok, this last eventuality is remote).

Concluding your talk: don't worry if you finish one or two minutes before, people won't bother about it. It's better to finish one minute before than 30 seconds later. If you want to leave an URL where people can find more details, how to contact you, put it in every slide so people will be able to take note of it from the first minute.

I hope to have resumed the most important points of the original article. If you think there are any other important things to say, please leave me a comment and I'll add them. I really hope you will enjoy Maemo Summit and its lightning talks!

In the last post of this series, we saw how to write a simple binding and we finished to build and install it manually. This is of course not a good way to manage the building/installation procedure.

In Python we can use a library called distutils that let us to automatize the building and installing process. I'll use the foo source code to create the package, so it will be easier to understand.

Using distutils

All we have to do is to write a setup.py file similar to this one:

from distutils.core import setup, Extension

foomodule = Extension('foo', sources = ['foo.c'])

setup (name = 'Foo',
       version = '1.0',
       description = 'This is a package for Foo',
       ext_modules = [foomodule])

As you can see, we have to first import needed modules with: from distutils.core import setup, Extension
then we create an entry for each module we have (in this case just one, "foomodule"). We then call the setup() method passing it all the parameters and our setup.py is complete.

Building and installing

To test it we can try to build the package in this way:

python2.5 setup.py build

if we want to install the module in our system:

python2.5 setup.py install

References

• Official Python documentation: http://docs.python.org/extending/building.html

The PyMaemo team is pleased to announce the second beta release of PyMaemo for Fremantle!

This new release is available through the extras-devel repository, see installation instructions in
http://pymaemo.garage.maemo.org/sdk_installation.html#fremantle

What is it?

Python for Maemo (PyMaemo for short) main objective is to make possible to use Python programming language as the scripting and development language for Maemo Platform, providing a better alternative for fast prototyping and programming in Maemo environment besides the C programming language.

Python is for serious programming and to have fun. Python has a nice syntax, it is easy to learn and powerful enough for a vast range of applications, this is why we choose Python for Maemo.

What has changed?

New packages:

• python-mafw (0.1-1maemo1)
  • Python bindings for the Media Application Framework [1]
  • Supported API is very basic at the moment, and there are some bugs. Feedback is welcome!
• python-hildondesktop (0.0.3-1maemo1)
  • Python bindings for the home/status widgets API
• python-notify (0.1.1-2maemo1)
  • Python bindings for libnotify
• pyclutter (0.8.0-1maemo2)
  • Python bindings for the Clutter API [2]
  • Experimental package, waiting for developer feedback

Updated packages:

• gnome-python (2.26.1-1maemo1)
  • major upgrade, matching current Debian testing release;
  • feedback on this is welcome, as it replaces a fairly old version (2.18).
• pygtk (2.12.1-6maemo7)
  • Enable glade support.
• python2.5 (2.5.4-1maemo1)
  • Updated to latest upstream 2.5.x release.
  • add support to --install-layout=deb flag.
• python-central (0.6.11.1maemo1)
  • dependency needed by the new python-setuptools version.
• python-defaults (2.5.2-3maemo3)
  • Change PREVVER in debian/rules, avoiding old python2.5-minimal versions that had "/usr/bin/python" and thus conflicts with python-minimal.
• python-hildon (0.9.0-1maemo10)
  • lots of bug fixes
• python-setuptools (0.6c9-1maemo1)
  • add support to --install-layout=deb flag.

Bugs fixed: MB#4530 [3], MB#4450 [4], MB#4629 [5], MB#4628 [6],
MB#4647 [7], MB#4632 [8],  MB#4646 [9],  MB#4750 [10],  MB#4749 [11],
MB#4791 [12]

Known issues

MB#4782 [13]: osso.Context causes segmentation fault
MB#4821 [14]: Cannot create HildonTouchSelector with single text column
MB#4824 [15]: python-mafw: source_browsing.py example does not work
MB#4839 [16]: python-mafw: mafw.Registry lacks list_plugins() method
MB#4849 [17]: python-mafw: MafwPluginDescriptorPublic structure is missing

We will not migrate to python2.6 in fremantle due to a (unresolved) bug (MB#4734 [18]), where a core SDK package explicitly conflicts with python >= 2.6, preventing any further upgrades from the 2.5.x series.

This release is supposed to be compatible with previous releases. If you have any issues regarding building your Python application on Fremantle, feel free to report it on the pymaemo-developers mailing list [19].

Acknowledgments

Thanks to everybody who helped making this release possible.

Bug reports, as always, should go to our Bugzilla [20]. Use the pymaemo-developers mailing list for help, feedback or suggestions.

References

[1] https://garage.maemo.org/projects/mafw/
[2] http://www.clutter-project.org/
[3] https://bugs.maemo.org/show_bug.cgi?id=4530
[4] https://bugs.maemo.org/show_bug.cgi?id=4450
[5] https://bugs.maemo.org/show_bug.cgi?id=4629
[6] https://bugs.maemo.org/show_bug.cgi?id=4628
[7] https://bugs.maemo.org/show_bug.cgi?id=4647
[8] https://bugs.maemo.org/show_bug.cgi?id=4632
[9] https://bugs.maemo.org/show_bug.cgi?id=4646
[10] https://bugs.maemo.org/show_bug.cgi?id=4750
[11] https://bugs.maemo.org/show_bug.cgi?id=4749
[12] https://bugs.maemo.org/show_bug.cgi?id=4791
[13] https://bugs.maemo.org/show_bug.cgi?id=4782
[14] https://bugs.maemo.org/show_bug.cgi?id=4821
[15] https://bugs.maemo.org/show_bug.cgi?id=4824
[16] https://bugs.maemo.org/show_bug.cgi?id=4839
[17] https://bugs.maemo.org/show_bug.cgi?id=4849
[18] https://bugs.maemo.org/show_bug.cgi?id=4734
[19] https://garage.maemo.org/mailman/listinfo/pymaemo-developers
[20] https://bugs.maemo.org/enter_bug.cgi?product=PyMaemo

Credits

This post was possible thanks to Anderson Lizardo, from PyMaemo team, who posted these informations on pymaemo-developers mailing list.