It seems that your UI is up already. Are you sure you don't see a
Android screen? So time, it takes a while for the screen to come up
depends on your real hardware.
On Fri, 2009-04-24 at 00:39 -0700, kjwdelicious wrote:
> OK. I found logcat.
> It's cool~!
>
> I looked log.
> And I found permission errors on /system/app/*.apk
> So I applied chmod 777 /system/app/*
>
> Then I looked log again.
> I attached part of it below.
> I think sound driver is a problem.
> And it seems that the Android is waiting for a uer key input.
>
>
> -------------------------------------------------------------------------------------------------------------------------
> 1 V/WindowManager( 1890): Waiting for next key: now=28410,
> repeat @ 29159
> 2 V/WindowManager( 1890): Event: type=1 data=KeyEvent{action=1
> code=40 repeat=0 meta=0 scancode=38
>
> mFlags=9}
> 3 V/WindowManager( 1890): Received key up: ignore repeat @
> 10027473
> 4 V/WindowManager( 1890): Dispatch key: KeyEvent{action=1
> code=40 repeat=0 meta=0 scancode=38 mFlags=9}
> 5 V/WindowManager( 1890): waitForLastKey: mFinished=true,
> mLastWin=null
> 6 I/WindowManager( 1890): Enter to find the targeted windows
> 7 V/WindowManager( 1890): Skipping event; no focused app:
> KeyEvent{action=1 code=40 repeat=0 meta=0
>
> scancode=38 mFlags=9} null
> 8 W/WindowManager( 1890): No focus window, dropping: KeyEvent
> {action=1 code=40 repeat=0 meta=0
>
> scancode=38 mFlags=9}
> 9 V/WindowManager( 1890): Waiting for next key: now=28474,
> repeat @ 10027473
> 10 V/WindowManager( 1890): Event: type=1 data=KeyEvent{action=0
> code=67 repeat=0 meta=0 scancode=14
>
> mFlags=9}
> 11 V/WindowManager( 1890): Received key down: first repeat @
> 29454
> 12 V/WindowManager( 1890): Dispatch key: KeyEvent{action=0
> code=67 repeat=0 meta=0 scancode=14 mFlags=9}
> 13 V/WindowManager( 1890): waitForLastKey: mFinished=true,
> mLastWin=null
> 14 I/WindowManager( 1890): Enter to find the targeted windows
> 15 V/WindowManager( 1890): Skipping event; no focused app:
> KeyEvent{action=0 code=67 repeat=0 meta=0
>
> scancode=14 mFlags=9} null
> 16 W/WindowManager( 1890): No focus window, dropping: KeyEvent
> {action=0 code=67 repeat=0 meta=0
>
> scancode=14 mFlags=9}
>
> ..............
> 204 I/ServiceManager( 1890): Waiting for sevice
> media.audio_flinger..
>
> ...............
> 399 W/AudioSystem( 1890): AudioFlinger not published, waiting...
> 400 V/WindowManager( 1890): Event: type=1 data=KeyEvent{action=1
> code=67 repeat=0 meta=0 scancode=14
>
> mFlags=9}
> 401 V/WindowManager( 1890): Received key up: ignore repeat @
> 10032138
> 402 V/WindowManager( 1890): Dispatch key: KeyEvent{action=1
> code=67 repeat=0 meta=0 scancode=14 mFlags=9}
> -------------------------------------------------------------------------------------------------------------------------
>
>
> On 4월24일, 오후4시02분, Yi Sun <[email protected]> wrote:
> > On Thu, 2009-04-23 at 23:59 -0700, kjwdelicious wrote:
> > > Thnks again.
> >
> > > I'm sorry but actually I don't know what the logcat is.
> >
> > Run /system/bin/logcat It seems that you don't have a framebuffer issue.
> > But it seems that your processes are crashed (event media server) for
> > some reason.
> >
> >
> >
> > > And I got this when I type 'cat /proc/fb'
> > > 0 Intel(R) 865G
> >
> > > Is there anything I can do to help you?
> >
> > > On 4월24일, 오후3시49분, Yi Sun <[email protected]> wrote:
> > > > The output of logcat may help.
> > > > BTW-- could you do "cat /proc/fb" as well?
> >
> > > > On Thu, 2009-04-23 at 23:26 -0700, kjwdelicious wrote:
> > > > > Thankyou for your quick response.
> >
> > > > > 1. fb
> > > > > I'm sorry but I don't know which framebuffer driver is used in case of
> > > > > Ubutnu using X server.
> > > > > I just read X server is able to access graphic hardware without help
> > > > > of framebuffer driver.
> >
> > > > > 2. i865G
> > > > > Anyway I use i865G graphic hardware and it works when I loaded intelfb
> > > > > driver.
> >
> > > > > 3. alt+f1
> > > > > Wow I din't know if it works.
> > > > > After that I typed ps and I found these including zygote
> > > > > ------------------------------------------------------------------------------------------------------------------------
> > > > > /system/bin/sh
> > > > > /sbin/adbd
> > > > > /system/bin/servicemanager
> > > > > /system/bin/vold
> > > > > zygote /bin/app_process -Xzygote /system/bin --zygote --start-system-
> > > > > server
> > > > > /system/bin/installd
> > > > > system_server
> > > > > ------------------------------------------------------------------------------------------------------------------------
> >
> > > > > 4. 5. log
> > > > > I checked dmesg but it looks same to my previous wrting.
> >
> > > > > Can you please figure this out?
> >
> > > > > On 4월24일, 오후3시07분, Yi Sun <[email protected]> wrote:
> > > > > > Ok, a few questions/steps:
> > > > > > 1. when you run a standard linux (like ubuntu), what kind of fb are
> > > > > > you
> > > > > > using?
> > > > > > 2. could you give more detail about your PC env? What kind of the
> > > > > > vido
> > > > > > card it has?
> > > > > > 3. boot with zygote, and do alt+f1 to see if you can switch to
> > > > > > console.
> > > > > > 4. if you can switch to console, then try to get logcat output.
> > > > > > 5. dmesg also helps
> >
> > > > > > On Thu, 2009-04-23 at 22:52 -0700, kjwdelicious wrote:
> > > > > > > I'm trying to port Android for Intel X86 desktop PC.
> > > > > > > I though it could be possible, because someone already have
> > > > > > > ported to
> > > > > > > ASUS eee701 which is X86 based.
> >
> > > > > > > I followed like this.
> > > > > > >http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/B...
> >
> > > > > > > And applied patch from here.
> > > > > > >http://code.google.com/p/patch-hosting-for-android-x86-support/downlo...
> >
> > > > > > > The only different thing I've done is inserting intelfb driver to
> > > > > > > kernel image instead of building as a module. And I check it
> > > > > > > works by
> > > > > > > checking /sys/class/graphics/fb0.
> >
> > > > > > > Anyway I've booted with new built kernel and rootfs both for
> > > > > > > eee701.
> > > > > > > But during the boot, screen goes black seems to be dead.
> >
> > > > > > > I think something wrong on invoking zygote.
> >
> > > > > > > And I tested like this.
> > > > > > > When I just commented out the zygote invoking part in init.rc
> > > > > > > shell
> > > > > > > command came up.
> > > > > > > And following process could be found but mediaserver.
> > > > > > > - servicemanager, vold, installd, adbd
> >
> > > > > > > Error message below comes up repeatedly.
> > > > > > > ------------------------------------------------------------------------------
> > > > > > > init: event { 'add', '/kernel/uids/1013', 'uids', '', -1, -1 }
> > > > > > > init: waitpid returned pid 2003, status = 00007f00
> > > > > > > init: process 'media', pid 2003, exited
> > > > > > > init: process 'media' killing any children in process group
> > > > > > > init: event { 'remove', '/kernel/uids/1013', 'uids', '', -1, -1 }
> > > > > > > ------------------------------------------------------------------------------
> >
> > > > > > > So I think zygote and mediaserver are not working properly.
> > > > > > > Please help me out~! >,<- 따온 텍스트 숨기기 -
> >
> > > > > > - 따온 텍스트 보기 -- 따온 텍스트 숨기기 -
> >
> > > > - 따온 텍스트 보기 -- 따온 텍스트 숨기기 -
> >
> > - 따온 텍스트 보기 -
> >
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
