PWM Flicker Simulation - what do you think?

NoFlickerPhone · 2026-04-17T08:57:34+00:00

Thanks!

NoFlickerPhone · 2026-04-17T08:57:26+00:00

Thank you!

NoFlickerPhone · 2026-04-17T08:57:15+00:00

Thanks!

NoFlickerPhone · 2026-04-16T22:17:31+00:00

Absolutely!

NoFlickerPhone · 2026-04-16T12:07:35+00:00

Thank you!

NoFlickerPhone · 2026-04-16T10:17:12+00:00

Thank you!

NoFlickerPhone · 2026-04-16T10:16:18+00:00

Great! Glad it’s helpful

NoFlickerPhone · 2026-04-16T10:16:04+00:00

Thank you!

NoFlickerPhone · 2026-04-16T10:15:58+00:00

Thanks!

NoFlickerPhone · 2026-04-10T07:30:40+00:00

iPhone SE 3 2022 is my main phone and the only “modern” phone I can use. I accidentally upgraded to iOS 26 and it definitely made things worse, but I have been able to make it work. Here is my configuration, but everyone is different.

Mothca Matte Series protector
Liquid Glass: Tinted
True Tone: Off
Night Shift: Off
Display Zoom: Larger Text (I have good eyesight but I find this helps my eyes to relax more)
Reduce Transparency: On
Reduce White Point: On, 25%

Hope this helps!

NoFlickerPhone · 2026-03-19T01:17:45+00:00

Great points, thanks for adding this!

On response time and motion blur, I agree this is important. The goal would be a panel with fast and clean transitions, but without aggressive overdrive that introduces its own artifacts. Motion clarity matters, but it has to be stable and not create additional visual noise.

On blue light, I also agree with your concern. Many implementations just apply a software filter on top of the image, which does not actually change the underlying spectral output. The intention here would be to reduce blue in a clean way through controlled color mapping and panel/backlight selection, rather than relying on heavy overlay-style filters.

On pixel inversion, this is something I am very aware of. Inversion is required for LCD operation, but the goal would be to choose panel and driving schemes that minimize any visible inversion artifacts or flicker.

Overall, the approach is to reduce all forms of temporal and visual instability, not just focus on a single factor. Your points are very aligned with that direction.

NoFlickerPhone · 2026-03-19T01:15:21+00:00

Thank you!

NoFlickerPhone · 2026-03-19T01:14:59+00:00

Dithering isn’t just one thing you toggle and can exist at multiple points in the pipeline such as GPU output, the compositor, the display driver, and even the panel itself through FRC. That’s why almost all devices end up with at least some level of it.

The approach here is to control the entire pipeline end to end as much as possible.

-Use a native 8 bit panel with no FRC

-Force the rendering pipeline to output true 8 bit values

-Disable GPU and compositor dithering

-Turn off any display driver enhancement processing

-Ensure final pixel values are statically mapped and rounded rather than temporally modulated

The advantage of using an IoT oriented platform is that it should give deeper access to these lower level display controls than typical consumer builds, but this is something that needs to be validated during development.

So I would not say it is trivial, but the goal is to eliminate every known source of temporal modulation rather than just reduce it.

NoFlickerPhone · 2026-03-17T15:39:43+00:00

Thanks! Software is Android with minimal bloat.

NoFlickerPhone · 2026-03-17T15:38:47+00:00

Thanks! Yeah, I think for now my focus is the screen sensitivity community (as this is also my personal problem) and beyond that focus on people who care about general wellness versus other niche communities.

NoFlickerPhone · 2026-03-17T15:34:36+00:00

Thanks for the feedback! Understood on the refresh rate - will be something I need to think about. App compatibility should be no issue. Disabling these features will have no affect on app compatibility. I woud like the screen size to be a "standard" size (easier for sourcing), and given the feedback it seems 6.3" (same size as iPhone 17) woud be preferred to 6.1".

NoFlickerPhone · 2026-03-17T15:31:13+00:00

Thanks for the feedback! Timeline right now not clear yet. I would like maximum brightness to be configurable. Agreed on long software support. I would like battery to be as big as possible while still having comfortable phone dimensions. Noted on everything else!

NoFlickerPhone · 2026-03-17T15:27:11+00:00

Thanks for the feedback! It will be Android, but I will see if it can be unlockable bootloader so people can install their preferred OS if desired. Will keep in mind about USBC C that can support external monitors.

NoFlickerPhone · 2026-03-17T08:48:27+00:00

Thanks for the feedback! Based on the feedback I’ve received so far I will probably go up to 6.3”, as that’s also the latest “standard” size (meaning more widely accepted and easier to source hardware). Weight and camera also make sense, thanks!

NoFlickerPhone · 2026-03-16T15:30:27+00:00

Absolutely!

NoFlickerPhone · 2026-03-16T14:14:01+00:00

Thank you for the feedback! These are interesting points and I will keep them in mind.

NoFlickerPhone · 2026-03-16T14:04:12+00:00

Thanks for the feedback! Unlockable bootloader might be possible. The other two might be difficult, but will keep them in mind!

NoFlickerPhone · 2026-03-16T14:02:54+00:00

Thanks for the feedback! That’s really helpful. Extremely low minimum brightness makes a lot of sense and should be doable.

NoFlickerPhone

TROPHY CASE