Device Negotiation Error - Ensure that Klink has been started on the device

[ToWin]

Hello,

I purchased the Klink license through the Android Market. I have
heard great things about the app and look forward to using it. I'm
using Windows 7, I've installed Klink for 64 bit on my computer and
installed the app on the phone. I keep getting Device Negotiation
Error - Ensure that Klink has been started on the device when I press
the start button in program window on the computer. I did make sure
the start button was pressed on the phone portion of this connection.
Could you provide some assistance? Thank you in advance.

[Kevin Ko]

Hi,

We'll get this working, or I'll give you a refund.  Could you tell me which phone model you have?

Also, do you by chance have a task killer (eg., Advanced Task Killer) running on your phone?  The device negotiation error occurs when Klink is not running on the phone.  What's possible is that a task killer might be terminating Klink on your phone soon after you press the "Start" button, which would prevent your PC from connecting successfully.  If you do have a task killer, please make an exception for Klink.

One other possibility is your phone's USB connection being disrupted (bad cable) just after you choose to connect, but this is unlikely to be the case since the error happens consistently.  With a bad cable, Windows and Klink's PC software would have problems even detecting your phone...

If the above does not apply, would you be able to provide me with some additional logging information?  This will take about 3 minutes of your time:

- Download the free utility "aLogCat" from the Android Market to your phone:

https://market.android.com/details?id=org.jtb.alogcat&feature=search_result

- Run Klink on both your phone and PC until you get the device negotiation error.

- Run aLogCat on your phone.

- Press the "Menu" key and choose "Share".  Could you then email me the logfile directly?  It will tell me if Klink is getting stopped while running in the background.

Kevin

[Al]

Hello, I'm having a similar issue now. I have no task killers and it
just stops running on the phone, usb cables are good, tried other
programs that tether no problem. hmmm I will get you a log file and
report back

On Oct 11, 12:25 pm, Kevin Ko <ke...@faveset.com> wrote:
> Hi,
>
> We'll get this working, or I'll give you a refund.  Could you tell me which
> phone model you have?
>
> Also, do you by chance have a task killer (eg., Advanced Task Killer)
> running on your phone?  The device negotiation error occurs when Klink is
> not running on the phone.  What's possible is that a task killer might be
> terminating Klink on your phone soon after you press the "Start" button,
> which would prevent your PC from connecting successfully.  If you do have a
> task killer, please make an exception for Klink.
>
> One other possibility is your phone's USB connection being disrupted (bad
> cable) just after you choose to connect, but this is unlikely to be the case
> since the error happens consistently.  With a bad cable, Windows and Klink's
> PC software would have problems even detecting your phone...
>
> If the above does not apply, would you be able to provide me with some
> additional logging information?  This will take about 3 minutes of your
> time:
>
> - Download the free utility "aLogCat" from the Android Market to your phone:
>

> https://market.android.com/details?id=org.jtb.alogcat&feature=search_...

[Al]

Hello again ...I sent you a log file. Hopefully that helps us out!!!!!

On Oct 11, 12:25 pm, Kevin Ko <ke...@faveset.com> wrote:

> Hi,
>
> We'll get this working, or I'll give you a refund.  Could you tell me which
> phone model you have?
>
> Also, do you by chance have a task killer (eg., Advanced Task Killer)
> running on your phone?  The device negotiation error occurs when Klink is
> not running on the phone.  What's possible is that a task killer might be
> terminating Klink on your phone soon after you press the "Start" button,
> which would prevent your PC from connecting successfully.  If you do have a
> task killer, please make an exception for Klink.
>
> One other possibility is your phone's USB connection being disrupted (bad
> cable) just after you choose to connect, but this is unlikely to be the case
> since the error happens consistently.  With a bad cable, Windows and Klink's
> PC software would have problems even detecting your phone...
>
> If the above does not apply, would you be able to provide me with some
> additional logging information?  This will take about 3 minutes of your
> time:
>
> - Download the free utility "aLogCat" from the Android Market to your phone:
>

> https://market.android.com/details?id=org.jtb.alogcat&feature=search_...

[Kevin Ko]

Hi, Al.

I just got your alogcat output.

Could you press the "Menu" key within Klink's Android app and choose "Exit"?  This will cleanly exit everything.  Then, run the app as before.

Just before this started happening, were you using the connection heavily?  You previously asked about bittorrent, so I wonder if you were using that.  While Klink can handle thousands of connections; most stock phones implement a hard limit of about 1000 simultaneous connections per app.  Realistically (after factoring in UDP traffic for name lookups), this means that you can have a few hundred connections.  If you ever torrent, could you limit the number of peers to about 60?  Most bittorrent clients keeps connections open for awhile, so the actual number of simultaneous connections will be a multiple of 60, which can come close to the per-process limit once name lookups are factored in, especially if you browse the web concurrently with Chrome, which will happily initiate another 100 simultaneous connections and name lookups.  If your torrent client has an option to turn off DNS lookups of peers, please do so, as you'll find that you can double the number of connected peers.

Does cleanly restarting Klink take care of things?

Kevin

[Al]

I will try again tonight..I was successful after many restarts of the
phone app. please note that it become increasingly unstable..about
every 15-20 minutes it stopped

[Kevin Ko]

Hi, Al.

I never heard back from you.  Did your problems end up reappearing?  Also, were you doing something heavy like bittorrent, or did it happen normally?

If torrenting, you will have to limit the total connection count to about 100 or you'll likely run into problems because of how bittorrent works, depending on your phone.  (Again, torrents will end up using multiples of the 100 connection limit in bursts, and there is a hard-coded per-app limit on non-rooted phones of about 1000, though it varies from phone model to phone model.)

Finally, if you're experiencing perceived connection drops, make sure that your computer's wifi adapter is not automatically searching for nearby hotspots.  Automatic connects are the default under Windows and Mac, and any subsequent connections will usually take precedence over Klink.  This can be a bad thing and lead to lost connectivity if any of those open hotspots don't actually connect to the internet (poor signal, etc.).  The easiest solution is just to turn off your wifi adapter when using Klink.  You can also turn off the automatic search mode through the wifi indicator on Windows or Mac.

I should be posting an updated version of the Windows software next week that will take care of the wifi issue so that any automatic and subsequent wifi connections will not take priority over Klink's own connection.

Kevin