Open GoogleCodeExporter opened 8 years ago
[deleted comment]
Could you test the newer versions? I changed the way reconnect works.
Original comment by kenny@the-b.org
on 13 Mar 2010 at 8:48
Had a chance to give this some real-world testing driving through dead zones.
At
loss of signal, got a nice "Connection lost" warning. Everything then stayed
quiet
until I was getting back into signal areas again. At that point, connectbot
tried
to reconnect, but then failed on its first attempt and hung. The way it hung
was
pretty much identically to the way it hangs on any initial connect attempt if
the
connection is flaky. Had to manually close session and reopen to get going
again.
Original comment by lauren4...@gmail.com
on 28 Mar 2010 at 8:01
I have similar behavior with latest version of connectbot on DInc (latest
original Verizon 2.2 firmware , rooted).
For example, going down to subway (where mobile network is not available) and
then out, ConnectBot doesn't try to reconnect anymore when out of subway.
Connection is lost for good, unless I try to reconnect manually.
In cases where provider chooses to give your phone a "private" IP address (like
Verizon and most others), using ConnectBot to establish and maintain a VPN
tunnel with your chosen server (with reverse port forwarding) is one of the
only universal ways of connecting remotely to your phone. But only if a tunnel
is stable and reliable, i.e. can reconnect automatically when network
conditions change.
Great app! Just need to make it stable for background 24x7 service-like
operation.
Original comment by dmitry.l...@gmail.com
on 29 May 2011 at 4:21
Original issue reported on code.google.com by
lauren4...@gmail.com
on 4 Mar 2010 at 5:43