I've had my Nexus 4 16GB for almost a month with no problems.
I plugged in my phone and went to shower for 10 minutes.
When I came back, I turned on the screen, and now I have a constant dim flickering over my entire display!
I've restarted twice and the problem persists.
How can I determine if this is a software or hardware issue?
If it is a hardware issue, do I have to remove the root (done about a week or 2 ago) before I send it to Google for a replacement?
Likely software. Some other phones I've had have also had screen flicker. If you do RMA it and it turns on and boots you should probably unroot and relock the boot loader.
Sent from my Nexus 4 using Tapatalk 2
Aoude. said:
I've had my Nexus 4 16GB for almost a month with no problems.
I plugged in my phone and went to shower for 10 minutes.
When I came back, I turned on the screen, and now I have a constant dim flickering over my entire display!
I've restarted twice and the problem persists.
How can I determine if this is a software or hardware issue?
If it is a hardware issue, do I have to remove the root (done about a week or 2 ago) before I send it to Google for a replacement?
Click to expand...
Click to collapse
Try flashing another ROM and see what happens. (Make a android backup first). To send it back to Google you're going to need to revert back to stock.
Sent from my Nexus 4 using xda app-developers app
Update for anyone who might get this problem randomly. I turned the phone of for a little while and then turned it back on and it was fine. I've since switched from stock to CM10.1, and it's still fine.
Sent from my Nexus 4 using xda app-developers app
Aoude. said:
Update for anyone who might get this problem randomly. I turned the phone of for a little while and then turned it back on and it was fine. I've since switched from stock to CM10.1, and it's still fine.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Strange, I've got the exact same issue right now... flickering is present in recovery/boot so I thought it maybe hardware failure.. will try CM10 instead of MCR once I've backed up! For reference:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you have something like this too? Did you wipe when to fix the issue?
r5ingh said:
Strange, I've got the exact same issue right now... flickering is present in recovery/boot so I thought it maybe hardware failure.. will try CM10 instead of MCR once I've backed up! For reference:
Did you have something like this too? Did you wipe when to fix the issue?
Click to expand...
Click to collapse
That's not exactly what mine looked like, the flicker was more of a flashing of the entire screen. That very well could be a hardware issue, but don't take my word for it. I never flashed a ROM or wiped anything to fix the problem. I simply turned the phone off a few times for around 10 or 15 minutes each time, and I just didn't see any more flickering. Hope yours can be fixed this way too
Doesn't look like it, I left it off for about 6 hours, still pretty stuffed. This is definitely hardware... looks like my night just went from bad to worse. :/
Oh that sucks
Hopefully you can get a replacement quickly.
Good luck
Sent from my Nexus 4 using xda app-developers app
Related
EDIT: This failed, just ignore...
If you're like me, you sometimes pickup your phone and it's stuck at the boot animation and the animation is grayish.
Well I think that this problem as nothing to do with custom rom or custom kernel but in fact is a Nexus S hardware issue. I think that when the NS reach a certain temperature the CPU stop intentionally so no damage is done to the phone. The problem is that when the CPU stop, the phone reboot but at boot uses a lot of CPU than overheats again than just get stuck in a reboot loop. That's my theory.
I also think that the problem comes from the NFC antenna. The rubbery texture of the NFC antenna seems to keep the heat in the handset.
So to try to fix the problem, I added a copper plate between the NFC antenna and the battery to try to dissipate the heat. The result, my NS runs a good 4C less than it use too and I haven't had a reboot loop yet.
If you have reboot loop problems, try a similar solution and let me know if it fix it for you...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloops commonly happen from too much undervolting, unstable overclock, phone/battery gets too hot. Looks interesting though. NFC still work?
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Bootloops commonly happen from too much undervolting, unstable overclock, phone/battery gets too hot. Looks interesting though. NFC still work?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm taking off undervolt and overclock out of the equation because I assume that someone has tested those thoroughly before setting them at boot.
I'm focusing on the fact that when your OC/UV is stable, you shouldn't have boot loops. I even think that some ppl are experiencing bootloops with stock kernel which has no OC/UV ...
As for NFC, it still works! I've been running my phone 4 days strait without any reboot and the phone definitely feel cooler to the touch. Temperature never went higher than 35 Celcius. My phone used to be constantly at 37+ Celcius.
Interesting information thanks for the insight.
Sent from my Nexus S
p00kienrayray said:
Interesting information thanks for the insight.
Sent from my Nexus S
Click to expand...
Click to collapse
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
steve.garon said:
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
Click to expand...
Click to collapse
i dont think its a heat issue because ive got my ns up to 123F without a problem, without a bootloop. and i regularly run at 105-115F torturing my phone testing out kernels.
steve.garon said:
Well.. After 4 days without reboot. Left my phone in the car came back after work. Battery was drained because of a reboot loop. So we can call that a false alarm. Copper does not fix the issue. I really thought it was
I guess this issue is software related. Anyone know a ROM that doesn't rebootloop? Cyanogenmod is kind of pissing me off right now because of this...
Click to expand...
Click to collapse
Try the oxygen rom. I haven't encounterd a boot loop or random reboot since switching to oxygen. Use to get bootloop or random reboot several times a day with cyanogen rom.
Sent from my Nexus S using XDA App
No bootloops with cm7 latest nightly and netarchy
Sent from my Nexus S 4G using xda premium
Hi all
Hope someone can help with this problem.
Tonight my phone just randomly turned off. I wasn't doing anything strange..just texting. I sent a text and placed my phone down. Looked at it and hour and half later and it wasn't responding. I held down power and it powered on but noticed my battery dropped quite a bit.
I'm bone stock 4.2.2, no root and locked boot loader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
Mysteries like this one are not uncommon.
Text message couldn't be sent, phone kept re-trying, got hot, turned off?
Signal loss, connection derp, overheating, turned off?
Who knows. I'd lean towards overheating..
If it's only happened once, what's the issue? It could have restarted for a multitude of different reasons but if it's not doing it on a regular basis then it's not really an issue in my eyes.
Mine did this for the first time today after 2 and 1/2 months of flawless performance too. Really weird, wouldn't respond to any buttons,charger, or USB cable. No red flashing LED. Battery was at about 50%. Wasn't doing anything with it beforehand, it was asleep.
After about 15 minutes of nothing, it recognized the charger and booted back up.
Jim Beam5 said:
If it's only happened once, what's the issue? It could have restarted for a multitude of different reasons but if it's not doing it on a regular basis then it's not really an issue in my eyes.
Click to expand...
Click to collapse
I'm more concerned about the battery. Why the sudden drop off from 90% to 70%
Sent from my Nexus 4 using Tapatalk 2
SeraldoBabalu said:
Hi all
Hope someone can help with this problem.
Tonight my phone just randomly turned off. I wasn't doing anything strange..just texting. I sent a text and placed my phone down. Looked at it and hour and half later and it wasn't responding. I held down power and it powered on but noticed my battery dropped quite a bit.
I'm bone stock 4.2.2, no root and locked boot loader.
View attachment 1769700
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I think the 4.2.2 OTA may have corrupted the battery stats file for some users.
I had a similar thing happen where it went from 30% then dropped to 2% after a simple reboot.
Based on my usage at that time, I should have had a lot less than 30%.
Now if your phone gets unusually HOT, you have bigger issues and may end up with the RED light of death
See this post for more info:
http://forum.xda-developers.com/showthread.php?t=2166250
SpookyTunes said:
I think the 4.2.2 OTA may have corrupted the battery stats file for some users.
I had a similar thing happen where it went from 30% then dropped to 2% after a simple reboot.
Based on my usage at that time, I should have had a lot less than 30%.
Now if your phone gets unusually HOT, you have bigger issues and may end up with the RED light of death
See this post for more info:
http://forum.xda-developers.com/showthread.php?t=2166250
Click to expand...
Click to collapse
phone gets warm but not hot. usually when i'm watching a video it'll get warm.
My issue was different, no heat or battery issues. Was at about 50% when it blanked out and 48% by the time it came back.
If phone becomes hot, theres a defense mechanism in which our kernel will make phone run at lower clocks which eventually gets our phone into sleep of death. So try one thing. If ever ur phone gets hot, dnt lock the screen and keep it on a cold surface, and once it get cold, press the lock button. See the diff!!
Sent from my Nexus 4 using xda app-developers app
thx everyone. i'll wait it out and see if it happens again.
if it does, i'll flash a fresh stock image.
SeraldoBabalu said:
thx everyone. i'll wait it out and see if it happens again.
if it does, i'll flash a fresh stock image.
Click to expand...
Click to collapse
Hopefully not! If you do, follow the guide in my signature.
just for good measure, i went back to bone stock 4.2.1 and installed the 4.2.2 update when it got pushed through and the same thing happened again. i didn't even install any apps - just what was in the factory google image. i was just lightly texting, locked my phone and looked at it a few mins later and it was off. this time my battery didn't change and i took notice of the temp of the phone and it was cool.
this only happened after the 4.2.2 update as for the couple of months of 4.2.1, i never had this issue. i've only had stock 4.2.2 for a little over a week.
i'm going back to stock 4.2.1 or maybe will try out a custom. if it does this on 4.2.1 stock, it's gotta be a h/w defect but i'm pretty confident it won't.
thx again all for your suggestions and help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys. See the attached pic. Bought Galaxy S4 octa 3 weeks before. Working fine. But suddenly today appeared a small red dot on screen. You can see it besided word wifi. It gets disappeared when screen gets off or if I turn off the mobile. But when screen is On it is clearly visible. What is it? Is it a hardware issue? Has anyone faced the same isdue on any phone. Currently downloading the latest firmware. Wish after updating firmware this issue get vanish. If not then I have to go to svc.
Thanks in advance.
Sent from my GT-I9500 using Tapatalk 2
Unfortunately, it seems that your phone has a dead pixel which is a hardware issue... there are some apps that pretends to wake-up dead pixels but for me it never worked. The only solution was to send it to repair
chokhu1585 said:
View attachment 2035293
Guys. See the attached pic. Bought Galaxy S4 octa 3 weeks before. Working fine. But suddenly today appeared a small red dot on screen. You can see it besided word wifi. It gets disappeared when screen gets off or if I turn off the mobile. But when screen is On it is clearly visible. What is it? Is it a hardware issue? Has anyone faced the same isdue on any phone. Currently downloading the latest firmware. Wish after updating firmware this issue get vanish. If not then I have to go to svc.
Thanks in advance.
Sent from my GT-I9500 using Tapatalk 2
Click to expand...
Click to collapse
Hi, looks like a stuck pixel on your screen. Use an app from play store that fixes stuck pixel and should fix it.
Something like this >> https://play.google.com/store/apps/...EsImNvbS5odGMuY2hyaXMuYmxhY2tzcG90ZGV0ZWN0Il0.
---------- Post added at 07:58 PM ---------- Previous post was at 07:56 PM ----------
kimkim said:
Unfortunately, it seems that your phone has a dead pixel which is a hardware issue... there are some apps that pretends to wake-up dead pixels but for me it never worked. The only solution was to send it to repair
Click to expand...
Click to collapse
A dead pixel is black. He has a stuck pixel. This can be fixed with some apps. In case doesn't fix , you can go from where you bought it and replace it, but first give a try to some apps that fix stuck pixels.
Thanks for reply Dean and Kimkim. I have installed that app and run it twice. First time for 10 mins and second time for 30 mins. But no luck. That stuck pixel is still there. Now have to go to service center only.
Btw what is the reason behind happening of this? Any idea?
Thanks & Regards,
Chintan
Sent from my GT-I9500 using Tapatalk 4 Beta
chokhu1585 said:
Thanks for reply Dean and Kimkim. I have installed that app and run it twice. First time for 10 mins and second time for 30 mins. But no luck. That stuck pixel is still there. Now have to go to service center only.
Btw what is the reason behind happening of this? Any idea?
Thanks & Regards,
Chintan
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Read here >> https://en.wikipedia.org/wiki/Defective_pixel
Dean-xXx said:
Read here >> https://en.wikipedia.org/wiki/Defective_pixel
Click to expand...
Click to collapse
I have managed to remove a stuck pixel on my S2 by simply rubbing the screen!
It sounds crazy but someone told me to try it and it worked, it never came back.
Just apply pressure to the screen where the stuck pixel is and keep rubbing, it should disappear.
Obagleyfreer said:
I have managed to remove a stuck pixel on my S2 by simply rubbing the screen!
It sounds crazy but someone told me to try it and it worked, it never came back.
Just apply pressure to the screen where the stuck pixel is and keep rubbing, it should disappear.
Click to expand...
Click to collapse
I remember i did this on a old LCD monitor and it worked, but i really wouldn't suggest apply any pressure on s4 screen. They're lots of reports of broken amoled under the glass. So doesn't sound like a good idea. Better to have it replaced for free than to bring it back with broken screen and to be charged for that.
Ok. Thanks everyone. Will go to service center in a day or two to get it replaced.
Sent from my GT-I9500 using Tapatalk 2
I tried rubbing the screen and that stuck pixel disappeared. But it again returns after some time. Tried it 4-5 times already. Why this pixel stuck? Any specific reason.?
Now I have to go svc only.
Sent from my GT-I9500 using Tapatalk 2
This suddenly happened on my phone this Eve of Christmas. It was never dropped, wet nor bent.. It just happened while I was trying out voicemate. I think this is not software related as it is the same when I'm in recovery mode. Sometimes the display is correct and is not garbled but after a few seconds of touching it it acts this way again, if I try to turn off the screen it goes away but returns immediately after. Sometimes the screen won't turn on but I can feel that it is actually on thru the vibration feedback it is giving when trying to press randomly in the screen. I'm still going to try to revert to stock Rom as I am on rayglobe and rooted in case I need to send it in for warranty. I have already reflashed the Rom but still the same.. I just can't believe this is happening hours before Christmas and a few days before the new year.. I'm sure repair services of LG will take time.. Coincidentally, last year when I was using Samsung S3, the motherboard of the phone broke down on New Year's Eve..
Any thoughts what part of the hardware is failing? And what else can I try to troubleshoot before bringing this is to repair? Appreciate your comments. Thank you!
Charles
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk
guys any thoughts what caused this?
upon observation, this is more of a heat issue. if the unit is rested in a cold place it takes more time before the screen gets distorted like this but after a while of having the screen on it starts acting like this.. i hope LG repairs this fast!
Sent it for repair man,nothing else you can do as it seems.I wanted to ask if you had it modded or something,to see if there was something that caused it.But it seems the hardware is failing.
Definitely faulty hardware. Have it sent in for repairs. Looks like a faulty flex cable. Or it could be the main board though.
Sent from my LG-D801 using Tapatalk
This just happened to me
reycharlesconrad said:
This suddenly happened on my phone this Eve of Christmas. It was never dropped, wet nor bent.. It just happened while I was trying out voicemate. I think this is not software related as it is the same when I'm in recovery mode. Sometimes the display is correct and is not garbled but after a few seconds of touching it it acts this way again, if I try to turn off the screen it goes away but returns immediately after. Sometimes the screen won't turn on but I can feel that it is actually on thru the vibration feedback it is giving when trying to press randomly in the screen. I'm still going to try to revert to stock Rom as I am on rayglobe and rooted in case I need to send it in for warranty. I have already reflashed the Rom but still the same.. I just can't believe this is happening hours before Christmas and a few days before the new year.. I'm sure repair services of LG will take time.. Coincidentally, last year when I was using Samsung S3, the motherboard of the phone broke down on New Year's Eve..
Any thoughts what part of the hardware is failing? And what else can I try to troubleshoot before bringing this is to repair? Appreciate your comments. Thank you!
Charles
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Hey mate, this just happened to me
i was wondering how you went about fixing it. Did you sent it to the repair centre.
rakinisbat said:
Hey mate, this just happened to me
i was wondering how you went about fixing it. Did you sent it to the repair centre.
Click to expand...
Click to collapse
So what did you end up doing? This just happened to me as well.
Just happened the same to me, did you fix it? what was it?... My observation is that when it's charging the screen stabilizes
I have read where the KitKat upgrade for the G2 is supposed to add speed and increase battery life even further. For me however it seems its the opposite. I have had way worse battery life since installing (pc lg tool) the KitKat update. I was going all day with anywhere from 40 - 30% left when it was finally plugged in for the night, now I am lucky if I make it to the end of the night. At first I thought perhaps it was just in need of a reboot, but I have done that several times since installation and battery times are still worse. What I don't understand is the battery meter says "System" is to blame for 53% cpu time. Before screen time was my number one battery drain, now its just from being on?.... I don't get it.. Anyone else having this issue, or can shed some light?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What are you doing different? Mine has gotten better since the update
Sent from my LG-D801 using Tapatalk
z0phi3l said:
What are you doing different? Mine has gotten better since the update
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
That's just it, i haven't done anything different. It can't be an app because i haven't installed anything since the upgrade. What bothers me is it seems to be a system process that's causing it.
SoCGHOST said:
That's just it, i haven't done anything different. It can't be an app because i haven't installed anything since the upgrade. What bothers me is it seems to be a system process that's causing it.
Click to expand...
Click to collapse
Location settings/reporting/Google Now on?
Pocket Mode
Not sure if it is something generic across KitKat or if it is specific to my ROM but pocket mode was killing my battery since it was constantly powering my proximity sensors looking for light to unlock the screen.
settings-security-lockscreen notifications-pocket mode.
Hope that helps man
howesfd said:
Not sure if it is something generic across KitKat or if it is specific to my ROM but pocket mode was killing my battery since it was constantly powering my proximity sensors looking for light to unlock the screen.
settings-security-lockscreen notifications-pocket mode.
Hope that helps man
Click to expand...
Click to collapse
theres pocket mode ? where is it located in settings ?
shriom_manerker said:
theres pocket mode ? where is it located in settings ?
Click to expand...
Click to collapse
I provided the path above, like I said though not sure if it is specific to the ROM i'm on(PA 4.4.2) or not. It the only real exposure to kitkat that I've had. If it isn't a default kitkat thing i apologize if I got your hopes up. I will say this though, if it is don't get your hopes up. It's rather annoying and a massive battery drain. With it on my phone acted like it had half the battery it does.
I don't have location settings turned on, so google now shows unavailable for location, also I don't have security turned on, so I have no security lock screen notification settings that I could find... I'm assuming this is only on if you are using pin, or pattern lock. Thanks for the suggestions tho... I'm going to keep monitoring it and see how it goes. So far today it seems to have normalized, Android System is only showing 2%, which is more like it.
I'm on Official LG Stock KK and to be truthful the battery life has been pretty bad. Like not really comparable to 4.2.2 and definitely not comparable to vanilla Android(of course). What's the issue? Anyone know?
Sent from my LG-D801 using xda app-developers app
Had a similar issue. Let It settle for a day or so. If no improvement, that's a pain but go through a factory reset. That should fix it. Did you have a specific setup like root/custom rom before?
Sent from my LG-D801 using Tapatalk
I am having serious Bluetooth battery drain even though it has been off. Anyone know how to stop this? Thanks
Sent from my LG-D801 using XDA Premium 4 mobile app
Draining bad...
Sent from my LG-D801 using XDA Premium 4 mobile app
Last one.
Sent from my LG-D801 using XDA Premium 4 mobile app
Same with me I'm going to do a factory reset luckily I can back up everything to box because they gave me 50GB free!
Sent from my LG-D801 using XDA Premium 4 mobile app
Factory reset fixed it for me.
Sent from my LG-D801 using Tapatalk
Sfkn2 said:
Factory reset fixed it for me.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Will you lose root if you do a factory reset and was this a factory reset from the Stock Recovery or from entering the Settings and inside Backup and Reset menu and then Factory Reset?