JUMP TO SOLUTION Solved

Original topic:

S24 Display Quality & AOD Missing Options

(Topic created: 01-30-2024 03:53 PM)
1741 Views
Locoblade
Asteroid
Options
Galaxy S24

Hi All

I've just got my S24+ today to upgrade my trusty but ageing S10+ having not strayed from Samsung for almost 10 years. Naturally I was hoping it would be an upgrade in all departments but although on the whole it is, there's several annoying and unexpected downgrades that are making me seriously question whether it's actually worth spending quite a bit of money to change.

Firstly, the screen although pin sharp is really washed out. Even in vivid mode the colours are dull and the blacks are significantly more grey than the S10 screen, and even look washed out when put alongside my wife's budget spec A52! I've played around with brightness and colour tone etc but I can't dial it out, and my cousin who's got an S24 Ultra said exactly the same when comparing it against the S22 it's replacing.

Then there's some bizarre features missing from OneUI 6.1, the ones I've noticed so far are specifically in the Always On Display settings.  I use AOD to display as a bedside clock,  with my S10 and also in OneUI 6.0 / Android 14 on the A52 you can rotate the AOD to landscape orientation and control the brightness, you could even do the latter from the AOD lock screen by tapping twice on the clock to access the brightness slider. In OneUI 6.1 unless I'm missing something it seems all that functionality is missing, the brightness of the AOD is linked to the main screen brightness setting which is far too bright for overnight use, and you can't set it to landscape mode which I'd prefer when on it's horizontal night stand next to the bed. Why this functionality would be omitted I have no idea, but it's really annoying! Please someone enlighten me to some hidden menu somewhere that fixes all these issues?! šŸ™‚

3,256 Replies
Gareee
Galaxy
Options
Galaxy S24
You've obviously not bothered to read the hundreds of other comments or solutions.
Samsung already confirmed the vivid mode setting it not working properly, and a fix is already in the works as of a few days ago.
Options
Galaxy S24
Can you post a link?
0 Likes
Gareee
Galaxy
Options
Galaxy S24
It was posted here in one of the million replied 2 days ago, I think... several youtibe videos about the issue also have it posted in the comments.
0 Likes
Options
Galaxy S24
That's good to know. Just gotta wait now.
0 Likes
Tidbitty
Supernova
Options
Galaxy S24
Don't expect a super drastic change. It's a matte display.

Before anyone says it isn't matte displays always reduce glare, and reflections, at the cost of brightness and color production. Glossy displays are the opposite. If a Glossy display could reduce glare and reflections at 70% that company would have already put it on Profesional displays.
Dipsy30
Galaxy
Options
Galaxy S24
Posted on Sunday night1706659619177.jpg
Options
Galaxy S24
That's good to know. Easy fix.
0 Likes
DronePro
Asteroid
Options
Galaxy S24
  • By now you have heard of the issues and I can say they certainly are true. I have now had my S24U for 2 days and the one and only time this phone is better screen wise than the S23U is when playing a YouTube video that is UHD with HDR and full brightness. The rest of the time, the S23U screen beats it hands down. S23U (in my experience) is brighter, more vibrant, colors look souch better. If it want for the anti glare of the S23U screen, I would consider it an absolute, 100% flop. Head over here to see the conversation and pictures. 
  • https://eu.community.samsung.com/t5/galaxy-s24-series/s24-ultra-washed-out-colours/td-p/9019030
Popsicle20
Red Giant
Options
Galaxy S24
There is a known bug in Screen Mode where the phone is stuck on "Natural" and cannot be switched to "Vivid". Samsung is aware of this and is working on a patch to fix it.

https://m.youtube.com/watch?v=RY80K_Fe0Vs
0 Likes
DronePro
Asteroid
Options
Galaxy S24
Correct. There seem to be more than 1 bug but apparently it's being worked on. Not sure how so many devices left the warehouse with this bug