A) W1245.

4 OSK (STE) ============ (Guided to customer on 461921)

And for getting boot-up trace log, please check steps below.

[1] Update modem_log_relay (ADB connection is needed) (command window on your PC) adb shell stop modem_log_relay exit

adb remount adb push modem_log_relay /system/bin/modem_log_relay (--> file is attached 'modem_log_relay.zip', need to modify location of modem_log_relay file)

adb shell chmod 777 /system/bin/modem_log_relay start modem_log_relay

[2] Power off and Power on rpt_host_2012_xxx (or rpt_boot_2012_xxx) file is generated on each boot-up

[3] Getting trace log file by ADB adb pull /data/log/boot_trigger C:/golden_log

*No need to change in trace_auto.conf (please ignore previous method) *Generated trigger will be stored in /data/log/boot_trigger *Binary will generate a trigger on each boot-up (not possible to disable) --> So, please use attached 'modem_log_relay.zip' only for getting boot-up trace log purpose, do not merge on mainstream of your project

B) W1247.4 OSK (STE) ============ (guide comment to customer for getting REAL boot-up log by FIDO box on GOLDEN, ER 461621)

On current trace configuration of GOLDEN, there is a gap (missing trace messages) on boot-up trace log, when using FIDO box. This limitation is due to microSD card slot is not easy to use on GOLDEN project (under battery slot).

If FIDO box trace logging is available, please check steps below for getting boot-up trace log and all power-off/power-on procedure.

[1] Edit modem.env // this step should be done

On modem.bin file, modem.env file is included. When you open it by text editor,

TRACE_DEFAULT_TRACE_ROUTING=1,2

Please change this parameter as below

TRACE_DEFAULT_TRACE_ROUTING=1,3

This means Trace route change (on boot-step) from BUFFER (inside UE memory) to XTI / BUFFER (both inside UE memory and external way, FIDO box), --> This step needs re-packing of modem.bin (new modem.bin needs to be made), and re-flashing to UE. Please contact software management team on customer side for details.

[2] Change mode // same as previous

// Write 2 in chmod_field adb shell echo -en "2" > /mnt/.lfs/chmod_field

// Check content of chmod_field is 2 # cat /mnt/.lfs/chmod_field // 2 expected

[3] STP in trace_auto.conf // same as previous

// Pull trace_auto.conf file adb pull /modemfs/trace_auto.conf c:/temp/

// Edit this file by text editor and save, BUFFER to STP dump -D FS /data/log/err dump -l 10 trigger -D /data/log/err trigger -l 0 trace -l ON 100 30 trace -u OFF trace -t STP trigger -m OFF // --> from "trace -t BUFFER" to "trace -t STP"

AUTOSTART 0 trace -D SDCARD /sdcard/modem_trace

// Push trace_auto.conf file adb push c:/temp/trace_auto.conf file /modemfs/

[4] Reboot

[5] How to use NTrace tool // same as previous Please check attached document (mini_How_to_Use_Ntrace_FIDObox_onJANICE_0.2.zip).

*Please use this method (and modme.bin binary) only for this issue purpose. Do not merge on mainstream of your project. *"modem_log_relay" method is only for getting short boot-up period (from power-on to around 9 seconds) by one file, automatically. So, there may be trace log discontiuity.

C) W1248.1 OSK (STE) ============ (/Updated/ How to get boot-up log without FIDO box - ER 468329)

Due to limitation of mini-SD card slot, there is a detour. Please check follwoing steps for getting boot-up log without FIDO box.

There are two big categories.

- modem_log_relay : from power-on to 9 seconds - AUTOSTART 1 and ModemTraceControl : from 9 seconds to issue point

*** modem_log_relay ***

[1] Update modem_log_relay (ADB connection is needed) (command window on your PC) adb shell stop modem_log_relay exit

adb remount adb push modem_log_relay /system/bin/modem_log_relay (--> file is attached 'modem_log_relay.zip', need to modify location of modem_log_relay file)

adb shell

chmod 777 /system/bin/modem_log_relay start modem_log_relay

[2] Power off and Power on rpt_boot_2012_xxx file is generated on each boot-up

[3] Getting trace log file by ADB (please check directory path for sure) adb pull /data/log/boot_trigger C:/golden_log

*Binary will generate a trigger on each boot-up (not possible to disable) --> So, please use attached 'modem_log_relay.zip' only for getting boot-up trace log purpose, do not merge on mainstream of your project

*** AUTOSTART 1 and ModemTraceControl ***

[4] AUTOSTART enable in trace_auto.conf

// Pull trace_auto.conf file adb pull /modemfs/trace_auto.conf c:/temp/

// Edit this file by text editor and save, '0' to '1' dump -D FS /data/log/err dump -l 10

D) Attached patch (0001-Add-boot-trigger-command-trigger-b.patch) introduce a new command to fetch boot logs.

New command will execute as soon as modem is started to ensure we always receive all boot logs.

Attached patch is based on Samsung Golden back delivery

New command: trigger -b or trigger --boot_trigger

If boot logs are needed add above command to trace_auto.conf

If you have any questions please let us know.

E) Solution proposal:

New command added (trigger -b/trigger --boot_trigger)

If command is present in trace_auto.conf MLR will create a boot trigger as soon as modem is up and running.

Trigger will be saved in /data/log/boot_trigger since we can't be sure that SD-Card is mounted.

http://gerrit.lud.stericsson.com/gerrit/#/c/82967/

F) W1302.3 OSK (STE) ============

On GOLDEN default configuration, it is not available to get boot-up (early beginning) trace log. For getting it, following steps are needed.

/// Change "trace_auto.conf" configuration ///

[1] Pull "trace_auto.conf" file from UE by ADB

C:/adb pull /modemfs/trace_auto.conf C:/temp

[2] Edit (Change) "trace_auto.conf" as below (trigger -b and AUTOSTART 1 is changed)

dump -D FS /data/log/err dump -l 10 trigger -D /data/log/err trigger -l 5

trace -l ON 100 30 trace -u OFF trace -t BUFFER trigger -m ON trigger -b AUTOSTART 1 trace -D SDCARD /sdcard/modem_trace

[3] Push edited "trace_auto.conf" to UE

C:/adb push C:/temp/trace_auto.conf /modemfs/

/// Install MTC application ///

[4] Download MTC application (ModemTraceControl_SSG_v1_5.apk) attached in this FIDO ticket

[5] C:/adb install ModemTraceControl_SSG_v1_5.apk

[6] Reset UE C:/adb shell sync C:/adb shell reboot

/// Power-on UE and getting trace log by MTC application (trace log is started by AUTOSTART 1) ///

[7] UE Idle

-> ModemTraceControl : Select 'Trigger Report' -> Check files generated properly My files > sdcard0 > modem_trace > ongoing > latest folder (date in file name)

[8] Pull rpt_host_.. file (or whole directory) from UE to PC

G) W1303.4 OSK (STE) ============ (from CR 451550) If detail trace log is needed but not available to use FIDO box, then following option can be useful.

trace -T PROTOCOL_XML_TRACE_SET_DEFAULT_HAL_SEC : more SIM HAL and SECurity trace messages are added trace -T PROTOCOL_XML_TRACE_SET_DEFAULT_SHM trace -T PROTOCOL_XML_TRACE_SET_DEFAULT_RFHAL trace -T PROTOCOL_XML_TRACE_SET_DEFAULT T' option : more SHM trace messages are added : more RFHAL trace messages are added : less trace messages than not defining 'trace -

EXAMPLE based on default "trace_auto.conf". If you want to get more RFHAL information by *#9900# triggering, then...

dump -D FS /data/log/err dump -l 10 trigger -D /data/log/err trigger -l 5

trace -l ON 100 30 trace -u OFF trace -t BUFFER trigger -m ON trace -T PROTOCOL_XML_TRACE_SET_DEFAULT_RFHAL AUTOSTART 0 trace -D SDCARD /sdcard/modem_trace