Database Users

[Q] Misbehaving N1

I got my AMOLED N1 back in Feb 2010.
Unlocked bootloader, rooted 2.2.1.
The problem which existed from day one but showing much more often these days, is that after running an app (e.g. Market) the touch screen misbehave. It either does not register the touch, or maps the touch about an inch lower from where it should be. The phone has plenty of free memory (internal).
The problem is more prominent since the 2.2.1 update (but I am not sure it's related).
Does anybody else experiencing this?
TIA

Most people!
There is no solution other than the temporary fix of turning the screen off and then on again.

OferR said:
I got my AMOLED N1 back in Feb 2010.
Unlocked bootloader, rooted 2.2.1.
The problem which existed from day one but showing much more often these days, is that after running an app (e.g. Market) the touch screen misbehave. It either does not register the touch, or maps the touch about an inch lower from where it should be. The phone has plenty of free memory (internal).
The problem is more prominent since the 2.2.1 update (but I am not sure it's related).
Does anybody else experiencing this?
TIA
Click to expand...
Click to collapse
Yes.
I'm getting really frustrated with the N1 due to the ****ty touch screen.
I had a play with my brother's Nexus S.... SO much nicer and smoother. The touchscreen on the N1 is abysmal and shocking!
I've also noticed "freezes" in the sense that the display won't come up - only the touch screen buttons light up and then slowly fade off.... only way to recover is to pull out the battery. Really annoying.

DirkGently1 said:
Most people!
There is no solution other than the temporary fix of turning the screen off and then on again.
Click to expand...
Click to collapse
Thanks DirkGently1, itay1,
Is there anything that can be done to fix this? e.g. replace a part (whether under warranty or not)?
It is actually becoming hard to even use the N1 as a phone or for text..

OferR said:
Thanks DirkGently1, itay1,
Is there anything that can be done to fix this? e.g. replace a part (whether under warranty or not)?
It is actually becoming hard to even use the N1 as a phone or for text..
Click to expand...
Click to collapse
DirkGently1 said:
...There is no solution other than the temporary fix of turning the screen off and then on again.
Click to expand...
Click to collapse
There's always the option of selling the phone while it's still worth something and buying something else!

DirkGently1 said:
There's always the option of selling the phone while it's still worth something and buying something else!
Click to expand...
Click to collapse
oh well...

It sounds like yours is worse than the normal problem. My screen will only mess up once every few days, some people have gone months, some a few times a day.
But if your phone is unusable just get it replaced under warranty.

Clarkster said:
But if your phone is unusable just get it replaced under warranty.
Click to expand...
Click to collapse
I think my phone sensed that we are talking about it. All of the sudden it behaves.

OferR said:
I think my phone sensed that we are talking about it. All of the sudden it behaves.
Click to expand...
Click to collapse
My first experience using Android was turning on my Nexus One and encountering this issue the very first time i had to use the screen! The device i have has had this problem in varying degrees since i got it. Very bad to start with, not so frequent after i sent it back for repair.
Take a look at the poll from my own thread about the issue...
http://forum.xda-developers.com/showthread.php?t=878477
Pretty commonplace problem, which along with the power buttons failing detracts from an otherwise great phone.

Blame HTC, I had this issue on my first N1 earlier last year. I would turn the screen off then turn it back on.

OferR said:
I think my phone sensed that we are talking about it. All of the sudden it behaves.
Click to expand...
Click to collapse
I find it behaves better when the screen is clean. Perhaps finger grease can confuse it... it might be *that* sensitive.

I flashed the frg83d update this morning and I've gone all day without the crazy screen thing and I'm loving it lol!
*knock on wood *
Hope it stays that way!

@DirkGently1:
I've added my vote
@itay1:
I was just about to write the same thing. It is much better after I've cleaned it (which I didn't for a while)
I am not using any screen cover. I never did. But maybe there is a cover that helps. Those of you who never suffered from this issue, do you use a screen cover/protector? which one?
Also, maybe the issue is intensified by how dry (or not) our fingers are compared to others..
@dusty-:
Do you mean frg83g? frg83d did not help my case. sorry..

Yes I meant frg83g lol

2.3.3 and back button stuck issue

I had a NS with a back button that used to get stuck and i exchanged that NS for a new one. Since then i did not have the issue. Here comes 2.3.3 and the little monster is back. I have seen it twice in the past few hours. Google fix this ASAP or this phone is going back for good.
Anyone else with this problem?
Sent from my Nexus S using XDA App

FlyingRequin said:
I had a NS with a back button that used to get stuck and i exchanged that NS for a new one. Since then i did not have the issue. Here comes 2.3.3 and the little monster is back. I have seen it twice in the past few hours. Google fix this ASAP or this phone is going back for good.
Anyone else with this problem?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's not good!! I had this issue occasionally (never exchanged the phone though) and so far since 2.3.3 it's not happened.
I would strongly suggest raising the issue on the google support forums - there is an existing thread from before the 2.3.3 update which as it happens was meant to fix the problem......
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=455215ff8747658b&hl=en&start=40

Mine is N1, I also got back button problem occasionally since 2.3.3. I press the Back, I feel the vibration, but there is no action. I should retry few times.
I guess this is 2.3.3 bug.

kikikaka said:
Mine is N1, I also got back button problem occasionally since 2.3.3. I press the Back, I feel the vibration, but there is no action. I should retry few times.
I guess this is 2.3.3 bug.
Click to expand...
Click to collapse
u know i had this issue on stock 2.3.2, both home and search was not working, then i wiped data & cache from stock recovery, and then it started working again, worth giving a try!!!

back button is very irresponsive in 2.3.3 !!! i thought google was supposed to fix that s**t. instead it has got even worse for me.

deeren said:
back button is very irresponsive in 2.3.3 !!! i thought google was supposed to fix that s**t. instead it has got even worse for me.
Click to expand...
Click to collapse
my back button is very responsive maybe you need to reflash.

OK I take back what I said previously, this has started happening to me again now. In fact I'd say it's worse than it was before.
I have no idea what to do other than trying to exchange the phone which will probably be a nightmare because I've had it since early January..........

weird cause i read people saying that if their phone had a back button issue it was fixed with 2.3.3

Well I've taken it back to the carphone warehouse where I bought it, they are going to attempt a repair..............will hopefully end up with an exchange for a new handset - i'll keep you posted.

Well the nexus one never had this problem at all, never. And now since the update it too has this issue. So that's pretty solid proof to me that this problem exists and needs to be fixed by Google.

I have non rooted nexus s 2.3.2 and noticed this for the first time last night. Back button key would either stick and/or be un responsive (light would turn off).
I wonder I'd this be a memory issue in that it might occur more frequently when the device is low. Notice a lot of apps run services around midnight and in the morning when this is happening for me..
I have also seen problems with green screen from flash when memory is low.
Closing some apps seems to solve this.
Just a thought. Hope this is not a sign of a hardware failure.

I'm waiting to collect my "repaired" Nexy - wondering what if anything they will have done to try and fix it.....
Feel naked without my phone........

Take off battery cover. Tighten up a bit the screws on the back of the phone. See if that changes anything. I experienced that a little while ago, tightened the screws and now all's good. Haven't seen a single issue since. 2.3.2 and 2.3.3
Sent from my Nexus S using XDA App

bogdi1988 said:
Take off battery cover. Tighten up a bit the screws on the back of the phone. See if that changes anything. I experienced that a little while ago, tightened the screws and now all's good. Haven't seen a single issue since. 2.3.2 and 2.3.3
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well I dont have the phone right now but I'll certainly give this a try if the problem happens again once I have the phone back.
Out of interest what size/type of driver do you need to fit the screw heads??
Thanks!!!

moon-unit said:
Well I dont have the phone right now but I'll certainly give this a try if the problem happens again once I have the phone back.
Out of interest what size/type of driver do you need to fit the screw heads??
Thanks!!!
Click to expand...
Click to collapse
a small philips head screw driver

same problem with me. I upgrade to 2.3.3, the back button will stick for several seconds especially when you hit back key very fast and repeat after fast scrolling the screen.
I flash back to 2.3.2, change rom, not install apps, the problem is still there. And even in bootloader, the issue is still there.

I've just been told my phone is being sent to some central repair hub and might take 28 days to get back to me :-(
will probably get scratched to bits and still wont be fixed.....
Guess I'll have to dig out the old Sony handset to keep me going for a few weeks..today is a bad phone day...

Well I picked up the phone today and noticed a few things where different, firstly I now have an unlocked padlock icon at the bottom of the bootscreen - On checking recovery it would seem my bootloader has been unlocked....
Secondly it was running 2.3.1 which I also found odd?
Going charge it up and do a manual update to 2.3.3 using the full 90mb ROM, wonder if the back button issue has been fixed......? the repair notes said the PCB had been checked and cleaned......
I'll keep you posted.

Need help explaining an odd issue.

I really cannot figure out this issue I'm having. Basically, I have the black rubberish/flexible case that T-Mobile sells. Once in a while, while using the touch keyboard ( stock gingerbread, I'm using cm7.) A couple letters become unresponsive. Most work, but others will not.
Weird thing is, when this happens and I take the case off, all goes back to normal. Maybe I'm missing something here, but how could the case cause this?
Sent from my HTC Glacier using XDA App

kimbernator said:
I really cannot figure out this issue I'm having. Basically, I have the black rubberish/flexible case that T-Mobile sells. Once in a while, while using the touch keyboard ( stock gingerbread, I'm using cm7.) A couple letters become unresponsive. Most work, but others will not.
Weird thing is, when this happens and I take the case off, all goes back to normal. Maybe I'm missing something here, but how could the case cause this?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Maybe the case is applying pressure to the device and for some reason making the screen less responsive. I have this with my TPU-S Curve case and the one with the kickstand on it.

I actually believe that is a CM7 bug. I have experienced the same problem on recent nightlies. Some keys on the keyboard will go unresponsive, while others will work. Occasionally the entire keyboard locks up. Once, the keyboard worked but the image of the keyboard didn't show up (tapping in random spots on a webpage resulted in text being typed, lol).

synaesthetic said:
I actually believe that is a CM7 bug. I have experienced the same problem on recent nightlies. Some keys on the keyboard will go unresponsive, while others will work. Occasionally the entire keyboard locks up. Once, the keyboard worked but the image of the keyboard didn't show up (tapping in random spots on a webpage resulted in text being typed, lol).
Click to expand...
Click to collapse
I have evil's unity rom so it cant be cm only. I havent tried the kb without the case off though.

synaesthetic said:
I actually believe that is a CM7 bug. I have experienced the same problem on recent nightlies. Some keys on the keyboard will go unresponsive, while others will work. Occasionally the entire keyboard locks up. Once, the keyboard worked but the image of the keyboard didn't show up (tapping in random spots on a webpage resulted in text being typed, lol).
Click to expand...
Click to collapse
Everyone experiences that in any rom, even stock, once in a while. The point is, some letters work, some dont. The ones that dont work usually are not even close to each other. and EVERY time it happens, I take off the case and it goes back to normal.
As for the theory that the case was causing pressure, the chances of that are slim for two reasons:
1. It hardly even reaches over the glass. at most, a couple millimeters. http://www.t-mobile.com/shop/AddOns...48e2-bb7a-0e5d354aefa7&inCart=True&catCode=21
2. Being a gel skin, it doesn't really cause pressure to the phone at all. (I could be wrong here, it just seems unlikely.)
This just baffles me because I KNOW its the case causing it but I can't begin to comprehend why.

Ace42 said:
Maybe the case is applying pressure to the device and for some reason making the screen less responsive. I have this with my TPU-S Curve case and the one with the kickstand on it.
Click to expand...
Click to collapse
Just for kicks I tried applying pressure to the edges of the screen using the gel case while typing. I also wiggled the phone around in the case so I could test all positions, all while typing away and nothing could reproduce the unresponsiveness.

kimbernator said:
Just for kicks I tried applying pressure to the edges of the screen using the gel case while typing. I also wiggled the phone around in the case so I could test all positions, all while typing away and nothing could reproduce the unresponsiveness.
Click to expand...
Click to collapse
The only solution is to ditch the case or just deal with the screen not responding.

Ace42 said:
The only solution is to ditch the case or just deal with the screen not responding.
Click to expand...
Click to collapse
I've come to this conclusion as well. The only thing keeping me from ditching the case is the fact that this is one dang slippery phone.

kimbernator said:
I've come to this conclusion as well. The only thing keeping me from ditching the case is the fact that this is one dang slippery phone.
Click to expand...
Click to collapse
Yeah that's true and I like the case to protect it when it falls.

Perhaps the gel case is electrically conductive? I noticed one day I was caught in the rain and some raindrops fell on my touchscreen, which caused random things to be selected until I wiped the water off.

It actually might not be the case... The myTouch 4G's screen has random spots that die temporarily for no reason, and keeping away from the screen or locking and unlocking it can revive the spots. It's not the case at all, probably just the time it takes you to take off the case that the spots revive and convince you that it's the case. Try letting it sit for about 20 seconds when the screen dies and see what happens.

synaesthetic said:
Perhaps the gel case is electrically conductive? I noticed one day I was caught in the rain and some raindrops fell on my touchscreen, which caused random things to be selected until I wiped the water off.
Click to expand...
Click to collapse
Water does that. Wet a paper towel and you'll see.

GazaIan said:
It actually might not be the case... The myTouch 4G's screen has random spots that die temporarily for no reason, and keeping away from the screen or locking and unlocking it can revive the spots. It's not the case at all, probably just the time it takes you to take off the case that the spots revive and convince you that it's the case. Try letting it sit for about 20 seconds when the screen dies and see what happens.
Click to expand...
Click to collapse
When at home I use the phone without the case quite regularly. I've never had this issue when the case isn't on.
In fact, I can usually (Without taking the case off) go back to the homescreen and do stuff, all spots being responsive, while the keyboard is acting funky. The keyboard itself has the issue but nothing else, even when using the same touchscreen spots.
It's such an odd correlation, the keyboard software itself and the case. Yet there has to be something that one does to the other.
Also, just to make this clear - this ONLY happens to the keyboard. If that theory was correct I would experience this in any app

I noticed this also when I first bought my phone, bought the rubber case the same day. after a couple of months, the letters towards the end of the keyboard would become less responsive and I had no idea why. took the case off and it went away. so I ditched the rubber case and got a TPU, never had the problem since then. I think over time the rubber case gets a bit stretchier and bigger, causing you to have to sort of roll your finger around/over the case to press the keyboard buttons on the end(unless in landscape mode)

You know I've always had this problem, and I thought I was the lone soul that had this retarded hardware (maybe software?) issue. I was on Royal Ginger 2.1 and never had this problem. But then subsequently left RG and started using ROM's like Virtual Fusion, MIUI, Virtual Unity, CM7 RC1 and other CM7 nightlies and all of them I've had the problem where some of my keys would just stop working, most noticeably the "delete" key. Other keys like the letters "P" and other vowels would cause the same problem as well. So I figured it's just another list to add on to the plethora of hardware defects that plagues this phone. I've used several KB's as well such as Flex T9, SwiftKey X, SmartKeyboard Pro and even the stock GB keyboard and problem still persisted in all of them.
So I thought what the hell might as well flash Royal Ginger 2.1 to see if the problem is still there and after 2 days I have yet to encounter it! So now I'm baffled... I was for sure that it was hardware related but now I don't get why it's not happening ONLY to Royal Ginger...
I have had the same case on my phone, it's a TPU case. I know it is not the cases' fault as it's always on my phone even now when I'm on RG where I have yet to experience that problem even once.
So I'm pretty much dumbfounded...

I don't think it's the case. I thought it was a ROM thing... agreeing with mackster on this... haven't had a problem while on RoyalGinger 2.1, but have encountered it on CM7 RC1, MIUI & Virtuous Unity...
Sent from my HTC Glacier using XDA App

Problem with orientation involving hardware keyboard.

My phone will switch to landscape orientation when completely closed. I can finally get it to switch into portrait by SLIGHTLY nudging the screen to the right. I've been having this problem ever since I got my EVO Shift around June. It's particularly annoying because it causes the screen to wake, and my phone is usually in my pocket causing it to move around. I often find my phones display is randomly on when I pull it out. It causes even more problems when I'm listening to music.
I want to know if anyone else has experienced this problem and/or if anyone has a suggestion/knows how I can fix this issue myself.
Sent from my PG06100 using Tapatalk

What Rom are you using? Are you rooted? You can disable Auto rotate. Menu-Settings-Auto rotate , and uncheck it. But it should not be rotating on the home screen unless you flashed a mod to do so.

prboy1969 said:
What Rom are you using? Are you rooted? You can disable Auto rotate. Menu-Settings-Auto rotate , and uncheck it. But it should not be rotating on the home screen unless you flashed a mod to do so.
Click to expand...
Click to collapse
Changing that setting does not do anything. As I stated in the title, this problem is related to the hardware keyboard. The mechanism that detects if the hardware keyboard is open or not is malfunctioning. It's detecting that it's open when it's completely shut, thus causing orientation switch.
EDIT: Just to clarify, this has happened on multiple roms. Stock 2.2/2.3, CM7, and MIUI. I'm currently running MIUI. I just want to avoid turning to Sprint to fix this issue ;(

Alvien89 said:
Changing that setting does not do anything. As I stated in the title, this problem is related to the hardware keyboard. The mechanism that detects if the hardware keyboard is open or not is malfunctioning. It's detecting that it's open when it's completely shut, thus causing orientation switch.
EDIT: Just to clarify, this has happened on multiple roms. Stock 2.2/2.3, CM7, and MIUI. I'm currently running MIUI. I just want to avoid turning to Sprint to fix this issue ;(
Click to expand...
Click to collapse
Run G-Sensor calibration (bubble level in market if not on sense) and see my CM7 optimal settings thread here:
http://forum.xda-developers.com/showthread.php?t=1262313
Basically want only 0 and 90 degrees of rotation. That should help.

If it did it on the stock Rom unrooted, than I would have to say it's a hardware issue. If it started after you rooted, than I would just RUU back to stock and see if that fixes the issue. But you might as well try the RUU if you have to take it back to Sprint anyway. The Froyo 2.2 RUU is HERE if you do decide to go that route.

I'm positive it's a hardware issue. I can't remember exactly when I got my Shift, but it was stuck on 2.3 OTA. The problem was occurring then and is still present on all the custom ROMs I've tried so far. I guess I'll just have to take this thing up to my Sprint repair store ;(
Sent from my PG06100 using Tapatalk

I'm not absolutely sure about the shift, but I know a lot of phones "read" the position of the keyboard by magnetic movement. Your magnet may have come loose. Any drops you remember? Very possibly. I wouldn't sweat taking it in if you have a repair store near by. It should be a quick fix.
Sent from my PG06100 using xda premium

Mine did this all the time... I got the htc case and there is no more wiggle to the keyboard and it stays completely shut... I actually just got a brand new replacement, so this problem happened with my old shift...
Sent from my PG06100 using Tapatalk

drob311 said:
Mine did this all the time... I got the htc case and there is no more wiggle to the keyboard and it stays completely shut... I actually just got a brand new replacement, so this problem happened with my old shift...
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I was thinking a case may fix the problem and/or prevent future problems. I've been looking at the OtterBox Commuter case. It's on sell for $21.85 on Amazon, but I'd like to find something a little cheaper. Any suggestions on a good, inexpensive case?

Alvien89 said:
I was thinking a case may fix the problem and/or prevent future problems. I've been looking at the OtterBox Commuter case. It's on sell for $21.85 on Amazon, but I'd like to find something a little cheaper. Any suggestions on a good, inexpensive case?
Click to expand...
Click to collapse
What ever you do, dont get the black carbon fiber holster and shield from sprint, when i used it the thing would short my screen out and i would have to flick it really hard in the middle to get it to come back, i removed the case and it has been fine since
Sent from my PG06100 using xda premium

strapped365 said:
What ever you do, dont get the black carbon fiber holster and shield from sprint, when i used it the thing would short my screen out and i would have to flick it really hard in the middle to get it to come back, i removed the case and it has been fine since
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Weird. I'm rocking that same case now without that problem.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!

jesusice said:
Weird. I'm rocking that same case now without that problem.
ALL HAIL OTAKING71, THE RAPER OF HBOOT!!!
Click to expand...
Click to collapse
It started about 5 months after i got my phone, and then i was forced to deal with it because no root so it hasnt dont it since i took the case off
Sent from my PG06100 using xda premium

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