So I recently got CM 10.1.3 stable on my GS3. I set the CRT Animation for the Screen Off to "OFF". But whenever I lock the phone, instead of getting a normal smooth screen off, I get a weird flicker on the phone. Anyone know why or any can suggest me some solutions? Thanks
imcol said:
So I recently got CM 10.1.3 stable on my GS3. I set the CRT Animation for the Screen Off to "OFF". But whenever I lock the phone, instead of getting a normal smooth screen off, I get a weird flicker on the phone. Anyone know why or any can suggest me some solutions? Thanks
Click to expand...
Click to collapse
Mine does the same thing. I just left the CRT on since the flicker was a little annoying. I think that this is just the way it is. Found no bad affects or other issues and I have been running CM 10.1.3 for at least six weeks now.
Related
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
deeren said:
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
the same issue with stock kernels too(unrooted and rooted).
btw, its not called bsod, its called sod(sleep oif death)
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
klobkelosh said:
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
Click to expand...
Click to collapse
Will try that.
Thanks everyone.
I have the same BSOD/SOD issue... will try the 0.5 animation trick and report back. I would hate to go back to 4.1 roms.
I found new love for my SGN with the 4.2.1 smoothness.
Did it help?
I am experiencing SOD / BSOD on my Nexus 4 + latest CM10.1 nightly from time to time... (stock kernel).
In developer settings there are actually three settings regarding animations - are all to be set to .5?
Best regards,
ww
For me it did, yes.
No more BSOD.
I put them all to x.5
I've been diagnosing this for some time and I feel fairly confident that it is only the animation duration setting that triggers the sod. I have the other two settings set to 0 and duration set to 1 and no sod. But, it will not turn off that pesky crt animation.
who in here looked at logcat/dmesg when that happens?
do you have daydream ON? do you use an adblocker?
i've had one on 4.2.1, WITH AN ADBLOCKER installed. no adblocker, no bsod. full stock (rooted, unrooted, tried them both, doesn't matter), default settings (only enabled usb debugging)
just had another SOD / BSOD: I connected the charger and realized after 15 minutes, that the clock was unchanged (still 15 Min prior) - I tried to open an app and got a timeout. After I switch the screen off and on again I just saw a black screen (a little bit lighter than actually off) - but no homescreen anymore... damned.
I can't post in development section yet. Running the release 1.7 and the 6/28 nightly, When I shut off the screen from my home page, the screen will not turn back on for about 15-20 seconds. This does not happen from the lockscreen.
Anyone else experience this or know a soliution?
Thanks
mustangl3 said:
I can't post in development section yet. Running the release 1.7 and the 6/28 nightly, When I shut off the screen from my home page, the screen will not turn back on for about 15-20 seconds. This does not happen from the lockscreen.
Anyone else experience this or know a soliution?
Thanks[/QUOTE}
After playing with the security settings, it seems the setting which delays the phone from locking is causing the problem. When the phone is set to lock immediately, the screen turns on immediately. If i set the lock delay, the screen will not come on for the amount of time it is set to delay.
Click to expand...
Click to collapse
Should this be a problem with your launcher software?
I hv flashed CARBON b4 but never experience this and neither do any other ROMs.
Right now I'm using MIRAGE V2.6, it's just perfect for me!
Hi, sometimes when I try unlock my Xperia M, then I stay on black screen. Phone is in standby and I must pull out battery. This issue I have two times, maybe three times per day.
I dont know, it is CM11 bug? Any fix for this issue?
cm 11 black screen issue
lookynator said:
Hi, sometimes when I try unlock my Xperia M, then I stay on black screen. Phone is in standby and I must pull out battery. This issue I have two times, maybe three times per day.
I dont know, it is CM11 bug? Any fix for this issue?
Click to expand...
Click to collapse
I have been having this problem since I installed cm11. I tried a lot of things and up till now i've gotten the best result with turning off the "agenda on lock screen". I'm now 36hours crash free.
I also installed the latest nightly. But I think the agenda causes the black screen on wake up.
edit: 60 hours
Hope this helps!!!
Hey all!
This is happening to me for 2 months now, I was running official 12.1CM and now official 13CM
I tried to also use some stock based rom but im pretty sure it happened there too.
Whats happening to me is that randomly throughout the day my phone's screen turns black and I cant reboot it by any home button combination, only by getting out the battery.
When this happens the phone just totally freezes and I cant get it to respond or make a sound.
I don't think that the phone dies because sometimes when its freezes I can still see the notification led blinking.
Does anyone know why this might happen? or where can i copy some logs that might help you guys figure it out?
Thanks in advance!
sounds like you have the sleep of death issue? Personally I haven't been on CM roms much on my G3 so I haven't really encountered this issue but on my previous phone I've encountered this a few times on CM.
EDIT: Though it shouldn't happen on stock are you sure it happens on stock as well?
I have this issue as well using the Exodus rom. I never had it while using a stock rom, so I think this is a cyanogenmod issue (Exodus is a CM based rom in 5.1).
I have the exact same issue with my vs985. Seems to happen the most when viewing any sort of video, but I have had it happen at other times as well. Pretty dang annoying, probably 3-4 times a day. Using CM 13.0-20151217-nightly-vs985 but it started when I first flashed CM. Never had the issue on stock rooted rom.