========================================================================
RELEASE NOTES FOR SERIES 40 6th Edition SDK v1.0            19 Feb. 2009
========================================================================

Product description:
====================
The Series 40 6th Edition SDK, based on the Nokia 6260 slide phone, 
provides a development and testing environment for Java(TM) Platform, 
Micro Edition (Java(TM) ME) applications, MMS, SMS, WAP, XHTML, HTML 
browser content and OMA digital rights management (DRM).

Features:
=========
This version of the SDK supports the following Java(TM) Specification 
Requests (JSRs): 

- Mobile Information Device Profile 2.1, 2.0                   (JSR-118)
- FileConnection and PIM optional packages 
  of the PDA Optional Packages for the J2ME(TM) Platform       (JSR-75)
- Wireless Messaging API 1.1 for SMS                           (JSR-120)
- Mobile Media API 1.2                                         (JSR-135)
- Connected Limited Device Configuration 1.1                   (JSR-139)
- Web Services Java API for XML Processing (JAXP), XML-RPC API
  1.0 of the J2ME(TM) Web Services Specification               (JSR-172)
- Location API for J2ME(TM) 1.0                                (JSR-179)
- Mobile 3D Graphics API for J2ME(TM) 1.1                      (JSR-184)
- Content Handler API 1.0                                      (JSR-211)
- Scalable 2D Vector Graphics API for J2ME(TM) 1.1             (JSR-226)
- Nokia UI API 1.1a including the Force Sensitive Joystick API
- Java(TM) API for Bluetooth 1.1                               (JSR-82)
- Java(TM) API Bluetooth OBEX                                  (JSR-82)
- APDU and CRYPTO optional packages of the Security and Trust 
  Services API for J2ME(TM) 1.0                                (JSR-177)
- Advanced Multimedia Supplements 1.1                          (JSR-234)
- Mobile Service Architecture (subset) 1.0                     (JSR-248)
- Wireless Messaging API 2.0 for MMS                	       (JSR-205)

The SDK emulator supports the following features:

- Implementation of the open source browser.
- Location provider to enable testing of location-based applications.
- Analogue joystick support in emulator as an input method.
- 320 x 480-pixel HVGA resolution support in emulator.
- A TCP/IP protocol stack.
- Diagnostics features that include switchable on-the-fly tracing,
  network traffic monitoring, and MIDP memory monitoring.
- Flash Lite Player 3.0 from Adobe.

The SDK is based on the UI of the Nokia 6260 slide phone, including the
general look, key layout, key definitions, error messages, display and
rendering, soft keys and menu selection. 

The SDK supports Dutch, English, French, German, Italian, Portuguese, 
Spanish, and Turkish language support as standard. Additional languages 
can be added by installing the World Language Pack.

The SDK allows MIDP tracing of Java events. Tracing is enabled using the 
SDK menu selection: Tools/Preferences/MIDP Monitor. 
Tracing information can be captured in a file; the SDK command-line 
interface can be used to start the SDK. For example:
C:\Nokia\Devices\S40_6th_Edition_SDK\bin> emulator -Xnew >>tracelog.txt

Supported IDEs:
===============
- Eclipse 3.4.1 with EclipseME 1.7.9 or Eclipse Mobile Tools for Java 
  v0.9.1.
- NetBeans 5.5 to 6.5 with Java ME pack.
- Adobe GoLive CS2
- Adobe Dreamweaver 8

System requirements:
====================

Supported platforms:
- Microsoft Windows XP Professional Service Pack 2 
- Microsoft Windows Vista Business.

Additional requirements:
- Java(TM) Runtime Environment (JRE) 6.0 or later.

Minimum hardware requirements:
- PC with a 1-GHz Pentium-class processor.
- 512MB of RAM.
- Display capable of 16-bit colour at 1,024 x 768-pixel resolution.
- 150 MB of free hard-disk space.
- Network interface card.

Recommended hardware configuration:
- PC with a 2.8-GHz Pentium-class processor.
- 1 GB of RAM.
- Display capable of 24-bit colour at 1,024 x 768-pixel resolution.
- 200MB of hard-disk space.
- Sound card.

JSR-177 developers need a smart card reader. Gemplus GemPC USB Smart 
Card Reader was used for testing.

Disclaimer:
===========
- While the SDK provides emulation of the phones functionality, it is 
  not identical due to simulations and differences in the hardware. It 
  is recommended that final tests be undertaken on a suitable phone.

- The rendering of colours in the SDK emulator may not match the colours 
  seen on the phone. However, the SDK is ideal for verifying pixel 
  location and the general appearance of the phone UI.

- Audio simulation in the SDK emulator does not accurately represent the 
  sound heard on the phone. As a result, this SDK emulator is not 
  recommended as the primary tool for the testing of audio. However, the 
  SDK emulator is ideal for verifying audio as part of application 
  testing.


Known issues and limitations:
===============================

1. Video recording functionality is not supported in the SDK.
   Workaround: use the phone for video recording testing. 
   
2. The SDK supports T=0 smart card communication in JSR-177 SATSA-APDU 
   only.

3. The devices support DRM 2.0, but the SDK supports DRM 1.0.

4. The Real Time Streaming Protocol (RTSP) is not supported as part of 
   MMAPI (JSR-135) 1.2.

5. In the Content Handler API (JSR-211), a security exception is not 
   thrown during OTA invocation, even if the content handler does not 
   have network permission and static registration and un-registration 
   of content handler functionality works fine in normal scenario but 
   fails in JSR211 tck execution. Please use the phone for this testing.

6. The SDK implementation of Flash Lite from Adobe does not support: 
   XMLSocket, in-line text, and external streaming video.

7. The emulator does not support SMS pushregistry and distributed 
   message listener APIs of the JSR-120, as they are not getting proper 
   notifications. please use the phone for this testing.

8. The SDK may not work well with some sound card/driver combinations. 
   In such cases sound may be inaudible and MIDlets that use MMAPI
   may fail. As a workaround, try replacing the driver for the sound 
   card.

9.SDK memory card simulation does not show the correct used memory size 
   when files are copied from the PC file system into directories within 
   the emulator.

10.For SMS send and receive in the Diagnostics window for some languages  
   that support UNICODE characters, the diagnostics window does not  
   display the Unicode Characters, instead it displays each Unicode 
   character in its hexadecimal Big-Endian format.

11.NotifyIncomingMsgSMS MessageListener and SMS access buffer APIs in 
   MSA Subset (JSR-248) do not work in the emulator. Please use a phone 
   for this testing.

12.The emulator hangs when the browser navigates through large web pages
   such as www.msn.com when the emulator is installed under Windows
   Vista. This behaviour is not observed when installed under Windows
   XP.

13.Only one instance of emulator can be launched using the emulator.exe
   file found in the bin folder. 
   Workaround: Launch multiple SDK instances from the Start menu, 
   sdk.exe, or S40_6th_Edition_SDK_em.exe. They function correctly.

14.Supported video files are played, but if the options softkey is 
   selected then the video screen overlaps with the option items.

15.Playing a paused video file doesn't render its audio clearly, 
   distortions will be heard. 

16.Sometimes NCF Lite do not function properly on Windows Vista. This 
   behaviour is not observed with Windows XP.
   Workaround:- Restart the computer two or three times or Use NCF Full.

17.Incoming call event gets generated only for the first sdk instance. 
   It doesnt get generated for later SDK instances, if more than 
   one SDK instances are running.

18.De-registration of SDK instances with the simulated network 
   environment is not happening, Because of which re-launching of second 
   or higher sdk instances throws assertion failed error message. 
   Workaround:- Kill all the SDK instances and launch again OR Delete 
   the <Instance id> folders of re-launching SDK instances and launch  
   again.

19.Emulating the GPS location is not supported. Location values are 
   hardcoded and cannot be changed.

20.SMS message with more than 160 characters will be received in the SDK 
   as two concatenated messages.  

21.Voice recorder application in the emulator doesnt work but JSR135 
   recorder related APIs work. 

22.SDK Browser shows Link not available error message when tried to 
   launch some links, ignore this message as the browser will launch the 
   same links on selecting again.

23.Camera functionality works fine but screens overlap when camera 
   application is launched. 
   Workaround:- press down arrow key to get the camera screen to 
   capture.



Fixed Defects:
===============

1. Memory card format option doesn't delete files and folders in the
   memory card.

2. When establishing APDU connection, the MIDP permission security APIs 
   from the APDU and CRYPTO optional packages of the Security and Trust 
   Services API (JSR 177) do not work.

3. 3D audio control, audio effect APIs of Advanced Multimedia 
   supplements API (JSR-234) do not work.

4. Video playback simulation is not supported in the SDK emulator.

5. DRM protected files, such as those using separate delivery and 
   combined delivery cannot be opened from the File|Open option on the 
   emulators menu bar.

6. The Diagnostics windows browser source and browser history views do 
   not display the active web pages url.

7. The File connection APIs (JSR-75) that provide information about 
   directory size and last modified details do not work in the emulator.

8. Values cannot be set in Settings, Contacts, and Log applications in 
   emulator when the emulator is set to the Hindi language, however this 
   feature works for other languages.

9. Simplified Chinese and traditional language is not supported in 
   emulator. 

10.Verify that your JRE version is 6.0 or later. Warnings may 
   incorrectly indicate versions installed.

11.Record control, Player listener and MMS Delete buffer APIs in MSA 
   Subset (JSR-248) do not work in the emulator.

12.Frame positioning APIs in MMAPI (JSR-135) do not work in the 
   emulator.

13. Metadata control, record control, and video control APIs in MMAPI 
   (JSR-135) do not work in the emulator.

14.The emulators Bluetooth connectivity feature enables the pairing of 
   emulator instances and the exchange of content between emulator 
   instances. However, the emulator may become unstable during execution 
   of some APIs included in JSR-82. 

15.Analogue joystick support GUI option in emulator does not shows 
   disabled even after physically disconnecting the hardware.

16.It is not possible to test the get, and set Location APIs of JSR-179
   using the location provider in the emulator, please use the phone for
   this testing.

17.ContentHandlerServer Access API of JSR-211 do not work on emulator. 



Product support:
================

For product support, please visit the Forum Nokia web site 
http://www.forum.nokia.com/.

This product includes software developed by the OpenSSL Project for 
use in the OpenSSL toolkit (http://www.OpenSSL.org/).

The S40 Webkit Browser used in this product includes Open Source Software.Visit http://opensource.nokia.com/projects/s40webkit/index.html 
for further information.

Copyright  2009 Nokia Corporation. All rights reserved. 

Nokia and Forum Nokia are trademarks or registered trademarks of Nokia 
Corporation. Java and all Java-based marks are trademarks or registered 
trademarks of Sun Microsystems, Inc. Bluetooth is a registered trademark 
of Bluetooth SIG, Inc. Other product and company names mentioned herein 
may be trademarks or trade names of their respective owners.
