Latest midlet manager for WM2003SE (Loox 420) - General Topics

Hi all,
which is the latest/best version of Intent Midlet Manager, that will work on Windows Mobile 2003 Second Edition Pocket PC device, namely FSC Loox 420?
Best I found so far is v10.1.2.76 (Build 20040705) from here:
http://wiki.pocketz.ru/index.php/Запуск_мидлетов_на_Pocket_PC
which is almost three years old.
Thanks,
Petr

Related

Java (Midlet manager) on WM2005

I noticed thre is no midlet manager on the latest wm2005. Is there anywhere i can download this so i can run som java apps?
have you tried ones from 2003 ?
http://forum.xda-developers.com/vie...storder=asc&highlight=midlet+manager&start=25
http://forum.xda-developers.com/viewtopic.php?t=27168&highlight=midlet+manager

Activesync 4.5 with Pocket PC 2003

Hi
I have installed Activesync 4.5.0 (Build 5096) because it is necessary to keep my HTC S710 in sync.
I have noticed however that I have frequent and repeated program crashes when i try to sync older devices such as my i-mate JAM and HP nw6515 (to my knowledge, both run Windows Mobile 2003 SE).
Did anybody have similar experiences and managed a way around it?
Thank you and best regards
Stefan
I had no problems with my WM6 device + ipaq 4150 (wm2003).
i also have no problems syncing both my xda mini (wm2003se) and my ipaq hx 2495 (WM5) with Acivesync 4.5. both work fine. if it doesn't, i've heard of other people using Activesync 4.2 successfully as well.
He has WM6 on his s710 so 4.5 is mandatory.

StowAway / iGo driver (multiplatform) compliance tests

Upon my fellow blogger Tim Hillebrand’s report and because I’ll need to quickly enter a lot of info at MWC (and I don’t want to lug around my desktop replacement and, therefore, pretty heavy IBM Thinkpad a31p just for inputting text), I’ve installed the latest StowAway / iGo Bluetooth drivers on all my mobile devices (even non-Windows Mobile ones) to find out whether the drivers available HERE are (still) compatible with the latest operating system / firmware versions. I’ve found out the following:
Windows Mobile
Pocket PC’s (a.k.a. WM6 Classic / Professional):
HP iPAQ hx4700 (WM5 AKU 3.5.2; selecting & using the Widcomm driver, NOT the MS one); HTC Universal (WM6), Dell Axim x51v (WM5 official A12 (AKU 2.3) ROM with the MS BT stack), HTC Wizard (mfrazzz’ XDA Mobile 6 Release 5 FINAL) and the WM2003 HP iPAQ 2210: all work OK with the factory, default driver.
(Note that, as far as mfrazzz’ XDA Mobile 6 releases are concerned, version 3 was a no-go at all: it didn’t even try to connect. Pressing the Disable built-in HID support doesn’t help at all – unlike with all my other test devices or the same Wizard running Release 5.)
Smartphones (a.k.a. WM6 Standard)
HTC Vox / s710 (factory WM6 Smartphone ROM); no native driver; therefore, I tested it with the s620 / Excalibur / MteoR driver (they’re the same – actually, it seems ALL HTC Smartphones have the same drivers, unlike with WM5 and pre-WM5 Pocket PC’s): OK
HTC Oxygen / s310 with the above MS SP drivers (no native driver): the config app doesn’t even load (“Keyboard driver not functioning!”); then, after closing it, I started to get system errors about the keyboard driver DLL not responding.
Blackberry:
BB 8800 (4.2.1.101 / 2.3.0.80, T-Mobile): Works OK; program invocation hotkeys also work as expected.
Palm OS:
Palm T3: Works OK, albeit some of the program invocation shortcuts (apart from the most basic calendar/ contacts / inbox) take you to some other program, not the default one (unlike with the WM or the BB version). Otherwise, it’s OK.
Symbian:
Nokia N95 (firmware version v20): No native N95 (or any new – the latest ones are dated from 03/2007; the Palm / WinMo / BB drivers have been released a bit later; for example, the BB one in 07/2007) drivers from ThinkOutside; however, the N92 driver works just great on the N95. All the shortcuts work (as opposed to the built-in drivers). Note that the green Fn + Backspace terminates the connection (unlike on WinMo), which, then, must be re-enabled by just re-invoking the wireless keyboard applet. Also note that, unlike with Windows Mobile, Alt+keys directly enters accented characters, which are a bit more cumbersome to bring up under WinMo.
Note that the built-in Tools / Connectivity / Wlss Keyboard works without the need to install any third-party driver – apart from the complete lack of program / task switcher shortcuts and the lack of the English Pound, Japanese Yen and Euro entry.
Conclusion
All in all, the drivers are fully compatible with even the latest devices / firmware versions on all mobile platforms. On Windows Mobile, all the tested WM6 devices, Smartphones and Pocket PC’s alike, worked just great.
That is, you don’t need to be afraid of purchasing the keyboard – it WILL (almost surely) work. The only device not compatible was the HTC Oxygen / s310 low-end MS Smartphone. This doesn’t mean there aren’t other WinMo devices incompatible with the existing drivers, though - it's just that I haven't found one.

IBM J9 for smartphone (or any other KVM that works with WM5 + smartphone)

Would anyone have the link for ibm's J9 kvm?
IBM's website for weme is down. Apparently, they don't support it anymore.
I have tried Jbed and Intent and they dont wanna run on my Samsung i600.
Im just trying to run midp java with Windows Mobile 5 on a samsung i600 smartphone. Nothing fancy, just a homebrew application that used to work on my old sony ericson p800.

HTC Tytn II JBlend - Blank Screen

Hi,
I have recently bought a HTC Tytn II mobile (Windows Mobile 6.1).
It has a preinstalled JVM JBlend (build number v3.3.5, 20071228.1.1).
Does the JBlend JVM support (Location API)JSR 179 ?
When ever I try to run any midlet, the midlet hangs - shows blank Screen with Title only. ( looks like some kind of refresh problem )
Any suggestions on how to get around this?
Any upgrades avaliable for JBlend that i might need to install ?
Regards
Rahul
did you ever get to sort this out?

Categories

Resources