>From discussions with the Google Engineers, the emulator emulates the *entire
*device on the lowest levels, not just the DalvikVM. It emulates the ARM
processor and the code that runs on it and a bunch of the in and output
devices (keyboard, touchscreen in some form, screen, GPS, etc). You can
Yes there is. Intel has honeycomb running on their IA (Intel Architecture).
But it's all in early phases.
But Google TV runs on x68 and Google TV will upgraded to Honeycomb (3.1)
this year.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
The docs are a little vague about any ARM emulation. It says "the SDK
contains ARM machine code for the Android Linux kernel". Would it use
that on Windows? And then it wouldn't be the first time the docs are
left vague as we all know. Seems to me if you are running Java byte
code then all you
Okay, I stand corrected. But you'll notice that there was no attempt to correct
this part:
> There is no PC on which it has usable performance.
I don't dispute that Android emulation is a hard problem. The unfortunate fact
remains that Honeycomb development simply isn't possible without a hardw
There are so much misinformation in this thread. Let's try to clarify:
The *main* bottleneck for slow performance in the emulator is OpenGLES
emulation, which is currently performed in software, moreover in emulated
ARM instructions. All platform releases are emulated by the same virtual
CPU, the
On Tuesday, May 31, 2011 3:30:39 PM UTC-4, jtoolsdev wrote:
Ah, the emulator isn't running ARM code just the Dalvik engine.
Really? There's an x86 build of honeycomb? And an x86 toolchain in the
NDK?
I don't believe that is the case... unfortunately.
--
You received this message because
Ah, the emulator isn't running ARM code just the Dalvik engine. The
problem has been addressed elsewhere by developer supprot that it is
not possible to build an emulator so far that can take advantage of
the graphics acceleration on your PC.
On May 31, 12:25 pm, String wrote:
> The bottleneck i
I have a 3.3ghz quad core with 4 gb ram that runs 2.3.3 on the emulator fine
at WQVGA432. Same computer fails miserably to run 3.0 at WXGA.
Runs fine, that is, except when it decides to randomly crash when clicking
anywhere on the skin, and then failing to clean up after itself and usually
kee
8 matches
Mail list logo
