Surface Hub Camera Switching Causing flickering

[Rob Ramos]

We are having issues with the camera attempting to autoswitch from left/right during Skype for business video conferences.  It keeps causing screen flickering on our Surface Hub even if the camera does not switch.  When we fix the camera to either left only or right only, the flickering never happens.   The last update was Windows 10 Build 15063 - KB4040724   This behavior is happening on all 5 of our Surface Hubs at this same revision level.  For now, we are telling our users to fix the camera to either side during the video conference.

Is there a policy we can push to turn off camera switching?

[#2]

Hi!

This is a known bug for us so please call Customer Support to get the latest on how to workaround this while the fix gets out. Here is the link: https://support.microsoft.com/en-us/help/4037645/surface-contact-surface-warranty-and-software-suppo...

Thank you!

Nydia

[#3]

Hi Rob. As Nydia has said, this is a known issue. You can read more about it here: https://support.microsoft.com/en-us/help/4010666

You can find the full list of known issues here: https://support.microsoft.com/en-gb/help/4025643

[#4]

Hi Nydia

I know this has been a bug for a while now. Is there anything I can do to help your team fix this, either by running a preview build on one of our test Hubs or by providing logs? Would be nice to finally nix this one!

D

[#5]

Hi Daniel,

thank you for your support =). We will contact you in case we need case for testing.

Nydia

[#6]

In our company we have the exact same issue on all our hubs. Including a few other problems all relating to sleep mode.

It appears a driver or hardware issue where devices do not wake up properly after deep sleep state

It's all resolved by disabling sleep mode

[#7]

Great news! Looks like this issue has finally been fixed in the December CU for Windows 10 1703 (Build 15063.786) that has just been released:

• Resolves camera video flashes (tearing or flickers) during Skype for Business calls

Will have to do some testing when our Surface Hubs receive it next week, but nice to see it finally being fixed. I'm guessing it was a difficult one to resolve given this has been a known issue pretty much since 1703 came out for Windows 10 Team back in May.