Android nRF Logger can not save large logs...?

[Pankaj Gupta]

I have nRF Connect and nRF Logger installed on my Android phone, getting BLE data from a Nordic embedded device.

I run it for over 2 hours, and am anticipating about 300,000 lines of log. The log displays fine on screen under nRF Logger, but when I hit the SAVE button, nRF Logger crashes after a while, and the log file under <sdcard -> Nordic Semiconductor> is 0 bytes.

How can I save large log file with nRF Logger, or where exactly in Android nRF Logger keep the log file, so that I can get it directly from there...?

[Pankaj Gupta]

If I reboot my Android phone, and bring up nRF Logger again, I can see the large log on the screen, which tells me that nRF Logger is keeping it "somewhere" - where is that "somewhere"...?

I can go directly to that "somewhere" instead of hitting the "SAVE" button. Either that, or how to not have nRF Logger crash after hitting the "SAVE" button...?

[Aleksander Nowakowski]

Hi,

The log is saved in the app's database. You could access it only on a router phone.

To be honest, my tests included logs big for couple of MB, not 300k lines... Most definitely the app crashed on OutOfMemory or TransactionTooLarge. I'll have a look at it this week.

[Pankaj Gupta]

Aleksander,

Very much appreciate your response. What is a "router phone"...? A google search didn't turn up much to tell me. I have a Samsung Galaxy S5 with Android 6.0.1

I can run nRF Connect & nRF Logger just fine for, say, 5 or 12 minutes, and the "save" works great. But, we need to collect readings of something over 2 hours. If I can't get nRF Logger to work with that much log, the alternative is to collect that much log over, say, 6 x 20 minutes (i.e. 6 separate logs).

May be nRF Connect & nRF Logger should simply keep on saving the log at run-time and later tell me the location. That way, issues like out of memory, etc. wouldn't come into play.