Android Emulator can#39;t start, #39;cause of wrong folder(Android Emulator 无法启动,因为文件夹错误)
问题描述
我刚开始使用 Eclipse 和 ADT,但遇到了一些问题,Android 模拟器无法启动:
I'm just starting to use Eclipse and ADT and I have some issues, the Android Emulator don't start :
[2011-07-10 15:32:25 - Android_FirstApp] ------------------------------
[2011-07-10 15:32:25 - Android_FirstApp] Android Launch!
[2011-07-10 15:32:25 - Android_FirstApp] adb is running normally.
[2011-07-10 15:32:25 - Android_FirstApp] Performing samr1.Android_FirstApp.Android_FirstAppActivity activity launch
[2011-07-10 15:32:25 - Android_FirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.1'
[2011-07-10 15:32:25 - Android_FirstApp] Launching a new emulator with Virtual Device 'Android2.1'
[2011-07-10 15:32:26 - Emulator] PANIC: Could not open: C:UsersSam.android/avd/Android2.1.ini
路径不正确,但Android2.1.ini中的路径是正确的.用户文件夹位于另一个磁盘中.
The path isn't correct, though the path in Android2.1.ini is correct. The User folder is located in an another disk.
如何修改 Android Emulator 的启动路径?我找不到在哪里.
How can I modify the start path of Android Emulator ? I can't find where.
谢谢
我发现图形 AVD 管理器在 Windows 7 上的 C:Users.android 内创建了 AVD 目录:AVD文件的默认位置
EDIT : I found that graphical AVD Manager creates AVD directory inside C:Users.android on Windows 7 : Default location of AVD files
但是使用命令行不起作用.所以我将我的 AVD 文件移到 C:UsersSam 中,现在它可以工作了.
But using Command Line doesn't work. So i moved my AVD files in C:UsersSam and now it works.
推荐答案
这是 ADT 插件中的一个错误.在修复之前的解决方法是使用 NTFS 符号链接.
This is a bug in the ADT Plugin. For a workaround until it is fixed use a NTFS symbolic link.
我有一个用于 Windows 7 的 C: 驱动器和一个用于我所有工作和数据的 D: 驱动器.安装 Windows 7 后,我将所有特殊文件夹从 C:UsersJohn Doe 重新定位到 D:John Doe.当 ADT 插件和配置文件位于 D: 上时,ADT 插件正尝试从 C: 加载模拟器(恐慌:无法打开等).NTFS 可以使用 NTFS 符号链接让 ADT 插件从 D: 中读取.在 C:UsersJohn Doe 中打开命令提示符(显然使用您的用户名),使用 mklink 命令.
I have a C: drive for windows 7 and a D: drive for all my work and data. After installing windows 7 I relocate all my special folders from C:UsersJohn Doe to D:John Doe. The ADT Plugin is trying to load the emulator from C: when it and the configure files are on D: (PANIC: Could not open etc.). NTFS can get the ADT Plugin to read from D: using a NTFS symbolic link. Open a command prompt in C:UsersJohn Doe (obviously use your user name), use the mklink command.
mklink/J "C:UsersJohn Doe.android" "D:John Doe.android"
mklink /J "C:UsersJohn Doe.android" "D:John Doe.android"
现在,当 ADT 插件尝试在 C: 上引用 .android 时,NTFS 将请求发送到 D: 并且模拟器正确启动.
Now when the ADT plugin is trying to reference .android on C:, NTFS sends the request to D: and the emulator starts correctly.
这篇关于Android Emulator 无法启动,因为文件夹错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:Android Emulator 无法启动,因为文件夹错误
基础教程推荐
- FirebaseListAdapter 不推送聊天应用程序的单个项目 - Firebase-Ui 3.1 2022-01-01
- 在 Libgdx 中处理屏幕的正确方法 2022-01-01
- 设置 bean 时出现 Nullpointerexception 2022-01-01
- 降序排序:Java Map 2022-01-01
- 减少 JVM 暂停时间 >1 秒使用 UseConcMarkSweepGC 2022-01-01
- Java:带有char数组的println给出乱码 2022-01-01
- 无法使用修饰符“public final"访问 java.util.Ha 2022-01-01
- Java Keytool 导入证书后出错,"keytool error: java.io.FileNotFoundException &拒绝访问" 2022-01-01
- “未找到匹配项"使用 matcher 的 group 方法时 2022-01-01
- 如何使用 Java 创建 X509 证书? 2022-01-01