i'm running on a darkside prefinal rom for about a month.
suddenly the soft stopped responding(don't work at all), and the screen sometimes think i'm touching it when the phone lays on the table far from me.
i think i should mention that before the darkside i had a gingerbread at&t stock rom and after that a cm7 nightly rom.
i read on the internet and even in this forum that i need to run a pds fix.
i tried that it fixed the phone for about day or two and then everything went wrong again.
i returned to the store where i bought the phone. they burned me a at&t original stock rom. that fixed the problem for two hours at most.
i wanted to know if someone knows how to fix it or did anyone encounter this problem.
thanks
Nir
Related
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).
Hi all, Yesterday I changed my set up from HD2Froyo_V3 to AmeriCanAndroid AOSP HD2 GB233 CM7|bkup2sdext234 [KERNEL:AmCanAndroid r3.06] Cyanogen CM7 (Gingerbread 2.3.3) (off SD card).
Installed and after some bugginess, it worked fine. It did eventually stop responding as before. I could use the hard keys to toggle it from sleeping/not sleeping, but it stopped recognizing any touch, anywhere on the screen.
So, I did a hard reset. Worked at first, then stopped working again.
So I went to T-Mo (even though I am using it unlocked on ATT) and updated the ROM to 3.14.531.1. Restarted, and still not working.
Bottom line: All the hard buttons work, but the screen does not respond. Was going to go through Task 29, but not sure if there is something else to do in the meantime
Currently:
2.15.50.14
15.42.50.11
3.14.531.1
Please help! Thanks
I had this problem before. It means the screen is dead. Call T-Mobile and have them send you a replacement phone.
Thanks for the reply- is that the only solution? I had originally searched "screen frozen" and didnt get anything that sounded like my issue. I have since found other posts with "screen unresponsive", but other than sending the phone back, there havent been many solutions.
Know of anything else to try before I do that?
Also to note- my phone/battery is not running hot at all like many others have reported.
Brian
T-Mobile Advice
Update: So I just got back from the Tmo store, and explained the situation to one of the guys. He sounded like he knew exactly what I was talking about, even mentioned his great site and how he uses it.
He told me that this was a known issue and had to do with HTC Sense-this sound right to anyone? He also said that there was an update to the ROM to correct it. however, the ROM is 2.13.531.1, which is older than what I just changed to- does this make sense to anyone? (http://www.t-mobile.com/wmupgrade/)
Thank you.
I bought my Blade 4 months ago and i have been noticing for the past few weeks that the touch sometimes has become less responsive, and only gets fixed until i reboot the device.
I noticed this behavior with SS RLS5, FLB, CM7 stable and a few nightlys. With CM7 sometimes it got worst being almost impossible to unlock the device, my finger goes to the right and the sliding tab goes to the left. And i have to press really hard until the touch responds. After i reboot it all runs normally for a while.
I am running gen2 (since almost i noticed this situation, maybe it has something to do with it...) and i always wipe everything when installing new roms.
Is this hardware failure?
Thanks.
I think when bugs like this happen after flashing a custom ROM a hard reset will fix them.
I think hard resetting after installing a new ROM is always good practice. Fixed my Galaxy Europa up when I upgraded it to 2.2
I don't think it's your ROM because I have the stock Orange ROM and have the same issues. The screen will become entirely unresponsive to touch and only a restart will fix it. Does anyone else have this problem?
How strange, I've had my phone for a while now and this has yet to happen. Too many apps running?
Modaco is probably a more likely place to find the answers you're after.
Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.
I think pds is unique for each device so other pds won't work on your phone. Correct me if I'm wrong.
Sent from my MB860 using XDA Premium App
Andy_Thatcher said:
Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.
Click to expand...
Click to collapse
pds are for their individual phone but there is a generic one on the forums for touchscreen fix. you are going to have to search for it.
did you do nandroid restore? which recovery? tenfer?
Really unsure to be honest.
Kinda hoping that isn't the case but if it is it is.
Have seem a couple of PDS's here but apart from one once they haven't made a difference so am trying for a definite match to find out.
My screen behaves normally until the phone starts to get warm then...well if I didn't know better I would think it was hacked with random key presses left and right.
Take out the battery for 10 minutes and get another 15 minutes or so and off it goes again.
Edit -
Managed to get some form of stability with the Aura ROM with Faux's Kernel and SetCpu under clocked....have managed to lose Wi-Fi in the mix somehow.
Could be time just to bite the bullet and buy a new one as I am due an upgrade. NOOOO enough of that defeatist talk !
Regrettably I do not have a back up of the original PDS, managed to miss that as being a requirement pre-boot unlock.
I have 2 PDS's from here I have found on here but neither seem to be a permanent fix. One is khoulk's (sp?) but I think that is from a non standard phone and another one that worked....briefly. I also have 2 from my phone but alas they were after the issues started so have doubts about them.
Just changed the CWM from tenfer's to the new one.
At present just playing around trying to get wifi back on the phone, then I will go back to the pds hunt.
Oh just for kicks it seems that I can't download from the market either at the moment. It starts but then after a few seconds stop.
I managed to get the phone to behave normally by going back to 1.2.6.
Then used OTA's to get to 1.8.3.
All stable at that point then SBF'd 4.5.1 with pudding and pre root and then....
Everything went to pot again.
Currently heading back to Froyo and will OTA again up to 1.8.3 and stay there for a while and consider my next move. Trouble is that I really need a working stable phone. so will do the smart thing next time and get a nandroid back up of the 1.8.3 and a copy of the PDS.
Try using the method described in this thread:
http://forum.xda-developers.com/showthread.php?t=1131649
It will fix both touchscreen issues, as well as the problem described in the thread. It worked for me...
Thankyou.
I had already tried that and first time it worked a treat alas not attempt 2,3,4,5,6....
I have absolutely no idea what is going on with this. Currently when i try and turn on bluetooth it will sit and think for about 15 seconds like it's turning the radio on, then just fail and go back to thinking the radio is off. When i try to activate wifi it does the same, but says error.
I am running neutrino 2.7, but was seeing this on 2.6 as well. I did a full wipe and re-install last night, and installed apps one by one to try and find what broke it. I thought i had identified google voice as the culprit, but with that uninstalled and almost no other apps installed bluetooth and wifi broke this morning.
if i flash a radio it will fix it maybe once in 5 tries, and only for about 20 minutes or so, then it fails again.
this started last week around the same time AT&T started throttling my data for going over 3.5gigs. No idea if that is related.
any ideas, things to try, etc?
Make a backup and flash the stock rom and stock radio for that rom, see if it still happens. I've read of others having wifi and bluetooth problems, you may try reading in those threads.
Sent from my MB860 using xda premium
Problem!!
you resolved the problem??? any idea???
nope, not yet. I've tried other kernels, and other versions of neutrino (was on EE, tried GT), nothing. Even with a clean wipe it's being dumb.
Downloaded the stock AT&T rom in fruitcake form, going to try that next.
From some reading i think there might actually be some phones with a hardware defect where some soldering wears out and starts messing up the bluetooth/wifi. I'm praying that isn't my phone because i'm well out of warranty.
i have the same issue on CM9 as of yesterday. no amount of wipes or different CM9 roms helps, haven't tried any GB roms yet though.
check this thread:
http://forum.xda-developers.com/showthread.php?t=1205775&highlight=wifi+error
i've read that.
flashed stock AT&T rom today, still have problems. not amused.
backing up my data, formatting all sd cards, wiping everything and trying again.
I'm with this problem too, Im running morrisoft rom since last month and I didn't any update, change configs or flash anything before It starts, so wierd...my wifi+bluetooth was working at night them in the next day it wasn't anymore lol..
(it happened today btw)
i ill try change my rom and see what happens...
same issue on a completely clean wipe. pretty sure at this point it's a hardware issue and not software.
I'll try the "fix" posted in the other threat at some point.
clean wipe has no effect. Wifi will sporadically work, bluetooth won't. I'm pretty sure based on how inconsistent the issue is this is a hardware issue. Not amused at all. No warranty left on this phone, and no upgrade until october.
This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")
taylrjones said:
This must be a pretty common problem. I had the exact same issue as OP, tried everything to fix it and nothing. Thankfully, I had an upgrade waiting for me. I tried to send mine in for warranty repair but no dice because of the bootloader being unlocked. (I even flashed it back to stock so that it didn't say "UNLOCKED")
Click to expand...
Click to collapse
They didn't want to repair it because they knew it had been unlocked? Are we talking about motorola?
same thing happened to mine..... it was a hardware issue, had it replaced...sorry..