First this is what I have:
HTC HD2(LEO) TMOUS
Android NAND: CMYLXGO's Stock Desire HD(NEWEST)
MAGLDR 1.13
16GB SDCARD
I TRIED GOOGLING AND SEARCHING FOR THE ANSWER
For some reason when im using the phone it seems to randomly acting like its being touch. The has never been broken, has a hard case. Im not sure what could be causing this. It doesnt happen on stock rom wasnt sure if it could be caused by the rom or kernel? Thank you for the help.
I have/had the same problem. It only happened when the screen got a bit of moisture on the screen then that certain part of the screen would go crazy with keyboard taps etc. I think it's your screen, as mine only started happening after I got a new screen, which I then had to get replaced, again.
Mine has done that. It would randomly spell words or poem apps like the screen was being touched. My screen was dry and clean. I just did a factory reset.
Well a clean install of Tom and it went away
Sent from my SGH-T959 using XDA Premium App
Related
I have a HD2 with miri v18 and darkstone sense v.2 and everything was working well until 2 days ago when the screen isnt responsive as before. It will not let me out of the unlock screen. It works sporatically at times, but overall, mostly not. It can possibly be a software issue, but someone suggested sending it to tmobile for service. My question is this. If the screen is cracked and I am not the original buyer of the phone, will I be in good terms to get the replacement. Or will tmobile just assume since it is cracked, it is by my own doings as to why the phone isnt working well.
if the screen is cracked they won't replace it under warranty at all.
xnifex said:
if the screen is cracked they won't replace it under warranty at all.
Click to expand...
Click to collapse
Seconded. Cracked screens are not covered under warranty.
Same Issue
I was using my Tmous to day listining to Pandord using Froyo 2.2 Darkstone Desire 2.1 and phone reset it self. Didn't think nothing of it and then after reboot screen was not responsive. My screen doesn't seem to be broken no nicks nothing of that kind rebooted multiple times and still no response from screen. I used Miri_Steve0007_EleganciaGTX_V4.0_FINAL to flash then installed Android on Sd card because my phone doesn't work i can recieve phone calls just can't dial out I am just wondering if the HTC sence file is corrupted im flashing various ROMs using the instructions on flashing each time
Prolly not. I would flash to a new ROM and see if that helps matters.
from what i have experienced, phone will get a bit hot from flashing a new ROM, and then from all the data syncing/downloading from initial setup. when phone gets hot, greater chance for screen to be unresponsive. give it some time to cool down. also, when unlocking phone, try to push the call or home button instead of the power button to turn on the screen before unlocking. some touch screen problems have been from something wrong with the power button (hardware problem).
Sorry for my bad English.
A few days ago, I decided to flash back my touch hd to the stock rom due to the big battery drain and slow performance.
Now my problems are gone and my phone is really fast,
but my screen is acting weird.
It happens mostly when I'm typing an sms, for example: I'm using swype and I want to swype a word that starts with the letter 'd', so I press 'd' and the swype line goes from the a to the d and then follows the path I've swyped.
It even writes a word that starts with an 'a'.
this is just an example, so I can describe what my problem is.
basically my screen thinks that I'm tapping somewhere else on the screen and then knows my actually tap-place.
This is not a bug in swype or sms, it happens everywhere in windows mobile.
It also isn't a screen allignment problem.
does anyone know how to fix this?
so again: it is the stock rom with the stock spl. is this a known issue, or are there any fixes?
thanks,
Artuur
Hmmm interesting...
so this did happen on any other rom you had flashed?
No, only on this stock rom.
I never had it with the stock rom when I had just bought the device, and I didn't had it on the cooked roms.
The problem began when I reflashed from energy rom to the stock rom.
Everything else (phone, wifi, bluetooth, battery...) is just fine.
i had strange issues with my touch screen before.
first i was sure that it came with the installation of mobile icq, so i got rid of it, didn't fix anything, hard reset, everything was fine for a while. then the problem came back, tried different roms, no change....
to cut a long story short, everytime the issue came up, i would panic, align the screen dozens of times and in the end perform a hard reset, just to realize it got me nowhere, until i finally found, that removing the display protector did the trick, apparently, there was a tiny air bubble somewhere on the very edge, that distorted all my inputs to slightly different spots.
since then i run the device without protector and everything is fine. from time to time it will still behave strange but carefully cleaning the display always resolves the issue, sometimes teeny tiny spots of dirt keep the device pressed in one spot and due to the way resistive touch screens work, it would only accept the middle of the 2 virtual press points as input.
so my advice would be:
1. clean your display, really clean it, especially the very edges, there can be something stuck there, practically invisible.
2. make sure, it is not software related, by flashing hspl, then a cooked rom and another radio, in combination with task 29 and hard resets makes sure, everything on your device is replaced.
3. if all that doesn't fix a thing, you might need to think about getting a new digitizer or entire screen.
hmmm. try a hard reset! or try flashing to a custom ROM, then reflashing again?
I have been using Ultimate Droid 3.2.5 for a couple of months now and a few days ago i pick up my phone to make a call and the screen doesn't respond when I touch the screen. Only the bottom buttons and volume buttons work. At first, if i I play with the buttons at the bottom i can usually get the touch screen to repond. I tried to wipe data/dactory reset and reinstall rom but now I cant even get it to work like before. Only thing I can do now is answer calls and call back the last person that called me. Has anyone else had this problem?PLEASE HELP!!! Thanks!
Did you eventually find out what cause this issues?
I think my phone is behaving similar, I'm using different Android ROMS for quite a while now, and suddenly without any apparent reason the touchscreen isn't responding very often after waking up the screen. It won't happen if the screen is on and the touch screen is working, only after a wakeup..
Sometimes it's just impossible to get it working again, and I'm forced to wait a while until it decides to respond again. It kinda feels like the phone is forgetting to wake or initialize the touchscreen properly.
ROM and Kernel changes didn't solve this so far.
I think the issues originally started with Typhoons CM7 NIGHTLY 3.7.1 / tytung 12.4v3 for me.
Actually I never found out what the problem was. I just flashed it back to stock and had T-Mobile send me another one. That was in May and actually a few days ago it happened to my phone again. So this time they sent me an HD7. It really sicks that they dont have that phone anymore. Cant do sh*t with this HD7!
Same here the Power Button is the problem, you just have to train yourself not to use it. I use Button Savior and Button Remapper. On my second HD2, luckily T-Mobile sent me a HD2, but that was in like March, right before my one year was up.
Make sure you keep this one working cuz there will be no more HD2! I may find one on Craigslist or something. This HD7 and Windows 7.5 really sucks monkey nuts!!!
tcole said:
Make sure you keep this one working cuz there will be no more HD2! I may find one on Craigslist or something. This HD7 and Windows 7.5 really sucks monkey nuts!!!
Click to expand...
Click to collapse
Yea I played around with WP7 on the HD2 when it first became avaliable and wasn't really worth the time and trouble it took to get it on there. One month later I went back to NAND and haven't looked back.
Same here! Registering Zune was a problem at first.
Thanks for your quick response! Yeah, seems to be a problem with the end button / flex connector of digitizer
I found another helpful thread about this issue: The Infamous Unresponsive Digitizier Screen Possibly Solved!
Obviously you need to replace the digitizer to fix this problem.
I'm sticking to the solution of not touching the button at all, there are apps to turn off the screen and shutdown the phone. At least waking with any other buttons works most of the time for now, but it's not really a long-term solution.
Wish I would have saw that thread b4 i sent my phone back!!!
Hello, my hd2 was working fine when with no particular reason it shut off and couldn't reboot (like it wasnt charged).
After I removed the battery for some minutes the phone boot and froze at MAGDLR.
After leaving it for a day the phone booted in Android and froze after a couple of minutes.
I guess this is a hardware fault since the phone was working flawlessly and now it doesn't even start at some times.
I think it is a problem of overheating. Can anyone point me to a direction of what replacements I need to find and if this is overheating or something else?
I thank you very much in advance
Maybe the battery.
sent from my HD2 using XDA App
How can it be a problem with battetry? It happens to me too, but sometimes it workes for 5 days and then for no reason it just hangs. Than i have to pull battery out and after that it works again for some time. I have installed android in nand and it happens with every android i've put on my phone. is it hardware problem or?
check if the battery pins are bent?
So youre saying that it can hang at lockscreen because of battery?
I checked it is not the battery... I changed the battery and things are the same. Also the pins are not bent
anyone that can help?
Which Android rom do you run?
sent from my HD2 using XDA App
I am currently using NDT MIUI but the problem doesn't seem to be this as the phone stops loading even in the MAGDLR screen.
Is this a temperature problem ?
Is the phone really hot when you touch it?
sent from my HD2 using XDA App
no not the phone, not the battery... however the problem remains. When the phone freezes it cannot boot, if you leave it for a bit it boots but only to MAGDLR or HTC Screen, if you let it for 1 day then it boots to build but then after a little it freezes
Can you check the radio rom?
sent from my HD2 using XDA App
If you can get into CWM, make a backup and tehn Task29 your device and re-install MAGLDR and start over and if the problem remains then its a hardware issue.
typical cpu bga failure case. Place the phone in a bag, then place the bag in a fridge. Let the phone there for about 1 hour then open the fridge door and try to boot up the phone while keeping it in the fridge interior area. If you notice improvements in it's behaviour, then yep, it's cpu bga failure. I haven't yet found a quick and easy solution, as you can see be the topic link in my signature.
Hello-
I usually do not open threads but I need advice on this recent touch responsiveness issue that has been happening. My Nexus 7 8 GIG was running great I had not had one issue with it, until one day I opened the case "Poetic leather case with magnet locks" and the screen came on notifications were on and animated everything looked fine. I went to unlock it and the touch screen did not respond to anything, now the screen rotates fine and all but it would not respond to touch. So I reset it with the power button, the touch screen then works until it times out and turns off, I wake it up and the screen does not respond again. I took it out of the case and have manually turned it on/off and it still does not respond to touch, but it will work every time I reset it. This problem has came out of nowhere it was running great.
I was originally on AOKP Milestone 1 with Franko's Kernel r25 so I thought maybe that was it so I re flashed Milestone 1 and kept the stock kernel and the problem persists. So I wiped everything and put BAMF Paradigm on it and it still does this, but the touch screen responds every time it is manually reset so I am trying to figure out if this is hardware or software related I am led to believe it is software considering the touch screen works flawlessly upon reboot but again I am not sure.
I have not added any new apps or anything like that to cause a memory leak or such. This problem started when I left the N7 for two days without touching it, then the problem happened after I tried to use it after the two days of inactivity.
Update: I turned the N7 off for about a day booted it back up now the touch screen is working every time I am confused.
So I still have 7 months on my ASUS manufactures warranty should I send this unit back? I just do not want to think its software related and it will get fixed through updates and then find out it is hardware related and be out of the warranty period.
I am on 4.1.2 with the last boot loader "not the new one"
latest version of TWRP
Thanks everyone in advance for your time.
It seems like a magnet bad effect to me! not sure though cuz the nexus 7 suppose to work fine with magnetic cases but it could be a Magnetic field effect. In my opinion as long as it works don't send it cuz you don't know what happens there in the service center, I mean once the device is opened it would never get the same as before.
Chaw Rash said:
It seems like a magnet bad effect to me! not sure though cuz the nexus 7 suppose to work fine with magnetic cases but it could be a Magnetic field effect. In my opinion as long as it works don't send it cuz you don't know what happens there in the service center, I mean once the device is opened it would never get the same as before.
Click to expand...
Click to collapse
Yea I had thought that was it but I took it out of the case and still does it so no dice on that field
well i flashed the latest google image and just started fresh. The touch screen is now working without issue so hopefully it was nothing still not sure though what would have caused this though -_-
Sent from my ADR6425LVW using xda premium
if anyone could shed any light on this issue it would be greatly appreciated thanks again.
Sent from my ADR6425LVW using xda premium