Scribd Logo
Upload

Welcome to Scribd!

  • 5 views

    First Boot Log

    Uploaded by

    lucia.benito.sanz12
    This log file documents the startup process and boot events of a FactoryTest application. At startup, it checks for the existence of encryption keys and initialization files. When the device boots, it receives a boot completed intent and waits to connect to a client, then determines it is running in user mode. Similar events are logged on a subsequent reboot.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    First Boot Log

    Uploaded by

    lucia.benito.sanz12
    5 views1 page
    This log file documents the startup process and boot events of a FactoryTest application. At startup, it checks for the existence of encryption keys and initialization files. When the device boots, it receives a boot completed intent and waits to connect to a client, then determines it is running in user mode. Similar events are logged on a subsequent reboot.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    TXT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This log file documents the startup process and boot events of a FactoryTest application. At startup, it checks for the existence of encryption keys and initialization files. When the device boots, it receives a boot completed intent and waits to connect to a client, then determines it is running in user mode. Similar events are logged on a subsequent reboot.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    5 views1 page

    First Boot Log

    Uploaded by

    lucia.benito.sanz12
    This log file documents the startup process and boot events of a FactoryTest application. At startup, it checks for the existence of encryption keys and initialization files. When the device boots, it receives a boot completed intent and waits to connect to a client, then determines it is running in user mode. Similar events are logged on a subsequent reboot.

    Copyright:

    © All Rights Reserved
    Download as TXT, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as txt, pdf, or txt
    of 1

    08-17 10:19:36:342 FactoryTest : [FactoryTestBroadcastReceiver$ModuleCommon](12989)

    EFS_FACTORYAPP_ROOT PATH : /efs/FactoryApp/


    08-17 10:19:36:366 FactoryTest :
    [FactoryTestBroadcastReceiver$requestKeyStringBlock](12989) KEYSTRING_BLOCK is
    already existed...
    08-17 10:19:36:373 FactoryTest : [FactoryTestBroadcastReceiver$initFailhist](12989)
    Failhist Version is not V3
    08-17 10:19:36:379 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](12989)
    onReceive boot mode = 0
    08-17 10:19:37:794 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](12989)
    onReceive action=android.intent.action.BOOT_COMPLETED
    08-17 10:19:37:795 FactoryTest :
    [FactoryTestBroadcastReceiver$processIntentBootCompleted](12989) [MSP_SEQ][BOOTING
    COMPLETED][ING : received IntentBootCompleted -> waiting connect FtClient]
    08-17 10:19:37:803 FactoryTest : [FactoryTestBroadcastReceiver$ModuleCommon](12989)
    EFS_FACTORYAPP_ROOT PATH : /efs/FactoryApp/
    08-17 10:19:37:816 FactoryTest :
    [FactoryTestBroadcastReceiver$requestKeyStringBlock](12989) KEYSTRING_BLOCK is
    already existed...
    08-17 10:19:37:828 FactoryTest :
    [FactoryTestBroadcastReceiver$processIntentBootCompletedWhenUserBinary](12989) Boot
    completed, IS_FACTORY_BINARY = USER MODE
    08-17 10:19:37:863 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](12989)
    onReceive boot mode = 0
    10-24 16:30:12:803 FactoryTest : [FactoryTestBroadcastReceiver$ModuleCommon](13251)
    EFS_FACTORYAPP_ROOT PATH : /efs/FactoryApp/
    10-24 16:30:12:843 FactoryTest :
    [FactoryTestBroadcastReceiver$requestKeyStringBlock](13251) KEYSTRING_BLOCK is
    already existed...
    10-24 16:30:12:865 FactoryTest : [FactoryTestBroadcastReceiver$initFailhist](13251)
    Failhist Version is not V3
    10-24 16:30:12:872 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](13251)
    onReceive boot mode = 0
    10-24 16:30:15:827 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](13251)
    onReceive action=android.intent.action.BOOT_COMPLETED
    10-24 16:30:15:829 FactoryTest :
    [FactoryTestBroadcastReceiver$processIntentBootCompleted](13251) [MSP_SEQ][BOOTING:
    ][ING : received IntentBootCompleted -> waiting connect FtClient]
    10-24 16:30:15:839 FactoryTest : [FactoryTestBroadcastReceiver$ModuleCommon](13251)
    EFS_FACTORYAPP_ROOT PATH : /efs/FactoryApp/
    10-24 16:30:15:865 FactoryTest :
    [FactoryTestBroadcastReceiver$requestKeyStringBlock](13251) KEYSTRING_BLOCK is
    already existed...
    10-24 16:30:15:885 FactoryTest :
    [FactoryTestBroadcastReceiver$processIntentBootCompletedWhenUserBinary](13251) Boot
    completed, IS_FACTORY_BINARY = USER MODE
    10-24 16:30:15:973 FactoryTest : [FactoryTestBroadcastReceiver$onReceive](13251)
    onReceive boot mode = 0

    You might also like