*** Installing the Titan device client The Titan device client is tested to run on Sprint Mogul running with ROM version 2.16.651.0. To install MJSP, you need to copy the Device\TitanDeviceRuntime-v1.0.CAB file to your device file system or a storage card using Active Sync or some other file transfer mechanism. Launching the CAB file directly from the device file system requires that you have 30 MB of free file system space. Launching the CAB file from a storage card only requires 20 MB of free file system space. Once the CAB file is copied, open File Explorer on your phone, browse to the folder containing the CAB file and tap on the CAB file. This will begin installation. When installation has finished, you may remove the CAB file. After MJSP is installed, it is running on your device will start every time the device is powered on. You may notice that the phone takes slightly longer than normal to be ready to use. In the Start ->Programs folder you will see a new shortcut for the Sprint Content Manager. See below for how to use Content Manager. *** Uninstalling the Titan device client To uninstall MJSP, go to Start -> Settings (System Tab) and choose Remove Programs. Select the Sprint PCS Titan Device Runtime and click remove. During uninstallation, you will receive a series of 3 popup messages as dll files are unregistered. These messages are expected. Uninstallation may leave log files in the device \temp directory. You may remove these files to free space on the device. *** Installation and Configuration of the Sprint Tools for Titan Prerequisites In order to use the Sprint Tools for Titan, you must have the Eclipse SDK Europa Release (aka 3.3) installed. This software package can be downloaded from Eclipse.org, IBM developerWorks, or a number of other locations on the web. Installing the tools After installing the Europa release of the Eclipse SDK, you can install the Sprint Tools for Titan by following these steps: 1. Start the Eclipse IDE 2. From the Eclipse main menu, click Help > Software Updates > Find and Install. The Install/Update wizard is displayed. 3. Select Search for new features to install and click Next. 4. In the "Update sites to visit" window, select the New Archived Site button. 5. Browse to select the drive and directory where the Sprint Tools for Titan zip file is located (Toolkit\TitanTools-20071210-1545.zip) and click OK. 6. Select the check box next to the site name and click Finish. 7. In the Search Results window, select the Sprint Tools for Titan zip and click Next. 8. In the Feature License window, read the licensing information for each feature that you are installing, and if you agree with the license, select to accept the license and click Next. 9. In the Install Location window, the directory location where this feature will be installed is displayed. You can select a different directory by clicking the Change Location button. 10. Click Finish to begin the installation. 11. In the Feature verification window, verify that the feature information is correct and click Install. Note: When warned about installing an unsigned feature, click Install to continue. This does not cause problems during installation. 13. When installation completes, you are prompted to restart your IDE for changes to take effect. Click Yes to continue. 14. Note: Clicking Apply Changes does not properly configure the environment. 13. To confirm that the installation was successful, start the platform and do the following: * Click Help > Software Updates > Manage Configuration. The Product Configuration window is displayed. Expand the list and verify that Sprint Tools for Titan is installed in the list. After installation, addition information on developing applications and use the Titan tools can be found in the Eclipse Hep. Start Eclipse Help from the IDE by selection Help > Help Contents *** Installing the runtime debug binaries In order to remotely launch and debug applications on the Titan stack, you must first install the developer additions to the stack. These additions are in the Device\TitanDeviceTools-v1.0.CAB and should be installed in the normal manner. After installing the CAB, it is recommended that you soft reset the device. The developer additions include the following components: * IBM J9 VM debug binaries allows applications to be launched in debug mode * ProSyst JProfiler Profiling Agent allows applications to be profiled for CPU, memory, threads, locks, etc. * Instrumentation Agent works in conjunction with the development host-side IDE plugins, allowing them to remotely launch the stack in normal/debug/profiling modes, access the administration console, deploy and manage the Titan stack software and more * Local OSGi Console provides a simple local administration console UI for the Titan stack *** Items not implemented in Rel. 1.0 of the MJSP implementation Application models: The following application models are not supported in this release. * OSGI Aware Midlets * WebApps Deployment: * Installation of midlets via OMA-DM is not supported. POMs must be packaged in OSGI deployment packages for distribution via OMA-DM. * Installation of midlets via browser requires that the jad contain an absolute URL to the jar file on the server. Sprint Extensions/System Events : * Sprint system events for clamshells open/close have not been tested but are implemented. * Sprint sytem events for MMS are not supported on Sprint Mogul and thus have not been tested. * Jog wheel events are not seen separately from the 5 way navigator events. Jog wheel up is seen as vkey_up and jog wheel down is seen as vkey_down. * com.sprintpcs.lcdui package not supported on CDC * com.sprintpcs.util.Muglet package is not supported on CDC * Sprint Extension events broadcast on OSGi Event Admin Service: All events are broadcast, but not all properties for these events are provided in this release. com/sprint/voice/outgoing 'CALL_ID'and 'TYPE' are provided, but 'CALLED MDN' is not provided. com/sprint/network/dataconnection/available 'TYPE' is provided, but 'NETWORKID' and 'HOME' are not provided. com/sprint/network/dataconnection/unavailable 'TYPE' is provided, but 'NETWORKID' and 'HOME' are not provided. com/sprint/network/dataconnection/connected 'NETWORKID' and 'IP' are not provided. com/sprint/network/dataconnection/terminated 'NETWORKID' and 'IP' are not provided. Note: In the case of a PCS connection, an outgoing call event will be triggered but the #777 phone number (called MDN) isn't provided. To avoid showing this as a call, you may filter on the combination of an outgoing call and a network connected for cellular. Content Manager : * non-java content is not handled. This includes items like ringtones, wallpaper, etc. * Applications packaged within an OSGi deployment package or midlet suite can not be removed individually. The package level must be removed as a whole. * The Content Manager update function will only work with OSGi standalone bundles. AMS: * Media MUGLET handling will not be supported by Teleca AMS since there is no support for GCD and non-java content Security: * MidpSignerCondition not supported, since midlets run in a separate CLDC VM * UserPromptCondition not supported, since midlets run in a separate CLDC VM Toolkit: * If device runtime terminated unexpectedly or has any problem for launching, try to delete z_iagent.txt in \mjsp\osgi\bin\scripts\ext and soft reset the device. * When remote debugging an application on a device, there are thread exceptions in the log. These exceptions will not impact the function of toolkit or the ability to debug the application. Runtime: * In OSGi, when attempting to load a second bundle with a native component of the same name a BundleException or FileException is thrown. The workaround is to explicitly request a 'gc' from the OSGi console before installing and starting the second bundle. * MIDlets should not make LCDUI calls in the PlayerListener.playerUpdate()callback. If LCDUI calls are required to handle a Player event, they should be executed in a separate thread. * JSR 120 SMS Push functionality is not functional. * Updating a DP containing a MIDlet with a DP of higher version (or a Fix Pack), which contains exactly the same MIDlet, will result in that MIDlet disappearing * Updating a DP containing a MIDlet with a DP of higher version (or a Fix Pack), which does not contain the MIDlet (or declares it missing), will result in that MIDlet disappearing * If a midlet experiences a port 80 or http error please verify the midlet is signed and http permissions are in the JAD. General: * On devices which with Windows Mobile security enabled, application icons in the shell produce warnings during device boot. * Device restart/shutdown cannot be detected on Windows Mobile 6, which increases the likelihood of data loss for applications running in the stack as the stack has no warning to shutdown the application before the device is restarted. * Do not reinstall a running midlet. If a midlet is running and you attempt to re-install it, the midlet will become unlaunchable. The solution is to go into Content Manager and remove the midlet and then install it again.