blank emulator screen

1,133 views
Skip to first unread message

Sandeep

unread,
Jan 18, 2011, 8:59:13 PM1/18/11
to Android Building
Hi all,

I have downloaded android code as per instructions on
source.android.com.
I am running 64 bit Fedora Core 14.

After building the android source and running emulator, emulator
screen goes blank and shows following verbose description:

****************************************
emulator: found Android build root: /home/sandeep/myfs/mydroid
emulator: found Android build out: /home/sandeep/myfs/mydroid/out/
target/product/passion
emulator: locking user data image at /home/sandeep/myfs/mydroid/
out/target/product/passion/userdata-qemu.img
emulator: selecting default skin name 'HVGA'
emulator: autoconfig: -skin HVGA
emulator: keyset loaded from: /home/sandeep/.android/default.keyset
emulator: skin name 'HVGA' aliased to '320x480'
emulator: WARNING: system partition size adjusted to match image file
(85 MB > 66 MB)

emulator: no SD Card image at '/home/sandeep/myfs/mydroid/out/target/
product/passion/sdcard.img'
emulator: argv[00] = "emulator"
emulator: argv[01] = "-kernel"
emulator: argv[02] = "/home/sandeep/myfs/mydroid/prebuilt/android-arm/
kernel/kernel-qemu"
emulator: argv[03] = "-initrd"
emulator: argv[04] = "/home/sandeep/myfs/mydroid/out/target/product/
passion/ramdisk.img"
emulator: argv[05] = "-nand"
emulator: argv[06] = "system,size=0x5500000,initfile=/home/sandeep/
myfs/mydroid/out/target/product/passion/system.img"
emulator: argv[07] = "-nand"
emulator: argv[08] = "userdata,size=0x4200000,file=/home/sandeep/myfs/
mydroid/out/target/product/passion/userdata-qemu.img"
emulator: argv[09] = "-nand"
emulator: argv[10] = "cache,size=0x4200000"
emulator: argv[11] = "-serial"
emulator: argv[12] = "android-kmsg"
emulator: argv[13] = "-serial"
emulator: argv[14] = "android-qemud"
emulator: argv[15] = "-lcd-density"
emulator: argv[16] = "160"
emulator: argv[17] = "-append"
emulator: argv[18] = "qemu=1 console=ttyS0 android.checkjni=1
android.qemud=ttyS1"
emulator: argv[19] = "-m"
emulator: argv[20] = "96"
emulator: argv[21] = "-clock"
emulator: argv[22] = "unix"
emulator: registered 'boot-properties' qemud service
emulator: mapping 'system' NAND image to /tmp/android/emulator-bw6He4
emulator: rounding devsize up to a full eraseunit, now 5514000

emulator: mapping 'cache' NAND image to /tmp/android/emulator-Mse7NH
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '16m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '160'
emulator: using 'esd' audio input backend
emulator: using 'esd' audio output backend
emulator: Trace file name is not set

emulator: control console listening on port 5554, ADB on port 5555
emulator: can't connect to ADB server: Connection refused
****************************************

Please tell me what is causing this problem. Why is emulator not
working in my case? Is there any extra care that I need to take while
using a 64 bit machine?

Any help is greatly appreciated.
Thanks.

Regards,
Sandeep

may may

unread,
Jan 19, 2011, 11:23:36 AM1/19/11
to android-...@googlegroups.com
I suggest to use ubuntu 64 bit 10.10 better
 
 

--
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

Sejuk Hijau

unread,
Jan 20, 2011, 10:57:01 AM1/20/11
to android-...@googlegroups.com
On 01/19/2011 11:23 PM, may may wrote:
> I suggest to use ubuntu 64 bit 10.10 better

Why?
How about ubuntu 10.4 32 bit?

Jean-Baptiste Queru

unread,
Jan 20, 2011, 12:38:27 PM1/20/11
to android-...@googlegroups.com
Building gingerbread and higher isn't supported on 32-bit hosts.

Ubuntu 10.4 (64-bit) is the preferred host OS.

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.

patrick Immling

unread,
Aug 9, 2011, 5:11:50 AM8/9/11
to android-...@googlegroups.com
I am not sure if it runs on Ubuntu 10-10 and higher :(
I just  downloaded the latest(3.1) android sources from source.android.com on my Ubuntu 11.04(2.6.38-generic-pae)

When I compiled the sources and finally started the emulator with command "emulator" I get the following error too:

emulator: WARNING: system partition size adjusted to match image file (97 MB > 66 MB)

followed by a blank android emulator screen.

I dont even see any more error messages. Just the one above and then waited for a long time and tried it several times over with the same error.

Please help.

Jean-Baptiste Queru

unread,
Aug 9, 2011, 10:30:26 AM8/9/11
to android-...@googlegroups.com
As far as I know, this isn't related to Ubuntu 10.10. Also, the
warning you're getting is really just a warning, which you can safely
ignore (it really just tells you that the system image wouldn't fit on
a G1).

The deep issue is that, at compile-time, the Gingerbread branch uses
version 7 of the emulator, but at run-time it requires at least
version 12.

In order to be able to run straight out of fresh build, I believe that
you need to do two things:

-use version 12 of the emulator: in external/qemu, run "git checkout
korg/tools_r12"

-launch the emulator with the matching kernel: emulator -kernel
prebuilt/android-arm/kernel/kernel-qemu-armv7

JBQ

patrick Immling

unread,
Aug 10, 2011, 6:53:28 AM8/10/11
to android-...@googlegroups.com
I am a little confused here.

 I did a git checkout for tools_v12.

I retarted the emulator with the prebuilt kernel and I get the same warning again with a blank screen :(

I also downloaded the kernel sources. Compiled it and started my emulator (after creating a new avd image with id=3 pointing to android2.1) and did:

emulator -avd myandroid -kernel common/arch/arm/boot/zImage -show-kernel -verbose

And no emulator comes. I also see that at this point it stalls:
emulator: ping program: /home/Droid/android-sdk-linux_x86/tools/ddms
emulator: ping command: /home/Droid/android-sdk-linux_x86/tools/ddms ping emulator standalone

What should I do?


Thanks.

Gulshan Singh

unread,
Jan 4, 2012, 12:59:03 PM1/4/12
to android-...@googlegroups.com
Did you solve your problem? I have a similar issue.

Jean-Baptiste Queru

unread,
Jan 4, 2012, 1:08:13 PM1/4/12
to android-...@googlegroups.com
This might have been the issue (and the solution):
http://groups.google.com/group/android-building/msg/e5fe494238e2c50d

JBQ

On Wed, Jan 4, 2012 at 9:59 AM, Gulshan Singh <gsing...@gmail.com> wrote:
> Did you solve your problem? I have a similar issue.
>

Jean-Baptiste Queru

unread,
Jan 4, 2012, 6:00:51 PM1/4/12
to android-...@googlegroups.com
Damn, I just realized that the instructions were wrong. The only
project that needed to be fetched from tools_r12 is qemu, not sdk
(which is incompatible with gingerbread). I'm really sorry for the
people I've been misleading with inaccurate instructions :(

Oh well, this is a perfect opportunity to add a "known issues" section
to source.android.com.

repo forall external/qemu -c git checkout aosp/tools_r12
make
emulator -kernel prebuilt/android-arm/kernel/kernel-qemu-armv7

JBQ

Reply all
Reply to author
Forward
0 new messages