Thursday, October 09, 2008


Gotchas with Google Android Development

If your screen resolution is not very high, you'll have problems with the Android Emulator. Needs a 768 pixel depth minimum. So you're out of luck with the standard setting on an eee PC, for example. Luckily there is a -scale setting for the emulator, which can vary between 0.1 and 3, so a value of around 0.6 makes the Android Emulator fit to a 600 pixel depth screen.

The Android Emulator can take a fair time to start up, up to 20 minutes on a PC, (but usually only 10 seconds or so on a mac pro,) so give it a minute or so with A N D R O I D displayed before you give up and look at what might be wrong. (It'll generally tell you on the command line if there really is something wrong, and that you're not being a tad hasty to kill the process.)

On really slow PCs you may get a message
Application Messaging (in
process is
not responding.

Which means, if you get it frequently, your machine is way too slow: you might like to try and install Linux or go out and buy something faster like a Mac.


or you can just add little more ram to your PC.
LOL: adding RAM doesn't help if the screen resolution is too small!
Post a Comment

Links to this post:

Create a Link

<< Home

This page is powered by Blogger. Isn't yours?

Subscribe to Posts [Atom]