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.

• 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.

• Carbide.c++ - Google News
• Carbide.c++ Development Team Blog
• Carbide.c++ - Forum Nokia Wiki
  

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

• 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.
  

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:

1. Phone information: manufacturer, model and serial number (IMEI). You've to basically use the CTelephony::GetPhoneId() API to get these information.
2. 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.
3. 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.

• 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).

• 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.