Skip to main content

DUBwise on Windows Mobile with PhoneME Advanced Dual Stack

3 replies [Last post]
ligi
Offline
Joined: 2009-03-13
Points: 0

Hi all,

Background:
I'm the Devleoper of an "Open-Source" ( public source code but a special CC licence - so not OpenSource in the sense of some orthodox folks ) J2ME application called DUBwise ( http://www.mikrokopter.de/ucwiki/en/DUBwise ).
I dont like windows-mobile so my main focus is not there, but the constant requests from users forced me to look deeper in the Problem. The normal JRE on these phones don't have jsr-82 , and DUBwise is not really usefull without it - so the first solution came up, which was J9 with Bluecove - but j9 has a lot of problems ( starting with the Donwnload of it ;-)
Lately i stumbled oppon this Project - which sounds very good - I really like Open-Source solutions - and the Project seems to be alive ( not as J9 which smells allready ..-)
Now i have a Windows-Mobile Phone from one of the users ( i will never buy a windows mobile phone my selves ) for 2 weeks - and try to make DUBwise work good with PhoneME.
After some Initial Problems ( Java Console Plopping over my main window ; removing all sound stuff - cuz it crashes when it is there on PhoneME advanced, .. ) - It is working now - and its better than the J9 solution - but some Problems are left.

Questions:

- if i'm quitting the app vie notifydestroyed the app is successfully terminated and everything is OK. But when the user clickes the x top right , the app isnt shown anymore but the system is very slow ( unusable ) and a second-start isnt possible. It seems to live as zombie in the background , but i see no chance to catch this ( tere is no call to pauseApp ,... )

- Can I bundle DUBwise and PhoneME in one Zip/CAB file and put it in our SVN? Its hard for some USERS ( especially Win-Mobile users) to copy two zips in one dir on the Phone ..-)

- Is there any roadmap to have DeviceControl / MMapi / LocationAPI / FileConnection / SensorApi together with jsr-82 on WIndowsMobile? These Windows-Mobile users request primary LocationAPI because of the FollowMe feature - I can USE openlapi, but then i can only use external GPS ...

- it seems that i have not enough memory to do the scrolling Backround thing i do on the other devices, which surprised me, because very limited devices can do it, and the normal JBEND JRE on this Device can do it to - i tryed some options for cvm.exe - but its not solved yet. I will dig into this problem it a bit more - and give some more information later.

thanx in advance, and keep up the good work!
ligi

Message was edited by: ligi

Message was edited by: ligi

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davyp
Offline
Joined: 2007-01-03
Points: 0

> - if i'm quitting the app vie notifydestroyed the app is successfully terminated and everything
> is OK. But when the user clickes the x top right , the app isnt shown anymore but the
> system is very slow ( unusable ) and a second-start isnt possible. It seems to live as
> zombie in the background , but i see no chance to catch this ( tere is no call to
> pauseApp ,... )

On Windows Mobile by default you do not close an application when the user clicks on the top
right X, you just move it into the background. Nonetheless, I have also seen the VM behaving
weird with certain midlets when you close the VM this way.

> - Is there any roadmap to have DeviceControl / MMapi / LocationAPI / FileConnection /
> SensorApi together with jsr-82 on WIndowsMobile? These Windows-Mobile users request
> primary LocationAPI because of the FollowMe feature - I can USE openlapi, but then i
> can only use external GPS ...

Not really, but it would help if there are open source implementation of these JSRs that we can
reuse (like the BlueCove implementation for JSR 82).

Davy

ligi
Offline
Joined: 2009-03-13
Points: 0

> On Windows Mobile by default you do not close an
> application when the user clicks on the top
> right X, you just move it into the background.
> Nonetheless, I have also seen the VM behaving
> weird with certain midlets when you close the VM this
> way.
>
Can u think of some workaround i can do on my project to prevent this?

> Not really, but it would help if there are open
> source implementation of these JSRs that we can
> reuse (like the BlueCove implementation for JSR 82).
>
imho openlapi is one for jsr-179 . The only missing part is the bridge to WindowsMobile. The location-data feed is very capsuled - i think it only needs a few lines native windows-mobile code to make it work ( initialisation to fetch e.g. nema-steam and then feed it to openlapi) . I had the intension to try it by myselves but then i realized that the only windows i have in some VM is outdated ( win2k) and is not working with the WindowsMobile SDK - and I won't buy windows anymore ;-)

Anyone knows more about the Bundling part? Can I bundle DUBwise with PhoneME? It woult make live a lot easyer for some users ;-)

Message was edited by: ligi

davyp
Offline
Joined: 2007-01-03
Points: 0

> Can u think of some workaround i can do on my project
> to prevent this?

I think not. The native window receives a message when you close a midlet by
pushing the X button in the top right corner. The message handler in the VM
then tries to close the window, but somehow there is something keeping the
VM from terminating.

> mho openlapi is one for jsr-179 . The only missing
> part is the bridge to WindowsMobile. The

Yes, the openlapi is the only open source jsr I found too.

> Anyone knows more about the Bundling part? Can I
> bundle DUBwise with PhoneME? It woult make live a lot
> easyer for some users ;-)

IANAL, but phoneME is released under the GPLv2 license (without classpath
exception). This basically means if you distribute the VM and your application
together, the application should be GPLv2 too.

Terrence Barr clarified Sun's position on his weblog and on this forum:
http://weblogs.java.net/blog/terrencebarr/archive/2006/11/a_license_to_i...
http://forums.java.net/jive/thread.jspa?messageID=175849