Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How "good" is the Android Emulator? [closed]

As the title says, how "good" is the Android emulator?

I don't have an Android phone but would it be possible to develop purely using the emulator as the testing environment?

My initial questions about it:

  • Is the emulator as responsive as a normal android phone (of course this depends on the exact phone but in general)?
  • Is there a way to control the memory on the emulator?
  • Has anyone had issues that have been flagged on the phone but not the emulator? or vice versa?
  • What's your normal testing procedure to test on both throughout, or emulator recursively and phone at the end?

Any feedback would be appreciated.

Thanks,

like image 840
1'''' Avatar asked Mar 01 '10 13:03

1''''


People also ask

Does emulator make PC slow?

Emulators are slow. There's really nothing you can do about it, but there are alternatives to the emulator. To make your emulator faster, you can host a GPU and use a lighter Android version (Android 2.3 (Gingerbread)). Developing on a Mac would be better.

How much ram do I need for Android Emulator?

o Depending on your computer specs, the recommended ram size is in the range between 512 MB – 1024 MB. Although you can give more ram to the emulator but an actual android device would normally have 512 MB – 1024 MB for ram only.

Why is my Android Emulator so laggy?

The Android Emulator is very slow. The main reason is because it is emulating the ARM CPU & GPU, unlike the iOS Simulator, which runs x86 code instead of the ARM code that runs on the actual hardware.


2 Answers

Q: Is the emulator as responsive as a normal android phone (of course this depends on the exact phone but in general)?
A: Absolutely not! The worst example is the 3D, which is, afaik, only software emulation.

Q: Is there a way to control the memory on the emulator?
A: Please specify, the size of the SD-Card is configurable, the RAM/VM-Memory... I don't know.

Q: Has anyone had issues that have been flagged on the phone but not the emulator? or vice versa?
A: Each device has his own customization. On the emulator you can only change the screen resolution, but caution: the size of your Emulator screen depends on the pixel density you set up. So what might look good on your big emulator could be too tiny on a real device. And don't forget, a finger is much bigger and not as accurate as a mouse cursor.

Q: What's your normal testing procedure to test on both throughout, or emulator recursively and phone at the end?
A: Functionality is tested during the implementation mainly on a (fast) device, like a Nexus One. The real test after implementation will be on as many devices as possible. The UI, too (most differences there)

Since I have a device which is has the latest SDK, I prefer testing on the device. Thats not necessary for programming an app, but please: don't publish an app without at least one test round on a real device :)

like image 161
WarrenFaith Avatar answered Sep 30 '22 07:09

WarrenFaith


  1. Yes, the emulator is very fast.
  2. Yes, you can set the RAM size of the target you wish to emulate.
  3. I'm sure someone has, but I haven't.
  4. I usually test on the emulator during development, then on my G1 when I'm ready for longer term testing. After that I test on the emulator when checking compatibility with 1.5, 2.0, and 2.1 targets.

See here for what options targets support. Note there is a GUI tool for setting these up as well.

like image 24
Tim Avatar answered Sep 30 '22 06:09

Tim