The next thing I see in logcat for the generic ARM build is SurfaceFlinger opening up EGL. Could it be hanging there on generic_x86?
BTW, sorry for the newbie questions. Once I get rolling I'll be good. On Sat, May 29, 2010 at 4:58 PM, Doug Schaefer <[email protected]> wrote: > Forwarding back to group where we ended up. > > > ---------- Forwarded message ---------- > From: Doug Schaefer <[email protected]> > Date: Sat, May 29, 2010 at 4:57 PM > Subject: Re: [android-porting] Re: VirtualBox Black Screen > To: Ashwin Bihari <[email protected]> > > > Could be, I don't see any Java apps starting up. I'll dig a bit more and > see what I can find. > > > On Sat, May 29, 2010 at 4:27 PM, Ashwin Bihari <[email protected]> wrote: > >> A lack of page flipping is not the problem..but that's fairly early in >> the Android startup process, there should be a lot more messages after >> as well..if you don't get that, Zygote, the startup application, is >> having an issue getting the rest of the system up.. >> >> -- Ashwin >> >> >> >> On Sat, May 29, 2010 at 4:21 PM, Doug Schaefer <[email protected]> wrote: >> > I'm doing the generic-x86 build as per the instructions >> > in build/target/board/generic_x86/README.txt. >> > Here's my report filtering out debug messages. gralloc does report a >> warning >> > about page flipping not supported. Could that be it? >> > I/vold ( 47): Android Volume Daemon version 2.0 >> > I/ ( 49): ServiceManager: 0x90ccd08 >> > W/AudioHardwareInterface( 49): Using stubbed audio hardware. No sound >> will >> > be produced. >> > I/CameraService( 49): CameraService started: pid=49 >> > I/AudioFlinger( 49): AudioFlinger's thread 0x90cd320 ready to run >> > I/SamplingProfilerIntegration( 48): Profiler is disabled. >> > I/Zygote ( 48): Preloading classes... >> > I/Zygote ( 48): ...preloaded 1939 classes in 1244ms. >> > I/Zygote ( 48): Preloading resources... >> > I/Zygote ( 48): ...preloaded 48 resources in 108ms. >> > I/Zygote ( 48): ...preloaded 15 resources in 4ms. >> > I/dalvikvm( 48): Splitting out new zygote heap >> > I/dalvikvm( 48): System server process 58 has been created >> > I/Zygote ( 48): Accepting command socket connections >> > E/BatteryService( 58): acOnlinePath not found >> > E/BatteryService( 58): usbOnlinePath not found >> > E/BatteryService( 58): batteryStatusPath not found >> > E/BatteryService( 58): batteryHealthPath not found >> > E/BatteryService( 58): batteryPresentPath not found >> > E/BatteryService( 58): batteryCapacityPath not found >> > E/BatteryService( 58): batteryVoltagePath not found >> > E/BatteryService( 58): batteryTemperaturePath not found >> > E/BatteryService( 58): batteryTechnologyPath not found >> > I/sysproc ( 58): Entered system_init() >> > I/sysproc ( 58): ServiceManager: 0x8d93838 >> > I/SurfaceFlinger( 58): SurfaceFlinger is starting >> > I/SurfaceFlinger( 58): SurfaceFlinger's main thread ready to run. >> > Initializing graphics H/W... >> > W/gralloc ( 58): page flipping not supported (yres_virtual=600, >> > requested=1200) >> > I/gralloc ( 58): using (fd=22) >> > I/gralloc ( 58): id = VESA VGA >> > I/gralloc ( 58): xres = 800 px >> > I/gralloc ( 58): yres = 600 px >> > I/gralloc ( 58): xres_virtual = 800 px >> > I/gralloc ( 58): yres_virtual = 600 px >> > I/gralloc ( 58): bpp = 16 >> > I/gralloc ( 58): r = 11:5 >> > I/gralloc ( 58): g = 5:6 >> > I/gralloc ( 58): b = 0:5 >> > I/gralloc ( 58): width = 127 mm (160.000000 dpi) >> > I/gralloc ( 58): height = 95 mm (160.421051 dpi) >> > I/gralloc ( 58): refresh rate = 83.43 Hz >> > On Sat, May 29, 2010 at 2:52 PM, Ashwin Bihari <[email protected]> >> wrote: >> >> >> >> What does logcat report as happening? >> >> >> >> Regards >> >> -- Ashwin >> >> >> >> >> >> >> >> On Sat, May 29, 2010 at 11:27 AM, Doug Schaefer <[email protected]> >> wrote: >> >> > On Sat, May 29, 2010 at 10:35 AM, Doug Schaefer <[email protected]> >> >> > wrote: >> >> >> >> >> >> Hey gang, first time poster :). >> >> >> There hasn't been much talk about running Android in VirtualBox in >> this >> >> >> group lately. But I saw the kernel_config_VirtualBox and thought I'd >> >> >> give it >> >> >> a try. I'm using the new VirtualBox 3.2. After adding the AHCI SATA >> >> >> driver >> >> >> to the config and building my kernel (android-2.6.32 branch). I was >> >> >> able to >> >> >> successfully run the installer.vdi and install into my main virtual >> >> >> disk. >> >> >> However when starting that up, I see the regular Linux boot messages >> >> >> fly >> >> >> by and then it fires up with a black screen and all disk and network >> >> >> activity stops. I'm not sure how to get any information out of the >> VM >> >> >> at >> >> >> that point. I can poke around in the installer after it's finished. >> I >> >> >> did >> >> >> notice that there were no fb devices, but that may be a red herring >> >> >> since >> >> >> the GUI doesn't try to come up in that mode. >> >> >> Has anyone been able to get this work lately or am I on untrodden >> >> >> ground. >> >> > >> >> > On the good news front, I have been able to adb connect to it and >> dmesg >> >> > and >> >> > logcat doesn't seem to report any errors. gralloc properly reports a >> >> > VESA >> >> > 800x600 screen. Maybe the screen is supposed to be black? >> >> > >> >> > -- >> >> > unsubscribe: >> >> > [email protected]<android-porting%[email protected]> >> >> > website: http://groups.google.com/group/android-porting >> >> > >> >> >> >> -- >> >> unsubscribe: >> >> [email protected]<android-porting%[email protected]> >> >> website: http://groups.google.com/group/android-porting >> > >> > >> > > > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
