blocks|key|1341464|text|这是解决ADT22.6.0中的错误的一种可能的方法，这些BUGS随后在下面构建的中被修复|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1341465|从+这里(拉链)+下载并安装新的ADTv22.6.1，或使用SDK管理器更新|1341466|似乎是谷歌方面的一些错误，这个问题在“ADT22.6”更新后发现。在上广泛报道的“安卓开源项目-问题跟踪器”上还没有人正确地回答它。|1341467|然而，通过从“Android”中打开“AVD+manager.exe"，创建新的AVD，尝试在SDK文件夹中直接打开AVD+Manager.exe，我在一定程度上成功地创建了AVD。|1341468|也许我们必须等待Android社区的任何构象。|1341469|为我工作，有点..。。|1341470|22.6.0.v201403010043-1049357)+(Windows8.1+Pro+64位，JavaJDK1.7更新25，EclipseStandardKeplerServiceRelease1，)|1341471|更新1|1341472|进一步的研究表明，从SDK+(Tools+-->+Manage+.)中启动也是没有任何问题的。|1341473|更新2|1341474|更坏的消息是，命令行工具也无法创建AVD。|1341475|更新3|1341476|假设在启动时传递了一些参数，则从中传递管理器会导致以下问题|1341477|更新4|1341478|更新Java到JDK1.7更新51和Eclipse+到KeplerServiceRelease2--他们对这些问题的最新解决方案没有解决方案。在Debian下也进行了测试，得到了相同的结果。|1341479|更新5|1341480|在https://code.google.com/p/android/issues/detail?id=66661，android项目成员将通过即将推出的ADT版本(22.61-22.6.3)解决问题并承诺修复。同时，我建议将ADT回滚到较低版本的22.3.0版。|1341481|要卸载当前ADT，请转到|1341482|帮助->关于Eclipse->安装细节->+Android+>卸载|1341483|我可能建议从Android+(DDMS、层次查看器、NDT、Traceview、OpenGL+ES..etc.)卸载整个软件包，以避免任何可能的兼容性问题，并通过归档安装方法从上面的链接中安装一个新的ADT。|1341484|希望这能暂时解决这个问题。并等待新版本的ADT+这里。|1341485|更新6|1341486|新的ADT，版本22.6.1现在已经发布，这将解决这些问题|1341487|entityMap|0|LINK|mutability|MUTABLE|url|http://dl.google.com/android/ADT-22.6.1.zip|1|https://code.google.com/p/android/issues/detail?id=66661|2|https://dl.google.com/android/ADT-22.3.0.zip|3|http://developer.android.com/tools/sdk/eclipse-adt.html^0|0|14|0|0|1|9|T|2|6|0|0|I|9|Y|K|0|6|9|I|H|0|8|9|0|0|U|21|0|0|3|0|0|1B|0|0|3|0|0|L|0|0|3|0|0|T|0|0|3|0|0|2N|0|0|3|0|0|3O|1|1K|1|3G|7|2|0|0|C|0|0|X|0|0|2W|0|0|R|O|2|3|0|0|3|0|0|T|0^^$0|@$1|2|3|4|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|24|8|@$9|25|A|26|B|C]|$9|27|A|28|B|C]]|D|@$9|29|A|2A|1|2B]]|E|$]]|$1|H|3|I|5|6|7|2C|8|@$9|2D|A|2E|B|C]|$9|2F|A|2G|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|2H|8|@$9|2I|A|2J|B|C]|$9|2K|A|2L|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|2M|8|@$9|2N|A|2O|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|2P|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|2Q|8|@$9|2R|A|2S|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|2T|8|@$9|2U|A|2V|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2Z|8|@$9|30|A|31|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|6|7|32|8|@$9|33|A|34|B|C]]|D|@]|E|$]]|$1|Z|3|10|5|6|7|35|8|@$9|36|A|37|B|C]]|D|@]|E|$]]|$1|11|3|12|5|6|7|38|8|@$9|39|A|3A|B|C]]|D|@]|E|$]]|$1|13|3|14|5|6|7|3B|8|@$9|3C|A|3D|B|C]]|D|@]|E|$]]|$1|15|3|16|5|6|7|3E|8|@$9|3F|A|3G|B|C]]|D|@]|E|$]]|$1|17|3|18|5|6|7|3H|8|@$9|3I|A|3J|B|C]]|D|@]|E|$]]|$1|19|3|1A|5|6|7|3K|8|@$9|3L|A|3M|B|C]]|D|@$9|3N|A|3O|1|3P]|$9|3Q|A|3R|1|3S]]|E|$]]|$1|1B|3|1C|5|6|7|3T|8|@$9|3U|A|3V|B|C]]|D|@]|E|$]]|$1|1D|3|1E|5|6|7|3W|8|@$9|3X|A|3Y|B|C]]|D|@]|E|$]]|$1|1F|3|1G|5|6|7|3Z|8|@$9|40|A|41|B|C]]|D|@]|E|$]]|$1|1H|3|1I|5|6|7|42|8|@$9|43|A|44|B|C]]|D|@$9|45|A|46|1|47]]|E|$]]|$1|1J|3|1K|5|6|7|48|8|@$9|49|A|4A|B|C]]|D|@]|E|$]]|$1|1L|3|1M|5|6|7|4B|8|@$9|4C|A|4D|B|C]]|D|@]|E|$]]|$1|1N|3|-4|5|6|7|4E|8|@]|D|@]|E|$]]]|1O|$1P|$5|1Q|1R|1S|E|$1T|1U]]|1V|$5|1Q|1R|1S|E|$1T|1W]]|1X|$5|1Q|1R|1S|E|$1T|1Y]]|1Z|$5|1Q|1R|1S|E|$1T|20]]]]

<h2>THIS IS A POSSIBLE WORKAROUND FOR BUGS IN ADT 22.6.0 ONLY, THESE BUGS SUBSEQUENTLY FIXED IN FOLLOWING BUILDS</h2>

Download and install new ADT v22.6.1 from <a href="http://dl.google.com/android/ADT-22.6.1.zip">here (zip)</a> or use SDK manager to update

Seems like some bug from Google side, this problem found after "ADT 22.6" update. Widely reported on "Android Open Source Project - Issue Tracker" and nobody properly answered it yet.

However I was partially successful to create an AVD by opening "AVD manager.exe" from "Android SDK" for creating new AVD try to open directly AVD Manager.exe in SDK folder.

May be we have to wait for any conformation from Android community

Worked for me, sort of.. .

(Windows 8.1 Pro 64 Bit, Java JDK 1.7 Update 25, Eclipse Standard Kepler Service Release 1, Android Development Toolkit 22.6.0.v201403010043-1049357)

Update 1

Further research revealed that launching AVD Manager from SDK Manager (Tools --> Manage AVDs...) also works without any problems.

Update 2

More bad news is AVD creation not working from command line tool too.

Update 3

Assuming some parameter passed during launching AVD manager from Eclipse causes these problems

Update 4

Updated Java to JDK 1.7 Update 51 and Eclipse Standard SDK to Kepler Service Release 2 their latest and no resolution to the problems. Also tested under Debian and same results obtained.

Update 5

At <a href="https://code.google.com/p/android/issues/detail?id=66661">https://code.google.com/p/android/issues/detail?id=66661</a> android project members conforms the problems and promises to fix by upcoming versions of ADT (22.6.1 - 22.6.3). At the mean time I would suggest to roll-back ADT to a lower version <a href="https://dl.google.com/android/ADT-22.3.0.zip">version 22.3.0</a> 

To uninstall current ADT go to 

Help --> About Eclipse --> Installation Details --> Android Development Tools --> Uninstall

I may suggest uninstalling whole packages from Android (DDMS, Hierarchy Viewer, NDT, Traceview, OpenGL ES..etc..) to avoid any possible compatibility issues and install a fresh new ADT from above link through archive installation method.

Hope this will solve this problem temporarily. And wait for new release of ADT <a href="http://developer.android.com/tools/sdk/eclipse-adt.html">here</a>. 

Update 6

New ADT, version 22.6.1 is out now which will solve these problems

blocks|key|1341526|text|给你的sd卡一些价值。可能是100或200|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1341527|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Give some value for your sd card. May be something like 100 or 200

blocks|key|621700|text|对于那些我们需要设置sdcard大小的帖子:我尝试过这种设置和许多其他设置，但这些都没有帮助。我在错误视图中得到了莫吉尔卡提到的NoClassDefFound异常。没有配置设置会修复这个问题。好像是个坏消息被推送了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|621701|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For those posting that we need to set the sdcard size: I tried that and many other settings, and none of that helps. I get the NoClassDefFound Exception mentioned by mogilka, in the Error view. No configuration settings are going to fix that. It seems a bad update was pushed

blocks|key|621719|text|为了详细说明“如果我从外部eclipse运行AVD管理器，我可以创建/编辑AVDs”，在OP中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|621720|在命令行上运行以下命令|621721|<android-sdk-location>/tools/android+avd+(on+Linux+in+this+case)|code-block|syntax|javascript|621722|这将启动与单击eclipse工具栏中的AVD管理器图标时所看到的相同的AVD窗口。但是AVD管理器的这个实例没有错误，您可以像引入bug之前一样创建和运行模拟器。|621723|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

To elaborate on the statement "I can create/edit AVDs if I run the AVD manager from outside eclipse" in the OP:

Run the following on the command line

<pre><code>&lt;android-sdk-location&gt;/tools/android avd (on Linux in this case)
</code></pre>

This launches the same AVD window you see when you click the AVD Manager icon in the eclipse toolbar. But this instance of the AVD manager does not have the bug, and you can create and run emulators as you did before the bug was introduced.

blocks|key|1620710|text|信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1620711|在几次单击OK并修改一些设置作为测试之后，我成功地创建了一个AVD。|1620712|我尝试过yashwanth解决方案，并试图直接打开AVD+Manageer.exe，但没有成功。在Windows8+x64上，管理器不会直接为我打开。它试图打开，然后立即关闭..。|1620713|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

INFO:

I WAS able to create an AVD successfully after clicking OK several times and modifying some of my settings as a test.

I tried yashwanth krishnan solution and tried to open the AVD Manageer.exe directly without success. The manager will not open directly for me on Windows 8 x64. It tries to open, then shuts down immediately...

blocks|key|621787|text|我也遇到过这个问题。这个问题发生在3月发布的最新版本22.6中。同时，我在22.3做了测试，没有发现问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|621788|因此，我建议将ADT回滚到22.3，并等待22.6的新修复。|621789|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I met this issue too . The issue occurs in the latest version 22.6 which was released in March . Meanwhile I did the testing in 22.3 , the issue was not found .

So that I suggest that rollback the ADT to 22.3 and wait the new fix for 22.6

blocks|key|1341688|text|我花了好几个小时才发现默认的位置是C:\username+path\SDKs之类的，我的系统上安装了安卓到D:\sdks\android_sdk_windows。因此，将Eclipse目录更改为D:\sdks\android_sdk_windows修复了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1341689|我还听说，如果您将Android安装到没有空格的路径上，可能会有所帮助。|1341690|希望这能帮你留点头发。|1341691|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I banged my head on this for several hours until I found out that the default location was C:\username path\SDKs or something, where Android was installed on my system to D:\sdks\android_sdk_windows. So, changing the Eclipse Android directory to D:\sdks\android_sdk_windows fixed it. 

I also heard that it may help things if you install the Android SDK to a path without spaces. 

Hope this helps someone keep some hair.

blocks|key|1341926|text|更新和解决方案：+AsYashwanth+Krishnan说，问题中的缺陷现在已经修复在以后的版本中。我试过ADT+222.6.1和ADT+22.6.2，他们没有受到无法创建或编辑Android虚拟设备的错误影响。直接的解决方案是将ADT更新为最新版本，下面编写的解决方案仅用于历史目的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1341927|正如@Yashwanth所说，历史解决方案是ADT插件22.6中的一个bug，所以最好的解决方法是回滚。对于那些询问如何回滚的人，下面是一个逐步的指南：|1341928|首先:卸载android的ADT插件和所有相关插件:+help->about|1341929|📷|atomic|1341930|安装细节|1341931|1341932|选择android插件并按卸载按钮。|1341933|1341934|1341935|1341936|1341937|重新启动|1341938|第二:从https://dl.google.com/android/ADT-22.3.0.zip下载ADT22.3.0档案|1341939|然后安装它|1341940|1341941|从本地磁盘上的存档中添加存储库|1341942|1341943|1341944|1341945|选择android插件|1341946|1341947|​|1341948|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/39f73bf37dea86b49669897bff836260.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/dde41b3b4889e2f41db52f01cbb28881.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/a459cba65bda63e92cdb6aa40067028b.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/841552d9c205392ab82bf77cd02c7969.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/f85f68eb538c13f39daf13a7318e4d68.png|5|https://developer.qcloudimg.com/http-save/yehe-900000/68113185b49b587fd4619f1f1be03da9.png|6|LINK|MUTABLE|url|https://dl.google.com/android/ADT-22.3.0.zip|7|https://developer.qcloudimg.com/http-save/yehe-900000/66398646ef34a948cc177a2fe433b91e.png|8|https://developer.qcloudimg.com/http-save/yehe-900000/c8c3e9df9459ba432af1fa3aa935d502.png|9|https://developer.qcloudimg.com/http-save/yehe-900000/beb88d9c4b3ddf1ff30b693d541626e9.png|10|https://developer.qcloudimg.com/http-save/yehe-900000/dd7e97affb1b62df3f86640d3999cfb0.png|11|https://developer.qcloudimg.com/http-save/yehe-900000/b2bc75adabdcbea558503960b7d04ede.png^0|0|8|0|F|6|0|0|0|1|0|0|0|0|1|1|0|0|0|1|2|0|0|1|3|0|0|1|4|0|0|1|5|0|0|4|18|6|0|0|0|1|7|0|0|0|1|8|0|0|1|9|0|0|1|A|0|0|0|1|B|0|0^^$0|@$1|2|3|4|5|6|7|2A|8|@$9|2B|A|2C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|2D|8|@$9|2E|A|2F|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|2G|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|2H|8|@]|D|@$9|2I|A|2J|1|2K]]|E|$]]|$1|M|3|N|5|6|7|2L|8|@]|D|@]|E|$]]|$1|O|3|K|5|L|7|2M|8|@]|D|@$9|2N|A|2O|1|2P]]|E|$]]|$1|P|3|Q|5|6|7|2Q|8|@]|D|@]|E|$]]|$1|R|3|K|5|L|7|2R|8|@]|D|@$9|2S|A|2T|1|2U]]|E|$]]|$1|S|3|K|5|L|7|2V|8|@]|D|@$9|2W|A|2X|1|2Y]]|E|$]]|$1|T|3|K|5|L|7|2Z|8|@]|D|@$9|30|A|31|1|32]]|E|$]]|$1|U|3|K|5|L|7|33|8|@]|D|@$9|34|A|35|1|36]]|E|$]]|$1|V|3|W|5|6|7|37|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|38|8|@]|D|@$9|39|A|3A|1|3B]]|E|$]]|$1|Z|3|10|5|6|7|3C|8|@]|D|@]|E|$]]|$1|11|3|K|5|L|7|3D|8|@]|D|@$9|3E|A|3F|1|3G]]|E|$]]|$1|12|3|13|5|6|7|3H|8|@]|D|@]|E|$]]|$1|14|3|K|5|L|7|3I|8|@]|D|@$9|3J|A|3K|1|3L]]|E|$]]|$1|15|3|K|5|L|7|3M|8|@]|D|@$9|3N|A|3O|1|3P]]|E|$]]|$1|16|3|K|5|L|7|3Q|8|@]|D|@$9|3R|A|3S|1|3T]]|E|$]]|$1|17|3|18|5|6|7|3U|8|@]|D|@]|E|$]]|$1|19|3|K|5|L|7|3V|8|@]|D|@$9|3W|A|3X|1|3Y]]|E|$]]|$1|1A|3|1B|5|6|7|3Z|8|@]|D|@]|E|$]]|$1|1C|3|-4|5|6|7|40|8|@]|D|@]|E|$]]]|1D|$1E|$5|1F|1G|1H|E|$1I|1J|1K|-4]]|1L|$5|1F|1G|1H|E|$1I|1M|1K|-4]]|1N|$5|1F|1G|1H|E|$1I|1O|1K|-4]]|1P|$5|1F|1G|1H|E|$1I|1Q|1K|-4]]|1R|$5|1F|1G|1H|E|$1I|1S|1K|-4]]|1T|$5|1F|1G|1H|E|$1I|1U|1K|-4]]|1V|$5|1W|1G|1X|E|$1Y|1Z]]|20|$5|1F|1G|1H|E|$1I|21|1K|-4]]|22|$5|1F|1G|1H|E|$1I|23|1K|-4]]|24|$5|1F|1G|1H|E|$1I|25|1K|-4]]|26|$5|1F|1G|1H|E|$1I|27|1K|-4]]|28|$5|1F|1G|1H|E|$1I|29|1K|-4]]]]

Update and Solution: AsYashwanth Krishnan said, The bug in question is now fixed in later versions. I tried ADT 222.6.1 and ADT 22.6.2 , and they did not suffer from the bug of not not being able to create or edit Android Virtual Devices. The direct solution is to update you ADT to latest version, The workaround written below is left only for historical purposes.

Historical Workaround As @Yashwanth Krishnan said, this is a bug in ADT plugin 22.6; so best workaround is to rollback. for those asking how to rollback, here is a step-by-step guide:

First: Uninstall ADT plugin and all related plugins for android:
help->about
<img src="https://i.stack.imgur.com/2Q3LS.png" alt="enter image description here">
Installation details
<img src="https://i.stack.imgur.com/Lv6qE.png" alt="enter image description here">
Select android plugins and press uninstall button
<img src="https://i.stack.imgur.com/QiGgT.png" alt="enter image description here">
<img src="https://i.stack.imgur.com/hKwK1.png" alt="enter image description here">
<img src="https://i.stack.imgur.com/rCEQZ.png" alt="enter image description here">
<img src="https://i.stack.imgur.com/JngiA.png" alt="enter image description here">
Restart 

Second: Download ADT 22.3.0 Archive from <a href="https://dl.google.com/android/ADT-22.3.0.zip" rel="nofollow noreferrer">https://dl.google.com/android/ADT-22.3.0.zip</a>

and install it
<img src="https://i.stack.imgur.com/xKIu6.png" alt="enter image description here">
add repository from archive on local disk
<img src="https://i.stack.imgur.com/wLbqw.png" alt="enter image description here">
<img src="https://i.stack.imgur.com/c7g5S.png" alt="enter image description here">
<img src="https://i.stack.imgur.com/9n4g6.png" alt="enter image description here">
Select android plugins
<img src="https://i.stack.imgur.com/egcGy.png" alt="enter image description here">

blocks|key|1620978|text|今天，我在安装Maven之后遇到了同样的问题。为了让它正常工作，我到处乱搞不同的路径设置，我遇到了一些问题。我还试图为GCM安装google服务器。在我所做的某个地方，我破坏了Android虚拟设备管理器。我搜索了S.O.的答案，然后决定遵循TechSupport的第一条规则。我重新安装了工具包！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1620979|我进入SDK管理器并卸载工具(单击工具复选框)。花了几分钟才把它们全部删除。然后我重新安装了大约十分钟的工具。我重新启动了Eclipse和AVD，就像昨天一样工作！|1620980|这次只花了二十分钟就修好了。|1620981|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Today I ran into the same problem after installing Maven. I messed around with different Path settings to get it to work and I ran into issues. I was also trying to install the google server for GCM. Somewhere in what I was doing I corrupted the Android Virtual Device Manager. I searched S.O. for an answer, then I decided to follow the first rule of TechSupport. I reinstalled the tool kit! 

I went into the SDK manager and I uninstalled the tools (by clicking the Tool checkbox). It took several minutes to delete them all. Then I reinstalled the Tools which took about ten minutes. I rebooted Eclipse and the AVD and worked just like it did yesterday!

This time it only took a total of twenty minutes to fix.

blocks|key|622194|text|根据发布说明，这个问题已经在22.6.1版本中解决了，该版本现在可供下载。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|622195|在Eclipse中，通过选择Window+>+Android+SDK+Manager并遵循安装更新的提示，将Android工具更新为22.6.1。|style|CODE|622196|在更新完成后，选择Help+>+Check+for+Updates，然后按照提示更新适当的Eclipse。|622197|在完成这些更新之后，我测试了AVD功能，并且它似乎工作正常。|622198|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.android.com/tools/sdk/eclipse-adt.html^0|2|4|0|0|E|6|N|J|0|9|4|G|H|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@$A|Y|B|Z|F|G]|$A|10|B|11|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@$A|13|B|14|F|G]|$A|15|B|16|F|G]]|9|@]|C|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]]]

Per the <a href="http://developer.android.com/tools/sdk/eclipse-adt.html" rel="nofollow">release notes</a>, this problem has been resolved in revision 22.6.1, which is now available for download.

Updated your Android SDK Tools to 22.6.1 in Eclipse by selecting <code>Window</code> > <code>Android SDK Manager</code> and follow the prompts to install the update.

After that update finishes, select <code>Help</code> > <code>Check for Updates</code> and follow the prompts to update the appropriate Eclipse components.

After completing these updates, I tested the AVD functionality and it appears to be working properly.

blocks|key|1621034|text|我刚刚从一个不同的系统复制了avds，如下所述：Android+-如何将仿真器复制到朋友进行测试|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1621035|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/4575167/android-how-to-copy-the-emulator-to-a-friend-for-testing^0|O|O|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

i just copied the avds from a different system as descriped here: 
<a href="https://stackoverflow.com/questions/4575167/android-how-to-copy-the-emulator-to-a-friend-for-testing">Android - How to copy the emulator to a friend for testing</a>

blocks|key|1621147|text|1分钟解|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1621148|我使用了一个快速的解决方法，我克隆了一个已经存在的设备。Clone按钮正常工作，我成功地编辑了克隆。|offset|length|style|CODE|1621149|步骤：|1621150|通过Google选择一个设备|1621151|​|1621152|📷|atomic|1621153|1621154|点击“克隆人”按钮|1621155|1621156|1621157|1621158|弹出一个窗口，单击“克隆设备”。|1621159|1621160|1621161|1621162|选择新克隆的设备，应该是“.+by+User”|1621163|1621164|1621165|1621166|点击旁边的“编辑”按钮|1621167|1621168|1621169|1621170|有了它，现在就有了自己的自定义虚拟设备。|1621171|1621172|1621173|1621174|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/dff41c47ef1f0ed2ea75ada93ab52016.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/839507286ef17e8434d55ccc6f988b47.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/9f0121825df1c99aef7058a9de3cca45.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/97c2faa72b37a6bbb80246bcdb015fc3.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/d762ebc6b12e7011d0b437e796162ae9.png|5|https://developer.qcloudimg.com/http-save/yehe-900000/282dd54f16f1da93f2b0a3f0b20afb37.png^0|0|S|5|0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|0|1|3|0|0|0|0|0|1|4|0|0|0|0|0|1|5|0|0^^$0|@$1|2|3|4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|20|8|@$D|21|E|22|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|23|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|24|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|25|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|26|8|@]|9|@$D|27|E|28|1|29]]|A|$]]|$1|Q|3|M|5|6|7|2A|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|2B|8|@]|9|@]|A|$]]|$1|T|3|M|5|6|7|2C|8|@]|9|@]|A|$]]|$1|U|3|O|5|P|7|2D|8|@]|9|@$D|2E|E|2F|1|2G]]|A|$]]|$1|V|3|M|5|6|7|2H|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|2I|8|@]|9|@]|A|$]]|$1|Y|3|M|5|6|7|2J|8|@]|9|@]|A|$]]|$1|Z|3|O|5|P|7|2K|8|@]|9|@$D|2L|E|2M|1|2N]]|A|$]]|$1|10|3|M|5|6|7|2O|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2P|8|@]|9|@]|A|$]]|$1|13|3|M|5|6|7|2Q|8|@]|9|@]|A|$]]|$1|14|3|O|5|P|7|2R|8|@]|9|@$D|2S|E|2T|1|2U]]|A|$]]|$1|15|3|M|5|6|7|2V|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2W|8|@]|9|@]|A|$]]|$1|18|3|M|5|6|7|2X|8|@]|9|@]|A|$]]|$1|19|3|O|5|P|7|2Y|8|@]|9|@$D|2Z|E|30|1|31]]|A|$]]|$1|1A|3|M|5|6|7|32|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|6|7|33|8|@]|9|@]|A|$]]|$1|1D|3|M|5|6|7|34|8|@]|9|@]|A|$]]|$1|1E|3|O|5|P|7|35|8|@]|9|@$D|36|E|37|1|38]]|A|$]]|$1|1F|3|M|5|6|7|39|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|3A|8|@]|9|@]|A|$]]]|1H|$1I|$5|1J|1K|1L|A|$1M|1N|1O|-4]]|1P|$5|1J|1K|1L|A|$1M|1Q|1O|-4]]|1R|$5|1J|1K|1L|A|$1M|1S|1O|-4]]|1T|$5|1J|1K|1L|A|$1M|1U|1O|-4]]|1V|$5|1J|1K|1L|A|$1M|1W|1O|-4]]|1X|$5|1J|1K|1L|A|$1M|1Y|1O|-4]]]]

<h2>1 minute solution</h2>

I used a quick workaround where I cloned a device that already existed. The <code>Clone</code> button worked and I was able to successfully edit the clone.

<h2>Steps:</h2>

<h2>Select a Device by Google</h2>

<img src="https://i.stack.imgur.com/5mlmn.png" alt="enter image description here">

<h2>Click the "Clone..." button</h2>

<img src="https://i.stack.imgur.com/DP7c0.png" alt="enter image description here">

<h2>A window will pop up, click "Clone device"</h2>

<img src="https://i.stack.imgur.com/h5qDT.png" alt="dddd">

<h2>Select the newly cloned Device, it should say "... by User"</h2>

<img src="https://i.stack.imgur.com/gbbL0.png" alt="enter image description here">

<h2>Click the "Edit" button on the side</h2>

<img src="https://i.stack.imgur.com/SLtFo.png" alt="enter image description here">

<h2>There you have it, you now have your own custom virtual device</h2>

<img src="https://i.stack.imgur.com/fjhE2.png" alt="enter image description here">

blocks|key|1342129|text|我也面临着类似的问题。我正在使用23.0.2版本的android。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1342130|"OK“按钮被禁用，但随后我进入了安装android的路径。就我而言：|1342131|C:\Program+Files\Android\android-sdk\|code-block|syntax|javascript|1342132|通过右键单击并选择作为管理员运行的来执行AVD-Manager.exe，它工作起来很有魅力。|offset|length|style|BOLD|1342133|entityMap^0|0|0|0|H|T|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I faced the similar issue. I am using 23.0.2 version of android SDK. 

"OK" button was disabled, but then I went to the path where android SDK was installed. In my case:

<pre><code>C:\Program Files\Android\android-sdk\
</code></pre>

and executed AVD-Manager.exe by right clicking and selecting Run as an Administrator, and it worked like a charm.

blocks|key|622420|text|有时，由于启动时出现以下错误，无法创建AVD+:+x86仿真目前需要硬件加速！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|622421|我也面临着同样的问题。如果您面临同样的问题，则可以通过在额外的->安装程序下打开same+->来解决这个问题。然后，在创建x86模拟器加速器时，选择合适的CPU。这应该是可行的。|622422|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Sometimes the AVD cannot be created because of this following error while starting:
x86 emulation currently requires hardware acceleration!

I was also facing this same issue. If u are facing the same, then it can be resolved by opening SDK Manager -> Under Extra -> Installed "Intel x86 Emulator Accelerator (HAXM Installer). Then when creating the AVD, select the proper CPU. This should work. :-)

This problem sounds similar to a <a href="https://stackoverflow.com/questions/13959128/avd-manager-cannot-create-android-virtual-device">few</a> <a href="https://stackoverflow.com/questions/14003009/android-virtual-device-manager-cannot-create-avd">others</a>, except in my case the OK button is not grey-ed out. But for those who would rather not click the links...

Trying to create or edit an AVD from within Eclipse, after entering my settings, the "OK" button seems to be "clickable", but when I click it absolutely nothing happens. <img src="https://i.stack.imgur.com/trEo8.png" alt="clickable but useless">

I've made sure I have the appropriate system images installed, and that the target platform matches the API being used. Clearly a CPU has been chosen, skin set, etc... all the things that would make the OK button greyed out, which it's not.

I can create/edit AVDs if I run the AVD manager from outside eclipse, so this isn't the end of the world, but I feel there's a solution to this particular problem and I want to help solve it.

I've tried running eclipse as an administrator (that's what stopped the AVD manager from crashing outside of eclipse). I've tried just waiting around, or clicking multiple times. Looking at the Task Manager, no new processes begin when I click OK, nor does eclipse's CPU or RAM usage increase at all. The "Edit Android Virtual Device" window doesn't even go away.

Any clues?

(Running Indigo with the ADT plugin, btw, not the bundled version, which failed to work in a different way. Java 1.6.0 45. Windows 8, unfortunately. Plenty of RAM etc)

Cannot create or edit Android Virtual Devices (AVD) from Eclipse, ADT 22.6

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

这个问题听起来类似于 ，但在我的例子中，OK按钮不是灰色的。但对于那些不愿点击链接的人.尝试从Eclipse中创建或编辑AVD，在输入我的设置后，"OK“按钮似乎是”可点击的“，但是当我单击它时，绝对不会发生任何事情。​我确保安装了适当的系统映像，并且目标平台与所使用的API相匹配。显然，CPU已经被选择，皮肤设置，等...

问无法从Eclipse创建或编辑Android虚拟设备(AVD)，ADT 22.6
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法从Eclipse创建或编辑Android虚拟设备(AVD)，ADT 22.6EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法从Eclipse创建或编辑Android虚拟设备(AVD)，ADT 22.6
EN