Android SDK 1.0.0 Integration Overview

SDK Version: 1.0.0
Platform: Android

This manual is written for customers without access to xTalk source repositories. With the Release AAR delivery and its manifest, you can implement permissions, connection, authentication, initialization, business traffic, and cleanup from these pages alone.

End-to-end call chain

Customer App
  → BLE Connection
  → Radio Transport
  → Device Auth
  → Device Init
  → Data / Text / File / Voice / Device capabilities
  → Disconnect and listener cleanup

Module	Responsibility	Not responsible for	Required input state	Successful output state
BLE Connection	Android permission helpers, scan/connect, GATT/AT/RF channels, device and business callbacks	Authentication and wireless defaults	Bluetooth enabled and runtime permissions granted	awaitBleReady() == true
Radio Transport	Common BLE/UART interface for AT, RF, events, and radio settings	Opening the physical link or defining the business protocol	Selected physical link open	isOpenOrConnected() == true
Device Auth	BLE AT-mode selection, Challenge verification, DID read/apply, and customer UART support	Frequency, rate, or work-mode configuration	BLE/GATT ready or UART open	Result.ok == true with a DID
Device Init	Apply authenticated BLE defaults or UART vendor/default settings	Scanning, connection, or authentication	Auth succeeded and DID available	BLE isReadyForSend() == true or UART Result.ok == true
Data & Device	Binary/RF, text, files, voice, image transcode, key, radio settings, versions, and battery	Customer protocol, file storage, and UI decisions	Interface-specific connection/Auth/Init state	Successful return and completion callback

ConnectResult.CONNECT_OK means that the connect request was accepted. It does not mean authentication is complete. Do not send business traffic until XTalkBleClient.isReadyForSend() is true.

Recommended path

1. Add Release AARs, dependencies, and permissions using Requirements and SDK Setup.
2. Initialize, scan, connect, and await GATT readiness using BLE Connection SDK.
3. Construct a RadioTransport.
4. Complete Challenge and DID handling using Device Authentication SDK.
5. Apply approved radio settings using Device Initialization SDK.
6. Implement business features using Data and Device Capabilities.
7. Copy the lifecycle owner in End-to-End Integration.

Documentation

1. Requirements and SDK Setup
2. BLE Connection SDK
3. Device Authentication SDK
4. Device Initialization SDK
5. API Reference
6. Errors and FAQ
7. RadioTransport
8. Data and Device Capabilities
9. End-to-End Integration
10. API Coverage Matrix
11. Mesh SDK
12. Low Latency PTT SDK
13. Channel Presence SDK
14. OTA SDK
15. Offline STT SDK
16. UART Transport SDK

SDK product catalog

Product	Primary purpose	Main entry
BLE	Scan, connect, and BLE AT/RF channel	XTalkBleClient
Channel Presence	Scan the official 16-channel profile	ChannelPresenceScanSdk
Device Auth	Challenge authentication and DID	DeviceAuthenticator
Device Init	Post-authentication wireless defaults	DeviceInitializer
Mesh	Text, voice, friend/map payloads, routing, and ACK	MeshSdk
Low Latency PTT	Dedicated low-latency half-duplex voice	LowLatencyPttSdk
OTA	TurMass and BT5632F firmware upgrades	XTalkTurMassOtaManager / XTalkBluetoothFotaManager
Radio Transport	Common BLE/UART AT and RF contract	RadioTransport
STT	Offline local WAV transcription	XTalkStt
UART	Android TTY connection and RF/AT transport	XTalkUartClient / UartRadioTransport

Application releases are independent from SDK version 1.0.0. These pages describe only formal customer APIs; diagnostic facilities are outside the customer API surface.