Discovering new device means we could find New valid device/service (couple validity check with search) so changes to ServiceInterface, BleSensorSDK18, CscService, HeartRateService, BatteryService.
When we buffer messages send to sensor, try to keep order: use FIFO rather than LIFO so changes to Executer
Ease operation:
Try to reconnect while riding with click or on disconnect (get far and comme back...) so changes to CockpitActivity, CockpitView, SensorService , AppBroadcaster, Connector
Improve new sensor discovery:
Make selective scan to reduce sensor list to sort: so changes to BleScannerSDK21
speed up new service association during scann: so changes to BleSensorsSDK18, SensorItemState
This improve significantly BLE discovery and keep connection, it would be worth in future to decouple "configuration" vs run time states
few improvements, few discovery and association challenges remains,
decouple configuration states and run time states.
e.g. do we need to space messages?
Code Inspection fixes:
Discovering new device means we could find New valid device/service (couple validity check with search) so changes to ServiceInterface, BleSensorSDK18, CscService, HeartRateService, BatteryService.
When we buffer messages send to sensor, try to keep order: use FIFO rather than LIFO so changes to Executer
Ease operation:
Improve new sensor discovery:
This improve significantly BLE discovery and keep connection, it would be worth in future to decouple "configuration" vs run time states
In relation with challanges highlighted in issues: https://github.com/bailuk/AAT/issues/78 https://github.com/bailuk/AAT/issues/61
few improvements, few discovery and association challenges remains, decouple configuration states and run time states. e.g. do we need to space messages?
sorry for confusion it is simply change: https://github.com/bailuk/AAT/pull/80/commits/b087bdd93c29702815051736c927bbd310512d6a