Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSD tests #231

Merged
merged 1 commit into from Jan 12, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
CSD tests
Signed-off-by: Jorma Virkkunen <jorma.virkkunen@jolla.com>
  • Loading branch information
jovirkku committed Jan 11, 2023
commit 148f9f31466b4e84db8a783f2bdb173d902d1c88
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
110 changes: 110 additions & 0 deletions Support/Help_Articles/Test_Tool_CSD/README.md
@@ -0,0 +1,110 @@
---
title: Test tool CSD
permalink: Support/Help_Articles/Test_Tool_CSD/
parent: Help Articles
layout: default
nav_order: 895
---

Sailfish devices have a built-in customer service diagnostic tool, abbreviated **CSD**. This test tool makes it possible for users to verify the key functions of their devices.



# Opening the CSD

Access the tool by tapping the item "Build" five times or more in "Settings > System > About product". The tool pops up in a few seconds showing the Disclaimer page first.

<div class="flex-images" markdown="1">

* <a href="CSD_about_product.png"><img src="CSD_about_product.png" alt="About product"></a>
<span class="md_figcaption">
Pic 1: About product
</span>
* <a href="CSD_disclaimer.png"><img src="CSD_disclaimer.png" alt="Disclaimer"></a>
<span class="md_figcaption">
Pic 2: CSD disclaimer
</span>
</div>


Please read the text carefully. Accept the disclaimers by tapping 'Accept' at the top right corner.

NOTE:  _Interpreting the test results correctly may not be easy without suitable technical training.  Please seek help from the **[Sailfish Forum](https://forum.sailfishos.org/)** or from **[Jolla Customer Support](https://jolla.zendesk.com/hc/en-us/requests/new)**._


# Main categories

There are three main categories of tests (Pic 3):

1. Factory tests
2. Hardware tests
3. Device status

We recommend using categories #2 and 3#. The only reason for using category #1 would be to run some long-lasting tests. Everything else and more are covered by category #2. The device status category provides data mainly on power consumption.

<div class="flex-images" markdown="1">

* <a href="CSD_caregories.png" class="narrow-image"><img src="CSD_caregories.png" alt="Test categories"></a>
<span class="md_figcaption">
Pic 3: Test categories
</span>
</div>



# All hardware tests

Tap "All tests" to enter the category of Hardware tests.

The tests are grouped by technology areas. The groups are shown at the right of the display (Pic 4). After executing a test, the verdict is shown with green or red colour in the list of tests (Pic 5).

The test results can be cleared by pulling down "Clear test results" for the next round.

<div class="flex-images" markdown="1">

* <a href="CSD_hardware_tests.png"><img src="CSD_hardware_tests.png" alt="Hardware tests"></a>
<span class="md_figcaption">
Pic 4: Hardware tests
</span>
* <a href="CSD_hardware_tests_passed_and_failed.png"><img src="CSD_hardware_tests_passed_and_failed.png" alt="Test results in colours"></a>
<span class="md_figcaption">
Pic 5: Test results in colours
</span>
</div>


## Test procedures

Each test has a short written procedure. Please follow it precisely.

Picture 6 below shows the test procedure of the loudspeaker test for example.

<div class="flex-images" markdown="1">

* <a href="CSD_loudspeaker_test.png" class="narrow-image"><img src="CSD_loudspeaker_test.png" alt="Loudspeaker test"></a>
<span class="md_figcaption">
Pic 6: Procedure of the loudspeaker test
</span>
</div>


After executing a test, some of them give the verdict of "Pass" or "Fail" automatically (Pic 7 below) whereas in some other cases, you must decide on the verdict based on your interpretation of the test results (Pic 8). In such a test, tap the appropriate button (Pass or Fail).

<div class="flex-images" markdown="1">

* <a href="CSD_USB_charging_test_verdict.png"><img src="CSD_USB_charging_test_verdict.png" alt="Test verdict USB charging"></a>
<span class="md_figcaption">
Pic 7: Test verdict of the USB charging test
</span>
* <a href="CSD_loudspeaker_test_verdict.png"><img src="CSD_loudspeaker_test_verdict.png" alt="Test verdict loudspeaker"></a>
<span class="md_figcaption">
Pic 8: Test verdict of the loudspeaker test
</span>
</div>


## Reporting

The CSD tests do not have a reporting utility. Take **[screenshots](/Support/Help_Articles/Tips_and_Tricks/#taking-screenshots-screen-captures)** if there is a need to save test results.