Just realized that the wiki is already rather plentiful in info, that i had missed, as i hadn't thought its content would be "hidden" in the left tripleline menu. Whoa!
Pinning / Wiki
What if a tag could be created for threads with solutions?
Mrak0020 That is the purpose of the tag "usable"
https://ledstrain.org/t/usable
- Edited
I think also that it will by far help more people than specific other solutions, since it is a quick fix for all binocular issues which are caused by many different triggers which themselves need different and more complex fixes.
From my perspective it should be as present as the other two pinned posts, since even if it the worst solution for many people here, it is at least the most generic and easy to apply.
I would ask if it is only an binocular issue then, since you have no binocular vision at this point. I know that your covered eye can move roughly in that arena even when covered and it takes some time to get used to covering your eyes, but in generell you get positive results very quickly if you have binocular problems.
If you have problems with one eye in specific those can still be there even if one eye is covered.
- Edited
xelaos it is most definitely one, but triggered by some extra dangerous light. It is described in thread https://ledstrain.org/d/1320-lightversion-problem
And it is quite common on tech forums, not on this one though.
The logical connection is reversed in this case, it is light causing binocular vision problems, not vice versa.
Sure, if you have problems with one eye it can lead obviously to vision problems with both eyes. It is also easier to compensate monocular issues if you only use one eye. So I'm totally with you.
In case of monocular issues covering on eye as you outlined don't necessarily fix all your problems.
xelaos sure, and that is why i am highlighting this: symptoms are the same, problems with convergence. In my case they start immediately after phone usage and are not present before.
This is why it is important to distinguish these issues, both are with binocular vision but when the reason is some dangerous light, pushing through the pain might be dangerous to retina.
- Edited
I have created a simple "links" page. I'm not sure of the best way to organize this information, so we can try using this as a sort of scratchpad.
https://wiki.ledstrain.org/docs/link/
https://wiki.ledstrain.org/contribute/#/collections/links/entries/_index
Thank you!
This is a sample of how an organized text with known problems, tests and solutions for newcomers could look like: https://ledstrain.org/d/1404-eyestrain-triggers/8
(I already tried using forum as a scratchpad )
What do you think about it?
It seems links solely will be not enough for organizing info, or maybe if some links will redirect to another wiki pages with text...
## Basic issues with smartphones that can be fixed easily:
- Minimal brightness is too high: There are many applications that can apply a black filter to the screen and thus reduce the screen brightness below the minimal system brightness, for example: Screen Dimmer, Screen Filter, Darker.
- Problems with auto brightness: Try turning off auto brightness and adjusting it manually, or install a third-party application from the GooglePlay.
- Dynamic brightness: A more malevolent version of auto-brightness: a built-in brightness adjustment in the firmware that cannot be turned off in the settings. This is how it is implemented on Nova 5T, for example. Dynamic brightness is easy to spot, but difficult to remove. Try asking on the forum of your device, which system file is responsible for this and how to delete it. Deleting system files can lead to some problems and bugs.
- Rough surface of anti-reflective film, bad protective film or glass
- Improper lighting conditions and a lot of reflected light rays from a glossy screen surface
- Wrong screen distance: too far, to close
- Screen too large /screen too small: If a large screen creates too much light for you, try moving it away and at the same time increasing the font / scale of the elements.
If the screen is too small, then the eyes will strain, reading, especially if it has a very small font.- Using the screen in the darkness: The same as with a minimal brightness: try software that apply a black filter to the screen and thus reduce the screen brightness below the system level, for example: Screen Dimmer, Screen Filter, Darker.
- Incorrect brightness and color temperature setting: A general rule of thumb for eye comfort is that white on the screen should look the same as white on a piece of paper in your lighting. Take a sheet of white paper, place it next to your phone and try to achieve:
the same brightness of the sheet and the screen the same shade of the sheet and the screen, the color temperature of the screen and the ambient light must match- Small font size: Adjust the font to a comfortable size, enable scaling of screen elements - the picture should be comfortable, your eyes should not strain when looking at small objects.
- Not sharp enough font, anti-aliasing problems: On Windows there may be problems with font anti-aliasing, ClearType. There were no complaints about font smoothing on mobile operating systems; the factor is given here "just in case". So far, there is no data on it.
Thanks for submitting this
I put this on the pull request, but in case that doesn't reach you,
Sourcing is needed. It's ok to link, embed or quote to show that
Something that says, I have this problem, I did one / some of these and it worked for me to solve that problem
Mrak0020 If I update the post, will wiki update automatically or it should be done manually?
Yes, it is automatic once changes are approved. If the changes requested consistently look good, I am pretty sure I can set them to not require approval
- Edited
As per @Slacor's request, I'm trying to find sources for your infos one by one via forum search. That may take me some time. If you can provide sources (for one or more of your smartphone infos) please send me private messages for them, so we can get this done faster
Edit: You can see my current link-adding progress here.