UnityShaderCompiler and adb port problem

The UnityShaderCompilers sometimes use the port 5554. This is the port that the Android emulator normally uses. This makes adb think that there is an emulator running (starting up as it doesn't respond) and therefore real devices can't be talked to anymore as it always complains that there are multiple devices available. The Unity Editor also starts to bitch around and can't deploy to the device anymore.

In that case it helps to kill all UnityShaderCompiler instances but this is an annoying work around. It would be great if the UnityShaderCompiler could ignore the port 5554 and start in a higher range to circumvent that problem.