Safety, journeys and devices
Open Settings, Safety, journeys and devices. Each tab uses the shared command executor, Android access checks and ordinary response contracts. Launcher controls display the installed version beside Close.
The Safety tab opens the bundled SOS custom app. Its complete UI and backend are editable under /sdcard/Dikciz/apps/sos/. Dikciz, Apps also includes Voice notes, Agenda, Device status and Travel todo, plus creation, complete-source editing and import/export. Places, Trips and the remaining companion tabs keep their native controls.
| Task | Guide |
|---|---|
| Choose contacts, preview messages, arm a missed check-in or record a route | Safety and journeys |
| Keep a Bluetooth, USB or NFC connection across commands | Device connections and Vehicle console |
| Read text/barcodes or create cleaned image PDFs | Image recognition |
| Inspect grants, read/aggregate records and write owned Health Connect data | Health records |
| Suggest/save a network, request a local connection or start a local-only hotspot | Wi-Fi networks |
| Run repeatable read-only briefings with a saved provider | Assistant routines |
| Stage base/split APKs together or cancel an owned install session | Package installation |
MCP starts at dikciz://docs/guides/companion. Search also indexes the focused manuals and installed tool schemas. Missing hardware, provider access or foreground eligibility remains explicit. Nothing starts sending SMS, recording a route or connecting a peripheral merely because the app was installed.
Companion commands accept full owner remote authority or the corresponding explicit command/action scopes. The permission reference covers the complete catalog. Existing named feature grants retain their original boundaries. App invocation and source management can execute owner-trusted code and must be delegated accordingly. Assistant read-only enforcement remains independent.
Native controls
The companion screen walkthrough covers every tab and the place, Bluetooth, USB, NFC and Wi-Fi forms. Entering a form does not start a connection, route or safety plan. Use the operation result to distinguish requested, approved, connected and failed states.
These captures show the isolated emulator, including a fictional safety contact. They demonstrate setup controls, not carrier delivery or physical-peripheral compatibility.