3.2 Ending Debugging

The Lotcheck process is not a debugging process, as noted on the 2 Lotcheck page.

Even if there is no problem with production device compatibility or the guideline standards, if a bug is discovered, an application may fail Lotcheck depending on the contents of the bug. In this case, it is necessary to perform Lotcheck again.

Submit the ROM after thorough debugging so that it requires the minimum amount of time to pass Lotcheck.

Info

The guideline test checks all items, even when bugs are discovered, but only for the initial submission of a release.

Even during the first submission, the guideline test may be canceled if it is determined that there are so many bugs that testing cannot continue.

Second and Subsequent Lotcheck for the Same Product

Note: This section is based on the Lotcheck procedure described in 4 Items for the Developer to Address During Lotcheck.

When submitting a product for Lotcheck the second and subsequent times, submit the product after fixing the bugs that were reported in the previous Lotcheck tests.

Resubmission After Failing Lotcheck and Fixing the ROM

  • Review the bugs reported as Lotcheck issues and fix the issues that are marked Will Fix in ROM in the thread status.
    After fixing the bugs, perform testing and verify that the bugs were fixed.
  • Check whether the bugs reported by Lotcheck adversely affect other functionality, and fix any issues.
    If you only fix the reported instance of a bug, your application may still contain related bugs.

Patch Submission

  • Fix the bugs marked as Temporary Waiver Approved in a previous release.
    Any Temporary Waiver Approved is only valid for the approved release version.

Common Problems

See 10 Common Problems and Bugs > Debug.

 


CONFIDENTIAL