Submit >>
  • Welcome
  • Site Updates
  • Technical Bulletins
  • Latest Forum Posts
  • Latest Blog Entries

Welcome to the Sprint Application Developer's Website - Join us today!

Sprint Wireless Tool Kit (WTK) 3.3
Download the newest Sprint WTK and check out the many new features. 

Professional Developer Program
Learn details about the Professional Developer Program, which extends advanced capabilities to members.

iDEN Total Content Uploader 
Utilize this free tool to do OTA download of Java applications to your iDEN handset (forget those cables)

Open Internet Browsing Optimization Solution
Register your mobile friendly sites and domains at the  Openweb site to have them experienced directly by Sprint CDMA subscribers without optimization.

iDEN Java Certificate Expiration Issue
iDEN Java certificate expired causing Authentication errors, please see the Java forums for more information.



  See All Site Updates >>


  See All Technical Bulletins >>
 
Latest Forum Activity See All Forums >>
Forum Topic Author Last Post
Java ME JSR -135 sahajankhan 22-May-2008
Java ME WTK 3.3/LWUIT strange behavior for a hello app vupham 21-May-2008
Phones and Devices Help w/enabling dev root on V3m Doug Nelson 20-May-2008
Java ME developer cert cannot be opened - new info vupham 20-May-2008
Wireless Web and Messaging can Sprint use ClientID to identify a subscriber? eclauson 20-May-2008
 
See last 10 blog entries>>   Show all blog entries>>
Blog Entry Date Author
Access browser simulator

All,

For those few unaware of it, there is an Access Browser Simulator for the Sprint profile. You can access and download it by clicking on "NetFront (TM) Browser Emulator v3.3 Sprint Profile" in the Access web site @ http://www.access-company.com/products/downloads/i ndex.html

Regards,

The Sprint ADP Team 		11-Jan-2008 Raymond Reeves
 
View Comments
909 error on Sanyo Handsets

For quite some time now, developers have encountered and reported issues with 909 error being thrown on some Sanyo handset models when trying to download and install digitally signed Java apps on the handset with the developer root enabled. A little investigation revealed the problem. Below we discuss the issue and a possible workaround -

MIDP security specification requires the Application Management System (AMS) to compare the MIDlet Permissions across the JAD and the Manifest files and verify them to be identical. If the MIDlet-Permissions attribute contains a lot of permissions, then, due the size limit of 72 characters per line for the Manifest file per the JAR specification, the MIDlet-Permissions are split into multiple lines with each line being 72 characters in length. After the MIDlet-Permissions attribute line reaches the 72 character limit, the remaining text is moved to a new line with a whitespace added at the beginning. This process is repeated to accommodate the MIDlet-Permissions on multiple lines, each being 72 characters or less in length. The permissions are split without regards to accommodating each permission value in full on the same line. Following is an example -

JAD attribute

MIDlet-Permissions:
javax.microedition.media.control.VideoControl.getS napshot, javax.microedition.media.control.RecordControl,
javax.wireless.messaging.sms.send

Manifest attribute

MIDlet-Permissions: javax.microedition.media.control.VideoControl.getS
napshot, javax.microedition.media.control.RecordControl, javax.wirele
ss.messaging.sms.send

If you ignore the word wrapping that is due to the editor you are viewing this document in, the MIDlet-Permissions in the JAD file are all on a single line. Also, you can see how the same permissions are split up into multiple lines in the Manifest file (note the whitespace at the beginning of the lines following the initial line). Normally, the phone AMS can reconcile these formatting changes and judge the permissions across the JAD and the manifest to be identical. On some Sanyo handsets, due the way the AMS treats the new line character, it flags the two sets of permissions as not identical thus causing the 909 error.


A quick Workaround this problem is to extract the contents of the JAR file to a local folder on your computer, then open the Manifest file and undo the formatting of the MID-let Permissions attribute - put all the permissions on a single line, comma separated, just the way they are in the JAD file and then re-JAR the folder again. A freely available tool like ALZip can be used to extract the JAR file and re-create the JAR from the extracted files.

The process of extracting the JAR file, making the modifications to the contents of the manifest and recreating the JAR file results in the newly created JAR file having a different file size. So, in the JAD, you will need to update the value of the MIDlet-Jar-Size attribute with the exact size in bytes of the JAR file you created after completing the modifications.

And as the last step, you can sign this new JAR file using the WTK3.0. The app will then download to a handset which has the developer root enabled.
03-Jan-2008 Jay Indurkar
 
View Comments