aljaz/Android-nRF-Toolbox
1
0
Fork 0
mirror of https://github.com/aljazceru/Android-nRF-Toolbox.git synced 2025-12-19 07:24:22 +01:00
Code Issues Packages Projects Releases Wiki Activity

Readme update

Browse Source
This commit is contained in:
Himali Aryal
2025-08-27 17:00:06 +02:00
committed by GitHub
parent 1155e0ba65
commit c264fe16d1
1 changed files with 24 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
README.md
View File

@@ -32,10 +32,30 @@ file.
If you get ["Missing Feature Watch" error](https://github.com/NordicSemiconductor/Android-nRF-Toolbox/issues/41#issuecomment-355291101), switch the configuration to 'app'.
### BLE Connection
### BLE Profile Service
The BLE connection is maintained by running a service. The service starts to connect to a device and stops when the user decides to disconnect from it. When an activity is destroyed, it unbinds from the service; however, the service remains running, allowing incoming data to continue being handled. The service keeps all device-related data and may be obtained by an activity when it binds to it to be shown to the user. Instead of maintaining individual profile service, this structure will create one service for all connected devices.
To add a new profile, create a subtype of _ServiceManager_, which provides logic for observing data interactions with Bluetooth devices.
The ProfileService is responsible for managing Bluetooth Low Energy (BLE) connections in a centralized way.
It runs as a foreground service, maintaining connections to multiple devices, handling lifecycle events, and exposing device data to bound components (e.g., activities or fragments).
#### Overview
The service establishes and maintains BLE connections via the CentralManager. Connections are kept alive independently of any activity or fragment lifecycle. When the UI component unbinds from the service, the connections remain active, ensuring uninterrupted data flow.
All connected devices are tracked, and their states (connection, services, disconnections) are published using StateFlow.
#### Key Features
- Single Service for All Devices:
Instead of running a separate service per device, one ProfileService manages all active connections.
- Connection Lifecycle: Starts a connection when onStartCommand is triggered with a device address. Cleans up and disconnects gracefully when no devices remain connected. Publishes disconnection events with reasons for UI handling.
- Device State Management:
Keeps a map of devices and their DeviceData (address, state, services). Tracks missing services and notifies observers if required services are unavailable.
- Service Discovery & Management:
Discovers services after connection. New profiles can be added by implementing a ServiceManager subclass.
- Logging:
Integrates with nRFLogger to provide per-device logs. Each device connection initializes its own logger instance.
### Nordic UART Service
@@ -66,4 +86,4 @@ contribution based on the [Apache 2.0 license](http://www.apache.org/licenses/LI
- Compatible with nRF5 devices running samples from the Nordic SDK and other devices implementing
standard profiles.
- Development kits: https://www.nordicsemi.com/Software-and-tools/Development-Kits.
- The nRF5 SDK and SoftDevices are available online at http://developer.nordicsemi.com.
- The nRF5 SDK and SoftDevices are available online at http://developer.nordicsemi.com.