Database Users

[Q] the daily show killed my nexus 7 !

So, here is what has happened to my Nexus 7. It worked flawlessly for a few weeks after I bought it. I installed the daily show app and it still worked fine. Went to a friends house to play cards and had the 7 in my pocket. A few hours later I pulled it out of my pocket and the screen was black with random pixels and lines flashing in random colors. I just let it sit there for about 10 minutes, then tried a re-boot. It rebooted fine but the message "Unfortunately the daily show has stopped" or something like that. It then worked ok (I removed the app) but still does the random black screen thing and sometimes shuts off when I want it to only be asleep (annoying when I use it as my morning wake up alarm). I can't believe the app itself was the problem. My guess is maybe it overheated and got damaged by running while in my pocket? I didn't have a pattern to unlock it, only the circle to slide, so I can imagine that it might have started while in my pocket somehow. Should I try and get a new nexus 7 or is there something I can do? random reboots and shut offs are not cool...

you say you had it in your pocket...did you by chance sit on it?
Sent from my Nexus 7 using xda premium

rex.regis said:
you say you had it in your pocket...did you by chance sit on it?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
haha. no. I thought about that right away, however it was in my front pocket. in addition to which physically it looks the same (i.e. no obvious bends or warping on the surface)

thats odd maybe the app has caused it to over heat and that can cause data corruption. I would try to reset it back to factory or if your on a custom rom.. Restore a previous backup in cwm... If still no luck..
go all the way back by wipe and factory rom new download...
Hope you get it resolved.. Keep Your tablet out of your pocket... Get a nice purse. Giggles. well or shoulder bag..

Good job it wasn't the Jeremy Kyle show, That kills everything.

Nexus 4 won't boot. Red LED Flashing

I was playing around with my Nexus 4. It fell in a glass of water. I took it out within 2 seconds. Phone booted up and worked fine except Camera and the earpiece. Those started to work fine after around 5 hrs automatically. I flashed Stock Android 4.2.2 via Fastboot after everything was working fine. It failed while flashing bootloader and then the phone went completely blank. I did 30 mins of work and google search and I was trying all sorts of combinations and the phone booted by luck. After then it went in Blank many times showing *white* LED. I was always able to take it out of that by some combinations. Now the phone got stuck in bootloop. I switched off the phone and plugged it for charging. It charged upto 100%. My mom took my phone and locked in the cupboard (due to exams) I got it today (after 2 days) and when I try to boot then it just shows *Red* LED for some time and then goes off. If I plug it to a wall charger then the Red LED lasts merely a second.
Please help me guys.

iHarkunwar said:
I was playing around with my Nexus 4. It fell in a glass of water. I took it out within 2 seconds. Phone booted up and worked fine except Camera and the earpiece. Those started to work fine after around 5 hrs automatically. I flashed Stock Android 4.2.2 via Fastboot after everything was working fine. It failed while flashing bootloader and then the phone went completely blank. I did 30 mins of work and google search and I was trying all sorts of combinations and the phone booted by luck. After then it went in Blank many times showing *white* LED. I was always able to take it out of that by some combinations. Now the phone got stuck in bootloop. I switched off the phone and plugged it for charging. It charged upto 100%. My mom took my phone and locked in the cupboard (due to exams) I got it today (after 2 days) and when I try to boot then it just shows *Red* LED for some time and then goes off. If I plug it to a wall charger then the Red LED lasts merely a second.
Please help me guys.
Click to expand...
Click to collapse
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.

ashishv said:
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.
Click to expand...
Click to collapse
The phone was powered off in the cupboard

ashishv said:
Take out the battery and reinsert it,i have seen people complaining of red blinking led issue,but in their case,the phone shut down due to 0 battery,and when try to turn on by connecting wall charger,the issue showed up.If there's a possibility that the phone got completely discharged in cupboard(due to low or no signal),then that might be ur issue as well.
Click to expand...
Click to collapse
I am afraid taking out the battery. What if voided the phone ?

If the phone has been water damaged, warranty won't help you anyway so you haven't got anything to lose! Just a reminder, if you drop your phone in water, turn it off (take out the battery if possible) and put it in a bowl of rice for 12-48 hours to help dry it out, do not turn it on before then!

iHarkunwar said:
I am afraid taking out the battery. What if voided the phone ?
Click to expand...
Click to collapse
You are already voided due to water damage.....

BigDig said:
You are already voided due to water damage.....
Click to expand...
Click to collapse
And btw no international warranty for this phone.

But it is already worked completely fine after around 5 days. I also instantly blew a hard dryer on it and it go to work. It shows no signs of Water Damage

ashishv said:
And btw no international warranty for this phone.
Click to expand...
Click to collapse
I can ship it back to US. I bought it from Indian site which ships phone to US if any problems come and will deal with RMA.

iHarkunwar said:
I can ship it back to US. I bought it from Indian site which ships phone to US if any problems come and will deal with RMA.
Click to expand...
Click to collapse
Which site?I used ppobox.

ashishv said:
Which site?I used ppobox.
Click to expand...
Click to collapse
TheAmericanBazaar
Also when it fell in water it had the cover on and the screen protector over too.

Was going to sell and buy HTC One and Google trolled me

iHarkunwar said:
I am afraid taking out the battery. What if voided the phone ?
Click to expand...
Click to collapse
The phone isn't really hard to take apart, I posted a video on YouTube a while back showing how to take apart the phone and replace the screen.
https://www.youtube.com/watch?v=A1aiut8RXhc&feature=youtube_gdata_player
Sent from my Rooted Galaxy S III using xda premium

speedygonzo said:
The phone isn't really hard to take apart, I posted a video on YouTube a while back showing how to take apart the phone and replace the screen.
https://www.youtube.com/watch?v=A1aiut8RXhc&feature=youtube_gdata_player
Sent from my Rooted Galaxy S III using xda premium
Click to expand...
Click to collapse
Will try then

I have a complete set of screw drivers. None worked on the Nexus 4 :/

Similar
Dropped phone in toilet. 2 seconds max. Didnt have luxery of a torque screw or pop open capabilities threw the N4 in bag of rice. 4 days later. it turns on and the screen looks fine, but auto shut down right when main screen loads. Checked for water damage on the inside: void stickers were pink, but phone seemed fine and no sign of water damage, until I took out the battery. it looked a bit damaged. I replaced it today and I am still getting the same issue. Right when I am taken past the Cyanogenmod loading screen, the main page loads and says "shutting off" or "powering down" whatever it says. The battery seems to always be between 16-18% also. Anyone ran into a situation like this or have any suggestions? please!!!! thanks!

[Q] Red Light of Death - RMA or Repairable?

I very recently had my Nexus give me the blinking red light of death. It started when I couldn't flash the latest Franco Kernel due to an "Unmatching MD5" error. So, I thought why not update Cyanogenmod 10 to the latest nightly? Lo and behold, it skips the prompt asking if I want to install it and the phone shuts off. The furthest I've gotten right now is getting it to the standard recovery, and that was only for a minute (this was after I hooked the phone up and used the Nexus toolkit to reflash the stock recovory). Now, when I try to flash the stock ROM, I either get "device not found" or that some random error has happened. I'm stuck between either using software methods to fix this, or sending it in for an RMA sooner than I thought I would (it has tons of scratches and dents).
Just as a note, I know about the battery trick, and I'm not up for doing that. I'd sooner RMA it, as I believe after relocking the bootloader it would still be under warranty since it seems to technically have no ROM installed right now.

Will it boot into fastboot?

It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.

CodemasterRob said:
It will. It won't go beyond that though. I did, at one point, get the default recovery screen where the dead android with a red triangle in it's chest popped up, but I haven't been able to get past that. I have a replacement coming in, but it'd be great to know how to fix this in case the replacement faces the same issue.
Sorry for the late reply, didn't have it set to email me or even had it subscribed.
Click to expand...
Click to collapse
If you can get into Fastboot mode, have you tried flashing the stock images from Google?

Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.

CodemasterRob said:
Yes. I've, as far as fastboot has told me, successfully flashed the stock kernel, ROM, and recovery, and the bootloader is still in tact so I can lock and unlock that at will. The phone is completely dead now though. Must have been a battery problem, because it won't even show the light now.
Click to expand...
Click to collapse
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app

Mephisto Zap said:
You need to take it apart and pull the battery connection off. Its the same thing as a battery pull. I had to do it this morning cause I had the red light of death. Booted back up no problem. There's a video on YouTube red light of death fix.
Just saw you know about it. Mine was bought used so I couldn't RMA. But it works easy enough. And I'm a amateur who isn't good at working on small tech stuff and it was easy enough for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Heh, I was about to direct you to the OP
That *might* fix it, but I believe a full battery replacement is in order. The phone was reaching an excess of 150 degrees before it shut down, it literally burnt my leg and gave me a red spot. All is well though; I managed to pry the SIM card out, wipe all of the partitions, and get it back to factory state before it completely turned over in it's grave. Learned my lesson the first time around; got myself a case to prevent all of those nasty scratches and I'll be ordering XO skins soon.

[INFO] How not to hard-brick your Nexus S

This is for anyone who does not want to accidentally HARD-BRICK their Nexus S.
I have read a post somewhere in this device's section that some chinese people who owned this device did something similar which also resulted to a non-repairable hard-brick.
Do not remove the battery if you still see the google logo before the boot-animation.
Description of the hard-brick I experienced:
The capacitive touch buttons do not light up and there is no vibration when the power button is pressed.
The device cannot be detected by any PC.
The device is now literally just a brick.
Updates(12/13/2013 - 01/11/2014):
I sent my device to several phone technicians with proper equipment but nobody was able to tell me why this happened, and what exactly happened.
Each of those techs examined the device for several hours and their conclusion: none.
JTAG (did twice) will not work in this kind of hard-brick.
I went to two official samsung service centers and they both suggested for me to have the motherboard replaced at the cost of ~$270. They cannot explain what happened either.
If I am to obtain a motherboard replacement from an unofficial service the cost would still be 2x the price of a used nexus s.
ej8989 said:
I'm about to update my nexus s to the latest CM11. I wiped everything, flashed the rom and gapps via recovery, and everything was fine.
Until.... I decided to remove my sim card, as usual, then set the phone up for a fresh install.
What I did wrong:
1. I removed the back cover, the battery, then the sim card
2. I re-installed the battery, but NOT the back cover
3. I booted the device, then upon boot (google logo) the battery accidentally FELL OFF.
So what happened? I re-installed the battery, then NOTHING. When pressing the power button, no vibration, no signs of life. NOTHING.
I learned a lot using this device. Time to move on to a faster phone
Click to expand...
Click to collapse

ej8989 said:
I'm about to update my nexus s to the latest CM11. I wiped everything, flashed the rom and gapps via recovery, and everything was fine.
Until.... I decided to remove my sim card, as usual, then set the phone up for a fresh install.
What I did wrong:
1. I removed the back cover, the battery, then the sim card
2. I re-installed the battery, but NOT the back cover
3. I booted the device, then upon boot (google logo) the battery accidentally FELL OFF.
So what happened? I re-installed the battery, then NOTHING. When pressing the power button, no vibration, no signs of life. NOTHING.
I learned a lot using this device. Time to move on to a faster phone
Click to expand...
Click to collapse
Sorry about your phone , but I'm not trying your how to guide... What are you moving to?
Sent from my Nexus S using XDA Premium 4 mobile app

Setting.Out said:
Sorry about your phone , but I'm not trying your how to guide... What are you moving to?
Sent from my Nexus S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It'll take me half a month to decide. I chose the nexus s because of voodoo sound. I don't really know what to choose next. :/

ej8989 said:
It'll take me half a month to decide. I chose the nexus s because of voodoo sound. I don't really know what to choose next. :/
Click to expand...
Click to collapse
I want an Oppo find 5.. or an N5.. or a Moto X.. or a Htc one... or a... you're going to need that month..

It can be fix, but only to a shop service store.. with their stuff. They take the battery out.. are wiring your phone.. and install the new rom.. does'nt matter witch one. Then you can install what you want..

ej8989 said:
I'm about to update my nexus s to the latest CM11. I wiped everything, flashed the rom and gapps via recovery, and everything was fine.
Until.... I decided to remove my sim card, as usual, then set the phone up for a fresh install.
What I did wrong:
1. I removed the back cover, the battery, then the sim card
2. I re-installed the battery, but NOT the back cover
3. I booted the device, then upon boot (google logo) the battery accidentally FELL OFF.
So what happened? I re-installed the battery, then NOTHING. When pressing the power button, no vibration, no signs of life. NOTHING.
I learned a lot using this device. Time to move on to a faster phone
Click to expand...
Click to collapse
too me, but yesterday
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
sirtivi said:
It can be fix, but only to a shop service store.. with their stuff. They take the battery out.. are wiring your phone.. and install the new rom.. does'nt matter witch one. Then you can install what you want..
Click to expand...
Click to collapse
You are sure??and you have idea what it costs to fix it?

sirtivi said:
It can be fix, but only to a shop service store.. with their stuff. They take the battery out.. are wiring your phone.. and install the new rom.. does'nt matter witch one. Then you can install what you want..
Click to expand...
Click to collapse
pask23 said:
too me, but yesterday
---------- Post added at 10:40 AM ---------- Previous post was at 10:32 AM ----------
You are sure??and you have idea what it costs to fix it?
Click to expand...
Click to collapse
No it can't be repaired. I had my unit checked thru a phone repair shop and they got all the tools needed for JTAG, JIG, re-flash, etc.etc...
For 5 hours they tried everything and I waited. Their conclusion: something's broken on the circuit board. Might be the integrated chip, the processor, etc..
Their advice for me is to hand it over to samsung for a circuit board replacement, but that will cost as much as a 2nd-hand Nexus S.
But still, there's no harm, in trying. Tell me if you had yours fixed :good:

ej8989 said:
No it can't be repaired. I had my unit checked thru a phone repair shop and they got all the tools needed for JTAG, JIG, re-flash, etc.etc...
For 5 hours they tried everything and I waited. Their conclusion: something's broken on the circuit board. Might be the integrated chip, the processor, etc..
Their advice for me is to hand it over to samsung for a circuit board replacement, but that will cost as much as a 2nd-hand Nexus S.
But still, there's no harm, in trying. Tell me if you had yours fixed :good:
Click to expand...
Click to collapse
You can try go and ask about the cost.. ussualy it shoed do around 20-50 Euro depending the contry.

sirtivi said:
You can try go and ask about the cost.. ussualy it shoed do around 20-50 Euro depending the contry.
Click to expand...
Click to collapse
Samsung service center told me it would cost as much as €200 lol. That's about as much as a Nexus 4. I'll go with the Nexus 4.

ej8989 said:
Samsung service center told me it would cost as much as €200 lol. That's about as much as a Nexus 4. I'll go with the Nexus 4.
Click to expand...
Click to collapse
Try a private service.. not a official service.

After a little less than a month of finding phone repair shops (even official samsung service center) noone was able to explain to me what happened to my phone; not even samsung. Because of this, samsung just concluded that replacing the motherboard of the device for about €200 will fix it without being 100% sure.
This is therefore a warning to all Nexus S users: Do not remove the battery when the phone is still booting, specifically on google logo. :good:

sirtivi said:
Try a private service.. not a official service.
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying:

ej8989 said:
This is for anyone who does not want to accidentally HARD-BRICK their Nexus S.
I have read a post somewhere in this device's section that some chinese people who owned this device did something similar which also resulted to a non-repairable hard-brick.
Do not remove the battery if you still see the google logo before the boot-animation.
Description of the hard-brick I experienced:
The capacitive touch buttons do not light up and there is no vibration when the power button is pressed.
The device cannot be detected by any PC.
The device is now literally just a brick.
Updates(12/13/2013 - 01/11/2014):
I sent my device to several phone technicians with proper equipment but nobody was able to tell me why this happened, and what exactly happened.
Each of those techs examined the device for several hours and their conclusion: none.
JTAG (did twice) will not work in this kind of hard-brick.
I went to two official samsung service centers and they both suggested for me to have the motherboard replaced at the cost of ~$270. They cannot explain what happened either.
If I am to obtain a motherboard replacement from an unofficial service the cost would still be 2x the price of a used nexus s.
Click to expand...
Click to collapse
my nexus s isn't bricked but capacitive touch buttons are not working (also not lighting up) i have tired many custom roms... any suggestion?
there is also no vibration in phone, may be it is a hardware problem...

ej8989 said:
Description of the hard-brick I experienced:
The capacitive touch buttons do not light up and there is no vibration when the power button is pressed.
The device cannot be detected by any PC.
The device is now literally just a brick.
Click to expand...
Click to collapse
This is what happened to my phone just minutes ago. I was watching Frozen using MX Player (S/W decoder) and the screen froze. I removed the battery and when I attempted to turn my phone on, It just wouldnt.

rho57 said:
This is what happened to my phone just minutes ago. I was watching Frozen using MX Player (S/W decoder) and the screen froze. I removed the battery and when I attempted to turn my phone on, It just wouldnt.
Click to expand...
Click to collapse
Try a JTAG service. Most phone repair shops have them. The last resort would be the unbrickable resurrector, which i have yet to try. I don't have the tools needed yet (and a linux system).

ej8989 said:
Try a JTAG service. Most phone repair shops have them. The last resort would be the unbrickable resurrector, which i have yet to try. I don't have the tools needed yet (and a linux system).
Click to expand...
Click to collapse
Thanks. I hope there'll be repair shops that could do that. I was tempted to buy a new phone, but I'll try as you suggested. BTW, in my case if I let the battery in for quite some time the phone heats up. Did this happen to yours too?

rho57 said:
Thanks. I hope there'll be repair shops that could do that. I was tempted to buy a new phone, but I'll try as you suggested. BTW, in my case if I let the battery in for quite some time the phone heats up. Did this happen to yours too?
Click to expand...
Click to collapse
Yes it does.

I dislike "me too!" posts, but one is appropriate here.
This just happened to me, exactly as described by OP.
Time to find a damaged Nexus S for real cheap and salvage the board, or get a new phone. Certainly not looking for another Samsung device, this issue is ridiculous. Fortunately Samsung has nothing to do with the Nexus 5.
I'm going to call for this thread to be stickied. Had I been aware of this vulnerability, I never would have been hacking on the phone with the cover off.
Edit: The thread title should be changed, to add something to the effect off "- Battery removal during Google Logo == BRICK"

Strange.
I removed the battery while it was booting (Google Logo) about 20 times today already.

Hrm. Was your handset attached to USB at the time? Mine was.

touch screen problems?

I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)

mikeinaus said:
I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
Click to expand...
Click to collapse
I have this problem too, any fixes?

Well I am in shock as to how we all have the same exact problem.
I first thought it was hardware failure on the screen itself and was pretty bummed. But now I see people have the exact same unresponsive touch screen in the exact same spot as mine? What ROM/Kernel are are you guys running? I am running what is in my sig and had not noticed it before until a couple of days ago. Coupled with the unresponsiveness, my Knock on does not work and the phone becomes mildly warm faster than usual. I think it might be a kernel software issue.

Ugh... I was hoping this wouldn't turn in to this big of a problem. I've got the same thing here, VS980 after flashing a Cloudy ROM.
I took over a thread here recently http://forum.xda-developers.com/showthread.php?p=52858791 , but I'll post here again anyways. I wonder if it's the same spot with you guys too. It's right where the install button is on the Play Store, right? For a few hours after it started it went back to normal, then messed up again permanently.
TOT'ing back to 12B didn't help, so I got a replacement device from Verizon. I've yet to send back my old one because I'm worried about the unrooted flag in the bootloader and settings.
I don't have enough posts yet to be able to do this, but can someone alert a dev about this? Particularly in the thread of whatever ROM it was that you last used? A lot of people in the last thread said it came from Cloudy, and I figured it might make sense as Knock Code was supposed to be a feature on there even though the VS980 source wasn't out. Then again I probably have no idea what I'm talking about, but I'd love to hear from someone who does.

I dont think my blacked out area is quite as thick as yours but yes its in the exact same place. To confuse things even more my phone just started working properly again (for how long is another story). Its very odd that It hasnt worked once in 2 months or so and now twice in 2 days its started working.
As a side note I'm pretty sure I started having this problem immediately or very shortly after the OTA kitkat update. I'm now running cloudypro II 2.0 with 3.4.0 kernel, which as i said before didnt fix the problem in the 1 month ive been using this rom.
I originally thought it may have been a software issue, but for it to randomly start/stop working all of a sudden after so long of no function (with no software being added or changed) I'm thinking its more likely a hardware problem? When I fly home on Monday I'm going to try opening up the phone and cleaning the contacts to the from the touchscreen to the mainboard.
If it is software related it may have something to do with air plane mode. I get almost no signal where I'm working at the moment and the constant searching for signal kills my battery pretty fast so I've started using air plane mode the past few days. Thats the only thing out of the ordinary that i've done software wise.

Having the same issue!!
Has anyone found a solution ?
Please reply.

hashir1296 said:
Has anyone found a solution ?
Please reply.
Click to expand...
Click to collapse
Yes, we've sent it to LG for repairs and they were able to fix it easily.

Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app

Had the same today but at the middle of the screen, I pressed on the corners and around the screen pretty hard and it is back to normal(for now).
Hope it wont come back.
You can unroot the device by flashing original rom with LG flash tool.

THISISINSANE said:
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am completely stock.

Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app

THISISINSANE said:
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
You claimed insurance rather than with LG repair?

Sfkn2 said:
You claimed insurance rather than with LG repair?
Click to expand...
Click to collapse
I went with T-Mobile's warranty replacement. I already sold my backup phone so I couldn't send the phone to LG for repairs and still have a phone
Sent from my LG-D801 using XDA Free mobile app