Database Users

[TEST] touch screen/calibration issues... may have figured some things out?

Ok, so over the course of time I have owned my phone I think I may have found one of the reasons for the phone to go out of calibration in terms of touch accuracy but I just want to make sure its not just my phone doing it.
What I have noticed is that if I hold my phone at an awkward angle for a few minutes (typically 5ish minutes) the calibration will go out of whack. This notoriously happens when I have my phone in navigation mode and just laying on my lap (landscape mode). Today I was driving and I got a text mid way to where I was going so I picked the phone up to hit the talk-to-text button (which is really nice for texting while driving by the way) and it was out of calibration, could not hit the button to save my life. Similar has happened when I held the phone at an awkward angle while watching a movie laying in bed. So I would like to see if anyone gets similar results holding the phone at an awkward angle for a few minutes, I would say give it 5-10 minutes for an accurate result. Try doing things like holding it literally upside down while its in landscape mode and then switching it back to portrait and type on the small keyboard again. I would go into a program of some sort that you can test touching all areas of the screen with.
Now, it seems like before the OTA update, I would have to reset the phone and sometimes that wouldnt work still. However now (and I have tested multiple times with consistent results) that if you lock the phone and then unlock it, the calibration seems to be adjusted again.
Let me know your results.
**For the record, I have had a very positive experience with this phone since I purchased it but I have been able to replicate the "touch screen issue" many a times and would just like to get to the bottom of the issue if all else to just avoid it or tell others how to avoid it happening to them because it is quite annoying.

it sounds like a software hiccup i would hope it would be getting patched sometime..... but as of now i dont know of anyone that's got a fix for it. i have the problem from time to time but i just lock and unlock and its fine, kind of annoying but not something that makes me want to throw it out the window or anything.

Judging from the behavior, I'll place my bets on it being a software issue rather than hardware. There seems to be some hiccups between the accelerometer and the screen getting confused about angles/tilting.

didnt happen to me before upgrade. Its happened a couple of times since.
My phone had been on charge and I had changed to setting to disable it from sleeping while on charge. I had turned the screen off but it must have woke up I went to use it and couldnt hit any keys.
I thought it may be something to do with it being awake for a long time - but it could be coincidence.
I can confirm that putting the phone to sleep and waking it fixes the problem

I have the same issue. No problem before OTA and described problem after that. Grrr.

Mmm, I experienced the problem both before and after the OTA, so I dunno.

Good to know that you can just sleep the phone and then wake it back up to fix the issue now. You used to have to reboot.
I have not had the issue at all since removing live wallpapers. Maybe just a coincidence.
Do people using custom ROMS have these issues?

Ok, so there are similar results out there then and sounds like 100% confirmed just locking and relocking recalibrates the phone back into proper order, no more full reboot is needed.
For the record, I am not using a live wall paper, I have not rooted or installed any themes or anything so my phone is all stock besides the OTA update. Also, as someone else stated that you used to have to restart your phone before the update and I experienced the same thing but again now I only have to lock and unlock the phone for it to recalibrate.
Grainysand you and I seem to have had similar "issues" if you even want to call them that with before and after the OTA and I share your view that there is an issue between the accelerometer and the software recognition.

It's definitely the accelerometer. For the record, I've never had to either reboot or relock/unlock the screen to fix this. I hold the phone upright and it corrects itself, though sometimes it recurs.

I've noticed this a few times after the ota, but just turned it off/on to fix.

galaxys said:
I've noticed this a few times after the ota, but just turned it off/on to fix.
Click to expand...
Click to collapse
Same here. Usually when in landscape mode and the device is tipped at a 45 degree angle. I've also seen the N1 (when using the browser in landscape) scroll the page back and forth very quickly (about 1/4"). When this happen the device seems to get 'stuck' in landscape mode even when I flip it back to portrait.

After the ERE27 update, I've only really noticed the issue when I've plugged in the charger.

Huey85 said:
After the ERE27 update, I've only really noticed the issue when I've plugged in the charger.
Click to expand...
Click to collapse
now that I think about it, I must say that most of the time I see this happening it has been on the charger... will test later though, i doubt this would effect the issue

I think it has something to do with live wallpapers, the ones that receive input touch to react in some way or another. Its a software issue.
You could put it to sleep and on wake up its ok.
Or you could touch the buttons slightly to the right.

htcmagic said:
I think it has something to do with live wallpapers, the ones that receive input touch to react in some way or another. Its a software issue.
You could put it to sleep and on wake up its ok.
Or you could touch the buttons slightly to the right.
Click to expand...
Click to collapse
no its not the live wall papers... I have tested both with and without live wall papers and I can produce identical results as far as loss of calibration

Not sure if its the same problem but when playing games sometimes, the isnput locks up sometimes when in landscape mode. However rotating the phone between landscape & portrait mode seems to fix the problem, might help for this too.

Huey85 said:
After the ERE27 update, I've only really noticed the issue when I've plugged in the charger.
Click to expand...
Click to collapse
same here.

cyanogen 5.0.5.3 touch screen

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.

Issues since updating my Bravo

I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.

roadkizzle said:
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
Click to expand...
Click to collapse
Something probably is messed up in the upgrade process.
Simple solution, flash the 2.2 sbf and you should be good.

roadkizzle, Something doesn't sound right at all with your update. I would try to remove the battery for a minute and reboot. If you still have issues I would try a factory data reset. If that doesn't cure your ills then flashing the 2.2sbf as bandroidx suggested may be in order.

Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?

roadkizzle said:
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
Click to expand...
Click to collapse
flashing the sbf already updated your phone to 2.2. You don't need to do anything else

I hope reflashing did the trick for you. That experience sounds nasty...
Sent from my MB520 using XDA App

Well, after a couple of hours of playing with my phone it's seeming better. I have been playing a few games of Worms, and my normal surfing the internet and so far I haven't noticed any real lag. The test will be my day through tomorrow.
I was just really confused because I was following the instructions from the Flashing SPRecovery SBF to a Motorola Droid youtube video, and his SBF file really seemed to only change the recovery screen. It looked like he still had to go through the actual update.zip process to make the actual updates to his phone.

Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.

roadkizzle, It sounds like you are still having issues. If you look at the system version in "about phone" in settings menu does it say version 37.4.0.MB520??

Yes, it says Version.37.4.0.MB520.ATT.en.US

roadkizzle said:
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
Click to expand...
Click to collapse
what apps do you have installed?

look in task master and get rid of any auto-ends and reboot and see if that makes a difference

Well, immediately after removing the AT&T apps from the auto-end list and rebooting, I thought I noticed some lag initially, but I've let it run for a few days now doing everything I was before and I've not been having any of those issues recently.
I'm not sure what it was. I wasn't very aggressive adding apps to my auto-end list, really just Maps and the AT&T apps. I added maps after a while because when I would use it once it would stay open and I'd notice later on that it would have been a major consumer of my battery, and I couldn't figure out how to close it fully.

Glad to hear things are going better. I had some issues totally unrelated to the apps I had in auto-end but pulling all of them off of auto-end got rid of the issues. Froyo is supposed to minimise the need for having to add apps to auto-end in task manager. Regards

(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.

humanque said:
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
Click to expand...
Click to collapse
Try taking things off of the auto-end list. You shouldn't need the task killer because android manages apps on its own (it's supposed to manage apps better in froyo than in 2.1)

I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not

kyngnothing said:
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
Click to expand...
Click to collapse
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
https://market.android.com/details?id=org.jraf.android.nolock

jorgonv said:
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
Click to expand...
Click to collapse
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
PS . If you can't get your screen to stop locking all the time with froyo 2.2.1dissable it in the same location ID # 61 screen_lock set to 0. ),
Click to expand...
Click to collapse
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out

kyngnothing said:
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
Click to expand...
Click to collapse
You can always sbf if you get locked out. your data will also be kept

[Q] Droid X Screen Problem - Hardware or Software?

The phone has been working very well, no problems of any kind. It is rooted and I'm using Go Launcher along with Widget Locker for the lock screen.
I just updated the Widget launcher application and everything was working just fine.
However, the last time I woke the phone, the display was bonkers. The lower 1/3 of the screen was grey, over writing the icons for the functions located there on the home screen. When I scroll through the home screens, the lower 1/3 continues to be greyed out. However on close inspection, the underlying icons can bee seen and are activated with a touch as normal.
The overwriting seems to be somewhat of a repeat of the top 1/3 of the screen. With the moto lock screen there is a digital clock displayed in the upper part of the screen and that is showing up in the lower third also.
This greying out is more like a Ghosting effect. The screen also has a general background flicker in the upper section that is not greyed out or ghosted over. I did nothing like dropping the phone or dunking it. This does have what I would somewhat characterize as connection issue. BWDIK.
Does anyone have any idea as to what could have caused this to pop up as a problem? The new version of Widget Locker seemed to be doing just fine and I had configured it to take more icons in the ICS default theme. Everything was going great until it suddenly was not.
Suggestions or accounts of similar problems would be appreciated. I sure hope there is a cure. The phone has been great and darned capable. I'd hate to have to change it out.

Reboot your phone.
If that doesnt work, make a backup in Clockwork and wipe data.
If that doesn't work, it's hardware related.
Sent from my DROIDX using Tapatalk 2

Thanks for the help.
Could you be a little more specific as to how to make the backup and then restore?
I've restarted the phone several times. That won't clear it up.

Download droid2bootsrtap>install>flash recovery>reboot recovery
Scroll to backup/restore (use vol keys select w/ camera key)
Select backup, let it do it's thing
Select wipe data
Reboot

Thanks for the additional help.
That did not seem to get the job done for me. I still have the problem with the top third of the screen being displayed again as an overwrite of the bottom third.
One odd thing did occur while I was working on this. I had the phone connected to the charger. It was in "sleep" mode with a dark screen. I picked up the phone, pushed the wake up button top. and at the same time I disconnected from the charger. When the screen first displayed it was displaying correctly and clearly with no overwrite. I don't believe I have a failed display in the sense of dead sections or pixels. It seems that there is some cross connection in how it is being addressed so that the upper one third is being written twice, one of those being an overwrite of the lower one third. The icons that should be showing in the lower third dispaly are visible through the "fog" created by the overwrite.
I have contacted the local smartphone Mr. Fixit and ordered the new screen. The problem may be deeper than that though. Any other suggestions would be appreciated. I like the way the phone operates and am getting to understand it after about a year of working with it. It is rooted with the handy WiFi tether operating, along with a few simple customizations. It would be great to get it sorted out as I don't want to go the upgrade route at this time.

Have you tried reSBFing? I had a similar problem, except the lower 3/4 of screen went black. Got an insurance replacement, but when i was wiping my old phone, i SBFd, and the screen worked again. Granted, i still had to send the phone in, so no idea how long it would've lasted.
Sent from my DROIDX using xda premium

Nothing to do with SBF'ing. The phone is rooted, and it worked the first time, several months prior to the problem.
I finally got the screen replaced and that part is working well. Nice and bright with no ghosting of another section. However, I now have developed a problem with the dialer turning off the screen when the call starts dialing. No capability of using number pad or even hitting the End Call button. Returns to the default lockscreen when call ends from a disconnect on the other end. still a great mystery.

Question: how's your camera working?
Sent from my DROIDX using Tapatalk 2

[Q] Verizon G2 buggy touch screen?

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.