Frequency of Notifications with Android BLE Library

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Tue, 22 Jan 2019 09:48:52 GMT

Hi! First of all, sorry for the delay. Secondly, sorry for a) not releasing ble-common 2.0.4 (I forgot! will do this asap) and b) not updating nRF Toolbox to ble-common 2.0.4. @Acutetech, thanks for the efforts and testing the code with those mixed up libraries.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Sun, 13 Jan 2019 12:14:16 GMT

David this sounds like it could be the same bug as I found. However for me the bug only occurs in certain conditions. It would be interesting to know what setup you have. Could you provide extra information:

(1) What devices have you tried, and do they all show the same results? (I only see the problem on a Samsung Galaxy A5 phone - no problem seen with 3 other tablets).

(2) Can you compare the results of nRF Toolbox downloaded from Play Store with nRF Toolbox re-built from GitHub source code? (I only see problems with the re-built nRF Toolbox; the version downloaded from Play Store works OK. Unfortunately they both report the same version number (2.6.0)).

If you wanted to replicate my experiments then you could program a PCA10040 development board with the Glucose app here:
infocenter.nordicsemi.com/index.jsp
then create some simulated readings and read these using the BGM app within nRF Toolbox. This uses notifications to read the glucose data.

LATER:

Aleksander suggests trying BLE Library 2.0.4. This is not straight-forward, as nRF Toolbox uses nRF Common 2.0.0, which uses BLE Library 2.0.0 - however after downloading nRF Common 2.0.0 and BLE Library 2.0.4 and making approprate edits in build.gradle files, nRF Toolbox builds and the bug is fixed!

IMHO it would be useful if David provides the information (1) and (2) above, then reports on results of using BLE Library 2.0.4. Then it would be good if Aleksander could report that he understands the bug and the fix.

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Sat, 12 Jan 2019 09:18:00 GMT

nRF Connect isn't using BLE Library, it has its own implementation. Did you try BLE Library 2.0.4? The latest nRF Toolbox may not be using the latest version. I'll update nrf Toolbox soon.

RE: Frequency of Notifications with Android BLE Library

davidpeaslee23 — Fri, 11 Jan 2019 23:09:52 GMT

Is there an update to this?

I have a similar problem: I want to receive 4 items at about .001 sec intervals. I've used the relevant UART and profile files from GitHub Toolbox app source, but both my custom app and what I think is the latest nordic toolbox UART activity (with log) only show the first, and 3 copies of the last received packet.

However, the current version of NRF Connect does catch all packets with the right data.

I've tried debugging both my app and the toolbox with and without nrf connect attached, and the apps show repeated catches, where NRF connect catches correctly (when connected and running).

I can not get to all devices right now to set a higher delay in broadcasting packets.

Any suggestions on what is different between NRF Connect and NRF Toolbox?

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Fri, 23 Nov 2018 17:38:35 GMT

Please report it on GitHub. I'll take it from there. Provide some logs or way to reproduce. I'll try to arrange Samsung a5, but can't guarantee.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Fri, 23 Nov 2018 17:14:57 GMT

Hi Aleksander - is there any chance of a response from Nordic on this? Summary: the "latest" BLE Library returns the wrong Notification data but only on one of my 4 Android devices (Samsung A5). The problem is not present with the earlier BLE Library.

I think it is a real bug, even if it is obscure.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Wed, 14 Nov 2018 18:55:47 GMT

I have done further work on this. First: I have bought another tablet: Lenovo TB-710F (Android 8.1.0, API27) and tried it with nRF Toolbox built from Github. That does NOT show the problem (kinda rules out a generic Android 8 fault). So I now have 4 devices all of which work except my Samsung A5 (SM-A520F, Android 8.0.0) phone, and that only fails with the latest version of nRF Toolbox.

On the Samsung phone I looked at radio RX and TX signal timing and see they are the same with both versions of nRF Toolbox. So we can apparently rule out the problem as being due to some radio timing differences. The version from Playstore collects notifications correctly but the new version returns all notifications containing the same data.

With the Nordic dev kit containing 20 records (seq. no.s 0-19) I download all and over 3 cycles see notifications with these sequence numbers:
7, 7, 7, 15, 15, 15, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19
6, 6, 6, 15, 15, 15, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19
0, 8, 8, 17, 17, 17, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19, 19

I have a CSR peripheral which I also load with 20 records (seq. no. 2-21). Notifications received were as follows (slightly different pattern?):
8, 8, 8, 8, 8, 8, 8, 9, 13, 13, 13, 13, 14, 21, 21, 21, 21, 21, 21, 21
8, 8, 8, 8, 8, 8, 8, 9, 16, 16, 16, 16, 16, 16, 16, 17, 21, 21, 21, 21
8, 8, 8, 8, 8, 8, 8, 9, 10, 11, 18, 18, 18, 18, 18, 18, 18, 19, 21, 21

There is clearly a bug here, but what???? Can you guys find a Samsung A5 phone to look at?

RE: Frequency of Notifications with Android BLE Library

Acutetech — Mon, 12 Nov 2018 15:15:27 GMT

Hi Alexsander. It was not entirely clear from your post where you have made changes: both to nRF Toolbox and BLE Library? I assume that changes to BLE Library will be picked up if I collect the latest version of nRF Toolbox? Anyway, that is what I have done (the Master branch). I see some differences, as follows:

My two Android 7 tablets now seem to be working OK. Notifications are displayed correctly. Thanks. (Though I seem to have a bonding issue: I might post separately on this).

My Android 8 phone (Samsung AM-A520F, Android 8.0.0, API26) still misbehaves. Exactly one record is displayed by the app (if it has any), regardless of how many are downloaded. Previously one record was displayed if it contained one record, and no records were displayed if it had more than one record. nRF Logger shows that every notification contains the same payload (as before).

Have you seen the problem with Android 8 devices?

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Mon, 12 Nov 2018 14:04:43 GMT

Hi, I've just pushed some changes to nRF Toolbox. The master branch is not using BLE library 2.0. Also, I've fixed an issue with GLS, but that was related only to UI and refreshing the table. I've also updated BLE lib dependency from beta5 to final version, but the fix seems to be already there (https://github.com/NordicSemiconductor/Android-BLE-Library/commit/e5e054b5952ce6c85798895c8c84f973cf58a624). Nevertheless, I've tested with 20 notifications and they are all displayed on Pixel 2.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Mon, 12 Nov 2018 12:00:32 GMT

It has proved quite complex to get quality evidence. However I have some results, running a slightly modified version Nordic's Glucose App running on the PCA10040 dev kit, and two versions of nRF Toolbox, on three Android devices. I have used nRF Logger to view activity. In my experiments I simulate 0, 1, 2, 3, 4 and 5 glucose readings and download these (as Notifications) to nRF Toolkit by pressing the "ALL" button.

There is no fault with the nRF Toolbox downloaded from Play Store, on any device.

If I rebuild the Develop branch of nRF Toolbox from Github then I get different, incorrect, results, depending on which device I use.

With my Samsung Phone (Android 8), nRF Logger shows that all the Notifications contain the same payload. In every case the payload is of the final notification (determined by the "Sequence Number" which increments with each glucose reading).

With both tablets (Android 7), nRF Logger shows that the Notifications contain the correct payloads. However the nRF Toolbox misbehaves. The toast messages in nRF Toolbox are correct, but reading data is not displayed properly. When the peripheral has one record it is always displayed. When it has more than one record, records are almost always NOT displayed (I see "No values to display"). But very occasionally the readings are displayed correctly.

So: two bugs, or two manifestations of the same bug.

I can provide a more detailed report and nRF Logger files, if you want these.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Wed, 31 Oct 2018 21:28:55 GMT

Let me clean some stuff up before I send you something. However I am expecting to see the problem with your example Glucose app as the Peripheral and the corresponding receiver in the nRF Toolbox. Get the two bonded, then disable BLE on the phone, then get many readings pending in the Peripheral, then turn BLE back on. The Peripheral will then send all its readings as notifications quickly. As my code is derived from the Glucose app within nRF Toolbox, I think I will see the same problem. But perhaps not!

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Wed, 31 Oct 2018 06:23:58 GMT

I will improve the lib in this aspect. Would there be a chance to get your firmware and app for testing?

RE: Frequency of Notifications with Android BLE Library

Turbo J — Tue, 30 Oct 2018 21:38:56 GMT

[quote userid="73161" url="~/f/nordic-q-a/38515/frequency-of-notifications-with-android-ble-library"] The peripheral hangs up as it sends the Notification AFTER the last one received by the central.[/quote]

Could be a problem in your peripherial code.

After about 6 notification you will get the BLE_ERROR_NO_TX_PACKETS, and IIRC this condition gets cleared only when the app processed the following BLE_EVT_TX_COMPLETE.

A tight loop just calling sd_ble_gatts_hvx() repeatedly can simply hang when other BTLE events cannot be processed.

RE: Frequency of Notifications with Android BLE Library

Acutetech — Tue, 30 Oct 2018 20:42:25 GMT

Hi Aleksander

I would like to press you further on this. While my code has changed (on both Peripheral and Central) since my earlier post, I am still seeing unexpected results - somewhat different from above but possibly with the same root cause. The top-level question is, can Nordic's Android library cope with a rapid succession of Notifications?

Today I see correct operation with two tablets (Asus and Acer, Android 7, with no delay added between Notifications at the Peripheral end). But with a Samsung phone (Android 8), when I attempt to transfer 5 notifications in quick succession:

- With no added delay between Notifications, the phone receives 5 notifications, but the payload of earlier Notifications have been lost and are replaced by the payload of later Notifications. Example: each payload includes a sequence number. The BLE peripheral sends sequence numbers 300, 301, 302, 303, 304 but the app on the phone receives 302, 302, 302, 304, 304. The messages in nRF Logger show the same payload data. It looks as though the events are happening too quickly and some variables are being over-written before their contents are picked up by my own application code (and nRF Logger).

- I have to add a delay of 50ms between Notification transmissions (on the BLE Peripheral) before I can get reliable operation.

I have looked at your source code. Can you tell me if I get this right:

- The operating system gets a Notification and calls onCharacteristicChanged() in your MainThreadBluetoothGattCallback().

- You grab the payload and call onCharacteristicChangedSafe() in BleManager.

- That prints the messages I can see on nRF Logger, and then (somehow) passes the data back to the onDataReceived() callback in my app - which is where I pick up the payload and process it. But it looks like by the time I get the callback, earlier data has been overwritten by later data.

Is there an inherent throughput problem with your library? Or something I need to do at my end so I can process an arbitrarily long sequence of Notifications?

My build.gradle has this:

implementation 'no.nordicsemi.android:ble-common:2.0-alpha6'
implementation 'no.nordicsemi.android:log:2.1.1'
implementation 'no.nordicsemi.android.support.v18:scanner:1.1.0'

Thx - Charles

RE: Frequency of Notifications with Android BLE Library

Aleksander Nowakowski — Mon, 17 Sep 2018 10:05:08 GMT

Hi again Acutetech

You should be getting all notifications in the order they were sent. The limit how fast notifications can be sent and received is build into Att protocol, so the sender doesn't send more then it can, and the received doesn't confirm more then it can handle.

Are you using the Ble Library v2 (nRF Toolbox from *develop* branch)?