would you like to provide the messages before the not responding?
The home application may have met some issues.
--
Chen
On Thu, Apr 16, 2009 at 8:46 AM, Zia <zia.cha...@gmail.com> wrote:
>
> ok i think I just broke something. The Android HomeScreen doesnt'
> respond to keyboard events now. Though I can Alt+F1 to console and
> back. I can see events in the logcat as well. Any ideas? :(
>
> 04-16 00:45:52.151: VERBOSE/WindowManager(2037): Event: type=1
> data=KeyEvent{action=0 code=0 repeat=0 meta=0 scancode=28 mFlags=9}
> 04-16 00:45:52.151: VERBOSE/WindowManager(2037): Received key down:
> first repeat @ 134699
> 04-16 00:45:52.151: VERBOSE/WindowManager(2037): Dispatch key: KeyEvent
> {action=0 code=0 repeat=0 meta=0 scancode=28 mFlags=9}
> 04-16 00:45:52.151: VERBOSE/WindowManager(2037): waitForLastKey:
> mFinished=true, mLastWin=null
> 04-16 00:45:52.151: INFO/WindowManager(2037): Enter to find the
> targeted windows
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): Dispatching to Window
> {9e6e6f10 paused=false}: KeyEvent{action=0 code=0 repeat=0 meta=0
> scancode=28 mFlags=9}
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): Delivering key 0 to
> Window{9e6e6f10 paused=false}
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): Waiting for next key:
> now=133950, repeat @ 134699
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): finishedKey:
> client=android.view.viewroo...@9e6e6bb8, force=false
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): finishedKey:
> client=android.view.viewroo...@9e6e6bb8, force=false,
> last=android.view.viewroo...@9e6e6bb8 (token=WindowToken{9e6cc0f8
> token=null})
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): finishedKey: last
> paused=false
> 04-16 00:45:52.152: VERBOSE/WindowManager(2037): releasePendingPointer
> null
> 04-16 00:45:52.231: VERBOSE/WindowManager(2037): Event: type=1
> data=KeyEvent{action=1 code=0 repeat=0 meta=0 scancode=28 mFlags=9}
> 04-16 00:45:52.231: VERBOSE/WindowManager(2037): Received key up:
> ignore repeat @ 10133029
> 04-16 00:45:52.231: VERBOSE/WindowManager(2037): Dispatch key: KeyEvent
> {action=1 code=0 repeat=0 meta=0 scancode=28 mFlags=9}
> 04-16 00:45:52.231: VERBOSE/WindowManager(2037): waitForLastKey:
> mFinished=true, mLastWin=null
> 04-16 00:45:52.231: INFO/WindowManager(2037): Enter to find the
> targeted windows
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): Dispatching to Window
> {9e6e6f10 paused=false}: KeyEvent{action=1 code=0 repeat=0 meta=0
> scancode=28 mFlags=9}
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): Delivering key 0 to
> Window{9e6e6f10 paused=false}
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): Waiting for next key:
> now=134030, repeat @ 10133029
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): finishedKey:
> client=android.view.viewroo...@9e6e6bb8, force=false
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): finishedKey:
> client=android.view.viewroo...@9e6e6bb8, force=false,
> last=android.view.viewroo...@9e6e6bb8 (token=WindowToken{9e6cc0f8
> token=null})
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): finishedKey: last
> paused=false
> 04-16 00:45:52.232: VERBOSE/WindowManager(2037): releasePendingPointer
> null
>
>
> On Apr 15, 4:21 pm, Zia <zia.cha...@gmail.com> wrote:
>> Got the keyboard working. The files in /system/usr/keychars were not
>> 0644. chmod 0644 fixes the keyboard. However, the I still dont see
>> mousecursor.
>>
>> Thanks,
>>
>> Zia
>>
>> On Apr 15, 4:14 pm, Zia <zia.cha...@gmail.com> wrote:
>>
>> > You are correct. I was missing
>> > setprop ro.HOME_APP_MEM 4096
>> > in the init.rc .
>>
>> > Now I get the new Android UI. However, my keyboard and mouse doesn't
>> > work with the UI. I've Dell USB keyboard and mouse, and in the logcat
>> > I can see the both keyboard and mouse event being fired. However, in
>> > the UI only the RETURN key responds. For the rest of the keystrokes
>> > the screen flashes. No errors in the logcat neither.
>>
>> > Any ideas?
>>
>> > Thanks,
>>
>> > Zia
>>
>> > On Apr 15, 3:41 pm, Yi Sun <beyo...@gmail.com> wrote:
>>
>> > > I remember that I add two setprop lines.
>> > > Anyway, check the line where it crashed and see what you are missing.
>> > > Yi
>>
>> > > On Wed, 2009-04-15 at 15:31 -0700, Zia wrote:
>> > > > I do have
>> > > > setprop ro.HOME_APP_ADJ 4
>>
>> > > > added to init.rc .
>>
>> > > > On Apr 15, 3:26 pm, Zia <zia.cha...@gmail.com> wrote:
>> > > > > I applied all the patches and now getting libhgl.so errors. How did
>> > > > > you guys resolve this one?
>>
>> > > > > 04-15 22:25:29.569: ERROR/GLLogger(2081): couldn't load <libhgl.so>
>> > > > > library (Cannot find library)
>> > > > > 04-15 22:25:29.601: WARN/dalvikvm(2081): threadid=19: thread exiting
>> > > > > with uncaught exception (group=0xb003fdf8)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): Uncaught handler:
>> > > > > thread ActivityManager exiting due to uncaught exception
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): *** EXCEPTION IN
>> > > > > SYSTEM PROCESS. System will crash.
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081):
>> > > > > java.lang.NumberFormatException: unable to parse '' as integer
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > java.lang.Integer.parseInt(Integer.java:364)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > java.lang.Integer.parseInt(Integer.java:333)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > java.lang.Integer.valueOf(Integer.java:590)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > com.android.server.am.ActivityManagerService.<init>
>> > > > > (ActivityManagerService.java:1303)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > com.android.server.am.ActivityManagerService.<init>
>> > > > > (ActivityManagerService.java:110)
>> > > > > 04-15 22:25:29.601: ERROR/AndroidRuntime(2081): at
>> > > > > com.android.server.am.ActivityManagerService$AThread.run
>> > > > > (ActivityManagerService.java:1130)
>> > > > > 04-15 22:25:29.611: ERROR/AndroidRuntime(2081): Crash logging
>> > > > > skipped,
>> > > > > no checkin service
>>
>> > > > > Thanks,
>>
>> > > > > Zia
>>
>> > > > > On Apr 15, 2:03 pm, Yi Sun <beyo...@gmail.com> wrote:
>>
>> > > > > > Go to code.google.com/patch-hosting-for-android-x86-support/ to
>> > > > > > download all the patches u need
>>
>> > > > > > On Apr 15, 2009, at 1:15 PM, Zia <zia.cha...@gmail.com> wrote:
>>
>> > > > > > > Brian,
>>
>> > > > > > > I'm having the similar problem. Did you find a fix for it?
>>
>> > > > > > > Thanks,
>>
>> > > > > > > Zia
>>
>> > > > > > > On Apr 1, 9:05 pm, Brian <bgc...@gmail.com> wrote:
>> > > > > > >> The system is trying to runzygote, but I got the following
>> > > > > > >> error.
>> > > > > > >> I'm attaching my logcat output.
>>
>> > > > > > >> E/Zygote ( 2126):Zygotediedwithexception
>> > > > > > >> E/Zygote ( 2126): java.lang.IllegalStateException: Missing
>> > > > > > >> class(es)
>> > > > > > >> for preloading, update preloaded-classes
>> > > > > > >> [com.android.internal.policy.impl.PhoneLayoutInflater
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow$1
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow$ContextMenuCallback
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow$DecorView
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow$PanelFeatureState
>> > > > > > >> com.android.internal.policy.impl.PhoneWindow$PanelFeatureState
>> > > > > > >> $SavedState com.android.internal.policy.impl.PhoneWindow
>> > > > > > >> $PanelFeatureState$SavedState$1]
>> > > > > > >> E/Zygote ( 2126): at
>> > > > > > >> com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:
>> > > > > > >> 299)
>> > > > > > >> E/Zygote ( 2126): at
>> > > > > > >> com.android.internal.os.ZygoteInit.main
>> > > > > > >> (ZygoteInit.java:512)
>> > > > > > >> E/Zygote ( 2126): at dalvik.system.NativeStart.main(Native
>> > > > > > >> Method)
>> > > > > > >> D/AndroidRuntime( 2126): Shutting down VM
>> > > > > > >> W/dalvikvm( 2126): threadid=3: thread exiting with
>> > > > > > >> uncaughtexception
>> > > > > > >> (group=0xb00dfdf8)
>> > > > > > >> D/dalvikvm( 2126): DestroyJavaVM waiting for non-daemon threads
>> > > > > > >> to
>> > > > > > >> exit
>> > > > > > >> D/dalvikvm( 2126): DestroyJavaVM shutting VM down
>> > > > > > >> D/dalvikvm( 2126): VM cleaning up
>> > > > > > >> D/dalvikvm( 2126): LinearAlloc 0x0 used 2087468 of 4194304 (49%)
>> > > > > > >> D/skia ( 2126): purging 6K from font cache [1 entries]
>>
>> > > > > > >> Any suggestion?
>>
>> > > > > > >> Thanks,
>> > > > > > >> Brian
>> > > > > > >> On Apr 1, 5:13 pm, Chen Yang <sunsety...@gmail.com> wrote:
>>
>> > > > > > >>> Cool. It seems that you don't have the essential
>> > > > > > >>> process:zygote. You
>> > > > > > >>> can check the logcat messages to see what was happenning.
>> > > > > > >>> Thanks.
>> > > > > > >>> --
>> > > > > > >>> Chen
>>
>> > > > > > >>> On Thu, Apr 2, 2009 at 8:09 AM, Brian <bgc...@gmail.com> wrote:
>>
>> > > > > > >>>> Hi all,
>>
>> > > > > > >>>> I finally managed to boot android x86 with vga=788 option
>> > > > > > >>>> without
>> > > > > > >>>> black screen in vmware.
>> > > > > > >>>> Thanks for all the help!
>>
>> > > > > > >>>> I'm trying to go to the next step.
>> > > > > > >>>> Even with vga=788 option, I don't see GUI. Why? Instead, I
>> > > > > > >>>> get a
>> > > > > > >>>> shell
>> > > > > > >>>> prompt.
>> > > > > > >>>> Here's the list of system processes stored under /system/bin/.
>> > > > > > >>>> /system/bin/sh
>> > > > > > >>>> /system/bin/servicemanager
>> > > > > > >>>> /system/bin/mountd
>> > > > > > >>>> /system/bin/mediaserver
>> > > > > > >>>> /system/bin/installd
>>
>> > > > > > >>>> I tried to do "ADBHOST=<ip> adb install app.apk", but I got
>> > > > > > >>>> the
>> > > > > > >>>> following error "Error: Could not access the Package Manager.
>> > > > > > >>>> Is
>> > > > > > >>>> the
>> > > > > > >>>> system running?".
>>
>> > > > > > >>>> I'd like to install this application with GUI and to start it.
>> > > > > > >>>> How can
>> > > > > > >>>> I do it?
>>
>> > > > > > >>>> Thanks,
>> > > > > > >>>> Brian
>>
>> > > > > > >>>> On Mar 30, 10:54 pm, Brian <bgc...@gmail.com> wrote:
>> > > > > > >>>>> Hi Chen,
>>
>> > > > > > >>>>> I managed to compile kernel 2.6.25.
>> > > > > > >>>>> When I ran it without vga=788, I see a shell prompt.
>> > > > > > >>>>> The screen does not go to black one.
>> > > > > > >>>>> But I keep getting the following message.
>> > > > > > >>>>> [timestamp] android_power: wakeup (0->0) at ...
>> > > > > > >>>>> (Btw, how can I turn off this message?)
>>
>> > > > > > >>>>> I still have a problem with vga=788.
>> > > > > > >>>>> This time I'm getting a kernel panic, which I'm attaching.
>> > > > > > >>>>> Has anyone seen this problem? What's a proper approach to
>> > > > > > >>>>> address this
>> > > > > > >>>>> problem?
>>
>> > > > > > >>>>> Thanks,
>> > > > > > >>>>> Brian
>>
>> > > > > > >>>>> Process netcfg (pid: 2031, ti=cf17c000 task=cf3001b0
>> > > > > > >>>>> task.ti=cf17c000)
>> > > > > > >>>>> Stack: ...
>>
>> > > > > > >>>>> Call Trace:
>> > > > > > >>>>> [<c01f12f2>] ? cursor_timer_handler+0x28/0x2b
>> > > > > > >>>>> ? run_timer_softirq+0x11d/0x176
>> > > > > > >>>>> ? cursor_timer_handler+0x0/0x2b
>> > > > > > >>>>> ? __do_softirq+0x70/0xd5
>> > > > > > >>>>> ? do_softirq+0x35/0x3a
>> > > > > > >>>>> ? local_bh_enable_ip+0x38/0x4f
>> > > > > > >>>>> ? _spin_unlock_bh+0x17/0x19
>> > > > > > >>>>> ? dev_set_rx_mode+0x38/0x3c
>> > > > > > >>>>> ? dev_open+0x60/0x7e
>> > > > > > >>>>> ? dev_change_flags+0x9f/0x154
>> > > > > > >>>>> ? devinet_ioctl+0x2da/0x5f8
>> > > > > > >>>>> ? inet_ioctl+0x93/0xaf
>> > > > > > >>>>> ? sock_ioctl+0x1af/0x1d1
>> > > > > > >>>>> ? sock_ioctl+0x0/0x1d1
>> > > > > > >>>>> ? vfs_ioctl+0x22/0x69
>> > > > > > >>>>> ? do_vfs_ioctl+0x222/0x235
>> > > > > > >>>>> ? sys_socketcall+0x51/0x168
>> > > > > > >>>>> ? sys_ioctl+0x40/0x5a
>> > > > > > >>>>> ? syscall_call+0x7/0xb
>> > > > > > >>>>> Code: ....
>> > > > > > >>>>> EIP: [<c012b22a>] mod_timer+0x9/0x27 SS:ESP 0068:cf17de18
>> > > > > > >>>>> Kernel panic - not syncing: Fatalexceptionin interrupt
>>
>> > > > > > >>>>> On Mar 30, 8:49 am, Brian <bgc...@gmail.com> wrote:
>>
>> > > > > > >>>>>> Thanks, Jerry!
>>
>> > > > > > >>>>>> I'm using kernel 2.6.27, and the modules have version
>> > > > > > >>>>>> 2.6.25 as
>> > > > > > >>>>>> you
>> > > > > > >>>>>> can see below.
>> > > > > > >>>>>> There are inconsistencies in the cupcake branch.
>>
>> > > > > > >>>>>> I will either get kernel 2.6.25 or try to compile 2.6.27
>> > > > > > >>>>>> modules.
>>
>> > > > > > >>>>>> Thanks,Brian
>>
>> > > > > > >>>>>> ./kernel/include/config/kernel.release:2.6.27-00120-g453dc2b-
>> > > > > > >>>>>> dirty
>>
>> > > > > > >>>>>> $ modinfo ./out/target/product/eee_701/rootimg/lib/modules/
>> > > > > > >>>>>> i915.ko
>> > > > > > >>>>>> filename:
>> > > > > > >>>>>> ./out/target/product/eee_701/rootimg/lib/modules/
>> > > > > > >>>>>> i915.ko
>> > > > > > >>>>>> license: GPL and additional rights
>> > > > > > >>>>>> description: Intel Graphics
>> > > > > > >>>>>> author: Tungsten Graphics, Inc.
>> > > > > > >>>>>> license: GPL
>>
>> ...
>>
>> read more »
> >
>
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
