Q:

Android emulator accuracy and predicting time of operation

How accurate is the Android emulator in terms of how an app will function on a physical Android device? I am an amateur developer for Android but due to circumstances, do not own an Android device myself. Is how long the app takes to load/function on the emulator accurate (i.e. will it be faster or slower on an actual device)? And is there any way to see how it functions on different types of devices? Also, I keep getting this error:
Skipped 60 frames!  The application may be doing too much work on its main thread.

Does this mean I'm trying too hard a computation?

A:

Normally it's much much slower.
Luckily, some system images were added recently to launch a pair of emulators over x86 systems. This speeds up the experience drastically. There are images ready to be downloaded for 2.3.3 and 4.0.3.
To take advantage of them, just open Android SDK Manager (either from Eclipse, there's an icon with an arrow pointing to the bottom, or from the SDK). There you just need to download the x86 system images for 2.3.3 and 4.0.3.
After that, when creating a new emulator on one of these new OS versions, you'll be able to choose the CPU system. 
There are other minor tweaks which slightly improve performance, but I personally haven't felt the difference.
Give it a try and let me know if it worked out for you!

