Android Plugin | DXSdata https://www.dxsdata.com Software | Network | Administration Wed, 11 Jul 2012 13:45:55 +0000 en-GB hourly 1 https://wordpress.org/?v=7.0.4 https://www.dxsdata.com/wp-content/uploads/2023/08/cropped-logo-32x32.jpg Android Plugin | DXSdata https://www.dxsdata.com 32 32 Eclipse with Android plugin: Error PANIC: “Could not open: … Android3.2.ini” https://www.dxsdata.com/2012/07/eclipse-with-android-plugin-error-panic-could-not-open-android3-2-ini/ https://www.dxsdata.com/2012/07/eclipse-with-android-plugin-error-panic-could-not-open-android3-2-ini/#comments Wed, 11 Jul 2012 13:45:55 +0000 http://dev.schausberger.cc/?p=56 If you use redirected paths in Windows, e.g. for your user profile or app data, and they point to a network share, this can cause problems when running the AVD device emulator in Eclipse with the Android plugin.

By default, Eclipse always looks for the [virtual device].ini under c:usersusername.android, which is not always useful.

Some web sites mention a way of creating a symbolic link with mklink /J, but this is not possible with network UNC paths.

 

Solution:

Set Windows system variable ANDROID_SDK_HOME, e.g. with value c:program files(86)androidandroid-sdk.

Restart eclipse and have a look at the AVD manager. It should now point to the new directory and you can create your virtual devices again.

Links:

http://stackoverflow.com/questions/2841766/possible-to-change-where-android-virtual-devices-are-saved

http://stackoverflow.com/questions/3109473/moving-default-avd-configuration-folder-android

]]> https://www.dxsdata.com/2012/07/eclipse-with-android-plugin-error-panic-could-not-open-android3-2-ini/feed/ 1