topic Samsung Tab s10+ - spen writing flickers after update to UI 7.0 in Tablets

Samsung Tab s10+ - spen writing flickers after update to UI 7.0

Yivs — Fri, 25 Apr 2025 14:32:10 GMT

I updated the system to UI 7.0 yesterday and since then everything is buggy.

Most annoying is the SPen - in any of the writing apps - Samsung Notes, Noteshelf 3, and others, whenever I'm writing, at random some of the newly written text flickers. Sometimes it's very light, sometimes it's the whole thing blinking in and out.

I've updated everything, cleaned cache multiple times, restarted multiple times, reinstalled even a number of the software and still the issue persists. I really hope Samsung releases fixes ASAP.

If anyone has any ideas of what I could try to fix this - please let me know.

There are no screen protectors, or magnetic covers on my tablet, so nothing is in the way of the spen to work properly.

It's strictly and only when writing.

(view in My Videos)

Re: Samsung Tab s10+ - spen writing flickers after update to UI 7.0

Otlayanadam — Wed, 02 Jul 2025 07:32:29 GMT

Solution steps for the S Pen flickering issue on Galaxy Tab S10 Ultra with One UI 7

First, try using only 60Hz refresh rate. This often solves the problem without any other changes.

Step 1
Go to Settings
Display
Motion smoothness
Select Standard 60Hz

Step 2
Check if the flickering is gone

If the problem is still there, then try this:

Step 3
Go to Developer Options in Settings
Find the option called Disable HW overlays
Enable it

This forces the GPU to handle all screen compositing and usually fixes the pen input issue completely

Notes
Using 60Hz alone is better for battery life and may be enough to solve the problem
Disabling HW overlays can increase battery usage but it also improves stability

Summary
First try 60Hz refresh rate only
If it does not help, then enable Disable HW overlays as a second step

This worked for me

Re: Samsung Tab s10+ - spen writing flickers after update to UI 7.0

Yivs — Wed, 02 Jul 2025 07:46:09 GMT

Big thanks! This solved the issue!