Wireless Display Adapter Disconnects

I'll give disabling Bluetooth a go. Hope it works.

My story: I had been using the Screenbeam with my SP3 every day without any problems. I updated the firmware on the Screenbeam and then started getting dropouts and failure to connect. At the same time my SP3 was replaced so I was then confused about whether the problems were due to the firmware upgrade or the new device. I purchased the Microsoft device ($100 in Australia) and the problems persisted so I returned the Microsoft device and downgraded the firmware on the Screenbeam. So now I'm back to the Screenbeam with the original firmware and a different SP3 but I'm still having the problems of failure to connect and dropouts when it does connect. Windows updates are all done so I'm assuming that I have the latest display drivers on the SP3. 

I use the Miracast extensively...several times a day. Onenote and the Screenbeam turn my tv into a whiteboard that I use with clients. 

Fingers crossed that disabling Bluetooth (that I rarely use anyway) will help. Thanks for the tip. I've been struggling with this for ages and it really has become a critical part of the way I do my job. 

Nope...no change. Disabling bluetooth didn't help.

Still doesn't connect properly. Will connect, but remain frozen on the screen that first appears. Or may freeze after a short while and then disconnect. Or works for a while but eventually disconnects.

Sorry to hear that. As I mentioned, I tried this with Microsoft's WDA. From my limited experience, you seem to be running into some sort of interference that's terminating the connection. What you've described above is exactly what I also saw with the WDA. It might be an option to identify any other potential source of interference that operates in similar frequency band on the SP3 or the TV.

Could a new 4G phone do this? (When I'm next in the office I'll turn off my phone and give it a go.)

It might be an option to identify any other potential source of interference that operates in similar frequency band on the SP3 or the TV.

How does one accomplish that? If you are correct and it is simply a problem of interference, then it seems to me that the product is pretty flaky as there are 6 pages of people with problems.

Either interference or an incompatibility issue - with the bluetooth hardware/driver implementation (at least in my case). There are some interesting pointers here - https://communities.intel.com/message/204003 and https://communities.intel.com/message/204048