Nokia Development
From University of Washington - Ubicomp Research Page
Jump to navigationJump to search
Go back to Nokia Overview
Python
Python on Symbian gives you access to hardware while still offering relatively easy development.
Java (NetBeans)
NetBeans is generally easier than Eclipse, but Eclipse is Nokia's "standard tool". Install the following tools (in order).
- PC Suite 6.82
- Java JDK
- NetBeans IDE 5.5
- NetBeans Mobility Pack 5.5
- Sun Wireless Toolkit has more optional packages and examples
If you haven't used NetBeans or done J2ME, try the following:
- Press F11 to build the application. The console will display the location of the .jar file you want. Once you've built find the jar, and use Nokia Application Installer (in Nokia PC Suite, Install Applications) to move it to the phone.
Java (Eclipse)
Most people use Eclipse and it's the Nokia standard. That said, the SDK seems to be crash prone. Install the tools below in order.
- J2SE v1.4.2_13 SDK. Install in the default location.
- Java JDK
- Eclipse 3.2.1. Known to crash, so save frequently. Use Java 1.4 to build or emulation will fail.
- Carbide.j 1.5. Get the SN from forum.nokia.com.
- Nokia PC Suite 6.80.21. Comes with Carbide.j. Newer versions will break deployment.
- S60 3rd Ed SDK for MIDP. Only needed for on-device debugging (BT,WiFi). Kind of buggy.
A few things to keep in mind:
- Hello World in Carbide.j is useful
- If emulation isn't working, you should check to see if Eclipse is using Java 1.4 to compile. If known working apps aren't working on the phone, it's most likely the wrong compiler. (Window > Preferences > Java > Compiler > Compiler compliance level should be 1.4)
- If deployment isn't working, you probably updated the Nokia PC Suite. Uninstall the entire PC suite and all Nokia connectivity drivers. Firmware updates seem to be OK, but unless you have a reason to update firmware, stay away.
- Make sure you hit the refresh button before you generate the new JAD/JAR files, or you may get stale files sent to the phone.
C++ (Carbide)
While you can build your own toolchain, Carbide.c++ is much easier and more stable.
- PC Suite 6.82
- Java JDK 5.0 Update 11. Needed for emulation,.
- Carbide.c++ v1.1. Get the SN from ( forum.nokia.com. You do not need the CFTags parser.
- Perl 5.6.1.638
- S60 Platform SDKs for Symbian OS, for C++, 3rd Edition, FP1
Symbian tends to be a pain, so these will help you get started:
- The Carbide.c++ screencast is mostly useless and definitely wrong in places. Try Carbide.c++: Getting Started instead.
- The Carbide.c++ tutorial is in Help-> Getting Started-> First Application Example.
- If you want on device debugging, you need €299 to pay for the developer edition of Carbide.
- The (very slow) emulator may look like an emulator, but it isn't. The phone will behave differently.
- To deploy an app, change the build type in Carbide to "Deploy (release)", then double click HelloWorld/sis/HelloWorld.sis to install
- If you get security errors on phone, Go into Menu: Tools: App Mgr. Then select Options: Settings. Make sure software installation is "All".
Links
- J2ME Source Tons of examples.
- J2ME Polish The easiest way to do GUIs, logging, and other useful things.
- J2ME Bluetooth Apps Before you do anything with Bluetooth in J2Me, check this out.
- J2ME on a Mac An emulator for doing J2ME on a Mac. Talk to yanokwa@cs for more Mac details.
- Framework for talking to native code over a socket J2ME (java for phones) doesn't have JNI, so this is useful.
- Symbian WLAN Signal Strength - Code for getting RSSI.
- Forum Nokia All things development on Nokia
- Howard Forums The premier phone site, Nokia section
- Signing Error Messages in S60 Explains certificate errors.