The Spatial Miscellany

A few weeks ago, I set about upgrading the firmware on my phone, I guess firmware on a mobile phone is comparable to an operating system on a personal computer. The mobile phone manufacturer, in this case nokia, sporadically releases new versions of firmware for each of its phones. When nokia gives its phone to a network provider for distribution (in this case vodafone), they also provide a stable version of the firmware. I assume at this point the network provider can work with the firmware to ensure it’s bug free and works on their network – generally this means disabling features the phone manufacture has provided, but the network operators are reluctant to support, for example, voip internet telephoney.

I purchased my N95 at a subsidized price from vodafone; when I received my N95 it was loaded with firmware version 11. You can find out which version firmware is loaded on your phone by punching in the following key combo: *#0000# . Nokia have recently released a new version of their firmware for the N95 that enables assisted-gps, firmware version 12. Keen to upgrade I contacted Nokia, first by dialing 191 and subsequently popping into their local store to ask for a firmware upgrade – but no joy. I don’t think the network provider has any real interest in updating firmware, as each firmware release requires comprehensive testing by the network provider to make sure it’s as stable as the previous version. The vodafone representative suggested I visit a local nokia service centre, which I did. However, it turns out that nokia have supposedly banned their service centres from touching the N95 as ‘it’s complicated’, any ‘fixes’ have top be undertaken back at nokia, which means a lengthy wait. Arrgh what do I do? Do-It-Yourself (DIY) – worst case scenario I end up with a £150 paperweight?

First I download the nokia mobile phone ’software updater’ software. Before you can install any software using the software updater, you have to supply your mobile phone product code, the phone updater software uses the product code to determine which version of software can be installed on your phone. An unbranded N95 supplied by nokia has a different product code to my subsidized vodafone N95. If I enter my vodafone product code, the software updater informs me that I already have the most recent firmware installed – version 11? If I enter the unbranded N95 product code, it informs me a newer version is available? When you wire your phone up to the ‘updater’ software, if your phone has a vodafone product code, it recognizes this and prevents you downloading version 12 .

There is a little gem of an application named the Nemesis Service Suite (NSS). Now I’m not sure exactly how this software works, or what exactly it does, but it was very useful. It’s handy software as it lets you change your Nokia mobile phone product code. So I back up my phone to memory card, change my vodafone product code to the nokia product code (0536062) (more product codes) and proceed to update my firmware. The nokia software updater now lets me download and install firmware version 12 (thinking I’m an unbranded phone). Now I have the new assisted GPS capabilities…but all is not well, my phone is now unresponsive, hangs and to be honest is pretty close to being a paperweight. So hoping to fix this I restore my memory from the memory card, but this just makes things worse, much worse. I restart my phone only for it to crash halfway through start up and suggest I contact my provider? Arrgh? It really is a £150 paperweight.

Surfing the web and I find a key combo that will format the phone, I hold the pencil key, plus *, plus 3, while booting; it performs some sort of reset, erasing everything on the phone memory, but the memory card is untouched. I then use NSS to switch my product code back to my vodafone product code and all works well…really well. I’ve been using it for best part of a month now and its working fine. I remain cautious as to what happens when vodafone try to upgrade my firmware, but that’s for another day.

So if you take this approach…

• Make sure all your contacts are stored on a memory card and not the phone.
• NSS will allow you to change product codes and ‘trick’ the Nokia software updater into installing the latest firmware.
• If you back your phone up to the memory card before the update, don’t restore unless prepared to reformat, and risk ruin.
• To avoid buggy behaviour, after the update, swap the phone back to it’s original product code.
• Your warranty is probably rendered null and void.
• Cross your fingers.

Find this post useful? Click to Digg!

I finally found some time to have a tinker with the Nokia Series 60 SDK, and build a hello world location application for my Nokia N95. Applications for the Series60 platform can be developed in several languages, as a developer you are spoilt for choice.

Having vague recollections of working with Java whilst undertaking my undergrad dissertation at Lancaster way back when, I plumbed for Java and promptly downloaded the Eclipse IDE. Next up, I installed Carbide.j, a suite of mobile development tools from Nokia. It was at this point I encountered my first frustration; it turns out the Carbide tools from Nokia don’t support the latest version of Eclipse, a school boy error of failing to read the doc. A quick uninstall, download, and install later, I’m back on track with an older version of Eclipse (3.1.2).

Nokia have provided a whole host of up-to-date documentation for building LBS applications for the series60 platform, so I downloaded their TouristRoute Java Midlet example and their location API developers guide. The location API is pretty concise, with a handful of important classes:


LocationProvider: represents the source of the location information (in this case the integrated GPS)

LocationListener: receives events associated with a particular LocationProvider.

Coordinates: represents coordinates as latitude-longitude altitude values.

Location: represents the standard set of location information (time-stamped coordinates, speed, accuracy, course, etc.)

Landmark: represents a known location with a name.

LandmarkStore: has some methods for persistent landmark store management (store, delete, and retrieve landmarks).


The sample built fine, generating a Java Archive (JAR) file and Java Application Descriptor (JAD) file. The JAR file is a package of the classes and resources, the JAD file a description of the Midlet. Right clicking on the JAR file (the midlet executable), the Eclipse context menu gives you two deployment options:


1) Deploy by Bluetooth
2) Deploy to Web Server


Unfortunately my laptop doesn’t have Bluetooth, so I went with option two and uploaded the files to my server (they can be downloaded here). I uploaded both files, the JAR and the JAD, I’m not sure if both are required or not? I added corresponding mime types to the .htaccess file on the server (this instructs the server how to handle requests for jar and jad files) and browsed to the jar file with my mobile phone browser. A couple of keypad clicks later, the application had been downloaded and installed on my phone.

Lots of useful documentation and active discussion forums made getting started building mobile app’s a breeze. However, it looks like my experiences may already be somewhat outdated, it appears Nokia have recently abandoned the Carbide.j developer kit in favour of newer tools provided by Eclipse.

I have had the phone for a couple of months now and am very impressed. Nice design, great camera, and a half decent GPS, but it’s the open development platform that sets this phone apart from the crowd, allowing everybody and anybody to develop a whole host of useful (and not so useful) applications. So far I’ve already acquired SportsTracker, which allows me to save my mountain bike routes as KML, some handy software that uploads my photos to my Flickr account, and the ubiquitous Google Maps which syncs nicely with the GPS.

James recently mentioned the latest GPS enabled camera from Rioch. The chipsets that receive the GPS signals are apparently now available in bulk for $4 a piece, very soon cost will no longer be the barrier to making this default functionality in digital cameras.

I’m waiting in anticipation for the new Nokia N95, it’s due for release this spring and promises a lot with regards to geo-enabled mobile applications and digital photography. Pocket sized it has a 5 mega pixel digital camera with what should hopefully be a half decent lens from Carl Ziess, and…assisted GPS! A few phones out there have this kind of functionality, but the big plus here is that this is the first Nokia phone to run the 3rd edition of the series 60 platform (S60).

The S60 platform provides rich developer support, here’s a blurb from the Niokia website…

application developers can work in C++ (using native Symbian OS APIs), the Java™ language (using Mobile Information Device Profile [MIDP] 2.0 with an extensive range of additional Java™ Specification Requests [JSRs]), Python, Visual Basic, or C#, as well as with Macromedia Flash from Adobe.

One particularly useful JSR, available on S60 3rd edition(sp1) phones, is JSR-179 – a location API. This means, for the first time, developers have access to location information outside of the walled garden. No longer do mobile developers have to make a web request to the mobile operator for the location, they can just grab it locally of the phone, mash it up with their spatial data, and bingo, you can find your nearest pub.

I haven’t tried my hand a mobile application development, but with the comprehensive SDK’s from Nokia, I can’t imagine it will be long before someone writes a little app that records the location of your camera phone photos and spits out some kml.