Marcin Juszkiewicz

After 4 weeks from ordering Nokia N900 device arrived at my place. Now I have one week to check is everything working and if not then request RMA from Nokia.

First feelings? Heavy and bulky. It is bigger then each of phones which I owned and feels bigger then N810 tablet (due to thickness).

OMAP3 processor which is in N900 has lot of power and it is nicely used — transitions are nice, normal DivX movies plays without problems. No lag noticed so far.

But how about software? This is other thing ;( Some things are just like they were in Maemo — more or less broken by design, some are missing, some things which were in previous releases are missing etc. For example application manager still does not allow to install more then one application at once and still does not scroll on keypress or limit entries on typing (which Contacts do).

Contacts application integrates also Instant Messaging. It looks like someone read my previous post about defining good contacts application — you have people and can add Jabber/Skype/ICQ/MSN/SIP/etc protocols to each of them. Looks really nice. But lacks any way to automatize merging of entries from different accounts so it took me a while to get most of them merged ;(

Email application is a disaster. It looks like it does not cache any data so going into my inbox (with just 550 mails) require half minute to get it refreshed — Profimail on my E66 phone handle it much much better. And I still did not found a way to go into inbox->mailinglists->development->oe folder which currently has ~14000 (yes, fourteen thousands) emails. According to talk on #maemo channel Maemo5 email client do not have an option to subscribe IMAP folders yet.

Software launcher is changed — no longer editable menu with categories but just set of icons sorted randomly(?).

Good thing is that PIM data got fetched from my Nokia E66 without any problems — I just had to pair them and everything got synced. Bad thing is that so far there is no way to sync with SyncML servers like ScheduleWorld ;(

I hope that some of problems will disappear after some use and/or in next software releases.

And one more thing — this is first Maemo device which has Polish language support out-of-box!

When I was choosing my current phone (Nokia E66) one of things which I wanted was ability to make video calls. I did not know what for I will use them but why not having them? Especially when they are treated as normal calls by my GSM operator (except roaming).

Some time ago I discovered why video calls are good to have. I have small daughter (~20 months now). When my wife has to travel somewhere (or I have to) we use video calls to wave her on good morning or before going sleep etc. Mira’s reaction is always positive and we usually have to be careful as she wants to keep phone and look at caller’s face.

And so far Nokia failed to implement video calls on N900 device :( So people — fix it or my daughter will force me to take my phone as a backup :D

It was over eight years ago when I wrote application last time. Since then I had my hands in countless programs, libraries etc. but never wrote something new from scratch. Until recently…

Some time ago Mickey Lauer presented his module player for iPhone. I like the idea and started thinking about creating such one for my devices. After some discussions about Modland music collection with him I started coding.

To make things as simple as possible I used Qt framework with Phonon for playing (GStreamer modplug plugin underneath). Current version maybe is not so beauty but it is usable and works fine. Application will be GPL — I used code from Qt demos, read random snippets of code from other programs etc.

Things already implemented:

• playing local modules
• fetching modules from modland archive
• author/song selection
• playing next song on song end (with looping on author)
• seeking
• volume change (will probably get removed from UI)

Things to do:

• error handling (especially fetching related)
• download progressbar
• playing counters
• favorites
• playlists
• small screen usability (stacked windows/tabs)
• and others…

For readers: what is a real name of Lord Performer? :D

Some time ago Nokia offered discounts for their newest tablet: N900 for about two hundred people which were active in Maemo community. For European ones the price is more or less 250€ which looks nice compared to original price which is ~600€.

But there is one nasty part in it — devices have just one week of warranty. What can be checked during that time? Dead pixels?

Situation got more strange when I looked at Maemo forum where people lists misc discounts which they found on the Internet… For example Dell had one for $442 which makes it just a bit more expensive then DDP ones but gives you normal warranty.

This is weird — developers and active people from community gets worse offer then normal users. And additionally all DDP orders are marked as “Critical” which probably is other way of saying “ignore as long as possible” because tomorrow there will be two weeks since I ordered N900 in DDP and all I got was locking of 250€ on my credit card and nothing more.

Previous developer programs were better at handling users (at least that is what I hear from people which were part of it).

During use of OpenEmbedded and Poky build systems I learnt few tricks which I want to start sharing.

Installing l10n packages for all software in resulting rootfs

This one is rarely used — I know one company which makes use of it. How does it works? It is called after root filesystem is populated with packages and goes one by one and install “-locale-LANG” for each required language. As you may expect it makes whole process much, much longer. Activation is easy:

ROOTFS_POSTINSTALL_COMMAND += "install_all_locales; "

Code is available only for building from IPKG packages and is stored in rootfs_ipk.bbclass file. So far that code is present only in Poky Linux.

Building AUTOREV packages over slow link

How many times you had a situation when you did a build and many components used SRCREV="${AUTOREV}" setting? Parsing can take eons then…

But there is a solution. It will cache values of all SRCREV variables so just one parse will be long — next one use cached values. Of course you lose automatic revisions but instead you have fast parsing time which is blessing when most of your work is fixing build problems. Activation is easy:

BB_SRCREV_POLICY = "cache"

Save disc space by not generating GIT tarballs in DL_DIR

How many of you readers share your DL_DIR (directory where OE stores all fetched sources) with others? For those who answered “not me” there is a way to gain some space by not generating tarballs with GIT repositories.

By default BitBake clones GIT tree and checkouts it. Then 2 archives are generated: one with just “.git” directory and second with sources — the one which is used in do_unpack task. So why waste space for storing first one? We have it somewhere in DL_DIR/git/ for next time… Activation is easy:

BB_GENERATE_MIRROR_TARBALLS = "0"

More tricks in next posts.

My Symbian based Nokia E66 phone has Ovi Maps installed so one day I decided to make use of routing function in it when I was driving to the town (on a road where I did not needed to be guided). BT headset on ear, paired with phone and let’s drive.

At start road was selected quite properly, the problems started later. Many times it was recalculating route (the funniest was when I stopped at traffic lights it recalculated route and then made it again after driving for 5 meters). Directions changes information were also distracting: “on 200m go left” then “go right” when I reached point. Or “go left,right” when it was straight road or when I had to turn right at crossing.

I have to admit that after two tries I totally gave up on driving with it and switched back to TomTom device. But there is one good thing in Ovi Maps — it works quite good for walk navigation. I used it in many cities abroad and it handled. I hope that Maemo5 version will work at least that good as Symbian one.

Today I found some time and played with Maemo 5 SDK. As I am one of those who do not like Scratchbox I used official image for VirtualBox. After boot I landed in GNOME session of Ubuntu 8.10 and after few moments I got Maemo 5 started thanks to instructions from forum.

Ok, so let’s test it. As official release notes mentioned Polish translation I switched to it. What I saw was disaster… And the problem is that latest firmware has same version available. Examples:

Note: I did system update by using “apt-get update;apt-get upgrade” followed by “fakeroot dpkg --configure -a” (because sbox root ‘emulation’ was too weak for “libosso-abook”). As a result translation “6.0+r7250+0m5” were installed (“calendar-l10n-plpl” package). Scary, isn’t it?

Next thing which I looked at was instant messaging — which I was not able to use since there was no Jabber support. It has ICQ, Gadu-Gadu, MSN, Sametime, Salut, QQ, Groupwise, Google Talk, AIM, Yahoo but no Jabber. I even installed “telepathy-extras” but that added me yet another MSN and still no Jabber… Probably other package needs to be installed but why it has to be? OK, maybe SDK image does not contain same packages as device one but why it supports such poor thing like Gadu-Gadu out-of-box?

Contacts app is improved when compared to Maemo4 one — finally something closer to application which I described some time ago in other post. Has some bugs (I can not enter “+48123456789” as number because only digits are available (and ‘p’ for internal numbers).

Looks like there will be a long list of things to report as bugs when/if I will get my N900 (so far it is somewhere in deep nowhere). Why not reporting them now? Simple — I want to be able to check them on device itself.

Other things I will check next time. Now it is time to sleep.

Today I got nice package in post office — Simplemachines One developer board (Sim.One in short). It is based on Cirrus Logic EP9307 processor with Maverick Crunch floating point unit. I got board with #0006 serial number.

Board is much better then EDB9301 which I used so far for EP93xx toolchain tests. What is on board:

• EP9307 CPU
• 64MB ram
• 8MB NOR flash
• MMC slot (connected over SPI so ~250KB/s max)
• 2 USB host ports
• VGA out port — XGA 8bit or SVGA 8/16/24bit
• serial port in RJ-45 instead of standard DB9 (but cable is in package)
• audio in/out jacks
• many connectors with different signals — will have to check schematics for that.

By default board boots into Debian ‘lenny’ system stored on 4GB SDHC card. But there are problems with it as this is MMC over SPI so speed is very limited (about 250KB/s only) and it time outs quite often so I plan to move to USB stick during next days.

Next step will be adding it into OpenEmbedded and running Ångström as base distribution.

BTW — how did I got it at all? That’s due my recent work on merging EP93xx support into OE — I was asked do I want developer board with this processor.