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
Related
First a disclaimer ... actually two disclaimers ...
#1. I'm an Android noob - I had installed it onto my old AT&T Fuze and loved it and based on that bought a Dell Streak which arrived today;
#2. Within an hour of getting it, it was rooted and 2.1 O2 image installed
I love it. Faster than I can believe is possible over 3G, smooth, lovely.
Except it constantly shuts down. It seems almost every time I go to switch it on it's booting from startup again ... Dell logo ... O2 logo ... then home screen.
OK, 3 disclaimers ...
#3. I've installed a ****load of apps onto it already
Is there an application that will allow me to monitor which applications are causing the instability, or do I just have to suck it up as the cost of running something that's beta/unstable/wrong network/wrong device ... ?
p_razzi said:
First a disclaimer ... actually two disclaimers ...
#1. I'm an Android noob - I had installed it onto my old AT&T Fuze and loved it and based on that bought a Dell Streak which arrived today;
#2. Within an hour of getting it, it was rooted and 2.1 O2 image installed
I love it. Faster than I can believe is possible over 3G, smooth, lovely.
Except it constantly shuts down. It seems almost every time I go to switch it on it's booting from startup again ... Dell logo ... O2 logo ... then home screen.
OK, 3 disclaimers ...
#3. I've installed a ****load of apps onto it already
Is there an application that will allow me to monitor which applications are causing the instability, or do I just have to suck it up as the cost of running something that's beta/unstable/wrong network/wrong device ... ?
Click to expand...
Click to collapse
have you checked the back plate is secure? when i had random shut downs it was because the backplate wasnt in place correctly. that could be the reason your having random shutdowns? the backplate is a little temperamental
I'm 99% sure it's secure ... it's flush to the device and can't see that it could possibly slide any further up.
It just shut down while I was using it ... hit the menu hard button in the XDA app ... reboot ... although this one was much faster restart.
p_razzi said:
It just shut down while I was using it ... hit the menu hard button in the XDA app ... reboot ... although this one was much faster restart.
Click to expand...
Click to collapse
hmmm, how odd. i dont think there is a app that will allow you to diagnose the problem. the best way would be to factory reset then reinstall one by one each app and try to find one which may be the problem
I've disabled the live wallpaper - will see how that works.
Sent from my Dell Streak using XDA App
Power it up let it sit and dont run anything. Pick it up and drop it back in your hand then tap on the back plate. If it powers off then either the cover is loose or like me i actually had to mess with the two tabs on the back that senses thae cover is on. It was easy fix but took a bit to find. Thought I had a lemon for sure. I am not sure why they care if the back is on or not but it drops the unit without warning. Your problem sounds similiar to mine.
I think you guys could well be right. Last night I picked it up and dropped it about an inch onto the table and it rebooted.
So far today it seems to be behaving after I really pushed the back plate for all I was worth!
A bit of a design flaw to have it quite that sensitive I think.
Sent from my Dell Streak using XDA App
p_razzi said:
I think you guys could well be right. Last night I picked it up and dropped it about an inch onto the table and it rebooted.
So far today it seems to be behaving after I really pushed the back plate for all I was worth!
A bit of a design flaw to have it quite that sensitive I think.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
You also need to remember that 2.1 is currently in Beta and is pretty buggy, that could also be causing the reboots
I'm on the 2.1 beta also, so expect the odd bug. Mine rebooted this morning after I dismissed the night clock after it had been running fine all night and the alarm woke me up fine.
Random rebooting is something I hope is fixed in final release
The back plate does become easier to fit after a bit, the first time I fitted mine I thought I was going to break something.
Not seen any random reboots on 2.1 (or none that I remember),4399 was much more prone to it.
Since giving the back cover a major push, the reboots have stopped. Kudos to flumps and martywix.
Loving this device ... why did it take me so long to discover Android?
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.
I am running the CM7 with the newest OTB kernal, and I am still getting the keyboard randomly popping up, the back key randomly will work 2 or 3 times in a row. I had the same problem on EF 3.6, com rom and even on the SC roms. Has anyone else had these random key strokes? I heard it was a froyo related issue? Is it hardware related? I had a screen protector that covered the soft keys and removed it, but it is still happening. Any thoughts on how to get rid of it?
FWIW I have odined back to stock, with the atlas pit and even used the ext4 reformatter before I switched to EF3.6.
Any help, advice or thoughts would be great.
I encounter the same issue but it always seems to happen when on the edge of losing cell signal. When going back n forth quickly from service to no service the capacitive buttons (I believe that's what they are called) seem to push themselves. And I have noticed this issue since DJ05 on any rom I have flashed since then and any kernal. I have run just about every rom posted except for miui and cm7. I can not confirm if cm7 has this issue because it is on my other fascinate and not on the cell network. I have terrible signal in the building at work and I have always seen this happen there, at least once a day.
You know am pretty sure I replied to this question before. I guess no one else has really has this issue and the thread died.
Also didn't matter which radio verison I used. I have come to terms that my fassy is just possessed lol
Sent from my SCH-I500 using XDA App
apparently you and I are the only ones that it happens to. I was hoping someone could give me some insight on how to at least find some relevance to a rogue program, bad kernal/rom combo or something. It's very strange and it does it to me more than once a day, and I have good signal most of the time.
Happens to me all the time when I'm at home where I have terrible signal.
I just started having this happen on CM7. The keyboard or the menu would randomly pop up. For me it happened more than just when I had bad signal, but it did seem to happen more often when I had poor signal.
I have this problem too, it would back out of apps I am in too. Quite annoying.
I've been having this problem as well on CommRom 2.1. Seems to be related to poor signal for me. It's pretty annoying to deal with.
Happens on a stock device also
chasmanian said:
Happens on a stock device also
Click to expand...
Click to collapse
Um. No. Not in my experience. Its something that has been well known that is associated with weak/intermittent signal. Didn't start for me until Comm Rom and became more pronounced with CM7…
This happens to me too. Oddly though it only seems to happen during the night when it's plugged in and it doesn't happen all the time. Sometimes I will wake up in the mornings and my screen is on and the keyboard is up.
Do a search for phantom softkey presses. It's pretty common and is a hardware issue.
I as well have this happen. Mostly it happens in low signal area. Recent, my keys just stop working, until I got better signal, or sometimes I am forced to restart the phone.
I just went back to stock ED05 mainly because of this ultra annoying issue and I am completely devastated to find out that it's still #$*%ing happening.
I am so pissed too because I called VZ a week ago and they offered me the Charge replacement, but I couldn't make it to the corporate store until yesterday where I was informed they stopped the replacement policy that day and that I was SOL. Argh. So angry.
420fan said:
I am running the CM7 with the newest OTB kernal, and I am still getting the keyboard randomly popping up, the back key randomly will work 2 or 3 times in a row. I had the same problem on EF 3.6, com rom and even on the SC roms. Has anyone else had these random key strokes? I heard it was a froyo related issue? Is it hardware related? I had a screen protector that covered the soft keys and removed it, but it is still happening. Any thoughts on how to get rid of it?
FWIW I have odined back to stock, with the atlas pit and even used the ext4 reformatter before I switched to EF3.6.
Any help, advice or thoughts would be great.
Click to expand...
Click to collapse
I commented on this a while ago in the CM7 thread. I have it on stock ed04.
What I wanted to know was if you guys have a screen protector on yours or not.
I wondered if my Zagg Invisible Shield was what was "pressing" the capacitive buttons.
Sent from my SCH-I500 using XDA App
lane32x said:
I commented on this a while ago in the CM7 thread. I have it on stock ed04.
What I wanted to know was if you guys have a screen protector on yours or not.
I wondered if my Zagg Invisible Shield was what was "pressing" the capacitive buttons.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You have a shield on gorilla glass???
Sent from my SCH-I500 using XDA App
tyler1234567 said:
You have a shield on gorilla glass???
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Verizon makes a metric **** ton selling screen protectors to those spending $200+ on a smartphone that doesn't need it.
jamesnmandy said:
Um. No. Not in my experience. Its something that has been well known that is associated with weak/intermittent signal. Didn't start for me until Comm Rom and became more pronounced with CM7…
Click to expand...
Click to collapse
Well, just to back this guy up. I had it happen back before and during the time I rooted my phone, and it still happen after I returned to stock (via Factory reset and OTA updates).
EDIT: To the guy who asked about the screen protector, I did have a ZAGG on there, then took off only the section covering the softkeys. Still did it even after I made sure to fully clean it to eliminate any residue. Took the protector fully off, same full cleaning, and it seemed to have gotten worse (if thats possible lol).
I'm about to call tech support, but wonder if it's worth it now that the good trade-in is over.
ElStormChaser said:
Well, just to back this guy up. I had it happen back before and during the time I rooted my phone, and it still happen after I returned to stock (via Factory reset and OTA updates).
EDIT: To the guy who asked about the screen protector, I did have a ZAGG on there, then took off only the section covering the softkeys. Still did it even after I made sure to fully clean it to eliminate any residue. Took the protector fully off, same full cleaning, and it seemed to have gotten worse (if thats possible lol).
I'm about to call tech support, but wonder if it's worth it now that the good trade-in is over.
Click to expand...
Click to collapse
yeah im sure it happens but its fairly rare on a stock phone i would say....
I have it happen semi-regularly. I'm currently on MIUI 1.7.22 / Glich 11.1 / ED05 radio, and never used a screen protector. I also had it happen back before when I was on Super Clean 2.9.2 (don't recall the radio), as well as most any other ROM I've been on.
It's not too uncommon that I would hit the power button to turn off the screen when back on SC2.9.2 and instead it would take a screen shot, because it assumed the back button was being held down!
Gotta love the Fascinate...
jpricesd said:
This happens to me too. Oddly though it only seems to happen during the night when it's plugged in and it doesn't happen all the time. Sometimes I will wake up in the mornings and my screen is on and the keyboard is up.
Click to expand...
Click to collapse
Yup, I got the same issues! Although minor, these things just shouldn't be happening? There's gotta be a fix for this?!?!?!
so my screen started with this crazy thing. theres a dead line on top of the screen. and touchscreen litteraly goes crazy. opens and closes apps, zooms in and out, swipes. this stops when i turn the screen of and back on, temporarely.
the phone has never been dropped or damaged in any way. just started randomly. i've tried 4.4.2, 4.2.2, custom roms, franco kernel,
flashing stock rom via fastboot fixes it,.
dead line desapears, everything goes back to normal. but when i leave it over night charging. the problem revives. i've seen this problem in youtube and google forum.. with the same deadline on the upper screen..
I Made a touchscreen text and everythiing is fine. but when the deadline appears fails
HELP!
My gf is having the exact same problem with her phone at the moment. I'm guessing that the digitizer needs to be replaced...but any other thoughts are certainly welcome.
Sent from my Nexus 4 using xda app-developers app
Xenoism said:
My gf is having the exact same problem with her phone at the moment. I'm guessing that the digitizer needs to be replaced...but any other thoughts are certainly welcome.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I also disconnected battery.. no fix. right now theres no deadline. i think it could be the battery. like when you plug in with wrong charger and phone goes crazy.
right now theres no deadline. works perfectly no deadline. low battery tho:crying::crying:
Could be a grounding issue. When I use chargers that aren't probably made I'll have that problem. Try using another wall charger and another wall socket.
Well, mine it's definitely the screen. I enabled screen touches in developer options and there is a dead rectangular area across the top of the screen that doesn't register most touches...and occasionally sporadic ghost touches start erratically pressing this area not allowing me to touch elsewhere. I'll likely have to start looking at repair options.
Sent from my Nexus 4 using xda app-developers app
Xenoism said:
Well, mine it's definitely the screen. I enabled screen touches in developer options and there is a dead rectangular area across the top of the screen that doesn't register most touches...and occasionally sporadic ghost touches start erratically pressing this area not allowing me to touch elsewhere. I'll likely have to start looking at repair options.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
i definitly lowered the frequency of the issue charging mi cellphone with the PC. the deadline is gone. sometimes returns. no more crazy touches. they sometimes come back too. im thinkin this could be battery grounding issue. ill try replacing the battery!
Happens me with g2 charger
Sent from my Nexus 4 using XDA Premium 4 mobile app
Xenoism said:
Well, mine it's definitely the screen. I enabled screen touches in developer options and there is a dead rectangular area across the top of the screen that doesn't register most touches...and occasionally sporadic ghost touches start erratically pressing this area not allowing me to touch elsewhere. I'll likely have to start looking at repair options.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
mine has the same issue. rectangular deadline on top of the screen. comes and goes. with developers options detects. but when it comes back doesnt. and sometimes the whole screen is unresponsive till i power of screen.
juanca_m21 said:
mine has the same issue. rectangular deadline on top of the screen. comes and goes. with developers options detects. but when it comes back doesnt. and sometimes the whole screen is unresponsive till i power of screen.
Click to expand...
Click to collapse
happened to me with my previous phone lg optimus black and kind of happened with my nexus. in the previous phone i had a lot of ghost touch. they started happening one every phew days and after six month i had ghost touches every single day rendering the phone almost unusable. got it for guarantee and they changed the touch screen. the problem started again on the new digitizer with some sporadic ghost touches, on the same day! after that i bought nexus. after a while i saw ghost touches too but it's rare. for me the ghost touches happened when i was playing a game called tubing and with time happened every where. tubing is a game where a lot of quick touches is required. now that i stopped playing that game everything seems fine
a friend of mine had this problem some time ago with htc hd2. the service told him that this kind of touch technology has problems in warm weather(i live in cyprus and in the summer it gets up to 42 43 degree celcious) .
ttheodorou said:
happened to me with my previous phone lg optimus black and kind of happened with my nexus. in the previous phone i had a lot of ghost touch. they started happening one every phew days and after six month i had ghost touches every single day rendering the phone almost unusable. got it for guarantee and they changed the touch screen. the problem started again on the new digitizer with some sporadic ghost touches, on the same day! after that i bought nexus. after a while i saw ghost touches too but it's rare. for me the ghost touches happened when i was playing a game called tubing and with time happened every where. tubing is a game where a lot of quick touches is required. now that i stopped playing that game everything seems fine
a friend of mine had this problem some time ago with htc hd2. the service told him that this kind of touch technology has problems in warm weather(i live in cyprus and in the summer it gets up to 42 43 degree celcious) .
Click to expand...
Click to collapse
Of topic: why'd you spell few with a pH? Phew
Sent from my Nexus 4 using Tapatalk
dethrat said:
Of topic: why'd you spell few with a pH? Phew
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
typo. i don't write english as often as i used to.
ttheodorou said:
typo. i don't write english as often as i used to.
Click to expand...
Click to collapse
Ah right just thought it was a strange spelling error
Since phew means something totally different.
Sent from my Nexus 4 using Tapatalk
i only had this issue when i charged the phone with a cheap Chinese charger, it would go crazy till i rebooted, as above grounding issues,
but op said it was gone with stock rom, so its not a hardware issue, tried charging via other means
republicano said:
i only had this issue when i charged the phone with a cheap Chinese charger, it would go crazy till i rebooted, as above grounding issues,
but op said it was gone with stock rom, so its not a hardware issue, tried charging via other means
Click to expand...
Click to collapse
THIS seems to be a grounding issue. after charging it comes back. but after a while without charging comes back.. no fix yet! i hate how google doesnt give support about this. theres a ton of people with this issue
I have this same issue, was wondering if anyone found a fix yet?
I have lost all touch sensitivity in the down part basically I can't use the Nav bars and also above the nav bars sometimes its very hard to press on things check out my video I have it here in the last part http://www.youtube.com/watch?v=eDDOSyLLnGs&feature=gp-n-y
nexus 4 ghost touches and dead screen.
Believe it out not, the crazy ghost touch and dead screen areas are NOT the screen. It is the battery. It sounds crazy, but it is true. The bad party is, nexus 4 batteries are old. Buying a new one won't necessarily solve the problem. I would buy the brand name this party battery.I have had bad new oem batteries die to their age.
Hello guys ley me join this party of ghost
As my device is also doing same weird thing like unnecessary touch without my feedback in most of third party app, setting app and in play store it goes crazy and start clicking on any option available without my touch
But the thing which is making me frustrate that this happens only on custom kernel as I tried all with stock google factory image 5.1 and this problem arise just a few days back and I was on custom ROM with custom kernel before 5.1 update everything was fine but after 5.1 update I mean custom 5.1 ROM with custom kernel this problem arises now if I m going back to 5.0.2 custom ROM with custom kernel my device become crazy and just start clicking any option in setting app I m totally stuck with Google factory image and stock kernel
Please guys if any one has pepper solution for this ghostly touch help me so that I can enjoy custom ROM and kernel :crying:
Mouse BlueTooth (without adapter)
I found the cheapest possible solution, as the replacement digitizer is not profitable.
I bought a mouse BlueTooth (without adapter) without problems and now I can move the cursor around the screen over the entire surface.
N4 is not for me everyday device.
In my case, I bought a mouse i-Tec Bluetouch 243.
Hello,
This is my first post in this part of XDA.
My wife has an s7 Edge and the screen started flickering. I got out of this state messing with the power buttons etc. Mainly getting the touch screen to unlock the phone and it somehow cleared right up.
Is this a software issue? The screen when it came back is working as usual when I restarted the phone it became crap again.
Im think it maybe the lock screen causing this, I never heard of parts being corrupted.
I've attached a little clip of the screen.
Thoughts?
Thanks in advance!
https://youtu.be/gFSTlcDWGQY
I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.
k1ska said:
I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.
Click to expand...
Click to collapse
Forgot to mention, it's not rooted completely stock.
So screen is messed up?
I had this issue. My phone fell from less than a foot off the ground and landed on the corner. Barely any force, but after that the screen would flicker intermittently. For a day or two it would come and go, and then it became permanent. It looked exactly like yours. If your bootloader/recovery/download mode flickers then it is a hardware problem, since the ROM isn't even loaded yet. With Verizon, your phone is fully covered from manufacturing defects for one year, so you should be able to get it replaced. Sorry bro. Wish I had better news.
v1ral said:
Forgot to mention, it's not rooted completely stock.
So screen is messed up?
Click to expand...
Click to collapse
Honestly with a screen issue like that, I really recommend taking it to the Verizon store and asking them about it. It seems like a hardware issue to me but that's just my opinion.
My screen has done some weird things as well fresh out of the box. I would have random areas of the screen pixelize until I smack the back of the phone. Even after root It will randomly do it every other month. My father in law had the same exact issue you're having. He brought it into T-mobile where the screen literally failed and went black in the employees hand. Neither his or my phone has ever been dropped. This is definitely a hardware issue. It's almost like a bad connection between the LCD and main board. Make verizon get you a new one before the screen goes black!
Okay...
Is it okay to say I can get a new screen and do that repair myself?
I wanna make sure that the issue I am having is just "buy a new screen and be good to go".
Thanks for your time!