Friday, August 23, 2013

Android Device Manager Change Path

Android device manager change path In the wake of experiencing the Xamarin establishment directions for Mac and Windows, I wound up in a scenario where the AVD Manager (Android Virtual Device Manager) on my Windows VM might not gave me a chance to make another AVD. It might toss the accompanying blunder: "The framework can't discover the way specifi

AVD Manager Android Device Manager Change Path

201305271052.jpg

Create new AVD

201305270123.jpg

Error

201305271042.jpg
The problem is that the location it is trying to save the AVD doesn’t exist, probably a result of running Windows as a guest OS under VMware Fusion. A quick check of the AVD Manager settings under Tools > Options, confirms that the Manifest Cache Directory points to wrong location.
To correct this, you need to modify the location of the Android SDK:
1. Run the systemadvancedproperties Windows command to open up the System Properties on the Advanced tab.
201305270124.jpg
2. Click on Environment Variables.
3. Add a new user variable:
Variable name: ANDROID_SDK_HOME
Variable value: C:\Users\\.android (or wherever the SDK is installed – %homepath% by default)
201305270124.jpg
4. OK and restart your Windows VM.
5. Check that the Manifest Cache Directory is now set correctly.
201305270124.jpg
6. Test and create a new AVD.
201305270123.jpg

No comments:

Post a Comment