matejcik

that explains it. as northernpenguin said above, you can't connect to bluetooth, internal nor serial GPS in Jbed. what you need is a tcp redirector, you might try for example this one: http://linuxtechs.net/kruch/tb/forum/viewtopic.php?t=1331 (note that i don't own a PPC, i never tried this, so i can't help you set it up. but i think that you can find all answers in that forum) with that, you will set up a redirection from your COM port to a local TCP/IP socket, and then input the TCP port number in openwig. then it should work :e)

OpenWIG has that ;e)

wait a minute here. you say that your virtual COM port is number 8, right? this seems that you set the local socket port to 8, instead of the serial port. yes, the wording is a bit clumsy in that regard :e) what the application should do is this: 1. when opening the options, you have an options list with the following options: --- ( ) Manual (x) Serial port ( ) TCP Socket --- below that should be a text: Port: /something/ Choose... 2. switch to "TCP Socket", the text below should change: Local port: 8 Choose... 3. click Choose, a text window input should come up and ask you to enter "Port number" 4. cancel the window, switch back to Serial port. make sure that the text changes, then click Choose. a window labeled "Serial ports" should come up and contain a list of your COM ports 5. select one of the ports from the list, make sure that the text is updated 6. if everything that i wrote here is true, go to GPS screen and try to connect again, the error should go away. 7. if something that i wrote is not true, which i'm afraid is the case, tell me how far you got and what happened :e) thanks

hi folks, if any of you has any experience in developing J2ME applications on BlackBerry, please come see my thread about OpenWIG and help me make it work on blackberries ;e)

Just as i thought. In that case, I'm sorry, but it won't work on a blackberry, not on your version anyway. (i have this nasty habit of using builtin interfaces and inheritance together, and either the translator or the device can't cope.) But as i said before, if you know about anybody with java-on-blackberry experience who's willing to help, let them contact me and we'll see what we can do.

interesting indeed. i'll try to get me a HTC device and try it myself this actually makes at least some sense - did you unset and re-set to "serial" connection? try switching to Manual, going to GPS screen and back and then setting Serial again. Maybe, but that won't work from the midlet - Jbed doesn't implement the necessary APIs. This new version can detect that and doesn't show the bluetooth option when it can't be used anyway. If your GPS is bluetooth, you need to set up a virtual COM port for it and connect through that. (the fact that it doesn't work is another matter, though ;e) but i hope that i can fix it)

both of you please try this newest variant: http://openwig.googlecode.com/files/openwig-0.3.07c.zip Geinponem: i'm not sure that it will solve your problem, because the error message you gave me should not happen ;e) are you sure that it says "comm,null;baudrate=9600" and not "comm:null;baudrate=9600" ? i discovered a bug with saving the connection method of choice, so please go to Options, choose a different method, save, then return and select serial port (and port number) again - but it's just a blind try Keith Watson: this version creates a completely separate subclass of PlayerListener, so there should be no way "metatable" sneaks in. but it is possible that there will be similar errors (Runnable.metatable comes to mind). i'm googling around and it seems that some people have similar problems ... not sure how to fix it yet, only "success story" i found was when the guy in question had mismatched Blackberry JDE and OS versions

hm, this looks as if the blackberry converter messed it up. it would be interesting if somebody could compile it directly with the BlackBerry JDE - i have no experience with it and it's windows-only anyway. please try this version: http://openwig.googlecode.com/files/openwig-0.3.07b.zip it should work around this problem - but i'm not sure that it will get very far if there is somebody who has experience developing for blackberries, please contact me and we'll work it out together ;e)

hi, did you specify which serial port to use in Options? there's a "choose" button below the gps type selection, you have to choose a port before attempting to connect. also, i'm curious, which version of Jbed did you use? i had somebody try it before on Kaiser, and there was no option of selecting the serial connection.

if by "OTA link" you mean "downloadable directly to phone", then here's one: http://openwig.googlecode.com/files/OpenWIG.jad that's strange. please try this version: http://openwig.googlecode.com/files/openwig-0.3.07a.zip it's not obfuscated, so we might learn what exactly isn't found.

Well, this was back in March. Any hope we'll see it soon? now that my thread is at least "approved by inaction", i guess i can advertise a bit: check out my project OpenWIG on http://forums.Groundspeak.com/GC/index.php?showtopic=207358 there seem to be a bunch of symbian-related bugs, but the sooner somebody tests and finds them, the sooner i can fix them.

Yes, it was talked about, and no, this is not a question. This, in fact, is an information. For some time now, i've been developing this little project i call OpenWIG. It is a J2ME application (midlet, if you wish) that you can run on your java-enabled cellphone. (and a variety of other devices that support J2ME) It plays Wherigo cartridges and it turns out to be already quite usable. Not yet as cool as the official player, and it can't play every cartridge properly ... but it can play many of them! ;e) you can download it here. As of now, the biggest shortcoming (and one that won't be fixed very soon) is that it can't save progress. On the other hand, it does not crash even remotely as much as any of the official players a little list of anticipated questions, complaints etc.: - It doesn't work on my phone! Too bad, i guess. Is your phone new enough? Check the specs: you need MIDP 2.0, CLDC 1.1 and support for JSR-75. Most phones in the last three years have all that, though. Then, many of you american guys have weird operator-locked phones that won't work with any app that's not bought with cold hard cash from the operator. I can't help there - get your phone unlocked. And if you are sure that your phone is OK, then perhaps the app is broken. Report a bug and i'll see what i can do to fix it. - The thing keeps asking me about reading user data! Yes, it does that. I'm sorry, but to fix this, i'd need a Java security certificate. Security certificates are expensive and i'm not buying one. So you'll have to be patient and always say Yes. It should not ask anything during the game itself, if it does, please tell me. - Cool, it seems to work, but ... which cartridge do i use? There is no "openwig" download available. We have best results for PocketPC cartridges, as they seem to have the most features. - It won't play my cartridge! Well, too bad. It isn't official and it isn't perfect. If you want it to play your cartridge, you need to tell me about the problem (and, if possible, provide a source code for the cartridge). - The images won't fit on my screen! Your phone doesn't scale images automatically. All's not lost, though. Take your downloaded cartridge file and submit it to Wherigo Cartridge Optimizer[1]. Select your screen resolution and download an optimized cartridge with images that fit your phone perfectly. Oh, and OpenWIG doesn't play sound yet. But it will in the upcoming version ;e) ([1] http://ati.land.cz/gps/Wherigo/ but with lowercase W. the forum won't let me write Wherigo uncapitalized...) - Great, another player, completely new device to worry about, good job smartass Um, no, you got it all wrong. See, with the official players, if you hit a bug, there isn't really that much to do about it, except try to work around it. On the other hand, my project is following something that already works. I can't expect to be successful if it works differently. So if you say "hey there, matejcik, when i do this and that, your java thingy acts all funky, when it should instead act sanely, cos that's what the official player does", then you have a pretty good chance that i will fix it and release a new version soon. (then again, i can say that it's hard to fix and release a new version much later, but oh well. at least you had a chance) there's an issue tracker for bugs you find, at http://code.google.com/p/openwig/issues/list . Don't worry about those foreign language bugs already in there ;e)