Known log file size

[mattmaclennan82]

I'm about to start a series of long duration tests and I want to use nRF Connect to record the data from my Bluetooth device. The test duration is 60 hours with notifications every second on 3 services.

Is there a known limit to the log file size?

[philips77]

Well.. it may not be possible to share the log afterwards (using Share button), but saving to a file should work. Install nRF Logger app so that even if nRF Connect crashes, the log is saved there. For such very long tasks I would actually recommend writing a small app, perhaps based on nRF Blinky, and log fro it, as you have then control over what's being logged and how. nRF Connect is using Content Provider, which is not the fastest way of doing it, so it may become laggy (?). Bug 3 notifications each second should not make it unusable.

I'm really curious about your finding. Could you please share if the app survived? Thanks!

[mattmaclennan82]

Thank you very much for the quick reply!

I'll keep you updated. nRF Connect has been invaluable during diagnosis and development work. I often refer to it as "the grown up app", whenever ours crashes or generally disappoints!

Matt MacLennan

---

From: Aleksander Nowakowski notifications@github.com Sent: Thursday, October 25, 2018 2:06:53 PM To: NordicSemiconductor/Android-nRF-Connect Cc: Matthew Maclennan; Author Subject: Re: [NordicSemiconductor/Android-nRF-Connect] Known log file size (#83)

Well.. it may not be possible to share the log afterwards (using Share button), but saving to a file should work. Install nRF Logger app so that even if nRF Connect crashes, the log is saved there. For such very long tasks I would actually recommend writing a small app, perhaps based on nRF Blinky, and log fro it, as you have then control over what's being logged and how. nRF Connect is using Content Provider, which is not the fastest way of doing it, so it may become laggy (?). Bug 3 notifications each second should not make it unusable.

I'm really curious about your finding. Could you please share if the app survived? Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/NordicSemiconductor/Android-nRF-Connect/issues/83#issuecomment-433042988, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AqY_M0p8S2Bf3trAj6117z05UdLtwa8sks5uobdtgaJpZM4X5GMW.

[philips77]

Hi, do you have any findings?

[mattmaclennan82]

Sort of…

We have an 86 hour long test that is sat “somewhere” on the Android tablet. We can’t find it as a file, but we can see it in nRF Logger. It takes a little while to load the log file. If we try to SAVE, COPY or SHARE the log, it fails and the “Not Responding” dialogue box appears.

We have managed to recover a 17 hour long test though (https://stevevick-my.sharepoint.com/:t:/p/matthew_maclennan/Ef4sHn8A6C1DnTEjWBg2GoEBx-bcx2vM54iasLP0TLVu8g?e=RD787j)

I had a go with nRF Cloud to see if there was any remote logging facility. I love the API exposure, but there’s a gap where logging should be. I’ve been in touch with Markus about the possibility of adding that as a feature.

Let me know if there is something clever I can do to recover the 86 hour log.

Thanks,

Matt

[philips77]

The only think I can come up with is, in the nRF Logger, instead of opening the log, you may long-tap the log entry on the list and select save to a file from there. It will generate "App not responsing", but you may let the app running. It should finish at some point, I hope. On Android 9 it will crash the app instead of showing this dialog, as they decided to make ANR crashable to force developers to solve them. I'll look into the code and will try to improve that part.

[omidxs]

Hi Im new to BLE and I have the same problem with nRF logger. do you have any findings?