Nokia phones should work well-ish with the next release, and (as long as you do not do too much in close succession) will not lead to an Out Of Memory Error. It can still get confused if the server sends it data it is not expecting, or if the server combines updates, which is allowed in the specs. Unless Nokia release an update for its mobile phones, I do not see this improving much. Ill continue to tweak it in hope of getting a smother ride for Nokia users.
It also will include a Nokia Compatibility Mode (defaults to On). Users should notice quite an improvement (if not using a Nokia phone, or a phone which has the same problems as Nokia phones) when this option is disabled, and J2ME VNC will not get confused.
I would like my next release to be the final Alpha, as it will be usable product on all J2ME enabled phones with Socket support. Actually it will be more of a Beta RC, if it works I shall release a version with the debug code removed (will increase the amount of time before Out Of Memory errors, and make it faster). If however it does not work reasonable well then Ill stay in Alpha until I have a workable version.
_The Big Question_
This leads to the next Big Question. What next. Id like feed back on this so please chime in. I have the follow ideas on what to do...
1) HTTP Support.
This would take form in the way of a HTTP based VNC proxy, and thus would require the user to install a web application between the VNC server and the phone (I would be able to provide a free proxy for small sessions only, but keep in mind the security implementations of using such a thing.) This would also have a few nice side effects.
Nokia phones would work well with it.
Security, the VNC server would not have to be globally accessible, and you could use HTTPS.
To keep the file size down, I intend on having two distributions, HTTP and Normal, both using the same interface, the only difference between the two would be
SSL support would be very nice. I dont yet know how to make it work, but Id like to have it.
3) New Interface
The current one is quite hard to use. Suggestions welcome.
The progress of j2mevnc is really impressive. So with this pace it is going to become really cool thing soon.
1. Sure, HTTP for me is the thing #1. I realize how shitty sockets are on my Nokia - so it would be nice to straighten things up.
2. What about extending the functionality? TightVNC is going to include fiile transfer into their product - would it be possible to do the same thing here? Also, they (optionally) use JPEG compression for traffic economy - can j2mevnc play around this as well (because both GPRS and Bluetooth are not exactly too fast media)?
TinyVNC support is defenly on the cards.
File Transport is unlikly. Most phones don't support files, and if they do the internal drive would be too small for any real use (the 7650 is ~64MB I think, but most phones are under 1MB). Using other features in TinyVNC (local cursor, maybe sending JPEGs etc) will make it in. I am however tring to keep the application under 32K, and it is currently (un-optimized) 31K ;)
Sorry, TinyVNC should be TightVNC.
Just been given an unusual request by my boss, and stumbled across this VNC client...
He wants me to do the reverse, present a mobile phone display on a PC.
So how about a VNC /server/ for a mobile phone?
Why do you need this?
Could be possable using Symbian APIs ( http://www.symbian.com/ ), but it is not using Java.
It is however out side the scope of this project.
Hi Nobody/ Anybody,
I have seen some product in Nokia which has exact same functionality as what you wanted. I do not know if this product is available for public distribution somewhere, but may be you can check if it is available on Nokia software market website http://www.softwaremarket.nokia.com.
By: Nobody/Anonymous - nobody
RE: Status Report: Nokia Phones and The Future
I would like to see VNC on my Blackberry 7280, which is a J2ME device.
The advantages of the Blackberry are listed in a post halfway down this thread:
Can VNC be brought to the Blackberry 7280? (BTW, I do have MDS access via Mailstreet hosting...)
It should work fine on the BB.
I shall check again when I get back from work (not BB emu here), but with the latest release you should have no problems downloading the JAD files from the main page.
I have tried version 3.0.4 on my nokia 6230, I must said it is a lot better than the old version. It is strange that I must turn off the NCM, if not it won't work. Isn't NCM is made speciall for the program to work on Nokia phone?
TightVNC support is definitly a need in order to have faster update. Anyway, keep up the good work! Thanks.
NCM is only for Nokia phones with crappy Socket implementations, if the 6230 works without it, then I guess Nokia have fixed the problem with this phone (it should still work with NCM enabled, just not as well).
You mentioned that the program works on the blackberry but in fact the screen works but the primary and secondary mouse fire keys don't work. When can I hope to get a fix for that??
As and when I get the time to fix it.
i only got the text box telling me that i`m conecting, connecting and open and running.. and the last letters are RUN INIT !?!
After that there is nothing.... at least if i not wait longer than 10 min ?
I got a Nokia 6230..
I try do change the password, but nothing happens, so it seems like the phone have not connected to my PC...
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.