While using deck's (newest) rom the brightness is stuck at 100% and theres nothing I can do to change it. So thats the original problem.
To fix it I tired different kernels (tiamat, netarchy 4.3.4..., HTC's stock kernel) and I've tried my nandroids of older deck and sense roms.
When I go back to sense roms it boots at 100% brightness and then after the first time you turn the screen off it returns to the lowest possible brightness setting which is even more infuriating. This makes me think the problem isn't probably hardware and the searching i've done has pulled up "gingersense" brightness issues, but none of those fixes seem to fix it for me (namely HTC's stock kernel and netarchy)
Anyone have any ideas?
Also the light sensor works fine, so that's definitely not an issue.
Well if it's on "auto brightness" and it's just going from one extreme to another and you've tried different roms/kernels then it sounds like it is a hardware issue.
I wish it were that simple, all settings (auto and manual) on cm7/deck roms keeps backlight maxed with the kernels theyre provided with.
Only when I use sense rom's does the backlight decide to stay maxed for when it is first turned on, but the second it's put to sleep then woken back up it drops to the lowest backlight setting. (and thats what makes me think it's not just a hardware failure)
There is NO control over brightness at all, even on manual (stuck on high currently with deck's rom), I've gone back to deck since it will at least be usable now, but there has got to be something I'm missing.
Edit: Just to be clear, when I say lowest setting, the backlight is on, but dim, not completely off.
Related
Hey guys,
I feel like this was addressed way back when but now I can't find the thread to confirm. My screen, when at full brigtness, particularly on all/mostly white screens flickers like nuts. Solution is to turn down the brightness. I'm running eb13 (EXT4) with the latest genocide kernel. I BELIEVE it's been an issue with every "unofficial" kernel I've tried.
Is anyone else able to confirm this (I have searched, or at least tried to sift through the 40 pages of threads)? And if so, has anyone found a solution?
NOTE: This only occurs when "power saving" checkbox under display settings is UNCHECKED (I like the crazy high brightness)
I've never noticed this, but to be honest I have never run my screen at full brightness, it would make my eyes bleed.
ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/
I have an Xperia Play currently on the stock ROM, fully updated.
I noticed that sometimes when playing some games, the screen seems to flicker as if it is changing the brightness settings very rapidly.
I did a Google and could only find a few other people having the same issue.
Is this just a normal thing with auto brightness? Sucks that you can't turn it off...
Cheers
I think it's normal (or a universal bug?) because mine would do the same on stock... since changing from stock it no longer did that.
Well if you're truly fully updated (Firmware version 4.0.2.A.0.42) then you can find the setting for auto-brightness right above the slider that adjusts the brightness, which is under settings>display>brightness
I flashed the fully updating ROM and it seems to be OK now. Haven't noticed it at all since... Would be nice to know if anyone else did actually notice it though.
Is auto brightness primarily controlled by the from itself or the me kernel? I ask this because I've flashed a few roms and the I'm currently settled on the codename android rc-2.0.
Love it but the auto brightness stinks. It seems to pop bright and pop dim at the most random of times. Maybe stock did this as well but since it gradually fades bright or dim its not very noticeable.
Currently on a Franco kernel variant milestone 3.08 that came with the rom. I even played with the auto brightness settings and values in the interface settings. But still get random changes in brightness that are annoying. Popping bright and popping low.
My question is how can I fix this? Any patches I'm overlooking? I've done a day of research and found hints of fixes but no links to them. Any one recommend a better kernel? Maybe just switch roms? Or just use the static brightness settings?
Sent from my Galaxy Nexus
For some reason starting yesterday, my phone brightness automatically goes to minimal brightness everytime i lock it. The brightness slider is on MAX (and it stays on max even when the brightness dies). Auto Brightness is OFF. Power Saving is Off.
Presus Kernel
Omega V16 rom.
nothing modified in the phone in a long time. After the issue happened, i updated the kernal, and still nothing.
The only thing that happened differently over the last few days was i used my phone too much to the point the battery would die. (and in general the screen turns to minimal brightness past 5%, but somehow this got STUCK. even when the phone is charging
Noodile said:
For some reason starting yesterday, my phone brightness automatically goes to minimal brightness everytime i lock it. The brightness slider is on MAX (and it stays on max even when the brightness dies). Auto Brightness is OFF. Power Saving is Off.
Presus Kernel
Omega V16 rom.
nothing modified in the phone in a long time. After the issue happened, i updated the kernal, and still nothing.
The only thing that happened differently over the last few days was i used my phone too much to the point the battery would die. (and in general the screen turns to minimal brightness past 5%, but somehow this got STUCK. even when the phone is charging
Click to expand...
Click to collapse
See if this helps :http://forum.xda-developers.com/showthread.php?t=1970870
Still doesn't solve the issue.
Wiped the device, new rom (Wanam), New Kernel (adam's).
Still the same issue.
Here's what happens:
Full Brightness, Lock screen,..... Unlock, Minimal Brightness
OR
Full Brightness, Lock screen,..... Unlock, (.5 second of full brightness), Minimal Brightness
Just to be clear, the problem isn't that the stock brightness isn't bright enough. The problem is that the brightness setting gets turned down to zero for no reason, (while the settings and slider) are still on max
Do you have any apps that might be doing it? That's the only thing I can think of, maybe you've set up a Tasker profile up wrong and is causing it or something.
Sent from my GT-N7100 using xda premium
D3_ said:
Do you have any apps that might be doing it? That's the only thing I can think of, maybe you've set up a Tasker profile up wrong and is causing it or something.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
well tried Wanam with Adams kernel
then
tried wana with Stock kernel . Wiping before every install.
Both didnt work.
So i wiped every thing. /Data, /SdCard, /Cachem etc. literally everything. Then installed wanam with adams kernel. And somehow that fixed the issue