Related
Has anyone else seen this on their screens or know how to fix this or why its happening?
Using Myns Rom, with Battery Tweak, etc etc
What?????????????????????
Actually no pic, the screen shot didnt get the vertical lines..
If the software isn't catching lines, then it's your screen.
Some hardware has lower tolerances with battery tweaks, voltages, etc. Try putting a stock kernel back on it and see if that fixes it.
Sent from my PC36100 using XDA App
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
I have had this issue as well with various Roms lately. After turning the screen off and on it would go away. I've also had other issues such as the phone starting up in car dock mode after a reset, screen auto rotatating even though it's disabled and my media volume not going down after being turned all the way up. I have wiped data, cache, dalvik various times and even ran the latest RUU to start all over but the issues still continue. Anybody else having similar issues ?
nerdmanpap said:
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
Click to expand...
Click to collapse
Same here. Lock the screen, wait a bit, unlock and it stops. Annoying but no big deal really.
Yeah Same thing with me, I turned off the screen and it went away, so weird but it fixed it for now
I forgot, after I saw that , I went into recovery and erased cache, dalvich, etc then I flashed Baked Snackk 1.8 on and still had the issue until I turned screen off then back on... weird
Seems like a lot of us are having the same issue wondering if anyone remmembers when they first saw this happen so we might narrow down the cause to this issue. Mine started after i flashed xxbabiboi228xx rom with kings kernal 11. At first i though it was due to the transition animations, but now i see it no matter what i flash. Not blaming xxbabiboi228xx rom, hes rom is bad ass. Am just pointing out when i first saw this happen.
Sent from my PC36100 using Tapatalk
nerdmanpap said:
i had this issue at first when i was running myns twopointtwo.
i'd boot up and have vertical lines everywhere. If i hit the power button to lock the screen, wait a sec, then hit it again to unlock it the screen would be fine. problem would not reappear at all. its like a momentary glitch i guess.
hope this helps
Click to expand...
Click to collapse
Had the same issue.
its the screen technology.
I JUST exchanged my evo for another brand new one (still within 30 days)
because i had lines going down my screen (Novatech screen).
They were faint yellow lines evenly spread. Got my New evo today and got a different screen (Epson). This screen also has vertical lines.
At the sprint store the 2 evo's on display had the lines however one of them was almost not visible unless u tried to look for it. The other Evo on display looked like mine.
So unless you guys know somethign i dont, i believe this is hardware related.
Theres other forums confirming this.
Both my evo's had hardware 003 but first one was a novatech and this one is a epson.
Novatech screen does look better.
Has anyone found what the issue with this is? I get vertical lines no matter what ROM I flash. I does not happen with the stock RRU ROM though. Got a replacement phone with an EPSON HW 003. Help!
I had the same problem and I found out its the kernal if you have hardware 003 like I do I just use the stock kernal from fresh
Sent from my PC36100 using XDA App
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
mizzos4 said:
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
Click to expand...
Click to collapse
Not sure. I had an 003 before also with an Epson screen which worked flawlessly with any ROM or Kernel I flashed on it. But I guess every phone is different.
Gotta learn to live with it..
mizzos4 said:
Weird, I have an 003 nova on Fresh 3.4.0.1 and tested the various kernel offerings on here, but been lucky enough not to see this. Is this kinda like the whole screen tearing issue with certain kernels?
Click to expand...
Click to collapse
I'm fairly certain the tearing and screen lines/corruption are related.
When I first got my phone a month or so ago, I tried a few different ROMs and kernels. All of the kingx and netarchy kernels I tried exhibited screen tearing, and would more than occasionally exhibit the screen lines/corruption you mentioned . . . sometimes even starting at the boot animation screen.
I was worried I got a bum phone (it was only the second day I had it, so I was a bit noobish) but I flashed the stock kernel (HTC #11) and never had the problem again.
Since then, I've tried a couple newer versions of those custom kernels, and wind up reverting back to an HTC kernel (also tried 10 and what's the latest one? 17?) due to the screen tearing. They just don't like my particular hardware I guess (003 with the Epson panel).
I am also having this same issue, but I am using a stock rom and a flashed kernel.
I had the momentary thing once, don't remember the circumstances, but screen lock / unlock fixed and it hasn't returned. Flashed cm6.1rc1 and after about 20 min. I got real bad, very uneven vert lines plus a flicker that persisted even after reboot. I nanded back to Azrael 2.5 and started using LPP instead of Sense - not CM, but better than the screen from hell! No screen trubs since.
Sent from my PC36100 using XDA App
I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.
Not sure..leds generally flicker before the burn out. They are also rated to handle long cycles....so five minutes should be easy. Bt the circuitry could be burned out. Sounds like this might be a warranty issue.
I did it all from my Nookie...
This same thing just happened to me last night. What happened in your situation?
You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.
stratax said:
You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.
Click to expand...
Click to collapse
Wait hold on just one min... so the flashlight app is not safe to use? i think that not right... you're telling me i can't record a Five min video with the LED light on?
level 3 brightness(flashlight app) is what the Recording Cam use
Zephyr757 said:
This same thing just happened to me last night. What happened in your situation?
Click to expand...
Click to collapse
Nothing, I just called it in for warranty. Will be receiving it in just a few days!!!
stratax said:
You arent supposed to leave the app on for over a minute or so. it can burn it out, and/or mess up your whole phone. it can overheat your phone. i would see if there are any other problems with it, and get it returned.
Click to expand...
Click to collapse
Hmmmm.. I don't think this is right. With my myTouch slide, I have successfully had it on for slightly over 15 mins with no damage what so ever. Maybe this one was defective. Otherwise, even on stock rom, the flashlight app wouldn't be there. But I don't know. Maybe like I said, it was defective. Thanks anyways.
Just came from the Zinx CM7 thread where he is warning the torch mode can burn out your LEDs.
dragon4000 said:
I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.
Click to expand...
Click to collapse
i am also facing the same problem. When i try to take a picture, the flash light only works for the first 2 or 3 pictures for the rest it wont flash until i leave it to lie for some time before it comes back and when i try using the torch it turns on bright then as some seconds go by it begins to dim and when i try to use brightlight feature it just flashes and goes offf
Can anyone help me out????
mickeyasamoah said:
i am also facing the same problem. When i try to take a picture, the flash light only works for the first 2 or 3 pictures for the rest it wont flash until i leave it to lie for some time before it comes back and when i try using the torch it turns on bright then as some seconds go by it begins to dim and when i try to use brightlight feature it just flashes and goes offf
Can anyone help me out????
Click to expand...
Click to collapse
Yes your flash is slowing and painfully dying out.
Sent from my HTC One S using Tapatalk 2
dragon4000 said:
I've looked around to see if there was a post about this and didn't see it. This is my problem, I was using my phone yesterday as a flashlight for like about 5 minutes when my light just started to dim little by little until it turned off. So, did I just burned my led flash? If so, is there a way to fix or do I just call it in to insurance? Thanks.
Click to expand...
Click to collapse
I had this problem on my Google Nexus 5X (on stock rom) and I changed it, to bunch of different ROMs and the flash worked on everyone, currently I've got it on some *android 12 AOSP without gapps something like that, maybe you could try to (unlock the bootloader) and then (flash TWRP *custom recovery*) and then go into TWRP and wipe your operating system then flash your choosen custom ROM then see if it works. Also I see that you have gotten one from warranty, that's great! I hope this helps other people, and you also get some new features with those custom ROMs! Or just update your outdated device upto 4 or more version ahead of when it got discontinued, * I'm sending from my LG G8 currently, that I got to try to mod, but cant figure out how to unlock the bootloader, but that's fine its my main device rn, I have a Google pixel 6 pro for that and the Google Nexus 5X )))
Hello, as I said in the thread title i have a problem with the screen lock after waking up the phone. It remains stuck, until i push the power button again to close the screen, and then it's working like it should. The problem appears one at 6 or 7 times i wake the phone.
I have tried to change the screen lock method, but i get the same problem, with the pattern activated.
I have also changed two roms, so I guess this is not the issue. It is more likely that an app is the cause of this, but i have the same apps as I had on my Galaxy Nexus, so it is difficult to figure out what is the app causing this. I have paranoid android with franco kernel.
Does anyone have a clue about what the problem could be?
neinfricatu said:
Hello, as I said in the thread title i have a problem with the screen lock after waking up the phone. It remains stuck, until i push the power button again to close the screen, and then it's working like it should. The problem appears one at 6 or 7 times i wake the phone.
I have tried to change the screen lock method, but i get the same problem, with the pattern activated.
I have also changed two roms, so I guess this is not the issue. It is more likely that an app is the cause of this, but i have the same apps as I had on my Galaxy Nexus, so it is difficult to figure out what is the app causing this. I have paranoid android with franco kernel.
Does anyone have a clue about what the problem could be?
Click to expand...
Click to collapse
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
-JFK- said:
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
Click to expand...
Click to collapse
Hi, you have understand well, that is the problem i am facing. It becomes unresponsive quite often.
No, i did not change anything regarding the cpu, nor the settings in franco kernel.
neinfricatu said:
Hi, you have understand well, that is the problem i am facing. It becomes unresponsive quite often.
No, i did not change anything regarding the cpu, nor the settings in franco kernel.
Click to expand...
Click to collapse
That's strange, I have the same settings as you (PA + Franco) without any problems.
I know that Franco's Kernels are great but this is the way that I should follow to try to found the problem.
Do a full wipe and re-install PA + PA Gapp.
Don't install Franco Kernel right now and do the test with PA stock kernel.
If the test is OK, the problem come from Franco's kernel -> ask in Franco's thread
If the problem is still there -> ask in PA thread
You haven't any other problem with your touch screen ? Only with the lock screen ?
-JFK- said:
Hi,
Please tell me if I have well understand :
When your phone is in standby mode (screen off) and you push power button, the screen lock appear but you can't unlock it ?
That mean the screen doesn't respond some time (1 to 6-7) after wake-up the phone ?
I don't know why but I want to ask you if you have under-volted your phone ?
Click to expand...
Click to collapse
-JFK- said:
That's strange, I have the same settings as you (PA + Franco) without any problems.
I know that Franco's Kernels are great but this is the way that I should follow to try to found the problem.
Do a full wipe and re-install PA + PA Gapp.
Don't install Franco Kernel right now and do the test with PA stock kernel.
If the test is OK, the problem come from Franco's kernel -> ask in Franco's thread
If the problem is still there -> ask in PA thread
You haven't any other problem with your touch screen ? Only with the lock screen ?
Click to expand...
Click to collapse
Thank you, i will try the stock kernel, as I only tried franco's.
Nop, no other problem with the screen, only this one with the lock screen, and it is becoming annoying
neinfricatu said:
Thank you, i will try the stock kernel, as I only tried franco's.
Nop, no other problem with the screen, only this one with the lock screen, and it is becoming annoying
Click to expand...
Click to collapse
OK, let's go for a full wipe, I'm sure it will solve the problem.
-JFK- said:
OK, let's go for a full wipe, I'm sure it will solve the problem.
Click to expand...
Click to collapse
Hmmm, that is highly unlikely, as PA is the second rom i have tried, with rasbelly i had the same problem.
I am now trying the stock kernel.
neinfricatu said:
Hmmm, that is highly unlikely, as PA is the second rom i have tried, with rasbelly i had the same problem.
I am now trying the stock kernel.
Click to expand...
Click to collapse
Any news after the FULL wipe ?
-JFK- said:
Any news after the FULL wipe ?
Click to expand...
Click to collapse
I have flashed the stock kernel, for a while it seemed to work better, but 5 minutes ago the screen lock remained stuck again.
I have made a full wipe for the instalation of PA coming from rasbelly, one week ago, still the same problem. As I said, i am almost sure that the problem is caused by an app, but it is quite difficult to see which app is causing this....
screen unlock
Hey I had a similar problem. Do you have Lightflow installed? When I had stock everything, enabling additional LEDs including the LCD backlight had no issues. But apparently with PA and Franco kernel it switches off backlight when you unlock screen. Light flow switches it off. Try disabling that control of LCD backlight maybe? That worked for me
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.
Flash a custom kernel. You'll be less likely to experience lag
Don't get any lockscreen lag on my stock Android.
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?
nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.
I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?
Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.
for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.
if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag
I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.
I have a rooted LG V20 and having a serious issue with it. As anyone who owns this phone (assuming there aren't any other variants of it) has the little display on the top right of the phone. Well after a few minutes of use, whether it's gaming, watching videos, or browsing the web, the upper screen begins to act strange. It gives this weird graphic that looks like a TV screen's static when it has no signal. First it begins to flash a few times eventually flashing faster, and faster. After a couple of minutes it stays rite there. Where the problem comes in is when ever it shows up, what ever on the screen freezes. The whole phone doesn't freeze, just the display. Sound continues to come out if the phone during that. If necessary I could provide a shirt video of what's happening, if what I just said doesn't make sense. If anyone know how to fix this, please let me know.
What model v20? What kernel are you running? What ROM are you running?
-- Brian
runningnak3d said:
What model v20? What kernel are you running? What ROM are you running?
-- Brian
Click to expand...
Click to collapse
I have the LG-LS997 with the Desolation ROM and werewolf kernel.
Use the kernel that came with Desolation and it should shut the second screen off. The only way you are guaranteed to not have static on the second screen is to run the kernel that came with the ROM, or compile your own.
AOSP and the second screen don't mix....
-- Brian
runningnak3d said:
Use the kernel that came with Desolation and it should shut the second screen off. The only way you are guaranteed to not have static on the second screen is to run the kernel that came with the ROM, or compile your own.
AOSP and the second screen don't mix....
-- Brian
Click to expand...
Click to collapse
Okay, thanks for helping.