What steps will reproduce the problem?
(Re)Connection Problem
1. Connect WIFI with Archos 5 internet tablet
2. Try to connect in 20m line-of-sight Proxomitry to the AP
3. Fail to Connect VNC
(The WLAN can be connected till ~60m Line of Sight. VNC fails.)
Additional Suggestion:
A Reconnection Option on the Archos 5 internet tablet that:
* Automatically tries to reconnect to the VNC-Server
(I suppose this will force the Archos 5 internet tablet to reconnect the WIFI).
* Forces the Reconnection to the VNC Server successfully over a greater
Distance to the AP.
* (Speeds up the Reconnection somehow).
What is the expected output? What do you see instead?
Somewhat Error resilient VNC Connection that survives occassional blackouts and
reconnects as fast as possible.
Switch from one AP to another on the same Channel and ssid should work too.
What version of android-vnc-viewer are you using?
Version 0.4.1 for the Archos 5 internet tablet
Which VNC server/version are you using? On which platform?
Ultra VNC Win32 Server v1.0.8.2
on
Microsoft Windows XP Proffessional 32bit Service Pack 3
Patch Level: 2010/09/21
What is the size of the desktop you are trying to access (i.e. 1024x768,
1920x1080...)?
640x480 Pixels
What device are you using?
Archos 5 internet tablet
Are you using a custom ROM? If so, which?
No.
Please provide any additional information below.
Device
* ARCHOS 5 internet tablet
Running Firmware 2.0.38 (WMDRMPD: 10.1) (Android 1.6).
If the Display turns black and the USB is not Plugged in then the
WLAN-Connection is seemingly turned off, even if I explicitly
turned off power safing in the Wireless Options.
VNC Server
* HP Workstation
Ultra VNC Win32 Server v1.0.8.2
on
Microsoft Windows XP Proffessional 32bit Service Pack 3
Patch Level: 2010/09/21
Access Point (Flawless AP takeover would be nice)
* Netgear WGR614v9
Firmware V1.2.4_16.0.15GR
Wireless Mode: "g only"
* (UNUSED) (not Plugged In)
Netgear WG1021
Firmware V5.0.3
Original issue reported on code.google.com by jmiller1...@gmail.com on 21 Sep 2010 at 1:34
Original issue reported on code.google.com by
jmiller1...@gmail.com
on 21 Sep 2010 at 1:34