4 ms·

I can't understand why people always complain about the performanceo of the android emulator. With an Intel X86 image and activated hardware acceleration (GPU &

by fotcorn 13y ago

I can't understand why people always complain about the performanceo of the android emulator. With an Intel X86 image and activated hardware acceleration (GPU & CPU KVM or HAXM), the emulator is much faster than an actual phone. Installation Guide by Intel: http://software.intel.com/en-us/articles/speeding-up-the-android-emulator-on-intel-architecture http://software.intel.com/en-us/articles/speeding-up-the-and....

gladimdim 13y ago
As for me Android emulator could not even start in >30 mins. I always tested on real device.
- Superleroy 13y ago
  If your emulator takes more than 30mins to start i would suspect there are different problems than the speed of the emulator. For me even the slow (non Intel X86) emulators never take more than a minute or two to load.
  - philbarr 13y ago
    Me too, and once it's open just leave it open and just start and stop the actual app. No need to reopen the emulator each time.
rogerbinns 13y ago
I had several problems with the emulator not doing audio recording and playback the same as real devices. Often they don't have the google apis or voice recognition either. I must admit I haven't found it a big deal to use real devices. I also use Wifi ADB so I don't actually need to mess with cables. Compared to those long intel instructions, switching simulators on iOS is trivial. I also found them mostly bug compatible with the devices - ie the same bug would appear on both. The Android emulators have historically diverged (I remember the 2.3 days when javascriptinterface on the webview would crash in the emulator but not the real device).
- archivator 13y ago
  AOSP is different from OEM builds. It's not an emulator problem, most of the time. The folks at Genymotion seem to be working on fixing that with preapproved builds and more powerful controls.
  - rogerbinns 13y ago
    The acronyms don't really matter. What I need to know is that a bug encountered in the emulator would also occur on the devices and vice versa. If that doesn't happen then the emulator becomes yet another platform with a differing set of unique bugs.
    - archivator 13y ago
      Agreed. Unfortunately, that's a guarantee that Android's licensing model can't provide. Every manufacturer can do whatever they please, so fragmentation can't be regulated.
BitMastro 13y ago
An useful tool for android emulation was http://androvm.org/blog/download/ http://androvm.org/blog/download/ now genymotion http://www.genymotion.com/ http://www.genymotion.com/
redcircle 13y ago
If you feel comfortable installing an Intel hypervisor on your Mac. I do not.

by fotcorn 13y ago

gladimdim 13y ago

As for me Android emulator could not even start in >30 mins. I always tested on real device.

Superleroy 13y ago
If your emulator takes more than 30mins to start i would suspect there are different problems than the speed of the emulator. For me even the slow (non Intel X86) emulators never take more than a minute or two to load.
- philbarr 13y ago
  Me too, and once it's open just leave it open and just start and stop the actual app. No need to reopen the emulator each time.

rogerbinns 13y ago

I had several problems with the emulator not doing audio recording and playback the same as real devices. Often they don't have the google apis or voice recognition either. I must admit I haven't found it a big deal to use real devices. I also use Wifi ADB so I don't actually need to mess with cables. Compared to those long intel instructions, switching simulators on iOS is trivial. I also found them mostly bug compatible with the devices - ie the same bug would appear on both. The Android emulators have historically diverged (I remember the 2.3 days when javascriptinterface on the webview would crash in the emulator but not the real device).

archivator 13y ago
AOSP is different from OEM builds. It's not an emulator problem, most of the time. The folks at Genymotion seem to be working on fixing that with preapproved builds and more powerful controls.
- rogerbinns 13y ago
  The acronyms don't really matter. What I need to know is that a bug encountered in the emulator would also occur on the devices and vice versa. If that doesn't happen then the emulator becomes yet another platform with a differing set of unique bugs.
  - archivator 13y ago
    Agreed. Unfortunately, that's a guarantee that Android's licensing model can't provide. Every manufacturer can do whatever they please, so fragmentation can't be regulated.

BitMastro 13y ago

An useful tool for android emulation was http://androvm.org/blog/download/ http://androvm.org/blog/download/ now genymotion http://www.genymotion.com/ http://www.genymotion.com/

redcircle 13y ago

If you feel comfortable installing an Intel hypervisor on your Mac. I do not.