I'm facing the same problem on my s3c6410 board, before the screen go into blank, i got the following logcat: * * I/watchdog_pss_stats( 64): [23924736,8,2597888,1,0,0,10753024,2,30875648,2,0] I/watchdog_proc_stats( 64): [1,1,1,1,1] I/watchdog_meminfo( 64): [12738560,20480,29396992,47587328,51159040,69373952,22265856,5578752,1404928,4173824,4857856] I/watchdog_vmstat( 64): [7250097,173829,15041,25682,289156,2880] I/watchdog_proc_pss( 64): [system,64,12361728] I/watchdog_proc_pss( 64): [com.android.phone,126,4033536] I/dvm_gc_info( 64): [8320808730293847748,-8919795260053104577,-4005807934825351131,8165193] I/dvm_gc_madvise_info( 64): [446464,335872] I/dvm_gc_info( 375): [7093854921883502205,-8913884560487540691,-4014252184126670811,7599809] I/dvm_gc_madvise_info( 375): [1646592,319488] I/dvm_gc_info( 375): [7093854921883534972,-8917262260208064467,-4014252184126670811,7599809] I/dvm_gc_madvise_info( 375): [1679360,319488] I/power_sleep_requested( 64): 0 I/power_screen_state( 64): [0,1,66149,357] I/power_screen_broadcast_send( 64): 1 I/screen_toggled( 64): 0 I/am_pause_activity( 64): [1137308128,com.android.browser/.BrowserActivity] I/am_on_paused_called( 375): com.android.browser.BrowserActivity I/power_screen_broadcast_done( 64): [0,240,1] I/dvm_gc_info( 64): [8320808730292123198,-8992978753997875137,-4002993185058244571,8165315] I/power_screen_state( 64): [1,2,0,0] I/power_screen_broadcast_send( 64): 1 I/screen_toggled( 64): 1 I/am_resume_activity( 64): [1137308128,4,com.android.browser/.BrowserActivity] I/am_on_resume_called( 375): com.android.browser.BrowserActivity I/power_screen_broadcast_done( 64): [1,165,1] I/dvm_gc_madvise_info( 64): [471040,335872] I/power_screen_state( 64): [0,2,0,0] I/power_screen_broadcast_send( 64): 1 I/screen_toggled( 64): 0 I/am_pause_activity( 64): [1137308128,com.android.browser/.BrowserActivity] I/am_on_paused_called( 375): com.android.browser.BrowserActivity I/power_screen_broadcast_done( 64): [0,407,1]
any guess? 2010/7/23 xift <mpurw...@gmail.com> > Try adb logcat... You will find errormessages there. > My guess is that NetdConnector hangs (Thats my problem at the moment) > because vold socket cannot be read. > The white screen should propably be black (screenstate 0). Thats just > a setting. > > For which device are you porting? > > On 22 Jul., 19:27, thirumalai Pachamuthu > <thirumalai.andr...@gmail.com> wrote: > > Hi, > > I am trying to boot froyo on my target. Target is able to boot the > kernel > > and i can able to use the target using adb shell but GUI is not coming. > The > > target screen is just white screen nothing is coming on the screen. > > What might went wrong? Any ways to debug further. > > -Thirumalai > > -- > unsubscribe: > android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
