I've noticed with my G2 for quite a while that the screen brightness will dim by itself with auto brightness turned off. I have the brightness set at 70%. When I wake the screen and go to Gmail or any other light themed app where it's noticeable, the screen will dim approximately 5%. I did a little testing this morning and it only happens when the area is well lit. In the dark hallway, it wouldn't dim at all. I am running Cloudy G3 1.2 on my LS980. I've noticed the same thing on versions 1.3 and 2.0. I do think though, it's likely something to do with the proximity sensor rather than the ROM. I've tried different kernels and the same thing happens. I also have Xposed installed with the Tweaksbox module, but with Xposed disabled it doesn't change. I haven't had time to go back to stock and test but will try soon if nothing is resolved.
Anyone else experience this?
Related
I noticed that the brightness only brightens but never dims back in automatic brightness display setting. I can reproduce this easy with turning the lamp on my desk on and off. It only goes back to the lower brightness if turning the screen off and on again.
Noticed this too but seems to only occur when I use a widget to toggle between Auto and 100%.
If I leave the setting in Auto from within settings then it seems to work. Brightness widgets seem to break the auto functionality.
Hmm, I don't use a brightness widget. The light of the softbuttons go on if I cover the light sensor, but the screens stays in high brightness.
Strahlenkanone said:
Hmm, I don't use a brightness widget. The light of the softbuttons go on if I cover the light sensor, but the screens stays in high brightness.
Click to expand...
Click to collapse
Must be an all around bug then. If you turn the Atrix off and back on then the auto brightness functionality is restored.
Strahlenkanone said:
I noticed that the brightness only brightens but never dims back in automatic brightness display setting. I can reproduce this easy with turning the lamp on my desk on and off. It only goes back to the lower brightness if turning the screen off and on again.
Click to expand...
Click to collapse
This must be an Android thing. My Atrix does the same thing, as did the Nexus One I had before. I've had several (high end) Nokia's that dimmed/brightened perfectly. After 5 seconds, they would brighten (or dim) accordingly. I was hoping Motorola was better at making phones than HTC (the KING of bad battery life). We ALL lose here. Our precious battery life is being drained by the poor execution of a simple function.
This is a stock android thing (problem). Custom ROMs can allow it to dim and change brightness smoothly rather than in discrete steps (Cyanogen).
That's what I thought. I found this free app called "esdimmer". It supposed to be for Galaxy phones, but it's somewhat working on my Atrix. Does this function work any better in Gingerbread?
Sent from my MB860 using XDA App
Well it's good to hear that it's a stock android problem and not the actual phone. I did find a way to get around this problem but it's very limited. You can get the screen to dim by first putting the phone into standby and then press the standby button once again (which gets you into the lock screen). You'll notice that the screen then dims (if coming from a well lit area/room to a darker one).
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Now that I'm able to Google, I realize it's a common problem with the S4.
Sent from my SGH-I337 using Tapatalk 4
Serfma said:
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Click to expand...
Click to collapse
The only time I had the screen go dim like you describe is I remember once following a phone call. It goes dark when you put the handset to your ear like it's supposed to, and lights back up when I pull it away from my head. I was stepping out of a truck into the broad daylight when I tried to hang up my phone, I couldn't see the screen very well. The other party ended the call, and my screen timed out while I was squinting at it. I pushed the home button and it lit right back up nice.
You got something going on, and if you tried all those different roms, say... can you nandroid back to stock? Did you try that?
I'd try everything I could on the outside chance of repair instead of replacement. If you get a replacement you might be stuck with that MF3 where you cannot install a custom recovery.
fukenbiker said:
The only time I had the screen go dim like you describe is I remember once following a phone call. It goes dark when you put the handset to your ear like it's supposed to, and lights back up when I pull it away from my head. I was stepping out of a truck into the broad daylight when I tried to hang up my phone, I couldn't see the screen very well. The other party ended the call, and my screen timed out while I was squinting at it. I pushed the home button and it lit right back up nice.
You got something going on, and if you tried all those different roms, say... can you nandroid back to stock? Did you try that?
I'd try everything I could on the outside chance of repair instead of replacement. If you get a replacement you might be stuck with that MF3 where you cannot install a custom recovery.
Click to expand...
Click to collapse
Mf3? Is that something new with the S4s to prevent custom ROMs?
It does not go pitch black. It goes very dim every time I wake the device. If you Google S4 screen dimming it's a wide problem.
Once you wake it, it's fine for 2 seconds and dims quite dark. It is not screen timeout/sleep/etc since I can still see the screen.
Sent from my SGH-I337 using Tapatalk 4
I'm on MDJ and don't get any auto dimming of any sorts. Auto brightness is off, brightness controls about 1/3 brightness (indoors), but Power Saving mode is on with all three options on.
My S4 is MDL. I found out the problem (More than likely) was the Paranoid Android ROM. I was on ver. 3.69 and since switched to CM 10.2 Nightlies, latest as of today, and no screen dimming. I will install my usual apps and use it as normal and if it happens, it's probably an app. However, the only apps I use are ones such as SwiftKey, LightFlow, ASTRO, Chrome, and Dashclock.
I'm on stock MDL. It has only been occurring since I upgraded from MDB 3 days ago, and is a huge PITA because brightness controls are unresponsive during this time - I go into settings to adjust brightness since I have removed all the brightness controls from the notification panel as they've always worked just fine, and turn off auto brightness, scale it all the way to max, and it is still dim as crap.... Only fix I've seen is to reboot, which is obviously not ideal in most situations when I need to wake the device! I'm using STOCK kernel, STOCK ODEXED ROM as well, nothing crazy should be going on to screw with brightness settings being unresponsive either!
KryptosXLayer2 said:
I'm on stock MDL. It has only been occurring since I upgraded from MDB 3 days ago, and is a huge PITA because brightness controls are unresponsive during this time - I go into settings to adjust brightness since I have removed all the brightness controls from the notification panel as they've always worked just fine, and turn off auto brightness, scale it all the way to max, and it is still dim as crap.... Only fix I've seen is to reboot, which is obviously not ideal in most situations when I need to wake the device! I'm using STOCK kernel, STOCK ODEXED ROM as well, nothing crazy should be going on to screw with brightness settings being unresponsive either!
Click to expand...
Click to collapse
Do you by chance use Light Flow?
I solved the problem. I had "lcd_backlight" control flipped on in the settings of Light Flow. It fixed it. To tell if it's an app problem, just factory reset and try, once you boot up, to lock and wake the device to see if it happens. If it doesn't, it's an app problem more than likely, or even a general setting. Troubleshoot for the win!
Serfma said:
Do you by chance use Light Flow?
I solved the problem. I had "lcd_backlight" control flipped on in the settings of Light Flow. It fixed it. To tell if it's an app problem, just factory reset and try, once you boot up, to lock and wake the device to see if it happens. If it doesn't, it's an app problem more than likely, or even a general setting. Troubleshoot for the win!
Click to expand...
Click to collapse
I do use Light Flow, but I don't have either one of the LCD Backlight controls enabled, never have and never will, so I don't know how that could be affecting my phone at all.... That's a good start for some, but not for me, unfortunately! Good catch though
Sent from my Samsung Galaxy S 4 using the XDA app
Serfma said:
Ever since as long as I can remember, my phones brightness will dim to a brightness so dark you just can't see it. Even if you manually set the brightness, once you lock and wake the screen, it's fine then suddenly switches to dark.
I've used multiple ROMs and they all do it. Is it a device issue, or could it be a kernel issue? I've not screwed with kernels so I don't know if it could be it. If it's a device issue, I'll be getting a replacement ASAP.
Any help is appreciated!
Click to expand...
Click to collapse
I had this issue before on my Galaxy S3. I ended up replacing the front glass because of a dead pixel. Come to find out I had a sensor issue and that was causing my brightness auto going to whatever level it wanted.
Perhaps you're experiencing that too. Haven't heard or read of any sensor issues yet with the S4 but you could be the lucky winner!
Hi, started this thread to see if anyone had the same problem I'm having with my screen.
I have a Galaxy S4 GT-I9500 (Octa-core variation), it is running 4.4.2, rooted, stock Touchwiz.
The problem is that the screen starts to flicker almost as if it would want to turn off, when in low light conditions and auto-brightness on, it continues to flicker unless I set the brightness between +2 and +5. I can reproduce the issue without auto-brightness setting the brightness to the lowest, one notch above the lowest and there is no flickering. It is noticeable in white backgrounds and also when swiping down the notification center, that's the most noticeable instance but you can see it in the home screen and in any app.
I started noticing it when I had 4.2.2 Jelly bean (rooted), and I updated to Kitkat hoping it would be solved but it is the same, I updated through Kies and rooted, no Factory reset, I want to try that as last resort.
Funny thing I discovered is when I set Juice Defender to control my brightness it does not flicker even in -60% brightness, but when the dimming happens before the screen turns off it does flicker (and the dimming thing is controlled by the OS I think, not Juice Defender).
I wish I could put up a video but I don't have another phone to film it.
Anyone know if this is software or hardware? What can I do?
I'd like to add, that I changed the battery, disabled overlays in developers option, forced GPU rendering, tried Pimp my rom and played with all the settings, checked and unchecked every option in Display settings and it still flickered given the low brightness conditions.
I think I've found the best solution out there for most annoying screen flickering issues... Done a substential amount of digging and finally discovered the app "Twillight" works like a charm by enabling backlight control feature... Try it out first, then thank me and share your experience here ...
Running the Alliance rom, clean install on stock slot. No other major issues that I can think of. I've got it set to maximum brightness, not on auto dimmer. When the screen dims after 30 seconds or so, when its about to turn off due to inactivity, half the time when I tap the screen, it recovers to full brightness. The other half the time, it gets a little brighter than the dim mode, but not much. It stays way dimmer than the full brightness setting that I keep it on. I have to pull the notification bar down, slide the dimmer down, and back up to maximum, and I'm good to go until the next time it does it. Which could be in 30 seconds when it dims again.
Anybody else having this issue?
scott_65 said:
Running the Alliance rom, clean install on stock slot. No other major issues that I can think of. I've got it set to maximum brightness, not on auto dimmer. When the screen dims after 30 seconds or so, when its about to turn off due to inactivity, half the time when I tap the screen, it recovers to full brightness. The other half the time, it gets a little brighter than the dim mode, but not much. It stays way dimmer than the full brightness setting that I keep it on. I have to pull the notification bar down, slide the dimmer down, and back up to maximum, and I'm good to go until the next time it does it. Which could be in 30 seconds when it dims again.
Anybody else having this issue?
Click to expand...
Click to collapse
I have the same thing happening. Personally I have been too lazy about it to check through settings to see if I've done something. I'll check on it and see if I can find a fix.
*Update*
I've checked through all my settings and can find nothing that might cause it. I don't have Auto Brightness set, nor do I have Auto Adjust Screen Tone turned on. I saw nothing in the Alliance Settings either. I believe it is a system setting that is probably buried in code somewhere (far beyond my knowledge).
**Update** I reported the bug in the Alliance Forum.
I tend to agree. I've looked through settings, etc. just as you have, to no avail. I'm nearly certain it's done it since install, so I don't think it's something that I've changed. But I could be wrong. I've also tried it with auto adjust turned on, does the same thing. Auto adjusts to a dimmer setting sometimes
So I tossed LP on over the weekend using the FlashFire method so I'm rooted and things seem to be working well. My only real issue is that the auto-brightness seems dimmer to me than at 4.4.4. It works, that is I see the screen brightness automatically change when ambient light levels change, but inside, in a "normally" lit room in a house (no overhead florescent lighting) it is definitely dimmer than before.
Does anyone know of a tweak for this besides just turning off auto-brightness, which I'd prefer not to do?
my only other complaint about LP is the owner info not showing on the lock screen if you have the notifications enabled...