PanosPetrou

I have the same problem too. I can't use the motor reliably because of this

If you are using Marlin, check issue #54 it might help.

I can't be 100% sure, but looks normal to me. If both motors do the same thing, they should be ok. I highly doubt both motors are defective.

I think it's unlikely. This board can't communicate with the drivers using UART, so most likely it's not possible. You can use these drivers (and others) in standalone mode only....

I can confirm this too. I have a Tinybee board too, I had to change #if ENABLED(WIFISUPPORT) to #if ANY(WIFISUPPORT, ESP3D_WIFISUPPORT) to make it work. #if EITHER(WIFISUPPORT, ESP3D_WIFISUPPORT) will work...

I agree, organic supports need at least one more layer for better adhesion.

Interacting with the web interface during printing, forces the processor to allocate some unplanned resources there and messes up printing. So don't use the web interface during that time.

Babystepping isn't currently supported on ESP32 boards, such as this one. Perhaps it will be supported in the future.

I have the same board, but not the same screen, so I can't help you fully. I would connect via USB and use Pronterface / Printrun to move the motors...

Most likely your endstops are wired with a wrong pin order and when they engage, they short circuit the 5V rail. Check your wiring and pinout.