Hay
I overclocked my Nexus 5X but the system did not function normal and suddenly all the colors went over saturated.
I went right back and reflashed the kernel (elementalX 1.14) with stock values. The freq of the CPU normalised some hours later.
Now I have this issue that the colors of my phone are still clearly over saturated, the phone itself freezes randomly when I perform a task (open app, notifications, wake from sleep, scroll a website etc.).
The only way to unfreeze the screen is by clicking the power button (put the screen to sleep), and re-click the power button (awake the screen).
Further I see ghosting on the screen. The start button from the bootloader apears and the clock and battery from the statusbar apears when there is a dark screen (f.or example when the phone boots).
Judging from the EX Kernel Manager values I can say that the CPU is working normaly now and the GPU should be fine as well?
Because when I take a screenshot and look at it on my PC with a different screen the colors are absolutely normal!
Could it be that something happend to the screen while it ran overclocked? Have you ever had such a issue and how did you solve it? Is this problem solvable?
I run Tesla v2.0 Alpha OS with the ElementalX 1.14 kernel.
Thanks for your help.
Hey pal, hay is for horses.
Dirty flash your ROM. If you still have issues, clean flash your ROM. If its still a problem, flash the factory images. If you continue to have a over saturated screen you have damaged you hardware.
Hey pal
Thanks for the feedbackk. I reflashed the rom and the kernel. After that flashed the stock images. Nothing helped. The color is oversatured even before boting. The usual warning because of the open bootloader is overdsturated as well. Any idea what else i could try? If it is the display , what can i do?
balpem said:
Hey pal
Thanks for the feedbackk. I reflashed the rom and the kernel. After that flashed the stock images. Nothing helped. The color is oversatured even before boting. The usual warning because of the open bootloader is overdsturated as well. Any idea what else i could try? If it is the display , what can i do?
Click to expand...
Click to collapse
Its a hardware issue then. Most likely because you overclocked. There really isn't much you can do. Maybe replace the screen? That might not be the only thing that is damaged though. Good luck.
Related
Hi,
Sometimes when i click Home button Middle-Bottom of the screen.
physical buttons's Backlight turning on but screen doesn't come up.
I have to try at least 5-6 more times for screen to show up.
What is wrong with my phone ?
It's just sometimes really annoying..
Thank you for reading.
Best Regards.
UP
Using the latest FW ?
From my sexy LT15i
Do you use any custom Rom/kernel?
Sent from my Xperia Arc using XDA
Seems like extreme lag to me. The next time it happens check with a program (like OS monitor) the cpu usage. The situation that you described happened to me once, the MtpApp process was using 100% cpu and i couldn't use my phone properly until i rebooted it.
I faced a similar issue on a Xperia Ray
Its hardware i guess, flashing stock didnt work for me
What i say is you should flash stock FW
Thank you for all those answers !
I'm using DoomKernel 2.32.9 ( I Guess it's 19v )
2.3.7 Modded GB Deluxe Edition ( http://forum.xda-developers.com/showthread.php?t=1533332 )
It was happening more before i started using Modded GB Deluxe Edition.
But it is still happening, and still a lot annoying..
Thank you for reading.
Best Regards.
If your using a program like SetCPU or no-frills cpu control make sure that the minimum clock frequency is not set to 122MHz. Try set it to atleast 245MHz. I tried setting the "screen off" CPU to the minimum on SetCPU before in the hope to get more battery life, but whenever I wanted to wake the phone there would be a 2-3 second lag before the screen showed up. I hope this helps.
I guess this will work.
remove your SD card, connect it to a PC & format it, Insert it back.
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
oojjii said:
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
Click to expand...
Click to collapse
Maybe you can try flashing the stock kernel to test? i tried flashing a non-stock kernel a few times before and results were mixed and never perfect for me (don't really know why). Sometimes it would randomly glitch and the screen would turn black for about 1/2 a second or something. Wifi would sometimes be intermittent despite flashing the modules for some as well.
I'm not experienced enough to fully understand but I'm thinking that it could be a regional thing? I mean, how signals differ between regions?
So.......
Did it work........
I was wondering if any has encountered this.
1) After a reboot and when I'm on my main screen, it would take a while for it to load the launcher. If I attempt to scroll with Nova, it would say its unresponsive, and if i wait, it would work.
I recall on stock ICS, after reboot, i'd unlock screen and pretty much immediately i can use the main screens.
2) Sometimes when I try to unlock the screen it would freeze up. The screen remains blank, but the capacitive buttons light up.
I can reboot to enter the phone.
I can wait it out and it would eventually load and say something is unresponsive, sometimes the launcher. And if i wait, it would work again.
Or I can increase min cpu to 486 instead of 384hz, and i dont see this problem. Can someone explain to me whats happeneing? Why would 384Hz create Sleep of death?
Any insights would be helpful. I would like to get rid of the sod or lock screen freezing thing without having to mess with my cpu settings.
And resolve the lag issue at during reboot. it would take like 10 plus seconds for it to be responsive. I'm not saying 10 seconds is long, but the point is that i never had this issue with stock TW.
I am rooted on paranoid android/CM10 latest build. with SuperchargerV6.
Thanks in advance guys.
bump
anyone?
mikoal said:
bump
anyone?
Click to expand...
Click to collapse
try dirty flashing the rom. that usually clears up issues in cm10-based roms. make a nandroid if you havent already. cheers
I rooted my galaxy s3 when I got it. sometimes the screen turns on and it is unresponsive to touch. As soon as I turn the screen off and back on with the lock button then it works fine. It does it randomly, for instance when somebody calls I can't answer it sometimes I have to hurry up and turn the screen off and back on so I can swipe to answer. Also when I'm playing a game like hill climb racing it works then after a minute it stops responding completely until I lock and unlock the screen. Everything was working fine until I rooted it. That is my only issue. Any suggestions? Thanks
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Spark91 said:
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Click to expand...
Click to collapse
No i am rooted only no rom or custom recovery just went back to stock and updated to 4.1.2 and re rooted and it still does the same thing.
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
bump
CNexus said:
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
Click to expand...
Click to collapse
Ok I turned the developer option on to track touchs and sure enough when the screen touch "freezes" it is still responsive to touch it's just way off. And even though it is way off I can get it right about where I originally am trying to touch, and it still does respond. Also when it freezes, there are two touch spots and they are way off of where I am touching..! Any Ideas???
I am having an issue on 4.1.2 TW; has happened on both TPR and JellyBomb... when phone boots or I wake it up with home or power button, lockscreen is in landscape mode and unresponsive to touch. Have to pull battery and wipe cache/Dalvik. Is this just from multiview?
Using CWM with KT Kernel (it has happened on various KT builds, including 14MAR, 27MAR and 11APR).
Anyone know what's causing this?
EDIT: well, as usual, a quick PM to Kennyglass123 has solved the issue! I forgot to uncheck the "ripple effect" and I'm using AOSP lockscreen. Nothing like feeling like a schmuck to start your weekend!
Mucho thanks to Kenny, as per usual...
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
broky said:
sometimes when i pick up my phone and press the power button to turn it on,i find the screen is black and i can t do anything but press power and vol + to reboot.
then the phone works fine again but of course this is quite annoying to happen and it happens maybe one or two times daily
it started happening when i upgraded to 5.1.1.
in 5.0 and 4.4 phone behaved fine.
how to find what causes screen to turn black when i try to turn it on?
does somebody faced this also?
any helpful idea?
Click to expand...
Click to collapse
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
levone1 said:
Phone stock? Rooted? Recovery? Etc... I've never experienced it, but with modded phones, cache wipe fixes these types of things often
Click to expand...
Click to collapse
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
broky said:
sorry,did not mention.
locked bootloader,stock 5.1.1 rom rooted and recovery,xposed installed.
i need a way to track what causes this situation,maybe an adb command?
Click to expand...
Click to collapse
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
levone1 said:
I don't know much in that realm, but I read this one time - http://forum.xda-developers.com/showthread.php?p=34960691 - looks interesting if you know what you're doing. Anyway, all I really had to offer is attempting a cache wipe, which you probably tried. Besides that, if it happens consistently, you could experiment with disabling Xposed modules one at a time, for a day or so, and see if that reveals it. I have gotten black screen before from installing incompatible modules before, but it would just boot to the black screen. I haven't had it happen only occasionally like that. My guess would definitely be somewhere with Xposed. Maybe something clashing with built-in settings, ( I don't remember what it's called, but there's something that senses when yo pick up the phone, and it wakes up automatically - that kind of thing).
Click to expand...
Click to collapse
thanks mate i m working on it and i ll repopt back if i solve it and how or need more help
SOLVED:after a lot of testing found out that my problem was xposed framework v74-sdk22.
from the moment i installed xposeeed v75-sdk22 everything works as it should,not a single reboot and phone is rebooting faster also and no lag as i used to have before,fingers crossed it won t show up again:good:
Hello everyone, I got LeEco Le Pro 3 two weeks ago. For the past two weeks of testing, I notice that the screen quickly turns red when pressing the power button to turn the screen off. Is any of you facing this problem? It happens randomly, not every time. I have attached the video in slow motion capture in the 7z zip file. So you can see, what I am talking about. Let me know if any of you see it.
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
marik1 said:
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
Click to expand...
Click to collapse
I did not power sleep my phone rapidly. The red screen still persist. I don't know if force kill app cause it. I submit the feedback through the leeco experience center about this issue. This is what I got from them:
"Le Engineer
Hello,
I just get some information for this issue, in low battery level the red screen issue will happen sometimes. We also find the same thing on other brand device.
However R&D team are working on it. Hope it will be fixed in next generation product.
Sorry for inconvenience. Thank you for choosing the LeEco."
So I don't know if my phone is defective or not. It's hard to tell. Base on this message, look like there is no fix for this.
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
crazy1990 said:
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
Click to expand...
Click to collapse
It could be a software issue since I don't have that on CM.
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
losteagle said:
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
Click to expand...
Click to collapse
If you have another phone with slow motion support just like I did, you can try that.
Other thing I want to mention, I would like to know that if the red screen does not happen to people who have CM or MIUI on lepro 3, can any of you go back to EUI and try to do the same steps? If you can. This would more confirm that the software is the issue and not the hardware defect.
Any update?
Hi folks! I've been searching for this rare issue since I got my LM2 last week. I have the very same issue and I notice the same @crazy1990 mentioned here. Besides, I notice this red light is more noticeable when the brightness is higher.
IMO, I don't feel it's a matter of bad hardware (I hope so), as there are no clues of any other issues at all. I'm also using stock (23s) and I suspect it's some poorly designed fade for the ROM.
Any updates from anyone?
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
crazy1990 said:
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
Click to expand...
Click to collapse
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
razmth said:
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
Click to expand...
Click to collapse
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
crazy1990 said:
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
Click to expand...
Click to collapse
Great to know it doesn't happen on Omni/Purity. My biggest concern was an increasing degradation and/or flickering issues arising when changing to a stock ROM.
Thanks for your information.
Sent from my Le X820 using Tapatalk