Database Users

Sorry for Cryin out loud but need your help guys

Hello Guys,
I am from india and I got the HD2 few months back, well to sum up the experience, I have had with the device would be “love and hate” kind of. There are times when I am simple awe stuck by the awesomeness of the device and yet there are times when she acts like a complete ***** freezes for no particular reason. It got so frustrating at times that I even contemplated on selling it off but some thing always stopped me .I would like to thank all the wonderful developers out here who have come up with such amazing apps that at least has made my device usable to a great extend. I THANK YOU ALL from the bottom of my heart.
I am on my official ROM with which the device came shipped with and the version being 1.43 and it’s quite ironical that we haven’t had a single ROM update ever since it has been launched in our country. Any way to cut the whole story short I would humbly request you guys to please look in to my queries:-
1)I am a newbie in to windows OS, so the utter thought of flashing the device kind of scares me off cause I have heard that if not done properly it can brick the device ,But lately I am willing to take that risk only if the cooked rom can solve these 2 grave issues of mine.
a) the screen acts like a lunatic on the run .ghost presses ,hyper sensitivity etc the screen sensitivity tweak did help me a lot but still I am not 100% confident while typing ,So my question is does any of the cooked ROM takes care of this ? and if yes kindly let me the name of it.(this is one issue which I really cant get over)
b) The phone freezes for no particular reason at all , It just stops responding of its own .does the cooked ROM would take care of this as well?
2)Do the official ROM’s address the issues that I have mentioned above from what I know that HK got a new ROM update with the version being 1.72 (Sorry if I am wrong),So in 200 million years I would get to get the official ROM in my country as well and If I am not a prehistoric fossil by then I would rather wait for the it to come as its rather a safe bet for a newbie like me .So any ideas guys as to if the HTC official ROMS take care of these issues .
3)The erratic nature of the screen is it a generic problem ? I can not replace my device in the pretext of this behavior if this is a problem specific to my device, because we have no replacement policies out here. So can a ROM update (cooked or Official ) get rid of this completely .
So guys please do let me know the name of the roms both cooked and official which can help me get rid of these issues.
Cheers .

Flashing the phone is extremely straightforward and easy to do.
If you can follow instructions, you can do it.
I've HSPL'd 3 devices and haven't bricked any of them.
Once you've HSPL'd it's highly unlikely that anything else (within reason) you do will brick the device.
You may render your device temporarily unuseable, but the fact that HSPL allows you to flash without a USB connection off the microSD (!) means that it's nearly impossible to brick a successfully HSPL'd phone.

my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed

antaed said:
my suggestion is to dare for a custom rom. study very carefully the tutorials in the rom development forum and you'll be fine, it's not rocket science.
however, to avoid any issues, please remember to always clean your device between two custom flashes by any of the 3 methods:
- flash stock rom + hard reset
- mtty
- task 29
i've always used the 1st method without any issues. it's more time consuming then the others but i've got used to it.
about which rom, this is a matter of preference, there is no best rom for everybody.
you can see which is my favorite under my signature. it's very fast and stable and very close to stock.
i will end by saying that i had many issues in the first couple of month after buying this phone but now it works like a charm, i love it!
oh, and i'm never gonna go back to stock... ever.
cheers and good luck,
antaed
Click to expand...
Click to collapse
Mate did you have problems with the screen as well? If yes then did the ROM that you are suggesting took care of them all?
Cheers.

i'm not sure if this is what you mean but i remember it acting strange at some point, after continuous use for 2-3 weeks with the original stock onboard and especially in opera. for example, streams of small vibrations but no movement while trying to scroll or zoom pages.
i've never experienced anything like that since but i have to admit that i flash a new rom every second week or so. i always want to try the latest release, it's very addictive .

hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.

challu said:
hey chakraa...
I have had similar probs...and did HSPL on my HD2 and have been satisfied, and have tried 30 different roms so far.... if you are looking for suggestions i would say "ROMeOS" makes some good roms... his latest 4.07 is good....suggest you try it.... after you do the HSPL your HD2.
Click to expand...
Click to collapse
Hey Bro ,Thanks a lot , I am finally mustering courage to go for THE big step(lol I am sounding as if I am about to get married or something), I would surely look in to the ROM which you have suggested,Would let you know about the outcome.

Finally did it.
Hey Guys,
Thanks a lot for your help I finally did flash the ROM all seems to be working fine now.
@CHALLU thanks buddy in the end I installed the rom suggested by you,seems quite stable as of now.Never been a big fan of SENSE so got SPB back ,the key board works like charm and some how I am getting this uncanny feeling that the battery life has improved as well.Do suggest me some other ROMS as well which would improve battery life ,take care of the screen sensitivity and enhance the over all stability.

MAGLDR NOT causes Touch Screen issues Confirmed

Update: According to info from Cotulla, MAGLDR does not initialize the touch screen since it doesn't have touch input. WinMo or Android (linux kernel) initializes the touch screen. The failures I'm seeing in Android NAND builds must be due to bug in those builds. I've just downloaded 14 different NAND builds (clockwork and not) to test out again. I'll report results later.
See Cotulla's post on the matter here. Thanks for all the help on the matter to everyone.
Update 2: Here is the link to my post testing a handful of builds and what I found.
Note: Please take the insults elsewhere. I'm trying to actually get some help and offer it. I never said MAGLDR caused any damage to my device. It's a simple bug which once pointed out can be researched and fixed.
The work the DarkForcesTeam has done is amazing! We're talking thousands of hours of work collectively. Some commercially available products don't receive such dedication. I just want to try to help out as best as possible to make it an even better product.
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.

FreakyFerret said:
When I use MAGLDR, my touch screen becomes over-sensative. It'll randomly select parts of the screen as having been touched when they're not, like a "ghost hand" was using the device..
It is not a bad digitizer. It is not a hardware defect. It is a problem with MAGLDR. I've confirmed this existing with versions 1.11 to 1.13. The problem only exists when using MAGLDR. If WinMo is used, problem goes away.
Here's what I did:
1) Task 29
2) WinMo 6.5
3) Ran an Android ROM from SD (Copes AOSP SD HD2 GB232/CM7 A2SD at
http://forum.xda-developers.com/showthread.php?t=898831
Everything is fine. Screen is incredibly precise.
4) Task 29
5) MAGLDR 1.13
6) Change SD build to boot from MAGLDR instead of HARET
7) Boot up, everything comes up fine.
8) Screen goes crazy.
Since I didn't change the build I was booting, and only changed MAGLDR, there should have not been any touch screen issues.
9) Task 29
10) WinMo 6.5 reinstalled
11) Change SD build back to boot from HARET
12) Boot the Android SD build
13) Screen is very precise once again.
Does anyone know if the DarkForcesTeam (DFT) has commented on this issue before? Are they working on it? Are they even aware of it?
Has anyone else had any issue like this?
I'm using one of the first HD2s to come out for T-Mobile in the US.
Click to expand...
Click to collapse
I do not know whether this will work or not. But try a NAND build with SENSE in it. Sense has a function of "Calibrate your Screen". Try and recalibrate your screen.
I know for sure the build "imilka's Vision Sense v3.0 (HD2Z)" has this feature. The link for this build is http://forum.xda-developers.com/showthread.php?t=898708
I hope that resolves your issue.

My touch screen stopped working during windows phone 7 and i cant figure out a reason why. Im running magldr 1.12

It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App

roloracer said:
It might be a mgldr booting SD build issue, I've been using cyanogenmod 7 android 2.3 nand for a month without a single issue..
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Same here
Sent from my HTC HD2 using XDA App

When I use a pure NAND build, the problem is there too.
Anytime I use MAGLDR, it happens.
I don't like Sense, but I'll give the one you recommended a try later tonight.

havent had the issue either.. BUT!!! cause its winter here whenever i come from outside and i use my phone i get random presses on the screen cause its wet, when i wipe it off it just behaves..

Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Edit: After flashing winmo - I kept getting problems for the first 1hr.
Now it seems that freezing is gone on Win Mo.
Will update later.

t0ny0 said:
Alright... my phone just died
Had the setup that you can see on my signature, and touchscreen just stopped responding randomly. First it was once or twice a day, now its like every other time that the screen is sleeping and I try to wake it up.
I did Task29, flashed official WinMo radio, and now the problem still exists. Every other time that the phone goes to sleep - i press any button, the screen lights up, but like the touchscreen function just wont work.
I know for sure that I am not the first, second or even tenth person that has this problem after running NAND-android. Maybe this should be put on the android development thread, so people wont break their phones.
I have no idea why is this happening, but I know that its time for a new phone. Hopefully T-Mobile will give me a new phone, which I can sell and get a native android phone. I hate windows, the reason that I got this phone was the screen size, which no other android phone had on t-mobile back when I got it.
So, one more time
PEOPLE, MAGLDR WILL CORRUPT YOUR TOUCHSCREEN IF YOU USE IT
With that said - I would like to thank everyone that made android on HD2 possible, and specially cotulla, his team, mdj and hastarin, I had a blast using it You guys ROCK!!
Click to expand...
Click to collapse
I had my touchscreen do that and just stop working BEFORE magldr even came out. A person I know who never hacked or did anything to his phone had this problem. It's a hardware defect and it's just coincidence that it broke while you had magldr on your phone.

not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.

jose makalolot said:
not again...
if MAGLDR makes those weird things to your phone then DON'T USE IT!!!
I have been using MAGLDR since it came out. EVen flashing a lot of builds everyday to test but never had any issues with the touchscreen.
Click to expand...
Click to collapse
Same, I've flashed well over 25 times and my Touchscreen hasn't had any problems.
MAGLDR is safe, end of story.

Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.

Buy a WinMO 6.5 phone stick to WinMO6.5 if you want it to work as intended by manufacturer.
If you want to tinker, then be prepared to tinker it to its death.
If you can't afford a new phone, don't mess with it.
If you can't be without a phone for even 1 day, don't mess with it.
If you want to blame, then blame yourself. You are just messed up.

Danation and hd2k10, I'm not smearing anyone. My phone is fine. There is a bug in MAGLDR. One I'm sure the DarkForces Team can fix if someone can provide some good feedback. Read what I posted again. I'm asking to help DFT solve this software bug. Not saying it's bad.
And I did confirm the problem only exists when using MAGLDR. It runs fine on most of the phones, but there are others aside from myself who have had problems with it. We would love to see MAGLDR working perfectly and I personally encourage anyone who it works for to continue using it. I wish I could use it and want to do everything I can to make that a reality.
psykick5, did you try flashing a WinMo ROM or Android SD build to see if your screen returns to normal?

Danation said:
Confirmed? Really? Because you think it happened to you?
This is anecdotal, and it is definitely not concrete in any way. This is pure FUD, nothing more. You should consider thinking before you post ridiculous claims that something has been "confirmed."
This has happened to ONE person on ONE phone, and pretty much everybody else is telling you that you are wrong. Does that sound confirmed to you?
It annoys me that you would smear somebody else's fantastic work because your phone had a freak accident. Go blame the government or something, just stop blaming magldr. Thanks.
Click to expand...
Click to collapse
Maybe you should read around and see that its not ONE person on ONE phone?
Also, I have flashed many many times, on HD2 and other devices, the fact of the matter is that it happened. Its not just the OP, its not just me, there are plenty of posts in here, saying that exactly the same thing happened to them /just search and you will see/.
Also, I would hate if someone is talking bad about someone elses fantastic work, and this is why I thanked everyone that helped getting android on our HD2s. There is no disrespect, I was just trying to warn other people that this has happened, and not once or twice. The fact that it didnt happen to you - means nothing It wasn't happening to me either, and I even wrote an angry comment to one of the people that was complaining a while back, and ha, guess what happened today
I agree, that probably "confirmed" is not the write word in here, but what we are trying to do, is just warn other users, AND DEVELOPERS so they can look into it, what if the problem is with MAGLDR? Hopefully its not, but thats a big coincidence. What if by some way its overheating a chip or something? You never know, since you are not a developer, I'm don't think that you can be 100% sure about something that is not open source, and you can't see how its made or what it does to the device.
So cool down, and if you can't help - there is absolutely no need to post negative comments.
Thank you,
Tony.
Edit: This is not for you only, its for all the other negative comments that are before yours. And after yours Y'all need to chill out, we are here asking for help. I have donated to a good amount of developers in here, and I am not trying to disrespect any of them, as I said in my previous post. I appreciate their work, but as far as I'm concerned, and the few other guys before me - there is a bug in MAGLDR, and it would be nice if Cotullas team can take a look at it.

Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.

I have EU HD2 and noticed same problems. Not all time and can say that i think its not MAGLDR problem. More NAND roms side. You ask why.
Tested many roms, not one. No, i dont go say these are bad. just tryed find wich works best for me.
With win 6.5 and win 7 roms i dont seen this problem but with android nand roms yes. Tested custom win 6.5 + android sd too. With that siutation dont had these problems.
Why i try here too is that i think its clued with another problem too, described on this hd2 forum on diffrent places. One is this thread.
Also i have read on some NAND roms thread that rom cooker are increased screen sensitivy or smth. Cant find right now it but if i remember it then i go back and post link.

Not all this sh1t again.
IF there was a "bug" in magldr for TS then it would affect the MAJORITY not the MINORITY.
Also the title of this thread is retarded, you havent "confirmed" a bloody thing other then your ability to presume something and then jump to a wrong conclusion.
EVEN if there is a bug would be a very small one and not one that DFT should waste their time on atm.

your understanding of a bug is that it shows up on the majority of a system? that's utter bull****! sorry.

HectiQ said:
Must be a T-Mobile problem. I don't have it. Sorry for you tho, wish I could help.
Click to expand...
Click to collapse
I have a tmous HD2 and don't experience that crap at all!
Sent from my HD2 Droid HD using XDA App

[Q] NAND Screen stays off after phone call

Hi All
Was using SD versions of Android in my HD2 which worked quite well .....decided to make the jump to NAND recently but I'm having a problem with phone calls.
When I make a call out, everything works fine, but when I hang up on the call, the hard buttons on the bottom of the phone all light up but the screen doesn't turn back on.... Only way to get the screen back on is to plug in the USB cable or power adapter or pull the battery and do a reboot!
Have tried a couple of different builds from different chefs and a couple of Radios just in case.
At the moment I've got the following on it:
Radio is 2.12.50.02_2
Android version is 2.2.1
Build is DL DesireZ v3.4 Final (but this problem also happens with CleanDROID V1.31)
Also tried an MTTY Task 29, reload of MAGLDR then re-flash of the NAND in case traces of my previous ROM were still around but that hasn't helped either.
Any ideas?

I seen many threads about same situation. Actually i itself use daily gpc hd2 gingerbread v1.5 with same problem. Sometime help back button (when call ended not at me). Sometime just more light to proximity (or it light) sensor (when inside and put phone with face to some light). Outside i just must turn phone with face to sun or good light then screen wakes up.
I tested many many nand roms. All have same problem.
Tested win 6.5, win 7 and sd version, they works well. That gives confirmation that my proximity (or it light) sensor works well. And finally that something wrong with nand.
Here was discussion that MAGLDR does that. NO.
I started run over net and find solution. Here seems no help for this right now. Maybe just problem ignored because cookers itself dont have this and cant do anything. If you dont have problem then how you can fix it.
On web i found some discussion about kernel problem or smth about this proximity sensor. I cant find it right now again. There was talking about this problem, but no solution.
I thinked about open new thread and invite kernel chiefs to discussion to solve this problem. But today i find your ask. I opened for any test and help that i can give. I dont be afraid to lose my phone if something must go wrong. Phone is just piece of electronic and you can replace parts. But knowledge and experience you cant buy.
Any ideas how to resolve this little bad thing?

Thanks for the reply.
Yes it's a real problem but mine won't wake up no matter how much light.
The only way I can get it to wake up is to plug it in to power, then the screen wakes up.
Is that the same as yours?

I i remember it right i was suprised once too if this happened. I just put my "again dead" phone to charging and its waked up.
If screen is dead and same time connected to pc (i use for managing inside phone androidcommander) then moving over dirs wake screen back too.
But lets look how long my nerves will be good. Today i thinked to move back win 6.5 and sell this bastard.

No don't sell we need to resolve! I'm hoping someone will look at this thread and help us figure out why this is happening. I can't believe we are the only 2 people who have this issue.
Anyone else have any ideas as to why this is happening?

This issue was also on sd versions. So I see nand has not fixxed it. I am running MDJ HD 4.6 and have this issue. Sometimes the light sensor works properly and other times it goes to black screen and gets stuck.
I read somewhere that it might be the hardware itself. Saw a video on youtube also. Seems the european T8585 and telstra T9193 might have poor light sensors. The T-mobile light sensor supposedly does not have this problem.
So I am guessing anyone with this problem does not have the T-mobile USA version??
It could just be drivers too. It is a pain and sometimes I wish I could just disable the light sensor.
Also NAND roms are no better than sd versions as far as bugs. If the sd version has the bugs then so will the NAND version. The build is just installed at a different location.

Yes good point.... the bug will be replicated as it's just where the OS is stored that's different.
I'm thinking it's the hardware as I have this problem on WinMo6.5 too and I have tried various WinMo roms but had the same problem.
Mine is a UK HD2 supplied by O2. Wish there was a fix for it :-( It's a real problem.
PS I ran PhireMOD's Skinny EVO SD Android for a while and didn't have as much as a problem as I have had with the 2 NAND roms I've tried..... if that's any clue? At least with that rom I was able to make calls and hang up and still get the screen back after I hung up (except for the screen going white and washed out which could only be resolved by a reboot). There was still the problem with the screen being on all the time during a call or the screen being black and not coming back on during a call though.

I have these sort of problems too. It's really annoying when you're in a phonecall and you take the phone away from your ear and it takes a few secs to turn on. Also when I'm unlocking it.
Sent from my HTC HD2 using XDA App

At least yours comes back on lol mine stays off for ages and ages and sometimes doesn't come back on at all!
Noticed that if I shine a torch into the proximity sensor that's the only way I can get the thing to turn back on :-( Also noticed the 2 little holes where the prox sensor sits appear dirty/cloudy... not sure how that happened.
I wonder if the prox sensor is busted or if it's just dirty or something? Going to get a T5 Torx and take my phone apart to find out if it's something I can resolve.

Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now

Hmm, are you sure g9650? Seems my guess about kernel was then true. I use gpc pure gingerbread 1.6 with gpc itself made kernel. I go right now replace kernel and test. Results tomorrow.

Took the phone apart yesterday night and uncovered the proximity sensor. Even out of the case it needs a torch/flashlight to shine on it to bring the screen back on :-( I honestly think the proximity sensor hardware isn't working anymore.
I'll try the kernal you suggested though just in case that's what's causing the problem.
Datas0ft let me know if it works for you?

Latz, actually i taked to test markinus extra clean 1.7.1 (right now on it itype this). Had one call before and no changes.
Also i stuck on taking out kernel at this version. Low knowledge. Dont find any help yet on xda. I work on it. If you have hints dont hestitate say.
Sent from my HTC HD2 using XDA App

:-( I was hoping we found a miracle cure! Ok let me flash mine tonight and try it to see if mine behaves any different. Will post back with results... let me know fi anything changes with your phone datas0ft.

q9650 said:
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Click to expand...
Click to collapse
Can anyone upload MarkinuX Kernel please? Thanks

Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.

datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Thanks, I just finished downloading the whole Markinus rom to extract kernel haha but you saved me... will test and report, thanks

datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Quick question, the zip file you gave me only has two .ko files and zImage while the original rafdroid kernel has like 5 .ko files... what should I do? copy raf's kernel .ko files missing into markinux ones?
Or just pack the zip file using two .ko files? Thanks

I cant ansver. Dont have much knowledge on this. I followed instructions. This taked to me these three files. I installed these.
I finded some problems right now (wifi and gps dont work and my 3g too). This may not happen at kernel side. I have made some changes on rom side. I go replace whole rom and then again kernel. Then i go make final decisions.

I'm having the same problems, you two are not the only ones. This has been really frustrating me lately, and I thought it might have been a problem for only me because I just had the screen replaced. It worked fine in winmo 6.5, now in NAND I'm having some issues. I text a lot more than I actually call, however so it's not that big of a problem for me right now

[Q] Emergency help, touch screen isnt working at all

I have just installed WP7 and when it started the touch screen doesnt want to work at all. On everything it said it was installed successfully and i did every step in the guide -> http://forum.xda-developers.com/showthread.php?t=1356833.
Buttons works.. i can volume+ and - and i can also lock the phone but due to not working touch i cant work with it..

Anyone? Its not broken .. it was working great on the Android before the flash. Please i really need to know what to do.
Edit: I even tried installing v4 but still doesnt works.... :x

Im really sorry for triple posting but this is getting annoying. All day im trying other and other ways, flash back to WM6.5 .. TOUCH SCREEN WORKS ITS NOT GOD DAMN BROKEN ... I've send a PM to the developer of the ROM, guess what no answer.. i dont want to get back to WM6.5 .. I've used to flash 4 NAND androids (the best ones) each one of them in the main functions shows at least 2 bugs which are annoying like freezing display or my favorite - i cant hang up... i posted a thread in the Q&A Android forum about this, again no answer... I ONLY NEED TO KNOW WHAT TO DO to get my touch screen responding and working on my god damn WP7 so i can stop getting freezing stupid display and to be able to god damn hang up.. IS IT that hard!?!?!? Oh the best one is - i cant post to the main topic of the rom because according to the forum rules the newbies are idiots and they cant recognize any bugs in the rom so they can report it!... Jesus Christ give me a f***ing answer how to fix my touch screen driver or something or whatever i want my god damn phone working........

Hello I have the same problem, I went back to Windows Mobile 6.5 but the problem remains !!!!!! The touch does not work anymore!! How do you solve this problem??http://media.xda-developers.com/images/smilies/mad.gif

Hello you some news? I hope you do not have to buy the new touch screen!

For the original poster, I have no idea, sorry. For the second poster, it definitely sounds like your digitizer is broken. Have the same problem with my HD2. You can get them for cheap on Amazon, but replacing it takes some skill. Don't know where you live, but most repair shops will do it for around $50 here in the states.

Same here. i tried the YukiXda/Xboxmod Rom and after a reboot the touchscreen stops working. Will report to the devs. do not worry my friend

Hey darky, did you try installing the old HTC drivers on your WP7? Not sure if you did, or if that particular rom uses the newer drivers, but that could potentially help out. I found the old drivers in the Xboxmod cab update thread. Don't know if the rom you're using supports cabs or not, I've only used xboxmod & yukis rom. Search that thread, would post a link but using my phone at work.
---------- Post added at 08:38 AM ---------- Previous post was at 08:35 AM ----------
Nitro_123 said:
Same here. i tried the YukiXda/Xboxmod Rom and after a reboot the touchscreen stops working. Will report to the devs. do not worry my friend
Click to expand...
Click to collapse
Same as you, over here. As soon as I updated to SP1 & rebooted, no more touchscreen! But mine wouldn't work in any OS, including WM6.5. So I think my digitizer just had bad timing for me, but who knows could be rom related.

Thank you all for taking time to answer!
@lorispari No i couldn't get it fixed at all, your problem sounds different than mine because my touchscreen works with other OS without problem.
@JonnieLasVegas I haven't tried, i only tried different radio version and reinstall of the HSPL... though i dont know how much that could help me because im still new with the smartphones... as far as i see this HTC HD2 is really great but has a lot of factory bugs in hardware and software side (if i could say it that way). Even with stock WM 6.5 it had a lot problems. Anyway when i saw the thread with all the known bugs that WP7 has... i just clicked the HTC Leo: HD2 category and switched back to Android ICS which was another mistake because i forgot its still buggy as hell so im flashing atm to Gingerbread however in few months im selling this phone and getting HD7, hope till then there will be a category for him (or it may have.. i havent checked)
Thanks again for the answers! Appreciate it!

My screen was unresponsive twice. Turns out digitiser was broken. So had to flash to stock rom and send to htc for repair

If you need a fix, pm me, found one

Touchscreen not working

Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!

read here http://forum.xda-developers.com/showthread.php?t=993787

I've already read that. Thanks
Im just seeing if it could be a Kernel problem or something of that sort.

I've had this problem on one of the ROMs i used, not sure which one since i didn't stay on it for to long.
After i flashed a different ROM it fixed it. This might seem like a lot of work but why not reinstall MAGLDR,
CWM & a new ROM. Maybe try RAFDROID HD. Yes i know its a really old ROM but its a goodie and this
would be for test purposes anyway. You can always switch back.
I read the mentioned thread before too and im sure it does sound like it happens but since it happened so
soon after you installed a new ROM it makes me think its the ROM, eventhough you tried to reinstall a
different one. Maybe you can make a backup of your SD card and repartition both your phone and SD.

PC10DaTruth said:
Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!
Click to expand...
Click to collapse
After reading the other guys thread about the end key it does seem like a bad digitizer . i read other threads explaining your exact same issue . the only way to figure out if its ROM related is to flash the stock winmo 6.5 ROM . yes , i said it , winmo but thats the last resort before deeming something hardware related . if you tried the end key option , pressing really hard on the key , then i guess i would change tto winmo and try to see if it still happens then

I do have to admit it could just be coincidence and the digitizer went up but considering this happened
only a few short days after he installed a new ROM makes me feel that there is a possibility its the ROM,
or maybe even the partition he changed (if it applies) when flashing that ROM over. I still suggest to start
over from MAGLDR on, including repartitioning your phone to the proper needs of the new ROM to see
if it helps before doing something drastic like reverting back to winmo.

Thanks for the help everyone, opened the phone up. Was hard as hell! But I cleaned the dust on the contacts under the end button, still no luck. I bought a new phone. Going to get a digitizer down the road and fix this one, If anyone want to buy it just let me know.

You will get a lot more people to see your interested in selling the phone if you post it in the xda marketplace found here.
Just open a new thread there and post how much you would want for the phone. I'm sure people would be interested
especially when you can get a new digitizer off ebay for so cheap.

change an other rom,if the problem still exist,i am sorry to tell u that u should send it to fix the touch screen..