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.
Related
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/
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.
Hello guys, I just updated my note to the latest DMA6 stock rom as I saw a lot of good reviews regarding battery life.
However, I was just stdading at my desk and as soon as the phone booted up after the flash, I noticed some massive tearing which annoys me as hell. For those who don't know what it is, it feels like the screen refresh rate has been drastically decreased. In order to detect it on most note 2 you can follow these steps (well most of them are working this way, because I have tested this with some other notes):
-- just lower your brightness bellow 30% go into a dark room and keep looking at a fixed point while moving the phone up and down in front of your face, this while having a bright image on it. If you see a flickering image you're a victim too:S
Another way to notice this is looking at your screen trough another (phone) camera...you will notice the old CRT effect of some horizontal lines scrolling up
I had this on my 4.1.1 as well but only till the brightness was at 40%. On 4.1.2 it goes all the way till 80%.
Being pissed to the max, I flashed my 4.1.1 backup and guess what?! Tearing gone at 40%, thus it seems to be an issue with the latest kernel.
For those wondering...yes I have disabled the screen power saving option in the power saving menu.
Has anyone noticed this? Does anyone knows how to fix it?
Cheers
If you mean to say lag then. Factory reset.
Sent from my GT-N7100 using xda app-developers app
I never recall mentioning lag whereas you probably refer as to graphic rendering delay. The phone's interface is acting as it should be, it is as smooth as expected, no issues there.
Perhaps this video will describe better what I mean http://www.youtube.com/watch?v=vL_6H-0GD3Q You can see the screen flickering very clear. This is why I mentioned that you can test this in a dark room by moving the phone reproducing the old crt effect
My question is why does the flickering/tearing dissapear on some roms at 40% and on other above 80%?
I'm generally loving 4.2.2, but there's one issue I've noticed since updating. When I close my smart cover, the screen will usually turn off like it's supposed to do. But every once in a while, it will immediately turn back on at maximum brightness, then turn off properly after a few seconds.
My first thought was it was an app trying to update. But the fact it jumps to maximum brightness makes me think it might be system related. Anyone else having this problem and/or have a solution? Could some variation of this issue be contributing to the power drain some are seeing?
Searched the forum and did some google searches but only came up with one thread somewhere else that never went anywhere. This may be glitchy apps (although I have both on my Droid Maxx as well with no issues) but I thought I'd ask anyway.
So the problem is the tablet(SM-T700, Android 5.02) will seemingly go to sleep while actively using an app (so far it's common in 8 Ball Pool and has also happened during Beach Buggy). I don't know if it's app related or a setting somewhere. I have power saving modes turned off (as well as auto screen brightness). Anyone else experience this?
Well it may be a combination of the app not telling the screen to stay on (twitch app had this issue for about 3 days then it got an update) any you having the auto screen off timer set too short.
The permission used is under others and is called quite simply (prevent tablet sleeping). With out that mode set if you do not touch the screen in (insert screen shutoff timer length here) the tablet will turn the screen off to save power.
Thanks, I'll check that out. I'm going to run a few more apps and see if it happens with them also.