yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Olioaglio:
IMO it is definitely a hardware issue, maybe affected by excessive flashing/heat/etc but not due to software/roms.

Btw, my own HD2 also suffered from a total defective TS some months ago (phone was about 3 months old) and it happened without any flashing with stock WM6.5 out of the blue. No TS response whatever I did. Had to send it to HTC for warranty repair. Got it back repaired and it's working rocksolid since w/o any issues. ATM I am using Gauners HD-FI nand rom and also used some custom WM6.5 roms before. So....

Just my 2 cents here.

Cheers, Olioaglio
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
I am not suggesting it is not a hardware issue, but I can't seem to figure why it has happened in this manner.

Screen has been rock solid in the almost one year that I have had the phone.

Twice it has happened right after flashing mdj roms. Once was even via clockwork so there was no usb cable connected (and therefore the battery/heat issue via usb theory doesn't apply).

And then once I finally get it to work again, screen is rock solid again.

If anyone has any ideas or theories, I would love to hear them.

Thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] trill12:
Weirdly enough, that was the EXACT SAME ROM I flashed when the touchscreen started dying. I kid you not.
[HD2 Android Q&A, Help & Troubleshooting and Genera] archiesnet:
MDJ's build (i think) is already over-clocked. Many times i used his build, my phone heats up fast.I don't know but in my case.this is what i experience. So every time i think my phone is heating. I eventually stop using it and let it rest for a while.Abuse the phone=brick phone.

Is there a way or a tool (Coolant maybe) that we can use so that our phone wouldn't heat up fast? (Couldn't imagine a fan tied to my phone..Haha)
[HD2 Android Q&A, Help & Troubleshooting and Genera] s0nniez:
I had my touch screen/phone completely died on me after flashing a nand build. It was fine before nand came out (and i've been flashing for many months now). But, sent it back to tmobile and got a new one. Don't know what the problem was but I had the same issue with OP. Not blaming NAND or anything but yeah...
[HD2 Android Q&A, Help & Troubleshooting and Genera] hello00:
Maybe because you have many app's running on the background? I'm using his last rom 2.5 and I'm not experiencing any problems..
[HD2 Android Q&A, Help & Troubleshooting and Genera] hecatombercm:
no response touch screen

this may all be unrelated but last night I updated to magldr 1.13, and the latest version of copeNwaren Sd android. I (shamedly) fell to sleep after installing a couple of preffered aps and left the phone running and on charger, with wifi on. I have since its public release day run wp7 off NAND. When I woke the next morning the touchscreen is completely unresponsive in all OS's. I have insurance and warranty, and also 3rd party inland marine insurance that will cover it, so I'm not to worried. I just wanted to share since Ive seen some similarities in issues in this and other threads.
[HD2 Android Q&A, Help & Troubleshooting and Genera] daz1uk:
Odd......
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Well since I already opened the phone and voided my warranty, anyone have suggestions for how to fix this?
[HD2 Android Q&A, Help & Troubleshooting and Genera] cliffordconradsumner:
There may be a newer thread for this issue but I though I'd pipe in here.

I acquired an HD2 that was working perfectly and as soon as I wiped it and installed a nand rom with mag 1.13 the touch screen starting acting funny. Randomly unresponsive and registering touches to random places.

The problem was terrible, though it did make texting a hassle, so I was still using it until I dropped it and totally shattered the digitizer.

I just replaced it with a brand new one and task29'd re-installed everything latest Jellybean rom and the touch screen problems are back.

I'm not exactly sure what controls the touch screen as far as the software side is concerned, whether it be through some drivers in the OS or in the boot loader or whatever, but if there are specific memory location that those controlling drivers find themselves in regularly then maybe there's some wonky issue with some memory blocks or something. that's all really conjecture, but what is clear here is that there is some sort of software issue that people are dealing with that is affecting the touchscreens of some of the HD2's.

YES!! WE KNOW that the digitizer has been known to fail....there is obviously ANOTHER problem that we're dealing with as well.

If anyone has any clue where to start with fixing this for nand installs that would be great.

One user here think it has something to do with Magldr so I'm going to try clk though I'm not too excited about the ppp data issues.
[HD2 Android Q&A, Help & Troubleshooting and Genera] illgodson:
Its been so long now that NAND builds have been everyday users I'm pretty this died off because it clearly has no relation. I personally have flashed dozens of Hd2s, and on this forum i would imagine the number is in the thousands, and what 10 people have had this happen, pretty much leads to the conclusion nand installs have effect on the touchscreen, at least in the manner of causing issues.
[HD2 Android Q&A, Help & Troubleshooting and Genera] cliffordconradsumner:
Yeah...I see the argument. But the issues described in this thread and mine specifically lead me to believe something different.

I flashed cLK with no result (of course), I'm going to go back to WinMo 6.5 and see what happens.
[HD2 Android Q&A, Help & Troubleshooting and Genera] cliffordconradsumner:
Been running winmo 6.5 for a while now with no touch screen issues...

I'm going to run it for a while longer just to be sure and then switch to an SD build once I get myself a class 10 card and see how that works.

I'll post back with my findings...not that anyone cares :crying:
[HD2 Android Q&A, Help & Troubleshooting and Genera] illgodson:
I feel your pain lol, anytime our phones act up its frustrating. I'm just lending to the fact that thousands upon thousands of HD2s are running nand builds without any screen issues, would seem to not be directly related across the board. Have you tried any of the newer dual boot builds? I personally don't like the feel of the builds as I'm using an old SD card that doesn't perform very well but a lot of users report excellent day to day use and most devs are adding the option to their aroma installs. That might give you an option to run the latest JB builds without encountering your nand issue
[HD2 Android Q&A, Help & Troubleshooting and Genera] cliffordconradsumner:
That was going to be my next step, currently I just have a class 2 sd card so I'm going to purchase a class 10 and see how it is I suppose.

before doing that though I'm going to see if I can somehow get the GPS working in my vibrant first...if I can then I'm just going to stick with that.

As an update, I've been fiddling around with WinMo 6.5 for several days now with no touchscreen issues.

I'm going to switch back to android nand just for testing purposes.

Thanks again for the reply.
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
It happened right after flashing each time. Didn't even have a chance to reload any apps.
[HD2 Android Q&A, Help & Troubleshooting and Genera] trill12:
Hmm, multiple people having the same issues after flashing NAND builds...
[HD2 Android Q&A, Help & Troubleshooting and Genera] chrispaw:
This happened to me also, i even flashed back to 6.5. I have to play with the buttons to get my screen working. It is very sporadic. I've learned to deal with it as it is not that bad for me.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Olioaglio:
Luckily MDJ just released the 2.6 version of his rom :D

Maybe worth another try. :p

O.
[HD2 Android Q&A, Help & Troubleshooting and Genera] KrewsialNL:
I have the exact same issue.

When coming out of standby, somethimes the screen does not respond anymore. Happened after coming back from WP7 to Android.

Task29, original Stock HTC WinMO rom, but no go unfortunately..

Waiting for HTC now hoping they'll repair it :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] nedevg:
almost the same problem

Yeah, you're right, I had the same problem. Actually my screen started having home problems around Christmas and stopped responding at the day the first NAND was released. Knowing that I didn't even install it! But it should be Android NAND, what else. Luckily, HTC costumer service realised nothing and replaced my screen...:D
[HD2 Android Q&A, Help & Troubleshooting and Genera] Beefheart:
In that case why do you seem so ignorant on the cause of this issue you're having? It is a hardware issue that could have happened at any point. Your claim that flashing Android NAND builds is the sole cause is quite simply a falsehood.
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
In my particular case, it has happened two separate times immediately after flashing Nand Roms.

Now I have also flashed dozens of other times without issue. I also do not dispute that it is a hardware issue. But my screen has always eventually returned to normal. I have not had to send my phone for service.

Clearly, at least in my case, something is being triggered upon the flash of a new rom (not every time however) to cause the problem with the screen.

Both times it happened to me, it was MDJ 2.5 Rom. I see that 2.6 is now out and someone suggested trying it.

Not sure I want to risk it since everything is working perfectly right now but maybe I will try it this weekend and report back.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Dylan Wilson:
In agreement with hardware failing being a hardware issue, but what the hell do you guys do to your phones? I live in Florida and take my phone to the beach in the middle of July (~110F) and turn on slacker and surf the web with wifi because I know a place where someones beachouse has an unprotected router, all with that wonderful black silicone case on that retains similar heat properties of a lit match, and usually with my phone oc'd to ~1100 mhz, and it still runs like a dream

Also, running mdj 2.5 and previously ran mdj 2.4
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
My phone has run very hot in the past without issue just as you outline.

That is why this is so strange to me. Excessive heat is the only logical reason I can think of to explain my temporary screen issue but it has only occurred right after flashing. Never during routine heavy usage.

Very strange.
[HD2 Android Q&A, Help & Troubleshooting and Genera] trill12:
Really? Then why have multiple people had the exact same issues?

Youre so quick to call someone ignorant, but youre not looking at the facts.
[HD2 Android Q&A, Help & Troubleshooting and Genera] trill12:
So when do we label this as a problem? Seems at least 6 peoples in this thread alone have had similar issues, all with flashing NAND Android builds. I had a previous HD2 running SD builds and I never had 1 single issue.

Or will people continue chiming in with their grade-school namecalling and blaming it on other factors?
[HD2 Android Q&A, Help & Troubleshooting and Genera] dwhsieh:
Possible Software

I don't usually talk on the forum but after reading this. I really do think maybe some software can affect the phone and maybe cause certain hardware to fail either maybe for a short time or needing a complete factory sent in. I have had many htc phones over the years and have flash numerous roms onto different ones. From my experiences in doing so, some versions of rom do run hotter or drain the battery faster than other. It is a hardware problem but there is nothing that say that some software can't push the phone into certain error looping or pass its limit and cause the phone to heat up and thus destorying the hardware. Personally, I don't know why anyone would argue about this single minded as anything is possible in most cases when dealing with flashing a rom not initially set up for the phone that it was originally intended for. The software possibility seems even more likely since there are several people that seems to be having the same problem after flashing a certain rom built. At least one would have to rethink their belief after hearing that more than one person is having the same problem, wouldn't they?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Mik0:
HD2 is known for digitizer failures *well* before NAND release. Other HTC devices have been plagued with this issue as well. Mine failed on me during Android SD usage.
[HD2 Android Q&A, Help & Troubleshooting and Genera] archiesnet:
Nope..Only Playing Angry Bird (Not Plugged). And this happens everytime i play games on my phone for like 30 minutes.And i'm not having problem when i'm Flashing..Only having this problem everytime i play a game.And again, not plugged.

And guys..No need to argue..This thread is meant for discussing..Thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
Update

I totally agree with you.

I was the one that had total screen freezes recently on two totally separate occasions immediately after flashing MDJ's 2.5 NAND Rom.

In both cases, after much reflashing of several different roms and other things, I eventually had my screen working perfectly again (no need for service).

Last night I decided to try MDJ 2.6 NAND Rom and everything went as expected. Screen is working perfectly.

I can only conclude (at least in my case) that my temporary hardware issues were triggered by something in the Rom or flashing process.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Sloeber94:
Seriously you are not making any sense. It's obvious you don't know how your phone works. How could it be a software issue if the problem also exists in stock windows?

Then you could say android F**** up the hardware. Nonsense.

Return to stock, stock SPL and send to HTC, it could also happen under windows you could say so..
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
I have similar issue.

http://xdaforums.com/showthread.php?t=897536

It is not hardware related (for me) since the problem only exists in NAND. I can reproduce (and resolve) this issue reliable.

When I install NAND / MAGLDR, the touch screen goes wonky. Period. I've tried MAGLDR 1.11 and 1.12. I've tried several builds of NAND Android (using different kernels) and with and without Clockwork Recovery (couple of versions). No matter what, the screen stops responding or acts like random parts are being touched.

These issues go away immediately once I load into Windows or Android SD. The screen becomes responsive and the precision is very accurate.

One thing I did notice that helped was reflashing HSPL. It cleared the issue up for a couple of hours. I also noticed installing Swype made the problem much worse.

Edit: Oh, and just so you know, I work in IT. I've been doing it for 20 years professionally and work mostly on troubleshooting and repair side though I have a few years experience in design and implimentation. Contrary to the other poster's comment earlier about IT not knowing what they're talking about, I do. And I've verified my theories through detailed experimentation.
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
That is a different issue than the one I have had. My touchscreen would become totally unresponsive. Flashing a different Android Rom, Task29, flashing back to windows mobile did not bring back any touchscreen responsiveness.

Do you get it in every single Android Rom you try? My issue only happened a couple of times. Other than those couple of times, my screen has been flawless with Android Roms.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
I got it with all NAND builds. I can't determine if the problem is with MAGLDR or what though since it doesn't have touch controls. Since it's the only thing that was common with all these problems, I would assume so. I've tried about 6 differen NAND builds using different kernels and Gingerbread and not and Cyangogen and not.

Android SD and WinMo has no problems. I'm thinking of trying Windows Phone 7 build since it uses MAGLDR too and see if the problem persists, but I don't want to bother having to do all the various steps necessary to get WP7 working and then having to undo it all to get back to Android.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Archer:
It can't simply be NAND or every single NAND user would have the same problems, and let's face it, there's a LOT of people using it and not having these problems.

It must be a combination of things, but what that combination could be completely baffles me!
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
I agree it's not just simply NAND. If it helps, I have a TMOUS HD2. Not sure what it is though. I Task29 and all. Even did a stock install, then reflashed HSPL and then Task29 then MAGLDR the a direct NAND (eliminating Clockwork being the cause).

That's why I'd like to talk to the DFT directly to try some experimentation.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Beefheart:
Infinitely more people are not having this issue. It is not down to NAND, as the person a few posts above says, it's going to be a combination of factors.
[HD2 Android Q&A, Help & Troubleshooting and Genera] pyrorob:
my 2 cents, could it be that due to imperfections in the manufacturing process, certain hd2's aren't as durable as other hd2"s?

not every chip made for every device is equal in terms of build quality, meaning inherent defects are present in random chips made during fabrication and that can lead to some devices that fail, immediately, after a few days,weeks or months or only under specific situations, such as putting the hardware under stress during a rom flash by using certain pathways or circuits that are vulnerable to failure, or just general breakdown caused by heat thats incurred during normal or heightened usage (these chips if my understanding is correct, are 65nm and should be able to handle up 190*F, but a defect can lower that, sometimes alot).

So, basically while software played a hand, not any more then what would be considered a normal function of the device, as it was primarily the hardware that failed, software of course would have to play a role as thats what the hardware is designed to run, the only exception would be if the phone is off and how useful is it then?
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Happened to me too...
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
So there's no fix for this aside from stockifying it and sending it in?
[HD2 Android Q&A, Help & Troubleshooting and Genera] sguler:
The same thing happened to my phone when I was playing with android, had to send for repair...

Could it be really android ? I heard that android has millions of color depths, while Windows 6.5 have only 65K, and this overheats the HD2 screen which is designed for windows... ( not sure if this info is correct, just read somewhere, don't remember )
[HD2 Android Q&A, Help & Troubleshooting and Genera] pretzdothack:
I had a touch screen problem before when I was in WM. HTC says it's a known problem that the touch screen can become unresponsive. I reverted my phone back to stock and sent it in.

Since then I've tried two NAND builds and several SD android builds all with no problems. I suppose it could be software related, but since HTC takes 'em back most won't look into it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Stoferr:
How long did it take HTC to repair your devices?

And when you got it back was the screen itself then replaced or was it the same? (Indication that it might be an internal controller)
[HD2 Android Q&A, Help & Troubleshooting and Genera] sguler:
actually I got mine back exactly in 7 days :D I just wrote a letter to them stating that I'm leaving the country next week for a long business trip and said I would appreciate if they repair it in 1 week :)

I appreciated, they saved my life =)

Actually, I had some big scratches on the corners and now it seems there are no! I thought they gave me a new device, cuz the screen, cam and the flash have gelatins on, all the scratches are gone! But the serial number is still the same.. So I think they changed everything but the mainboard...
[HD2 Android Q&A, Help & Troubleshooting and Genera] bigmikehd2:
HD2 is known for having digitizer problems. A good repair shop will fix it for around $110. If your good at fixing things you can attempt to do this yourself and save about $50 or $60 in labor. I had mine repaired and it works and looks just like new. It took 3 days to get it back but only because they had to order the digitizer. And please dont believe the guy who said "another dead screen after flashing to nand", Flashing has nothing to do with it, its a hardware problem that affects hd2 users on ALL operating systems, look it up.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mickfarr:
Without any numbers it very hard to pinpoint the cause of the problem.

I'd say percentage wise there's as many people running WM6 on the HTC HD2 having touch screen problems as there are people running NAND on their HTC HD2's with touch screen problems.

Just google touch screen problems on HTC's and you'll see its very common.
[HD2 Android Q&A, Help & Troubleshooting and Genera] i n f a m o u s:
Honestly, I don't think it's the ROM or the temperature to blame here. My device always reaches high temperatures when I'm tethered at home and I've flashed numerous ROM's on the phone and it's still functioning just fine.

I think its just a faulty digitizer that needs replacement. Just call up HTC Customer service and I'm sure they'll either replace your or repair your HD2 free of charge.
[HD2 Android Q&A, Help & Troubleshooting and Genera] MarlinFF:
Looks like my digitizer just died as well.. That is great...
[HD2 Android Q&A, Help & Troubleshooting and Genera] flynney:
Just my 2 cents here

I've been following android development from the early SD builds to NAND. I have flashed many customs roms and android roms and have had no such problems. As someone earlier pointed out in this thread, it must be down to quality control letting out 'weak' devices.

IMO i think its just hard luck that some users are experiencing this problem since using android NAND.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
The HD2 has tons of digitizer problems. Buy a replacement off of eBay for 30 bucks and fix it yourself.
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
While I understand that any screen can have problems at any time, none of the recent responses here can explain my experience outlined earlier in this thread.

On two separate occasions after flashing a Nand Rom, my screen totally stopped responding. Not even going back to windows mobile solved the problem.

On both occasions, (after many and various re-flashes) my screen eventually started to work and returned to perfect normal operating condition without any need for service or part replacements. I am currently running a Nand Rom without any issues whatsoever and have also flashed my phone dozens of times going back to windows mobile, Android SD builds, Nand, etc....

I am definitely not blaming the Nand process nor Android for anything. But there does appear to be something that makes this screen issue occur (at least a little more frequently) during this process.

If anyone has any ideas or theories for what occurred with my phone (again, my screen is now fine), I would love to hear them.

Thanks,
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
So...keep reflashing and it'll work?
[HD2 Android Q&A, Help & Troubleshooting and Genera] deweylima:
That has been my experience but while it is happening, it is not a good feeling.

And I am always thinking maybe this time it won't start working again.
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentfazexx:
Well I'll just keep reflashing Windows Phone 7 and see how we go...I'll report back soon.