Looking for a solution to record information I get from my device with ESP32

[Maiko_Herrmann]

I really noticed a small loss of information.
Thanks for the observation. I'll try to fix it and post the block diagram here.

[Maiko_Herrmann]

@ABG

I apologize, I missed an error in your blocks.

You are doing multiple BlueTooth.ReceiveText operations in the same Clock.Timer event.

• One of them saves incoming text to a file
• The other adds incoming text to a list for further processing.

Unfortunately, the second ReceiveText asks for the NEXT piece of text to arrive, so you will lose some text that way.

It's better to have just one ReceiveText block in a Timer, going into a global variable, and have all subsequent blocks in the Timer refer to that global variable's contents.
That way, you can both log and process your incoming text.

Dear friend, I tried to follow your tip, but I'm doing something wrong, an operation error is appearing.

[Maiko_Herrmann]

And I try this, but have a same error.

[Taifun]

variable info is your list and not DataReceivedList
DataReceivedList is just the received text separated by pipe symbol
you might want to rename your global variables accordingly...
info -> listInfo
DataReceivedList -> dataReceived

Taifun

[Maiko_Herrmann]

oh my god, i was seeing this now... total lack of attention from me

[Maiko_Herrmann]

It's working fine now, thanks Taifun, thanks ABG

I'm learning little by little and I'm enjoying it, I'm very grateful for your support.

Thank you very much for your attention!

[Maiko_Herrmann]

I tested the app on android 8.0 and got error message: 908 - The permission WRITE_EXTERNAL_STORAGE has been denied

I'm asking for permission when starting the app, but even so the error remains, there is a way to get around this problem, as it only worked correctly on Android 10

[Taifun]

when exactly do you get that error?
did you

@Taifun

set the default file scope in the screen properties to Legacy

Taifun

[Anke]

@Maiko_Herrmann

I'm asking for permission when starting the app, but even so the error remains, there is a way to get around this problem, as it only worked correctly on Android 10

Since it works as you claim on Android 10, WRITE permission must have been granted. This means that this permission is declared in the Manifest. Then it should / must also work for Android 8 (< 10).

Of course, when we talk about permissions, we always talk about the APK and not Companion.

[Maiko_Herrmann]

@Taifun

when exactly do you get that error?
did you

the error appears from the moment I request the connection with bluetooth and it starts reading and writing data.

@Taifun

set the default file scope in the screen properties to Legacy

At first I did as you had indicated earlier, unless I misunderstood.

@Taifun

• set the default file scope in the screen properties to Legacy
• use the file component, set the file scope of the file component to Shared and store the file in shared storage like /Download

[Maiko_Herrmann]

@Anke

@Maiko_Herrmann

I'm asking for permission when starting the app, but even so the error remains, there is a way to get around this problem, as it only worked correctly on Android 10

Since it works as you claim on Android 10, WRITE permission must have been granted. This means that this permission is declared in the Manifest. Then it should / must also work for Android 8 (< 10).

Of course, when we talk about permissions, we always talk about the APK and not Companion.

Hi Anke, thanks for your attention.

In reality I did the permission request test to see if it worked on Android 8, but the error message was the same.

When running again on Android 10 with this permission request at the top of the screen, the same error appeared and the file did not write, that is, the permission did not work in either of the two versions I tested, so I removed it from the project.

I'm kind of lost, because at the beginning I had already researched about possible problems according to the android version, I wanted to find a way that would work on any system

[Taifun]

@Maiko_Herrmann

At first I did as you had indicated earlier, unless I misunderstood.

To

@Taifun

set the default file scope in the screen properties to Legacy

means this

this is required to get the correct permissions in the manifest...

btw. there have been several requests to set the correct permissions to make life easier for everyone, for example here AI2 Files block - shared scope file storage cannot read / write text files to media folders - #21 by Anke or here Release nb187: Copy a text file / image from assets to shared storage (→ Android 10+) - #11 by Anke and I would like to take the opportunity again to ask @ewpatton about some feedback concerning this subject...

@Maiko_Herrmann

the error appears from the moment I request the connection with bluetooth and it starts reading and writing data.

make sure, you first grant WRITE permission and then store the file...
you might want to provide a screenshot of how you are trying to store the file, so we also can see which directory you are using... remember... it should be /Download/yourFile.txt

Taifun

[Anke]

@Maiko_Herrmann

When running again on Android 10 with this permission request at the top of the screen, the same error appeared and the file did not write, that is, the permission did not work in either of the two versions I tested, so I removed it from the project.

WRITE permission must be declared on ALL Android versions, even Android 11+, which of course is a bug (which I've mentioned countless times already). However, your app does not declare WRITE in the manifest at all (on any Android version). If you dragged my AllFilesPermission extension into your project (Screen1), the WRITE permission on Android < 11 would have been declared in the Manifest. Then it would have worked on all Android versions < 11.

Note: It is not necessary to request storage permissions. These are automatically requested with the file component.

There are two ways to make your aia work (on all Android versions):

1. Do what @Taifun suggested. However, the WRITE permission is then also requested on Android 11+ (which is of course nonsense, because firstly this permission is not necessary there and secondly it is no longer available on Android 11+.

2. Use my MFile extension. This way no storage permissions are requested on Android 11+ (as it should be). Of course, you don't have to use AllFilesPermission ext. then, since the storage permission with the MFile extension is correctly declared in the Manifest.

MFile - a modified version of Sunny's `EFile` extension - Shared folders - storage permissions - Android 11+

Here is a modified version of Sunny's EFile extension, which added some methods that are needed (among others things) for testing purposes with Companion & AKP. Because if you try to save in one of the Shared folders (/Documents or /Download) first with Companion it is not possible to do this without deleting the saved text file before testing with the APK and vice versa (at least on Android 11+). So the Delete & FileExists & API level methods are needed. The Delete method exists with the File …

Note: And use the correct path: /Download/... for this Shared folder.
(not /download/...).

[Maiko_Herrmann]

@Taifun

set the default file scope in the screen properties to Legacy

means this

this is required to get the correct permissions in the manifest...

Taifun

That was exactly what was missing.
I had understood it the wrong way, now it works in both versions (8 and 10).

Sorry for the lack of experience, I'm trying to learn and age doesn't help much.

Thank you very much for your enormous attention.

[Maiko_Herrmann]

@Maiko_Herrmann

When running again on Android 10 with this permission request at the top of the screen, the same error appeared and the file did not write, that is, the permission did not work in either of the two versions I tested, so I removed it from the project.
....
......
........
Note: And use the correct path: /Download/... for this Shared folder.
(not /download/...).

Anke thank you for the huge contribution.
I will continue studying the subject, thank you for clarifying my doubts.

I'm trying to learn little by little, I'm very grateful for the collaboration of all of you.
I am happy to be part of this beautiful community.

Thank you!

[karl_thomas]

hello,
you can save the .csv in the spiff of esp32
or add a sdcard to you're esp32.
the android app read the file on the esp32.

[Maiko_Herrmann]

Thanks for the suggestion friend, but I'm doing it this way just to escape the sd card and I use minimal spiffs + ota.

[ABG]

Whats a spiff?

[Maiko_Herrmann]

The ESP32 contains a Serial Peripheral Interface Flash File System (SPIFFS). SPIFFS is a lightweight filesystem created for microcontrollers with a flash chip, which is connected by SPI bus, like the ESP32 flash memory.