Bug 5322 - VS Select Device Dialog needs a Refresh button
Summary: VS Select Device Dialog needs a Refresh button
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Visual Studio Compatibility ()
Version: 3.0.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-25 08:05 UTC by Javier Rodríguez
Modified: 2015-11-20 12:26 UTC (History)
3 users (show)

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 or GitHub 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:

Description Javier Rodríguez 2012-05-25 08:05:41 UTC
Never shows any emulator started.
Comment 1 Jonathan Pryor 2012-07-25 22:47:52 UTC
The IDE maintains a connection to the Android Debug Bridge daemon, and occasionally this connection is interrupted. This is most visible when the Select Device dialog comes up empty.

The workaround is to restart Visual Studio.

A better workaround would be to add an explicit Refresh button to the Select Device dialog which would recreate the adb connection. This is what MonoDevelop does.
Comment 2 Mikayla Hutchinson [MSFT] 2012-07-27 13:38:34 UTC
To clarify, it doesn't just reconnect to adb, it restarts adb first. This is useful if adb has crashed, been killed, or got into a bad state.
Comment 3 Naqeeb 2015-11-20 12:26:17 UTC
I have checked this issue and observed that this is working fine at our end. 

Screencast: http://www.screencast.com/t/O8S5GbYM

As of now I am closing this issue. Please feel free to reopen this issue if you
are still getting this.


Environment info: https://gist.github.com/saurabh360/dbfe5e41fab5e11ed479