Sprint phones updating to MIDP 2.0

Ok, first off I am new to the J2ME world, I have been doing Java professionally off-n-on for 5 years (between C/C++, VB, and .NET in its various forms). The last mobile application I did it was WML. So I have a couple of questions which likely have already been covered but I couldn't find in the search feature, so sorry. =)

1.) Can a phone's JVM be upgraded? I would assume so but I couldn't find any hint to it. I would like to use some of the MIDP 2.0 features, but not if older/current phones aren't ever going to be able to run the app(s). I searched Sprint's site, Google, and here and never found anything about this.

2.) So various phones behave/interact with Java apps differently? The JVM isn't a complete and robust seperation between the app and the hardware? WOW! That said, is there characteristics of how the JVM behaves across manufacturers or something; or must you really test against each and every phone you want your app. to be available on?

Ok, thats more then a couple of questions. =)

Thanks in advance for any help.

Jenslove

By Jenslove at 26 Oct 2004 - 17:53
Java Applications
Add new comment

JcPtzzuxODwEc

car insurance qoutes bmoi slots noed auto insurance quotes =DDD

By buckstab at 5 Sep 2010 - 20:54
reply

YBkYfjfIwlYhIE

buy accutane tjua online accutane =-DD ativan online 809 propecia %-) buy valium in 6276

By mkaymer at 19 Aug 2010 - 16:41
reply

BTPcYGIhROaXrPIfor

vVgrY4 iaopylpejfjk, [url=http://acmbaafkssrk.com/]acmbaafkssrk[/url], [link=http://lpitkfaypggc.com/]lpitkfaypggc[/link], http://mscudegvxafx.com/

By mkaymer at 18 Aug 2010 - 12:55
reply

Sprint phones updating to MIDP 2.0

1) As far as I know, no. A phone's JVM can't be upgraded.

2) Much to the bain of the developers where I work, there are quite a few differences between phones, even among the same manufacturer. For instance, the Samsun A600 is a dog slow phone, while the A660 is relatively fast and the A700 is a speed demon. Audio is a major point of difference between phones. Sometimes a certain sound will crash the program just because the phone didn't like it. Audiovox is the worst at this since their phones don't throw an exception. It just sits there dumbfounded until you press the end key.

Another major difference are the font sizes. Plan ahead, don't hard code for a specific font size. A rouge phone will come along and smash any dreams of a single build working exactly the same across multiple phones.

By dogmouse at 6 Nov 2004 - 00:55
reply

Sprint phones updating to MIDP 2.0

You can update the JVM in the Treo 600, which by the way, is the only Sprint handset I'm aware of that has a MIDP 2.0 JVM.

In general, you can't update any of the OEM software. Sprint could update it if they wanted to, but they are a business and there is no money to be made in improving the JVM in your phone. You can expect only bug fixes from them.

I've said this before, but Java's premise of "write once, run anywhere" is a pipe dream. The reality is that the JVMs are horribly broken so the end-user experience is completely unpredictable. If you are selling a product, you have to test every handset. Truly, it is "write once, debug everywhere."

The simulator provided with the development kit is a sham. In my experience, when you get something working perfect in the simulator you are only about half done. Now you have to test it on your target JVMs and start removing features until you get to a common base that actually works.

By wfrantz at 7 Nov 2004 - 23:57
reply

Thanks!

Wow, definitly different from the Java world I am use too!

Very interesting way to run a technology based business. You'd think that the phone companies would have the manufacturers conform so that their services could be as useful as possible and stable.

Guess wireless phone companies haven't stepped into the 21st century yet, which is funny when you think about it.

Course maybe I am missing something. Maybe the manufacturers are the drivers.

Anyway, thanks for the responses.