Shared publicly  - 
38
21
Xavier Ducrohet's profile photoEugene Krivenja's profile photoZakaria Bouam's profile photoTim Luther Lewis's profile photo
24 comments
 
I finally caved in and installed the preview this morning (trying to avoid previews in prod env).
Good news anyways, happy to install again tomorrow morning! :)
 
Yay, so excited to install new ADT.
 
A fast emulator? Hell yes. Can't wait to test it tomorrow.

Edit: only for Windows and Mac OSX :(
 
Only on Windows and Mac? Why not on Linux?
 
+Peter Hayduk I see also a description how to turn hard-acceleration on for Linux. Where do you see Windows / Mac only?
 
+Lars Vogel I read it in the blog post.

"Thanks to contributions to AOSP from Intel, the emulator now supports running x86 system images in virtualization mode on Windows and Mac OS X"

Didn't know that the emulator could be accelerated with KVM on Linux. Will try this tomorrow. Sadly I have a very slow PC at work hope to get an upgrade soon.
 
"We have changed the way Library Projects generate and package R classes:
- The R class is not packaged in the jar output of Library Projects anymore.
- Library Project do not generate the R class for Library Projects they depend on. Only main application projects generates the Library R classes alongside their own."Waited for it :)
 
+Peter Hayduk x86 is something different then accelaration as far as I understand.

+Xavier Ducrohet Linux can run Intel. Why should QEMU not be able to run Intel?
 
qemu can emulate either arm or intel CPUs but it does so in software.
To make qemu use virtualization so that it can run x86 guest instructions directly on the host x86 cpu is more complicated and require host side kernel drivers. They only existed for linux (KVM). Intel has added support for MacOS X and Windows by creating drivers for them.
 
+Lars Vogel The next sentence was "This allows the emulator running at near native speed." So I thought the emulator is still slow under Linux but if KVM makes it faster too I will give it a try.
 
+Xavier Ducrohet Thanks for the explanation. I still don't get it. If they already existed for Linux via KVM, why can't I run x86 on Linux?

I sounds like Intel provides something additional for Mac and Win but Linux should work without additions.
 
You need a system image compile for x86. If the guest system image is running arm then you can't run in virtualization (unless you were running the host system on an arm CPU, but I dont think kvm works for arm cpu).

The google TV system image for instance is x86. You can run it with KVM.
Our system image are currently only arm based so you can't run those on KVM.
Intel just started shipping their own system image so you can now use those.
 
The speed is comparable to Android x86 running on VirtualBox, nice! For now it seems there's only an x86 image for Android 2.3 though.
 
Nice! But we are still waiting for hardware accelerated openGL in the emulator, right? Any progress on that?
 
Hi,I wanted 2 upload 1 image from android devices as well as using android camera.Could u plz provide sum code 2 do the same,thanks
 
just tested it ... there are some improvements but, it's still far from the iOS emulator's experience
:(
 
I'm probably still deploying to device where possible, still need to find the money to get a tablet.
 
Another issue is there. Image x86 from Intel is a pure Android without Google API. It means, impossible to use it for developing and testing applications, for example, with Google Maps.
Or exists some tricks?
 
It's not about Image x86, it's about android emulator - it doesn't support the google api.
 
+Andrey Zhodevsky, android emulator does support the google api, sure.
Add a comment...