4k 120hz issue

Looking at the Sony website, I see this,



and the footnotes for this tv also show this

Hi,

Do you have the Xbox One, or the Xbox Series S? You'd be surprised how many people get the names confused.

If it's an Xbox One S, then that console doe not support 120Hz @ 4K. Also, the HDMI out on the Xbox One S is HDMI 2.0, not 2.1. Only the Xbox Series S and Series X support 4K @ 120Hz via the console settings. The One S is only 1080P.

Bear in mind also, that there are no games for the Xbox One S that do 120Hz (or 120 fps). The 120Hz option is only there to support VRR (variable refresh rate).

If you want to play 120Hz supported games, you will need a Series X. The Series S support of 120Hz games is a lot more limited.

Note that on the Qn95a, only HDMI 4 supports HDMI 2.1

Hi,

Thanks for the reply. I've been trolling through Sony site for a few hours.

The update should of activated those features.

I have just found that only hdmi ports 3 and 4 support 2.1 connection and4k @ 120hz.

But still wasn't showing for the tv. I've now managed to sort it out, you have to go into the tv sub menu in display settings and switch on the hdmi 2.1 setting and 4k@ 120hz.

Doesn't just do it once updated and a restart.

VRR though still isn't available for now, but it as you found it will come at some point.

Thanks very much for your reply, and taking the time to have a look as well.

Cheers

Hi
My name is Rishabh an Independent Adviser, I hope you are doing great out there.

It sounds like you're experiencing an issue with your Samsung QN95A Neo QLED TV not allowing you to select 4K 120Hz when connecting your Xbox One. This could be due to various factors, including compatibility, settings, or cable issues. Here are some steps you can take to troubleshoot the issue:

1. Check HDMI Port:
Make sure you're using the HDMI port on your TV that supports 4K at 120Hz. On some TVs, only certain HDMI ports are capable of handling higher refresh rates and resolutions.

2. Enable HDMI 2.1 Mode:
Check if your TV has an HDMI 2.1 mode that needs to be enabled. Some TVs require you to enable this mode manually in the settings to support higher resolutions and refresh rates.

3. TV Firmware Update:
Ensure that your TV's firmware is up to date. Manufacturers often release firmware updates to improve compatibility and fix issues. Check Samsung's official website for the latest firmware version for your TV model.

4. Xbox One Settings:
Check the settings on your Xbox One. Go to "Settings" > "Display & sound" > "Video output" and ensure that the resolution and refresh rate are set to the desired values (4K and 120Hz).

5. TV Display Settings:
Navigate to your TV's display settings and make sure it's set to the proper input source for the Xbox One. Also, look for any specific settings related to display modes or input settings that might affect resolution and refresh rate.

6. Cable Quality:
You mentioned that you bought a new HDMI 2.1 cable, which is the right step. However, make sure the cable is properly plugged in and that it's fully compatible with HDMI 2.1 specifications.

7. Test with Other Content:
Try connecting another device that supports 4K 120Hz (if available) to the same HDMI port on your TV. This can help determine if the issue is specific to the Xbox One or the TV itself.

8. Factory Reset:
As a last resort, you might consider performing a factory reset on your TV. Make sure to back up any important settings before doing this.

I hope this helps! Let me know if you have any other questions.

Thanks and regards
Rishabh Sohal

It's capped at 120hz over HDMI anyway so it shouldn't be an issue. Unless I go via DP then I could access 144hz so that's irrelevant. I really don't understand what your response is about and the firmware is up to date.

I can do 4K/120hz without HDR fine, I can do 4K/60hz with HDR fine but it seemingly doesn't work doing 4K/120hz/HDR which points to it being an Xbox issue.

I can do 4K/120hz/HDR on my PS5. The PS5 supports standard VESA resolutions and refresh rates over HDMI so I feel the blame is being shifted here.