Bug 8640 - MonoDevelop should offer to create Android AVDs if none available
Summary: MonoDevelop should offer to create Android AVDs if none available
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: 3.0.x
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Greg Munn
Depends on:
Reported: 2012-11-28 15:05 UTC by dave
Modified: 2016-12-20 19:17 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 dave 2012-11-28 15:05:38 UTC
I installed Mono for Android using the admin account.  I then use a non admin account for development.  The various soft emulators show up if I'm logged in as admin, but missing if I log in as non admin.  The Nexus 7 shows up in either case.
Comment 1 Mikayla Hutchinson [MSFT] 2012-11-28 17:50:45 UTC
MonoDevelop shows the available configured Android emulators. Android emulators are configured per user, and the Mono for Android unified installer only creates emulator configurations for the current user, not all users, however you can get to the Android emulator manager from a button in "Project->Manage Devices..." and create more.

Alternatively you could copy them from the .android in the Admin user's profile.

See http://developer.android.com/tools/devices/managing-avds-cmdline.html#DefaultLocation
Comment 2 dave 2012-11-29 10:15:20 UTC
I had copied from Admin account .android into non-admin account several weeks ago.  Seems recent Android update broke my copy.  Recopied and it works great.  Thanks.
Comment 3 Mikayla Hutchinson [MSFT] 2012-11-29 19:16:38 UTC
I guess arguably the installer could copy them into some system-wide location and MD could offer to "install" them if they weren't installed for the local user, so I'll leave the bug open.
Comment 4 Greg Munn 2016-12-20 19:17:26 UTC
Closing this since we have work items planned to address this.