Thanks for the info, the client can be downloaded here:

http://www.robocommunity.com/download/file/15188-104

Thanks MrScott

the "Video" is a few to several frames per second, on an evdo1x (3g - sprint) connection. Its enough to easily control the bot. However, the real limit at this point is not bandwidth per-se, At present I am just requesting a new jpeg image one by one, so the limiting factor in frame rate is really the http request-response delay between pictures. When I get time I'll figure out how to decode the mjpeg stream which should improve the video as this eliminates the request for each image.


Blackberry has 2 main network paths that I know of ... BES and DirectTCP, both use the carriers underlying technology, 3G(evdo,umts) or EDGE,GPRS etc.

BES is usually if your BB is through a company and connected to exchange. This works as its how I am connected.
Without BES, you are supposed to use a connection url (under settings) of "your_Rovio_address:your_rovio_port;deviceside=true"
This also requires your APN is set up for the blackberry, this is under Options-Advanced->TCP, Cant help on the APN settings as this is carrier and plan dependent - but its most likely already set.
hope that helps

Thats all I had to change int the JAD to make it install (the JAD is created by the dev environment). The 406 error sounds like an issue between the webserver and the browser, maybey some permissions or config ont he webserver side ?? I am by no means an expert on the COD install process, so if there are any changes problems I am happy to correct. I have used the following process with an SD card for other apps, see link maybey that helps.

http://supportforums.blackberry.com/rim/board/message?board.id=java_dev&messa...

UPDATE: I have working code for mjpeg. but I'm chasing down some weird behavior with Blackberry API's namely that..

1) opening an MJPEG stream requires (eg only works) via direct TCP (deviceside=true qualifier set in the url)
2) opening a JPEG stream requires MDS (eg deviceside=false or nothing set in the url).
3) I rewrote using a direct socket connection and manually processing http this gets further

I am pretty certain its a BB APIs not liking something coming back from Rovio, even the HTTP demo code supplied by BB fails exactly the same way. I dont have another mjpeg stream to test against

If anyone has any advice or could offer some I'd appreciate it.

addertay, thanks for testing, I took a look to see what could be happening found the problem, I'm inserting the deviceside=true in the wrong place...just silly stupid on my part. Dont know what I was thinking, I need to add a separate field for the "qualifiers" on the config screen so I can append it to the end of the url. This will be fixed soon. Sorry for the confusion.

Hello, and sorry for the late reply, I've been swamped with wok stuff.
For the current version, the deviceside parameter should not be set - for BES.
I've run into significant issues with the BB API's for networking, when it comes to processing streams. I think the user-API's were designed for small transactons, nt continuous long ones.
In any event, I did create another version that may work with non-bes. It works on the mjpeg stream, but it has rather high latency.
I will also post the source code, maybey someone can help,figure out what i'm doing wrong.