Why can't PMP stay full screen (Windows 10) (Not answered as stated :( )

@vlang said:
Last time I took a look at this, I couldn’t reproduce it. Do you have any reproduction instructions that are sure to work?

I am not using v1.2 anymore so I don’t currently. I may update again to try to help, but there were threads about this back when it started that I think had logs as well.

I’ve experienced the same in 1.2.x as well, refusing to remain full screen across reboots, key strokes, etc.

1.1.7 did not have the issue at all.

I tried switching from build in AMD bulldozer apu graphics to Nvidia GeForce dx11 card on win 10 to no avail and switching from Panasonic full HD plasma to Samsung suhd 4k didn’t change this behavior either.

Switched to the Kodi plugin for now without any such issues.

@vlang I included some logs the other day for you here: https://forums.plex.tv/post/quote/254032/Comment_1359527

Logs are not reproduction steps.

@vlang said:
Logs are not reproduction steps.

I’m running 1.1.7 now and don’t have this problem, but it should appear with the following steps (if I remember correctly):

My setup: Intel NUC (Win 10) → HDMI → Marantz Receiver → HDMI → Sony TV

  1. Everything is started and PMP is running with full screen option checked
  2. All screen savers and screen power options are disabled
  3. Turn off TV and Receiver (NUC + PMP still running)
  4. Later (don’t know if one should wait a few hours) - Turn on TV and Receiver
  5. PMP has now dropped out of full screen, and the full screen option in PMP is unchecked

I’m also having this issue, and I’m running an Intel NUC (Win 10) -> HDMI -> Onkyo TX-NR809 -> HDMI -> Sony Bravia XBR-52HX909

The receiver is set to send passthrough HDMI to the TV if it is turned off. HDMI CEC is disabled on both the receiver and TV.

If I turn off the TV with the receiver running, or turn off both the TV and receiver, and then turn everything back on, it will happen every time.

If I turn off the receiver and leave the TV on, it will only do it maybe 50% of the time.

One thing of note, the time it takes for the TV to sync the HDMI and show a picture is significantly longer when turning the receiver on, or starting with both being completely off. I wonder if maybe something is timing out and going back to a default.

The non-full screen size is around 480p sized. Occasionally if I use alt+enter to full screen, it seems like it takes the smaller 480p version and zooms in on that. Which looks soft and pixelated versus if I exit the app and start the video over again.

Finally somebody of the Plex team is finally getting busy with this!

I also was thinking about abandoning PMP but found a workaround.
I connected my Windows 10 pc with a HDMI cable through my receiver to my TV AND a DVI cable directly to one of the HDMI ports of my TV and haven seen any annoying scaling issues anymore. Maybe this also helps to find a solution.

@vlang could you please talk to your colleague @tobiashieta he solved this issue before in a previous version.

@vlang said:
Logs are not reproduction steps.

No, they’re not but I already listed my steps, which are exactly the same as others, so I figured I’d offer up the logs, too. But my steps once again are: HTPC (Win 10) → HDMI → AVR → HDMI → TV. HTPC stays on 24/7, everything else powers off when not in use. When coming from a cold start, PMP is always windowed. If I power on straight to the HTPC or to another device to use for awhile and then to the HTPC, it’s always like this. If I correct PMP, then switch to another device (say my Xbox One or PS3) and then back to the HTPC with powering the AVR and TV off, PMP will usually still be correctly fullscreen. But as soon as the AVR and TV power off, even for just a moment and then are powered back on, PMP is windowed again. So it clearly has to do with the AVR/TV power cycle.

No, they’re not but I already listed my steps, which are exactly the same as others, so I figured I’d offer up the logs, too.

Yeah, that’s fine. I just wasn’t able to reproduce it from that, and all the other descriptions of the problem were more confusing than helpful.

I finally managed to reproduce it somewhat reliably with these simple steps:

  • run windows 10 on a laptop
  • connect a display via HDMI
  • make sure the display and the laptop’s internal display have different max. resolutions
  • configure windows to use only the external display
  • unplug and re-plug the HDMI cable at least 10 times

The last step makes it break in 1 out of about 3-5 attempts. It will show a fullscreen PMP window that partially covers the screen, but on the right/bottom you can see the desktop. (It sort of looks like it’s not in fullscreen, but it still reacts to mouse events in the transparent right/bottom regions.)

I’m hoping that I can come up with a workaround. I’m not really sure whether this is really a regression.

@vlang said:

No, they’re not but I already listed my steps, which are exactly the same as others, so I figured I’d offer up the logs, too.

Yeah, that’s fine. I just wasn’t able to reproduce it from that, and all the other descriptions of the problem were more confusing than helpful.

I finally managed to reproduce it somewhat reliably with these simple steps:

  • run windows 10 on a laptop
  • connect a display via HDMI
  • make sure the display and the laptop’s internal display have different max. resolutions
  • configure windows to use only the external display
  • unplug and re-plug the HDMI cable at least 10 times

The last step makes it break in 1 out of about 3-5 attempts. It will show a fullscreen PMP window that partially covers the screen, but on the right/bottom you can see the desktop. (It sort of looks like it’s not in fullscreen, but it still reacts to mouse events in the transparent right/bottom regions.)

I’m hoping that I can come up with a workaround. I’m not really sure whether this is really a regression.

I too see the “fulscreen PMP window that partially covers the screen.” However I am not able to click on anything in the exposed desktop. I have the “always in top” setting turned on. I don’t know if that matters.

I am using an ASUS HDMI stick with Win10 if it matters.

However I am not able to click on anything in the exposed desktop.

What I meant is that clicks go to the PMP window. It’s like the graphics are not fullscreened, but input is.

@vlang said:

However I am not able to click on anything in the exposed desktop.

What I meant is that clicks go to the PMP window. It’s like the graphics are not fullscreened, but input is.

That could be. I’ll have to test later when I get home. It just looks like a partial screen to me and I know it didn’t pick up any of the icons on the exposed desktop. I didn’t try to click on anything but the task bar which of course isn’t going to do anything with the Plex interface.

@vlang said:

However I am not able to click on anything in the exposed desktop.

What I meant is that clicks go to the PMP window. It’s like the graphics are not fullscreened, but input is.

Yep, this is exactly what my PMP looks and acts like. PMP is fullscreened inside of a small window so I can only see the upper right corner of PMP, and I can see the Windows desktop as well. My remote commands still work so as soon as my TV powers on and I see this, I just hit back and click Enter knowing I’m selecting Exit. I then have to get my keyboard/mouse out, relaunch PMP, which is still windowed but now normal size inside of it. And then I can finally see to navigate to settings and reselect Fullscreen.

@mglaird said:

@vlang said:

However I am not able to click on anything in the exposed desktop.

What I meant is that clicks go to the PMP window. It’s like the graphics are not fullscreened, but input is.

Yep, this is exactly what my PMP looks and acts like. PMP is fullscreened inside of a small window so I can only see the upper right corner of PMP, and I can see the Windows desktop as well. My remote commands still work so as soon as my TV powers on and I see this, I just hit back and click Enter knowing I’m selecting Exit. I then have to get my keyboard/mouse out, relaunch PMP, which is still windowed but now normal size inside of it. And then I can finally see to navigate to settings and reselect Fullscreen.

What I do is actually end-task on PMP when this happens.

bump @vlang @tobiashieta bump

@sa2000 can you get somebody of the Plex Team looking at this issue or should Windows 10 users abandon PMP and go for KODI?

I just give up PMP, I use the old PLEX windows application and this one is working pretty well, no full screen issues…
Hope it will be fix one day.

Where can you download 1.1.7?
This is no go issue, im considering PMP (im using IR remote), but not with this issue

https://nightlies.plex.tv/public-test/plexmediaplayer/public-testing/latest/

Or click Parent Directory and you can download any previous beta version. I hope it works better for you but even with rolling back to 1.1.7 I still have fullscreen issues. They’re not quite as frequent but it’s still almost every day or every other day.

@mglaird said:
https://nightlies.plex.tv/public-test/plexmediaplayer/public-testing/latest/

Or click Parent Directory and you can download any previous beta version. I hope it works better for you but even with rolling back to 1.1.7 I still have fullscreen issues. They’re not quite as frequent but it’s still almost every day or every other day.

I rolled back to 1.1.7 and the full screen issue is nearly gone for me. It happens rarely, but it’s not related to powering off the gear. That works fine. I haven’t identified what it is related to yet, but it happens so rarely now I can live with it.

Rolling back though did re-introduce an audio issue where it gets slowly out of synch, but only on some HD videos. Standard DVD rips are no issue and not all HD is an issue. Haven’t identified exact conditions yet either, but to fix it all I have to do is pause the video for a second and hit play again. All is back in synch.

Neither problem is ideal, but much less annoying than having to deal with the full screen problem EVERY. TIME. I. TURN. IT. ON.

Do you need more users with examples / logs of this
Because i’ve been having the exact same problem, following this thread gives little hope.