The log file documents the startup process of a FactoryTest application on multiple dates. On startup, it checks the location of a root folder, verifies an existing key string block, and finds the failhist version is not V3. When it receives boot completed intents, it waits to connect to an FT client and determines the binary is running in user mode.
The log file documents the startup process of a FactoryTest application on multiple dates. On startup, it checks the location of a root folder, verifies an existing key string block, and finds the failhist version is not V3. When it receives boot completed intents, it waits to connect to an FT client and determines the binary is running in user mode.
The log file documents the startup process of a FactoryTest application on multiple dates. On startup, it checks the location of a root folder, verifies an existing key string block, and finds the failhist version is not V3. When it receives boot completed intents, it waits to connect to an FT client and determines the binary is running in user mode.
The log file documents the startup process of a FactoryTest application on multiple dates. On startup, it checks the location of a root folder, verifies an existing key string block, and finds the failhist version is not V3. When it receives boot completed intents, it waits to connect to an FT client and determines the binary is running in user mode.