Forum Discussion

Christoph Puetz's avatar
Christoph Puetz
Copper Contributor
Aug 25, 2017

Skype for Rooms not presenting to TV after system sleep

We have one of those LogiTech Skype for Rooms systems with the Surface Pro / Docking station. Ever since the upgrade from v2 to v3 of SRS the system fails to present meeting content to the TV. 

 

After a reboot the unit works fine. It shows the default splash screen on the TV and dashboard on the Logitech docking station/Surface Pro. I can start a video call or present from a laptop just fine. Fast forward - the unit is not being used for a while and goes to sleep. I come back 2 hours later, the unit activates. I turn on the TV and only see the (I assume) the desktop extension of WIndows 10 on the TV. I am supposed to the see the default splash screen of SRS, but only see the default Windows 10 background.

 

The docking station/Surface Pro shows the standard SRS dashboard. I plug in a laptop and it switches to presenting, but the TV stays on the default Windows 10 background. 

 

Again, this worked fine in v2, but ever since v3 came out, this is bugging us. Any ideas how to fix this?

  • Jeff Koertzen's avatar
    Jeff Koertzen
    Copper Contributor
    I've been running into this issue with several new devices. One of the first things I do with Teams Room devices is to domain join so that I override the default admin login and require a domain admin for edits.

    What I have found is that once I domain join the device, the autologin registry field reverts to No (0). When I change that field back to Yes (1), the devices will login at startup as normal and no longer go into the unrecoverable sleep mode. It's the autoadminlogin field from the following website: https://docs.microsoft.com/en-us/troubleshoot/windows-server/user-profiles-and-logon/turn-on-automatic-logon.

  • Martin Malm's avatar
    Martin Malm
    Copper Contributor

    Now with the most recent update 3.1.98.0 it seems like the problem with getting the Windows background on the front room display is solved. At least on our setup. It would be great if more people that had this problem could upgrade to 3.1.98.0 and test. 

    • David Groom's avatar
      David Groom
      Icon for Microsoft rankMicrosoft

      We made some changes related to window management in 3.1.98.0.  This may account for the improved behavior that you are seeing.

      • Tobie Fysh's avatar
        Tobie Fysh
        Copper Contributor

        I've had confirmation from Logitech that they DO NOT support CEC on the Smart Dock. Would be interested in other SRS vendors statements on this.

  • In the single front of room display configuration, SRS v2 effectively creates 2 app windows, one for the console screen and another for the front of room screen. When power management wants to turn off the display (by default 10 mins of idle outside of a meeting), SRS v2 ceases to send any video signal, expecting the displays to go into standby. When motion sensor is triggered, the video signal is resumed, expecting the displays to turn back on automatically.

     

    This power saving behavior is pretty standard for PC displays, but it appears that TV displays (including HDMI CEC enabled ones) seem to behave a little differently.

     

    In this case, it sounds like the front of room display is turning back on automatically at the same time as the console display. If it is not, then it would be an issue with the HDMI CEC behavior.

     

    The problem appears to be the front of room display showing the windows desktop instead of the SRS front of room screen. My guess is that when we stop sending a video signal, causing the displaysto go into standby, the front of room display disconnects itself (as if you turned the TV off), causing Windows to think that there is only 1 display (the console screen) connected to the system. This would cause Windows to relocate the SRS front of room window that was previously placed on the front of room screen to the console screen underneath of the console window that is currently visible.

     

    I'll look into how we can handle this case better at the app level. In the meantime, you may want to look into if your front of rooms displays can be configured such that standby doesn't cause the display to disconnect from the PC. FWIW, I understand our internal deployments have a box between the SRS and Front of room TV to achieve this.

     

    Hope this helps,

    Dave [MSFT]

    • David Tse (SKYPE)'s avatar
      David Tse (SKYPE)
      Icon for Microsoft rankMicrosoft

      UPDATE: Happy to report we have a fix in the works for this. Cannot provide an ETA yet but it is coming.

      • Pavel Aivazov's avatar
        Pavel Aivazov
        Iron Contributor

        Hello,

        any update on this issue? This is holding us from 700+ SRS deployment in our company.

        Can you please also share more details about "a box between the SRS and Front of room TV"? We are happy to purchase and install them to fix the issue

    • Christoph Puetz's avatar
      Christoph Puetz
      Copper Contributor

      These are high-end TVs, so that this is not the problem - especially as it worked fine before the upgrade to version 3.

      • Slawomir Garbarz's avatar
        Slawomir Garbarz
        Brass Contributor

        christophe limet I agree with   Christoph Puetz , we also are using high end SAMSUNG MEC Series professional displays with CEC and other industrial features and it doesn't realy matters, if this all features are on nor off. This issue appears randomly, from time to time without any information in event viewer. The system just hanging on (in our case we can see just frozen screen from one display), and needs to be restarted by pressing button for about 10 s. I realy hope that this issue will be fixed, because it is a roadblock for our deployment of 20-30 SRSv2 across the company.

  • I've seen issues where the external monitor just getting "no signal as well" anyone experienced that ?

    • Christoph Puetz's avatar
      Christoph Puetz
      Copper Contributor

      3.0.10 is installed. It all worked fine with 2.x. Wish I could go back ...

    • Yauhen Mikhailovskii's avatar
      Yauhen Mikhailovskii
      Copper Contributor

      Faced with same problem. Current app is 3.0.10.0, winver is 15063.540.

      As I remember, problems began after update to 3.0.0.0 application. The only workaround - restart SRS.

  • Tobie Fysh's avatar
    Tobie Fysh
    Copper Contributor
    Seeing the same thing. Have disabled sleep in power settings to stop this but will cause screen burn over time.
      • Tobie Fysh's avatar
        Tobie Fysh
        Copper Contributor

        Yep - left on all the time. 

         

        I think its a feature of the TV not supporting the power on over the HDMI instead of the SRSv2 not doing it correctly.

Resources