UPDATE (some 5 hours later): I’ve also tested the latest Jbed version, JRebeiro_EsmertecJbed_20071119.3.1. I’ve already mentioned it HERE but, then, I didn’t have the time to thoroughly test it.
The bad
- not possible to install it to a storage card by default
- display problems on MS Smartphones (as with all the other Esmertec Jbed versions – except for the M3G-specific, hacked 4pda.ru version). Note that, again, this doesn’t have any effect on how Opera Mini 4 or games work; only the main MIDlet manager MIDlet lists and, for example, the Gmail MIDlet are affected
The good
- the latest version; reported to be very fast
- M3G compliant
- has sound (as with Cloudyfa’s version)!!
All in all, highly recommended for gamers.
It’s available HERE (mirrored HERE so that you don’t need to search / register).
Also see THIS German language Pocket Players Reloaded article on the games it’s compatible with.
1.THIS and THIS posts in THIS thread (from an iPAQ 210 user) might be of interest to, for example, Opera Mini users.
2. I’ve published a review of SHAPE Services’ TSMobiles: Terminal Service Client for Mobiles (cross-posts: AximSite, XDA-Developers - 1, BrightHand, HowardForums, MoDaCo), a Java-based remote desktop accessor, RDP-compliant client. It works pretty well on Windows Mobile, both Pocket PC’s and MS Smartphones, under (the latest, 3.1 version of) Jbed, the best MIDlet manager for Windows Mobile. (Incidentally, this also shows what’s Java is capable of – this MIDlet is REALLY nice and fast, even by Windows Mobile standards!)
UPDATE (04/05/2008):
In the meantime, I’ve tested two versions of the latest, 3.1 version of Jbed and found out the following (starting with, currently, the latest and, unless you MUST install it on your storage card without any manual hacking, most recommended version):
1. Jbed Java 3.1 20080222 (available HERE; mirrored HERE for your convenience): this version runs flawlessly under WM5 (not only WM6 – note that some older versions of 3.1 are NOT WM5-compliant). It supports 3D (tested with Need for speed carbon and Night Fever; neither of them run under the non-3D-capable Cloudyfa 2.1), (as usual, excellent) sound. It can’t be directly installed onto a storage card, however. (As with some older versions, it’s possible it can be hacked there, though, with some manual file copying and registry / start menu link rewriting – I haven’t tested this.)
2. I’ve also thoroughly tested JBed_20071119.3.1_3dMod_HeapSizeFix_v2_wm6(lovetz1) linked from THIS MoDaCo thread. As a plus, it can be directly installed on a storage card, as opposed to the version above. It, however, doesn’t support sound at all. Otherwise, it seems it’s pretty much the same as the version above – except for WM5-compliance: I haven’t tested the WM5-compliant subversion. Again, I’d stick with the 20080222 (the first) version unless you really need every single byte in your built-in storage.
3. Note that neither version was able to run the s60v3 (Nokia) version of Command & Conquer 3: Tiberium Wars, the latest-and-greatest real-time strategy from EA Mobile – upon loading the mission (and displaying the progress bar), it just locks up. (Needless to say, it’s working flawlessly on the Nokia N95 v20). It seems no Jbed version is compatible with this excellent game – I’ve tested with several. This means the extended, “hacked” heap didn’t help with particular game. It might help with others, though.
4. Also note that the first beta of Opera Mini 4.1 has been released in the meantime. It simply ROCKS and is a must. See THIS for a complete review & tutorial.
UPDATE (04/11/2008): XDA-Devs forum member Ebenezerhas released a version of Jbed 20080222 3.1 that can be directly installed to a storage card. It also supports sound and M3G (3D). Make sure you switch to this version if you prefer keeping your MIDlet manager and deployed MIDlets on your storage card. I've also got rid of the old, 2.1 Cloudyfa version (along with all the previously-mirrored and, now, outdated Jbed versions - this is why the old mirror links will no longer live) and made the new version of Jbed available HERE for direct download.
UPDATE (04/12/2008): Note that the just-recommended Ebenezer Jbed 3.1 doesn't create a link in Start Menu (not even when installed to the built-in storage); therefore, you'll need to manually create it. It's pretty simple: either copy (after, if you install Jbed on a storage card, changing "\Windows\jbed.exe" to "\Storage Card\Esmertec Java\jbed.exe" in it; if you're afraid of manually editing the file, I've created it for you; just right-click THIS and select Download / Save) to \Windows\Start Menu\Programs (on a touchscreen-enabled Pocket PC) or \Windows\Start Menu (on a touchscreen-less MS Smartphone). On Pocket PC's, you can also go the usual way: go to the home directory (for example, \Storage Card\Esmertec Java), highlight jbed.exe, select Copy; go to the target directory (\Windows\Start Menu\Programs or any subdirectory of it) and select Edit / Paste Shortcut. Then, you may still want to rename the just-created .lnk file so that you can remove the "Shortcut to" prefix.
Hi,
...did you notice that the free navigation application nav4all at http://www.nav4all.com is also using a midlet manager for smartphones? It supplies Fullscreen, Bluetooth and Cleartype support but is unfortunately tightly linked to this single application. Do you know any way to get this decoupled? The midlet manager is called AIMSmidp.exe and I could not find any reference around the internet for this one. I did some primitve renaming of files to trick it - but no success.
UPDATE (04/14/2008): XDA-Devs forum member defcomg has just released a version of Jbed 3.1 not suffering from the Start menu link creation bug any more. It's currently available HERE and will be avalable on my DB back-end in a few hours. Therefore, if you still haven't installed Jbed 3.1, make sure you prefer this version to the others linked to above.
UPDATE (04/16/2008): In the meantime, the last-recommended defcomg version has turned out to be buggy; for example, if you install it on a storage card, it’ll still store the deployed files in \Windows\appdb - that is, the main storage. Furthermore, some people have reported (see for example THIS and THIS) it to be incompatible with Opera Mini 4.1 beta (it worked on my Wizard tho) – which isn’t the case with the previously-recommended Ebenezer version. Finally, it can’t be installed on a storage card NOT named Storage Card – that is, on a, say, non-English device or into an alternate Flash memory like “Storage” or “Flash disk” in the Ranju WM6.1 version v7.6 for the HTC Universal.
Therefore, you’ll want to switch back to the Ebenezer version available HERE (requires registration at XDA-Devs) or HERE (direct download from my DB back-end) if you encounter these problems and want to keep your deployed MIDlets on your card. Again, note that you will need to manually create (copy) a shortcut to Jbed.exe with this version – this is the only problem with it. It runs (the signed version of) Opera Mini 4.1b (and, of course, all the other compatible MIDlets, including games) just great.
1. Unfortunately, it seems none of the Jbed 3.1 versions are able to run Opera Mini 4.1 beta on touchscreen-less MS Smartphones (but NOT on Pocket PC's!!!) if you switch to other apps (for example, the home screen) and, then, back, you will no longer be able to control Opera Mini. I've tested this on my WM5 s310 / Oxygen (major problems) and, with HTC's recently-released ROM upgrade, upgraded WM6 s710 / Vox (not that frequent problems but still annoying). At XDA-Devs, other people have also reported the same problem with their Smartphones.
If you do encounter problems like this and can't refrain from task switching, you'll want to downgrade to the Cloudyfa 2.1 version available HERE. Note that it can safely co-exist with 3.1 if you've installed the latter in another directory (for example, on a storage card or a flash disk) - then, it's only the file associations that will be needed to, say, quickly switched if you don't want to manually deploy a MIDlet from inside the GUI of the specific MIDlet manager. That is, you don't need to delete Jbed 3.1 if you plan to keep it for example for M3G gaming.
Note that touchscreen-equipped Pocket PC's do NOT suffer from this problem!
2.Ebenezer has released a fixed version of his Jbed 3.1 MIDlet manager HERE. Now, it does create a link file in Start Menu / Programs on both Pocket PC's and MS Smartphones. It also installs to any target media (not only "Storage Card"s) without problems. Note one caveat, though: the link file (the one the installer puts in the Start menu) has \Storage Card wired in, which doesn't work with any storage card (or flash disk) named other than "Storage Card". Hope this is fixed some time; in the meantime, just manually edit the link file to have the correct path.
2. badbob001, who has just released a new, 0.09b version of his StartOperaMini by adding the exclude list feature (and a LOT of other goodies – make sur eyou check out the dedicated XDA-Devs thread!), has found out a pretty easy-to-use fix for the above-mentioned Jbed 3.1 resume bug: if you have Direct Address Input disabled (it’s enabled by default), press #1 to open the Enter Address window. Then cancel out and the Opera Mini screen should be responsive again. (BTW, this might work with other dialogs requiring manual input – I don’t know, haven’t tested the latter.) Incidentally, he has also found out the problem is surely a Jbed-related issue because the Gmail MIDlet is also affected by it. Let me cite him: “One thing you may want to investigate is Jbed's background running option. If I run jbed, turn on background running, then launch opera mini, the problem seems to not occur with my limited testing. Since I prefer to directly launch opera mini, it would also be nice to have a way to enable background running by default.
If enabling background running really fixes the issue, then I guess it's a bug with jbed 3.1 restoring itself from its own suspend mode.”
Linear Mode
LinkBacks (?)
