Not sure where to put this, but it's a question, so here will do. I am experiencing quite a bit of lag upon pulling the notification shade down. I am running ViperRom 1.8 and have LeeDroid kernel. But this was happening before as well. Does anyone else use a zagg glass screen protector? It's very thick. Is there a chance this is whats causing it? I turned power saving off and the governor is still on the stock Interactive so it can't be CPU settings. Any help would be great, thank you.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
Hi Everyone,
As the thread title states, I'm currently using an OC kernel (Flippy's 1.9GHz, to be exact) and I'm noticing that I have to press the power button many times in order to get the screen to turn on. Does anyone know why this happens? I asked in the kernel thread and someone replied that this happens with all OC kernels, although no explanation was given.
I also read that this issue may be due to the screen off frequency being set too low. I currently have that set to 768MHz and this should be sufficient given the Desire Zs normal clock of 800MHz.
Does anyone have any insight about this? Thanks in advance
I'm using a pershoot OC kernel and haven't met that problem yet. My cpu is set at a 386mhz minimum. Try Pershoot?
Make sure that in CM settings, screen on/off animation is turned off.
From what I can recall, its a problem with a combination of overvolting the CPU for overclocking, and having the animations turned off that results in not enough voltage to turn on the screen.
CPU stepping is also related, so you can try changing the governor and see if that helps also.
This is a common issue, and has been well covered in the CM7 thread, so just do a search in that thread for suggested settings.
redpoint73 said:
Make sure that in CM settings, screen on/off animation is turned off.
From what I can recall, its a problem with a combination of overvolting the CPU for overclocking, and having the animations turned off that results in not enough voltage to turn on the screen.
CPU stepping is also related, so you can try changing the governor and see if that helps also.
This is a common issue, and has been well covered in the CM7 thread, so just do a search in that thread for suggested settings.
Click to expand...
Click to collapse
Thanks for replying I've disabled the screen on/off animations and the screen wakes up with no issues now.
Hopefully this issue will be fixed soon as I'm missing those animations already!
im having a problem with incoming calls. half the time it works fine, screen pops up...no issues. the other half the phone will ring/vibrate/light will blink but the screen wont pop up.
rooted, currently running CM 7 RC4, but any rom ive loaded does the same thing. any fixes anyone knows of? i also downgraded to CM stable 6.1 and it does the same thing.
is your phone overclocked or underclocked? are you using set cpu and have a screen profile set?
Are you overclocked? If you are, search for "wake issue" to find a solution. Basically, you need to increase the max of your screen off clock speeds until it goes away.
Sent from my HTC Vision
yes overclocked, using setcpu. not using a screen profile set...i will look into that now. also look into the wake issue. thank you.
make sure if you set a screen profile no to set cpu speed to low or you will have the same issue
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/
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%?