BLE Challenges, #78
Comments
…), display message to user when reconnecting
…is with SensorStateButton in MainActivity
|
Hi, a new user here. I just got the newest version (c443993, v1.18) via F-Droid. I did not manage to set up a minimal build environment on my Debian system yet. Some 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:
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 |
|
Hi, Wheel circumference gets calculated from GPS samples. Information from the speed sensor is then used to display current speed inside the cockpit view. WheelCircumference.java, CscService.java, CurrentSpeedDescription.java Android Studio is the official development environment for Android. #!/bin/bash
export ANDROID_HOME=/home/user/Android/Sdk/
git clone https://github.com/bailuk/AAT.git
cd AAT/
./gradlew assemble --stacktrace
ls -l app/build/outputs/apk/release/ |
|
Thank you, @bailuk! I will be busy with work for the next few weeks, but I am looking forward to return to this in the near future. |
|
Sorry, I have been too busy with work to contribute to this great application. Meanwhile, I figured out that my combined speed/cadence sensor was not making contact with the spoke magnet. After I fixed that, the display started showing "Speed S" instead of "Speed GPS". A more obvious indication of "lost" speed sensor could be useful, especially when configuring the sensor for the first time. For cadence or heart rate, this is less of a problem, because you would directly see the measurement values. I have an annoying problem with my BLE heart rate sensor. It keeps disappearing while I am recording. It will reappear and resume recording if I go back to the main screen and click on the Sensors button. I do not think that it is related to power savings, because on one ride, the HRM sensor disappeared while I was watching the screen. It should also not be a problem on the sensor side, because I never have to touch the sensor to resume the connection. (I could understand that the sensor enters power-saving mode if the connection to my body is too weak, but that does not seem to be the case.) The non-BLE speed/cadence sensor has worked perfectly for the past 3 months. Here is a sample from a recent ride where it seems that the heart rate measurements were lost for some time: It is likely that I manually re-enabled the heart rate sensor during this recording snippet, but I am not entirely sure. If it helps, I can try to look up a better sample where I clearly remember that the display was active when AAT stopped reporting the heart rate. (Side note: I find it somewhat strange that the cadence is being logged only once per 3 or 4 seconds. Does the sensor really deliver data so seldomly? The pulse rate should be 1 Hz already at 60 rpm, and I have the impression that the AAT display would refresh the cadence data about once per second.) |
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:
#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
The text was updated successfully, but these errors were encountered: