Depends how you are sending data (notify, indicate, write, write with no response) you should be able to achieve 40-100kB/s with android device. I only one time had similar issue like you and i still dont know why. It was when ive been trying to perform OTA over BLE on esp32 ble mesh node. I know th...

Im not 100% sure, but command line seems to be wrong: Der Terminalprozess "C:\Users\Marvin\.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe 'C:\Users\Marvin\Desktop\esp-idf\components\esptool_py\esptool\esptool.py', '-p', 'COM10', '-b', '460800', '--before', 'default_reset', '--after', 'har...

1. you can use regular ble API to scan for devices
2. you can filter ble devices and scan only for ble mesh nodes
3. this suppose to be implemented and all nodes probably
4. you have to think how to send those data to client, maybe with vendor element?

It is not a flash memory corruption. It is ram memory corruption in code (just guessing from experience).

That make sense if you have memory corruption problem and semaphore handle get corrupted eventually.

Something is not working correctly. My suggestion is to run nrf connect and change MTU in it after connecting, then check logs and see if it works.
If it works, then android app is problem most likely.

https://github.com/hathach/tinyusb/tree ... usb_serial

1. please check this option in menuconfig SPIRAM_MALLOC_ALWAYSINTERNAL
2. again, its safest to use heap_caps_malloc(n, MALLOC_CAP_SPIRAM), because you control where exactly variable/array is placed

1. 4MB ram is a bit confusing, because you still have only <400kB internal RAM 2. in menuconfig you have option to set when malloc/calloc (and probably arrays too) should use PSRAM instead of internal ram (default is 16kB) 3. you can explicitly malloc from psram with: https://docs.espressif.com/proj...