Qt / MeeGo Mobile Apps Development

Rich J2ME Mobile Applications using LWUIT for Nokia Symbian S40

2012-03-01T08:12:00.001-08:00

LWUIT is a Java UI framework for mobile devices aka Java ME.

While most mobile developers nowadays will think of smartphones, the lower end market is actually very huge. In fact Nokia has sold 1.5 billion Symbian S40 phones.

J2ME applications not only run in Nokia Symbian phones but also BlackBerry OS phones, low-end Chinese phones, entry level Samsung and Sony Ericsson phones, etc.

Developing with plain J2ME is painful. However LWUIT is a UI framework to the rescue.

With LWUIT you can develop beautiful visual user interfaces that support touch and modern controls. Of course within the limits of the devices, but it's much easier than coding plain MIDlets. it's also portable, you can develop from single source for Symbian S40 phones and BlackBerry phones.

Here is sample screenshots from a sample J2ME LWUIT app I made for DietYuk, an Indonesian healthy living site.

See the full gallery on Posterous

How to Uninstall Nokia Connectivity Framework (NCF?) - Cannot Install Nokia SDK 1.0 for Java

2011-09-02T01:21:00.001-07:00

My first attempt at installing Nokia SDK 1.0 for Java failed due to Avira AntiVir detected a malware on it, so I had to "ignore" the Malware and cancel the installation (which it seemed to not undoing it properly) and restart installation.

However the next installation failed while giving the following message:

Nokia Connectivity Framework(NCF) is already installed. Please uninstall NCF and press 'Ok' to proceed with installation.

At this point I am stuck. I've deleted the C:\Nokia\Tools folder entirely, and I can't find the "Nokia Connectivity Framework (NCF)" entry on "Add Remove Programs. There's not even a Cancel button (to close the installer) or Override button on this dialog box. Quite annoying. :-(

If you have a solution for this problem, please help.

How to Setup Qt Quick 4.7.3 / QML Project with Microsoft Visual Studio C++ 2008 Express

2011-08-06T18:58:00.001-07:00

It's possible to configure Qt Quick 4.7.3 / QML Development using Microsoft Visual Studio C++ 2008 Express project.

Quick Start

Install Microsoft Visual Studio C++ 2008 (Express)
Install Qt Library 4.7.x for Visual C++ 2008
Set environment QTDIR to C:\Qt\4.7.x

How to Create A New Qt Project in Visual Studio 2008

Create a new Makefile project
For Debug, set the build command as: qmake && nmake
Set the Debug launch command as: debug\YourApp.exe
For Release, set the build command as: qmake && nmake release-all
Set the Release launch command as: release\YourApp.exe
Add a YourApp.cpp file
Create initial Qt .pro project file by running: qmake -project

You should get this:

TEMPLATE = app
TARGET =
DEPENDPATH += .
INCLUDEPATH += .

# Input
SOURCES += YourApp.cpp

You need to update this .pro Qt project file when you add source or header files.

A simple YourApp.cpp would be:

#include <QApplication>
#include <QPushButton>

int main(int argc, char *argv[])
{
    QApplication app(argc, argv);
    QPushButton hello("Hello world");
    hello.resize(100, 30);

hello.show();
return app.exec();
}

You can see how this simple Qt GUI application looks on the screenshot.

How to Add Qt Quick / QML Support

To support QML / Qt Quick, add to .pro file:

QT += gui declarative

Create the .qml file :

import QtQuick 1.0

Rectangle { width: 100; height: 100; color: "red" }

Then load the .qml file from the main .cpp :

#include <QApplication>
#include <QPushButton>
#include <QDeclarativeView>

int main(int argc, char *argv[])
{
QApplication app(argc, argv);

    QDeclarativeView view;
    view.setSource(QUrl::fromLocalFile("qmlvs.qml"));
    view.show();

return app.exec();
}

You can see how this QML / Qt Quick application looks on the screenshot.

What about Visual Studio 2010?

It's possible but you'll have to download Qt sources and
build using Visual Studio compiler which can take 3 hours or more.

Download / Clone Sample Projects from Git Repository

To make it easy for you, the sample projects are freely available as Apache Licensed open source projects in my Nokia Developer Projects Git repository:

https://projects.developer.nokia.com/qmlexperiments

Learning Resources

To get started on Qt GUI / Qt Quick Development on desktop and mobile devices, check out these recommended books:

See the full gallery on Posterous

NewsPopper - Read your favorite news sites and share them! [Early prototypes & sketches]

2011-06-21T23:16:00.001-07:00

With NewsPopper, you can get the latest news easily from favorite sites that interests you, and share among your friends.
Set up alerts so NewsPopper --as it name says-- will "pop" the news for you on your mobile device!
You can get notified when your friend comments on the news they read, or liked.

Sounds interesting ? It should :-)

It's a mobile application I'm currently working on. The app uses the latest powerful Qt 1.1 SDK and will run on all mobile devices that support Qt framework (which means modern Symbian S60, Symbian^3, Maemo/N900, and MeeGo devices like the upcoming Nokia N9/N950).

It will support touch and swipe gestures (on all touch devices and especially on the Nokia N9) and should be very user friendly from the first start.

The images shown are some sketches and how the current prototype looks.

When it's finished (hopefully!) you'll find it in an Ovi Store near you. :-)

I highly recommend you to get these resources to gain skills on Qt Development on desktop and mobile devices :

See the full gallery on Posterous

(Nokia) Qt SDK 1.1 including Qt Framework 4.7.3 Libraries Released

2011-05-04T06:18:00.001-07:00

The Qt team is truly pleased to release the Qt SDK 1.1 for desktop and mobile development.

Using the Qt SDK you benefit from the Qt Creator IDE as a starting point for your development and you can also speed up your development - especially for touch-screens - with Qt Quick. During installation of the Qt SDK, you select the packages you need. In addition you will receive notification when new features and quality updates are available i.e. Qt Creator and / or new targets. No need to make special upgrades or extra downloads.

What is in the Qt SDK 1.1?

Qt 4.7.3 for desktop, Qt 4.7.3 for Symbian and Qt 4.7.0 for Maemo/N900
Qt Creator 2.1,
Qt Mobility 1.1.3
Qt simulator
Remote compiler supporting Linux and Mac for Nokia supported platforms
Symbian toolchain
Madde toolchain for N900

Get your Qt apps into the Ovi Store
Now, all your apps developed with the Qt SDK 1.1 will be accepted into the Ovi Store. Yay!

Qt Developer Days 2011 Munich Announced!

We are also happy to announce the dates of Qt Developer Days 2011 Munich: October 24-26th. Stay tuned for more information on this soon.

Learn more here.

Get More Information
Get the download links and read about the changes here.
Qt 4.7.3 and Qt Mobility 1.1.3 have been released (Labs Blog) here.

I highly recommend you to get these resources to gain skills on Qt Development on desktop and mobile devices :

(copied mostly verbatim from Qt SDK 1.1 release announcement)

My Forum Nokia Champion 2011/2012 Diploma

2011-04-02T23:38:00.001-07:00

See I am now a Forum Nokia Champion again. Not kidding.. ;-) *brag mode on* hehehee :-)

I am now a Qt Ambassador :-)

2011-03-28T01:59:00.001-07:00

"Congratulations! You have been accepted into the Qt Ambassador Program."

The mail just came in this morning. Thank you Nokia... :-)

Sincerely,
Hendy Irawan
Qt Ambassador ;-)

P.S. More information about Nokia's Qt Ambassador program :

The Qt Ambassador Program is a membership-only program that honors Qt development projects. All developers around the world who create products and projects with Qt are eligible to apply. Membership to the Qt Ambassador Program is free and based on your outstanding and innovative Qt project.
Note: In order to apply to the program, you must have a live Qt project, which you are able to post on the Qt Ambassador Showcase.

The Qt Ambassador is a recognition program that complements our Nokia Certified Qt Developer program. We encourage all Nokia Certified Qt Developers to apply to be Qt Ambassadors and further extend their distinction in the Qt and overall developer community.

Nokia E5 Is an AWESOME Phone, But...

2011-03-10T22:42:00.001-08:00

I love my Nokia E5. It's reasonably priced, the keyboard is excellent, the feel and form factor is just great. BUT...

I'll try not to make this sound like bashing Nokia E5..although it probably is. It's definitely more about Nokia E5's software/OS that is Symbian S60 3rd Edition FP2... than it is about Nokia's hardware.

I have 3 "major" problems with Nokia E5 : (as you can see, they aren't destructive, but simply annoying)

SMS Alert Tone Sound Failure. After I reach about 1800 messages in SMS Inbox, my Nokia E5 won't alert me with sound. Practically the only way I can see if there are new text messages is by looking at the blinking keypad white light.
Screen dims under bright sunlight. I don't know if this is by (mal-)design or there is a setting that I mistakenly set, but it's very annoying that when I use my Nokia E5 under bright sunlight, the screen goes completely dark and I can't see anything. The phone UI itself is still working (invisibly) and when I press keys, it actually makes actions. Now it gets annoying and dangerous (e.g. I could mistakenly delete a message).
Exchange ActiveSync / Google Contacts regularly wipes my phonebook. This is probably more to do with Exchange ActiveSync than with Nokia E5 or Symbian, but I need this functionality to work well, because it's convenient for me to sync my Gmail address book with Nokia E5's phonebook (and I've been doing this since my BlackBerry days). However at times the sync will fail and it will wipe my Nokia E5 phonebook and for some time I'm left with completely empty phonebook before the next resync is successful. It's not dangerous, because all the data in Google Contacts is intact, but it's annoying because I have to re-specify default phone numbers and add members to groups all over again.

There are also slight annoyances :

Push mail / Nokia Messaging is not actively updating (i.e. "always on"). I'm not sure why it doesn't work now, but it did work a few months ago. I tried to set it to update a few hours, but it never updates unless I Synchronize ("Z") manually from Email. I also tried setting to "Always On", but it's never on... I'm using WiFi and most of the time I'm within WiFi area.
Email application in Nokia Messaging is slow. It's about an order of magnitude slower than my old BlackBerry Curve 8520's. From displaying a picture to composing it in an email takes about 5-10 seconds. After composing the email, sending it takes about another 5 seconds until it goes back to the previous screen. Email application is probably the slowest messaging application in Nokia E5, Contacts and Text Messages is sometimes slow (but usually just OK), and I have about 600 contacts and ~2000 text messages which I don't consider "huge" for today's smartphone standards (like Nokia E5).

Despite these shortcomings, Nokia E5 is still a great phone. Seriously. :-)

Being a Forum Nokia Champion again until 2012! :-)

2011-02-24T08:00:00.001-08:00

I got a really pleasant news from Forum Nokia tonight:

We are pleased to announce that due to your active participation in the field of mobile development and service to the Forum Nokia community in the past year, you have been re-selected to the Forum Nokia Champion program. Congratulations!

I'm currently the only Forum Nokia Champion from Indonesia, which is both sad (where's everybody?) and great (I'm special :-)

Here's my profile at Forum Nokia and my blog at Forum Nokia.

SMS Message Alert Tone not playing on Nokia E5

2011-02-09T20:35:00.001-08:00

I got the same problem again: SMS message alert tone is not playing on my Nokia E5. No sound at all, just the blinking light.

My previous suggestion, changing the home screen to another and then back, is not foolproof.

So I tried deleting messages fromSMS inbox and now it's working again. Right now I have 1825 messages and SMS alert notification sound is working. It seems the threshold is about 2000 messages and it starts to "silence" itself.

After deleting messages to about 1800 or under, if you still can't get SMS alert tone playing, restart the phone and then switch the home screen theme. It should work.

Qt Developer Workshop by Nokia - Bandung, Indonesia

2011-02-06T20:00:00.001-08:00

Forum Nokia invites mobile developers all around Bandung, Indonesia to attend Nokia-sponsored Qt Developer Workshop, held in Aston Primera Hotel, Pasteur, Bandung, Indonesia.

This session is presented by Eileen Khoo, Snr. Technology Expert at Nokia.

I met a few familiar faces, particularly smart people from ITB and iComm Bandung. Of course, ALL faces are familiar in some way in any developer event. ;-) (hint: it's not a Salsa dance course!)

How to Fix Nokia E5 Problem: Text/SMS Message Tone Not Working

2010-12-14T03:24:00.001-08:00

For the last few days (or weeks?) my Nokia E5 has an annoying problem: the text/SMS message tone is not played when receiving SMS. It won't vibrate either.

After searching through the Internet, seems like this has happened with other Nokia phones, especially Symbian S60 ones, like X6, E75, E72. I tried changing the message tone to Nokia default, but didn't work. I also tried deleting all text messages in my Inbox, but also didn't work.

I have restarted my phone numerous times.
I was about to reset my phone settings (by using *#7780#) but I remember something...

I once had a similar problem with email message tone. The solution was to change my home screen theme to 'Active'. My home screen was already 'Active', so I switched it to another home screen theme and tada! My Nokia E5 text message tone works again!

So, the solution is:
1. Go to Control Panel > Settings > General > Personalisation > Standby mode > Home screen theme.
2. Choose another theme. You can go back to your favorite theme after making sure the message tone works again.

Good luck!

Note: this bug dates back to around 2003 or probably earlier. Ironic that it still occurs with a modern 2010 device.

I'm Now Posting on Forum Nokia Blogs!

2010-11-30T07:05:00.001-08:00

Great news!

I'm now also posting articles on Forum Nokia Blogs titled Hendy Irawan on Mobile Qt.

I will still be posting here, though I'm not sure which articles should be on Forum Nokia and which ones should be here.

Or perhaps I will just cross-post. We'll see.

Anyway, it's good to have one more channel to share my experiences with Nokia, Qt and mobile applications development

fatal error: alsa/asoundlib.h: No such file or directory - building Qt Mobility 1.1.0

2010-11-29T10:56:00.001-08:00

If you get this error message while compiling Nokia's Qt Mobility 1.1.0 :

In file included from audio/qaudiodevicefactory.cpp:60:

audio/qaudiodeviceinfo_alsa_p.h:57: fatal error: alsa/asoundlib.h: No such file or directory

compilation terminated.

make[2]: *** [../../build/Debug/QtMultimediaKit/qaudiodevicefactory.o] Error 1

make[2]: Leaving directory `/home/ceefour/Vendor/qt-mobility-opensource-src-1.1.0/src/multimedia'

make[1]: *** [sub-multimedia-make_default] Error 2

make[1]: Leaving directory `/home/ceefour/Vendor/qt-mobility-opensource-src-1.1.0/src'

make: *** [sub-src-make_default-ordered] Error 2

You need to install ALSA Shared Library headers. In Ubuntu you just need to:

sudo apt-get install libasound2-dev

Sign Symbian/Qt SIS Apps with Qt Creator on Linux (Bonus: Qt+Qt Mobility Smart Installer for Nokia)

2010-11-28T09:15:00.001-08:00

The latest version of Qt Creator 2.0+ (included in Nokia Qt SDK) can now easily sign Qt/Symbian applications (.SIS files) with your Symbian Signed certificate and key files.

The best part of it is that it can also be used with Linux operating systems (e.g. Ubuntu). And you don't have to install Wine!
(See my previous article on how to use makesis.exe to sign SIS files on Linux for more details.)

To build a Qt/Symbian application on Linux and also sign the generated SIS file with your developer certificate and key, first you must install the Nokia Qt SDK Remote Compiler.

Open your Qt/Symbian project, go to Projects facet and add "Remote compiler" configuration.

Under Build Steps, expand "Compile at Server" details and you will see Sis Type and Symbian Signing settings.

There you only need to specify certificate file, certificate key file, and password/passphrase (if any).

As a bonus, you can not only sign the SIS file, but also automatically package it with Nokia Smart Installer!
Therefore, your Qt and Qt Mobility application now complies with Ovi Publish requirements and can be published to the Nokia Ovi Store! :-)

Example Nokia Qt SDK Remote Compiler output with Symbian Signing enabled :

Running build steps for project messagemerge...

Uploading to remote compiler
Uploaded: 16/24 kB
Uploaded 24 kB, waiting for build
bldmake bldfiles
WARNING: When building for ARMV5 platform Compiler RVCT2.2 or later is required.
ABLD.BAT build gcce urel
make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/EXPORT.make" EXPORT VERBOSE=-s
make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'

Nothing to do
make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'
make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/GCCE.make" MAKEFILE VERBOSE=-s
MMPFILE "/home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP"

make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'
make -s -C /home/ceefour/project/MessageMerge/messagemerge -f "MAKEFILE_0XEA138C70.MK" TO_ROOT=../../../../../../../../.. EPOCBLD=../../../../../../../../../Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MAKEFILE_0XEA138C70/GCCE TO_BLDINF=../../../../../../../../../home/ceefour/project/MessageMerge/messagemerge PLATFORM=GCCE MAKMAKE

MifConv version 1.11 build (39).
Checking: art/messagemerge-tiny.svg
Choosing...
Convert files...
.
Loading mif icons...
Loading file: /Symbian/9.2/S60_3rd_FP1/epoc32/winscw/c/system/temp/s1c0.tmp/art_messagemerge-tiny.svgb

Writing mif: /Symbian/9.2/S60_3rd_FP1/epoc32/data/z/resource/apps/messagemerge.mif
perl -S makmake.pl -D /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70 GCCE

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(51) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/osextensions/stdapis/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(52) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/osextensions/stdapis/sys/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(55) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/oem/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(57) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/middleware/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(58) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/osextensions/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(59) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/osextensions/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(61) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/applications/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(62) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/osextensions/loc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(63) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/middleware/loc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(64) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/applications/loc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(65) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/osextensions/loc/sc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(66) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/middleware/loc/sc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(67) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/domain/applications/loc/sc/" not found

WARNING: /home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70.MMP(72) : SYSTEMINCLUDE path "/Symbian/9.2/S60_3rd_FP1/EPOC32/include/osextensions/stdapis/stlport/" not found

initialiseConfig: GCCE
perl -S ecopyfile.pl "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70/GCCE/messagemerge.rsg" "/Symbian/9.2/S60_3rd_FP1/EPOC32/INCLUDE/messagemerge.RSG"

make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'
make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/GCCE.make" LIBRARY VERBOSE=-s

make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'
make -s -C /home/ceefour/project/MessageMerge/messagemerge -f "MAKEFILE_0XEA138C70.MK" TO_ROOT=../../../../../../../../.. EPOCBLD=../../../../../../../../../Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MAKEFILE_0XEA138C70/GCCE TO_BLDINF=../../../../../../../../../home/ceefour/project/MessageMerge/messagemerge PLATFORM=GCCE LIB

make -s -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70/GCCE/MESSAGEMERGE_0XEA138C70.GCCE" LIBRARY

make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'
make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/GCCE.make" RESOURCE CFG=UREL VERBOSE=-s

Created /Symbian/9.2/S60_3rd_FP1/EPOC32/INCLUDE/messagemerge.RSG
make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'

make -s -C /home/ceefour/project/MessageMerge/messagemerge -f "MAKEFILE_0XEA138C70.MK" TO_ROOT=../../../../../../../../.. EPOCBLD=../../../../../../../../../Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MAKEFILE_0XEA138C70/GCCE TO_BLDINF=../../../../../../../../../home/ceefour/project/MessageMerge/messagemerge PLATFORM=GCCE CFG=UREL RESOURCE

make -s -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70/GCCE/MESSAGEMERGE_0XEA138C70.GCCE" RESOURCEUREL

Creating /symbian/9.2/s60_3rd_fp1/epoc32/build/home/ceefour/project/MessageMerge/messagemerge/messagemerge_0xea138c70/gcce/urel
make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'

make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/GCCE.make" TARGET CFG=UREL VERBOSE=-s
make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'
make -s -C /home/ceefour/project/MessageMerge/messagemerge -f "MAKEFILE_0XEA138C70.MK" TO_ROOT=../../../../../../../../.. EPOCBLD=../../../../../../../../../Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MAKEFILE_0XEA138C70/GCCE TO_BLDINF=../../../../../../../../../home/ceefour/project/MessageMerge/messagemerge PLATFORM=GCCE CFG=UREL BLD

make -s -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MESSAGEMERGE_0XEA138C70/GCCE/MESSAGEMERGE_0XEA138C70.GCCE" UREL
main.cpp
templatesdialog.cpp
templateeditdialog.cpp
mainwizard.cpp
messagemerger.cpp
moc_templatesdialog.cpp
moc_templateeditdialog.cpp
moc_mainwizard.cpp

qrc_images-symbian.cpp
make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'
make -r -f "/Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/GCCE.make" FINAL CFG=UREL VERBOSE=-s
make[1]: Entering directory `/home/ceefour/project/MessageMerge/messagemerge'

make -s -C /home/ceefour/project/MessageMerge/messagemerge -f "MAKEFILE_0XEA138C70.MK" TO_ROOT=../../../../../../../../.. EPOCBLD=../../../../../../../../../Symbian/9.2/S60_3rd_FP1/EPOC32/BUILD/home/ceefour/project/MessageMerge/messagemerge/MAKEFILE_0XEA138C70/GCCE TO_BLDINF=../../../../../../../../../home/ceefour/project/MessageMerge/messagemerge PLATFORM=GCCE CFG=UREL FINAL

make[1]: Leaving directory `/home/ceefour/project/MessageMerge/messagemerge'
make -s -f Makefile sis
Processing messagemerge_release-gcce.pkg...
Created messagemerge_unsigned.sis
Successfully created messagemerge.sis for release-gcce using certificate c/home/ceefour/project/MessageMerge/messagemerge/.cert/OVI_10-29-2010.crt!

make -s -f Makefile ok_installer_sis
Processing messagemerge_installer.pkg...
Created messagemerge_installer_unsigned.sis

Successfully created messagemerge_installer.sis using certificate c/home/ceefour/project/MessageMerge/messagemerge/.cert/OVI_10-29-2010.crt!
Binary downloaded to: /home/ceefour/project/MessageMerge/messagemerge-build-wcc/messagemerge_installer_qt-4_6_3_m1_0_2_s60_3_1.sis
Download complete

See and download the full gallery on posterous

Signing Symbian/Qt Application in Linux

2010-11-28T04:29:00.001-08:00

Signing Symbian/Qt Mobile Applications conventionally has to be done on Windows.
The good news is now it's possible to sign Symbian/Qt mobile applications in Linux-based operating systems such as Ubuntu, with the help of wine.

First you need to get a Symbian certificate and key.
You can get your applications Symbian signed for free and get developer certificates from Ovi Publish.
Extract the signsis.exe file from this zip file.
Source: FExplorer thread
I recommend to make this file executable so you can run it directly with Wine and not having to prefix "wine" command for launching.
Running this command on Terminal:
chmod +x signsis.exe
Install Wine.
In Ubuntu, open Terminal and type:
sudo apt-get install wine

Now you can sign your unsigned SIS application files.

Type this command in Terminal:

wine path/to/signsis.exe <application-file.sis> <certificate.crt> <certificate.key>

If you make signsis.exe executable you can simply type:

wine path/to/signsis.exe <application-file.sis> <certificate.crt> <certificate.key>

Now you can sign any SIS file at will. :-)

For example in my system this is how it looks:

$ /opt/signsis/signsis.exe -s -v messagemerge_qt-4_6_3_m1_0_2_s60_3_1.sis messagemerge_devsigned.sis OVI_10-29-2010.crt OVI_10-29-2010.key

Signing
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub

Download qt_installer.sis Qt Installer for Symbian and other goodies

2010-11-17T12:14:00.001-08:00

Your Nokia/Symbian phone doesn't have the required version of Qt framework library yet.

And you're lazy to to install Qt for Symbian SDK.

What to do? You just need to download the qt_installer.sis file.

It can be found here:

ftp://ftp.qt.nokia.com/qt/symbian/

On the appropriate subfolder (Qt version), you'll find qt_installer.sis that can be transferred and installed on your Symbian/S60 Nokia device.

Nokia Qt SDK Remote Compiler - Available Environments

2010-11-17T10:49:00.001-08:00

Here are the list of build environments provided by Nokia Qt SDK Remote Compiler :

(see attached image)

It's pretty exhaustive. And covers about all the most common options (or *all* possible options???)

I've tried building with Qt 4.6.3 + Mobility 1.0.2 on Symbian 3rd Edition Feature Pack 1 and it builds fine!!! :-)

Really cool!

Installing Nokia Qt SDK Remote Compiler

2010-11-17T10:09:00.001-08:00

If you want to compile Qt Symbian/S60 applications on Linux/Ubuntu, you have to install Nokia Qt SDK Remote Compiler.

During Nokia Qt SDK installation, do not choose "Full", but choose "Custom" installation.
Then you can choose to install Experimental > Remote Compiler.

However, if you've already installed Nokia Qt SDK in "Full install" mode, you don't have to uninstall it.

On panel, click Applications > Programming > SDK-Maintenance-Tool
Now you can choose to install Experimental > Remote Compiler
(see attached picture)

Compiling Qt Symbian S60 applications on Ubuntu/Linux !

2010-11-17T10:03:00.001-08:00

I've just found a (very) hidden gem in Nokia Qt SDK : ability to compile/build Qt Symbian S60 applications on Ubuntu/Linux !

It uses a feature called Nokia Qt SDK Remote Qt Compiler.

Nokia Qt SDK has made it possible to simulate/run Symbian applications in a simulator (not emulator!) environment in Windows, Linux, or Mac OS X.

However, by using Nokia Qt Remote Qt Compiler, it's possible (and practical) to build Symbian/S60 applications on Linux/Ubuntu as well.
(Note that you still need to run the generated SIS files on a device, because Symbian/S60 emulator is not available for Linux, at least not with straightforward installation.)

I'm still on my way to installing the required stuff, but the steps are outlined here :

Nokia & AT&T 2010 Calling All Innovators North America developer contest for Nokia N8

2010-10-10T02:01:00.001-07:00

Welcome to the 2010 Calling All Innovators – North America developer contest, presented by Nokia and AT&T. We’re challenging developers to create new applications and games for the new Nokia N8 and future Nokia devices for consumers in the U.S. and Canada. With $10 million in cash, devices, and marketing prizes up for grabs, now is the time for you to take advantage of Ovi Store’s global reach which gives you access to the world’s largest community of app-purchasing mobile consumers.

The Nokia N8 is a powerful Symbian^3 device that is a new platform for innovative developers to create advanced, graphically rich, high performance apps that will delight consumers in the U.S. and Canada. We challenge you to take maximum advantage of the new capabilities in both the N8 hardware and Symbian^3 O/S, to create the next level of apps for the Nokia N8 and Ovi Store.

You can build apps for the Nokia N8 with Qt or Web Runtime:

Symbian, Android, and iPhone developers: Nokia Qt SDK – the new way to build powerful native apps for Symbian^3, Maemo, and in the future, MeeGo
Web developers: Nokia Web Runtime Plug-Ins, including Adobe Flash Lite 4.0

How to Enter

The App Submission Period is the period beginning on Sept 21st, 2010 at 12:01AM Eastern Time, and ending at 5:00PM Eastern Time on Friday, January 28th, 2011.

STEP 1:	Develop your app for the N8
STEP 2:	Register as an Ovi Publisher at http://publish.ovi.com
STEP 3:	Publish your app to the Ovi Store for the N8 in English for the USA and/or Canada.
STEP 4:	During the App Submission Period, complete and submit the Contest Registration Form.
STEP 5:	During the App Submission Period, complete and submit the App Submission Form for each App being entered in the contest.

More info: http://www.callingallinnovators.com/10m/

Installing Qt Mobility Final Libraries on Windows 7

2010-06-10T20:30:00.000-07:00

By following this article, you should be ready to develop Qt Mobility applications on Windows.

Note: This is only for Qt for Windows installation. If you want to develop Qt applications for Symbian on Windows, click here.

Install Qt SDK 4.6.3 + Qt Creator 1.3.1 for Windows.
Install Strawberry Perl for Windows (~ 32 MB). The reason why Perl is needed is covered in the later in this article.
Download Qt Mobility library sources.
Unpack Qt Mobility source distribution into a drive, e.g. C:\. This will create C:\qtmobility\qt-mobility-opensource-src-1.0.0
Launch Qt Command Prompt.
IMPORTANT: You cannot use regular Command Prompt!
Set the PATH to Strawberry Perl : (do not skip this!)
```
set PATH=%PATH%;C:\strawberry\perl\bin
```
Go to your Qt Mobility source folder and run configure:
```
cd \qt-mobility-opensource-src-1.0.0
configure
```
This will configure Qt Mobility build with default target directory: C:\QtMobility
Build Qt Mobility:
```
mingw32-make
mingw32-make install
```
Add C:\QtMobility\lib folder (the target folder) to your PATH environment variable (more on this below).
To add Qt Mobility documentation in Qt Creator: Go to Tools -> Options -> Help -> Add. Then browse C:\QtMobility/doc/qch/qtmobility.qch.

Now you're ready to develop with Qt Mobility on Windows. Check out Qt Mobility Quickstart App for an example.

Setting Environment Variables

In order to use Qt Mobility some environment variables need to be extended to locate the libraries, which are placed in the lib directory of the install path.

On Windows: PATH should be extended to include: C:\%TARGET_DIR%\lib

On my setup this folder is: C:\QtMobility\lib

PATH can be extended through Start -> Settings -> Control Panel -> System -> Advanced -> Environment variables. Under System variables, select "PATH", click "Edit..." and append your Qt Mobility lib folder.

Reboot your system to apply your changes to system environment variables.

You're now ready to develop Qt Mobility applications in Windows. :-)

See also:

Installing Qt SDK 4.6.2 on Ubuntu/Linux

2010-06-04T02:37:00.000-07:00

Qt is used for cross-platform desktop and mobile development for Symbian S60, Maemo (N900), Meego, Windows, Linux, and Mac OS X using C++ programming language.

To install the latest Qt SDK 4.6.2 on Ubuntu/Linux, follow these steps. For this example I'm using Ubuntu 10.04 Lucid Lynx.

Download the Qt Development Environment 2010.02. Install the

Install additional development libraries:

sudo apt-get install libglib2.0-dev libSM-dev libxrender-dev libfontconfig1-dev libxext-dev libgl1-mesa-dev libglu-dev

You're now ready to develop cross-platform Qt applications.

25 Most Useful Nokia N900 Mobile Apps

2010-05-27T02:44:00.000-07:00

Nokia N900 powered by Maemo 5 has great useful mobile applications.

1. Pidgin protocols plugin for Conversations and Contacts

AIM, Facebook, GaduGadu, Groupwise, ICQ, MSN, QQ, Sametime & Yahoo

A plugin for configuring accounts supported by libpurple, the same library Pidgin uses. The plugin adds support for the following protocols: AIM, Facebook Chat, GaduGadu, ICQ, MSN, QQ, Sametime, and Yahoo.
Warning: Do NOT use the Facebook Chat feature. Use Pidgin with XMPP or use the new built-in Facebook chat feature of N900 firmware version PR 1.2.

2. Conboy

Conboy is a note taking application.

It is designed to be easy to use - yet powerful. Conboy can read and write the Tomboy file format to be compatible with Tomboy on Linux, Mac and Windows.

3. MaStory

Blogging from your hands. MaStory allows you to blog from your Maemo device. Right now it supports Wordpress, Blogger, Livejournal and Drupal. You can write posts in offline mode and edit posts already published. It interacts with photo services like Flickr and Picasa. And more features for blogging from your hands. URL: http://maemo-wordpy.garage.maemo.org

4. Pidgin

Dedicated chat application for Nokia N900.

5. gPodder Podcast Downloader

Subscribe and download audio podcasts.

6. Hermes

Update your contacts with their Facebook profile photos.

7. DocsToGo Viewer Edition

View Office files (trial version).

8. Mauku

Update your status on microblogging sites like Twitter. witter (below) has more functionality for Twitter.

9. Pixelpipe Media Gateway for Nokia Share

Upload photos and media files to Facebook and other social networks and publishing services.

10. witter

Best Twitter client for N900.

11. TuneWiki Lyrics Widget

Show lyrics on desktop while playing music.

12. TuneWiki SMP for Maemo

Play music while showing lyrics, and other features.

13. Xournal

A better app to draw notes than Sketch, but for notes I still prefer Conboy.

14. Countdown Home Widget

Track deadlines.

15. Call Blocker for Maemo 5

Block unwanted calls.

See also Call Blocker for Maemo 5 article.

Call Blocker talk.maemo.org thread.

Alternative: PyCallBlocker, which requires rootsh and maemo-python-device-env.

16. zip

Compress files with ZIP using Command Line Interface (CLI).

17. Unzip Plugin for File Manager

Extract ZIP files from File Manager.

18. PyGTKEditor

Edit and run Python scripts.

19. fbreader

Read mobile books and CHMs.

20. kchmviewer

Read CHM format books, a good alternative to fbreader.

21. Flashlight

Use the bright N900 camera LED as flashlight in the dark.

To use: Slide open the camera cover, then turn on Flashlight applet from the status area.

22. grr

Read your Google Reader RSS feeds using a fast and user friendly Maemo UI.

23. fMMS

Send and receive MMS messages.

24. Extra Decoders

Enable N900 to play all sorts of movie and video formats.

25. icedtea6 JDK

Run Java Standard Edition (Java SE) applications.

Let me know your favorite N900 / Maemo 5 apps!

How to Set Qt Application Icon and Title in Symbian S60

2010-03-30T21:05:00.001-07:00

Set Symbian S60 Application Title/Caption:

Alter project.loc file as necessary. Backup as project.loc.manual for future use (or if overwritten).
In Qt Creator, go to Projects panel. Remove QMake from Build Steps.
You can run QMake manually. Afterwards, replace the project.loc file with the one you backed up.

Set Symbian S60 Application Icon (in Launcher and in Task Manager):

Create icon using Inkscape or Adobe Illustrator. If using Adobe Illustrator, export directly to SVG-Tiny. Otherwise, export to SVG (Basic) format.
You need to convert SVG to SVG-Tiny format. Go to <S60 SDK>\S60tools\svg2svgt\installer and run the installer (SVG2SVGTConverter.exe) using the following settings:
- Compatibility: Windows XP Service Pack 3
- Run as administrator
Use the installed SVGT Tool to convert your SVG to SVG-Tiny format. Refer to this Forum Nokia Wiki article for more information.
Add the following to your project.pro : (make sure to use the SVG-Tiny file)
ICON = project-icon.svg

After changing your application icon, you may need to restart the phone to clear the icon cache so the updated icon will be shown. This problem happens at least in Nokia E71.

For detailed Symbian development resource, check out Developing Software for Symbian OS 2nd Edition (Symbian Press).

Update: Starting from Qt 4.7.2 (which is "currently unusable" for Symbian applications, since Ovi Store doesn't yet accept Qt 4.7 apps), QTBUG-13917 provides a better way:

If developer specifies "CONFIG += localize_deployment" in .pro file, the generated .loc and .pkg will now use translatable strings from .ts files defined in TRANSLATIONS. The .ts files must have an underscore and Qt language code at the end of the filename body to be compatible with deployment localization. E.g. myapp_en.ts.
Running lupdate will generate these entries into .ts files:

Application short caption

Application long caption

Package name

Smart installer package name