Vinod Kumar K V's Forum Nokia Blog

Now setup Google Sync with Mail for Exchange !

Fri, 06 Nov 2009 21:13:04 +0200

While going through Gabor's article On Google's move in navigation, I happen to see the Google Sync page, Google Sync can setup with Mail for Exchange. You just need to download and install the Mail for Exchange (MfE) and later follow the Setup Google Sync.

This is for the first time I saw one of the Google's official page contain a link to NOKIA software, they usually provide all softwares their own. I don't know how many of you're aware of this, those who're not aware they can just try this NOKIA + Google combination.

New signing process - ACS Publisher ID now known as just Publisher ID

Sun, 09 Sep 2007 17:33:56 +0300

Yesterday I wrote an article on Forum Nokia Wiki about the general procedure to get an application Symbian Signed based on my previous experience on SymbianSigned.

Later, Jo had modified the article with this update: "The Publisher ID used to be known as an "ACS Publisher ID" and was previously purchased from Verisign, but this process has now changed."

So now onwards you've to approach TC TrustCenter to get the Publisher ID. More over there is a reduction on the cost of the Publisher ID, it's now around 200$ (earlier for getting the ASC Publisher ID from VeriSign was around 350$).

Thanks to Jo for sharing this update. :)

Turn work into play, the hero always wins !

Mon, 30 Jul 2007 07:47:32 +0300

Nokia For Business - Nokia Intrusion Prevention With Sourcefire

"You work hard at keeping the network safe. Here's a chance to simplify things for yourself. All you have to do is go back to school, play a computer game, and win prizes.

Try beating the clock in our computer game contest. Register your high score and you might even take home a Nokia E61 or one of five 4GB USB drives. While you're at it, learn about information security conferences within the region. Read up on Nokia's Intrusion Prevention with Sourcefire and securing your network soon becomes child's play." - http://www.nokiaforbusiness.com/apac/ips/.

Courtesy to Kriran Trivedi for this information. ;)

Another latest release of Carbide.c++ for Symbian C++ Developers.

Mon, 07 May 2007 14:10:13 +0300

Forum Nokia had released the ever waited new version of Carbide.c++ 1.2 to the public. This latest version supports the new Open C SDK plug in. Regardless to the earlier releases there are mainly four kinds of Editions available:

OEM Edition: This edition is for those of who spotlight on Symbian Kernel Development. This is feature rich as well as the costlier edition of Carbide.c++. The included features are: JTAG Debugging support, Crash Debugger, Performance Investigator, On-device Debugging (TRK) and UI Designer.
Professional Edition: This is aimed at those of who concentrated on device development and high performance and requires early access to next-generation Symbian technical specifications. The main difference from the first mentioned edition is that there is no JTAG Debugging support for this edition.
Developer Edition: The main attraction of this edition is that there is a UI Designer which will help most of the developers to create their application quickly. Other than this On-device Debugging (TRK) is also with this edition.
Express Edition: Developers can download this edition with free of cost. This is an entry level IDE for the developers, does not have any advanced features of other editions, but still have the so called Intellisense feature and some other basic features. More over you can integrate the SDK Help which is available from Forum.Nokia as an eclipse plug-in: C++ Developer's Library (Eclipse plug-in) with this edition.

Find more details about the latest version of Carbide.c++ v1.2 from here: Carbide Development Tools for Symbian OS C++.
More over these links will help you get to know more about Carbide.c++:

Remote Device Access - an introduction

Tue, 17 Apr 2007 12:01:18 +0300

Remote Device Access – An Introduction

Remote device access (RDA) is one of the latest services provided by Forum.Nokia to its registered users for free of cost. This will enable you to access the limited devices remotely from any where in the world. This will be a very useful service for those of who doesn’t have a phone for testing their application, and those of who want to explore the features of different models of Nokia phones. At present you will get access to only some limited Nokia S60 models based on a reservation. Following are the models which is available at present:

Nokia 3250
Nokia 5500 Sport
Nokia E60
Nokia E61
Nokia E65
Nokia E70
Nokia N73
Nokia N80
Nokia N93
Nokia N95

Basic Requirements

You need a standard web browser and JRE pre installed on your system to access this service. Find the detailed information on how to use this service here: Instructions for RDA usage.

Salient Features

Here are the key features of Remote Device Access service:

Manage files: This facility allows you to browse through the file system of the connected remote device (the protected directories are denied from access).
View debug log console: You can view the debug logs in a separate window. When ever a panic occur this window will show the thread causing the panic with the reason code.
Reboot phone: You can reboot the connected remote device when ever you want.
Clean phone: This will clean the user created file from the phone and will restore from a backup which is made previously.
Install software: This allows you to install your singed sis file on to the connected remote device so by which you can test it online.
Capture image/video: You can take a screen shot of the remotely connected phone and store in your PC. You can record a video from the remote device also possible.

You’ll get a comprehensive help with screen shots from this link: RDA User Guide.

DevInfo - Get the IMEI, IMSI, CellId etc., synchronously on 3.x devices.

Sat, 24 Feb 2007 14:26:26 +0200

In this blog entry I would like to share a small utility class, which is nothing but to find the Phone/Network/Subscriber related information in a synchronous way. In Forum Nokia Technical Library there is already a tip for finding the IMEI number in synchronously, you can find it here. I've just used that approach here to find these details:

Phone information: manufacturer, model and serial number (IMEI). You've to basically use the CTelephony::GetPhoneId() API to get these information.
Network information: cell id, location area code, country code etc. (this can be extended, check the SDK Help of CTelephony for that). With CTelephony::GetCurrentNetworkInfo() API you can gather the network related information. Notice here you need a ReadDeviceData capability for accessing this function.
Subscriber information: subscriber id (IMSI). The CTelephony::GetSubscriberId() API will help you retrieve this information.

All the above functions are not synchronous so to make it synchronous the work-around is the use of CActiveSchedulerWait. After the call of these asynchronous and SetActive() you have to call a iActiveSchedulerWait->Start() and in your RunL() you have to check whether the iActiveSchedulerWait is already started with iActiveSchedulerWait->IsStarted() if then stop by iActiveSchedulerWait->Stop(), then fetch the information. Get to know more about this please refer this example: DevInfo_3.x.

Please check my comments below for more clarity.

EDIT: Changed the article name (previously it was Get the IMEI of a 3.x device) and added a more elaborated and extended example. Changed the CDevInfoAppUi::ShowNetworkInfo() as mentioned by 'operelstein' in his comment and updated the latest link for the example to download.

EnvSwich(Reloaded): The tool to switch between SDKs.

Mon, 29 Jan 2007 11:46:16 +0200

This is my first blog to Forum.Nokia. I thank to the Forum.Nokia Team for giving me the privileges to post here.

Environment Switch

The switch between the SDK is again one of the issue with the developers in our community. Recently I saw more queries related with this issue on our discussion boards. So that I thought of sharing a modified version of the environmentswitch (which was a part of 2.x platform SDKs) unfortunately that is not available with the newest 3.x SDKs.

This tool is working perfectly with 1.x, 2.x and 3.x SDKs in my system. I hope you can even use it for other platform SDKs like UIQ and S80 etc. You can download that modified version of tool from here: EnvSwitch.

Content of the ZIP file

Basically the ZIP file contains the following files:

EnvSwitch.exe: The application which is used to switch between SDKs will be running in the background and will show an icon on you System Tray.
Index.html: A help on this tool.
Readme.txt: General instructions to use the tool.
Settings.xml: This file is an important file, which includes your SDK details, can be modified according to where you’ve installed your SDKs. (I’ve included the details of 1^st Ed to 3^rd FP1).

Configure

Please make sure that you’ve installed/unzipped this tool on the same drive where you’ve installed your SDK. I assumed that you’ve installed all of your SDKs on C: drive. In case if it’s in a different drive please makes sure that you’ve made the necessary change to the Settings.xml, such as the drive letter. In order to work this tool properly you’ve to make sure that the EPOCROOT environment variable does not exist on the system. You can check it by Control Panel->System->Advanced->Environment Variables.

Advantage

After running the EnvSwitch.exe, you’ll find a new icon on your System Tray. See below given pictures:

Figure1: The system tray after running the EnvSwitch.

Figure2: The EnvSwitch cascade menu option.

You will get a cascade menu on right clicking on that icon. The following menu items will be available:

Name of the SDKs: The SDK names which has been configured in Settings.xml.
Emulator: Will be shown after you select a particular SDK name. Can be used to launch the selected SDK.
Setup: This option will open the Settings.xml file in a text editor, so you can view it or modify it according to your needs.
Close: This will exit the application.

After selecting a particular device from the menu if you double click on the icon will launch the explorer with the SDK path as a root (please verify your SDK path the Settings.xml).