(day off work today, hence the numerous posts!)

To try to better fix specific device problems, I've been trying to see if I
can run other device system.img files in the emulator. At least if I can run
it, I can check the software out and fix problems, that's my theory.

I've done this before with a custom rom for the hero - VanillaEclair. It
runs very nicely in the emulator, thank you.

But I've not been able to run any other custom rom or default rom from any
other device. I've been trying recently with roms from the Haipad and X5A -
two exotic "chi-pads" that appear to be having problems with my app that no
other device does.

The system.img looks fine - the permissions inside are all correct, but I
just can't get it to boot enough to write a single line to the logcat.

I've ripped the system.img apart under linux and rebuilt it to prove this.
and I did the exact same thing with a platform android image to confirm the
process works and that still boots fine.

I'm wondering if it is something to do with arm versions..? Can the emulator
only emulate arm5 and I think these new pads are arm6 and won't even boot?

When I use the -debug all or -show-kernel, I don't see any unusual messages.

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en