Bug 29532 - If running Genymotion emulator and plug in real device neither one shows up as an option
Summary: If running Genymotion emulator and plug in real device neither one shows up a...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Android ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: Normal normal
Target Milestone: 4.3.0 (C9)
Assignee: Bugzilla
Depends on:
Reported: 2015-04-29 11:36 UTC by Jeremy Kolb
Modified: 2016-12-09 17:39 UTC (History)
5 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 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 Jeremy Kolb 2015-04-29 11:36:57 UTC
If I have genymotion running (it shows up as a device in VS) and I plug in a physical Android device then neither one are available.

Restarting adb and/or killing genymotion and reinserting the original device both fail to get either device showing up.

The only recourse I have is to then restart Visual Studio.
Comment 1 Jeremy Kolb 2015-04-30 13:20:55 UTC
Might be related to https://bugzilla.xamarin.com/show_bug.cgi?id=23107
Comment 2 Jose Gallardo 2016-11-22 13:46:16 UTC
There were several changes on device management since this issue was reported.
That should already addressed this bug.
If you're still facing it please feel free to reopen it and we'll investigate.