I just installed an Atoto A6 Pro. For about a day, the brightness adjustments were working. It is set up to dim with the headlights and moving the brightness adjuster worked great. Today, I noticed that the screen would not dim when I turned on my headlights. The LED lights on the buttons would dim, however the screen would not change. I tried manually adjusting the brightness through sliding the slider back and forth and nothing is happening. I have restarted the system a few times and that did not work. I have installed Headunit Reloaded and I am wondering if this is what is causing this issue, but I deleted the app and restarted and the issue still persists. Anyone have any clue how to fix this?
What did the reseller suggest?
marchnz said:
What did the reseller suggest?
Click to expand...
Click to collapse
I contacted ATOTO support and they haven't responded just yet. I bought it directly from Amazon new. I am wondering if it is a software issue because the brightness adjuster doesn't even work.
Related
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 ...
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Yep got the same here. Thought I had a faulty ambient light sensor but obviously not.
Sent from my SM-G935F using Tapatalk
Just tried it by covering the light sensor to make sure, no problem here (G935F). My only concern related to brightness is that the s7 just has auto brightness, but no adaptive brightness.
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
jackdforme said:
Uncheck the auto box and recheck. Then don't touch the slider. It's usually because in marshmallow the slider moves with the auto bright and most people touch it which makes it hold position.
Click to expand...
Click to collapse
There seems to be a bug somewhere still. I just tried to move the slider while auto brightness is ticked and to cover the light sensor afterwards again and it still worked and to my surprise it even took into account that I lowered the brightness and took also a lower brightness at the covered state and took my initial setting after uncovering, pretty nice, so there is indeed still adaptive brightness. After ticking und unticking auto it went back taking the default steps for brightness as before.
Having the same issue here
Definately not touched the slider.
Also, I have tested the light sensor and it appears to work fine so definately a software issue. Though I imagine we will see some software updates to fix bugs shortly after the official release date.
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
jackdforme said:
So you can adjust the slider with the box checked and get various levels of auto? Does it learn?
Click to expand...
Click to collapse
Yes.
I can't tell for sure, when I change further steps the previous seems to stick, at least to some extend so there is a logic behind it, but I can't tell for sure if it really is based on each step and sets it accordingly or if it's just changes the range it operates in. Anyways I'm a happy camper.
Also, I could reproduce the device not changing the brightness, when I put it to full at darkness it won't move anymore in auto. But as soon as I lower it again it will also change accordingly again, maybe at those with the stuck brightness the min brightness is only raised, but not lowered anymore, but just an assumption and doesn't help anyone atm unfortunately.
Use lux in play store
Sent from my SM-N920W8 using Tapatalk
https://play.google.com/store/apps/details?id=com.velis.auto.brightness
This is the first Galaxy phone I had, that Auto brightness actually works the way I like it.
It seems to be working fine now. It just takes a few seconds for the screen to dim (maybe I was being impatient).
After testing it further it's actually really good auto brightness.
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
AngioNicholai said:
It works, just takes some time to adjust to the lighting. Maybe the default settings are set to a certain time. Maybe with root we can adjust this..
Click to expand...
Click to collapse
It seems to only do it quickly when the device is lay down (as 954wrecker said). Maybe Samsung did that so it doesn't annoy you when using your phone.
this is definitely a bug imo... the auto brightness doesn't change for me either...
CuBz90 said:
When I'm in a light room the screen goes brighter but if I walk into a darker room, the screen doesn't dim unless I lock and then unlock the screen.
Anyone else having similar issues?
Click to expand...
Click to collapse
I also have an auto briteness issue, when I disable AutoBrite and set it manually about half my apps override the setting and enable AutoBriteness in the app's screen usually dimming the screen? SpadesFree one example and I do not see an override in the app.
Confimed that I'm having same issue, auto brightness not adjusting and slider not movingoing. Have to move it manually
Same issue. It needs to be fixed manually by editing services.jar (root needed)
Nothing else will work. None of google play apps will help with that issue. Does not matter what you do, it will always dimming if you don't fix it in framework.jar
Try it out: http://forum.xda-developers.com/s7-edge/development/auto-brightness-bug-try-fix-t3339858
I have an unidentified Head unit (this one http://www.preston-i-c-e.co.uk/vw-006-oem.php) and I've obviously changed something with buttons and now the screen turns itself off after a few seconds.
Brightness is set on auto, and to keep awake. Sat Nav stays lit all time, but any other app turns screen off.
Attached is system details. I'd love to know more about it!
contact the guys you bought it from?
i think there's a setting for screen auto off time, but you have to look for it. my unit(s) don't have this.
try display settings, under brightness, or factory settings somewhere...
zerozoneice said:
contact the guys you bought it from?
i think there's a setting for screen auto off time, but you have to look for it. my unit(s) don't have this.
try display settings, under brightness, or factory settings somewhere...
Click to expand...
Click to collapse
Thanks, I actually flashed iqnavi on it instead, that worked!
Hi,
The issue has appeared only in last few days.
- HU is running fine but always appears to be on the lowest brightness setting. It's usable by night but too dim for sunlight.
- If I try to adjust brightness, the UI shows the slider but it has no effect on the screen brightness.
- I've looked for and disabled any and all "auto brightness" settings which could be interfering.
- The unit can also auto-dim the screen when my headlights are on. I can tell it's getting this signal because the buttons on the unit light up when my headlights are on but it has no effect on screen brightness.
That's about all. Wondering if anyone has any ideas what could be going on? This is my 2nd Android Head Unit in as many years so I'm getting unbelievably frustrated.
Thanks.