So, I have the AT&T Lg G2 D800 running custom recovery and stock rooted KitKat.
Today, I woke up used my phone for a bit, then laid it on my bed.
Came back, and the phone was doing crazy stuff. Was moving on it's own, pushing random buttons and going crazy
Thought it was the software, booted into recovery and it was pressing buttons on that as well.
It stopped maybe 20 minutes later, but now I have dead spots on my touchscreen.
I used quick memo and can't draw a straight line across certain points, nor does my knock on feature work correct anymore. (but knock off does).
I can't click certain buttons on webpage, and even in the playstore I can't click install.
Any suggestions?
Tried recalibrating the motion sensor, and even went into the hidden settings menu and tried fixing the screen that way too.
Suggestions?
Thanks.
brswattt said:
So, I have the AT&T Lg G2 D800 running custom recovery and stock rooted KitKat.
Today, I woke up used my phone for a bit, then laid it on my bed.
Came back, and the phone was doing crazy stuff. Was moving on it's own, pushing random buttons and going crazy
Thought it was the software, booted into recovery and it was pressing buttons on that as well.
It stopped maybe 20 minutes later, but now I have dead spots on my touchscreen.
I used quick memo and can't draw a straight line across certain points, nor does my knock on feature work correct anymore. (but knock off does).
I can't click certain buttons on webpage, and even in the playstore I can't click install.
Any suggestions?
Tried recalibrating the motion sensor, and even went into the hidden settings menu and tried fixing the screen that way too.
Suggestions?
Thanks.
Click to expand...
Click to collapse
from the hidden menu have you tried the settings>upgrade touch firmware option
XxZombiePikachu said:
from the hidden menu have you tried the settings>upgrade touch firmware option
Click to expand...
Click to collapse
Yes, I have.
brswattt said:
Yes, I have.
Click to expand...
Click to collapse
then problem may be the dead spots, I've notice that anyone that has had at least one dead spot appear on their g2 have lost the ability to knock on, the only reason they don't lose knock off ability is because that is a feature of lg launcher unlike knock on which is hardware and kernel
Related
So, I installed a bunch of programs last night, and installed updated versions of a bunch of already installed programs. Shortly after, my phone battery went dead, and when I turned the phone back on, the touchscreen is just insane, way too sensitive. I can't do long touches, no matter how still I hold my finger, it registers as a regular touch. I can't pull down the notification area, can't close folders I've got on the home screen. I can navigate fairly well using the track ball, but it's definitely an exercise in alternative thinking after using the touch screen almost exclusively for the past 2 months.
So, my question is this. Where is the touchscreen sensitivity setting, what config file, and what is the default, ie what is YOURS set to? Thanks!
I don't think there are config files. I believe it is database stored and no one has yet posted information on how to use it for the average user.
I think maybe this isn't a software issue but that maybe something happened to the screen... maybe you turned it on while touching the screen and like many past game/computer systems it recalibrated at startup.
heldc said:
So, I installed a bunch of programs last night, and installed updated versions of a bunch of already installed programs. Shortly after, my phone battery went dead, and when I turned the phone back on, the touchscreen is just insane, way too sensitive. I can't do long touches, no matter how still I hold my finger, it registers as a regular touch. I can't pull down the notification area, can't close folders I've got on the home screen. I can navigate fairly well using the track ball, but it's definitely an exercise in alternative thinking after using the touch screen almost exclusively for the past 2 months.
So, my question is this. Where is the touchscreen sensitivity setting, what config file, and what is the default, ie what is YOURS set to? Thanks!
Click to expand...
Click to collapse
I am having the same problem! What is worse when I text using the screen, it types the letter three times even with the lightest touch! Any updates on this?
I really like to keep this phone!
I believe adjusting the sensitivity will mean adjusting the kernel
is it normal that my touchscreen goes nuts sometimes? I find that sometimes (usually at night or first thing in the morning) my touchscreen on my n1 is inaccurate. I'll touch in the middle of the screen and it will click on something on the bottom of the screen. if I reboot my phone, the phone works great again.
yes its normal, its been posted here that even stock rom will get that problem now and then. Although mine has been random, not at a certain time.
Google is working on a software fix for it, and cyanogen 5053 (for my experience) has cut that problem to a minimum. I think ive experienced that problem 2 times since flashing. So a span of 3 weeks it happend twice. So i say its been pretty good.
And you dont need to reboot, just turn off the screen and turn it back on. Last i had a problem, i did that and it worked.
So as soon google fixes it im sure this board will be flooded with threads about it. And the devs are fast enough to implement it to their ROMS!
Are you holding it differently at those times? You mentioned at night or in the morning. Are you still in bed? I find I sometimes grip the phone is a way that my hand touches the edges of the screen. That throws off the touches and I've noticed it jumping down to a different icon at times. Just make sure your hand doesn't wrap around to the front of the screen.
My nexus one touchscreen will go nuts at times too. Locking the phone and unlocking does fix it though. I'm also 100% positive it has nothing to do with erroneous input from the way I'm holding it.
ya I was making sure that I wasn't holding it weird. hopefully Google makes a fix : )
p.s. thanks for the tip on turning off the screen rather than rebooting the device.
mine does this too but it seems that if I just put it to sleep and wipe it off it's back to normal
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Mine too does this w/ cyanogen 5053. sometimes it's so bad that i cannot even unlock the phone. I never noticed it this bad before on stock... but then again i only used stock for about two weeks before i rooted it.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I'm on a non modded phone and I get it every once in a while. Hit the power button and all is well.
Hey guys, I seem to have a problem with my A4g.
Basically, once in a while, the screen starts to press on its own. Usually towards the middle of the screen, so if i go to text message, keys such as "F" and "S" get rapidly hit on their own! Turning off and on the screen helps fix it, but sometimes i need to restart the phone altogether.
Anyone else having this issue?
I'm on Gingerbread with Unlocked bootloader and rooted but this problem has been around since i got the phone.
we'll need to know a little bit of information on your phone.
are you running stock software? (for instance, i'm using Ninja Speed Freak 0.4.5 and Faux's custom OC kernel)
have you dropped your phone recently?
has your phone gotten any contact with water recently?
do you have any suspicious third party apps installed?
bigdog_nick said:
Basically, once in a while, the screen starts to press on its own. Usually towards the middle of the screen, so if i go to text message, keys such as "F" and "S" get rapidly hit on their own!
.
Click to expand...
Click to collapse
OMG! its like a spirited game!!!
Sometime it happens to me, the screen to become unresponsive..
And i turn of the screen and on and its gone.
The thing happened at you it happens only with raindrops.
And rarely FP sensor dont work, so i reboot..
Are you stock? Or on a custom rom probably ?
As i wrote in OP, i'm running on the AT&T Unlocked bootloader 2.3.4 found here:
http://forum.xda-developers.com/showthread.php?t=1182526
This problem isn't due to the rom, it happened to me before the update too.
Ive only dropped this phone once since May and it was on carpet.
have you tried doing a factory reset? quick google search brought this up for me, but i'm not having the problem so i can't test it out myself for ya =\
http://www.atrixforums.com/forum/motorola-atrix-general-discussion/889-screen-issues.html
That was the first method i tried 3-4 months ago with no luck.
I can't do that anymore because of the unlocked bootloader
Is anyone else having issues with the touch screen triggering at different places when touched, or randomly knocking off the phone when you're not even touching the phone? I turned off my knockon feature, but I would see my notification bar be highlighted without me touching it. Just wondering if i'm the only one with this problem.
No issues at all.
Sent from my VS980 4G using XDA Premium 4 mobile app
I just picked mine up yesterday and have not had any problems with it.
I've had since launch and For the first time today I had a glitch. Touched a link in the browser and it clicked a link 3 links down. Clicked back button and it went back.tried to click the link again and it clicked several links down. I exited the browser and restarted.Clicked the link and it worked perfectly. The only time I've had an (issue?) At all.the phone is practically perfect in every way to me. My favorites smart phone and I've been phone jumping since the HTC touch Windows mobile
Sent from my VS980 4G using Tapatalk 4
I have had issues when typing, some times the letter is entered in like 3 tines. I have also had some other very strange issues but I still love this phone!
Sent from my VS980 4G
dru06 said:
I have had issues when typing, some times the letter is entered in like 3 tines. I have also had some other very strange issues but I still love this phone!
Sent from my VS980 4G
Click to expand...
Click to collapse
this glitch is kinda what happened with mine, and i confirmed what it was doing
in swiftkey, you know how tehre's the option to change the long press delay? well i was holding down that little bar to drag it down, and i noticed while holding it inplace, the numbers were going crazy..it was going up/donw/up/down incredibly fast, instead of just staying stationary..i was like, wtf? so i went to dev options, turned on show touch points and the trace so i could see the axis, and i noticed it was freaking out. holding my finger in place, it was as if it was moving around like crazy.
so i did a factory reset and flashed the clean verizon rom scott posted, and it hasn't done it since. no idea wtf was going on. i realized it was messing up bc my typing became really bad, and it would enter things i didn't type.
Touch Screen has a mind of its own - bad digitizer??
I woke up today to find my screen on, showing the lock screen which I found odd. Now most of the time the screen has a mind of its own where basically its like an invisible finger is randomly touching the screen at a frantic place. This opens up apps, moves icons around, calls people if the phone app manages to get opened, etc. After struggling to override the "invisible finger" I've done a reboot from the power menu, powered off from the power menu and left it off for 10 minutes before turning off and held down the power and volume down button to reboot. None of these methods fixed the problem0
Please note I did accept the Verizon update but was good on it for a day prior to this issue. I have installed minimal 3rd party apps and can't attribute the problem to starting right after installing something. I do use the Ghost 100 wireless charger but have been using this from day 1 without issues so I don't think that'a problem either. The Verizon store sold me this charger and although its not listed as being compatible on Verizon's website I have a feeling that's cause the phone is so new. The charger is WPC certified. Being that this problem is intermittent (happens way more often than not) I think it may be a software issue and I'm about to do a hard factory reset. If that doesn't work then I'm convinced its a hardware issue and probably a bad digitizer. I've been very gentle with the phone - haven't dropped it, no moisture or water exposure, not rooted, etc. I'll report back if the factory reset works. Anyone else having the same or a similar issue?
Super buggy lockscreen!!!
prophecy408 said:
Is anyone else having issues with the touch screen triggering at different places when touched, or randomly knocking off the phone when you're not even touching the phone? I turned off my knockon feature, but I would see my notification bar be highlighted without me touching it. Just wondering if i'm the only one with this problem.
Click to expand...
Click to collapse
You're not alone! My G2 has been driving me crazy the last couple of days when trying to use the lockscreen. It'll spaz out and either skip a connection of display a whole different pattern than I drew. It will also shut off the screen and reset the "wrong password" counter. I love this phone but this is super aggravating!
Hard reset didn't help at all. I went to a Verizon store and they exchanged for a new one and determined I had a hardware failure.
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Same issue here. But I can't figure out if it was due to switching to ART or not.
We can wait others reply with this i hope someone will post a tip on this kind of problem.
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
kameleongt said:
I switched to art after installing apps and I'm ha ing this issue didn't really play with phone much until after switching to ART. Is anyone having this issue not on ART?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Yes this is happening to me running Dalvik.
Happened just now to me. It has happened a few times.
Sent from my SM-G900V using Tapatalk
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
Is it kind of bugged?
Lodaserves said:
Is it kind of bugged?
Click to expand...
Click to collapse
This is actually becoming quite an annoyance to me and happens very often. I'm still on Dalvik. Could this be caused by an app?
I feel like half the time I go to use my phone the screen doesn't turn on.
tehgyb said:
Had this a time or two. It's like the power button doesn't register or something. Yes I switched to art.
I have found though that if I hold power for a second it pretty much fixes itself without having to do anything crazy like yanking the battery or restarting the phone.
Imo: not a big deal, doesn't seem to happen a lot for me.
Sent from my SM-G900V using xda app-developers app
Click to expand...
Click to collapse
I'm having the same issue for the past two days; although, I am not switching between apps or anything (only trying to use the phone). No display, but get sound/vibration from buttons and LED lights from soft keys. Unfortunately, both times required me to yank the battery. My S5 is completely stock (not using ART) and have manually reinstalled my apps from old device. Any suggestions?
I am not experiencing this and I have switched to ART...
Lodaserves said:
I think your phone have a problem and others don't have this kind of problem.
Click to expand...
Click to collapse
I hope this isn't the case. Once again I experienced these EXACT same issues with my Galaxy Nexus running 4.4.2. I can't help but think it might be some app causing it since not everyone has it.
I am noticing this every once in a while. But it's mostly right after I shut the screen off after a large processed app or task, and then remember something I forgot to do and try and turn it back on and there is some lag bringing up the screen again.
Black screen when quickly pushing lock
Lodaserves said:
Try to ask the person where you bought it.
Click to expand...
Click to collapse
I was about to return my S5 to Verizon for this very reason. I haven't switched to art and have been having the screen go black on me, you can tell the phone is on because the physical buttons are lit. It seems to happen to me alot when I take the phone off the charger and hit the on button. I will hear the phone rebooting, but not see the boot animation. Thats when I do a battery pull. Holding the button doesn't do it. I also have had a few random reboots. Thats ok...I'm going to try every root method under the sun..gggrrrr..lol
I've started to try to uninstall apps to see if I can narrow down the issue. It still plagues me at least half the time I try to use my phone.
This is happening to me as well. Not as often. I'd say once a day, but I have to pull my battery to restart it. I did 2 factory resets and am now using a new google account as per verizons request and I added apps slowly. I have been fine until I put a second launcher on. I installed the GEL launcher but did not use it just to see if having multiple launchers could cause this glitch. Could it be this? Is everyone else using a different launcher? Also the only time I ever had it happen while messing with the phone was two times while working in light flow. Any one else connected to those two happenings? Trying to narrow down what could be causing this.
Running ART here, I'm not sure if I'm getting this problem, but I have realized some latency from pressing either the home or power button and the screen turning on. Not sure what causes that lag, but it's a good almost full second whereas my S4 would be instant
eagle132 said:
I'm having a bit of a weird issue with my new Verizon GS5.
Scenario: I am doing something such as reading a text, decide I'm done and lock the screen, and then a second or two later realize I forget to check something and hit the lock button again to turn it back on. Most of the time when I do this the physical buttons will light up but the screen will stay black, and a few seconds later the physical buttons will turn off. This will happen a few times until finally the screen turns on and I see the lock screen.
I had a similar issue with my Galaxy Nexus (rooted and running Kit Kat) phone prior to the GS5 and figured it was my old hardware- is this some Kit Kat bug?
Thanks for any input
Click to expand...
Click to collapse
I would assume this is NOT the physical hardware issue, but the software, I heard somewhere that Samsung version of KitKat 4.4.2 is quite buggy and glitchy.
Njzkrish said:
Same issue here. But I can't figure out if it was due to switching to ART or not.
Click to expand...
Click to collapse
I had the issue before and after switching to ART
Anyone have any further ideas yet? I'm not running ART bit I was able to have it happen again when I had Google experience launcher installed. Removed it and it hasn't happened for two days. I'm installing Google launcher again now to see if that was causing the issue.
Anyone else with further developments?