Geolocation API faults

First of all I want to say that I am a big fan of Google Company, and this blog don’t intend to decrease its value. I am just stating the faults of Geolocation API Network Protocol

Geolocation API faults with examples

1. Google don't take into consideration the signal strength of the submitted towers, that appears when you send 2 requests to Google with same tower id but with different signal strength, the response of Google will be the same for the 2 requests, example
   
2. Google don’t take into consideration the MCC of the submitted request, that will appear when submitting 2 towers with the same MCC while one response will given certain country location while the other response will give another country, example
   
3. Google do nothing with the history is the towers submitted by the user. That appears when you send 1 tower X and get a response Y also when you send 2 towers X and Z you will get the same response Y, example
   
4. When a tower is unknown is submitted as the current tower with a know tower as previous tower, Google do nothing with the second tower and return nothing, example

Notice:

• The submitted examples are Wireshark files so to be able to open these files you need to download that software, download link
  
• You can download the total examples from here

How to sign your sis/sisx on your S60 Symbian SDK mobile

In that tutorial i will talk about you to sign your sis files on S60 symbain SDK I did manage to deploy my application on E63 Nokia device which has Symbian OS v9.2 version S60 3rd Edition, Feature Pack 1.
I will divide this tutorial into 2 parts

1. Deploy simple application that require no capabilities
   
2. Deploy applications that require capabilities from your phone device

Simple application without capabilities

If you will want to deploy a simple application that doesn’t require any capabilities from your mobile phone you can deploy the generated sisx file generated from your carbide or whatever IDE you use but you will probably see that error message “Certificate error. Contact the application supplier”, to get around that error you can easily set your phone to install any application without checking for signed application and these are the steps to do that

Go to installations -> App.Manager -> choose options -> Settings, there you will find Software installation option change it to ALL and not signed only

After that you will be able to install any simple application you develop on your mobile isa

Application with capabilities

Case you are developing more complicated applications that requires capabilities from your phone, I assume you know the capabilities your application require also you know how to choose these capabilities from your IDE

If you try the previous way for deploying simple application you will probably get the following error “required application access not granted”, to get around that you will have to get a certificate to be able to install your application on your device

There are 2 main choices to get your application signed to be able to deploy it

Without using publisher key/id

And so without any cost which I will take about in that tutorial. This way is mostly used for testing products or for students trying to make application required for their study in college like my case.

To be able to sign your application you will have to use the Nokia open signing beta tool online at the following link in which you have to set the IMEI of your mobile, choose the required capabilities of your application and finally upload your sis file and not the sisx file. After going through the whole process, Nokia will provide you with a new signed sis file which will be installed easily on your device isa

With using publisher key/id

This way is mostly used when you want to develop commercial products, you will have to require a publish key as far as I know and so you will have to pay for Nokia there share, I don't know much about that way but I guess this link might help you more if you like to go ahead in that direction.