-
-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE: E-Ink theme #1175
Comments
Do you know an Android app that simulates your display colours? I don't have an E-Ink device to test |
Thank you. I have searched online and found that the Developer Options of Android enable one to set the screen colours as monochrome. If you would like to add a theme using the colours stated below, prominent borders, and high contrast, I would be happy to test.
|
I appreciate the RedReader team's interest in accessibility. Thank you! |
I can activate a black and white mode on my Android 12, but it has a lot more than 8 shades of grey, and Redreader still looks good. I would need an app or option that limits the display to 8 shades of grey, and unfortunately I haven't found anything like that |
It might be easiest to take a screenshot in full colour, and then use an image editor to convert it to 3-bit/1-bit monochrome to see how it looks. |
Thank you, I asked on the E-Ink Reddit sub: https://www.reddit.com/r/eink/comments/1atoeed/which_greyscale_colours_should_an_application/ EDIT: A commenter on that question had some good tips:
|
The extant RedReader themes are not suitable for E-Ink devices. Many buttons are unable to be read in any theme, among other smaller issues. May I suggest that an 8-level greyscale theme be added to RedReader?
I did try the OLED focused Ultra Black theme, but I found it unsuitable for E-Ink devices for the following reasons:
I expect that there are other problems that I do not know about, simply because I cannot see them!
I am using RedReader version 1.23.1, to which I upgraded from whatever was current in February 2023. That February 2023 version has these same issues, I upgraded specifically to see if things had gotten better.
The text was updated successfully, but these errors were encountered: