> For the complete documentation index, see [llms.txt](https://smedai.aivd.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://smedai.aivd.ch/applications/materiel/readme/mobiles/depannage-mobile.md). # Dépannage mobile **SAV** · **Mobiles** ## Dépannage guidé ### Choisissez le symptôme observé Sélectionnez le problème principal pour ouvrir le bon parcours. {% hint style="warning" %} Si l’appareil est cassé, gonflé, très chaud ou endommagé, ouvrez un ticket sans continuer. {% endhint %}
SymptômeDescriptionParcoursCover image
01 · :power-off: Ne s’allume pasLe mobile reste éteint, même après appui sur le bouton.Le mobile ne s’allume pas2026-07-03 13_37_22-Greenshot _ Explorateur de fichiers.png
02 · :signal: Réseau ou appels indisponiblesLes appels échouent ou la connexion mobile reste indisponible.Pas de réseau ou d’appels2026-07-03 13_36_42-Greenshot _ Explorateur de fichiers.png
03 · :sim-cards: Problème carte SIML’autonomie chute anormalement sur une courte période.\n\n4 étapes · ~ 5 minCarte SIM qui n'est pas reconnue2026-07-03 13_28_40-Greenshot _ Explorateur de fichiers.png
04 · :hand-pointer: Écran ou tactile bloquéL’image reste affichée mais le mobile ne répond plus correctement.~ 6 minÉcran figé ou tactile bloqué2026-07-03 13_38_32-Greenshot _ Explorateur de fichiers.png
### Mon problème ne figure pas dans la liste Ouvrir un ticket --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://smedai.aivd.ch/applications/materiel/readme/mobiles/depannage-mobile.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.