[Nexus One Themes and Apps] BootsSiR:
I've started to investigate the connection losses a bit and from doing a continuous ping of my device I can see some points when the connection dies (once being when the screen is turned off, and others seem to happen randomly. I need to build a bit more robustness into the connection to cleanly handle these connection drops.

I had implemented an auto reconnect but I'm going to yank the code out and rewrite it because I'm not happy with it.

I wouldn't mind if a few of you could do the following command with your device on WiFi and post the results. While it's running, turn your screen on and off, let the device go idle, etc and see if you see the same timeouts I do.

C:\Users\Steve>ping -t 10.0.0.201

Pinging 10.0.0.201 with 32 bytes of data:
Reply from 10.0.0.201: bytes=32 time=2ms TTL=64
Reply from 10.0.0.201: bytes=32 time=1ms TTL=64
Reply from 10.0.0.201: bytes=32 time=1ms TTL=64
Reply from 10.0.0.201: bytes=32 time=178ms TTL=64
Request timed out.
Reply from 10.0.0.201: bytes=32 time=329ms TTL=64
Reply from 10.0.0.201: bytes=32 time=286ms TTL=64
Reply from 10.0.0.201: bytes=32 time=210ms TTL=64
Reply from 10.0.0.201: bytes=32 time=131ms TTL=64
Reply from 10.0.0.201: bytes=32 time=254ms TTL=64
Reply from 10.0.0.201: bytes=32 time=175ms TTL=64
Reply from 10.0.0.201: bytes=32 time=200ms TTL=64
Reply from 10.0.0.201: bytes=32 time=119ms TTL=64
Reply from 10.0.0.201: bytes=32 time=149ms TTL=64
Reply from 10.0.0.201: bytes=32 time=273ms TTL=64
Reply from 10.0.0.201: bytes=32 time=89ms TTL=64
Reply from 10.0.0.201: bytes=32 time=318ms TTL=64
Reply from 10.0.0.201: bytes=32 time=238ms TTL=64
Reply from 10.0.0.201: bytes=32 time=507ms TTL=64
Reply from 10.0.0.201: bytes=32 time=77ms TTL=64
Reply from 10.0.0.201: bytes=32 time=367ms TTL=64
Reply from 10.0.0.201: bytes=32 time=229ms TTL=64
Reply from 10.0.0.201: bytes=32 time=150ms TTL=64
Reply from 10.0.0.201: bytes=32 time=68ms TTL=64
Request timed out.
Reply from 10.0.0.201: bytes=32 time=292ms TTL=64
Reply from 10.0.0.201: bytes=32 time=270ms TTL=64
Reply from 10.0.0.201: bytes=32 time=197ms TTL=64
Reply from 10.0.0.201: bytes=32 time=113ms TTL=64
Reply from 10.0.0.201: bytes=32 time=395ms TTL=64
Reply from 10.0.0.201: bytes=32 time=57ms TTL=64
Reply from 10.0.0.201: bytes=32 time=83ms TTL=64
Reply from 10.0.0.201: bytes=32 time=414ms TTL=64
Reply from 10.0.0.201: bytes=32 time=26ms TTL=64
Reply from 10.0.0.201: bytes=32 time=261ms TTL=64
Reply from 10.0.0.201: bytes=32 time=382ms TTL=64
Reply from 10.0.0.201: bytes=32 time=302ms TTL=64
Reply from 10.0.0.201: bytes=32 time=572ms TTL=64
Reply from 10.0.0.201: bytes=32 time=145ms TTL=64
Reply from 10.0.0.201: bytes=32 time=63ms TTL=64
Reply from 10.0.0.201: bytes=32 time=333ms TTL=64
Reply from 10.0.0.201: bytes=32 time=7ms TTL=64
Reply from 10.0.0.201: bytes=32 time=278ms TTL=64
Reply from 10.0.0.201: bytes=32 time=156ms TTL=64
Reply from 10.0.0.201: bytes=32 time=424ms TTL=64
Reply from 10.0.0.201: bytes=32 time=306ms TTL=64
Reply from 10.0.0.201: bytes=32 time=19ms TTL=64

Ping statistics for 10.0.0.201:
Packets: Sent = 47, Received = 45, Lost = 2 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 572ms, Average = 209ms
Control-C
^C
C:\Users\Steve>