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.