Freshly built Gingerbread emulator black screen

[DusteD]

When I build the aosp gingerbread branch and launch the emulator I get
a black screen, nothing more.
emulator -logcat *:v gives nothing either.
adb shows the emulator as offline:
List of devices attached
emulator-5554 offline

But after a while, adb do not show the emulator at all, I suspect I
have the same problem as this fellow:
http://stackoverflow.com/questions/7997686/android-2-3-emulator-blank-screen-after-build/8123273#8123273

Steps I did:
mkdir gingerbread
cd
repo init -u url -b gingerbread
repo sync
. build/envsetup.sh
lunch
1
make -j 8
emulator -logcat *:v

[Jean-Baptiste Queru]

Oh, that's a complex issue.

In a nutshell, even though we have both the dev tools and the platform
in the same source tree (they can't be built without one another), the
versions that are in a given source tree aren't always compatible.

The dev tools in the gingerbread branch are tools_r7, i.e. 8 versions
old, and they're not enough to run the latest gingerbread platform.

I believe that this might work, but since those are notes that I made
a long time ago these instructions might be obsolete as well:

repo forall sdk external/qemu -c git checkout aosp/tools_r12
# build, possibly a clean build
emulator -kernel prebuilt/android-arm/kernel/kernel-qemu-armv7

JBQ

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[DusteD]

I see, thank you for your help, this worked for me.

[Jean-Baptiste Queru]

Glad to head that. I realize that this isn't an "easy" fix,
unfortunately we're juggling multiple requirements that are hard to
reconcile in a way that's transparent for everyone. Thanks for
understanding.

I should document that somewhere. I really need to create a "known
issues" section on source.android.com.

JBQ

On Mon, Nov 14, 2011 at 11:16 PM, DusteD <dust...@gmail.com> wrote:
> I see, thank you for your help, this worked for me.
>