Hi guys is anyone able to getthe midlet manager within the HTC device to put on the TREO 750v. I know its made by HTC butthere is no Java Midlet Manager.
Read http://forum.xda-developers.com/showthread.php?t=272499
Device specific
Keep in mind that, atleast for the Intent Midlet Manager, they are very much device specific. You might be able to install them on similar hardware (ie. using a Wizard Midlet Mgr on an Apache) but trying to use an HTC mgr on non HTC hardware will probably not work.
I believe the reason for this is that the Midlet Managers require alot of hardware hooks to work correctly, especially when it comes to graphics and phone controls.
-Jim
I have been trying to use JSR-75 API for a J2ME application on my SPV M3100. It seems the PIM api is not on the phone :-( even though it is MDIP 2.0 and CLDC 1.1 compliant...
Firstly, it would be great if someone else could confirm this!!!! I have only found one other place on the net to verify it, so another few would help!
Secondly... has anyone managed to successfully use the JSR-75 PIM functionality on this device (or similar)? I have also installed the ibm J9 code, but this too did not give me access to the phone's contacts list, as I wanted
PHUH!
I am sure there is an easy answer to some of this and I m just missing a part of the puzzle
Many Thanks
Sanjay
If the Intent software doesn't support that JSR, then there's nothing you can do about it. The latest WM6 ROMs have a slightly newer version of MIDlet Manager, maybe it supports JSR-75. You could also try the version of Java that comes with NetFront.
Esmertec Jbed (as of version 20070622.2.1), prolly the best Midlet manager today (if you don't take the lack of 3D, direct links and proxies into account, in which Tao 11.1.x is still better), has stopped working yesterday (see for example the last few posts at http://www.ppc-welt.info/community/showthread.php?t=110939&page=3 for other user reports).
The reason for this is that it simply timed out in September - yeah, it was timebombed.
Does anyone have a Windows Mobile device sporting a newer, (still) working version? Or, does anyone want to cure the problem in some other way?
Im suprised no one has commented on this yet. For me, Opera 4 is THE way to browse the internet on a pocket pc, and no midlet manager did it better than Jbed mainly because it worked in fullscreen mode. While Tao's manager is okay, especially since the new beta 2 allows for the removal of the top and bottom red bards (pressing **), this is is a problem that needs to be addressed.
Ross
I too just ran into this problem!
megarek said:
Im suprised no one has commented on this yet. For me, Opera 4 is THE way to browse the internet on a pocket pc, and no midlet manager did it better than Jbed mainly because it worked in fullscreen mode. While Tao's manager is okay, especially since the new beta 2 allows for the removal of the top and bottom red bards (pressing **), this is is a problem that needs to be addressed.
Ross
Click to expand...
Click to collapse
BTW, speaking of Opera Mini 4 beta 2, did you read my related review at http://forum.xda-developers.com/showthread.php?t=326368 ?
I've sent the Esmertec folks a mail asking whether they would make their Midlet manager purchasable.
Hope they DO consider this so that we won't have to rely on "hacking" it off other ROM's.
it is true in my wizard when i want to open the esmerc app it closes why for me that is better than java mannager of risidoro
Opera Mini 4 Beta 2 works now ok on Tao Intent Midlet Manager (not crashing it as Beta 1 did), so not a big problem for me...
Mirek
I'm using the Esmertec Java , Joedek Build: 20070425.1.1 with no problem
hma4 said:
I'm using the Esmertec Java , Joedek Build: 20070425.1.1 with no problem
Click to expand...
Click to collapse
Esmertec Jeodek is vastly different from Esmertec Jbed. The latter is generally MUCH better. See the preview of my Midlet Bible if interested.
mirekluza said:
Opera Mini 4 Beta 2 works now ok on Tao Intent Midlet Manager (not crashing it as Beta 1 did), so not a big problem for me...
Mirek
Click to expand...
Click to collapse
Jbed offers, among other things, seamless full screen (unlike Tao Intent); this is why it'd be great to make it work / being able to legally purchase it.
londere said:
it is true in my wizard when i want to open the esmerc app it closes why for me that is better than java mannager of risidoro
Click to expand...
Click to collapse
BTW, as far as Tao Intent is concerned, check out the above-linked Opera Mini 4 thread; I've posted a lengthy excerpt on what ither Tao Intent versions there are from my forthcoming Midlet Bible.
In general, I recommend using the Russian builds over that of Risidoro, for two reasons:
1, they run off a storage card (and, therefore, store the deployed JAR files on a card too)
2, there's a vastly enhanced, "turbo" version of them.
Menneisyys said:
BTW, as far as Tao Intent is concerned, check out the above-linked Opera Mini 4 thread; I've posted a lengthy excerpt on what ither Tao Intent versions there are from my forthcoming Midlet Bible.
In general, I recommend using the Russian builds over that of Risidoro, for two reasons:
1, they run off a storage card (and, therefore, store the deployed JAR files on a card too)
2, there's a vastly enhanced, "turbo" version of them.
Click to expand...
Click to collapse
Here's the link: http://forum.xda-developers.com/showpost.php?p=1479183&postcount=13
It's right (it's his nick) posted a cab file of Jbed (but it doesn't work for me) on the bottom of this thread's first page: http://forum.xda-developers.com/showthread.php?t=327080
For those really desperate on keeping their Jbeds (like me). Just move the time/date back to something before Sept 1, 2007 when starting Jbed. It will still work.
DaVince said:
It's right (it's his nick) posted a cab file of Jbed (but it doesn't work for me) on the bottom of this thread's first page: http://forum.xda-developers.com/showthread.php?t=327080
For those really desperate on keeping their Jbeds (like me). Just move the time/date back to something before Sept 1, 2007 when starting Jbed. It will still work.
Click to expand...
Click to collapse
Yes, then, it'll work. However, Opera Mini will complain of the date being too early and, then, refuse to work. (Other MIDlets will, however, work.)
Partial Fix by its right (maker of the TNT ROMs)
Found here:
http://forum.xda-developers.com/showthread.php?p=1480902#post1480902
It's pretty much just a Joedek Build: 20070425.1.1.
I have tried the calendar reset and it works fine. Once the app is launched you can set the calendar back to proper date and jbed / opera mini continue to run. This should be the case until you close jbed / opera mini. At that point you would have to reset the calendar again. (so just leave the apps running)
I'm just curious. Is anyone else's "OLD E-Java" shortcut still working? Mine seems to still work, I had two versions the NEW-nowdefunct versoin and my OLD one. I was unable to use GMaIL with the OLD, but once I installed teh NEW version, I was now able to use Gmail on my OLD E Java. My new E JAVA doesn't work anymore , but the old one still works great with GMail and Opera Mini 4.2
Menneisyys said:
Esmertec Jeodek is vastly different from Esmertec Jbed. The latter is generally MUCH better. See the preview of my Midlet Bible if interested.
Click to expand...
Click to collapse
The Esmertec Jbed is better??
Where can i get that version, please ??
The esmertec JVM (non jbed) still works without a hitch. Only problem is no full screen. It's the esmertec Jbed JVM that does not work any longer. As to which is better I have used both and the esmertec Jbed JVM blows the regular esmertec JVM out of the water.
I see. Well hopefully we can get the Jbed version working again, without a "timebomb" as some people have said.
Right now I am using IBM's J9 Midlet Manager and it works out well with the maps application, but it's slower than JBED and for some reason it doesn't show the maps in high resolution even with the high resolution J9 version installed. JBED's only problem is that you can't connect to the serial ports of your phone and thus MGMAPS keeps reporting that there is no GPS unit available. I've had the same problem with the Intent Midlet Manager and thus would like to know if there is
a) a way to make it work with JBED or Intent.
b) a way to make IBM's J9 display high resolution.
Please no "use Mobile GMaps" answers as I have my reasons for using the midlet (offline maps, favorites, extra services). Any help on this would be greatly appreciated as I really hope this can be fixed either way.
Falk said:
a) a way to make it work with JBED or Intent.
Click to expand...
Click to collapse
Nope, they don't support serial ports.
b) a way to make IBM's J9 display high resolution.
Click to expand...
Click to collapse
This is easy and has already been explained in my MIDlet Bible (see row "Opera Mini 4 beta 2 fonts - VGA?" of the chart at http://www.winmobiletech.com/092007MidletBible/CompatibilityAndMain.html ):
Forcing J9MIDP20.EXE (or, for that matter, ANY .EXE's) doesn't help, as opposed to earlier, 5.7-series J9 versions. The only way to get high-res support is switching to Real VGA mode and using the QVGA version of J9 (NOT the VGA version - the latter won't execute your deployed MIDlets at all!). An example screenshot of this is HERE (using Large characters). Note that, as the QVGA and VGA versions can co-exist on the same machine and will use the same deployed MIDlets, this seems to be a usable solution to get hi-res support when you really need it (and, at the same time, can live without hardware softkey support - you'll need to use the on-screen menus to issue commands, unlike with the VGA version. At least this was the case on my VGA Universal.).
Thank you! Problem solved. It's really a shame that HTC didn't get around to put a decent midlet manager onto their devices. I could play with a N95 a bit recently and like your comparison chart shows it's a whole different world. I am not a heavy user, but MGMAPS sure has taught me a lesson that midlets can even be better than native Windows apps... with the right manager / device.
Trying to figure out if there was ever a real Java VM developed for WM6. I know my TyTn II has something called Esmertec Jbed but when I try to run a MIDlet it says "the MIDlet could not be instatiated: java.lang.NoClassDefFoundError"
Could someone else try this out and see if they have better luck?
http://startofentry.blogdns.org/space/MobileControl/MobileControl+Midlet
Otherwise I'm looking for recoomendations on an application to use my WM6 device as a remote over bluetooth mapped to keystrokes on my vista box.
Thanks,
Devan
devanl said:
Trying to figure out if there was ever a real Java VM developed for WM6. I know my TyTn II has something called Esmertec Jbed but when I try to run a MIDlet it says "the MIDlet could not be instatiated: java.lang.NoClassDefFoundError"
Could someone else try this out and see if they have better luck?
http://startofentry.blogdns.org/space/MobileControl/MobileControl+Midlet
Otherwise I'm looking for recoomendations on an application to use my WM6 device as a remote over bluetooth mapped to keystrokes on my vista box.
Thanks,
Devan
Click to expand...
Click to collapse
1. no BT in any J2ME's, sorry - read my MIDlet Bible.
2. check out my remote Bibles for alternates - for example, http://wiki.xda-developers.com/inde...s for Windows Mobile - the Definitive Roundup . I recommend for example PPC Tablet Remote Control Suite
Thanks for the write-up really shows a lot of options out there for media control.
I'm trying to use this to control XBMC, which primarily uses just the simple arrow keys. I got really excited by PPC Tablet Remote Control Suite but it seems that the keypresses don't work correctly in XBMC. That is to say that when I test them in another window they work, but then in XBMC I have no luck.
Then I tried jaylee.org’s Bluetooth Remote Control for Windows Mobile but I can't get the WM client to discover the server app.
Really I just need something that allows me to map controls on the display of my phone to keypresses at the PC (like the above programs)
Handy comparison table though.