FreeRTos on ESP32 to speed up sending ADC Data.

Without seeing the full code, my guess is that your tasks are interrupting each other at random times - I can't see the way you have set up the pre-emption but I think you will find that your task3 is being interrupted at various times as the freeRTOS tried to give some CPU time to task1 and task2.
I suggest that you read up on semaphores and set them up so that your task that reads from the ADC is allowed to read whatever your required number of samples is, it then triggers the semaphore that lets your display task access the data and send that number of samples over bluetooth. It can then go back to wait for the next semaphore.
You probably also want to investigate a double-buffer scheme so that one task can fill one buffer while the other tasks send the data - when the first buffer has been filled it triggers the semaphore and witches to the other buffer. Of course this assumes that you can send data faster than the ADC can fill a buffer.
Susan

You need to be aware that there are blocking functions involved. The println() for example, since there are a different number of calls in each task, depending on the baud rate, the smaller it is and the larger the number of characters, the smaller the amount of data sent by the Serial port from each task with the same priority level. Another strongly blocking function is the ADC, which even without knowing the library you are using, looks like a callback for a sample-hold/conversion in a single instance. In short, consider a timed call, or the use of semaphores as Aussie Susan mentioned.

Hi,

I have no experience with RTOS on ESP32. I guess it´s a valid way to go.

But with ESP32 I successfully used interrupts via Arduino IDE. It worked great.
It helped to avoid blocking functions, thus it speeded up overall timing.

Klaus

IIRC FreeRTOS is the basis for both the 'Arduino' and 'ESP_IDF' frameworks anyway for ESP32s.
Susan