Emulator Problem

[Slacker]

I can't get the emulator working, it just hangs on the A N D R O I D _ boot screen.

I've installed the SDK and packages as per the guide. Created a Virtual Device (2.1-update1), copied the system.img to the corresponding folder. Messing about with the device options (ram etc) doesn't fix it.
The device starts ok without the custom system.img.
Tried both Win7 and WinXP 32 bit.

Any ideas?

Thanks

[Fonefixer]

Welcome to the forum,

I moved your post to a more relevant section.

[suggsy89]

i think your system.img may not be compatible with androids default ramdisk.img (boot.img)

not 100% though

[Slacker]

Still no joy with this, can't get the emulator to boot so can't get a ID to fix my Market .

Android SDK tools has now been updated to rev 12, plus tried it on Win7_64.
Also tried to run with a old copy of rev 6 tools, as per the original Slate fix but it wasn't having it.

[bloggs]

I couldn't remember how I'd done this, so I just went back through the process. I tried using version 1.6 and 2.1 virtual devices (should really be 1.6 as that's what the "market fix" system.img provides) and didn't have any problem getting it to boot, although I did have to change the Device RAM setting (I used 100). I'm using Windows XP 32 with SDK version 11.

Could your download of the system.img be corrupt? I get an MD5 checksum of

9b7f449ec56b2fc5c9c9f3b243a7b958

from my copy (you have to check the original download as Android will modify the copy in the virtual device's directory.) Might be worth checking and/or downloading again?

Eddie

[Slacker]

Thanks for the help Eddie, turns out you were bang on the img file was corrupt. Downloaded again, double checked the md5 and this time worked fine.
Have pushed the id, fingers crossed this fixes Market .

Cheers

Mark