Hi Weston, Its a Framework reboot issue. You need to collect ADB logs from the boot up.
adb logcat -v threadtime > logcat.txt adb shell cat /proc/kmsg > kernellogs.txt ............. adb bugreport > bugreport.txt ................ Make sure you clear below things at the beginning /data/anr/* /data/tombstone/* Pull the traces and tombstone files from the /data/anr and /data/tombstone adb pull /data/anr/ . adb pull /data/tombstone . Note: You can save in any folder by logging it outside the adb shell prompt Search for the time stamp where you encountered the Framework reboot. Map it appropriately with the traces/tombstones to find the issue. *Note: There is one more method of capturing the logs in the sdcard. With the same set of commands by routing it to /sdcard and then pulling it after hitting that issue.* Thanks, Abdul Haseeb On Sun, Oct 21, 2012 at 8:39 PM, Weston Weems <wwe...@gmail.com> wrote: > With the exception of earlyprintk and logwrapper stuff, is there anything > I can do to diagnose a booting problem? I am getting "an untracked pid > exitted" and get stuck at the android logo. > > Any ideas? > > Weston > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
