Turns out this is obviously an issue with my phone, and not the new kernels I have been using. All though it has only happened with Fserve's franco.Kernel.v19.3-gbs.v15 and franco.Kernel |.v19.4| 2.6.32.46. But the problem is the same between both of them, happens less often with v19.4. But rather than bother the kernel developers I will put a general post here. I'm sure that they already have their hands full, and I don't think it's a kernel issue anymore.
The issue:
My lockscreen keeps burning the image into my LCD when I put the screen to sleep. Always is the last image it was at when I shut it off, and it takes around 3-4 hours after flashing a kernel to start with the issue.
It's basically the same type of thing that happens if you leave a computer monitor on at the same screen for day or so, the image stays on the screen for a while because it has burned itself into the monitor.
I cannot take a Logcat as it is disabled in the franco kernel I am currently running. Current specs are in my signature.
Essentially I am trying to track down the cause of this issue, as it seems to happen across different setups, no matter the LCD sleep settings I set, and doesn't go away with lower overclock settings. But when I flash my phone back to OEM specs with KDZ updater it does not produce the problem at all.
It has to be software related because if it was my hardware, It would produce the same result when KDZ updated.
Anyone have this issue at any point? Any suggestions on how to fix it?
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
bigsupersquid said:
I'm not sure how much use it'll be to you, but if it's actually a kernel issue, and not just an android problem, this might be useful:
instead of logcat you can use dmesg.
in a terminal app or adb shell:
Code:
dmesg > /sdcard/dmesg.txt
if the /sdcard path isn't appropriate for your device, replace it with something accurate.
Click to expand...
Click to collapse
No luck, not supported in this kernel. I return the message
Code:
dmesg > /sdcard/dmesg.txt
klogctl: Function not implemented
Just returns an empty dmesg.txt file.
gahhh, i'm sorry. thought that'd work for sure.
maybe adb bugreport?
FOUND IT!!
Turns out the screen off animation in CM7 was the cause of my issues. For whatever reason, with the screen off animation disabled my screen no longer burns any images into the LCD. I have been burn free for 2 days now.
Weird. Oh well
EDIT: **** me it's back again, what the hell? This is truly a noggin scratcher of a problem here...
I have the bugreport:
Download the bugreport(report.txt)
Compiled through Terminal Emulator v1.0.29 and taken 5 min after screen burn was noticed.
Currently running franco.Kernel v19.3 CFS to see if the problem goes away, as I ran this kernel for a week with absolutely no issues.
Update: Logcat is working on v19.3 CFS version so I was able to take a look at what the phone was doing. Turns out the screen state is set to 0 when I turn it off, and it runs all the screen state off commands properly. But, with logcat not working on v19.4 CFS I am not able to compare notes. Going to look through the bugreports I have and see if there are any differences.
Aha! I have found something that might be of some help. In the battery history section of the bugreport, v19.3 does a Kernel wake_lock when turning the screen on and off, while v19.4 is doing just a wake_lock. They may be versions of the same thing, but maybe the difference in the process is what's causing my problems? I ran v19.3 for around 6 hours today and I had no issues with screen burning.
Well, after 8 hours of 19.3 CFS I still am facing the same screen burning problem. Nothing seems to be making the problem go away. My next step is going to KDZ flash my phone back to stock and run it like that for a day. If the problem persists I am taking it in to be serviced because it is definetly a hardware problem.
Update:
Day One of running stock V10V firmware, and no screen burning occurring at all. Going to keep it running like this for the rest of the week to see if anything will pop up. Maybe CM7 went on a fritz? I dunno, I'm no closer to finding the source, but it's looking like software right now.
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Okay, approximately 4 hours into CM7 with francokernel v19.4 BFS, I am experiencing the same LCD Screen burning issue. Nothing is making it go away in any settings. Going to try void forever and see if anything changes.
Download Bugreport HERE(log1.txt)
Shofire91 said:
Been running stock V10V software for more than a week, no symptoms of any type of screen burning. Definitely software related, I am going to begin flashing again tomorrow and see if anything turns up. Will report back if I find the issue again, as for whatever reason this could have just been an anomaly I have found in the custom ROM's and kernels.
On another note, It'll be nice to have this phone running fast again
Click to expand...
Click to collapse
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
dancom96 said:
How does that happen? If the screen is not on, how could an image be burned onto it? Or is it not 'physically' burned on?
Click to expand...
Click to collapse
Not too sure, it's almost like the backlight LED turns off, leaving the lockscreen image there to burn into the LCD. Or maybe just a programming anomoly?
Either way, 2 hours into void forever's rom I am getting the problem once again (argh!!).
It only seems to do this with a custom ROM, the v10v firmware ran without any LCD issues whatsoever. Now why would it do that? I ran V10V rooted and clockworkmod recovery and no LCD issues. Only with a custom ROM.
Download the bugreport here(log2.txt)
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Shofire91 said:
MIUI-Gen71 v0.666 Suicidal Edition
This is apparently the answer to my problems. Since it is based off of CM7.1 6.6.1 it is not producing the LCD issue that I have been having with CM7.1 6.5.7.
Been running this ROM for about a day now. No lockscreen burning issues so far. Cross my fingers and hopefully the issue is gone.
Makes sense since the other roms I've tried were based off of 6.5.7. Could have been a CM7 issue in the first place.
Click to expand...
Click to collapse
i dont know it it is cm7 6.5.7 issue cuz i never experienced ur problem with this rom or rom based on 6.5.7
I'm working on the assumption that my problem is just an anomoly that I have come across. Searches returned nothing, and I was able to run 6.5.7 without a single issue for weeks, across different kernels. It just came out of nowhere, maybe it will still turn up in 6.6.1, but at this point only time will tell.
This thread is essentially a record of my findings over time to help anyone who has had this issue(there are a few, but not many) figure out where to turn on fixing the problem.
Took a bugreport in 6.6.1 MIUI just for anyone to look through and see if any differences turn up. I have yet to find something that points to the cause.
Download the bugreport(log3.txt)
UPDATE:
3 days in and nothing so far, seems to have been a problem in CM7 6.5.7. Haven't had a single bug since.
Im also experiencing the lcd burn issue on cm7 6.5.7 with goldleaf kernel... doesnt happen on other kernels tho. Ive had this issue before with stock froyo when i got my phone. Since goldenleaf or whatever is based on stock kernel then i think it must be the kernels fault...
Wierd, I had the same trouble as soon as I tried fserve's kernel as well. Mind you it was 19.3 gbs v15 where it all began for me. But yet it went away when I flashed the phone back to stock with KDZ updater, but still came back after reflashing CM7 6.5.7 with franco's 19.4 kernel, and any other kernel after that, even the stock CM7 one. Even any ROM I used that is 6.5.7 based caused the problem to come back. CM7 6.6.1 seems to be the only answer for me at this point. Not sure what is causing the problem but it seems to be based from fserve's modded kernels, but yet it only manifests itself on a few number of devices. Is your O1 a P500 or a P500h?
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
ert69 said:
Mine is p500. I flashed v18b2 now. Gonna give it a couple of hours and see if the problem still exsists.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Let me know how it turns out.
Shofire91 said:
Let me know how it turns out.
Click to expand...
Click to collapse
Nope. Still can see my lockscreen. I think it might be the roms fault as some have stated before. Plus, that kernel drained my batt like crazy so I went back to goldenleaf.
Sent from my LG-P500 using xda premium
Were you not having the same trouble with goldleaf as well? It has to be the ROM because I am running the setup in my signature since Sunday. No issues at all. Something about 6.5.7 and fserve's kernel don't seem to mix for certain phones. I wonder what the difference is that causes it? I wish I knew more about Unix and Java so I could figure it out. Any developers out there with a little free time?
Sent from my LG-P500h using XDA App
Wondering if that is what I am experiencing? I'm running mean ROM 4.3 and my phone (I think) is randomly shutting off. When I hit the power to wake the screen nothing, but only once the notification light was flashing and I still couldn't wake the phone.
Pretty annoying to have to do batt pulls all the time.
Anyone get this and know a possible fix.
Also I flashed the stock kernel because I thought the screen off under bolting was causing this, but no.
Sent from my PG86100 using xda premium
gilbydakid said:
Wondering if that is what I am experiencing? I'm running mean ROM 4.3 and my phone (I think) is randomly shutting off. When I hit the power to wake the screen nothing, but only once the notification light was flashing and I still couldn't wake the phone.
Pretty annoying to have to do batt pulls all the time.
Anyone get this and know a possible fix.
Also I flashed the stock kernel because I thought the screen off under bolting was causing this, but no.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
I'm currently running MeanROM ICS, but if I remember right, Mean 4.3 was a little flaky. I recommend you run 4.2 with Dodova 5.4 (I believe it's 5.4) as that was the most stable setup for me on the GB version of Mean.
I Appologize if this has been answered. I am running into a odd problem
Just tried flashing 1.7rc1 on my S3 i9300, Installation went perfect, however upon reboot half way through the boot animation all white turned black, and the phone went very dark. As if it did not have the ability to produce the color white or something along those lines. Even with brightness at max I could barley make anything. out All yellows were replaced with an odd redish color and the only color i could see was blue.
Thankfully I was able to flash back to 1.6.8, which resolved the problem.
Tried re-downloading and reflashing 1.7rc1 with no luck.
Running Omega v28 Rom.
Anyone else experiance a problem like this, and if so find a solution? or am I just lucky!
I honestly have not tried v1.7rc1 but i believe that rc may have a bug, after all.. it's still a release candidate and it is still unstable
Sent from my GT-I9300 using xda premium
NewAussiefromCanada said:
I Appologize if this has been answered. I am running into a odd problem
Just tried flashing 1.7rc1 on my S3 i9300, Installation went perfect, however upon reboot half way through the boot animation all white turned black, and the phone went very dark. As if it did not have the ability to produce the color white or something along those lines. Even with brightness at max I could barley make anything. out All yellows were replaced with an odd redish color and the only color i could see was blue.
Thankfully I was able to flash back to 1.6.8, which resolved the problem.
Tried re-downloading and reflashing 1.7rc1 with no luck.
Running Omega v28 Rom.
Anyone else experiance a problem like this, and if so find a solution? or am I just lucky!
Click to expand...
Click to collapse
Re download files were updated he forgot to correct something it will be fine now
Sent from my GT-I9300 using xda premium
Worked perfectly. Thank you! :victory:
And about baterry life ???? i use omega v28 and my baterry gone 20% in 6 hours on stand by...
Try wiping battery stats and fixing permissions
Sent from my Jelly Omega SIII using XDA App
NewAussiefromCanada said:
I Appologize if this has been answered. I am running into a odd problem
Just tried flashing 1.7rc1 on my S3 i9300, Installation went perfect, however upon reboot half way through the boot animation all white turned black, and the phone went very dark. As if it did not have the ability to produce the color white or something along those lines. Even with brightness at max I could barley make anything. out All yellows were replaced with an odd redish color and the only color i could see was blue.
Thankfully I was able to flash back to 1.6.8, which resolved the problem.
Tried re-downloading and reflashing 1.7rc1 with no luck.
Running Omega v28 Rom.
Anyone else experiance a problem like this, and if so find a solution? or am I just lucky!
Click to expand...
Click to collapse
Don'T FLASH OMEGA V28 it has ALOT of bugs and it's not stable AT ALL,i got force closings on all my apps,lock screen with siyahkernel 1.7rc1 is still crap with bugs.iwould recommend flashing v27.1 and siyah1.7b6 for better stability,trust me i tried!
NewAussiefromCanada said:
Try wiping battery stats and fixing permissions
Sent from my Jelly Omega SIII using XDA App
Click to expand...
Click to collapse
Tanks for this i have the same isue and this slove me the problem.
nhariamine said:
Don'T FLASH OMEGA V28 it has ALOT of bugs and it's not stable AT ALL,i got force closings on all my apps,lock screen with siyahkernel 1.7rc1 is still crap with bugs.iwould recommend flashing v27.1 and siyah1.7b6 for better stability,trust me i tried!
Click to expand...
Click to collapse
given no one else seems to have your issues with both siyah and OmegaI would think it is something you have done. Given they way you dis the devs I have no reason to trust you or anything else you have posted. Clean up your act you aren't being helpful to anyone.
jeffnz said:
given no one else seems to have your issues with both siyah and OmegaI would think it is something you have done. Given they way you dis the devs I have no reason to trust you or anything else you have posted. Clean up your act you aren't being helpful to anyone.
Click to expand...
Click to collapse
100% Agreed! :good:
nhariamine said:
Don'T FLASH OMEGA V28 it has ALOT of bugs and it's not stable AT ALL,i got force closings on all my apps,lock screen with siyahkernel 1.7rc1 is still crap with bugs.iwould recommend flashing v27.1 and siyah1.7b6 for better stability,trust me i tried!
Click to expand...
Click to collapse
I only have a few days worth of rooting exp and I have flashed Omega v28 and haven't encountered any bugs at all. The one or two issues I had were down to my lack of experience.
If you have had genuine issues you would be best served to raise them with the dev to find solutions to the problem, not slate all their hard work with no substance to what you are saying!
Sent from my GT-I9300 using xda app-developers app
I am working with the cm7, but hav e a really strange issue I cannot figure out a way to correct. When I make a call the screen goes blank and will not allow you to turn it back on. You have to take the battery out and put it back in. For some odd reason if you have the bluetooth hooked up it will blank the screen but it does not lock you completely out of the phone.
Anyone else experienced this and know a workaround?
Its's been a while since i have used CM7 but i think i remember this problem. i could be wrong but i think it had something to do with deep sleep and there was a flash-able zip that fixed it. like i i said it has been a while since i've used cm7 (over 7 months now).
What cm7 rom are you using? i think Mrom had this bug fixed. Mrom was the last cm7 rom i used and to me (and this is only my opinion) it was the most stable for me
Xiaomi Note 3 Pro 2/16GB
Hi,
i am currently on a nightly cm13 build. before i had the same issue on the snapshot build.
Used also different kernels but with the same results.
Issue is shown in the video below.
https://www.youtube.com/watch?v=HI43XX0WIpY
This happens probably once a day and only when i am waking up the phone from deepsleep with the fingerprint sensor.
The screen keeps being black for a second when this happens. When i turn off the screen and wake it up again, everything is fine.
What do you think, hardware or software issue?
EDIT: Just found out, that it could be potentially a LiveScreen issue on cm13
EDIT2: No, LiveScreen is not the problem
I'm also facing this issue. Are you using any custom kernel?
I'm using the Blaze kernel.
Yes, was using Blaze kernel as well but i tried different others as well.
I am now on Exodus ROM without these issues.
Seems to be a cm bug.
I've had the issue also while charging my phone last night.
CM13 with Redon kernel.
Scared the sh*t out of me...
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
MiripRedmoon said:
I have a screen flickering bug too, i revert to MIUI then. But, flickering still.
Repairing to the counter now.
Click to expand...
Click to collapse
i know its long time ago, but could you repair the device?
screen glitches
same problem, flickering and mistyping too. Please anyone resolve, this has happened after the latest update
I had this issue, rom and kernel reinstall solved the problem. Maybe something is cached/crashed or both (the phone acted weird other ways too, random apps crashed and so on), before reinstall wipe cache, dalvik, data and system, then install the latest versions of the rom and kernel you want to use. Don't forget to flash firmware.
Since I did this everything is fine.