While playing around with the Nokia 6212 NFC I found a very annoying issue.
A dialog appears every time I start the emulator telling me “This SDK has been tested with Microsoft Windows XP SP2 only, and may or may not function properly on this computer.”

The problem is, checking the “Do not show me this warning again.” does not work.

I assumed there would be some entry in the registry or some ini file that sets this flag. Unfortunately, I could not find it easily.

I looked into the S40_Nokia_6212_NFC_SDK_em.exe to find some “Microsoft” text but it looks like it’s compressed somehow.

I was quite disappointed that I could not find the source of this annoyance, but I did not give up.

I had one more ace up my sleeve: the ProcDump from SysInternals – now Microsoft.

It then took me less than 1 minute to fix the issue.

I executed

C:\KITS\kits system\SysinternalsSuite>procdump.exe S40_Nokia_6212_NFC_SDK_em.exe ProcDump v1.5 - Writes process dump files Copyright (C) 2009 Mark Russinovich Sysinternals - www .sysinternals .com
Writing dump file C:\KITS\kits system\SysinternalsSuite\S40_Nokia_6212_NFC_SDK_em.dmp...
Dump written.


I got a 100 Megs file. I did a quick search for Microsoft and got this:
os_version_warning_suppressed   Service Pack 2  jvm_version_warning_suppressed  Nokia SDK Launcher  This SDK has been tested with Microsoft Windows XP SP2 only,
and may or may not function properly on this computer. jvm_version_warning_suppressed  The SDK located Java Runtime Environment (JRE)  
   Unless you install JRE 6, the SDK might not operate properly.

Tada... my annoying text. Finally.
The text looked like registry entries, so I opened HKEY_CURRENT_USER\Software\Nokia\Series_40_Nokia_6212_NFC_SDK and saw a string key named jvm_version_warning_suppressed.
I then created a string key called os_version_warning_suppressed and set its value to true. Tada… No more annoying message.



In conclusion, it seems the developers for the emulator forgot to write the os_version_warning_suppressed to the registry.
But with a little bit of patience and the right tools, I was able to overcome this annoying inconvenience.

Edit 2009-11-10: if you are a developer make sure to check my colored logcat tool

I have seen that it can be a pain the ass to install the Android usb drivers used for debugging, so I put here the steps I made and successfuly got the Android to debug correctly.

1. install Samsung PC Studio 3  v3.2.3 IE2 to get the normal usb drivers. My link was http://lfiles3.brothersoft.com/internet/mobile/Samsung_PC_Studio_321_GJ9.exe

2. connect the Samsung Galaxy Android device(at this time USB debugging is turned off - see #4). Let Windows install the new hardware - the Samsung drivers.

You can now access the SD card on your device. You will see a USB symbol in the notification bar of the phone at the top. Pull it down and you will see "USB connected. Select to copy files/from your computer". Enable it and you will have access to the SD card.

Next steps are for development only!

3. modify c:\android-sdk-windows-1.5_r3\usb_driver\x86\android_usb.inf

under the [Google.NTx86] entry add
; SAMSUNG GALAXY
%USB\VID_04E8&PID_6640.DeviceDescRelease%=androidusb.Dev, USB\VID_04E8&PID_6640
%USB\VID_04E8&PID_6640&MI_04.DeviceDescRelease%=androidusb.Dev, USB\VID_04E8&PID_6640&MI_04
%USB\VID_04E8&PID_6640.DeviceDescRelease%=androidusb.Dev, USB\VID_04E8&PID_6640

under the [Strings] entry add
; SAMSUNG GALAXY
USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNG GALAXY"
USB\VID_04E8&PID_6640&MI_04.DeviceDescRelease="SAMSUNG GALAXY Composite ADB Interface"
USB\VID_04E8&PID_6640.DeviceDescRelease="SAMSUNG GALAXY Bootloader"

Some people have reported the MI_04 combination above is not working; you may want to try MI_1 to MI_4 to be sure.

4. go to the phone -> Settings -> Applications -> Development -> enable USB debugging

5. Windows will ask for a new driver - this is used for debugging. Point the driver search to c:\android-sdk-windows-1.5_r3\usb_driver\x86\.

You should now be able to use debugging on the Samsung Galaxy Android.

Tips on debugging Samsung Galaxy Android:

1. to check if you can debug on the Android, use “adb devices”
I have
C:\>adb devices
List of devices attached
I7500wJLU2AuEy0 device
This entry is for my Samsung Galaxy I7500 Android phone.

2. use “adb logcat” to see the live and past Android logs. This is probably the most used command.

3. check out the documentation to see how to install and remove applications from the Android phone: http://developer.android.com/intl/de/guide/developing/tools/adb.html

Good luck and have fun!

Edit 2009-09-28: also un/check(depending on your needs) the "Mass Storage only" option under Settings/About phone.