Match logs missing lines at start

[shelbyRobots]

We are trying to use match logs, as they are much easier to deal with than the entire robotController log. But we are running into an issue. The first several seconds (~7-15) are missing from the logs, and there are lines like:

10-03 06:59:37.681 11559 11559 I chatty : uid=10134(com.qualcomm.ftcrobotcontroller) Thread-83 expire 1 line 10-03 06:59:38.285 10837 11560 I chatty : uid=10134(com.qualcomm.ftcrobotcontroller) GLThread 941 expire 1 line 10-03 06:59:38.281 11560 11560 I chatty : uid=10134(com.qualcomm.ftcrobotcontroller) GLThread 941 expire 1 line 10-03 06:59:42.381 10837 11535 I chatty : uid=10134(com.qualcomm.ftcrobotcontroller) expire 509 lines 10-03 06:59:44.758 10837 10848 I chatty : uid=10134(com.qualcomm.ftcrobotcontroller) HeapTaskDaemon expire 1 line 10-03 06:59:45.226 10837 11535 I SJH_DTRN: curLpos0 1795 curRpos0 1677 tgtL0 2306 tgtR0 2060

The last line is the first actual line of our prints. In this case, the robotControllerLog.txt has:

10-03 06:59:36.970 10837 11041 I RobotCore: ******************** START - OPMODE UgAutoShelby ********************

Which is actually the beginning of init - not start. But note that it 9s prior to our first line in the match log. And the run/start line has:

10-03 06:59:41.995 10837 11042 V Robocol : received command: CMD_RUN_OP_MODE(13715) UgAutoShelby

So, the match log misses all of init, and the first 3-4s of the actual auton run in this case.