The Definitive Guide to Running 3D-enabled Java MIDlets on Windows Mobile
Iâ€™ve started working on my MIDlet Bible, the premiere and definitive resource of everything related to running the, particularly on â€œdumbâ€ mobile platforms, hugely popular Java programs called â€œMIDletsâ€. Currently, the project is on hold because Iâ€™m still waiting for some MIDlet Manager developers to answer my mails so that I can, for example, can directly recommend where to download / purchase MIDlet Managers from. (If youâ€™re one of them and we used to be in correspondence but you havenâ€™t heard anything from me, please check your spamfilter â€“ it might have caught my mail(s).)
Several people have been looking for running 3D-based games on Windows Mobile. As this part of my forthcoming MIDlet Bible is pretty much self-contained, doesnâ€™t really depend on the rest of the Bible and can, therefore, be separately published, Iâ€™ve decided to take the plunge and publish it right now, before coming out with the â€œfullâ€ MIDlet Bible.
1.1 Is it worth bothering at all? Isnâ€™t Java, particularly 3D games, slow?
You may have heard a lot of people despising Java because of its â€œsluggishnessâ€. This is not really a case, particularly with the highly optimized Java environments, that is, MIDlet Managers (also abbreviated as KVMâ€™s; some people also refer to them as JVMâ€™s, using the well-known desktop/server mnemonic) of today. You will be REALLY astonished: current KVMâ€™s can produce at least as quick 3D speed as highly optimized, native Windows Mobile games written in C(++).
You donâ€™t believe me, do you? Neither would I have before embarking on some serious 3D MIDlet testing (and, of course, I also know most, if not all, native racing games for Windows Mobile like the palm of my hand).
Well, just give some of the tested racing games (for example, 3D High Speed, 3D Andreotti Racing, 3D Fast or Furious Fugitive) a try and youâ€™ll see this for yourself. Compare them to the current native 3D titles. These Java programs are blazingly fast even on VGA devices and even on, otherwise, graphically, pretty sluggish models like the HTC Universal â€“ while still rendering high-resolution (not plain pixel doubled) graphics. Yes, I told you, many Java titles just rock on Windows Mobile â€“ if youâ€™re into games and, particularly, racing games, you WILL want to give these programs a try.
Speed issues aside, price is another factor. Java MIDlets games, in general, way cheaper than native Windows Mobile games â€“ several high-quality Java games cost no more than $5, while native WM games, generally, start at $10. In cases, you are allowed to even buy a MIDlet for all your phones and, then, you can put it on any number of your dumb & smartphones and Windows Mobile handhelds. Think of it: you buy a high-quality MIDlet game for, say, $5, and, then, deploy it on the phones of your wife / husband / children in addition to your WM phone so that they can also kill some time playing it. You wonâ€™t ever have problems explaining to your wife why youâ€™ve spent a single penny on a game ;-) Yeah, being multiplatform (meaning a single Java MIDlet can run on a vast number of mobile phone platforms, even cheap dumb phones) has definite advantages.
This, of course, doesnâ€™t mean you shouldnâ€™t purchase Windows Mobile games, not in the least. The Windows Mobile market being tiny (orders of magnitude smaller than that of desktop Windows or, even, yes, Java MIDlets) developer community (and, consequently, the future of the entire platform) does need your software purchases too. Itâ€™s just good to know you can play a lot of cheap and, in cases, really high-quality games you may not have been aware of.
2. Available, 3D-capable KVMâ€™s
In this roundup, I mostly concentrate on playing games with three-dimensional (3D) graphics. There is a separate standard (JSR 184, also known as M3G) that most 3D (but not all!) games rely on. This means that, in order to be able to play these games, the KVM must support JSR 184. There are, currently, two KVMâ€™s that, currently, do this: Jblend by Aplix (coming with the Samsung BlackJack MS Smartphone and some, outside Japan, not widely used Pocket PC phones like the Sharp W-ZERO3), the 11.x series of TAO Intent MIDlet Manager coming with several Pocket PCâ€™s (note that the current TAO Intent version shipping with current (!)Smartphone ROMâ€™s, for example, the German ROM with the HTC Vox, still contain a 10.x-series, non-3D-capable TAO Intent version).
However, as there are some 3D titles that donâ€™t use the specific features of JSR 184, there may be cases you can use non- JSR 184-compliant KVMâ€™s to run these games. Without doubt the best of these non-M3G-compatible KVMâ€™s is Esmertecâ€™s Jbed, the successor of Jeodek of the same company, which ships with many current, WM6 Pocket PCâ€™s and Smartphones (for example, the HTC Vox / s710). Itâ€™s Jbed that you will always want to prefer when playing, especially because of its unique full screen and music emulation capabilities and speed.
Now, letâ€™s take a look at all these three KVMâ€™s.
2.1 Aplix Jblend
This KVM is compatible with everything Windows Mobile 5+ with a phone inside: that is, all WM5+ Pocket PC Phone Edition (Windows Mobile Professional) and Smartphone (Windows Mobile Standard) devices. This, unfortunately, also means itâ€™s NOT compatible with non-Phone Edition (that is, Windows Mobile Classic) Pocket PCâ€™s.
It has excellent M3G support and has no problems (as opposed to the TAO Intent MIDlet manager, introduced below) with WM5 softkeys either. It also has some other goodies; for example, by default, it stores all the deployed (installed) MIDlets under its home directory, unlike Jbed, the other excellent KVM. This has particular advantages on storage-constrained devices, particularly, low(er)-end Smartphones like the HTC s310 / Oxygene, which, by default, only has some 12M of built-in storage free. As a modern, decent (3D) game can easily take up 300-1000 kbytes, you will fill in your built-in storage very quickly if you use a KVM storing its deployed MIDlets there.
Its only downside is, in addition to not being compatible with non-phone-enabled devices, is the very bad sound and non-existing music emulation. In this respect, the two other alternatives (particularly Jbed) is WAY better.
Itâ€™s available for download HERE (direct download link to CAB file). Just download the CAB file and install it and, after that, you can just click on any JAR files copied to your Windows Mobile device, itâ€™ll deploy them (just press the left softkey two times to let it go on). Again, unless you have plenty of built-in storage memory and/or you only plan to install a handful of games, youâ€™ll want to install it on a storage card so that the deployed games (and other MIDlets) donâ€™t take up any central storage.
Note that there is another version of Jblend circulating on the Net; a much older and non-M3G-capable one called â€œJBlendFullScreenâ€. Its only advantage over the Jblend version Iâ€™ve linked in is that it uses the full screen (no taskbar will be visible at the top), which is of BIG help when you run strictly 240*320 (QVGA) MIDlets displaying important information (status row or even softkey titles) in the bottom-most 10-15 pixel rows otherwise hidden.
2.1.2 Consequences of not being full-screen
Several games suffer from the recent Jblend versionâ€™s not being full-screen; for example, the QVGA version of the pretty good, Russian-language Wolf3D clone "3D Bunker" and "3D Storm", 3D Burnout, 3D Formula Racing, 3D Covert Ops etc. Hopefully community hackers will soon come up with a decent solution for this problem. If you do suffer from this problem, in the meantime, either give a try to the old JBlendFullScreen (it MIGHT run the game if it isnâ€™t strictly M3G-based) or, even better, Jbed. Alternatively, you might want to use a version of the MIDlet, when available, meant for devices with smaller screen. Most MIDlets have several different versions for different screen sizes; 176*208 (old(er) Symbian S60), 176*220 (non-QVGA MS Smartphone) and QVGA (newer / better Symbian S60 and Windows Mobile) being the most widely used and available.
2.1.3 Java heap size setting
Finally, note that, unlike most other KVMâ€™s, you can set the memory given to Jblend in the registry ( [HKEY_CURRENT_USER\Software\JBlend\JavaHeapSize; which is 0x00400000 by default; that is, 4 Mbytes, which is already pretty high, compared to most other KVMâ€™s (except for Jbed; more on this question in the forthcoming MIDlet Bible). Setting it to a much higher value, 12M, didnâ€™t help with the non-working games Iâ€™ve retested.)
2.2 TAO Intent MIDlet manager
Another M3G-capable KVM is the TAO Intent MIDlet manager, of which Iâ€™ve already published a lengthy tutorial HERE. Youâ€™ll want to download the latest, 184.108.40.2066 version (direct CAB link), unless you have a non-Phone Edition Pocket PC, in which case youâ€™ll want to get version 1023 (direct CAB link). Finally, if you have a Smartphone, youâ€™ll want to forget it altogether as itâ€™s only the non-M3G-compliant 10.1.x series that is compatible with the â€œdumberâ€ platform.
As with Jblend (and, for that matter, Jbed, to be introduced below), itâ€™s simple to install: just get the CAB file and install it. As with Jblend (and unlike Jbed), if you install it on a storage card, itâ€™ll also deploy the MIDlets on the card to save built-in storage memory. That is, make sure you install it on a storage card if you have little built-in storage left.
Unfortunately, the TAO Intent MIDlet manager is, gaming-wise, pretty bad and youâ€™ll only want to use it in few cases (most importantly, when you only have a non-phone-enabled Pocket PC). For one, it has pretty bad music emulation. While itâ€™s certainly better than that of Jblend (the latter has no music emulation at all), itâ€™s WAY worse than that of Jbed. What is even worse, it doesnâ€™t support softkeys in most games (and many applications as is the case with, say, Teashark reviewed HERE), which means you just wonâ€™t be able to run these games if they do depend on softkeys (and most do â€“ very few games can be played / menus can be navigated without them).
2.3 Esmertec Jbed
This MIDlet Manager doesnâ€™t directly support the M3G library. However, as itâ€™s without doubt the best KVM out there right now, particularly music emulation and WM5 softkey-compliance-wise, itâ€™s still worth mentioning it in here. The reason for this is pretty simple: some of the popular 3D titles arenâ€™t strictly M3G-based (that is, based on JSR 184). These titles may run under Jbed as well, which means, in general, superior music and/or sound and, sometimes, speed compared to Jblend and, on top of all this, softkey support, compared to TAO Intent.
While thereâ€™re some purchasable Jbed distributions at Handango, I donâ€™t know whether theyâ€™re updated at all (their last-updated field are all 2005) and, despite my several mails sent to my Esmertec contact, in the last month I havenâ€™t received a definite answer to this question. Therefore, for the time being, youâ€™ll want to use an OEM version of Jbed version 20070802.2.1 available HERE. Unfortunately, this version is pretty buggy. Should you want to use it for other purposes (most importantly, for Opera Mini 4 beta 2, by far the best MIDlet-based Web Browser and one of the best Web browsers even on Windows Mobile), be aware of that it doesnâ€™t support for example cookie handling, unlike previous, but not any more working versions. This, however, wonâ€™t have any affect on running games, where itâ€™s really excellent at.
Jbed is, just like Jblend, compatible with both WM5+ Pocket PC Phone Edition and Smartphones. It is NOT compatible with regular Pocket PCâ€™s without a built-in phone. Sorry. Hope as soon as the Esmertec folks contact me back, Iâ€™ll be able to provide more info on which Handango Jbed distributions support non-phone Pocket PCâ€™s.
2.4 Co-existing on the same Windows Mobile devices
All these KVMâ€™s (and, for that matter, additional ones like IBM J9, Esmertec Jeodek etc.) can co-exist on the same Windows Mobile device â€“ they wonâ€™t have any influence on the other MIDlet managers. The only restriction will be that, should you click a JAD or a JAD file on either the Web or the local file system, the last-installed KVM will be invoked and it will deploy the given MIDlet.
However, you can easily remake a given KVM the default KVM to be invoked when clicking JAD / JAR files. No, you donâ€™t even need to reinstall the given KVM â€“ you will only need to import a given Registry import file, which changes the JAD / JAR file associations. Iâ€™ll provide these files in the final version of the Bible.
In the meantime, keep the following in mind: if you download the JAR file of all MIDlets youâ€™d like to use (you do NOT need the JAD files!), you can easily deploy them under any KVMâ€™s.
Fortunately, this is pretty easy in two of the three KVMâ€™s (in addition to the, in this respect, inferior Jblend, itâ€™s only with the, here, not discussed IBM J9 that itâ€™s a pain in the back to deploy a MIDlet to if you donâ€™t have set up the file associations or theyâ€™re pointing to another KVM: in there, you must enter the full path and name of the JAR file by hand and canâ€™t even use any file system browser tool). The Jbed and TAO KVMâ€™s have a â€œdeploy local filesâ€ option; you go there; in there, you are listed the JAR files in the file system. Your only task is selecting the one to deploy and all is done â€“ after this, you will only need to let the KVM deploy the stuff (answer Yes to the security questions and, with Jbed, to the question of the target folder). These menus are as follows:
TAO Intent: Menu / Install / Local (a list of the MIDlets found, just click the one youâ€™d like to deploy). Note that itâ€™ll only find JAR files residing in the root directory of your storage card(s), NOT in subdirectories, unlike Jbed.
The fact that Jblend doesn't have file browing capabilities also means that, should you want to keep all the three KVMâ€™s on your phone, youâ€™ll want to install Jblend last so that its file associations remain the default.
3. Compatibility info & chart
I've made some VERY thorough tests with ALL the 3D games available HERE. Feel free to give these titles a try. You only need to download the JAR files off the Web site; donâ€™t bother with JAD files. Note that you wonâ€™t be able to access the page with the standard desktop Internet Explorer (as is also pointed out in my Windows Mobile Web Browser Bible) because it isnâ€™t WAP-compliant. Therefore, if you do access it on the desktop (in order to download the JAR files to your desktop and, then, transfer these JAR files onto your Windows Mobile handheld in order to deploy them), make sure you use either Opera or Mozilla to access these pages.
You will find the compatibility results in the chart available HERE. Sorry for not including it in here â€“ itâ€™s way too big and, after all, itâ€™s only an additional click away. Iâ€™ve tested the latest, above-linked versions of Jblend, TAO Intent and Jbed. With Jblend and Jbed, Iâ€™ve run the tests with the HTC Vox (s710) Smartphone (Iâ€™ve chosen a Smartphone because of the directly and easily accessible dialpad on the front). For the (few) TAO Intent tests, I had to use a WM6 VGA HTC Universal because 1, it also has numeric hardware keys so I could still test controllability via dialpad (numeric) keys 2, itâ€™s a Pocket PC, and the 11.1.x, that is, M3G-compliant series of TAO Intent only supports Pocket PCâ€™s.
3.1 Dynamic screen stretching
Note that Iâ€™ve tested ALL the games compatible with Jblend that dynamically use (stretch) the full available screen estate on the WM6 VGA HTC Universal Pocket PC as well. Iâ€™ve done this STRICTLY in Portrait mode (in Landscape, there were graphics problems with Jblend). The aim of this was to find out whether the given games are able to adapt to HUGE screens like those of VGA devices. As can clearly be seen, while all dynamic stretching-capable games were able to dynamically adapt to QVGA screens (from inherently smaller screen sizes), the situation was quite different with four times bigger (VGA) screens. Note that this isnâ€™t a problem with the Universal itself but with the given titlesâ€™ inability to dynamically stretch themselves onto â€œhugeâ€ VGA screens. That is, they wonâ€™t run on other VGA Pocket PCâ€™s either, let alone Pocket PCâ€™s with even bigger screens (for example, the WVGA (800*480) Toshiba G900 or the, hopefully, forthcoming HTC Omni).
With titles that donâ€™t run (right) on the Universal, Iâ€™ve also repeated the tests on the WM5 QVGA HTC Wizard Pocket PC to find out whether it was a VGA-related problem or a generic Pocket PC incompatibility. As can clearly be seen, these were all VGA-related problems and not because of the different (Smartphone vs PPC) platform: all the (dynamically adopting) titles that had (severe) problems on VGA devices ran flawlessly on the QVGA Wizard.
Also note that Iâ€™ve only tested the Jblend compatibility of dynamically stretching titles. Games that turned out to be of â€œdumbâ€ static ones will run on any large-screen Pocket PCâ€™s â€“ confined to the boundaries of their original, hard-wired screen estate. This means all the other â€œstaticâ€, for example, 176*208 or 176*220 titles are supported and playable on VGA devices too.
4. Additional sources of information
JSR 184 (M3G) - everything you will need to know about 3D in MIDlets (mostly meant for programmers and/or advanced users)
Cross-posted to (might be worth checking out for additional info / discussions!): PPCT, AximSite, XDA-Developers, XDA-Developers - 2, FirstLoox, BrightHand, HowardForums, SPT, MoDaCo, PocketGamer.org, PocketGaming.de.
Thanks to XDA-Dev forum member niala6433 (see THIS thread), my attention was brought to a M3G-capable Jeodek version (20060421-95649). It seems to be a bit faster than Jblend and is compatible with both Pocket PCâ€™s and (at least Portrait) types of (touchscreen-less) MS Smartphones (Iâ€™ve thoroughly tested it on the QVGA HTC Vox (s710) and the 176*220 HTC Oxygen (s310)) with some disadvantages on the latter (namely, the constant visibility of the bottom bar). As itâ€™s a comparatively old and quite restricted build of Jeodek, you will ONLY want to use it to run 3D games otherwise not (sufficiently well) running under Jbed, which, currently, doesnâ€™t support 3D but support real full screen mode on both platforms, has, generally, superior speed and the best sound / music emulation. For everything else, youâ€™ll want to use the other, much more optimal solutions.
(Deep 3D on a QVGA HTC Wizard Pocket PC PE)
(Absolute Lightup Deluxe on a VGA HTC Universal Pocket PC PE)
(Absolute Lightup Deluxe on a 176*220 Smartphone; the â€œStart / Call historyâ€ softkeys are both from the Today screen)
Itâ€™s available HERE for download. Installing it is pretty simple: just unRAR jeodek.exe and jeodek.exe.0409.mui to anywhere on your handheld (storage cards preferred because, then, itâ€™ll also store the deployed MIDlets there, not taking up any built-in storage memory). Copy the \lnk\Esm3D.lnk to \Windows\Start Menu\Programs on Pocket PCâ€™s (or \Windows\Start Menu\ on a Smartphone; you can, of course, use subfolders) and, finally, import \fileassoc\ Jeodek3DStoragecard.reg into the Registry so that the file associations are right, should you want to deploy MIDlets from the outside of the MIDlet manager. (This isnâ€™t essential as Jeodek has built-in support for searching for MIDlets in the file system.) Note that youâ€™ll want to change all occurrences of â€œesm3dâ€ in the Registry import file, should your files be somewhere else than \Storage Card\esm3d. Also note that, should you want to deploy MIDlets using this file association, Jeodek must already be running.
Finally, note that you do NOT need to install an â€œofficialâ€ Jeodek / Jbed on your handheld before intsalling the hack. You can, but don't need to. Simply doing what Iâ€™ve explained suffices.
On the Smartphone, the bottom bar of the previous screen will always be visible. This means games specially designed for the given screen resolution (320*240 or 176*220) will be severely cut off, as can be seen in the following two screenshot pairs:
(VGA Pocket PC)
See the difference? Not only the softkey titles have been cut off with the Smartphone version, but even the bottom part of the text bubble. A solution to this, should you still want to play these kinds of strictly 320*240 titles on your QVGA Smartphone but can't because of the lacking screen content, is looking for a, say, 176*220 version of the same MIDlet. (And, the same stands for the case of playing on a 176*220 Smartphone. Then, your best bet is looking for a 176*208 (Nokia S60) version instead.)
Worthy for Opera Mini and the Gmail MIDlet?
While the network access works and thereâ€™re no security problems or other bugs either (unlike with Jblend), you wonâ€™t really want to use it because of the lack of full screen support as can be seen in HERE. In this respect, later Jeodek versions (no command bar at the bottom on Smartphones) were better, let alone Jbed (real fullscreen).
niala6433 has reported in his post (see thread above) that, in benchmarks, this Jeodek version produced slightly better 3D results than Jblend. This is definitely good news.
You should keep this KVM on your handheld too, should you run into a strictly M3G-dependent, working title not usable (or, not fast enough) under Jblend or TAO, the two other, M3G-compliant MIDlet managers.
- Iâ€™ve greatly enhanced the 3D compatibility chart with
the games linked from THIS post (three of them, EA Sportsâ€™ Fight Night Round 3 (V 4.6.0), THQâ€™s Juiced 2 and Falcon Mobileâ€™s Bimmer Street Racing 3D are really kick-ass)
- Iâ€™ve continued adding compatibility info with other really nice titles like Red Pyramidâ€™s Hummer Jump And Race, I-play's Fast and the Furious: Fugitive, Digital Chocolate's Mini Golf Magic (also see THIS), EAâ€™s Need for Speed Carbon (Xbox 360 review HERE), 3D Night Fever, 3D Rally Evolution, i-Playâ€™s The Fast And Furious Tokyo, 3D Tron 2.0 and Gameloft's Turbo Jet Ski 3D, just to name a few.
- what is more, now that I also have a Nokia N95, Iâ€™ve tested ALL the games on it too, mainly to see whether itâ€™s compatible with (far) more titles than the Windows Mobile KVMâ€™s (the answer is, unfortunately, no â€“ while it does run a bit more titles, itâ€™s in no way compatible with all older titles) and whether the 3D hardware acceleration support really increases speed.
Unfortunately, as it seems, the hardware 3D acceleration doesnâ€™t help the speed of emulation much. Based on the JBenchmark synthetic tests, one would expect a speed increase of about an order of magnitude. The reality, however, is different: in general, games where 3D hardware acceleration works at all run on the 330 MHz TI OMAP-based Nokia N95 only run two to three times faster than on a TI OMAP-based HTC Vox clocked at the default 200 MHz. Iâ€™ll continue doing some extensive tests to find out why the results are, indeed, below expectations and why the JBenchmark synthetic tests show much better results than the real-world games really show.
I really plan to publish the Bible this weekend or early next week. I think I will be able to do so.
In the meantime, donâ€™t forget to check out the main chart of the Bible, which has been constantly evolving in the meantime and contains a lot of tricks (for example, â€œhow can I increase the heap memory available in Jblend? How can I make Esmertecâ€™s MIDlet managers, TAO Intent and Jblend run on non-phone Pocket PCâ€™s? Why I should refrain from using the latest Gmail MIDlet (I really recommend THIS MoDaCo thread, particularly my posts there, for more info on it) "on TAO / Esmertec Jeodek, and where can I download the older, 1.1.1 version?â€ etc.) It also has all the download links and, again, as with all my other charts, answers to ALL the question you will EVER want to ask about these applications.