If KDS 2.0 closes suddenly by itself (force close), the KDS 2.0 log alone is often not enough to find the cause. A system log of the tablet (dump log) is also needed. This guide explains how to create the dump log on a Samsung Galaxy Tab, find the ZIP file, and send it.
Applicable Environment: KDS 2.0 Tablet App on a Samsung Galaxy Tab
Symptom: KDS 2.0 closes suddenly (force close) without any user action.
Target Version Code (App Prefix): NEK
Tested On: Galaxy Tab S9 FE (Android 16 / One UI 8.0). Screens and menu names may differ on other tablet models or software versions.
When to Use This Guide
- KDS 2.0 closes by itself while you are using it, without you tapping any button to close it.
- You are asked to provide a system log (dump log) of the tablet.
- Collect the dump log as soon as possible after the force close occurs.
- If KDS 2.0 does not close but a function fails (for example, diagnosis or ECU upgrade), use the Log Collection guide instead: KDS 2.0 | How to Submit an Error Log Report Using Log Collection
On this page
1. Video Manual & Workflow Summary
Watch the video or follow the steps below. The whole procedure has four steps.
| Phase | Where / What to Tap | Key Point |
|---|---|---|
| Step 1. Generate |
Phone > *#9900# > Run dumpstate/logcat > Copy to sdcard(include CP Ramdump)
|
Wait for each Dump Result pop-up and tap OK. Do not tap other SysDump items. |
| Step 2. Locate | My Files > Internal storage > log | Select the newest dumpState_..._YYYYMMDDHHmm.zip file, not the .log file. |
| Step 3. Send | KDS 2.0 Error Report > Attachments (optional) > Select | If the file cannot be attached or the report cannot be submitted, send the file by Quick Share or email instead. |
| Step 4. Contact | Your Distributor / NSC | Provide the Report No. or VIN and the dump log file name. Your Distributor / NSC escalates the case to GIT. |
2. Step 1: Generate the Dump Log (SysDump)
Use the Samsung SysDump menu to create the dump log and copy it to the internal storage of the tablet. This step is done outside KDS 2.0.
Before You Start
- Do not tap any other SysDump item (for example, Delete dumpstate/logcat). Use only the two items described in this guide.
- Do not close the app or turn off or restart the tablet while a Wait... pop-up is shown.
- Copy to sdcard(include CP Ramdump) copies the whole system log folder, not only the ZIP file (about 467 MB on the test tablet). Make sure the tablet has enough free storage space.
- Files with the same name that are already in the log folder are overwritten during the copy.
Step 1-1. Open the Phone App
Open the app list and tap Phone.
Step 1-2. Enter *#9900# to Open SysDump
On the keypad, enter *#9900#. You do not need to tap the call button. The SysDump screen opens as soon as you enter the last #.
Step 1-3. Tap Run dumpstate/logcat and Wait
Tap Run dumpstate/logcat. A Wait... pop-up is shown while the dump log is created. This took about 2 minutes on the test tablet and may take longer on other tablets. When the Dump Result pop-up appears, tap OK.
At this point the file is saved in a system folder (/data/log) that you cannot open in My Files. Continue with Step 1-4.
Step 1-4. Tap Copy to sdcard(include CP Ramdump)
Tap Copy to sdcard(include CP Ramdump). When the Dump Result pop-up shows Copy Success!, tap OK. The copy took about 15 to 20 seconds on the test tablet.
Do not skip this step. Without it, the ZIP file stays in the system folder and cannot be found in My Files.
If Your Tablet Has No Phone App
If the Phone app is not available on your tablet, open SysDump from the Samsung Calculator app:
- Open Calculator and enter
(+30012012732+. The DRParser Mode keypad opens. - On the DRParser Mode keypad, enter
*#9900#. The SysDump screen opens. Continue from Step 1-3.
Do not use any other function on the DRParser Mode screen.
3. Step 2: Locate the ZIP File in My Files
The dump log is copied to the log folder in the internal storage of the tablet.
Step 2-1. Open Internal storage > log
Open My Files, tap Internal storage, and open the log folder.
Step 2-2. Find the Newest ZIP File
Scroll down to find the file named dumpState_<build number>_<YYYYMMDDHHmm>.zip. The last 12 digits show the date and time the dump log was created.
- Example:
dumpState_X510XXU8DYJ4_202611051927.zip(24.16 MB on the test tablet). - The folder may also contain older dump files. Choose the file with the most recent date and time.
- A
.logfile with the same name (about 128 MB, not compressed) is also created. Do not send the.logfile. Send the.zipfile.
No Need to Compress the File
The dump log is already created as a ZIP file. You do not need to compress it again.
4. Step 3: Send the ZIP File
First try Method A (attach the file to a KDS 2.0 Error Report). If the file cannot be attached or the report cannot be submitted, use Method B.
Method A: Attach the ZIP File to a KDS 2.0 Error Report
Method A uses the KDS 2.0 Log Collection function. For more details on each screen, see the Log Collection guide: KDS 2.0 | How to Submit an Error Log Report Using Log Collection
Step 3-1. Open Configuration > Log Collection and Tap Run
On the KDS 2.0 main screen, tap Configuration, select Log Collection, and tap Run.
Step 3-2. Tap Start
Read the guide and tap Start, then go back to the KDS 2.0 main screen. A floating widget is shown at the bottom right of the screen. If possible, repeat the operation you were doing when KDS 2.0 closed.
Step 3-3. Tap Error Report on the Floating Widget
Tap the floating widget and select Error Report. On the Error Report screen, write down the Report No. shown under User Information. Select the error type and enter a title and a description of the symptom (when KDS 2.0 closed and what you were doing).
Step 3-4. Tap Select Under Attachments (optional)
Scroll down. Under Log Data, the KDS 2.0 log file gdsnLog.git is included automatically. Under Attachments (optional), tap Select. The Android file picker opens.
Step 3-5. Open the Tablet Storage
In the file picker, tap the menu icon at the top left (Show roots), then tap the name of your tablet (internal storage). The name is different on each tablet.
Step 3-6. Open the log Folder
Tap the log folder. The next time you tap Select, the file picker may open directly in the log folder.
Step 3-7. Select the ZIP File
Scroll and tap the newest dumpState_...zip file. The file name may be cut off, so check that the type is ZIP archive. The file is then listed under Attachments (optional) with an X (remove) button.
On the test tablet, searching for the file name in the file picker did not filter the list. Scroll to find the file.
Step 3-8. Agree and Tap Submit
Check the e-mail address, select the (Required) Do you agree to send error report? check box, and tap Submit. The Submit button stays disabled until the required check box is selected. Do not close KDS 2.0 while the report is being sent.
About the File Size
The KDS 2.0 Log Collection guide states a limit of 20 MB in total for attachments. Dump log ZIP files on the test tablet were about 21 to 24 MB, so your file may exceed this limit. On the test tablet, a 24.16 MB ZIP file could be selected and was listed as attached without any warning, but whether it is accepted when the report is submitted has not been confirmed.
If the file cannot be attached or the report cannot be submitted, use Method B below.
Method B: Send the ZIP File by Quick Share or Email
- Open My Files > Internal storage > log and find the dump log ZIP file (see Step 2).
- Transfer the file to your PC or mobile phone using Quick Share or another file-transfer method, and send it as an email attachment. You can also send it directly from Gmail on the tablet.
- Send the ZIP file to your Distributor / NSC together with the information listed in Step 4.
5. Step 4: Contact Your Distributor / NSC (Escalation to GIT)
Escalation Path: Dealer > Distributor / NSC > GIT
To start a technical investigation, contact your local Distributor / NSC and provide the information in the table below. Your Distributor / NSC will then escalate the inquiry to GIT.
Provide the following information together with the dump log.
| Information | Details |
|---|---|
| Report No. | Shown under User Information on the Error Report screen (only if you used Method A). |
| VIN | 17-character VIN of the vehicle that was connected when KDS 2.0 closed (if a vehicle was connected). |
| Date, Time, and Symptom | When the force close occurred and what you were doing in KDS 2.0 at that moment. |
| Tablet Model and Android Version | For example: Galaxy Tab S9 FE, Android 16. |
| Dump Log File Name | For example: dumpState_X510XXU8DYJ4_202611051927.zip
|
| Number of Affected Tablets | Whether the issue occurs on one tablet or on several tablets. |
Comments
0 comments
Please sign in to leave a comment.