It is not only slow, but also buggy. :(
After the home screen starts up, when I hit any key, seems nothing
happends.
And frequently the screen will go to black, and a message box says
"Activity Home(in
process android.process.acore) is not responding." pops up.
The logcat says:
V/WindowManager( 1709): New key dispatch window:
win=android.os.binderpr...@9e65c788, last=null (token=null),
finished=true, paused=false
I/ActivityManager( 1709): ANR (application not responding) in process:
android.process.acore
I/ActivityManager( 1709): Annotation: keyDispatchingTimedOut
I/ActivityManager( 1709): CPU usage:
I/ActivityManager( 1709): Load: 0.59 / 0.52 / 0.21
I/ActivityManager( 1709): CPU usage from 6787ms to 133ms ago:
I/ActivityManager( 1709): system_server: 18% = 18% user + 0% kernel
I/ActivityManager( 1709): adbd: 1% = 0% user + 1% kernel
I/ActivityManager( 1709): logcat: 0% = 0% user + 0% kernel
I/ActivityManager( 1709): kjournald: 0% = 0% user + 0% kernel
I/ActivityManager( 1709): +android.process.acore: 0% = 0% user + 0%
kernel
I/ActivityManager( 1709): TOTAL: 100% = 92% user + 7% kernel + 0% irq
+ 0% softirq
I/ActivityManager( 1709): Removing old ANR trace file from /data/anr/
traces.txt
D/HomeLoaders( 1855): --> starting applications loader
I/Process ( 1709): Sending signal. PID: 1855 SIG: 3
I/dalvikvm( 1855): threadid=7: reacting to signal 3
I/Process ( 1709): Sending signal. PID: 1833 SIG: 3
I/Process ( 1709): Sending signal. PID: 1820 SIG: 3
I/dalvikvm( 1820): threadid=7: reacting to signal 3
I/Process ( 1709): Sending signal. PID: 1785 SIG: 3
I/dalvikvm( 1785): threadid=7: reacting to signal 3
I/Process ( 1709): Sending signal. PID: 1805 SIG: 3
I/dalvikvm( 1805): threadid=7: reacting to signal 3
I/Process ( 1709): Sending signal. PID: 1765 SIG: 3
I/dalvikvm( 1765): threadid=7: reacting to signal 3
I/dalvikvm( 1833): threadid=7: reacting to signal 3
I/Process ( 1709): Sending signal. PID: 1709 SIG: 3
I/dalvikvm( 1709): threadid=7: reacting to signal 3
I/dalvikvm( 1765): Wrote stack trace to '/data/anr/traces.txt'
I/dalvikvm( 1805): Wrote stack trace to '/data/anr/traces.txt'
I/dalvikvm( 1785): Wrote stack trace to '/data/anr/traces.txt'
V/WindowManager( 1709): Delivering key 22 to Window{9e6fd388
com.android.launcher/com.android.launcher.Launcher paused=false}
W/KeyCharacterMap( 1867): Can't open keycharmap file
V/WindowManager( 1709): Waiting for next key: now=278209, repeat @
278898
W/KeyCharacterMap( 1867): Error loading keycharmap file '/system/usr/
keychars/AT_Translated_Set_2_keyboard.kcm.bin'. hw.keyboards.
0.devname='AT Translated Set 2 keyboard'
W/KeyCharacterMap( 1867): Can't open keycharmap file
E/KeyCharacterMap( 1867): Can't find any keycharmaps (also tried /
system/usr/keychars/qwerty.kcm.bin)
I/ActivityManager( 1709): Process android.process.acore (pid 1867) has
died.
I/WindowManager( 1709): WIN DEATH: Window{9e6fd388
com.android.launcher/com.android.launcher.Launcher paused=false}
V/WindowManager( 1709): releasePendingPointer null
V/WindowManager( 1709): finishedKey: client=android.view.IWindow$Stub
$pr...@9e6f9488, force=true
D/Zygote ( 1699): Process 1867 terminated by signal (11)
V/WindowManager( 1709): finishedKey:
client=android.os.binderpr...@9e6f9450, force=true,
last=android.os.binderpr...@9e6f9450 (token=
And in the console, it reports something link this:
binder: 1709:1735 transaction failed 29189, size 96-0
Seems the keyboard in qemu does not work normally.
Is there any one encounter such problem?
Any help is appreciated.
On May 21, 10:56 am, Alex <alex....@gmail.com> wrote:
> Thanks. It really makes sense.
> Alternatively, the following page says grub could be used to bring up
> the frame buffer.
> I have tried it, it does bring up the frame buffer. But seems too
> slow...(compare to virtualbox)
> Maybe the cause is lack of kqemu.
> I am using ubuntu 8.04, is theare anyone knowing how to install kqemu
> using apt-get?http://qemu-forum.ipi.fi/viewtopic.php?f=10&t=3913
>
> On May 21, 10:41 am, Chen Yang <sunsety...@gmail.com> wrote:
>
> > AFAIK, qemu doesn't support the vga= option with append,
> > You may need to patch the qemu for that
> > option:http://lists.gnu.org/archive/html/qemu-devel/2007-02/msg00269.html
> > Hope it helps!
> > --
> > Chen
>
> > On Thu, May 21, 2009 at 10:12 AM, Alex <alex....@gmail.com> wrote:
>
> > > Yes, oh, I forgot mentioning my qemu command.
> > > qemu -kernel bzImage -initrd rootfs.cpio.gz -hda system.img -dhdb
> > > userdata.img -append "console=tty0 console=ttyS1,115200n8 console=tty0
> > > androidboot.hardware=eee_701 vga=788"
>
> > > On May 21, 9:54 am, Chen Yang <sunsety...@gmail.com> wrote:
> > > > have you specified the vga=788 in the cmdline? The vesafb can only be
> > > > started when booting up.
> > > > --
> > > > Chen
>
> > > > On Wed, May 20, 2009 at 2:13 PM, Alex <alex....@gmail.com> wrote:
>
> > > > > I have installed android x86 eee_701 in VirtualBox successfuly.
> > > > > But the steps seem too repeated when I try to replace a kernel or
> > > > > system image.
> > > > > So I go to qemu emulator.
>
> > > > > The problem I encounter is, seems it always fails to bring up the
> > > > > frame buffer, I mean it always go to a purely blank screen.
>
> > > > > I tried 3 options in kernel frame buffer configuration.
> > > > > *****VESA VGA graphics support
> > > > > which fails to resize the qemu window, the logcat outputs continously:
>
> > > > > ID/AndroidRuntime( 1829): >>>>>>>>>>>>>> AndroidRuntime START
> > > > > <<<<<<<<<<<<<<
> > > > > D/AndroidRuntime( 1829): CheckJNI is ON
> > > > > D/AndroidRuntime( 1829): --- registering native functions ---
> > > > > E/Zygote ( 1829): Couldn't find preloaded-classes.
> > > > > D/dalvikvm( 1829): GC freed 618 objects / 28640 bytes in 16ms
> > > > > I/Zygote ( 1829): Preloading resources...
> > > > > D/dalvikvm( 1829): GC freed 95 objects / 2680 bytes in 5ms
> > > > > D/dalvikvm( 1829): GC freed 129 objects / 5192 bytes in 5ms
> > > > > D/dalvikvm( 1829): GC freed 340 objects / 14864 bytes in 7ms
> > > > > D/dalvikvm( 1829): GC freed 206 objects / 7976 bytes in 7ms
> > > > > I/Zygote ( 1829): ...preloaded 48 resources in 732ms.
> > > > > I/Zygote ( 1829): ...preloaded 15 resources in 34ms.
> > > > > D/dalvikvm( 1829): GC freed 117 objects / 7896 bytes in 7ms
> > > > > D/dalvikvm( 1829): GC freed 145 objects / 5488 bytes in 7ms
> > > > > D/dalvikvm( 1829): GC freed 36 objects / 1328 bytes in 6ms
> > > > > I/dalvikvm( 1829): Splitting out new zygote heap
> > > > > I/dalvikvm( 1829): System server process 1830 has been created
> > > > > I/Zygote ( 1829): Accepting command socket connections
> > > > > D/dalvikvm( 1830): Trying to load lib /system/lib/
> > > > > libandroid_servers.so 0x0
> > > > > D/dalvikvm( 1830): Added shared lib /system/lib/libandroid_servers.so
> > > > > 0x0
> > > > > I/sysproc ( 1830): Entered system_init()
> > > > > I/sysproc ( 1830): ServiceManager: 0x815ff00
> > > > > I/SurfaceFlinger( 1830): SurfaceFlinger is starting
> > > > > I/SurfaceFlinger( 1830): SurfaceFlinger's main thread ready to run.
> > > > > Initializing graphics H/W...
> > > > > E/MemoryHeapBase( 1830): error opening /dev/pmem: No such file or
> > > > > directory
> > > > > E/SurfaceFlinger( 1830): Couldn't open /sys/power/wait_for_fb_sleep
> > > > > or /sys/power/wait_for_fb_wake
> > > > > E/GLLogger( 1830): couldn't load <libhgl.so> library (Cannot find
> > > > > library)
> > > > > I/SurfaceFlinger( 1830): EGL informations:
> > > > > I/SurfaceFlinger( 1830): # of configs : 6
> > > > > I/SurfaceFlinger( 1830): vendor : Android
> > > > > I/SurfaceFlinger( 1830): version : 1.31 Android META-EGL
> > > > > I/SurfaceFlinger( 1830): extensions:
> > > > > I/SurfaceFlinger( 1830): Client API: OpenGL ES
> > > > > W/EGLDisplaySurface( 1830): FBIOPUT_VSCREENINFO failed, page flipping
> > > > > not supported
> > > > > W/EGLDisplaySurface( 1830): page flipping not supported
> > > > > (yres_virtual=480, requested=960)
> > > > > I/EGLDisplaySurface( 1830): using (fd=20)
> > > > > I/EGLDisplaySurface( 1830): id = VGA16 VGA
> > > > > I/EGLDisplaySurface( 1830): xres = 640 px
> > > > > I/EGLDisplaySurface( 1830): yres = 480 px
> > > > > I/EGLDisplaySurface( 1830): xres_virtual = 640 px
> > > > > I/EGLDisplaySurface( 1830): yres_virtual = 480 px
> > > > > I/EGLDisplaySurface( 1830): bpp = 4
> > > > > I/EGLDisplaySurface( 1830): r = 0:6
> > > > > I/EGLDisplaySurface( 1830): g = 0:6
> > > > > I/EGLDisplaySurface( 1830): b = 0:6
> > > > > I/EGLDisplaySurface( 1830): width = 102 mm (159.372547 dpi)
> > > > > I/EGLDisplaySurface( 1830): height = 76 mm (160.421050 dpi)
> > > > > I/EGLDisplaySurface( 1830): refresh rate = 68.38 Hz
> > > > > D/Zygote ( 1829): Process 1830 terminated by signal (8)
> > > > > I/Zygote ( 1829): Exit zygote because system server (1830) has
> > > > > terminated
> > > > > D/AndroidRuntime( 1849):
> > > > > D/AndroidRuntime( 1849): >>>>>>>>>>>>>> AndroidRuntime START
> > > > > <<<<<<<<<<<<<<
>
> > > > > *****VGA 16-color graphics support
> > > > > which resizes the windows of qemu, but logcat also output the above
> > > > > message...
>
> > > > > *****Cirrus logic support
> > > > > which fails to resize the windows of qemu, but logcat outputs the
> > > > > following message. Seems it has start up successfuly, just the frame
> > > > > buffer can not show anything.
>
> > > > > D/MountListener( 1698): handleEvent ums_disabled
> > > > > D/MountListener( 1698): handleEvent ums_disconnected
> > > > > D/MobileDataStateTracker( 1698): CONNECTED event did not supply
> > > > > interface name.
> > > > > D/MobileDataStateTracker( 1698): DNS server addresses are not known.
> > > > > D/dalvikvm( 1698): GC freed 4279 objects / 188160 bytes in 700ms
> > > > > D/HomeLoaders( 1739): load applications
> > > > > D/HomeLoaders( 1739): loading user items
> > > > > D/HomeLoaders( 1739): --> starting workspace loader
> > > > > I/ActivityManager( 1698): Start proc android.process.media for
> > > > > broadcast com.android.providers.downloads
>
> > > > > Has any successfully run android x86 in qemu? Or meet similar problem?
> > > > > Could you give me some help to fix it?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"android-porting" group.
To post to this group, send email to android-porting@googlegroups.com
To unsubscribe from this group, send email to
android-porting+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-porting?hl=en
-~----------~----~----~----~------~----~------~--~---
