[Q] Atrix Touch Screen Issues - Atrix 4G General

This seems to be a different issue than what I am finding in a search so I figure i'll make a new thread.
My wife's atrix (seemingly since the gingerbread OTA update and non existent previously) has an issue where the launcher section of the touch screen will be inoperable sometimes after unlocking. This means you can hold it in portrait mode, unlock it and not be able to press any of the buttons, then turn it landscape, not be able to press any of the launcher buttons (where you could before). Its inconsistent so its hard to find a cause. It doesn't seem to be a problem with the digitizer because in different screens the sections work which don't on the launcher.
Here is what I know:
-Problem occurs with stock motoblur launcher, launcher pro and launcher 7
-Sometimes pressing the keypad to unlock the phone will only cause the bottom buttons to light up.
-Seems to be a software issue because the unresponsive section of the screen becomes responsive in a different context.
Here is some history:
-Few months ago it was dropped in milk which caused everything to get all scewy. I took it apart and cleaned it with isopropyl (this phone is great for teardown), reassembled and everything worked fine. I don't think this situation is related because the problem only occured recently after the 2.3.4 update and worked fine on froyo for months of heavy use.
-Did a master clear after the problem started since OTA updates aren't always the best.
I plan on flashing a rom on it tonight because it seems like it might be a software issue but has anyone else experienced or heard of this problem? All my searching on google found dead or unresponsive sections of the touchscreen but never a situation that matched mine. Sorry for the long post, just didn't want to have to make 1,000 replies to common questions.
Edit: Another example. In a text message window touching the "enter" key in portrait mode causes the digitizer to register either the enter key and the delete key or no register at all. In landscape mode, the done button does not work (same section of the screen that didn't work before). Hit the home capacitive button and the icon in that section works just fine. Additionally this time in a text message window before the keyboard comes up, you cannot get it to register in the compose section to bring up the keyboard but if you press home the launcher buttons in the same section work just fine. Very confusing problem.

I would try SBF'ing back to 1.2.6 to see if the issues remain.
If everything works as it should chances are it is a software issue if not you may have to risk the $30 and replace the digitizer.

Nonono do not SBF back if you did the OTA to gingerbread it will brick your phone. That guy is an idiot.
Sent from my MB860 using XDA App

jadwv2210 said:
Nonono do not SBF back if you did the OTA to gingerbread it will brick your phone. That guy is an idiot.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I completelly agree with him NEVER EVER do a SBF downgrade if you did the OTA... this guys knows nothing...

Don't downgrade!!!!. I had the exact same issue except it was near the notification bar.. its hardware and has to do with faulty rain drop detection, call at&t. They'll make you try all sorts of **** from wiping it to pulling the battery and sim and sd out.. after none of that works they'll send you a refurbished atrix .. good luck
Sent from my MB860 using XDA Premium App

This kind of sounds like a PDS partition problem. Did you ever backup the phone then restore it? CWM doesn't properly restore the PDS partition, which has data in it for calibrating / controlling the touch screen. There is a way to restore the PDS which might be an option for you.
I wouldn't start with a PDS restore though. I had problems with my touch screen randomly not responding a while back and a wipe of data, cache, and dalvik fixed the problem for me. I would start there, since you mentioned that you wanted to flash a ROM anyway. The first step to doing that is wiping.
If that doesn't work, and assuming its not a hardware failure... the PDS fix would probably be the next logical step.
This thread:
http://forum.xda-developers.com/showthread.php?t=1131649
has a PDS fix file attached to it, and instructions on how to get it onto the phone via ADB.
I suggest making a backup of your own PDS file first, just in case. The following commands will make a backup of your PDS file to the root of the internal SD card.
Enable USB debugging, set USB connecton to None.
Open a command prompt window, navigate to where ever you have adb and use the following commands:
adb shell
su
dd if=/dev/block/mmcblk0p3 if=/mnt/sdcard/pds-backup.img
exit
exit
You will now have a backup of the PDS partition on the root of the internal sdcard and it will be called pds-backup.img. At this point you could try to restore the PDS partition in the thread I linked above, as if the problem is with the PDS, that should solve the issue.
The other possible solution is an SBF flash...
**BUT THIS SHOULD BE YOUR LAST RESORT**
A small number of people have reported hard bricks even when using the SBFs that come with pudding.
If it was my phone... I'd wipe data, dalvik, cache, install a new ROM and see if that fixed it. If not I'd flash the PDS fix I linked above. If that didn't work... I think I'd go for the 4.1.83 SBF with Pudding as I don't recall hearing about a single hard brick with that one, as opposed to the 4.5.91 SBF with pudding which did result in a small number of hard bricks.
Let me know how it goes.
DK

Odd that when you try and help someone whose thread was unanswered at the bottom of the second page the immediate response is to abuse rather than point out where they were wrong.
So that is a lesson learned on this forum.

Andy_Thatcher said:
Odd that when you try and help someone whose thread was unanswered at the bottom of the second page the immediate response is to abuse rather than point out where they were wrong.
Click to expand...
Click to collapse
Many people have bricked their phones, which is something we all try to avoid having happen to others. Don't take it personally
DK

Andy_Thatcher said:
Odd that when you try and help someone whose thread was unanswered at the bottom of the second page the immediate response is to abuse rather than point out where they were wrong.
So that is a lesson learned on this forum.
Click to expand...
Click to collapse
I'm not trying to be a **** or anything, but you shouldn't be giving advice on something when you clearly don't know what you're talking about.

To op. I think I may have had the problem you're describing happen a couple times in the last month. It happened today. I couldn't do anything but keep changing landscape. After about 15 seconds everything went back to normal. I think you're ok and its a very small nuisance to have to deal with. Unless it doesn't give the screen back to u and u have to pull battery. Then keep searching for answer.
Sent from the coolest voided warranty phone ever.

its a very odd issue. Thank you for all the replies! I am going to clean the underside of the digitizer tonight to make sure there isn't any residue from the initial cleaning.
I had never done a backup/restore or anything to her phone prior to last night. Its currently on pie crust and running fine except the same problem is happening. I downloaded a "touch screen test" app and when it happens, its clear that a section of the screen is dead. Here is the weird thing, touching near the screen will trigger the home button under normal conditions. Touching the same spot while the error is occurring triggers whatever is above the home screen. I've also confirmed this with the touch screen test where touching the upper part of the digitizer (near the earpiece) will automatically trigger the bottom center of the screen. I am no professional but that sounds like a short to me.
I am going to read about the PDS partition thing just in case it becomes something worth trying, thank you for passing that along! It may be something she can live with (though it is frustrating) but for some reason its bugging the hell out of me. My captivate with a giant crack in the front has a more reliable touch screen right now
ps. I will not be downgrading to anything =) Thank you for your post though, it did bring the thread back to the top and get some responses!

Related

[Q] Touchscreen semi-unresponsiveness?

I've looked around and a lot of people have fully unresponsive screens. However, mine is I guess semi-unresponsive?
I can perform all my functions fine, but when I try to power down my phone via power button. It pops up the power menu and then my screen becomes completely unresponsive. I can only use the hard buttons, but nothing on the screen works. When I press the power button again to go into standby, it'll work like normal and my screen works again, all until I try to go to the power menu again. Does anyone know what is wrong?
I forgot which HD2 I'm using, but I know I bought it in the June of it's release and I'm in the US.
My current ROM is HyperDroid-GBX-v12, but I don't think it's a ROM issue since the previous ROM I had was even worse, same problems, but unresponsive at the lock screen at times.
Thanks, and let me know if I can give any other info.
Has this been happening since you flashed the Rom or is this a new problem?
This has just started happening. I think it was present to a lesser extent before, but I am noticing a lot more recently. I flashed a new ROM because I thought it was my old ROM, but the problem isn't going away.
For a work around, download the quick boot app from the market and power your phone off that way.
What Rom are you running now btw?
My current ROM is HyperDroid-GBX-v12,
Thanks for the work around, but I'm really wondering what the problem is since it persists between ROMs. I'm thinking hardware, but then it's so specific that I'm not sure.
The only other think I can think of trying to wipe your phone via CWR by formatting data, boot, system, Sd-ext (if applies), cache, and Dalvik cache. I know you re-flashed your Rom already but did you do a full wipe prior? It could be data corruption from the previous Rom. Just trying to troubleshoot
I'm currently having touchscreen issues myself. At first I though mine was totally hosed but then I read on some thread if you press the power button hard it can revive the screen. It worked for me. I assume there must be some loose cable somewhere beneath the power button that's causing these issues. It's probably just a coincidence that it stops working when you hold it down and you are really having the same issue as me.
I did wipe everything, but now I think of it I think I forgot to format my SD card. I'll try it now thanks.
Nope, still doesn't work. I'm at a lost for what's wrong right now =\
JesusFreak316 said:
I'm currently having touchscreen issues myself. At first I though mine was totally hosed but then I read on some thread if you press the power button hard it can revive the screen. It worked for me. I assume there must be some loose cable somewhere beneath the power button that's causing these issues. It's probably just a coincidence that it stops working when you hold it down and you are really having the same issue as me.
Click to expand...
Click to collapse
Be careful about mashing the power button too hard. I already have broke one HD2 because the power button cracked.....
telmedragon said:
Nope, still doesn't work. I'm at a lost for what's wrong right now =\
Click to expand...
Click to collapse
Sorry to hear this. Like I said earlier try using Quick boot. It won't fix your problem but at least your phone will still work. Sorry I couldn't be of more assistance....

[Q] Black Screen...

Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
It sounds like you're suffering from some sort of hardware failure. You need to send your phone in for repair/replacement.
The Unnamed Time Lord said:
Hello all. First let me state that I rather not make a thread to ask help on a problem that seems to have happened to a few owners, but my knowledge as to how I could resolve the issue is severely lacking..
At some point today my phone was ringing but the screen would not show. I thought about taking the battery out and turning it back on but there would be no HTC, Bootanimation, anything. It was Just a black-lit screen which responds due to tactile feedback and the four touchkeys light up as usual. At first there was an odd sound that would play after a few minutes so I decided to charge it but again there was nothing. Even tried to access bootloader with -Vol and Power still no screen.
I asked a friend of mine to call my phone to see if it would ring but they said it instantly goes to voicemail as if my phone was off. Note that I WAS SURE IT WAS ON.
Adb seems to work with it as it seems whatever I need to do I have to do it through there.
G2 rooted with gfree method
CM7.1 RC1
Clockwork Recovery
Again i am sorry if I bothered those with posting something others would think is "too common of a problem" as I have no experience in fixing this issue. Plus I would like to try any option available as I would not like to try and have my phone replaced (because of the risk of discovering root and obtaining a G2 with stock gingerbread which is currently not rootable)
Please help..
Click to expand...
Click to collapse
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Same issue here...
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
then i shut it down, pulled the battery and then back, and restarted: the phone goes directly to that black backlit screen, i tried several times and tried recovery with no luck, so i thought my phone was messed up although i did have some haptic feedback, well in fact the phone was actually booting, but just not showing anything else than the backlit screen; i waited a minute or so to the booting completes (still shows nothing), then i lock/unlock the screen again and there it is, asking for the pin code.
I tried to go to the recovery again to try to wipe dalvik-cache, i know for sure it goes to recovery, but with a totally black screen, not even backlit this time; the trackpad is too sensitive in the recovery to just blindly navigate in the menu, so it is not useable at all.
Then i had the idea to go to Rom Manager, i reflashed the rom from my sd-card, and enabling wipe dalvik-cache, which worked (all through a black screen). After a few minutes i "felt" it rebooting (vibrating) but still back to that black backlit screen, and i locked/unlocked it again and back it was asking pin code...
I also tried to roll back recovery to 3.0.2.4, since i remember i updated it a few weeks ago, but still the same issue.
I don't know what else to do without accessing the recovery, i wanted to try another kernel, or remove the trackpad wake... is there a way to do it via a script? I guess it's what Rom manager does...
Next step will be a total wipe, but i need to make some room on my sdcard for backup purposes first...
If anyone has an idea to sort this out, i'm highly interested...
I'll try to get a logcat, maybe could give a hint
Edit: Virtuous sense 2.0.0 (used it with no issue since it came out, could it be a hw issue?)
Edit2 : attached logcat
Is the pin screen differant than the usual one ie white number keys? If it is that's the sim lock screen you need to call the carrier to get the code or find out the default. Or just get a new sim lol
nah it's the 4 digit pin code, i didn't lose it btw, it's still working and i can use the phone, but i have a black backlit screen whenever i want to wake the phone, and thus when i receive a phone call, i don't know who it is and i blindly press/swipe the screen to answer, because if i want to use the same trick of locking /unlocking, it doesnt work as the lock button is also used to reject a call...
Maybe rip and reinstall the phone app?
asim0 said:
I'm facing the same issue, when i try to unlock the phone (power button or trackpad) the screen lights but stays black, and the buttons are also backlit. I have to lock again with power button and unlock again to get to the actual screen.
It first happened a few days ago, and since i didn't reboot/restart in weeks i tried to reboot but the same issue comes back.
Click to expand...
Click to collapse
I have the same exact problem as this EXCEPT, it's intermittent. Sometimes when I wake the phone I get an all black but backlight screen, and other times it's fine. I'm on CM7.1.
But a superwipe and reflash will probably fix it. Also don't restore system data on TB
I know i still can use wipe data + cache + dalvik through rom manager, and i always used to superwipe before switching roms, but how can i do that now when the recovery is all blacked out?
can anyone guide me to a script or something i could do while the phone is active, to tell him to reboot to recovery and flash that superwipe?
anyway i'll try the regular wipe and keep the thread updated
---------- Post added at 02:42 PM ---------- Previous post was at 02:35 PM ----------
SuperDave81 said:
EXCEPT, it's intermittent.
Click to expand...
Click to collapse
On my side if i leave the phone locked more than 30 seconds, it happens 100% of the time; also I noticed that now the backlight blinks 2 or 3 times (1 second blinking) when locked, first a few minutes after locking, and then randomly, about 3 or 4 times per hour; I guess it's getting worse;
I've read on another thread that it could be video cable getting loose, but since mine is still under guarantee, i won't open it right now just to check, if i can't fix by wiping / superwiping (when i know how to), i'll use that guarantee, which is one month left (lucky me)
EDIT: one other thing that makes me think it's no hardware, when the black screen appears because of a phone call or a message, the ringtone and notification sound are both half as loud as they should be, this is all really strange
after backing up my data, i reflashed the rom via Rom Manager, and I wiped data and cache (which equals to factory reset) this time: the first screen that should show the pin code numpad was already a black (backlit) screen!!
Also, thinking about it, i realised that the "flash rom from sdcard" menu in Rom Manager is in fact "Flash ZIP from sdcard": the zip doesn't have to be a ROM!!
So I tried flashing a new kernel this way, also some framework modifications (extended settings, removed TP wake, etc...) they all install Ok, but still this black screen...
Also I was about to flash SuperWipeG2.zip this way, but if it doesn't fix my problem, I will be stuck with a blacked out recovery, as SuperWipe wipes everything including /system; so if anyone has an idea to tell Rom Manager to flash two zips (Superwipe then Rom) i'll be willing to try, or a script to do that;
Maybe i'll have a look of the scripts in Superwipe and in the rom, and put both zips together... don't know if it's possible?
Maybe I'll try the Superwipe alone if I can get a spare phone, just in case...
Other thing:I used the phone's gps for more than 5 hours with the screen lit, and it never flickered even once; so it's hard to believe it's a screen connection issue...
Just to keep this updated, everything i did, including superwipe didn't change this issue, so i sent it back to the technical support (under guarantee) and I got it back today; the report that came with it says the screen has been replaced; so it was hardware finally...
Hi, i have same problem.. Black screen in recovery and during the boot. When the system boots, screen is OK. Sometimes i have also blackscreen when I want to use HW keyboard. I tried 4ext, reflash older versions of CW but still the same. I can see a screen through Android Screen Monitor and I can cotrol it. But phone is blak, only backlight. Can somebody say, how to solve this issue?
So, for other, if you cant see screen, you can use Android Screen Monitor for Windows and connect phone through USB and see a screen.
G1ForFun said:
A. They don't care if its rooted.
B. You can root stock Gingerbread.
Click to expand...
Click to collapse
WAIT one minute... they don't care? where was I when this meeting took place?
I had this issue as well on a spare G2 I had.
The screen was just black but you could tell it was lit, hardware keys were lit as well.
The phone was actually my brothers and it rooted w/ CM7.
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
I never attempted to get it replaced and kind of wish I did now if they don't care about the device being rooted.
I purchased my G2 before he had his, and it's never had the issue so not sure what to think of it.
Saintfyre said:
I ended up selling the phone as is on Ebay but after some research it was a failure in the hardware for the screen and I found extensive instructions on how to replace it that I didn't wish to do.
Click to expand...
Click to collapse
I think I have similar issue, can you post where you found those instructions?
Thanks in advance!
http://www.youtube.com/watch?v=u-dR8CHEGjY&feature=youtube_gdata_player
Sent from my HTC Vision using XDA Premium App
I used the same tutorial to change the LCD but after I put the new its just the backlight but nothing else... I will give it another go maybe and have a look again at those ribbon cables! I guess...
---------- Post added at 10:59 AM ---------- Previous post was at 10:09 AM ----------
I found on ebay: HTC-Desire-Z-T-Mobile-G2-A7272-Slide-Flex-Cable-Ribbon
or I found also with the chassis for a bit more.
Thinking to buy this, it would be great if anyone could confirm that it would help "my condition" ?
THanks in advance!
In terms of cables, yes the flex cables are what you want.
Sent from my T-Mobile G2

SCH-I800 Galaxy Tab 7.0 touch screen flipped

So I've finally gotten my tablet to work on stock firmware (2.2 i believe)
The touchscreen has flipped somehow. In order to unlock the device, I have to swipe down to unlock and up to silence. Once I unlock, I have to swipe from the right side to the left to get the top menu to drag down. Then I can kind of figure out where to touch to hit each button.
Anyway, this is terribly annoying. It's as if my digitizer is flipped. Anyone had this issue?
EliteEmerz said:
So I've finally gotten my tablet to work on stock firmware (2.2 i believe)
The touchscreen has flipped somehow. In order to unlock the device, I have to swipe down to unlock and up to silence. Once I unlock, I have to swipe from the right side to the left to get the top menu to drag down. Then I can kind of figure out where to touch to hit each button.
Anyway, this is terribly annoying. It's as if my digitizer is flipped. Anyone had this issue?
Click to expand...
Click to collapse
It's may be a sensor problem, try to deactivate the auto-rotation and reboot your device.
EliteEmerz said:
So I've finally gotten my tablet to work on stock firmware (2.2 i believe)
The touchscreen has flipped somehow. In order to unlock the device, I have to swipe down to unlock and up to silence. Once I unlock, I have to swipe from the right side to the left to get the top menu to drag down. Then I can kind of figure out where to touch to hit each button.
Anyway, this is terribly annoying. It's as if my digitizer is flipped. Anyone had this issue?
Click to expand...
Click to collapse
i must send u to 2.3.5 stock and gather 10 forum messages
http://forum.xda-developers.com/showthread.php?t=2383201
need_elf said:
i must send u to 2.3.5 stock and gather 10 forum messages
http://forum.xda-developers.com/showthread.php?t=2383201
Click to expand...
Click to collapse
Edit: Found the download, file is corrupted.
I also made a mistake, I'm already running on 2.3.5. I will try the download again and see if I can rerun it all with heimdall.
I just tried like 3 different stock roms
Honestly I'm about to give up. If I use any ROM except stock it won't boot up whatsoever (tried cubed 3 or whatever too).
Ive tried to load CM10 but my tab won't see the SD card with the zip file on it even if I follow the instructions to a T
I'm done with it for a little while. Thing is useless. Digitzer is flipped for NO reason. To make matters worse, it can't even find WiFi signal, so it's useless anyway.
don't know about CM10 for CDMA, but for GSM, there is one version of CWM where the external SD and internal SD are swapped around at recovery.
But it is easy to spot which is which if you know your own storages.
I have CDMA so none of those fixes for GSM will work since apparently the hardware inside has slight differences

Part of screen not working

For the past few weeks I noticed I couldn't respond to posts unless I removed the keyboard and brought the button to the bottom of the screen.
Then I realised that area of the screen just did not respond to anything, like in contacts I couldn't select letters in that area.
I enabled screen touches and they were showing up but there was no response from the OS.
I did a search and one fix was to clear the cache in recovery, which worked for a few hours maybe.
The next step is factory reset which I'll do if it's a permanent fix, but I'd rather not otherwise if I really just need a new phone.
No root so any backup will not be a full one so I'd rather just start again on a new phone if that's what it takes.
Has anyone had this?
Mine is the international version.
Well, today I mentioned this to work mate as it's been rather annoying so I prepared a screen to show them the issue at the store and now it's been working ever since.
Up until at least yesterday it was still happening. Very confusing as I was going to bite the bullet and backup what I could and try a new phone as it doesn't seem like a widespread problem.
Part of Touch Screen not working
I have the same issue with my S7 Edge too. It's really annoying especially when you are typing a message and can't send it because that particular area of the screen is not responding to touch. Now I have to type in a message and close the keyboard just to bring the send button down and tap on it. The issue gets solved when i restart the device but the problem continues after a few hours of normal use. Does anyone have a solution to this , Please?
Ok, my phone did reboot last night so it will probably come back.
You have exactly the same symptoms as me.
My girlfriend has the AT&T version of this phone and she has had the same exact problem the past few weeks. Like someone above said, it's right where the send button is in the SMS app.
I wonder what this issue could be?
Sent from my SM-G935F using XDA-Developers mobile app
Well, you can blow me over with a feather as mine has been fine now for about three days, since I was about to show them in the store and ask for a new one.

S8 Touchscreen Issues

So my touchscreen is acting really weird and I can't pinpoint exactly what the problem with it is. Im planning on just sending in the phone for repairs, but wanted to post here as a sort of "last-ditch effort" to see if there is anything else I can do.
I've already done a factory reset of my phone (and it seemed to work a little bit better) only to start acting up again like 10 minutes later. Safe mode doesn't resolve the issue. I can't swipe to unlock my phone and pressing once either doesn't work or registers as a long press. Everything is telling me this is a hardware issue, but it started happening randomly with no screen damage and there seems to be a pattern to when the touches register and when they don't, so it might be a software problem albeit a very weird one.
This is what the touchscreen input should look like: https://i.imgur.com/qhTNgq9.gif[/url]
This is what the touchscreen input actually looks like: https://i.imgur.com/DFtMVSz.gif[/url]
Any help is appreciated. Ask me anything, ill try to get back as soon as possible.
Also, if this is the wrong place to post this, please direct me to the correct place.
I think really the only thing you might be able to do is reinstall the firmware, if that still doesn't fix the issue then it probably is some sort of hardware issue
Things you can consider
- After a Factory reset, try using your phone without installing any "other" Apps except the ones from Google. / or / using it in Safe Mode ?
- I am sure you might have already tried removing the tempered glass
- Did you try the *#0*# and test Touch ?

Categories

Resources