The article provides a step-by-step guide for reporting GPMS failures, including describing symptoms, checking Commanager version, attaching visual evidence, and providing GPMS ID. If needed, users can collect additional logs by downloading and unzipping a file, copying the "mvci" folder, reproducing the issue, then compressing and sending the folder to support@gitauto.zendesk.com. Support will analyze logs, suggest workarounds, and update users on fixes.
1. Reporting Failures
- Describe your symptom: Briefly explain the issue you're facing with GPMS.
- Check "Commanager" version : Let us know version of Commanager(Setting > Apps > Commanager > check version on the bottom)
- Visual evidence: Attach photos or videos that clearly demonstrate the problem.
- Include your GPMS ID and submit a request
2. Collecting Additional Logs (if required)
- In some cases, we may need additional logs to diagnose the problem. Here's how to collect them:
2.1 Download and unzip the file:
- Download the file attached on the bottom of this post(VCI2_ShowPacket.zip) to your tablet.
- Unzip VCI2_ShowPacket.zip on your tablet.
2.2 Locate and copy the file:
- Find a "mvci" folder and copy it into "Internal Stroage"
2.3 Reproduce the issue:
- Run GPMS on your tablet.
- Perform actions that normally cause the issue you experienced.
2.4 Send the log folder:
- Once you've finished demonstrating the problem, close GPMS.
- Compress (zip) the entire "mvci" folder.
- Send the zipped "mvci" folder to us.(support@gitauto.zendesk.com)
3. Next Steps
- We will analyze the logs you provide and investigate the issue.
- We will suggest a suitable workaround (if available) and keep you updated on any potential GPMS updates to address the issue.
Comments
0 comments
Article is closed for comments.