purplewakanda
Gold Level Poster
It's working fine with my MacBook. Could AMD Sync stop the screen from sleeping?
Oh no, someone is in trouble now? Could you check AMD settings?@SpyderTracks @Martinr36 @Citrus_9 I switched off AMD Freesync and the sleep issue seems to have stopped. What's the point in getting this monitor if I have to switch off Freesync so that sleep works!
You mean turn on Sync in AMD settings and not the monitor?Oh no, someone is in trouble now? Could you check AMD settings?
I'm under impression that your PC is with a 6700XT GPU (?) - check AMD graphics settings. I'm just guessing here as I don't know what are the AMD graphics settings - will know soon thoughYou mean turn on Sync in AMD settings and not the monitor?
Yes, it is. I've turned on sync. Is there anything else I need to enable?I'm under impression that your PC is with a 6700XT GPU (?) - check AMD graphics settings. I'm just guessing here as I don't know what are the AMD graphics settings - will know soon though
I posted there as it's a relief knowing how many people have the same issue.purplewakanda
1h
I have the same issue with Samsung G5 + 6700XT
When your looking around the internet for solutions and you find a post from the op on reddit View attachment 26344
Without a doubt im glad you did its brilliant when you can see a issue is a widespread issue and your not alone in it !!!I posted there as it's a relief knowing how many people have the same issue.
@Martinr36 @SpyderTracks @Citrus_9 jamiephillips909 New update: The monitor sleeps when the mouse and keyboard are not plugged in. However, I tested with disabling the waking up option (device manager) on the mouse and keyboard but it doesn't let the monitor sleep when plugged in. Do you have any ideas to solve the issue?
I had updated it when I was on the call with Samsung with this issue.Is there a firmware update for the actual monitor itself ?
So strange least its fixed !@jamiephillips909 The monitor seems to be sleeping again. I installed the 21H1 windows update and all updates following that. I guess it was a windows issue.