A80 4G SOS Watch: Hardware and Server Protocol Reference
For platform operators, senior-care solution providers and integrators evaluating an A80 sample. The A80 is an Android-based 4G SOS watch platform with a documented Sanji communication-protocol route for supported projects. Confirm the quoted firmware and device-to-server behavior on the sample before treating an interface as a production deliverable.
Hardware reference and source boundaries
| Item | Reference | Selection checkpoint |
|---|---|---|
| Platform | ASR8601C; Android 8.1; 2 GB RAM + 16 GB storage reference | Freeze the quoted hardware and firmware revision |
| Display | 1.83-inch IPS, 240 x 284 reference | Confirm the supplied sample |
| Positioning | GPS/BDS, assisted GPS, Wi-Fi and LBS reference | Measure update interval and behavior on the destination network |
| Calls and SOS | 4G calling and supported SOS / fall-alert workflows | Confirm activation, escalation and caregiver behavior |
| Battery capacity | Written configuration confirmation required | The current factory reference shows 800 mAh; an existing website reference shows 830 mAh. Reconcile these references with the quoted BOM and sample label before ordering. No runtime is inferred. |
| Regional radio configuration | Separate regional configurations are listed in source material | Request the exact band sheet; do not merge regional options or infer named-carrier approval |
| Water resistance and wellness fields | Source-sheet features require selected-version confirmation | Request applicable test evidence; no medical accuracy or guaranteed rescue is claimed |
Source basis: the A80 international and elderly-care factory-reference specifications, together with the existing A80 product page. Conflicting or optional items remain configuration checkpoints. The agreed specification and approved sample define the final order.
What the protocol documentation covers
| Message group | Documented scope | Sample verification |
|---|---|---|
| Heartbeat | LK keep-alive includes counters and battery information; the platform replies with LK | Verify login, interval, acknowledgement and reconnect behavior |
| Position and retransmission | Location upload and blind-spot data retransmission are described | Check timestamps, units, ordering, stale fixes and offline recovery |
| SOS and configured alarms | Alarm upload and senior-specific fall-alarm commands are documented | Confirm supported commands, cancellation, duplicate handling and escalation |
| Device status and supported wellness fields | Documented groups include status, battery and selected sensor fields | Confirm the quoted sensors, firmware fields, permissions and intended wellness use |
| Configuration and server routing | Configuration commands and server-address changes are described | Confirm authorized configuration, address format, restart behavior and recovery |
The Sanji Communication Protocol V3.1 reference describes a bracketed vendor/device/length/payload message envelope. Documentation coverage does not establish that every command is enabled in every A80 firmware. Actual message availability, field definitions and use rights must be included in the project scope.
Three deployment routes to separate
- Supplied app/platform: confirm the operator, languages, account roles and applicable charges.
- Buyer-controlled endpoint: agree device routing, protocol delivery, endpoint support and firmware prerequisites.
- Custom firmware/app: define engineering work, update responsibilities and acceptance milestones.
The existing Galax self-hosted integration guide describes the standard protocol project direction. Confirm any licence, cloud, hosting, engineering or support charges in the written agreement; no universal fee promise is made by this reference.
Before accepting the integration sample
- Record sample identity, BOM, regional bands, firmware and agreed protocol version.
- Demonstrate connection to the selected endpoint and retain a de-identified message capture.
- Verify heartbeat acknowledgement, position timestamps, SOS delivery and supported configuration commands.
- Test network loss, duplicate/replayed messages, reconnection and low-battery behavior.
- Confirm device authentication, transport protection, user permissions, data retention and update responsibilities. TLS or a particular security mechanism is not inferred from the protocol name.
- Record unresolved issues and approve the exact production configuration and commercial scope.
Use a supplier-agreed safe method for any fall-alert evaluation. Never ask a person to fall. Location and wellness functions do not replace emergency services or medical equipment.
Discuss the selected configuration
Send the destination market, intended carrier, server architecture and required data fields. A model choice and quantity can be discussed with Galax if they are not final.
Model documents and quotation scope · Connected-product procurement checklist
