All of the sudden (I didn't drop it or anything) my DX2 just displays garbage. I tried pulling the battery, etc. Even went as far as opening the phone to reseat the display cable, just to see.
The display, backlight, and the touchscreen, it seems, all still work, but the phone is useless since it just displays random (well, sort of random) garbage.
Anyone seen anything like this?
I see you can buy screens off of ebay, but have a feeling the problem isn't the screen itself, but maybe in the graphics hardware.
Any ideas? I'm 2 months from being eligible for a discounted upgrade
Nope none here (knocks on wood) and no clue sorry
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
Are you on a custom ROM? If so, perhaps a reinstall. Or maybe a data/cache/dalvik wipe? Nandroid first of course.
Sent from my MB870 using xda app-developers app
OK, thanks. I got it to reflash. No help. It's definitely a hardware issue.
Umm 1 hold up+power goes straight into rsd protocol
don't be scared it's only a phone
ogd x d2g x2 sg3
old ladies ^
OK, thanks.
Got it to reflash. Still no-go. Definitely a hardware issue
Related
So ive had my eris for about a year now. And now when i plug the usb in to charge the phone, the touchscreen goes all wacky. The phone basically loses full functionality. The light up buttons dont function, you have to try multiple times to get the screen to recognize your finger swipes, etc. If you press on the plastic of the phone around the trackball/usb port the phone goes wacky on screen clicking stuff itsself.
Im guessing something is weirding out with the connections in that area or something making the phone do stuff itsself. I bought the phone from a person online about a year ago, would HTC covery this faultyness of the phone? If so how would i go about the process/how long does it take, etc. Are there any home remedies(taking apart the phone and doing something, etc.)?
Thanks
Bump. My bros Eris does the same. Plug it in and the screen will go all the way to the left and select things. Would really like to see an answer to this
Sent from my Eris Lightning 3.02
Mine does the same. I have noticed that if you unplug it and hit the end call button twice to turn the screen off and then on that it behaves again.
Does not matter which ROM I use, I see the same behaviour.
Sent from my FroyoEris using XDA App
Well my phone started scrolling by itself when on the charger. I googled it and apparently the charger port is messing with the trackball. I called verizon and have a warranty replacement on the way.
To emerica243, sorry to say you have no warranty on the phone since you didn't buy it from verizon so your kind stuck unless you have insurance on it, then you could just file a claim. You'll have to pay the deductible but its cheaper than buying a new phone.
To everyone with this problem that bought from verizon, I suggest calling verizon and getting it replaced. I also suggest reverting your phone to stock just in case (see sticky in development forum).
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype
orkillakilla said:
Well my phone started scrolling by itself when on the charger. I googled it and apparently the charger port is messing with the trackball. I called verizon and have a warranty replacement on the way.
To emerica243, sorry to say you have no warranty on the phone since you didn't buy it from verizon so your kind stuck unless you have insurance on it, then you could just file a claim. You'll have to pay the deductible but its cheaper than buying a new phone.
To everyone with this problem that bought from verizon, I suggest calling verizon and getting it replaced. I also suggest reverting your phone to stock just in case (see sticky in development forum).
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype
Click to expand...
Click to collapse
This. It is a known hardware issue that HTC didn't forsee happening where the trackball sensors aren't quite insulated enough and make contact with the charger sleeve when it is plugged in. It will escalate to a permanent problem and there isn't a solution except to take the phone back in to Verizon and have it replaced. I'm on my second Eris because of this problem.
zerocool79346 said:
This. It is a known hardware issue that HTC didn't forsee happening where the trackball sensors aren't quite insulated enough and make contact with the charger sleeve when it is plugged in. It will escalate to a permanent problem and there isn't a solution except to take the phone back in to Verizon and have it replaced. I'm on my second Eris because of this problem.
Click to expand...
Click to collapse
Up and I'll tell you if I have to keep getting a replacement cause of this I'm going to raise hell with verizon tell they either give me a diff phone or I'll just go to sprint
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype
This is my second Rezound (I got this as a replacement from Verizon). Everything has been working fine for the past 2 months, but recently the screen won't turn on at random times. The screen seems to get stuck in the off mode and I have to do a battery pull to get it on again. Everything else is working when this happens, like I can hear people calling and hear emails coming in, but I can't do much without the screen! I noticed that it happens often when I'm in phone calls... the proximity sensor won't work after the first time I hold it to my head, the screen just goes off and then stays off. Sometimes (rarely) the screen will turn on when I press the power button, but then turn off as soon as the screen is touched (which makes me want to break the phone).
I hope this makes sense. Any ideas from anyone or I am on to my third replacement phone? Will they even replace my phone again? I bought it back in December.
They will replace it again, and it does sound like a hardware issue.
Sounds like you need a replacement
-- Sent from my TouchPad using Communities
happened on my incredible on a few custom roms, and then it happened on my rezound stock not rooted too. it's an HTC issue, probably.
had the exact same problem on my rezound. busted proximity sensor. Verizon replaced it with no hassles.
Thanks for all the input so far people! I'll be getting in touch with Verizon.
I got my new replacement Rezound today and now have a new problem where the phone will not allow data connections. I finally got Verizon to let me switch to a different phone. This will be my first non HTC phone since 2004, starting with the i-mate JAM. I am so glad to be done with the Rezound finally.
damn sounds like u have bad luck with thus phone
Sent from my ADR6425LVW using xda premium
I was having this problem consistently too with both GB and ICS when I was using custom kernels. So far, only the 2 most recent 3.0 ICS leak kernels have stabilized the problem to the point where I haven't had a reboot or freeze in a couple weeks.
So my bro's had an Atrix for a little over a year.
Some time back, it started exhibiting this behaviour where the whole screen would just become totally unresponsive.
Searching around, I see issues where people lose responsiveness with a fraction of their touch screen, or the entire screen starts spazzing out with all these presses and swipe actions the user did not enter...
...but his just seems to have these periods. He'll be stuck at the lock screen from anywhere between 1 minute and a whole day... I can usually get it to work with random rapidfire hardware commands... and when it works, it works completely for a certain amount of time.
Thing is, that's only temporary, and the touch-screen ends up going back to an unresponsive state.
Any clue what's going on, or how to resolve it?
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Sent from my ATRIX using the Premium XDA App
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Yep, that's right. The over-priced, highly (over)rated $20 iShields brand one. I know for a fact that was the cause, after I figured it out and started talking to other atrix owners (minus the liar fanboys that lurk in every forum saying "works fine for me derp!" whenever someone dares to suggest a product has flaws).
Problem immediately went away, forever. I've gone naked since May /11 without a single scratch. IMO screen protectors on gorilla glass is for people who wear a seat belt in a car wash. I'm not sure, but I suspect the problem happens when the screen protector starts to age, and/or when it gets really warm. I also suspect it's a problem with certain phones and the types of touchscreens on those phones not playing nice with screen protectors. Started happening on mine after just one month.
omnius1 said:
You know what's (not so) funny about this? All of the things that you think are causing this sound really complicated. Is my phone corrupt? hardware defective?? etc etc.
You know what I found it caused this behavior after numerous factory resets and weeks of research and tweaks to my phone?
The f-ing goddam screen protector.
Click to expand...
Click to collapse
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Voelker45 said:
What's the software is he currently on? Is the phone bootloader unlocked and/or rooted?
Click to expand...
Click to collapse
Just to offer some backstory, this started a couple months ago back when he just had the stock AT&T rom (2.3.X or 2.2.X I think? I can't recall clearly) During one of it's "working" periods (last week), I unlocked his bootloader and flashed it with CM9...
Probably won't mean much since the problem existed before I unlocked+CM9'ed it, but while it's not freaking out, I can give you some numbers:
• Model Number: MB860
• Android Version: 4.0.3
• Baseband Version: N_01.77.15P
• Kernel Version: [email protected] #47
• CyanogenMod Version: 9.0.0-RC0-olympus-KANG
omnius1 said:
The f-ing goddam screen protector.
Click to expand...
Click to collapse
Yeh, I have had this problem with screen protectors interfering with capacitive screens before, I am now using some really cheap protectors (5 for £3) and have had no such problems since and have a good bit of pocket money left .
TLRtheory said:
That rant's nice and all, and I'mma let you finish... but there's no screen protector. He's been going bare gorilla all since he got it...
Click to expand...
Click to collapse
ah ok in that case, I have nothing else, I'm only good for ranting. GL!
My touchscreen randomly does these freak outs and stops working:
Usually for me it is caused when the phone is really warm (like on the charger in the car) or when my hands are sweaty (also could just be the the phone is warm in this case as well)
Once it's done with its freak out, I turn off the screen (my power button still works) and clean off the screen with my shirt, wipe the sweat off my hands and turn it back on...everything is then fine.
Also, with my old phone (dell streak) if I kept the phone in my pocket with the screen facing towards my leg it would exhibit this behavior (probably again a case of the screen becoming really warm) but if I kept it screen out it was fine.
I have the same exact problem and have gone back to my Captivate because I couldn't figure it out.
Sent from my Touchpad using XDA
News on this? Here's my experience.
Any news on this, guys? I'm going insane. Here's my experience: I used to get these touchscreen-stops now and then but then they started getting more and more often. What I do to make them stop for a while is a clean restore, that is wiping boot, system, preinstall, cache, userdata with fastboot before installing a new ROM or restoring from backup. Whenever I do that, it comes back to life. If I flash a new ROM without all those wipes, it doesn't work. What sucks so bad is that, even though that fixes the problem, it's only temporary. It starts again after a few weeks. There is NO way this is hardware, and there's also NO way we can't find a solution for this!!!! Come on, guys!!! HELP US OUT, PLEASE!!!!!!!
Have you tried the raindrop fix? I was having similar problems and it worked for me.
Sent from my MB860 using xda premium
My screen has ghost fingers if my hands are even the slightest damp.
A buddy of mine had really bad touch screen issues and had to send back for warranty.
Sent from my MB860 using xda app-developers app
I'm having the same issue
I'm having the exact same issue. It sometimes works, sometimes doesn't. Anywhere from one minute to a whole day, everything you described exactly. No screen protector. I wiped it once and it worked temporarily, but it's back to the old sporadic unresponsiveness again.
I'm still not convinced that it isn't a hardware issue. I'm going to buy a T5 Torx Screwdriver and open her up and see if one of the connections is loose. Has anyone else done this?
I'll post tomorrow night with my results.
Here is a handy trick to determine if your digitizer it going out.
1. Find an appliance like a cable set top box, AV receiver or computer for example
2. Lay your phone face down in the warm air that emits from devices like this.
3. Leave it alone for about 10 to 15 minutes.
4.Pick your phone up and perform some finger swipe heavy tasks.
If you notice its a lot more sensitive like you remember when you first got it then you have a digitizer that is going bad. If nothing changes then its most likely software related.
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
cjmillisock said:
Okay so I took it apart (removed the motherboard, disconnected the radio and 3 cables, then put everything back together. It's not fixed 100% but it's a lot more consistent than it was. youtube dot com/watch?v=kxuF_73YIIY
Click to expand...
Click to collapse
Could be the ribbon behind the digitizer, if its loose or moves it can kill all response to touch. You may have to replace your digitizer to fix this.
Sent from my MB860 using xda premium
I'm dying here
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
pichualvarez said:
I opened it up like the video explained. Everything looked OK. I used a heat gun at 50 C to eliminate any trace of humidity and put back everything in its place. Then, I did a full wipe and a new ROM flash. STILL NOTHING!!! This phone is a little over a year old! This is not possible :crying: Any new ideas???? THANKS!!!!
Click to expand...
Click to collapse
I would also suspect the digitizer. I replaced mine for $45 (frame pre attached attached highly recommended).
The connections are very small, so there is much that can go wrong while doing this kind of brain surgery and the ribbons will rip easily.
Sent from my MB860 using Tapatalk 2
Same problem here. It is like some Ghost is operating it without my permission
Sometimes feels like is should hit the phone on the wall.
I know its not gonna help.
Anybody there who has solution for this
So I started having major issues with my Rezound about a week ago and was sent a replacement. I was having data issues on my first one and the replacement solved that issue but the "new" ones screen would randomly turn solid blue and flicker upon unlock. So now I'm on my second replacement and am pretty pissed off-it gets blistering hot and the battery dies super quick.
Verizon is sending me a new one again but I'm getting pretty frustrated with the issues I've been having. They offered to give me a different phone but I really want the Rezound. I might consider the Nexus or Maxx but feel like both are inferior phones.
What would you guys do if the third replacement (fourth overall) still has problems?
daddyshatch said:
So I started having major issues with my Rezound about a week ago and was sent a replacement. I was having data issues on my first one and the replacement solved that issue but the "new" ones screen would randomly turn solid blue and flicker upon unlock. So now I'm on my second replacement and am pretty pissed off-it gets blistering hot and the battery dies super quick.
Verizon is sending me a new one again but I'm getting pretty frustrated with the issues I've been having. They offered to give me a different phone but I really want the Rezound. I might consider the Nexus or Maxx but feel like both are inferior phones.
What would you guys do if the third replacement (fourth overall) still has problems?
Click to expand...
Click to collapse
I just got my second replacement (third rezound) and This one will be getting shipped back on Tuesday. If this new one has any troubles I think I'm going to grab either a Maxx or a Nexus. I'm leaning towards the Maxx. Every Moto phone I've had on my account has lasted forever. I still have 1 OG droid laying around, 2 X's and an X2. All still functioning.
daddyshatch said:
So I started having major issues with my Rezound about a week ago and was sent a replacement. I was having data issues on my first one and the replacement solved that issue but the "new" ones screen would randomly turn solid blue and flicker upon unlock. So now I'm on my second replacement and am pretty pissed off-it gets blistering hot and the battery dies super quick.
Verizon is sending me a new one again but I'm getting pretty frustrated with the issues I've been having. They offered to give me a different phone but I really want the Rezound. I might consider the Nexus or Maxx but feel like both are inferior phones.
What would you guys do if the third replacement (fourth overall) still has problems?
Click to expand...
Click to collapse
The blue screen problem, was that on stock? Only seen that on leaked kernels.
Sent from my ADR6425LVW using Tapatalk 2
Yes blue screen was on a stock replacement from HTC/Verizon straight out of the box. You can see some of the lock screen sometimes with the blue and also it will split the screen into two identical screens with the blue. Very strange.
daddyshatch said:
Yes blue screen was on a stock replacement from HTC/Verizon straight out of the box. You can see some of the lock screen sometimes with the blue and also it will split the screen into two identical screens with the blue. Very strange.
Click to expand...
Click to collapse
That is weird. Makes me curious what the firmware was.
Sent from my ADR6425LVW using Tapatalk 2
Id tell them i want a new rezound in box for the troubles. If not go for the razr maxx.
fix-this! said:
Id tell them i want a new rezound in box for the troubles. If not go for the razr maxx.
Click to expand...
Click to collapse
i agree id ask for a brand new rezound
but between the Nexus and MAXX umm id go with the Maxx I had the Razr and Nexus i prefer Nexus but the battery life is hard to fight
So I was going to try and put an SD card in my Motorola X2 one day and opened it up, the case came off kind of hard but I didn't think anything of it. When I turned it back on after putting the battery back in, this is what I saw (x2front1.jpg). After that I took the case back off and it seemed to work for a bit but if I wasn't careful and put the phone back in my pocket for awhile the screen would glitch out horribly. I found that simply hitting the phone on a hard surface would allow me use my phone and I would just have to be careful but now that doesn't even seem to be working, even with the case off. Is there any anyway to fix my phone or is it basically a brick? I can still slide my finger over the unlock button and I can tell it unlocks it but it doesn't show anything different. My contract is up in February and I was hoping to make it that long with a half functioning phone but I think I may be doomed. When making calls people can only hear me on speaker as well, I doubt that has any involvement in this but perhaps it does. Anyway, if anyone has any ideas or suggestions I will gladly try them, I cant cause much further harm from what it looks like to me. Thanks for your time!
skolden said:
So I was going to try and put an SD card in my Motorola X2 one day and opened it up, the case came off kind of hard but I didn't think anything of it. When I turned it back on after putting the battery back in, this is what I saw (x2front1.jpg). After that I took the case back off and it seemed to work for a bit but if I wasn't careful and put the phone back in my pocket for awhile the screen would glitch out horribly. I found that simply hitting the phone on a hard surface would allow me use my phone and I would just have to be careful but now that doesn't even seem to be working, even with the case off. Is there any anyway to fix my phone or is it basically a brick? I can still slide my finger over the unlock button and I can tell it unlocks it but it doesn't show anything different. My contract is up in February and I was hoping to make it that long with a half functioning phone but I think I may be doomed. When making calls people can only hear me on speaker as well, I doubt that has any involvement in this but perhaps it does. Anyway, if anyone has any ideas or suggestions I will gladly try them, I cant cause much further harm from what it looks like to me. Thanks for your time!
Click to expand...
Click to collapse
Sounds like the frame got warped.
Sent from my SCH-I535 using xda premium
looks like the lcd is bad, it can be replaced just look on ebay for droid X2 LCD
should be a link to a take apart video in my list
sd_shadow's [Collection] of Links for Droid X2
Sent from my Amazon Kindle Fire using Tapatalk 2