Surface Pro 3 Miracast+Already Active Bluetooth Screen Res Issue

Posted Posted in Miracast, Surface

 

I’m not sure when this issue first started, but it is being reported with increasing frequency on Microsoft Communities. Note that while the following applies to the Surface Pro 3 running Windows 8.1, fully updated, it has been reported that the same issue occurs for those running the Windows 10 Technical Preview.

 

The issue:

A full HD connection via Miracast is expected but does not occur (to any Miracast display, not just the MS branded one) when Bluetooth peripherals are paired and connected. Only a 1366 x 768 connection is established. (This does NOT apply to the Surface Pro 3 Pen which has no impact on screen resolution.)

 

Below is my TV, ready to connect at full HD 1920 x 1080:

ready 1920.1080 

The problem:

The connection is made at 1366 x768. You can see below the VGA like desktop on the Surface itself which switches screen resolution to match what is negotiated on the TV. (Looks even worse on the TV, and with streaming video, this stinks).

1366.768 

The reason this happens (bug):

If you already have an active connection with a Bluetooth device like the Microsoft Arc Touch Mouse Surface Edition, or other peripherals (I tested with my Parrot Zik BT headphones and repro’d this easily), some BT connected phones, etc. this BUG seems to force a 1366 x 768 connection.

 

Work around:

For some people (and I realize that folks using the Surface Pro 3 Dock may not find this useful)

1. Don’t use Bluetooth peripherals OR

2. Don’t CONNECT your Bluetooth peripheral to your SP3 until AFTER you have established the Miracast session.

Either way, you will be able to get 1920 x 1080 if your TV supports it.

 1920.1080

 

 

I don’t know what the experience is like for folks using the Surface Pro 2 or Surface Pro original, but I’d be interested to know if there are similar Miracast + Bluetooth issues there as well. Please tweet your experience to me on Twitter @barbbowman

Logitech K810 Setpoint Incompatible with Surface Pro 3 after September Update

Posted Posted in Surface

 

Logitech has a really nice backlit K810 Bluetooth keyboard that many folks had been using with their Surface Pro 3 tablets successfully and without problems. After the 9/9/2014 updates, reports started surfacing (pun intended) on the Communities Surface Forums http://answers.microsoft.com/en-us/surface/forum/surfpro3-surfdevice/logitech-k810-and-new-surface-pro-3-firmware/5550000b-af2f-46f7-9c06-53bc887145e4?msgId=78d9c656-6234-4601-b3a2-e98071999570 and the third party forum at http://www.surfaceforums.net/threads/logitech-k810-keyboard-and-9-9-14-firmware-update.11391/ . A thread has been started on the Logitech Forums http://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Logitech-K810-Surface-Pro-3-and-SetPoint-not-playing-nicely/m-p/1316053 as well.

logitech K810

 

It turns out that the September Surface Pro 3 driver firmware/update for the Marvell WLAN/BT adapter now conflicts with the Logitech Setpoint control software for the K810 keyboard. The keyboard pairs, but immediately goes into a connect/reconnect loop and may display a driver error.

Work Around:

Users are confirming that uninstalling the Setpoint software (which again, worked prior to this update without issue) resolves the disconnect loop, but of course prevents setting up Function Keys permanently, etc.