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
Related
i have an HD2 with a cracked screen i bought on craigslist. the unlock screen will stop working sometimes, and when i pull the battery and reboot, the home screen sometimes doesn't work. i've heard of these problems before but i'm not sure if this is a software or hardware problem. the previous owner had the phone running on AxLor DF1 XLite WWE. please help!
also i'd like to know how to flash to stock through micro sd, since i don't have a usb cable.
Thanks.
isoDUB said:
i have an HD2 with a cracked screen i bought on craigslist. the unlock screen will stop working sometimes, and when i pull the battery and reboot, the home screen sometimes doesn't work. i've heard of these problems before but i'm not sure if this is a software or hardware problem. the previous owner had the phone running on AxLor DF1 XLite WWE. please help!
also i'd like to know how to flash to stock through micro sd, since i don't have a usb cable.
Thanks.
Click to expand...
Click to collapse
Go to this thread here, this is a thread on flashing from SD card. It has all the info you will need.
Also you can buy a replacement screen and install it. There is a couple of threads here on XDA on how to do this just do a search for them.
T-Macgnolia said:
Go to this thread here, this is a thread on flashing from SD card. It has all the info you will need.
Also you can buy a replacement screen and install it. There is a couple of threads here on XDA on how to do this just do a search for them.
Click to expand...
Click to collapse
thanks, got on the stock T-Mobile rom now, but the touch screen on the lockscreen only sometimes works. would flashing to android fix this? i notice it will unlock sometimes after i press power then give it a few minutes, so i'm not sure if this is hardware or software related, and i'd like to avoid replacing the screen if i can.
EDIT: weird, i read a thread that said i should use the call button to unlock, and after a battery pull and waiting a few minutes, its worked for a bit, so i guess i found a temperary fix....
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
isoDUB said:
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
Click to expand...
Click to collapse
You can't have them all. You can have WP7 running from NAND and Android running through SD. Not too sure on the rest though.
Sent from my Nexus One using XDA App
isoDUB said:
thanks, got on the stock T-Mobile rom now, but the touch screen on the lockscreen only sometimes works. would flashing to android fix this? i notice it will unlock sometimes after i press power then give it a few minutes, so i'm not sure if this is hardware or software related, and i'd like to avoid replacing the screen if i can.
EDIT: weird, i read a thread that said i should use the call button to unlock, and after a battery pull and waiting a few minutes, its worked for a bit, so i guess i found a temperary fix....
so now, i was wondering if its possible to boot android from the nand, and boot windows mobile 6.5, wp7, ubuntu, and meego from the sd, or can win mobile 6.5 only be booted from the nand? also, i need spl/hspl to boot all these things right?
Click to expand...
Click to collapse
I know it would be a pain in the butt and in the wallet too. But it would probably benifit you to replace your screen. But this is a dessision that you will have to make for yourself.
Glad you found a teperary fix!
Yes you will need HSPL and also MAGLD flashed to your HD2 in that order to flash a NAND Andriod ROM. I beleive you can flash HSPL from your SD card, I think the thread I linked covers this. Buy I din't think you can flash MAGLD from your SD card. So you will have to have a USB cable for this. You can go to the HD2 Andriod NAND ROM section here on XDA and do a search for MAGLD and you will find the thread on it so you can double check and see if you can but I really don't think it is possibble. But you will have to have a USB cable to flash Andriod, WP7, MeeGo, and Ubuntu cause MAGDL does not have SD card flashing ability yet but they are working on it though. They are also working on being abale to run Windows Mobile 6.5 from SD card but as of right now it is not possibl, only from NAND right now. Also if you install a NAND Andriod ROM I think you can run WP7 from SD card but don't hold me to that cause I am not 100% sure of that, but if So that isit no other OS from SD card when running a NAND Andriod ROM.
T-Macgnolia said:
I know it would be a pain in the butt and in the wallet too. But it would probably benifit you to replace your screen. But this is a dessision that you will have to make for yourself.
Glad you found a teperary fix!
Yes you will need HSPL and also MAGLD flashed to your HD2 in that order to flash a NAND Andriod ROM. I beleive you can flash HSPL from your SD card, I think the thread I linked covers this. Buy I din't think you can flash MAGLD from your SD card. So you will have to have a USB cable for this. You can go to the HD2 Andriod NAND ROM section here on XDA and do a search for MAGLD and you will find the thread on it so you can double check and see if you can but I really don't think it is possibble. But you will have to have a USB cable to flash Andriod, WP7, MeeGo, and Ubuntu cause MAGDL does not have SD card flashing ability yet but they are working on it though. They are also working on being abale to run Windows Mobile 6.5 from SD card but as of right now it is not possibl, only from NAND right now. Also if you install a NAND Andriod ROM I think you can run WP7 from SD card but don't hold me to that cause I am not 100% sure of that, but if So that isit no other OS from SD card when running a NAND Andriod ROM.
Click to expand...
Click to collapse
thanks. for now i'll just work on installing android to the nand. i have a question though, will turning off the lockscreen in android possibly fix the touchscreen problem? i've been racking my brain trying to figure this out. i can either hurt my wallet with a screen repair, or i can do a battery pull every everytime i use the phone.. a real pain in the ass... sigh.. at least i got the phone cheap..
isoDUB said:
thanks. for now i'll just work on installing android to the nand. i have a question though, will turning off the lockscreen in android possibly fix the touchscreen problem? i've been racking my brain trying to figure this out. i can either hurt my wallet with a screen repair, or i can do a battery pull every everytime i use the phone.. a real pain in the ass... sigh.. at least i got the phone cheap..
Click to expand...
Click to collapse
You know I can not say for sure if turning off the screen lock would solve your problem. But it sure is worth a shot so I say go for it and see. Also you can use a app like Touch Tools or BsB Tweeks to cut the lock screen off in Windows Mobile. Just do a search here on XDA or do a Google search for them and you will find them I recomend the Touch Tools this is a really great app. It adds a lot of tweeking ability to your HD2. I love it and have been using it for atleast 5 to 6 months now. Anyway if turn off the lock screen with one off these apps and it fixes your issue. Then you will know if you turn off the lock screen in Andriod it should have the same result. Heck if it fixes it you might just keep Windows Mobile ha ha just joking. I would not blame anyone for flashing a NAND Andriod ROM and getting rid of Win Mo. I personaly like Win Mo.
You're best off investing in a USB cable too lol. Your local hardware shop will have them. Its just a basic USB to micro USB cable.
I dont think any amount of tinkering with any OS is going to resolve your touchscreen problem............
The screen is cracked right?? Theres your problem.........
Could be issues with the digitiser as well because of this.
First job, new screen...........
i've been messing with the phone last night, and it seems the problem is related to the end call button. it seems whenever i try to wake up the phone with that button, it will freeze, while using the green button will wake up with no problem most of the time (>20% chance of freeze). it seems the freezing doesn't happen after a certain amount of time, since i left the phone in sleep all night and woke it up in the morning no problem. so in case anyone has the same problem as me and is too cheap to fix it, try only using the end call button when actually calling/putting the phone to sleep.
and where could i get a micro usb cable cheap besides online? i think t-mobile has them but they're like $10+...
it's dead again!
help! (again). the touchscreen is dead after i HAD to use the power button today, and now i can't use the touchscreen at all! i've tried turning the screen on and off like 50 times, tried like 10 battery pulls, but nothing! please help! can i open my phone somehow to get to the end key hardware or something???
earlier today also happened to me this problem, I install several rom a day, I can not go a day without testing new rom, I thought the problem was that, because I found this topic, when I use the button to connect the phone, everything is well, but not always the case that with the off button. Was it any rom that did this damage in some piece of hardware?
Body said:
earlier today also happened to me this problem, I install several rom a day, I can not go a day without testing new rom, I thought the problem was that, because I found this topic, when I use the button to connect the phone, everything is well, but not always the case that with the off button. Was it any rom that did this damage in some piece of hardware?
Click to expand...
Click to collapse
isoDUB said:
help! (again). the touchscreen is dead after i HAD to use the power button today, and now i can't use the touchscreen at all! i've tried turning the screen on and off like 50 times, tried like 10 battery pulls, but nothing! please help! can i open my phone somehow to get to the end key hardware or something???
Click to expand...
Click to collapse
Sorry to tell both of you but your problems are hardware related. Member isoDUB yours is most definitly a hardware issue, but it has been a little bit sense you posted that post so I hope you have got your HD2 fixed or are working on getting it fixed. Member Body yours sounds hardware related to cause if you flash another ROM and you still have the problem with your buttons then it is most definitely a hardware issue.
Best option is to send to HTC and see if you can get a new one for free if you are under warranty.
same problem
hi
im not original english speaking so please excuse my bad english.
a few days ago i got the same problem. the display doesn't work when the phone was waked up with the endcall button.
when i woke up the phone with an other button the display worked.
i sended it to htc an they just told me they will not repair it because it is not in the original contition.
i flashed it with the latest original rom from htc but they didn't tell me what is wrong in detail.
i answerd them an asked what is wrong but until now i didn't get an answer.
Hello, I have a similar problem. When you unlock the screen so we jump on the green but some spots that disappear after a while.
Disaster strikes !!! Same prob here !!!
its indeed something with the buttons ... Touch screen is dead ... but sometimes its workin!!
Three months ago ... I changed the case of the HD2 with a new one. The "old"one was full of scratches ...
I think yhat HTC is not gonna accept that ... the "void-label" on the screw is damaged...
What do you think Guys ??
Grtz
every where the htc hd2 screen problem ........... i think that every one who has the htc hd2 facing the screen problem we shopuld start the new thread where we that who has the htc hd2 without any touch screen problem
Have the same damn problem ..once the screen is locked ..its impossible to slide it to unlock ..previously it was working 50% of the time and now it doesnt work at all :-(( ..
Any suggestions ? ...I read alot on the forums and people seem to say that its digitizer related but the imp thing is to note that almost 98-99% of the people having this problem are frequent Android rom flashers ..so does Android have something to do with this and will flashing original stock rom back be the solution ??
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
check here
LOADS of people are having this problem including myself.
As long as Mobile Data and Gps are OFF, I have no freezing issues.
BUT, if I turn on Mobile date or Gps, or both, then GAME OVER.....it freezes within seconds.
It's not your battery, or SD card and don't listen to the muppets who repeat themselves by saying "do a task29" coz it doesn't work.
I've tried 5 different SD card, got 2 hd2's, task29, over 100 roms, different radios etc etc.
Never used to happen on SD builds, only Nand.
if i had the cash, i'd smash my hd2 against the wall and get a Android native phone.
this aint ever gonna be solved.
matt
freeridindirtbiker said:
So my HD2 freezes constantly. I don't have the unlock freezing issue nor the black screen freezing issue. My phone will just freeze quite constantly. Doesn't matter if I'm just doing a message, online, or it's just sitting there doing nothing. It will freeze and will have to remove the battery and restart it. I've reinstalled MAGLDR, CWM, and tried several ROMS and it still doesn't make a difference. I remove the battery and have to let it cool for around an hour just to turn it on and be able to use it for a period of time.
Any suggestions out there? Could the battery be bad? The hardware? I constantly use Task Killer and Data Eraser to make sure there aren't unnecessary programs running. I've narrowed my app collection to just the necessary ones that I need. Still doesn't make a difference. Any programs out there that would help with this issue in any way. Would repartitioning my SD card help at all. I have pretty much everything on my SD card as well so the hardware shouldn't be overloaded at all.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Hi,
It might be worth trying to flash an original ROM and seeing if the same thing occurs in WinMo.
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
I had a similar problem, but mine came about under different circumstances. I smashed my HD2 against a wall for whatever personal reasons that you shouldn't care about, anyway, so I ordered a replacement display. When I installed the display the phone would freeze just as described by OP. I found that disabling GPS and WiFi allowed me to use it for a longer time, but if I ever so much as applied any pressure to the display (rather than just lightly touching it) the screen would freeze and sometimes it would just straight shut off until it didn't turn back on at all (this was barely the first day after installation). I opened the phone and tested, found out that the LCD flex cable had a defect to it where if it was bent (the position it's supposed to be in once the phone is assembled) the display would "short out" and with the cable fully extended no problems would be present, even after applying pressure to the display or any of the other internal components.
I'm sending my LCD back for a replacement and hopefully the new one will work fine. I've read that some LCD's cause the HD2 to freeze and I think I was unlucky enough to receive one such. I need the phone to hold on long enough until I get my contract renewal May 2012. I'm surviving on my Dream right now and I'm going through Angry Birds withdrawal...
Compatible-Bad Hardware-Insurance Questions
freeridindirtbiker said:
I've tried all those things. I'm using the Nexus 2 Gingerbread ROM by tytung. I've tried winmo roms, android, etc. I've done task 29 several times. Different radios as well. It doesn't make a difference at all. I found a thread that might be the culmination of it all. If anyone else is having problems like I am, take a look at this thread. It's definitely the motherboard overheating and freezing/and or shutting itself off.
http://forum.xda-developers.com/showthread.php?t=982454
Luckily, I pay insurance through t-mobile so I will be picking up a new HD2 pretty soon.
Click to expand...
Click to collapse
I have similar issue. Could use advice. Please.
My HD2 is about a year old. Decided to try android on the sd.
Device: HTC HD2 TMOUSA
Radio: 2.10.50.26 (Original) NOW flashed to 2.15.50.14
SPL: 2.10.xxxx (Original) NOW HSLP 2.08.0000
Android Rom: SD AmeriCanAndroid AOSP HD2 GB234 CM71
WM Rom: 2.13.531.1 (Original)
ACA seemed ok but would freeze randomly. So I flashed the radio to the 50.14. Seemed a little better but still a few freezes in android. Thought I would try the partition to improve the sd card performance. can't tell if it helped or not to many freeze ups to use android during the day. NOW my winmo side it giving me random reboots. It gets hot reboots, especially bad if using gps. I know overheating is part of the issue because during the middle of the day in my car without A/C it is terrible.
I also have an OTTERBOX Defend which has kept the phone looking great but is a really pain with on all the battery removal with the freeze ups.
I have read that this can be a mainboard issue, but how can I tell if it is or not?
Could the radio and winmo rom be incompatible?
Should I flash the winmo rom to a more compatible android rom?
Should I send it in since I have TMO insurance? (Anyone know if there is a deductible if you didn't lose the phone?)
I have also noticed the on the winmo side it reboots less if I turn htc sense off.
Not sure if I should go back to a different radio or send it in?
Are the insurance replacements refurbished or new? do they have the same issue?
Thanks for any expertise you care to share.
Had similar problems with Tmous HD2. Problems were really bad in Winmo; aca worked somewhat better. Read forums, tried standard "solutions". With time the problems got to the point where the HD2 would not boot unless it had been placed in the refrigerator for 5 minutes.
Did T-Mobile warranty exchange in April. Replacement was refurb (arrives without battery or sd card, used old one), but looked fine. Had a week to test "new" phone, before sending the old one back. Replacment phone works much better. In Winmo, gps, videos, sense no longer cause reboots; aca also works great.
Hope this helps...
TheATHEiST said:
Have you properly formatted card? (overwrite with size adjustment)
Which rom are you using?
Does it do it on multiple roms?
Have you done a task29?
have you tried a different radio version?
Click to expand...
Click to collapse
Exactly as my post from a few days ago predicted..."task 29"
FFS.
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Does the area beneath the battery shell, behind the phone, feel particularly hot? If so, it's likely overheating (HTC calls it a current leakage... something?) and if you're under warranty you may wish to send it back.
Otherwise, there are fixes (suck as devising your own extra heatsink, reflowing the solder).... but it's non-trivial.
Does it freezes while using any particular applications, and what happens when it freezes???? I mean does it get to normal by itself or you have to pull the battery out and restart your HD2.
I am asking this because I was also having the same issue with my previous HD2, and then I came across this post
http://forum.xda-developers.com/showthread.php?t=1189544
which explains a lot about bad blocks which affect the android build.
DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.
hstr said:
dude, u need to give the detail of your problem, when and how it freezes. Cuz there are lot of problems by which a phone can be freezed up.
Click to expand...
Click to collapse
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located
I'm having the same problem. My HD2 will freeze if I play games on it causing me to pull out the battery and when I boot it up, sometimes it will freeze at the MAGLDR screen, will freeze as soon as the rom boots. Right now my phone seems stable and I'm only using it for texting and making calls and nothing else for the fear of damaging the phone any further. I have a TMOUS phone btw.
DutchMaster117 said:
yea sorry im just at the point where idk what else to do.
Lemme be more specific about this.
Theres times where it would actually boot up to where i can make a call but only for less than a couple minutes most of the time. There are times where i get lucky and it stays on for a good while ( couple hours ) and it'll stay that way as long as i dont use it. It freezes up starting up just about any app so i have this odd feeling it might be my sd card. But then i dont understand why the next thing happens. After i remove the battery and put it back in and boot either 1 of the 3 happens.
1) 1EFATAL HIT 1
2) Gets stuck on Go go go
3) gets stuck after go go go when rom tries to boot up.
Only thing i can do to get it to boot up again is take the battery out and leave it out for a good 10-15 minutes.
I tried Task29 and reinstalling magldr, cwr, and Rafdroid Rom and i still get the same crap
The Phone gets a little warm under the cover sometimes but its right were the micro sd is located
Click to expand...
Click to collapse
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol
hstr said:
Last question to u, that when u had ur stock windows rom in ur mobile , does any thing happened like this.
if not, then the problem is not in your mobile or sdcard, the problem is in the method u are intalling by.
1)try to get back to windows mobile.
2)install hardspl4 - 2.08 (not Hardspl3 - 2.08)
3)install magldr 1.13 (not magldr 1.11)
4)install clockworldmod recovery 3.0.0.5 (if ur rom is a cwm rom.)
5)Now flash the rom.
6)give it a try, if not any issue, then
7)push the thanks button. .. lol
Click to expand...
Click to collapse
That's actually the same thing I do.
Alright I know this might sound ridiculous but it seemed to work ( so far ). After 6 hours of trying to get this phone to work I decided to try something I saw on another thread. I got an icepack and did a complete install while having the phone on the icepack to keep it from getting warm. To my suprise it worked... I'm using my phone now with no issues yet and its been about 12 hours and it hasn't frozen yet. Although it did do a random reboot once ( I have a few bad blocks so I'm guessing that might be the reason). But Yea this worked for me some how. I'll update on any issues I get as soon as I can.
Sent from my HD2 using XDA Premium App
Same problem for me. My hd2 always freezes with any sense ui android build. MIUI and Nexus HD rom works fine.
My simple advise is... reinstal windows. And try again.
This worked for me when i started with the HD2.
Sent from my mercury using XDA App
Hi I had the same problem, but I sent my phone for repairs and it never froze again. According to HTC they just replaced the main board. But before I did that I actually flashed the official RUU (windows 6.5), and it continued to freeze, so I was quite sure it was a hardware problem. Indeed after repairs my phone didn't freeze anymore.
Sent from my HD2 using XDA App
DutchMaster117 said:
Ive had 2 HD2's and its been the same problem for both.
No matter what rom i use on my hd2 it ALWAYS freezes(I was having the same issues with my first hd2 but eventually the screen on it stopped working and i sent it back for warranty and got a new one)
Ive flashed 2 other hd2's that belong to some friends and i did the exact same thing to their phones that i did to mine and they dont have any issue.
I dont know what to do and why am i the unlucky one
Please XDA Community i come to you for Guidance! I know this phone can be amazing but why is it being so stubborn!
Can it be SD related?
Click to expand...
Click to collapse
I also had 2 x HD2 which did this.
Froze when got to hot, or if using gps or mobile data.
Sold it 2 weeks ago, now own Desire HD and it's BRILLIANT!!
So now ive been running rafdroid on the phone without an sd and it runs.. but laggy since theres almost no space left in phone and it isnt getting hot. It only gets hot when it operates with the SD inside.
anyone know anything about that?
same problem
i have the exact same issues. the phone freezes every time it boots, be it magdlr nand, sd, wm 6.5 anything. however my old hd2 had no problems at allbut i broke it changing the screen digitizer and lcd.
(the white plastic on the connector that connects the lcd and digitizer to the main board broke.)
im pretty sure the reboots are mother board related but i don't know if telling tmobile or htc that will do anything because the phone is old. (i got this other hd2 from a guy on craigslist.)
I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.
oztorque said:
I had the same freezing problem with my HD2. After all the research I've done, none of them worked. Then i put the phone into the freezer for a minute and took an ice pack, placed it on the back of the phone where CPU is located. While holding the ice pack, I re installed the ROM and at the and freezing issues were solved. It never froze again.
I hope this solves your problem too.
Click to expand...
Click to collapse
I want to ask whether this cooling trial fixed freezing problem forever? suppose if u use your set for more than for hour streaming over wifi? never it got freeze again?
The best solution that you can flash back to WinMo 6.5 and run Android from SD Card.
I have the same issue... but...
Make a complete instalation with an ice pack?? Are u joking me?? It works??
well... i have not to lose... i will report if i try it...
I flashed stock rom and run android from sdcard. but when i press Haret.exe is going to HTC green logo and after restarting. some solution?
Similar problem
I have a similar problem. But with two different phones.
I bought LG Optimus One about two years ago. After a few months, some freezes appeared... I've sent it to manufacturer three times and every time they changed some parts... but nothing have helped. I've made some experiments (another battery, SIM card, MicroSD card, custom ROMs) and than I realized, that the problem occurs only while the mobile internet is ON.
This summer, my friend offered me used HTC HD2 and I bought it. He used to have Android there with no problems. After a few weeks, the freezes occured again. And again: I can surf internet all day by wifi with no problems, but when I tunr on the mobile internet (MI), the phone freezes. The back cover of battery is a bit hot, but this appears while long using the phone too without MI (without freezes).
I've tried almost everything to solve this problem: changed SIM card, changed SD card, everytime with flash of the newest ROM... nothing helped.
I'm not sure if the problems with LG OO and HTC HD2 have the same reason, but I can't believe I can buy two phones with similar problems without transfering them.
What aboutthat crazy plan of flashing with ice cooling? Does it work afret a few months too?
PS: Sorry for my English
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..