Android 模拟器在 Ubuntu Maverick 上不断重新启动
感谢您抽出时间。
我正在使用 Titanium Appcelerator 为 Android 编写应用程序，与模拟器相当稳定的 Windows 相比，在 Linux 中，我出现以下症状：
模拟器无故重启，有时在运行时错误后，有时正确启动我的应用程序后，有时在启动后完全启动后立即启动
模拟器通知“进程$1没有响应”，其中$1通常是系统进程，但有时可能是acore或日历。在模拟器上安装我的应用程序时、加载应用程序后或解锁屏幕后，可能会发生这种情况。
很容易想象，测试这样的代码可能非常困难，所以我想知道，是否有其他人偶然发现了这个问题，和/或知道如何解决它？
预先非常感谢您，请让我知道我应该提供的任何信息。
狮子座
and thank you for your time.
I am using Titanium Appcelerator to write an app for Android, and as compared to Windows, where the emulator was quite stable, in Linux I get the following symptoms:
emulator restart with no reason, sometimes after a runtime error, sometimes right after launching my app, and sometimes just right after booting completely after being launched
emulator informs that "process $1 is not responding", where $1 is generally the system process, but sometimes may be acore, or the calendar. This may happen while installing my app on the emulator, right after loading it, or right after unlocking the screen.
As it is easy to imagine, testing code like this can be quite difficult, so I was wondering, has anyone else stumbled upon this problem, and/or know how it could be solved?
Thank you very much in advance, and pls let me know of any info I should provide.
Leo
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您应该首先验证模拟器是否在没有 Appcelerator 的情况下正常工作。一定要更新到最新的 SDK (r8) 并创建一个新的模拟器 AVD，看看在没有 Appcelerator 的情况下是否存在问题。
You should verify that the emulator is working fine without Appcelerator first. Definitely update to the latest SDK (r8) and create a new emulator AVD and see if the problem is there without Appcelerator.
我想我找到了一个解决方案，但我并不声称它是普遍有效的：我只是删除了在 Titanium 下创建的虚拟设备，更改了项目文件以使用 SDK 1.4.2，并在 1.4.2 下再次启动它。它当然没有构建我的应用程序，但至少它创建了一个新的虚拟设备，我现在用它来构建 1.5.0，到目前为止，它工作得非常顺利。
再次感谢曼弗雷德为我指明了正确的方向！
I think I found a solution, but I don't claim it is universally valid: I just erased the virtual device created under Titanium, changed the project file for it to use SDK 1.4.2, and had it launched again under 1.4.2. It certainly didn't build my app, but at least it created a new virtual device, which I use now to build against 1.5.0, working like a charm so far.
Thanks again Manfred for pointing me in the right direction!