Database Users

(SOLVED) Serious screen problem, please help!

Looks like it was my generic charger causing all the problems all along...
Too high output (6.5VDC where it should be 5VDC)
Ordered a replacement, hoping for the best.
Thanks for all the help!
Sometimes my touchscreen is just perfect. Lately, it's driving me nuts!
When I hold my finger on the screen, the touch screen registers rapid multiple touches. Possibly as many as 10 per second.
This makes dragging and long-press actions almost impossible. Scrolling is very hard and typing is a PitA.
The problem goes away at times but keeps returning. I'm not sure if I had it before the recent update.
At first, it seemed like rebooting helped but today it proved useless.
Anybody, please help!!!!
(phone was used and has no warranty coverage )

dfan said:
Sometimes my touchscreen is just perfect. Lately, it's driving me nuts!
When I hold my finger on the screen, the touch screen registers rapid multiple touches. Possibly as many as 10 per second.
This makes dragging and long-press actions almost impossible. Scrolling is very hard and typing is a PitA.
The problem goes away at times but keeps returning. I'm not sure if I had it before the recent update.
At first, it seemed like rebooting helped but today it proved useless.
Anybody, please help!!!!
(phone was used and has no warranty coverage )
Click to expand...
Click to collapse
Do you have a screen protector on the screen? Sometimes the cheaper ones are too thick and the screen doesn't register touch like it should.

Talonnb said:
Do you have a screen protector on the screen? Sometimes the cheaper ones are too thick and the screen doesn't register touch like it should.
Click to expand...
Click to collapse
Just the one that came on the phone.
Like I said, the phone works beautifully some of the time but registers multiple contacts other times.
I suspect software but it seems I'm the only person with the problem...

do you have a warranty.... sounds like a hardware fault to me.... the only way you can prove it's software (or not).. is to do a factory data reset and then run it with the standard basic build for a few days.. see if you still have problems when you don't have any other apps on the phone.

Do you have wet fingers when you experiment this behaviors?

Happens to me too. I figure its due to gunk on the screen like water, sweat your gf's makeup (a major one)
Sent from my X10a using XDA App

This happens to me too.
Only started happening since the last update so I just assumed it was a bug in the new firmware. It's like the phone lags and then catches up with itself, very annoying.

bushbox browser said:
This happens to me too.
Only started happening since the last update so I just assumed it was a bug in the new firmware. It's like the phone lags and then catches up with itself, very annoying.
Click to expand...
Click to collapse
I think it is since the update. I'd better reset the phone using SEUS and see what happens.
@ everybody, believe me, I have had the problem through a variety of circumstances and no problem with sweaty fingers etc. It seems pretty random!
I don't have a warranty so re-install here I come!

I would definetly try the factory reset first. I have had similiar issues but its only been while typing quickly. It lags a bit and then it all shows up on the screen plus a few extras of whatever the last character I typed was.
I did read somewhere, can't remember exactly where, that because our screens are capacitive they can malfunction. What I mean is this:
"Surface Capacitive touch panels: a layer that can store an electrical charge is created on the glass panel. When a user touches the monitor with his or her ungloved finger, a portion of the charge is transferred to the grounded user reducing the charge on the capacitive layer. The controller calculates, from the differences in charge at each corner and determines where the touch occurred."
Sooooo if say the ground for the screen is damaged then it will not register your touch appropriately. Hopefully it just requires a reset, cause the latter I think would be a tougher fix.
Let us know

dfan, is it happen only when you charge your phone? What charger are you use? Original?

I did a restore but no change, issue still there, it doesn't happen often though.
Dose seem like a bug and it never happened to me before the last update.
Also it happens to me when not charging.
Sent from my X10i using XDA App

very bad.. you cannot drink a cold coke and use the phone. I think that it is a hardware related problem. I was trying to reproduce the same with N1 and Legend (with my fingers flooded) without problems. So.. guys with hyperdrosis keep away from this phone!

No it's not a hardware problem as it only started happening with the last update.
Remember the x10 uses different software to nexus one or desire so can't compare with them.
I believe it's the software lagging, this update is faster overall but just lags occasionally, maybe the next software update will fix it, and if not the 2.1 update should definitely fix the issue.
Sent from my X10i using XDA App

bushbox browser said:
No it's not a hardware problem as it only started happening with the last update.
Remember the x10 uses different software to nexus one or desire so can't compare with them.
I believe it's the software lagging, this update is faster overall but just lags occasionally, maybe the next software update will fix it, and if not the 2.1 update should definitely fix the issue.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Are you pretty sure?

Tested... it is present on old roms

Well the old roms were laggy as hell anyway. It seems like classic software lag so I still think it's software.
Maybe when 2.1 is released we will find out, or even better when we get stock android running though root, that would clear it up once and for all.
My iPhone 3g also suffered from similar lag issues.
Sent from my X10i using XDA App

brunswick000 said:
I would definetly try the factory reset first. I have had similiar issues but its only been while typing quickly. It lags a bit and then it all shows up on the screen plus a few extras of whatever the last character I typed was.
...
Sooooo if say the ground for the screen is damaged then it will not register your touch appropriately. Hopefully it just requires a reset, cause the latter I think would be a tougher fix.
Let us know
Click to expand...
Click to collapse
Hells yeah I don't want a defective screen or this thing is done!
regarding your first comment, this is not lag. It is like I had a turbo button. If I touch for more than 1/15 sec, I get 2, 3 or 4 letters.
instead of one long press, the screen continually registers new presses, no matter how firm my touch is.
Imagine how much fun it is drawing the unlock pattern when my phone's in a bad mood...

That dose sound different to the small lag I occasionally experience, very odd.
Sent from my X10i using XDA App

I've reinstalled the FW and it didn't fix it.
The other day I had 5 straight hours of rapid-fire screen during which I couldn't even unlock the phone.
Gonna have to send it in for repair. Anybody know how expensive S-E are for repairs? Is it even worth doing?

I have narrowed the suspects down to my generic charger.
The charger I bought outputs over 5V (claims 6.5V) which seems to be the problem since I don't experience the issue when charging from a USB port.
New charger ordered, fingers crossed.
Thanks for all the suggestions!

[Q] Cold Outside - Screen Doesn't Work Properly

My HD2 has been awesome so far, but it recently got a little bit chilly outside, and I live in Ottawa in Canada, so this is a pretty pressing concern. When the phone is being used outside, it seems like the cold weather causes the screen to go a little bit wonky.
When i'm texting, sometimes it won't register my fingers pressing the screen, or it will think that im HOLDING down the button. This wouldn't be a big deal if I didn't live in Canada and winter is coming, but it is and I do. Any help or knowledge in the matter would really be appreciated.
I bought the phone off of Ebay so i'm not sure if it has any sort of warranty on it, Is there any way of telling what revision of screen the phone has? Can i buy a new LCD/Digitizer/whatever on Ebay to fix the problem?
P.S. I searched for cold and screen and LCD but i couldn't find anything relevant to my question. If I missed something, sorry!

Heres a couple things you can try- If you have a screen protector on the phone, remove it and replace it with a new one. I have found that even with a good fitting screen protector, dirt and such can still get under it and cause mispresses. Not relevant to the cold I know, but still something to try. Now, does the device work well under room tempreature conditions? Third, to see what revision you have, check these out: Is your device T-Mobile branded? Under your battery cover, what color is your reset button-yellow or red?

It is tmous with a yellow reset button. It works great inside at room temps. Something to mention is that it does this in Android, not sure if it does in winmo cause I only thought to compare today, but its pretty warm today. HTC said that its still.covered by warranty but is one rather not send it in as is have to pay shipping etc.

hereric said:
It is tmous with a yellow reset button. It works great inside at room temps. Something to mention is that it does this in Android, not sure if it does in winmo cause I only thought to compare today, but its pretty warm today. HTC said that its still.covered by warranty but is one rather not send it in as is have to pay shipping etc.
Click to expand...
Click to collapse
Oooh. In android. Your not alone. This happened to my first hd2 with android. I get off the train after a 3 day ride to seattle, then Bam! freaky screen. It froze and usually when the screen turns off, its back. Well, after 20 minutes i hit the reset. The screen never unfroze and i got tmobile to send me a new one. Now i get the new one. Outside? Same thing! I use bangsters with the evo kernel and it does it a LOT less vs. default kernel. If i use gps with the default bangsters kernal, its frozen. period.
Try a different kernel, different build, new radio (?), or even a new windows mobile build.
I am fairly certain, sending it in won't do any good. Your going to be without a phone for a week or more and when you do get it back, same issue. If you know your going to be outside all day and need a working phone, stay in windows mobile. I will bet my life that win mobile will work flawlessly.

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.

HD2 killed itself

So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
to not confuse anyone it poped again which then made the device inoperable, forgot to mention that *hits head*

flynney said:
So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
Click to expand...
Click to collapse
suicide !! domestic violence !!

its the HTC auto destruct sequence. It has detected that you have enough money saved up for a new phone, has reported this fact to HTC and they have sent the kill signal. You should start recieving phone ad emails from them any time soon.

lol I would never hurt my beloved HD2 i love it too much.
and im broke i dont have enough money for a cup of tea now days lol

bbbbbbbbbbbbbbbbbibibibi
bobobobobobobobobo
get a job
Whilst at it, get a new or 2nd hand hd2

flynney said:
So this morning was casually playing bubble jump on WP7 and all of the sudden backlight went off on lcd and the camera flash started going rampant.
hardware buttons wont work and a distinct sizzling sound and a giant pop then came from it before it became completely inoperable.
i left it for a day and the screen turns on but no light and the battery is still amazingly working.
any ideas what the problem might be, I've sent it back now just curios on people's thoughts.
Click to expand...
Click to collapse
Maybe you were pushing the GPU aspect of the Snapdragon SOC too much.

i haven't a clue didnt think bubble jump was a demanding game, and i have a job, but ive used all my money on car insurance lol

If you can get to the bootloader (even if you can not see the screen) task 29 and reflash original Win 6.5 ROM. By doing that you can eliminate software and, if you have warranty or insurance, exercise that.
I could not possibly suggest that now is a time to get insurance and, having waited a significant time period, drop the HD2 from a great height.
Sent from my HTC HD2 using XDA Premium App

hey, couldn't boot in to spl due to the pop, i think that ultimately killed the whole system as non of my spare batteries work nor does the charger, the insurance i have on it accepted it fine and have told me i should expect a replacement in about a week.

I am very pleased that you have insurance then and will not be without your beloved HD2.
If no charge is a secondary problem then an interesting test was whether or not you could access the bootloader whilst external power is applied - in this Maglr world I believe that you can trickle charge through that method. You probably did that which I think confirmed a major hardware problem (check battery terminal pins though).
I hope it arrives quickly for you.
Sent from my HTC HD2 using XDA Premium App

well from what i could tell the pins were all still in tact and before the pop, the charger worked on it. seemed very odd why it would just do that, but I'm no electrician. thanks for the replys guys =)

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