Related
RootDim (formerly known as ScreenDim) lets you set the screen brightness on backlit screens below what the OS normally allows, which is handy for amateur astronomy where the lowest normal OS backlight setting (even with a red nightmode) leaks enough through the black pixels to damage night vision. Moreover, SuperDim lets have several brightness profiles, and to include nightmode settings (enabled by ChainFire3D or Cyanogenmod's render fx) as part of the brightness profile.
Needs root.
Public domain, source code available. In Market (search for RootDim).
Now in Market (free, no ads).
I just uploaded version 1.10, which restores low brightness settings after the screen is turned off and back on (the OS normally was restoring its brighter screen).
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
bobtentpeg said:
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
Click to expand...
Click to collapse
I assume this is when you use the other lights option to toggle these lights, or when you restore a profile, right?
In version 1.11 (just uploaded), I no longer restore other lights when a profile is loaded--this should help with your problem, as long as you don't touch the other lights. Eventually, I may add an option to choose which lights get restored from a profile.
I originally made SuperDim for setting very low backlight settings on LCDs, and so I made it not work on non-LCD screens (e.g., OLED). But I've since realized that the profile feature might be useful for non-LCD users as well, so I've released version 1.20 that supports non-LCD screens. It's in Market. While I was at it, I cleaned up the code a little, made it more javaish (I'm new to java).
My MyTouch 4G just seems to turn the screen off totally if i go below 20 brightness, it dims but then shuts off.
Doesn't work at all with Dell Streak 5
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Awesome, thanks for the Advise!
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Screen filter merely adds a black semi-transparent overlay across the screen, making it look dimmer.
This app adjusts the backlight, which means darker black levels on the screen.
Frosty666 said:
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
Click to expand...
Click to collapse
My eyes don't care. +1 Screen Filter
lownox said:
My eyes don't care. +1 Screen Filter
Click to expand...
Click to collapse
Your eyes would probably care if you were doing amateur astronomy under a dark sky (which is the primary purpose for SuperDim). Screen Filter doesn't turn down the backlight, and on a lot of devices there is enough backlight leaking through even completely black pixels to damage night vision. You can try this experiment. Turn a backlit device to a completely black screen (maybe view a black jpg) and take it to a completely dark room. Let your eyes dark adapt. The "black" screen will in fact probably be quite grey. (If it's really black, that's probably because you have an OLED device.)
When I do amateur astronomy, I am not infrequently looking to see objects way dimmer than backlit black pixels.
I'd like to do something about the screen turning completely off issue.
To that end, I need people to do some experiments for me, and I will be very grateful (I'll also give a free full version of Force2SD as compensation for the first couple of experimenters, if you want it--just email me). The first experiment is this. Download SuperDim 1.22, now up in the Market. Press the menu key, and choose "Turn on safe mode" (you can tell safe mode is on, because next time you pull up the menu, it says "Turn off safe mode"). Now, turn brightness down to 10. Does your screen turn off?
I should warn that very low brightness levels can be very low indeed. For instance, if I am outdoors on a sunny day, I have trouble telling the difference between brightness 4 and off. So you need to be in a dark area--I recommend a room without windows and with the lights off.
If the screen does not turn off at 10, turn it down to 5, and then 1. Let me know if it ever turns off.
I am guessing that in safe mode, it doesn't turn off at all.
What safe mode does is it makes very low brightness settings not persist. So if you are in safe mode and leave SuperDim, you lose your low brightness setting.
I'd also appreciate it if people who can normally turn their brightness down to 1 could do some experiments with safe mode. Specifically, I'd like to know if moving the slider to 1 in safe mode has the same effect on screen brightness as moving the slider to 1 in non-safe mode has. (Again, if you're one of the first few experimenters and want a free copy of Force2SD, email me.)
On my Archos 43, brightness 1 is very, very dim, but the screen is still on. And I can't tell the difference between safe mode and non-safe mode, except that in safe mode, the settings don't persist after I leave SuperDim.
Tried this app on my desire HD.
Great idea, but when I reach 10 and below, the backlight doesn't get lower.
If I use the adb method (don't remember the command), I can set the backlight manually all the way down to 0.
There is no difference with or without safe mode on.
inspire 4g with coredroid V7.0 doesnt work
elmanortega said:
inspire 4g with coredroid V7.0 doesnt work
Click to expand...
Click to collapse
What happens? And does safe mode work?
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
kamranh3 said:
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
Click to expand...
Click to collapse
I found a bug. In fact, the bug is such that I have no idea how it was managing to work on my device at all! In any case, I think I fixed it. Try 1.23 (should be in Market or here) and see if it does the job. If not, I have some more ideas.
Hi!
It may look strange, but I really would like to keep the screen of the gear watch always on, at the lowest possible light setting and that when the watch detects the wrist movement, the light settings come back to the normal one.
I'm sure this will add up to very low battrey life. But if I can get a day like this, it would be great!
Thanks!
I wanted this at first, because coming from the Pebble -it's just so convenient having the screen accessible all the time and the gesture doesn't always register.My idea was that it should just be a very minimal screen in terms of pixel use to leverage the power saving qualities of the AMOLED tech. Problem is, the AMOLED screen is also known for burn-in on the phones, so I'm afraid even if we set this it would damage the watch screen in the long run (and I would be ok if I only got a day of use also, as I'm fine charging every night anyways).
There is a watchface called "AlwaysWatch" in the Samsung Gear store that's supposed to give you an always on face until the battery runs out. Problem is, it runs as an app instead of the default face and of course I'm afraid to try it due to the burn-in issue. I sent the developer a note saying make the watchface a small, but still legible digital font instead of analog and float the time around the screen periodically would get around this burn-in risk, we'll see if he adds the option.
Thanks for the info on this app (I also have a pebble ).
In order not to burn the screen, it would be preferable to change the watchface form time to time and put it in the lowet light possible...
FixB said:
Thanks for the info on this app (I also have a pebble ).
In order not to burn the screen, it would be preferable to change the watchface form time to time and put it in the lowet light possible...
Click to expand...
Click to collapse
One of my disappointments besides the flaky gesture wake up is that there doesn't seem to be an ambient light sensor to trigger screen brightness changes. I would have thought that would be a no brainer for a device such as this by now.
rEVOLVE said:
One of my disappointments besides the flaky gesture wake up is that there doesn't seem to be an ambient light sensor to trigger screen brightness changes. I would have thought that would be a no brainer for a device such as this by now.
Click to expand...
Click to collapse
Maybe the camera light sensor in the Gear 2 could be used for that purpose?
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
Enable Settings -> Style -> Watch Always On
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
I don't think I've really ever used the default faces. I know in a lot of the Watchmaker faces you can get a toned down face with maybe just the numbers and hands glowing when using AOD mode but I don't know about the default faces. In display settings there's a setting for auto low brightness that may affect that.
10urshin said:
Enable Settings -> Style -> Watch Always On
Click to expand...
Click to collapse
If you read the first sentence of my post you'd see that I'm already using this setting.
tamanaco said:
If you read the first sentence of my post you'd see that I'm already using this setting.
Click to expand...
Click to collapse
Yea i have read it. Not just first sentence but I also read the whole thing, you must admit it is not really making much sense. "Screensaver"? There is no such thing on this watch, only AOD and "Now the displays dims after the time out and then it turns completely off (black)." this sentence perfectly describes the AOD off behavior. So i thought it worth mentioning.
Only other thing that comes to my mind is default analog AOD watchface(attachment) which is something watch shows if the current watchface does not support AOD. But since you stated that you were getting your "screensaver" on Chronograph+ which supports AOD, it doesn't really make sense either.
Anyway hope you'll find your answer.
I also saw this "screensaver" mode in a review video somewhere, but I have not been able to locate it again. Once I find it, I'll post a screenshot of it.
tamanaco said:
While I had my my AT&T S3 Frontier LTE watch set to "Always On" I was getting something like a "Screensaver" which consisted of just the hour and minutes hands in white on a black background. It came on after the watch display dimmed and after the display time out. This happened while using the Chronograph+ (default) watch face. It was a distinctive + useful screen face that probably saved me some battery life. Now the displays dims after the time out and then it turns completely off (black). After I power cycled the S3 yesterday, I stopped getting this "Screensaver" and can't find the settings combination that will get this "screensaver" back. Does anyone know what I'm talking about and how to get it back?
Click to expand...
Click to collapse
Thinking more about it, I don't think the AOD is even supposed to remain on all the time. That has been a major complaint, the AOD mode not being actually AOD. What you're experiencing now isn't normal and there should be no setting to change that. If you want to set up the watch again, you might try resetting it. That's assuming you've already tried just restarting it.
What comes to my mind with "Watch always on" (or "Always On Display", AOD) and having screen completely black is if watch thought at some point that you weren`t wearing it - only in that case should the screen go completely black with AOD set, otherwise it should, well, keep "always on display", that`s the point of the setting
When you take the watch off your hand, then it goes blank even though AOD setting is still active - watch is "playing it smart" to preserve battery life in case where you`re not actively using it.
But, it`s possible for the watch to (wrongly) think that you`re not wearing it even when you do, thus turning the screen off when it should otherwise be in AOD mode (as set). For example, it can happen when your wrist band is a bit loose so the heart rate sensor has issues reading your pulse, or when the heart rate sensor itself is smudgy or otherwise blocked to make the valid reading - some people with tattoos reported that AOD doesn`t really work for them, having the screen constantly turning off (tattoo effectively confusing the heart rate sensor reading).
This is especially troublesome if you`re using "Samsung Pay", where the watch asks for you PIN in order to unlock itself every-single-time, as it`s thinking that you didn`t wear it in the meantime...
All this said, from what you described, it looks like AOD doesn`t work for you at all anymore, as what you seem to call "Screensaver" is actually AOD - a dimmed and more simple version of the watch, whose main purpose is to spare the battery while still providing a bit more realistic feel, having the watchface shown all the time.
There is additional "trick" to trigger AOD mode (once you have the setting configured), besides simply waiting for some (configured) time to pass by - just cover the watch with your palm for a few seconds, and it should fall back to AOD mode. If the screen goes blank instead, you might have an issue with the watch.
It would be good to have some default watchface in use when you`re trying AOD (like mentioned Chronograph+), just to opt out a possibly "broken" third-party watchface, and you could also check if "S Health" heart-rate reading works for you, starting a heart-rate readout manually (you can use a widget for that as well).
If the issue is still there, you may try restarting the watch again, or eventually soft (or factory) resetting might be a thing to go for, too, though you`ll have to setup the watch again, as already mentioned.
I have seen the exact same behavior. My AOD will suddenly become black and white, while normally it is full color, and any app icons that are usually on the AOD disappear. When the watch is active (by turning wrist or touching the screen), the full color face returns and looks normal - it is only the AOD that is always B&W. The difference for me is that I don't like it and I would like to figure out how to get it to stop happening.
I've had the watch for about 2 months and it has happened to me 3 times with different watch faces. It lasts from several hours to more than a day. I have changed every related face setting, changed faces, changed face settings, AOD settings, restarted, and reset the watch completely (and restore), but it still happens. The only thing that I've noticed may help (may be coincidence) is that it will stay indefinitely until I power cycle the watch. After restarting, the AOD remains black and white for a few hours and then suddenly the color AOD will return. Next time it happens I will take a pic.
I'm actually somewhat relieved that I'm not the only one who has seen this because my googling revealed next to nothing. I don't know if I would call this a screensaver, but it would be nice to be able to control it.
annulation said:
I'm actually somewhat relieved that I'm not the only one who has seen this because my googling revealed next to nothing. I don't know if I would call this a screensaver, but it would be nice to be able to control it.
Click to expand...
Click to collapse
I knew I was not seeing things... please take a picture if it happens again, so that we can have a reference image. I'll do the same if it happens to me again. In certain situations... I actually like just having the hour and minute hands in "brightish" white on black background. Like you, I would also like to control it. I thought it was a "screensaver-like" feature as the watch face turns mostly black. But as you say, it might be a glitch... it has not happened to me since I last power cycled the S3.
Low Color AOD
I finally figured it out.
The behavior is called "Low Color AOD" and "High Color AOD". It is controllable by swiping from the right side of the screen near 5 o'clock straight up. This consistently toggles it for me, and a popup message shows a message saying either "Low Color AOD" or "High Color AOD". See pics attached (sorry, don't know how to rotate them).
Pics:
1. Low Color AOD
2. High Color AOD
3. popup message Low Color AOD
4. popup message High Color AOD
Only some faces support this behavior. For me, "Low Color AOD" always means monochrome B&W and no app icons.
PS - this face is called "Stylish Set" and the creator gives free coupons for it if you email him. It is one of the few faces I've found that shows day/date, with temperature and battery.
As mentioned, the function described is dependent on the functionality of each watch face independent of the watch itself. If a given watch face supports it, it can be accessed. The "always on" function also depends on the capabilities of each watch face. Some have customized always on displays, and some do not (generic). The watch will go black if it senses it is not against the skin (the sensor on the back). This will also cause the watch to lock again and require the security code to re-activate. If a band is too loose, the watch can falsely think it has been taken off. The time that the watch face itself is on can be extended with an app called "Flaunt" available from the Galaxy app store. It can extend the original watch face active time to 30 minutes. It can then be re-activated to extend for other 30 minute time periods. Of course it does impact the battery life.
Yesterday i noticed something strange in my OP7p and i'd like you to check whether something like this occurs in your phones. Issue, which i will describe occurs only when i have 90hz refresh rate set and the low brightness of the screen with the auto adjustment of brightness turned off. The easiest way to see that is on youtube application with a dark theme. When we start a movie on the full screen (horizontally) and watch it for a few seconds, then go back to the vertical position, there is something like weak but visible blink of the screen, or a minimal colours change. It can be noticed in other apps, e.g. on facebook. Seems to me this is a software problem, beacause the same phenomenon doesn't exists when we set 60hz refresh. I would be very grateful if you can check it on your phones and give me a know about it.
I don't usually start videos in full screen mode and never noticed it but yeah definitely does a white flicker.
This is the highest brightness I could get it to do the flicker at.
Thank you for an answer. Personally i am able to see this flicker on a little bit higher screen brightness, but maybe its because im sitting in a dark room now. I was worried cause sometimes i see it during the normal usage of phone, and if only my OnePlus would be affected by this flickering i could still return it or exchange for a new one. It isnt very disturbing however interesting is whats cause of it.
kamkoz96 said:
Yesterday i noticed something strange in my OP7p and i'd like you to check whether something like this occurs in your phones. Issue, which i will describe occurs only when i have 90hz refresh rate set and the low brightness of the screen with the auto adjustment of brightness turned off. The easiest way to see that is on youtube application with a dark theme. When we start a movie on the full screen (horizontally) and watch it for a few seconds, then go back to the vertical position, there is something like weak but visible blink of the screen, or a minimal colours change. It can be noticed in other apps, e.g. on facebook. Seems to me this is a software problem, beacause the same phenomenon doesn't exists when we set 60hz refresh. I would be very grateful if you can check it on your phones and give me a know about it.
Click to expand...
Click to collapse
this is usual for EVERY Oled screen and is called jelly effect...
You might want to try the DC dimming option in Settings->Utilities->OnePlus Laboratory.
matze19999 said:
this is usual for EVERY Oled screen and is called jelly effect...
Click to expand...
Click to collapse
From what i know jelly effect appears while we scrolling some content and propably that's not what i meant in my first post. Also flicker in my case is only visible on 90hz refresh rate.
I have galaxy s7e as a second phone and that effect doesn't happen there.
vishal3967 said:
You might want to try the DC dimming option in Settings->Utilities->OnePlus Laboratory.
Click to expand...
Click to collapse
Thanks but i tried this option and it didn't do the job well.
I have read articles that said using DC brightness on OLED/AMOLED screens can effect colors, particularly at low brightness. How are people finding it? I dont really care if it makes colours "less accurate" as long as they dont look weird
Looks fine to me. Barely can tell the difference.
Working well as described, couldn't tell the difference.
Can someone try to port it to OnePlus 3 / 3t?..
anz563 said:
Can someone try to port it to OnePlus 3 / 3t?..
Click to expand...
Click to collapse
What makes you think the 3 / 3T screen is capable of DC dimming? Can every AMOLED screen support it?
First off, I don't notice any flickering when the screen brightness is low so maybe DC dimming isn't for me. I'm sure someone with a fancy color monitor device will probably post a technical breakdown of how it affects the screen, but I don't see any difference except in one scenario.
In bed I tend to set the brightness settings on the lowest and then turn on nightmode to dim the screen even further. If you have small white text with a black background such as the settings menu or Youtube in dark mode, some of the text fades into the blackness and is unreadable. Images with dark colors or areas will look weird because you won't be able to distinguish them apart.
I tried to take pictures to show a comparison, but the screen is so dim that it doesn't work.