Bug 4872 - Loses Device or ADB connection
Summary: Loses Device or ADB connection
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-05-03 20:56 UTC by Eric Malamisura
Modified: 2016-08-03 15:23 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Eric Malamisura 2012-05-03 20:56:13 UTC
First off in the new release I love the new way the devices are handled, but I keep having a pretty major issue.  The device will constantly dissapear from the list and it will never pick it back up.  In previous versions when this happened I could do a adb kill-server and it would pick it right back up and I could just continue on with my work.  But now when I do it, it never picks it back up.  I have to shutdown Visual Studio and start it back up before it will find the device again, and this happens consistently.  I am pretty sure there is some adb instability with one of the devices I am using or in my setup in general, but as I said before the ability to recover from adb issues in the past was much better than it is now unfortunately...
Comment 1 Jonathan Pobst 2012-05-24 14:40:34 UTC
We've fixed various things that could potentially have caused this, and we've
added better logging so that things shouldn't crash and should give a better
error message for 4.2.2.

If you are still hitting errors in 4.2.2, please file a bug or reopen this one,
hopefully we'll at least provide you with a better error message!