connection drop constantly, how to fix it?

[CHENG]

connection drop constantly, how to fix it? Otherwise refund please

[Kevin Ko]

Would you be able to give me a little more information?

1) What phone do you have?

2) What operating system is your computer running?  (eg., Windows Vista 32-bit, Mac OS X 10.6)

3) If you are running Klink's Windows software, could you make sure that you're running the latest version that I released at the very end of August?  That latest version is 1.06, and you can check by clicking on the "About" button within the PC software.  I looked up your order by your name and see that you purchased before I released the update, so you should try updating the software, as I fixed a few bugs affecting connection reliability.

To get the latest version of the PC software, you may either download it by following the setup guide within the Android app or by downloading it directly to your computer from here:

http://www.faveset.com/klink/download

Please be sure to uninstall the old version before installing the new one.  You can do that by running the uninstaller program within the "Faveset Klink" program group or under Windows Control panel.

4) Do you have a task killer on your phone?  If so, please make an exception for Klink or you will experience disconnects on regular intervals.

5) Another cause of disconnects deals with the USB connection itself.  Phone charging ports can become flaky with age (this is most common).  USB cables can also become temperamental.  Moreover, some computers (laptops especially) simply cannot supply enough power to the USB port.  Could you try one of the following:

  * Try a different USB cable, which might better fit your phone or PC port.

  * Try a different USB port on your computer, which might supply slightly more power to your phone.

6) If you have a Windows computer, do you have any Android sync software installed on your computer?  Examples might include HTC Sync or Motorola Media Link (MML)?  Klink is compatible with HTC Sync, but MML might cause problems, so you should try uninstalling MML if you do not use it.

7) Do you have similar software installed on your PC?  (Eg., EasyTether or Pdanet software?)  They all use similar mechanisms, and those two in particular are configured to start automatically when your computer starts up, and setting them to auto-connect may interrupt Klink's behavior.

We should be able to get something working, or I'll give you a refund, so let me now how it goes.

Kevin

[CHENG]

1)samsung galaxy s 2

2)windows 7 64bit

3)try it now

4)no

5)my laptop is bought 3 months ago, and it has fast charging function,
thus power supply should be ok

6)no

7)PDAnet is installed, now I try uninstalling it

[Walt]

Let me add from my own experience, that I have found

that I need to ensure that all other networks are
DISABLED.

 

Go into your Network Connections, Adapters Settings,

and make sure that all listed networks are at least

DISABLED.  Well, except for theTAP-Win32 Adapter

network used by Klink itself.

I know that for my notebook, disabling the WiFi seems to

be very important.   My guess is that if not disabled, my

notebook PC will still attempt to try to connect to some

WiFi network.   Of course it will eventually fail (that's

why I am using Klink instead), but while it is attempting

a WiFi connection, it will appear to stop using Klink's

TAP-Win32 adapter.

 

And a Klink connection that appeared to be working for

a brief while, will suddenly stop working.

[Kevin Ko]

Thanks for the pointer, Walt.  Automatic connections to a wifi hotspot is something that I've completely overlooked, and I will update the FAQ to reflect this when I reorganize it in the near future.

To add to what was suggested, if you disable your wifi adapter connection, don't forget to enable it whenever you want to use wifi again.  To enable/disable an adapter:

- Go to Windows' Network Connections window as Walt described.  (Windows Control Panel->Network Connections->Adapter Settings.  Alternatively, run "ncpa.cpl" from the Windows Start menu.)

- Right click on your computer's network adapter, and choose "Enable" to re-enable it.

I've seen a negative comment in the market from someone who had problems with wifi after configuring his computer to use Klink, and it should have been a matter of re-enabling the wifi adapter.

Kevin

[Sean McNamara]

Hi,

One thing I've found that also helps is to eliminate the operating
system as a potential factor. This can help you determine where the
problem actually lies.

The potential areas where the problem *could* reside are as follows:

-Is the problem with your Android device being incompatible with Klink?
-Is the problem that your Android device does not have a stable (or
any) Internet connection?
-Is the problem that your USB cable, USB port (on the phone or on the
computer), or other hardware is defective?
-Is the problem that your USB port on the computer is being put to
sleep by the operating system?
-Is the problem that you have some software installed on your
operating system that interferes or conflicts with Klink?
-Is the problem that you have buggy or incompatible device drivers
installed for your phone on the computer?

The last three questions are related to the operating system you have
installed on your computer. You can decisively eliminate these by
trying another operating system.

Fortunately, Klink runs natively on GNU/Linux, and you can easily
install it in a Live CD environment.

So, you could do something like this:

1. Download Ubuntu 11.04 32-bit (or 64-bit, as you please) Desktop
Live CD from http://ubuntu.com

2. Boot up Ubuntu's Live CD (which doesn't make changes to the
operating system installed on your hard drive, but allows you to try
Ubuntu)

3. Install Klink in the temporary Live environment

4. Try Klink and see if it works consistently in the Live environment

The results will be revealing either way:

(a) If you experience similar or identical connectivity issues while
running Klink under Ubuntu, then the conclusion is that your Windows
operating system and its software is NOT the problematic factor.
(b) If the connection works correctly while running Klink under
Ubuntu, then the conclusion is that your Windows operating system,
software, or drivers IS the problematic factor.

Provided that you can download the ~700MB Ubuntu ISO and burn it to a
CD using a pre-existing internet connection, or save it to your
phone's SD card and transfer it to your computer, this method should
be fairly revealing.

I don't know if Kevin has "blessed" this method as a way of isolating
problems with Klink connectivity, but in my own experience, it has
proven extremely revealing. I know for a fact that some software on my
Windows desktop is preventing Klink from working stably, because when
I run it on Linux, I can keep a steady connection for an indefinite
time (days on end). I have been unsuccessful in isolating the exact
software that's causing the problem on Windows, but I suspect it's one
of the (many!!) VPN or netfilt drivers I have installed.

I always found Windows' networking stack to be fairly uncooperative;
back when I was going to college and working at the same time, I had a
Cisco VPN for school and a Nortel VPN for work, and if I had both
installed at once, I'd get a BSOD if I tried to initiate a connection
through either one. And I experienced random stability issues like my
NIC refusing to enable/disable or obtain a DHCP address. Since Klink
seems pretty sensitive to other parts of the Windows networking stack
interfering with it, you might want to consider that any special
networking stuff you have installed (e.g. LogMeIn Hamachi, OpenVPN,
etc) will *probably* conflict with Klink (as well as every other piece
of specialized networking software out there, more than likely!). This
is just another reason to use Linux full-time, but even if you can't,
at least you can decisively determine through trying a Linux Live CD
that the problem resides with your operating system (if, indeed, that
is the problem -- I don't know for sure in your particular case).

HTH,

Sean

On Tue, Sep 6, 2011 at 7:41 AM, Walt <Wa...@early.com> wrote: