Nokia 3300 User Guide

Nokia 3300 Software
Developer’s Kit
Version 1.0
User’s Guide
September, 2003
Copyright © Nokia 2003. All rights reserved.
This document is for use with the Nokia 3300 Software Developer’s Kit. Reproduction, transfer, distribution or storage of part or all of the contents in this document in any form without the prior written permission of Nokia is prohibited.
Nokia, Nokia 3300, and th
Corporation. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.
e Nokia Connecting People logo are trademarks or registered trademarks of Nokia
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc
.
Nokia operates a policy of on-going development. Nokia reserves the right to make changes and improvements to any of the products described in this document without prior notice.
UNDER NO CIRCUMSTANCES SHALL NOKIA BE RESPONSIBLE FOR ANY LOSS OF DATA OR INCOME OR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL OR INDIRECT DAMAGES HOWSOEVER CAUSED.
THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED BY APPLICABLE LAW, NO WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR CONTENTS OF THIS DOCUMENT. NOKIA RESERVES THE RIGHT TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR NOTICE.
The availability of particular phone products may vary by region. Please check with the Nokia dealer nearest to you.
Visit Forum Nokia (http://www.forum.nokia.com)
, the site designed for developers using technologies
supported by Nokia.
Content
About This User’s Guide ........................................................................................................... 5
Who Should Read This Guide?.......................................................................................................5
Typographical Conventions in This Guide ..................................................................................... 5
Other Documents About This Product ...........................................................................................6
1 What is the Nokia 3300 Software Developer’s Kit? ............................................................. 7
Quick Tour of the Nokia 3300 SDK ............................................................................................... 8
Getting Information About the Content on the SDK ..................................................................... 10
About the Diagnostic Window................................................................................................... 10
About the Tracing Options........................................................................................................ 11
Setting Up the Nokia 3300 SDK.................................................................................................... 11
Starting the Nokia 3300 SDK Within an IDE ................................................................................ 12
Getting Information About the SDK............................................................................................. 12
Exiting Nokia 3300 SDK .............................................................................................................. 12
What’s Next?............................................................................................................................... 12
2 Setting Up the Nokia 3300 SDK ........................................................................................... 15
Setting Up Preferences.................................................................................................................. 15
Establishing General Settings ..................................................................................................... 16
Setting the Display Size of the SDK Main Window.................................................................. 16
Selecting the Language of SDK Menus .................................................................................... 16
Activating the Content Cache ................................................................................................. 17
Sending Sounds to a Sound Card............................................................................................. 17
Setting Up Network Access........................................................................................................ 17
Setting Up a WAP Gateway .................................................................................................... 18
Setting Up Direct HTTP for MIDlets...................................................................................... 18
Setting MIDP Provisioning and Execution Options .................................................................... 19
Setting the Provisioning Mode ................................................................................................ 19
Setting MIDlet Execution Options .......................................................................................... 19
Changing the MIDlet Security Policy ................................................................................... 19
Setting the KVM Heapsize................................................................................................... 20
Enable Persistent Record Store Emulation............................................................................ 20
Setting MIDP Tracing and Speed Options.................................................................................. 21
Selecting Tracing Options.......................................................................................................21
About MIDlet Speed Controls ................................................................................................ 21
Setting MIDlet Canvas Speed............................................................................................... 22
Setting MIDlet KVM Speed ................................................................................................. 22
Changing Instance Numbering and Access to Diagnostics............................................................. 22
What’s Next?............................................................................................................................... 23
3 Using the Nokia 3300 SDK ................................................................................................... 25
About Loading Content on the SDK............................................................................................. 25
Opening Content on the SDK Standalone Application .................................................................. 26
Nokia 3300 SDK User’s Guide 1
Loading Content With File>Open.............................................................................................. 26
Loading Content Using the SDK Menus..................................................................................... 26
Previewing and Browsing With NMIT....................................................................................... 26
Previewing WML Files Within Adobe GoLive............................................................................ 27
Viewing the Content .................................................................................................................... 27
Inputting Text and Commands From a Keyboard......................................................................... 28
Emulating Mouse Clicks With Keyboard Shortcuts .................................................................... 28
Inputting Text From the Keyboard ............................................................................................ 28
Working With Content Types ......................................................................................................29
What Content Types Are Mapped to What File Types in the SDK?............................................. 29
What Content Types Can You Load Directly Using the Browser?............................................... 30
What Content Types Can You Reference in a COD Object?....................................................... 32
Emulating a Multi-Media Memory Card (MMC) on the SDK....................................................... 32
What’s Next?............................................................................................................................... 33
4 Getting Information About the Content on the SDK.......................................................... 35
Working with the Diagnostic Window ......................................................................................... 36
About the Traffic View ................................................................................................................ 38
About MIDP View....................................................................................................................... 41
About KVM Heapsize Status ..................................................................................................... 42
About JAM Storage Status......................................................................................................... 42
About the Browser Source View ...................................................................................................43
About the Browser History View..................................................................................................45
About the Log View..................................................................................................................... 46
What’s Next?............................................................................................................................... 47
5 Using the SDK for Message Content Development........................................................... 49
About MMS Messages ................................................................................................................. 50
Creating an MMS Message Directly on the SDK........................................................................... 50
Creating and Previewing an MMS Message Using NMIT 4.0........................................................ 51
Creating and Sending an MMS Message With Adobe GoLive and NDS for MMS....................... 52
Processing an MMS Message on the SDK................................................................................... 53
Working with Push Messages....................................................................................................... 54
Creating a Push Message with NMIT ........................................................................................ 55
Processing a Push Message on the SDK ...................................................................................... 56
What’s Next?............................................................................................................................... 57
6 Using the SDK for MIDlet Development.............................................................................. 59
About MIDP MIDlets .................................................................................................................. 59
About Loading MIDlets With and Without Provisioning .............................................................. 60
Running a MIDlet Without Provisioning.................................................................................... 61
Provisioning a MIDlet ............................................................................................................... 61
Provisioning Using the Network ............................................................................................. 62
Provisioning Using Local Files and the Command Line Interface ............................................. 62
About JAD and JAR Validations for Provisioned MIDlets ......................................................... 63
Setting Up the SDK To Run MIDlets............................................................................................ 63
Using the Nokia 3300 SDK With JBuilder..................................................................................... 63
About the Nokia 3300 SDK Life Cycle in JBuilder ...................................................................... 64
Creating a MIDlet With JBuilder and Running It on the SDK..................................................... 64
Running a MIDlet and Displaying Trace Information in JBuilder ............................................... 64
2 Nokia 3300 SDK User’s Guide
Using the SDK with JBuilder and NDS for J2ME ....................................................................... 65
Using the Nokia 3300 SDK With Sun One Studio.......................................................................... 65
What’s Next?............................................................................................................................... 65
7 Running the SDK from a Command Line ........................................................................... 67
Accessing the Command Line Prompt .......................................................................................... 68
About the Command Line Syntax................................................................................................. 68
About the Executables ................................................................................................................. 69
About emulator.exe................................................................................................................... 69
About 3300.exe.......................................................................................................................... 69
About Options............................................................................................................................. 69
Getting Information About the CLI Options .............................................................................. 70
Options for Managing SDK Instances ........................................................................................ 70
Options for General Use ............................................................................................................ 71
Options for Tracing Java Output............................................................................................... 72
Options for General Management of Java Output...................................................................... 72
About Parameters ........................................................................................................................ 74
Working With a CLI Shell to Repeatedly Send Commands ........................................................... 75
Using Inboxes and Outboxes With MMS Messages ...................................................................... 75
Nokia 3300 SDK User’s Guide 3
4 Nokia 3300 SDK User’s Guide

About This User’s Guide

This manual describes how to use the Nokia 3300 Software Developer’s Kit (Nokia 3300 SDK). Nokia 3300 SDK is a development tool that lets you preview how wireless content will look and work when it is ultimately deployed to an actual Nokia 3300 mobile handset. You can also use the Nokia 3300 SDK to develop content for other Nokia handsets with characteristics and functionality that are similar to those of the Nokia 3300 handset (Series 40).

Who Should Read This Guide?

You should read this guide if you plan to use the Nokia 3300 SDK in the process of creating:
Web content designed to be browsed on a mobile phone, such as browsable WML and XHTML content
Wireless messages such as MMS (multimedia message service) and SI/SL (Service Indictor/Service Load) Push messages
MIDP MIDlets - Java applets in the form of JAD and JAR files. Typically, the MIDlets take the form of games or applications that can be downloaded from the Internet and used on a mobile phone.

Typographical Conventions in This Guide

This guide uses the following typographical conventions:
Convention Explanation
Courier
Italic Names of books and documents
Bold Names of Windows menus, commands, buttons, and icons
URL link
Text that you enter (as opposed to system prompts and responses)
•File paths
Commands
Program code
New terminology
Active link to a URL.
Nokia 3300 SDK User’s Guide 5

Other Documents About This Product

These other documents contain additional information about the Nokia 3300 SDK:
Nokia 3300 SDK Release Notes
Nokia 3300 SDK Installation and Configuration Guide
You can find these documents in the installation directory of the SDK. They are also freely available at www.forum.nokia.com.
Additional documents about this product and its related technologies may also be available at www.forum.nokia.com.
6 Nokia 3300 SDK User’s Guide
1

What is the Nokia 3300 Software Developer’s Kit?

The Nokia 3300 Software Developer’s Kit (Nokia 3300 SDK) is a development tool that lets you preview how wireless content will look and work when it is ultimately deployed to a Nokia 3300 mobile handset. You can also use the Nokia 3300 SDK to develop content for other Nokia handsets with characteristics and functionality that are similar to that of the Nokia 3300 handset (series 40).
The Nokia 3300 SDK has an WML and XHTML color browser that lets the SDK receive content from web servers through a WAP gateway. Such content includes:
Web content designed to be browsed on a mobile phone, such as MIDP, WML, and XHTML content
Wireless messages such as MMS (multimedia message service) and SIC (Service Indictor, Compiled) Push messages
MIDP MIDlets - Java applets in the form of JAD and JAR files. Typically, the MIDlets take the form of games or applications that can be downloaded from the Internet and used on a mobile phone.
Nokia 3300 SDK User’s Guide 7
What is the Nokia 3300 Software Developer’s Kit?
MIDlet development is supported by these technologies:
CLDC 1.0.4 (Connected Limited Device Configuration)
MIDP 1.0 (Mobile Information Device Profile)
JSR 120 1.0 (Java Specification Request)
JSR 135 1.0 (Java Specification Request)
The browser runs on top of a WAP 1.2.1 stack.

Quick Tour of the Nokia 3300 SDK

You can run the SDK:
As a standalone application by selecting Start menu>Programs>Nokia Developer Tools>Terminal SDK>Nokia 3300 SDK 1.0>3300 SDK 1.0 or by double-clicking
<installation_directory>\bin\emulator.exe.
In an integrated development environment (IDE) that lets you create content with supporting applications and then immediately test the content with the Nokia 3300 SDK. (See Using the SDK for Message Content Development on page 49 or Using the
SDK for MIDlet Development on page 59.)
For this quick tour, start the SDK as a standalone.
The appearance of the SDK is faithful to the appearance of the handset, although the contrast and color rendering capabilities of each might differ slightly because of differences in monitor calibration, imaging technologies, and ambient lighting.
The menu structure displayed in the SDK’s browser is identical to that of the Nokia 3300 phone handset, although not all menus in the SDK work identically to their Nokia 3300 handset counterpart because the SDK is not a phone but a developer’s tool. For example, you cannot make a phone call on the SDK. When you place a phone call, the SDK simulates placing the call to the extent that you have to cancel the call function by clicking the End Call key, but the call is never placed.
8 Nokia 3300 SDK User’s Guide
The SDK’s main window looks like this:
SDK Instance number (like a telephone number)
Quick Tour of the Nokia 3300 SDK
SDK Menus
Content display 128x128 canvas size
Up and down keys for scrolling
Left and right keys for scrolling
Radio key
End call
Start call
Left soft key activates function on left (in this example, Menu)
Right soft key activates function on right (in this example, Contacts)
To simulate pressing the buttons on a Nokia 3300 mobile handset, click the corresponding keys on the SDK with the mouse. The SDK replicates the user interface of the Nokia 3300 phone handset with respect to its key definitions, menus selections, message display, backlight and vibration modes.
You can also select To o l s > C anva s to bring up the display area of the SDK, which displays canvas of the SDK at four times the resolution (512 x 512):
Instance Identifier
Nokia 3300 SDK User’s Guide 9
What is the Nokia 3300 Software Developer’s Kit?

Getting Information About the Content on the SDK

You can get information about the content on the SDK by using:
The Diagnostic window, which provides information about how the content of the content behaves
Command fine interface tracing options, which can help you debug a MIDP MIDlet

About the Diagnostic Window

When you select Tools >Diagnostics, the Diagnostics window appears and you can get information about how the content on the SDK behaves.
The Diagnostic window looks like this:
The information in the Diagnostic window lets you see information in views:
To se e Look at this view
Information about requests to and responses from the Internet Traffic
Information about KVM and JAM status MIDP
The source code of the content that is currently loaded on the SDK browser
A history list of the SDK browser Browser History
Warnin g messag e s Log
Browser Source
For more information about the Diagnostic window, see Getting Information About the
Content on the SDK on page 35.
10 Nokia 3300 SDK User’s Guide

About the Tracing Options

You can also activate tracing options that help you debug the content. These tracing options are displayed in the DOS Console:
For more information about tracing options and running the SDK from the command line, see Running the SDK from a Command Line on page 67.

Setting Up the Nokia 3300 SDK

To control some aspects of how the SDK operates and looks, select Tools>Settings. In Settings, you can set values for attributes such as the language in which the phone menus
are displayed, the network connection mode you want to use, and settings for running MIDlets. For more information, see Setting Up the Nokia 3300 SDK on page 15. The Settings window looks like this:
Setting Up the Nokia 3300 SDK
Nokia 3300 SDK User’s Guide 11
What is the Nokia 3300 Software Developer’s Kit?

Starting the Nokia 3300 SDK Within an IDE

While you can use the SDK as a standalone application, you can also use it within an integrated development environment (IDE) to create a powerful development and testing environment. These are some of the IDEs that support the Nokia 3300 SDK:
Browser IDEs Messaging IDEs MIDP Development IDEs
Nokia Mobile Internet Toolkit
Adobe GoLive Nokia Developer’s Suite for MMS Borland JBuilder
Nokia Mobile Internet Toolkit Nokia Developer’s Suite for J2ME
Adobe GoLive Sun J2ME Wireless Toolkit
You might need to configure your IDE to recognize the SDK as a supported device before you can launch the SDK from within the IDE interface. For information about configuring IDEs to work with the SDK, see the Nokia 3300 SDK Installation and Configuration Guide in the SDK’s installation directory.

Getting Information About the SDK

You can get information about the SDK from the Help menu:
For information about Select
Late-breaking news Help>Release Notes
Installing and Configuring the SDK Help>Installation and Configuration Guide
Sun One Studio
Using the SDK Help>User Guide
This version of the SDK Help>About

Exiting Nokia 3300 SDK

Select File>Exit. The SDK instance is terminated.

What’s Next?

If you want to begin using the SDK as a standalone application right now, you can:
Set up how the SDK operates and looks. See Setting Up the Nokia 3300 SDK on page 15.
Begin to load content on the SDK to see how the content looks and works. See Using
the Nokia 3300 SDK on page 25.
12 Nokia 3300 SDK User’s Guide
What’s Next?
Or you might want to explore running the SDK as a standalone application from a command line. See Running the SDK from a Command Line on page 67.
Nokia 3300 SDK User’s Guide 13
14
Nokia 3300 SDK User’s Guide 14

Setting Up the Nokia 3300 SDK

You can control some aspects of how the SDK operates and looks by
Making selections in the Preferences window (Tools>Preferences). See Setting Up
Preferences on page 15.
2
Editing the text file,
Access to Diagnostics on page 22
You can also change the default numbering style of SDK instances and turn off the Diagnostics feature (Tools>Diagnostics) by editing the text file,

Setting Up Preferences

In the Preferences window (Tools>Preferences), you can control:
SDK main window size, SDK menu language, cache use, and sound control
Networking settings, such as the WAP gateway and whether to use an HTTP connection for MIDlets:
Nokia 3300 SDK User’s Guide 15
3300.user.config
. See Changing Instance Numbering and
3300.user.config
.
Setting Up the Nokia 3300 SDK
MIDlet provisioning and execution options
MIDlet monitoring such as tracing options, KVM and canvas speed controls

Establishing General Settings

Select Tools>Settings and click General to set up how the SDK appears and operates. This panel appears:
Setting the Display Size of the SDK Main Window
Select the image size you want for the main window of the SDK. Both sizes function identically. This setting applies only to the SDK’s main window. The actual canvas size of the canvas remains constant at 128 x 128 pixels.
You can also elect to display the SDK on top of any other window on the screen by checking SDK always on top.
Selecting the Language of SDK Menus
For localization, you can select the language in which the menus in the SDK’s browser will be displayed.This setting affects only the menus on the SDK. Internet documents are displayed in the language in which the document was created. You must restart the SDK after changing the language setting for the new setting to take effect.
These languages are automatically installed when you install the SDK: English, German, Danish, Swedish, Finnish, and Norwegian You can download other languages from
www.forum.nokia.com. For more information about languages, see the Nokia 3300
SDK Installation and Configuration Guide.
16 Nokia 3300 SDK User’s Guide
Setting Up Preferences
Activating the Content Cache
The Nokia 3300 handset has a cache that stores downloaded Internet content. This feature improves browser performance. Checking Cache downloaded content enables the cache in the SDK, which causes the SDK to behave like the actual handset.
Unlike the handset, the SDK also provides you the option to disable this cache. Uncheck the box if you prefer to fetch a fresh copy of content over the Internet each time you browse to a location. Unchecking Cache downloaded content lets you observe any changes you made to the content on an Internet Web server and disables all cache directives from downloads.
Sending Sounds to a Sound Card
Check Play phone sounds to direct the SDK to send supported sound content to the computer’s sound card. When you don’t check this box, you won’t hear any sound from the SDK.

Setting Up Network Access

Both the Nokia 3300 SDK and the Nokia 3300 handset:
Use a WAP gateway - that is, you must have a WAP gateway or gateway simulator for the SDK to communicate with the Internet
Support MIDlets that use HTTP protocol through a WAP gateway
Unlike the handset, the SDK also lets you run MIDlets through a direct HTTP connection.When you use this option, you do not need a WAP gateway or gateway simulator. Using direct HTTP can facilitate the development of a MIDlet during the early stages. However, the communications using direct HTTP is different from communications using a WAP gateway, so you should do your final testing through a WAP gateway.
Nokia 3300 SDK User’s Guide 17
Setting Up the Nokia 3300 SDK
To set up network access for the SDK, select Tools>Settings and click Networking in the Setting dialog box. The Networking tab looks like this:
Set up the WAP gateway the SDK uses to communicate with the Internet.
Option: You can run MIDlets that use HTTP protocol with direct HTTP when you specify this information.
Setting Up a WAP Gateway
The SDK, like the handset, uses a WAP gateway for Internet connections. Under WAP Networking, enter the WAP gateway IP address and select a connection mode. This
information is available from your system administrator.
Setting Up Direct HTTP for MIDlets
To run MIDlets with direct HTTP - that is, without requiring a WAP gateway - check Use HTTP for MIDlets.
You might also need to use an HTTP proxy server if the Internet requests made from your computer passes through a proxy, which would be the case, for example, if you were working within a corporate Intranet.
To set an HTTP proxy, check Use an HTTP proxy server and specify the address of the proxy server (for example,
113.14.176.11
or
proxy.domain)
and a port number. This
information is available from your system administrator.
18 Nokia 3300 SDK User’s Guide
Setting Up Preferences

Setting MIDP Provisioning and Execution Options

Select Tools>Settings and click MIDP to set options that help you run MIDlets.The MIDP tab looks like this:
To access the options on the MIDP tab, check Overrule default handset behavior.
Setting the Provisioning Mode
For information about loading MIDlets, see About Loading MIDlets With and Without
Provisioning on page 60.
In the MIDlet Provisioning section of this tab, you can:
•Check Provisioning mode to load MIDlets through JAM.
•Check Non-provisioning mode to run MIDlets immediately and without provisioning. (Non-provisioning is the default value.) When you select this option, you can also set the maximum JAR file size of a MIDlet the SDK can run.
Setting MIDlet Execution Options
In the MIDlet Provisioning section of this tab, you can configure the MIDlet execution runtime.
Changing the MIDlet Security Policy
Network security settings override any security settings you set through the SDK menus with Applications>Games>Select Application> <MIDlet suite name>> Web Access.
Network security settings do not apply to direct HTTP communications. Direct HTTP communications is always allowed regardless of the current settings in Network access.
Set a new security parameters by checking Overrule default MIDP security policy and selecting a new value for:
Nokia 3300 SDK User’s Guide 19
Setting Up the Nokia 3300 SDK
Network access - The SDK controls a MIDlet’s access to the internet.
Allowed - The SDK automatically grants network access. (Default value on the SDK.)
Ask first - You’re asked to approve network access each time you execute a MIDlet.
(Default value in the handset when MIDP 1.0 applications are provisioned.)
Not allowed - Network access is not allowed.
Messaging access - Controls access to messages
Allowed - Accessing the message system is automatically permitted, and Message Sent is not displayed on the SDK display area. (Default value of the SDK.)
Ask every time - You’re asked to approve message access each time you send a
message. (Default value in the handset when MIDP 1.0 applications are provisioned.)
Not allowed - Sending messages is not allowed.
Setting the KVM Heapsize
The size of the KVM memory heap (heapsize) controls how much memory the MIDlet can take to run.
You can simulate the memory constraints of different devices. Let’s say you are working on a handset that is capable of loading MIDlets up to a maximum size of 320K. If you have a MIDlet that exceeds 320K, you may want to adjust the heapsize on the SDK to verify that the MIDlet can run in a tight memory space. Set a new value for the KVM heapsize by checking Set KVM heapsize and specifying a new value in kilobytes by appending a k to the number or in mega-bytes by appending an M to the number. The new KVM heapsize takes effect the first time you run a MIDlet after you set the heapsize. See the
Enable Persistent Record Store Emulation
-Xheapsize
option on Options for General Use on page 71.
Enable persistent records by checking Enable persistent record store emulation. A persistent record is a file a MIDlet can create that remains even after you turn off the SDK. For example, a persistent record from a MIDlet might contain scores from the last time you played a game. (Default value is enabled RMS emulation.)
20 Nokia 3300 SDK User’s Guide
Setting Up Preferences

Setting MIDP Tracing and Speed Options

Select Tools>Settings and click MIDP Monitor to set options that let you trace the performance of a MIDlet and control the speed at which it runs. The MIDP Monitoring tab looks like this:
Selecting Tracing Options
Check the tracing options you want to display in the SDK’s DOS Console. These tracing options trace events that occur in the KVM. (To view events that occur between the SDK and an external entity such as a gateway simulator or Internet, see About the Traffic
View on page 38.)
To use tracing options within an IDE, you must set the tracing options within the IDE.
These tracing options are the same tracing options in the command line interface. For more information, see Options for Tracing Java Output
on page 72.
About MIDlet Speed Controls
When you run a MIDlet on a fast computer, you might not get an accurate demonstration of how the MIDlet’s runs on a handset because the simulation runs faster on the computer than it does on the handset. MIDlet speed controls (KVM and Canvas speed) let you slow down the performance of a MIDlet on a computer to better reflect the MIDlet’s performance on a handset. Developing a MIDlet in an environment with a slower KVM or canvas delay speed can help you monitor and optimize your code.
However, turning on the canvas speed and KVM speed simultaneously can adversely affect the data you collect because canvas speed and KVM speed both control the speed of the SDK executable in ways that can conflict. For example, let’s say you are testing a MIDlet game with an intricate graphical display that requires frequent updating, and you slow down the canvas speed to better simulate the graphical display on a handset. Simultaneously slowing down the KVM speed will additionally slow down the canvas
Nokia 3300 SDK User’s Guide 21
Setting Up the Nokia 3300 SDK
speed, so the performance of the MIDlet will be distorted and the data you get will be inaccurate.
For more accurate results, enable only one performance feature at a time - either the canvas speed or the KVM speed.
Setting MIDlet Canvas Speed
Use the MIDlet speed delay slider to slow down a MIDlet that displays too rapidly on a fast computer. This setting is recommended for a MIDlet with an active graphical display that requires frequent updating (for example, a game).
Move the slider to the right to increase the delay in milliseconds of the canvas paint function. Because the maximum delay you can set is 100 milliseconds, this setting has no visible effect unless the canvas repaint rate of an object is significantly greater than 10 times per second.
Setting MIDlet KVM Speed
Use this slide setting to regulate the speed of bytecode instructions in the KVM - that is, the speed at which a MIDlet runs. This setting is recommended for a MIDlet whose graphical display does not need to be updated frequently (for example, an application that calculates a mathematical equation and then displays the result).
A value of 0 (zero) indicates this feature is turned off and that the KVM is running at maximum speed. The maximum average bytecode instruction execution time is 500 microseconds.

Changing Instance Numbering and Access to Diagnostics

You can change the default numbering style of SDK instances and turn off the Diagnostics feature (Tools>Diagnostics) by editing the text file, which is located in
<installation directory>\Nokia_3300_SDK_1_0\bin\
Disabling the Diagnostics feature, makes the SDK start faster. The SDK Tools menu does not change when you disable the Diagnostics feature in this file; however, when you select Tools>Diagnostics, the Diagnostics window will not appear.
The
3300.user.properties
# # Nokia 3300 User Configuration File # #First device instance ID DeviceFirstInstanceID = 3300000 #Diagnostics DiagnosticsEnabled = yes
file looks like this:
Change
to change the default instance numbering scheme
Change
3300.user.properties
.
3300000 to another number
yes
to no to disable Diagnostics
,
Sometimes when you make an international call on a handset, a plus sign (+) is required for the telephone number to connect - for example, +3300000. The SDK does not require the plus sign, although the SDK distinguishes between +3300000 and 3300000, considering each a distinctly different number.
22 Nokia 3300 SDK User’s Guide
Loading...
+ 56 hidden pages