I had a weird instance happen on one of my pros a little bit ago. I hope I'll be able to explain this well enough for someone to recognize it (i'm pretty tired).
I was charging my pro... i disconnected it from the usb, then went to turn the display off via power button and my screen turned black. Not off, but black. Even in this black mode, you could see fuzzy lines so it was obviously acting strangely (picture an old tv on an input channel not being used. Youd be able to tell the tv was still on...). The phone still functioned, i just couldn't turn the display off at all no matter how many times i pressed power on/off (I'd only get the strange fuzzy black screen). A soft reset fixed this right away... I just think it's weird that it would still acknowledge my power button presses by turning to that black screen... why couldn't it just turn off if it was acknowledging what i wanted?
Has anybody ever had this happen on any of their phones, present or past? I'm thinking this is just an isolated incident, but i'd like to know how rare of an occurance it actually is...
i'd hate to think i'm the only one that this has happened to.
I've had this same problem -- and so is a coworker of mine who has the same phone... we're running Juggalo's 0.06B ROM.
Hello, I have recently discovered a very annoying problem with the touchscreen on my Motorola Defy:
I have noticed that the touch screen acts strange sometimes, so I have installed a touch test application(Touchtest by Hermit). In this application I have noticed that if I touch the screen in two different points in a fast succession, a line appears between these two dots. This makes a lot of application that require multitouch pretty much useless, because I have to restart the application to have the touch screen working again.
Is there any solution for this? I have heard that this may be a software issue, so I have e-mailed Motorola, but they have not answered yet.
I have attached two pictures to illustrate what I am saying, one taken before this strange error, and one after pressing on two spots very fast. You can see the line connecting the dots in the second picture. I can make a video if you still can't figure out what I am saying.
Thank you.
Im having a very similar problem here on my defy. When I play games on psx4droid and when I keep pressing x key, it stops working for a while then I have to release the button and when I press it again, it stops working and it continues
I encounter similar problems with my Defy.
When for instance using slide to unlock , 1 / 5 sildes fails. I have to slide 2 - 3 times until it unlock.
It also scrolls very slow in applications and the same thing happens when typing a message.
Solution : Unse lock button.
It currently runs Pays ROM, but the situation appeared since I installed 2.2.1.
I don't remember having this problems on 2.1.
Don't know if the situation is only related to software but it is really annoying.
Found this info regarding touchscreen slowness, but I am using the original charger so it doesn't apply for me.
Motorola Defy Touchscreen Problem
I recently got my Motorola Defy,my Defy's touchscreen acts sometimes really weird, on keyboard it's hard to enter 'r' or 'b' and some other characters, it takes little while to unlock the phone, it automatically opens applications, I don't know if it's due to faulty handset or software, I am considering it returning to Phone4U and get a replacement handset.
What version of Android are you using ?
Same problems here, but I think it is a software issue.
I'm having the same problem on my Defy.
After a while, the multi touch stops. I posted on the Motorola Forums
https://supportforums.motorola.com/thread/44733
but no response.
I used YAMTT and when having two touches, after 20 seconds, one of them disappears
This is repeatable
2.51.1 UK with 2.1 Android
Well, it is clear that this is a problem that affects many Motorola Defy users. But I wonder if someone could fix this thing?
Looks like the new software version 2.51.1 did not fix this bug. I haven't tried it yet, but I see some of you have.
So it looks like our only solution could be a developer from XDA. Could someone help please?
This is ridiculous...i've sent my phone to motorola only because it was giving this problem and basically what i think is that their own software is causing this problem so i'll be waiting for 3 weeks and when i get my defy...it'll still have that problem...Ridiculous...
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
efpob said:
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
Click to expand...
Click to collapse
Defy doesn't support cynogen mod and 2.3
I was messing around today and even the single touch disappears after a while
30 seconds or so
Mine sometime stop response after few seconds
really wierd
Tell me who is on stock rom and is having problem..because im on 2.2 leaked..so i cant really say if u hv this problem on 2.1...
I got this response from a Motorola employee. Anyone know of a way around this?
Motorola Employee said:
If you touch the screen and don't move for a long time, the screen will eventually try to ignore that touch as it'll be considered invaild. That's what you're seeing. If you continue to move your finger(s), touch will continue to work. Also, when you release the screen, it acts to clear the invalid touch region that you generated earlier.
Click to expand...
Click to collapse
https://supportforums.motorola.com/thread/44733
have simular problems............100 procent hardware problem..... if i twist phone a little it will go back to normal for a while
any ideas for disable it?changing some parameter or something?
I have the same problem. screen sometimes go crazy. i am using stockrom eclair SEA 2.59. sometimes it seems that it tap icons or part of the screen even without I actually tap on something. and it seems it affect the capacitive button under the screen. I am not touching the search button but the search box suddenly appear.
I have to push the power button and unlock the screen to make it normal.
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
brjshshrma said:
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
Click to expand...
Click to collapse
i returned my defy months ago but what you can do is, try to flash cyanogenmod on your defy...that should fix the problem.
Hi, I've registered myself just a minute ago, reading the link that efpod left here and I've remembered that I charged my Defy with a Galaxy S i9000 charger friday (I've charged it once the batery was drained later with my original charger) and today it is failing A LOT, it's really anoying.
I got Cyanogen Mod (latest) installed on my phone so that doesn't fix the problem.
I'm uncharging it with "StabilityTest - CPU / GPU Test" and when the battery drains out I'm gonna charge it with the original one, after that, I'll test it during the day and I'll leave a messege to keep you informed.
Hey guys,
I have a really strange display issue with my Galaxy R.
I'm on CM10.1 nightly and already tried different nightlies with factory reset and wipe data/cache.
If the phone is not used for a while (sometimes even after 30 minutes), meaning it is on and screen is off, the display won't turn on anymore.
So I press the power button and the capacitive buttons light up, but the screen stays completely black.
Today I noticed that I can even use the touch screen and I could hear all sounds, I even managed to open the dialer and start typing blindly and it would make the dial sounds.
But whatever I try, the screen won't turn on.
Also, it seems when I'm connected to a charger and/or connected to wifi, this problem doesn't seem to occur.
Then I have no choice but to remove the battery, but then often I can't even start the phone.
Sometimes it takes some minutes, sometimes a really long time until I can start it again.
Usually the battery isn't drained, this only happened once.
This occurs after I dropped the phone twice, so it might be related to that.
(Though before I've also dropped it and this never happened.)
Any ideas?
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Nikhil said:
flash stock ics and see if problem persists.
once i flashed a custom rom and faced this issue, reverted to stock and now my device is running with zero issues.
Click to expand...
Click to collapse
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
wasabah said:
I tried to find the stock rom online, but all links seem to be down.
Do you know where I can get it?
Click to expand...
Click to collapse
You need to register and then download from here.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Thanks for that, I installed newest stock rom.
Could boot fine, set up the phone, put it to the side.
One hour later I checked it - same problem again.
Capacitive buttons flaring up, screen not.
Then you should visit SSC. They can only repair your device.
Hi, I've been using ViperS 5.1.2 for some time now on my Sensation XE, and it used to work great for me. But since a few days I've got this really annoying freezing problem and I just cannot find a solution.
The touch screen just freezes without any reason, sometimes after using the phone for half an hour, but most of the time within a few seconds after unlocking the screen. When it freezes, the screen won't respond to anything, also not on the back or home button. If I use the on/off button though, the screen will respond again for one or more seconds. This happens randomly; a lot of times I can't even unlock the screen properly, and the rest of the time I only get the screen working normal for a at most 10 seconds. This way it can take a few minutes just getting to the settings menu, for example. The phone does not report any error; after using the on/off button it just goes on where it froze. Also the phone reacts to tilting the screen. Or when playing a video, this just keeps playing normally. So it seems to be purely the screen itself...
I tried a lot to figure out what could be the cause of this problem: uninstalled a lot of recently installed or updated apps, checked the amount of free space/RAM, cleared cache, Dalvik, used nandroid backups to return to a previous (in the past good working) state, tried if removing the sd card would make any difference and finally flashed the rom again. All to no avail; the problem keeps occurring. At first, after trying out a possible solution like the ones I've mentioned, it looks like this did the trick. Sometimes the phone appears to work normal for at most half an hour. But then the problem occurs again, and will at that point occur at a high frequency.
I am out of idea's right now and am getting quite desperate. I need this phone to work properly badly, as I will go on my vacation in a few days and really need to be able to use some of my apps then. So I do hope somebody can help me out here? Any help would be greatly appreciated!
Does it do this while connected to the charger or usb.??
sent by v.konvict
v.konvict said:
Does it do this while connected to the charger or usb.??
sent by v.konvict
Click to expand...
Click to collapse
Yes, does not make any difference. I found today that the phone is now also acting strange in clockworkmod recovery touch, that's for the first time. Can't properly use the touch screen there either any more, only with hardware buttons. So now I guess this should really be a hardware issue. Maybe the phone is just dying...
Yess its a common thing for our phone to act that way while charging.... It has somtheing to do with its poor grounding. You can find threads to help u with how to solve it.
sent by v.konvict
My Nexus has a display problem and i'm trying to troubleshoot what the issue is and I'm wondering if anyone could help as it's not obvious where the issue lies.
What happened is I was using it as normal this morning and then the screen started flickering to different sizes/colours until it finally just went off. It was almost like it is trying to find the correct refresh rate and the colours appeared polarised at one point. After holding power down to reset it, the google logo appeared and then the spinning dots. Once the boot was complete the android logo appeared and then as soon as the main screen was displayed the display cuts off with a white pixelated mist and shuts off. The phone is still running as if I connect via HDMI I can see everything as normal however the phone responds extremely slowly. I can get into recovery however the screen quickly does some strange things, it flips like a mirror and cuts 1/3 of the screen off.
I'm not sure if this is a LCD problem as its a replacement from ebay that I've been using for a few weeks now. I would suspect that before anything else however it's odd the pre boot logos display fine. I've checked and cleaned all connections however it's still doing it. I'm running stock 5.1.1 rooted.