Mobilizing the world

If you want to handle both trackwheel and trackball click events at the same time without using the TrackWheelListener, you have two options:

• Build the app for 4.1 which will run on most BlackBerries but the navigationClick() won’t receive trackball events (that is, it will be useless on newer devices)
• Build the app for 4.2 and then you’ll lose a couple of devices (the old ones) but you’ll receive both trackball and trackwheel events

I guess you’ll have to have two binaries if you want to support the older devices as well (those who didn’t update their OSs).

Finally, after months of agony, Apple decided it’s time to move on and allowed our mobiPoke into the App Store.

Just a couple of hours ago we went live, both on mobipoke.com and halcyon.ro (brand new site design and content). You’ll find out there what our freshly baked product is all about.

If you have an iPhone/iPodTouch just search for mobiPoke in the App Store and download the Lite version or buy the Pro version (you should do the latter).

Enjoy!

We purchased mobipoke.com and we have a new placeholder site up there, check it out.
Launch date is sometime in the first half of July. Hang on to your hats for a little more…

In the upcoming weeks we’re launching an exiting new iPhone app called mobiPoke which is basically a fusion of the best ideas from superpoke/facebook/twitter/email packaged in a spiffy iPhone application. Watch mobipoke.com for further updates.

I’ve written a small application (Nokia2Google) that aids Nokia users in copying their contacts to GMail. One might want to do this when moving from a Nokia phone to an Android phone (just as in my case, from E61 to G1) and has to copy the contacts from the Nokia phone to Google, as Android (at least in the G1) uses your Google contacts directly.

I haven’t found one end-to-end solution for this; the closest I got was using the export tool in the Nokia PC Suite and the import tool in GMail. But, of course, the file that PC Suite spits out isn’t exactly what Google expects. This is where my little apps comes in: it converts the PC Suite contacts file into one that Google can import.

Here’s how you should use it:

Step 1.: Syncronize your PC Suite with your phone, to make sure it has all your contacts (I assume you know how to do this). Then, from the Contacts app (part of the Communication Centre, as Nokia likes to call it nowadays) in PC Suite select File / Export and save the comma separated file.

Step 2.: Using Nokia2Google open the previously exported csv file, and just save it as a different file. Conversion to the Google format is automatically done, as you save it.

Step 3.: In the GMail web interface go to Contacts and press the Import button. Select the saved cvs file and confirm the import. And there you go.

The G1 will automatically syncronize (if auto sync is enabled - otherwise you will have to manually sync) with the web and you should have all your GMail contacts on your Android device.

The fields Google uses are quite a bit different from the ones Nokia uses, but about 90% of the data can be correctly transferred to Google contacts (just as an example, Google contacts don’t have a birthday field). If you’re using basic fields (name, address, different kind of phone numbers, notes, etc.) you should be OK.

About the app

Nokia2Google was written in Java, and besides the regular runnable jar there’s a windows executable (with nice icons and all) wrapped using JSmooth. It worked well for me with Nokia PC Suite 7.0.9.2 with contacts from my Nokia E61. I think the cvs formats didn’t change much in time so it should work with other phones/pc suites. Leave a comment if you try it with a different combination or you have some ideas for future development (actually, one idea would be to send the contacts directly to google using the Google Data API; of course, only if there’s enough interest in the app).

Download

Windows executable: .exe
Platform independent jar: .jar

Once in a while my wireless toolkit emulator (wtk 2.5.2) starts behaving like a mad cow. Well, actually, it just forgets what I store in the RMS between emulator runs. The data is stored correctly and is accessible up until I close the emulator and run it again, after which the RMS contents is lost. It’s not a big deal, but a good bunch of other emulators I use can’t persist the RMS between runs at all, so I liked this feature of the WTK.

A quick way to fix this problem is to delete all the data from C:\Users\username\j2mewtk\, as the sdk will recreate these files when you run the emulator again, and from there on it stores the RMS contents correctly.

If someone knows the exact source of this problem (or at least the specific file I need to delete instead of all of the files under j2mewtk), please leave a comment.