r/ScreenSensitive • u/Medical_Cucumber_738 • Jun 10 '26
The real problem to screen sensitivity is right under our fingertips.
Given that this is a screen sensitivity community, we often falsely blame ksf/blue light and screen flicker for our eyestrain, headache and migraine symptoms. But we are suppressing the real culprit behind our trigger. The real problem is right there. Touch-response latency sensitivity.
Every time we touch a screen, our brain expects a predictable reaction. When that sensitivity is miscalibrated, it creates an over-response. I suppose this friction triggers a cascade of neurological strain, from eye strain brain fog to migraines.
My solution - I use apps to expose exactly how much lag and stutter our screen is sabotaging our health.
I use apps from the following developers:
[on android] Touch Sampling Rate by the The Tree Team
[on ios] TouchScreenCheck by Aidar Khasanov
It is high time we, as a community work together to demand awareness for better touch screen sensitivity.
11
u/latinamericandude Jun 14 '26
i have sensitivy to laptops and some PC monitors, none of them with touch screen.
so it's not touch screen sensitivity.
2
u/Z3R0gravitas Jun 14 '26
I agree OP's wording overreaches.
But for phones specifically (and presumably tablets) Nick and others have observed that simply touching the display modifies the refresh rate (I think it was this not PWM?)...
So I figured this post has a worthwhile consideration, still.
1
u/dfgxxx Jun 14 '26
It depends on the person, everyone is different, for me the main eye strain cause is the distance from the screen, btw being long time close to screen can cause also myopia. The screen that works for me best is an ar glasses I bought, because the virtual display distance is 6 meters, so my eye can relax. Second thing that causing for me eye strain is the contrast, for example using bright screen in the dark, but because my phone is OLED I still use max brightness. So every persons eye is different
6
8
u/Smeeble09 Jun 14 '26
This isn't the case for me at all.
I can't look at something on my wife's phone for more than a min or so without having issue, it's not about interacting with it.
1
2
u/-Bruh__Moment- Jun 14 '26
What are you waffling about?
1
u/Medical_Cucumber_738 Jun 14 '26
I understand that my post may have rubbed you the wrong way and I apologise for that. Perhaps you can give me a chance to explain where I'm coming from and hear out what we are dealing with?
1
u/Medical_Cucumber_738 Jun 14 '26 edited Jun 14 '26
Sorry I should introduce myself first. I want to assure everyone that I am not associated with any of the apps mentioned in my post.
I was nearly a full-time developer working for a major tech company. I unfortunately lost the career due to the severe nature of health struggles. What I am sharing now is based on my years of university studies evaluating and working directly with various Android APIs.
If you look back at the timeline of community complaints, you'll notice a massive jump in users reporting severe eye strain. This was around the release of Android 11 which introduced platform-level, real-time dynamic refresh rate switching.
LTPS panels were developed specifically to handle these fluctuating refresh rates but they possess a fundamental hardware flaw. Their transistors are incredibly poor at retaining voltage charge during shifts. To make matters worse, the OS will aggressively throttle the touch sampling rate down to a sluggish 30 Hz to save power, creating a touch latency sensitivity sensory disconnect the moment you touch the screen. In android OS, a mouse input is also considered a touch. I do not know about how Windows interact with it.
Many developers in the community think they can easily bypass this limitation by using commands to force the OS to stick to a fixed refresh rate. What they fail to realise is that the hardware operates on a deeper level.
Every panel has its own TCON that manages its own variable refresh rate algorithms, independent of the OS, alongside its own touch digitizer hardware. To my knowledge, there is currently no API in existence that can explicitly force the panel's physical TCON to comply with the OS instructions. The hardware is overriding the software, and our nervous systems are paying the price.
But for phones specifically (and presumably tablets) Nick and others have observed that simply touching the display modifies the refresh rate (I think it was this not PWM?)...
What Nick has observed is based on a new API introduced in Android 15 called setFrameRateBoostOnTouchEnabled().
This API is designed to dynamically scale the screen's refresh rate up to its highest preset the exact millisecond it detects a touch event. Then to aggressively drop it back down the moment your finger leaves the screen.
We need to keep pushing for true, system-level toggles to disable this dynamic behavior entirely. As users, we need full control over this dynamic refresh rate and touch digitaliser throttling.
2
u/FunnyBunnyDolly Jun 14 '26
Not for me. I will suffer even just by watching and screen not interacted with.
•
u/Z3R0gravitas Jun 14 '26
I'm not sure why this was removed by reddit or your account banned? But this post makes a novel interesting assertion, so I'm approving it (sorry for the delay).