That's what I've been lead to believe, the phone never reaches initialization state. I'll check my init.rc and init.tuna.rc to see if I have the same line of code.
However, what file do you edit to enable "earlyprintk"? I've opened the kernel config menu with "make", but could only find under "kernel hacking" the option for "dynamic printk" no earlyprintk which is actually what I want from the phone/emulator. On Wednesday, July 25, 2012 2:38:05 PM UTC-4, Giveen wrote: > > In your init.rc you should have adb set up for it. > Maybe its stuck on a point before gets to activating adb > For example on my init.rc I have this (Jelly Bean port on CM10) > > # adbd is controlled via property triggers in init.<platform>.usb.rc > service adbd /sbin/adbd > class core > disabled > > > > > > On Wed, Jul 25, 2012 at 12:25 PM, Jason Shim <[email protected]> wrote: > >> Hi, >> >> You can enable early printk from config option. >> >> Thanks, >> Jason >> >> On Wed, Jul 25, 2012 at 11:20 AM, 9exceptionThrower9 <[email protected] >> > wrote: >> >>> But what if your phone or emulator gets stuck in a "boot-loop"? It >>> seems that ADB only works if the ADB daemon can detect the phone or >>> device/emulator. I've tried "$ ./adb logtcat" before, but it hangs b/c it >>> cannot detect the device. >>> >>> I've tried using the phone's emulator as a work-a-round: however, upon >>> running the adb server I get the following error: >>> error: device offline >>> >>> I've tried killing adb server, rebooting it, and then running "$ ./adb >>> devices" to get: >>> * daemon not running. starting it now on port 5037 * >>> * daemon started successfully * >>> List of devices attached >>> emulator-5554 offline >>> >>> Is there a way to turn the phone online? >>> >>> >>> On Wednesday, July 25, 2012 2:05:49 PM UTC-4, Giveen wrote: >>>> >>>> adb logcat > logcat.txt >>>> >>>> Thats how I do it. Look up how to use the 'adb' tool. >>>> >>>> On Wed, Jul 25, 2012 at 8:55 AM, 9exceptionThrower9 < >>>> [email protected]> wrote: >>>> >>>>> I've been trying various methods on getting some kind of debugging log >>>>> from one of these three phones as they boot up. >>>>> >>>>> I've read that the "init" process produces a boot log, and some kernel >>>>> messages are produced and can be found via "strace" and such. However, >>>>> does this mean that you can only access these phone logs (from boot mode >>>>> onward) if the phone makes it to a stable state? >>>>> >>>>> What if the phone crashes during the "Google" splash-screen? Is there >>>>> any way to get some kind of boot log or error log or messages from the >>>>> phone to the terminal or to an output file as it boots up? How far does >>>>> the phone need to get in the boot process before any kind of log could be >>>>> accessed? >>>>> >>>>> When the kernel is loaded into memory after the main bootloader stage, >>>>> does it produce logs that can be accessed? That is, it does not just >>>>> simply produce log messages that are only found in the phone's file >>>>> system >>>>> but somewhere perhaps on the computer the phone is plugged into via USB. >>>>> Is there any way to configure this if it doesn't do so anyway? >>>>> >>>>> Thank you. >>>>> >>>>> -- >>>>> unsubscribe: >>>>> android-kernel+unsubscribe@**googlegroups.com<android-kernel%[email protected]> >>>>> website: >>>>> http://groups.google.com/**group/android-kernel<http://groups.google.com/group/android-kernel> >>>> >>>> >>>> -- >>> unsubscribe: [email protected] >>> website: http://groups.google.com/group/android-kernel >>> >> >> >> >> -- >> Jason Shim >> Software Engineer, Motorola, Inc >> >> -- >> unsubscribe: [email protected] >> website: http://groups.google.com/group/android-kernel >> > > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
