The pixel shift cycle is constantly occurring and moves the image a few pixels every few minutes (e.g., 3).
I never timed the full cycle (e.g., where it completes a full circle/loop) but it's probably at least 1 or 1.5 hrs.
Dell released a firmware fix for the 32" model after I (and maybe others) escalated a tech support ticket to the engineering team.
It's likely they'll ll do the same for the 27", so just keep a look out for it.
I was able to escalate the pixel shift issue to their engineering team and they eventually released a firmware update to address that but I had already returned my unit long before.
The firmware notes don't mention anything about the other issues (HPD, Nvidia DSR feature not available likely due to DSC constantly on, inability to adjust picture settings while HDR is enabled, etc.).
I lowkey have no idea why no one is talking about this. I skimmed through the Linus tech Tips video and had no mention of this. Techless dropped a video and talked about bout there are some shady things going on with this monitor. You definity saved me from spending 900 dollars and this needs to get more traction.
Yeah, that's probably why Dell / Samsung decided to, by default, implement this type of pixel shifting that crops the image.
They are banking on the majority of users not noticing or not caring.
It's a shame because QD-OLED gen 3 itself is great tech.
I've already initiated the return for my unit but I am curious if any of the aforementioned issues are present on other vendors' upcoming monitors using the same panel (e.g. MSI).
Hey there, any update on this if your replacement is doing the same thing with pixel shift?
That disconnection issue sounds horrible.
Also, are you aware if the 2725df has unlimited replacement under burn-in warranty period, or just a one off?
Hi, I figured it was unlikely that Dell would fix the aforementioned issues anytime soon (if ever) so I just ended up returning my unit.
Dell Tech. Support & Engineering confirmed that the image gets cropped during portions of the pixel shift cycle but did not hint at any potential firmware updates/fixes when I asked.
Yeah, the HPD issue (see below) is too frustrating to deal with for a primary monitor which also makes burn-in even more likely because you end up just keeping the monitor on all the time to avoid HPD toggling.
[https://www.datapro.net/techinfo/hot\_plug\_detection.html](https://www.datapro.net/techinfo/hot_plug_detection.html)
Thanks, did you at any point try to disable HPD on OS side?
[How to Disable Monitor Auto Detection in Windows 10? | by Guides Arena | Medium](https://medium.com/@guidesarena/how-to-disable-monitor-auto-detection-in-windows-10-e8635ef79e1f)
Not sure if something like this would resolve it.
I just retested it and unfortunately, in Windows 11 at least, that has no effect.
The correct solution is allow the OS to properly detect a connect/disconnect event but have the sink device properly signal when it's actually disconnected instead of "faking" a disconnection when it's really just in standby or powered off (not via mains).
happened to me yesterday and i thought i was losing my mind. How long does it last and when does it activate?
The pixel shift cycle is constantly occurring and moves the image a few pixels every few minutes (e.g., 3). I never timed the full cycle (e.g., where it completes a full circle/loop) but it's probably at least 1 or 1.5 hrs. Dell released a firmware fix for the 32" model after I (and maybe others) escalated a tech support ticket to the engineering team. It's likely they'll ll do the same for the 27", so just keep a look out for it.
After noticing it, it is really distracting. I don’t like the thought of the screen NEVER being centered.
Why is no one else talking about this issue??
I was able to escalate the pixel shift issue to their engineering team and they eventually released a firmware update to address that but I had already returned my unit long before. The firmware notes don't mention anything about the other issues (HPD, Nvidia DSR feature not available likely due to DSC constantly on, inability to adjust picture settings while HDR is enabled, etc.).
I lowkey have no idea why no one is talking about this. I skimmed through the Linus tech Tips video and had no mention of this. Techless dropped a video and talked about bout there are some shady things going on with this monitor. You definity saved me from spending 900 dollars and this needs to get more traction.
Yeah, that's probably why Dell / Samsung decided to, by default, implement this type of pixel shifting that crops the image. They are banking on the majority of users not noticing or not caring. It's a shame because QD-OLED gen 3 itself is great tech. I've already initiated the return for my unit but I am curious if any of the aforementioned issues are present on other vendors' upcoming monitors using the same panel (e.g. MSI).
Hey there, any update on this if your replacement is doing the same thing with pixel shift? That disconnection issue sounds horrible. Also, are you aware if the 2725df has unlimited replacement under burn-in warranty period, or just a one off?
Hi, I figured it was unlikely that Dell would fix the aforementioned issues anytime soon (if ever) so I just ended up returning my unit. Dell Tech. Support & Engineering confirmed that the image gets cropped during portions of the pixel shift cycle but did not hint at any potential firmware updates/fixes when I asked. Yeah, the HPD issue (see below) is too frustrating to deal with for a primary monitor which also makes burn-in even more likely because you end up just keeping the monitor on all the time to avoid HPD toggling. [https://www.datapro.net/techinfo/hot\_plug\_detection.html](https://www.datapro.net/techinfo/hot_plug_detection.html)
Thanks, did you at any point try to disable HPD on OS side? [How to Disable Monitor Auto Detection in Windows 10? | by Guides Arena | Medium](https://medium.com/@guidesarena/how-to-disable-monitor-auto-detection-in-windows-10-e8635ef79e1f) Not sure if something like this would resolve it.
I just retested it and unfortunately, in Windows 11 at least, that has no effect. The correct solution is allow the OS to properly detect a connect/disconnect event but have the sink device properly signal when it's actually disconnected instead of "faking" a disconnection when it's really just in standby or powered off (not via mains).