Ionic run android - Connection Lost

Hello guys,
I’m having this really annoying problem.

I connect my device (Xiaomi Mi 9) to my Macbook. Than I’m able to do

ionic cordova run android -l

The application starts, I can change the code and see the changes in realtime on the device.
But after about 10 minutes, the pairing notification appear on my device’s screen with the RSA Key (the same that before). From that moment I can’t do anything, my app shows net::ERR_CONNECTION_REFUSED.

I have to remove all permission, disable and enable debug, reconnect the phone and hope to be able to run again.
Often I have to repeat all the operations more times, sometimes works restarting the phone, sometimes I’m not able to restart the application.

This is the console response.

> cordova build android
> native-run android --app platforms/android/app/build/outputs/apk/debug/app-debug.apk --forward 8100:8100
[native-run] No hardware devices found, attempting emulator...
[native-run] ERR_NO_TARGET: No targets devices/emulators available. Cannot create AVD because there is no suitable API installation. Use --sdk-info to reveal missing packages and other issues.
[native-run]    More details for this error may be available online:
[ERROR] An error occurred while running subprocess native-run.
        native-run android --app platforms/android/app/build/outputs/apk/debug/app-debug... exited with exit code 1.
        Re-running this command with the --verbose flag may provide more information.

Why “No hardware devices found” if the first time my phone is detected?
How can I solve this problem?
I can’t lose 15/20 each time!

Thanks in advance.

I’ve seen this before, but it tends to be related to the android native tools plus the device. Oddly enough, a Xiaomi device as well. I’ve never really had a solid solution other than running

adb kill-server
adb start-server

then verify things with

adb devices

Thank you for this partial solution. Unfortunately, how you said, this is not the definitive solution.
However, this is faster then remove permission, disable debug etc.
It works 8/9 times out of 10, but you need to disconnect the device before run commands.

Thanks again!