Just starting yesterday my Aria has been acting really strange. It started when I let the battery get under 5%. At times the screen is completely unresponsive, at others it seems not calibrated right (touching one point selects somewhere else) and then sometimes it will work perfectly fine after I do a soft reset for about 10 minutes. I thought it was a software problem so I did a hard reset, but same problems. So I flashed new roms / kernals, same thing. Could it be the battery? Cpu? I thought maybe the digitizer was bad but considering the screen works sometimes could that be it?
corber22 said:
Just starting yesterday my Aria has been acting really strange. It started when I let the battery get under 5%. At times the screen is completely unresponsive, at others it seems not calibrated right (touching one point selects somewhere else) and then sometimes it will work perfectly fine after I do a soft reset for about 10 minutes. I thought it was a software problem so I did a hard reset, but same problems. So I flashed new roms / kernals, same thing. Could it be the battery? Cpu? I thought maybe the digitizer was bad but considering the screen works sometimes could that be it?
Click to expand...
Click to collapse
**FIXED**
So in case anyone else has similar problems, I figured out what was wrong but I don't know why. I was messing around with it and trying different roms, so I took another microSD card I had to save time of switching them and everything works perfectly with the other one now. I had done a complete reformat of the old one so it must have just gone bad I guess?
Related
Looks the video and comment, or give me a fix:
I'm having a similar issue - only difference is that I'm on AT&T. My power button gets extremely hot, almost hot enough to burn your finger, and the screen and capac. buttons do not respond to touch AT ALL.... I've restored my pds partition backup, completely wiped and reflashed sbf (2.3.6) restored every NAND backup I have.... nothing... Started on Saturday morning - no rhyme or reason... just POOF. the volume buttons and power button still work (although its very hot) and it boots just fine.... I'm at a loss for ideas.
[edit] this is my original Atrix 4G that I got on pre-release day... never had any issues before, never had to replace it... until now, unless anyone has some ideas that will fix this...
Bump for replies.... Any ideas here guys? I've taken my atrix completely apart since my last post... there are no broken connections or any circuits that appear "burnt" or anything like that.... I'm really puzzled...
anyone have *any* ideas at all here?
Now using Epsilon5 Rom i have no bug, calibrating in Aroma installer.
I'm still searching for answers to my issue.... I'm glad you got yours fixed.... I'm seriously confused with mine...
Hi, I have a quick question.
My digitizer starts failing. I know in the end it should fails cause most of them need to be replaced but maybe my problem is different.
Most of digitizers are stop working at all or only some parts of it. My digitizer is working fine but ONLY after turning on screen sometimes it's working like using it with wet fingers - it's crazy pointing everything without my control. After turn off and on screen it's working fine until next turning on.
I'm wondering can it be software problem?? I had similar problem in Defy+, leds under hardware keys stop lighting and before sending it on warranty I wiped it and now all working fine.
It's no problem for me to replace digitizer or wipe system but it would be good to know that it can be software problem before buying new digitizer.
Maybe you need to apply the raindrop fix. Been discussed already.
First, thaks for understanding what I mean. (Very poor english)
Second, this is exactly what I ment. I just copied tounchpad.cfg from http://forum.xda-developers.com/showthread.php?t=1467696 and all looks fine now. No mess up on multitouch. I hope it will stop messed up touch while turning on screen, need to test it for a while cause this issue isn't appears on each turning on but ocassionaly.
Anyway thanks for fix. You saved my time (3 hours on wiping and bulding new system) and money on new digitizer.
One more thing. I'm using this phone from few months and everything was ok. The problem appears few weeks ago. So if it is bug in rom it should appears just after I bought it, not after few months. Or maybe it's not factory bug but just error in touchpad.cfg??
Sorry for post under post but I have few more informations.
After testing few days raindrop fix the problem still exist. Fix helped but not fixed problem. Still after turning on screen touch is acting crazy but after first touch it stops and before applying fix it stops only after turning off screen and turning it on.
I reflashed full sbf stock Gingerbread, full wipe including internal memory and still the same problem.
Strange thing I observed is the problem appear only when WiFi is on and it's searching or trying to connect. When WiFi is off or it's connected to router the problem never appears and when I turn on screen and after that turn on WiFi everything is ok. Only when I'm turning screen with WiFi on screen touch acting like crazy.
Is there any chance to fix it or should I buy new digitizer??
Ok, I changed digitizer on warranty and now everything is okay. Funny thing is that I have unlocked bootloader and they changed my digitizer without any problems. Less funny is that they broke both sensors changing it and I had to send My Atrix to Motorola once more after two days to change flex. But now I hope it should be working fine.
So after all it had to be popular hardware problem.
Thred can be closed.
Sent from Motorola Atrix
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
jfall said:
I have a Galaxy S3 that I have been running CM 10.2 on for quite some time. Today I dropped the phone and cracked the screen. The phone still worked perfectly in every way despite the cracked screen. I used it for a few hours after without any issues. I took it to someone today to replace the screen assembly. When I got the phone back it turns on and the screen looks fine but it hangs on the samsung screen for 3-5 minutes before booting in to anything (booting the rom, recovery mode, download mode etc. all take 3-5 minutes to start) when the phone finally boots the touch screen does not work at all. All buttons work fine, including the bottom buttons (back and settings) for touch but no where else does the screen respond to touch.
So far I've tried:
- wiping cache
- factory reset
- re-installed CM 10.2 rom
- Took the back off the phone and checked all the connections, unclipped and clipped back in to be sure they were connected ok.
- Completely removed battery and all sim/sd cards for an hour
At this point I'm not sure if I'm dealing with a hardware issue (maybe they guy screwed something up when replacing the screen) or the digitizer/screen he used is faulty? I know this doesn't neccessarily mean anything but when I got it back the new screen still had the protective film etc. on it so I'm almost positive the screen assembly the guy used was at least new.
And I don't really understand where the 3-5 minute boot issue could come from? I wouldn't think it would be related to the screen/digitizer but I suppose anything is possible. What could explain this?
Is there any way this could be a software issue or any other troubleshooting I can attempt?
Click to expand...
Click to collapse
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
suyash1629 said:
Go and talk to the person who replaced your screen.. maybe has used faulty screen and also may be he has changed with some of the faulty parts..
Click to expand...
Click to collapse
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
jfall said:
Very strange, but it looks like it was indeed a software issue after all. For some reason changing the screen out while having CM 10.2 installed did not play well together. I did a full wipe and went back to stock rom and touch is working now. I may try a new install of CM again to see what happens. Odd
Click to expand...
Click to collapse
Strange issue.. never had it ever, m flashing CM from more than a year.. Try to do a new flash downloading new files..
Hello mates.
I've got some issue with my desire x touch screen. It is becoming unresponsive.
The whole thing started like 1 month ago. I've noticed that as my phone gets hotter (playing games, using internet) my touchscreen was slowly becoming unresponsive. Firstly I was unable to scroll down my notifications (only the narrow bar at the top was not working) and then it came to a random places of screen, so I couldn't even write sms message. The thing is that it is not unresponsive at all. When I press certain unresponsive area it finally detects the touch. I tried everything, from wiping my screen with a soft tissue through removing battery and sim and sd card to wiping dalvik and cache. I've noticed, that after night the problem was almost gone. And again, after using phone for some time issue occured again. I figured that flashing a new kernel might be a good solution. And it helped and I was happy.
Unfortunatelly, yesterday problem returned. But as you probably suppose - flashing kernel ain't helping. I've also tried other methods mentioned above, but the only thing what helps a bit is leaving the phone unused for like 1 hour or so.
Do u guys have any ideas, what can I do to repair it or to fix it? Any help will be strongly appreciated
ptaq1234 said:
Hello mates.
I've got some issue with my desire x touch screen. It is becoming unresponsive.
The whole thing started like 1 month ago. I've noticed that as my phone gets hotter (playing games, using internet) my touchscreen was slowly becoming unresponsive. Firstly I was unable to scroll down my notifications (only the narrow bar at the top was not working) and then it came to a random places of screen, so I couldn't even write sms message. The thing is that it is not unresponsive at all. When I press certain unresponsive area it finally detects the touch. I tried everything, from wiping my screen with a soft tissue through removing battery and sim and sd card to wiping dalvik and cache. I've noticed, that after night the problem was almost gone. And again, after using phone for some time issue occured again. I figured that flashing a new kernel might be a good solution. And it helped and I was happy.
Unfortunatelly, yesterday problem returned. But as you probably suppose - flashing kernel ain't helping. I've also tried other methods mentioned above, but the only thing what helps a bit is leaving the phone unused for like 1 hour or so.
Do u guys have any ideas, what can I do to repair it or to fix it? Any help will be strongly appreciated
Click to expand...
Click to collapse
I have a similar problem after replacing touch screen. I have found the source of the issue, it could be similar to yours.
My touch screen at the bottom was glued to the LCD in a short line and the adhesive was probably touching part of the LCD cable that goes underneath. I used a hair drier to warm it up and lift off the touch screen. That way there is no bad interaction between the touch screen and the LCD. Haven't had this problem since but my touch screen is unfortunately a bit lose this way. Even now, whenever I push the navigation part of the touch screen too hard, the problem comes back. I will need something to isolate the bottom part of the touch screen from touching the LCD. I will keep you updated if I find a final solution. In the meantime, it could be worth trying it on your phone too.
I think I will just get S-OFF, revert my phone to stock and give it back for warranty repair Anyone of you guys did this? Did 7 vibrations at boot void your warranty?
I'm thinking about warranty repair, cause my bro has the same phone, but full stock, not even rooted. And he got simmilar problem to me, but with less intensivity (it just comes and goes once in a while). Also recently I got this phantom touch problem (after enabling show touch in options I saw my phone is detecting some touches in specific areas) So I think warranty will be the only option :/
Hey guys,
I got my Redmi note 2 yesterday and I'm having trouble with the touchscreen. sometimes it seems to be perfectly fine and sometimes it doesn't react properly. It seems to be worse in the right half of the screen. Sometimes I start scrolling and it works fine in the beginning, then the screen stops detecting my finger and when it detects it again, it opens the thing that my finger is on instead of scrolling.
I'm not sure if this is a hardware of a software bug.
Would calibrating the screen help? If so, whats the best way to do that?
I would usually try flashing a clean stock rom (the one it came with has some bloatware anyway) and test if that resolves the issue, but that's probably not the best idea if I decide to return it.
thanks for your help
alkoy said:
Hey guys,
I got my Redmi note 2 yesterday and I'm having trouble with the touchscreen. sometimes it seems to be perfectly fine and sometimes it doesn't react properly. It seems to be worse in the right half of the screen. Sometimes I start scrolling and it works fine in the beginning, then the screen stops detecting my finger and when it detects it again, it opens the thing that my finger is on instead of scrolling.
Click to expand...
Click to collapse
Try entering in the MTK Eng. Mode, then go to Hardware Testing->TouchScreen->HandWriting and try drawing some lines crossing the point where the problem occurs.
A friend of mine had a Nexus 5 with a malfunctioning touchscreen, doing a similar test we noticed that there was a full horizontal line where the touch were not detected so every vertical line we were trying to draw were broken on the point where the bad line were crossed.
Obviously in that case it was an hw fault.
EDIT:
Reading your post again, it seems a behavior caused by lag, so maybe it's a sw problem and not an hw one, especially for the fact that "it opens things instead of scrolling".
Does it always happen in the same point/area? Or is it totally random?
gnazio said:
Try entering in the MTK Eng. Mode, then go to Hardware Testing->TouchScreen->HandWriting and try drawing some lines crossing the point where the problem occurs.
Click to expand...
Click to collapse
I already did that and the results are very inconsitent. When I first tried it, it started drawing a line as it should, then it stopped and started again half a centimeter later, then it stopped again, and it pretty much went like that from top to bottom of the screen (at least on the right side of the screen, the left side worked better).
When I did the same test again, it didn't even draw lines, it just highlighted a few single pixels along the way that my finger was traveling.
And currently everything works perfect and smooth as it should.
It does kind of feel like a software-thing, but in my mind (correct me if I'm wrong) that should affect the complete screen equally and it just doesn't. I tried pulling down the notification bar earlier, from the top right of the screen and it just didn't work. I did a few tries and nothing happened. Then I tried pulling it down from the top left and it worked fine.
As I said it works fine at the moment, but I guess I'll make a few screenshots and a video of the problem, when it occurs again.
Ok, so the problem came back and I was able to do some more testing and make a video (sorry about the shabby quality, but it'll have to do ).
youtube . com / watch?v=rKsponNr9lA
As it turns out, the whole screen is affected equally, so I'm pretty confident that it's just the software but I'd still like to hear a second opinion.
The thing that kinda throws me off is that the reboot didn't help at all...
So what do you think? Is it just buggy software?
I'd try contacting the seller and explaining him the problem.
Maybe he will ask you to flash a new rom to be sure that it's a hardware problem and not something that could be solved without a replacement. That's what happened with my first phone from China.
If not, you could ask him and I think he will authorize you.
gnazio said:
I'd try contacting the seller and explaining him the problem.
Maybe he will ask you to flash a new rom to be sure that it's a hardware problem and not something that could be solved without a replacement. That's what happened with my first phone from China.
If not, you could ask him and I think he will authorize you.
Click to expand...
Click to collapse
sounds like a good idea, I'll do that.