dr-m
commented
4 years ago Hi, a new user here. I just got the newest version (c443993e279ff0f5741cb67cb108c9357f22d34b, v1.18) via F-Droid. I did not manage to set up a minimal build environment on my Debian system yet. Some README.developer.md would be nice for developers who prefer minimal command-line tools and are not that familiar with Android development.
I tested with a heart rate sensor and a speed/cadence sensor, mostly on v1.17, for some hours. Even though the source code has some references to wheel circumference, I did not find it in the user interface, and it appears so that only the cadence is being displayed. I have a few wishes:
- It would be really nice to get the data stored in the GPX file (including the wheel rotation pulses, or speed and distance information even when ‘redundant’ compared to the GPS data).
- Audio notifications for sensor lost/connected. Each type of sensor could have its own sound sample that would be played in 2 tones: low-high for connection, high-low for loss. For example, a heartbeat sound.
- Audio and visual notification for sensor out-of-bounds, with user-settable bounds. Again, with sensor-specific sound samples. This would say 'your heart rate is too high/low' or 'your cadence is too low/high'.
- Audio and visual notification for progress, with user-settable intervals (time or distance).
Last, I noticed some typos. Because I do not have a working build environment, I would rather not open pull requests for something that I did not test myself. Here are some suggestions:
git grep -i satus
git grep -i conectThe first one is visible in the user interface. The "SENSOR_DISCONECTED" in the second one might also affect some external interface, so I am not sure if that can be changed.
bailuk
BLE Challenges,
When searching for new sensor the system find them during scan but fail or takes many tries to recognize them as having supported service.
Could not find the reason….
We may have too many sensor around? ==> Would it make sense to scan only for supported services? to improve probability of support?
in BleScannerSDK21 add:
private final ScanFilter HrFilter = new ScanFilter.Builder() .setServiceUuid(ParcelUuid.fromString("0000180d-0000-1000-8000-00805f9b34fb")) .build();
private final ScanFilter CscFilter = new ScanFilter.Builder() .setServiceUuid(ParcelUuid.fromString("00001816-0000-1000-8000-00805f9b34fb")) .build();
and replace startScan parameters:
// scanner.startScan(callback);
Issues are open on this subject: https://github.com/bailuk/AAT/issues/70
Workaround (last resort) not very elegent:
——————
After we have Sensors recognized as supported and enabled. Getting them connected is complex exercise, We have « Connecting… » for a while. Some time, rescan or disable & enable works?
In order to keep connection and being able to work in parallel the system use connectGatt( context, « autoConnect » …)
found that BLE on Android is not as straight forward as we would expect It looks that one of key element to connect with « autoConnect » is to have the sensor in the cash beforehand. But we have difficulty to get there…..
Workaround to have servers in the cache, if they have disappeared, e.g. reboot, Bluetooth off and back on…:
Good articles with references which may help: https://medium.com/@martijn.van.welie/making-android-ble-work-part-1-a736dcd53b02 https://medium.com/@martijn.van.welie/making-android-ble-work-part-2-47a3cdaade07
and code examples:
https://github.com/NordicSemiconductor/Android-BLE-Library/blob/master/ble/src/main/java/no/nordicsemi/android/ble/BleManager.java#L140 https://github.com/NordicSemiconductor/Android-BLE-Library/blob/master/ble/src/main/java/no/nordicsemi/android/ble/BleManager.java#L563
https://github.com/weliem/blessed-android/blob/master/blessed/src/main/java/com/welie/blessed/BluetoothCentral.java#L543 https://github.com/weliem/blessed-android/blob/master/blessed/src/main/java/com/welie/blessed/BluetoothCentral.java#L563 https://github.com/weliem/blessed-android/blob/master/blessed/src/main/java/com/welie/blessed/BluetoothCentral.java#L609