platform reboot will originate from kernel side., can u enable complete logs and see whats last thing happened in kernel side? this might give us some clue.
#do it in init.rc or manually once android shell is up.. echo 8 > /proc/sys/kernel/printk On Mon, Mar 15, 2010 at 1:55 AM, Wolfram Hofmeister <[email protected]> wrote: > Logcat does unfortunately show nothing... at least nothing that is > linked with the crash.. > bugreport also shows nothing. > Yap someone else compiled my source, and everything worked fine. Even > on my phone. > I then made sure were using exactly the same commands. We do now. But > my kernel still reboots. Then I made sure we use the same environment > - same toolchain, same java version... but my kernels still reboot :-( > > Greetings, > Wolfram Hofmeister > > On Mar 14, 9:17 pm, Deva R <[email protected]> wrote: >> hi, >> - logcat would have been handy to nail down crashing component.. >> 'logcat -d' will dump last traces.. is that still void?? >> - btw, can you try the kernel binary working for someone else, and >> make sure your filesystem is ok? >> >> On Sat, Mar 13, 2010 at 9:00 PM, Wolfram Hofmeister >> >> >> >> <[email protected]> wrote: >> > Update: >> >> > I now installed Java 5 as I heard theer are problems with Java 6, but >> > my kernels still reboot :( >> > Please help me! >> >> > Greetings, >> > Wolfram Hofmeister >> >> > -- >> > unsubscribe: [email protected] >> > website:http://groups.google.com/group/android-porting > > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-porting > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
