This issue tracks solving the root issue discussed in #125971. To summarize the issue, flutter daemon occasionally exits when trying to run adb devices -l due to the command completing with an error. Source of this call:

See #125971 (comment), which includes the exception that comes from invoking adb devices -l. Specifically, we see

daemon still not running
error: cannot connect to daemon at tcp:5037: Connection refused"}}]

While it's not clear what the root cause of this failure is, it's possible that the flutter tool could prevent or workaround it. See #125971 (comment). It's possible we can use something like adb reconnect, which should restart the connection to the server from the host side.