I have this issue where my phone screen will randomly become unresponsive. To get it back all I have to do is shut the screen off and back on and the it will accept my input. The menu, home, back, and search buttons will still work just the screen wont respont to me touching it. It may happen several time in a few minutes. Then again i might go a day it only happen once. I dont recall this happening on unrooted 2.2.2 but Im not 100% sure. It does do it 2.3.3, 2.3.4, 2.3.5, and it has done it on Liberty, Eclipse, and Molten. If anyone else has run into this problem and has a way to fix it i sure would appreciate the help.
I have the same issue. Its a deffective screen. No matter what rom you are ob it will be there. And if your is like mine it was there on 2.2.2 unrooted.
Answer to it is getting a referb. But what i learned on referbs from moto (i went through 6 razr2 in one 1 hr never left the verizon store. One worse then the other) so if thats all your worring about then id say put up with it you could get one thats even more of a pos.
Its only annoying to me when it acts up while im typing a long txt or playing a game other then that its two presses and a swipe and all better (and mine happens at least 6 times a day everyday) consider yourself lucky you could have my pos dx2.
Sent from my DROID X2 using XDA App
Ok. Its not to bad I mean Ive kinda gotten use to it. Its just annoying as hell cause it always happens at the worst time.
Mine does this too from time to time. Same fix.. Turn screen off and then back on and all is well again. Hasnt done it a long time though
Sent from my DROID X2 using XDA App
Yatkoos said:
Mine does this too from time to time. Same fix.. Turn screen off and then back on and all is well again. Hasnt done it a long time though
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
If mine did that more then once I would be in with Verizon getting a replacement...not a refurb. No way would I deal with a unresponsive screen but mine is only a few weeks old. If you deal with them right you might get a new phone out of it. The in store employees have always treated me well.
Over the course of 6 months back when I had my Samsung Rogue they exchanged it for a new one 3 times until I got a new one. After about a month or so it would start to randomly reboot.
motcher41 said:
If mine did that more then once I would be in with Verizon getting a replacement...not a refurb. No way would I deal with a unresponsive screen but mine is only a few weeks old. If you deal with them right you might get a new phone out of it. The in store employees have always treated me well.
Over the course of 6 months back when I had my Samsung Rogue they exchanged it for a new one 3 times until I got a new one. After about a month or so it would start to randomly reboot.
Click to expand...
Click to collapse
Its been so rare for me it hasnt bothered me enough to worry about. Ive also had poor luck convincing people problems exist when I can't recreate them on demand.
Sent from my DROID X2 using XDA App
Yatkoos said:
Its been so rare for me it hasnt bothered me enough to worry about. Ive also had poor luck convincing people problems exist when I can't recreate them on demand.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I could never get it to reboot in there so I would explain the issue and politely suggest that I should switch to a different carrier since I cant depend on my phone and it worked every time.
I might go up to the store and see what they will do. At the worst im still stuck with the phone till I upgrade.
This sounds like a defective screen. You should look into getting a replacement.
I might go up to the store and see what they will do. At the worst im still stuck with the phone till I upgrade.
Click to expand...
Click to collapse
I would go in....if you play it right you might even be able to talk yourself into an early upgrade.
Sent from my DROID X2 using xda premium
Mine does this quite regularly, and I have issues typing sometimes because of this. It's incredibly aggravating, but I'm getting a GNex soon, so I'm not too worried about it anymore.
motcher41 said:
I would go in....if you play it right you might even be able to talk yourself into an early upgrade.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Now that alone would make it all worth while. Now I've got to give it a shot.
If my phone started doing that I would have been at the store before I even thought about making this thread lol.
Sent from my DROID X2 using xda premium
pacman377 said:
Now that alone would make it all worth while. Now I've got to give it a shot.
Click to expand...
Click to collapse
Shmooz them.with all the I love the network. Ut this screen just drives me nuts and blah blah. Then shmooz into you need a replacement cuz you've only had is x amount of days...then if they agree to it just bring up you know when I got this phone this other phone wasn't out and I would got that one. Instead of giving me a new one how about I just pay the difference with the upgrade cost like if I just upgraded now instead. I mean a sale is a sale and im just trying to have a good phone I don't trust this one not to brake again. Maybe throw in id hate to have to go to att or sprint for a good phone.
You'll be golden
Sent from my DROID X2 using xda premium
I like it. I like it a lot. Of course this never worked with sprint. But who knows. Razer here I come? Uh.... Maybe.... I hope.
03civicdx said:
If my phone started doing that I would have been at the store before I even thought about making this thread lol.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
This phone is a replacement. My first x2 had an unfortunate accident at the river. This one wasn't stock for an hour before I was getting eclipse on it. So I was asking to be sure it couldn't be related to the things I had changed on my phone. If I had be certain of this yes I would have gone directly to Verizon.
pacman377 said:
This phone is a replacement. My first x2 had an unfortunate accident at the river. This one wasn't stock for an hour before I was getting eclipse on it. So I was asking to be sure it couldn't be related to the things I had changed on my phone. If I had be certain of this yes I would have gone directly to Verizon.
Click to expand...
Click to collapse
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
03civicdx said:
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
+1
Sent from my DROID X2 using xda premium
03civicdx said:
One sure fire way to be certain is to sbf to stock. If the problem continues then you know its hardware related.
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I have sbf multiple times since I've noticed it. It has done it every time, and every rom, even when i went and mixed and matched between a couple different roms. So from what I've heard it is deffinetly hardware related, which is why i asked. So to all of you who have helped me, a big thank you.
I've had this happen too. Not hardware related though. In my case it was caused by Launcher Pro. Switched to Go Launcher and haven't had a problem since. Might be something to look into if you use LP too.
Sent from my DROID X2 using xda premium
Related
I have a problem where my haptic feedback stops working. This includes vibrations. It'll happen randomly. When this happens if I drop my phone onto a table (say from about an inch up) the vibration and haptic feedback work again. sounds like a hardware issue to me, anybody else having a similar problem? I haven't searched since I'm on my phone and not on a computer. can anybody point me to a fix?
Sent from my MB860 using XDA Premium App
Actually it seems to work again with just a slightly forceful shake or a tap to the front or back of the phone. Wtheck is wrong with my phone lol
Sent from my MB860 using XDA Premium App
Same problem here
Sent from my MB860 using XDA Premium App
Weird, this has actually happened to me twice in the last three days too. Never happened before. Haven't done anything recently (haven't unlocked my bootloader yet even lol). I found that a simple screen lock and then wake will fix. It seems mine happened when too many vibrate type things happened at once and sort of killed it I guess.
mine will still not work even with screen toggling.
i assumed it was the activation of a vibration command before the previous vibrate command had finished, but i turned off the keyboard haptic feedback and its still occasionally shutting off even when i havent pressed any button yet. I am sorely annoyed at the moment..
Have the same problem notice it after flashing 1.8.3
Sent from my MB860 using XDA App
I am getting very frustrated with this anybody have a solution?
Sent from my MB860 using XDA Premium App
Bump.
Does anybody have this probllem on 1.5.7 or 1.2.6 or 2.3.4?
Sent from my MB860 using XDA Premium App
I have had the same problem. Any insight would be great.
Same here on 2.3.4
Sent via the power of a unicorn's horn.
If its a present problem in 1.8.3 and 2.3.4,
then I'm assuming its the small motor inside thats starting to malfunction... Sadness.
Can anybody on 1.2.6 or 1.5.7 verify if they have the same problem?
bump. we must solve this heinous problem.
I've noticed this since I bought this phone in Feb. So its been present on all versions for me.
Sent from my MB860 using XDA Premium App
This drives me crazy as I use haptic feedback on my keyboard as I type. I hope some of the experts here can fix this (if it's software related).
beatphreek said:
I've noticed this since I bought this phone in Feb. So its been present on all versions for me.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF.
TT_TT I guess I'll just turn off all vibrations.. :<
In my post on this thread's first page I said it had happened just a couple times. Since then I've noticed that it happens probably 3+ times a day lol. I too fear that it's a hardware malfunction, which is VERRRRY unfortunate. I'm sure any of us could send in our phone to get a repair, but that is a huge fatty hassle.... I wish I was in that 30 day period still, I have a ton of problems with my phone (problems that I'm unsure an SBF flash can fix). But I'm not about to dish out mula for a phone off contract
mm if we applied pudding we're no good for a warranty replacement...
I thought it was 1.8.3 or something wrong with my current install, so i did a full wipe and applied pudding as well. Now I realize its probably hardware. I do have insurance though..
Will it blend? XD
xredjokerx said:
mm if we applied pudding we're no good for a warranty replacement...
I thought it was 1.8.3 or something wrong with my current install, so i did a full wipe and applied pudding as well. Now I realize its probably hardware. I do have insurance though..
Will it blend? XD
Click to expand...
Click to collapse
Haha crap you're right, I totally forgot about that. Now I'm gonna have to randomly tap the back of my phone all the time xD
Perhaps once the OTA comes out that allows the unlock, perhaps we'd be okay to send it in? Claim we unlocked with what came in the update...I dunno if that'd work. Maybe I'll just buy a new Atrix elsewhere lol. Or an SGS II I've gone through too much with this phone already though!
I feel like if i traded it in for another phone I'd regret it later on (due to the advanced hardware) Once custom roms can get rid of the webtop reserve ram and get rid of motocrap, this thing will be a monster.
I want to play with the infuse (simply because texting on it is so easy) but I feel that I'd regret it later on.
Oh.. what to do. Trade in for a Desire Z and call it a day..
xredjokerx said:
I feel like if i traded it in for another phone I'd regret it later on (due to the advanced hardware) Once custom roms can get rid of the webtop reserve ram and get rid of motocrap, this thing will be a monster.
I want to play with the infuse (simply because texting on it is so easy) but I feel that I'd regret it later on.
Oh.. what to do. Trade in for a Desire Z and call it a day..
Click to expand...
Click to collapse
Yeah I love this phone, I'm just upset about some minor hardward malfunctions that aren't fixable with just ROMs and such. I considered trying to swap for an Inspire in some way, since it's been OC'd to 1.8 or something...even without dual core, that's fast! But I dunno. I suppose I could somehow swap for another Atrix of some kind.
Since the 4.0 OTA my phone has just been doing random crap.
1.) Locking up and rebooting at least once a day.
2.) In the middle of a phone call it will disconnect the call with whomever i was talking to, and connect me with a random person from my address book.
3.) one of the verizon junk apps (Emergency Alerts i think it is) will go off on its own, and i have never used it or set it up..
so i take it in and Im not sure if i am the only person who has been having these problems (from what the verizon rep noted, i was not the only one). they are sending me a new one , they said that the OTA made a mess on some phones, bricked others and the ones that are from the factory or newer ones are working much better.
now for the part that surprised me..take this with a grain of salt as usuall but she said that the 4.1 Jelly bean was going to be ota in about another month..
anyways, anyone else had the listed problems?
ps central us for those that are going to ask, no longer vat/city
If I do a lot of browsing, my phone will randomly scroll through random apps and open them, almost like the screen is stuck. Only way to stop is power volume down. Then it is good for a day or two, then it does it again. I am completely stock, never rooted or installed custom rom.
Sent from my DROID RAZR using xda app-developers app
cmraymond said:
If I do a lot of browsing, my phone will randomly scroll through random apps and open them, almost like the screen is stuck. Only way to stop is power volume down. Then it is good for a day or two, then it does it again. I am completely stock, never rooted or installed custom rom.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
I got my phone yesterday, and so far not a single problem and there is a difference from a phone that received the ota and one that was shipped with 4.0. one that has been shipped with it is defiantly smoother has a quicker response. im happy i sent mine in.
Do a factory reset and you will have no more problems.
Sent from my DROID RAZR using xda premium
Adauth said:
Do a factory reset and you will have no more problems.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I'll second this: the sound on my Razr cut out at times. I did a factory reset last week, and have had no problems since then.
Sent from my DROID RAZR using xda app-developers app
I have done two resets since I received the update. Didn't install any apps for a few days in case that was the culprit. Still have the issue.
Sent from my DROID RAZR using xda app-developers app
I can vouch for what cmraymond is saying, i tried repeatedly using the factory reset and nothing it would still do it. i even deleted everything i had on my sd card and even tried a diff one. no change. new phone is running great.
phrite said:
I can vouch for what cmraymond is saying, i tried repeatedly using the factory reset and nothing it would still do it. i even deleted everything i had on my sd card and even tried a diff one. no change. new phone is running great.
Click to expand...
Click to collapse
So how does returning the phone work if I bought it on new egg.com. Do I go through them or can I call Verizon to do a warranty exchange. I've had the phone since March this year.
Sent from my DROID RAZR using xda app-developers app
cmraymond said:
So how does returning the phone work if I bought it on new egg.com. Do I go through them or can I call Verizon to do a warranty exchange. I've had the phone since March this year.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
If it's under factory warranty, Verizon will send you a refurb. My previous phone was a Incredible 2 that I purchased at Radio Shack, and when my LCD stopped working after about 5 months, Verizon sent me a replacement at no cost.
As a last ditch effort, you can try flashing the stock fastboot files. I'd recommend a factory reset and format of the cache partition before doing so. That way, if there was something that didn't update properly with the OTA, you're starting off with a fresh, clean install. Instructions to flash are here http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/, and the fastboot files are found here: http://sbf.droid-developers.org/cdma_spyder/list.php
So my girlfriend is still on her Tbolt. She's never wanted me to root it or anything so still stock. Anyway since the ics update the phone has become next to useless. She was complaining about it being slow, laggy etc. I thought she was exaggerating but after messing with it myself ya its really bad. Super slow to do anything and backup media force closes every few minutes.
Just curious if this is an isolated incident or if others have similar issues? I told her to try a factory reset but she doesn't want to do that yet.
Sent from my HTC6435LVW using xda app-developers app
broons said:
So my girlfriend is still on her Tbolt. She's never wanted me to root it or anything so still stock. Anyway since the ics update the phone has become next to useless. She was complaining about it being slow, laggy etc. I thought she was exaggerating but after messing with it myself ya its really bad. Super slow to do anything and backup media force closes every few minutes.
Just curious if this is an isolated incident or if others have similar issues? I told her to try a factory reset but she doesn't want to do that yet.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
My girlfriends phone apparently didn't take well to the update either. Hers never got FC's, but it froze a lot... especially on the lock screen. After a while, the screen started wigging out... it started scrolling around on its own and even made screen selections on its own.
Good thing I have a reliable source here that warned me about the ICS Goblins that come with the OTA and harass the user of the phone. I sent her phone in for an insurance claim and got her a new one and no more ICS Goblins harass her.
Disconnecktie, if you see this, thanks again!
Sent from my ADR6400L using xda premium
RBarnett09 said:
My girlfriends phone apparently didn't take well to the update either. Hers never got FC's, but it froze a lot... especially on the lock screen. After a while, the screen started wigging out... it started scrolling around on its own and even made screen selections on its own.
Good thing I have a reliable source here that warned me about the ICS Goblins that come with the OTA and harass the user of the phone. I sent her phone in for an insurance claim and got her a new one and no more ICS Goblins harass her.
Disconnecktie, if you see this, thanks again!
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
You never know when they might sneak up on you.....
Sent from my ADR6400L using Tapatalk 2
In all of my years using Android I have never seen a full on kernel panic dump screen. I saw it this morning while installing swype beta on my phone running jbsnow's jellybean port.
Should I return my phone for a new one?
gunnyman said:
In all of my years using Android I have never seen a full on kernel panic dump screen. I saw it this morning while installing swype beta on my phone running jbsnow's jellybean port.
Should I return my phone for a new one?
Click to expand...
Click to collapse
I've had the phone since it came out and only seen it twice. I wouldn't worry about it... yet. See if it happens a lot in the coming days or before your unable to return in-store.
Sent from my LG-E970 using xda app-developers app
Ok thanks I'll keep an eye on it.
gunnyman said:
Ok thanks I'll keep an eye on it.
Click to expand...
Click to collapse
Yeah, I think a lot of us rooted users on custom ROM's have at least # it once. I've never heard of it being fatal or that anyone couldn't get the phone out of it. I know it's a scary SOB when it pops up though!
Sent from my LG-E970 using xda app-developers app
Jank4AU,
PM'd you, sir.
Happened to me when the phone was new all the time, including before I'd rooted it. Gradually happened less and less. Now I can't remember the last time it happened. A few weeks? Over a month? In any case, don't worry about it too much. Mine was the black kernel crash screen though. I think I've only had the yellow screen once.
Sent from my Nexus 7 using Tapatalk HD
I'm pretty sure it happens on that rom because of a glitch in the WiFi part of the kernel. When I was running it I just set the WiFi band to 2.4 only (instead of 5) which fixed it for me.
Sent from my Nexus G LTE
Happened to me once, scared the crap outta me. Rebooted and never saw it again.
I still can't figure out why the idiot that wrote that error message couldn't tell his up button from his down button.
I wouldn't worry about it. It should not affect anything. I will try to see what it is and fix it in the next version though.
DraginMagik said:
I still can't figure out why the idiot that wrote that error message couldn't tell his up button from his down button.
Click to expand...
Click to collapse
That happens because we are using the n4 aboot. Our hardware differs from the n4 where our up is the opposite key of their up, so it gives that bug.
Sent from my LG-E970 using xda app-developers app
SnowLeopardJB said:
I wouldn't worry about it. It should not affect anything. I will try to see what it is and fix it in the next version though.
That happens because we are using the n4 aboot. Our hardware differs from the n4 where our up is the opposite key of their up, so it gives that bug.
Click to expand...
Click to collapse
if it means anything, i got that screen whilst using TheBase.73
and thanks for the explanation.
The demi-god yellow screen? I've gotten that months before using a JB rom.
I've seen it twice, and they happened when I was playing Ingress on my phone while either using WiFi or GPS. I was either rooted+stock or running The Base.
I can honestly say I've never seen this. I got a black screen kernel panic from UVing too far on The Base but that's about it.
Sent from my LG-E970
Murasakiii
Did you find a ROM or fix that works with Ingress on this phone?
I've had it freak out while trying to drop an item or select a xmp to fire.
I usually play on another phone, but I have to send it in for repairs so my Optimus G is my only phone for a week or so and I'd love full functionality in the game.
jackslim said:
Murasakiii
Did you find a ROM or fix that works with Ingress on this phone?
I've had it freak out while trying to drop an item or select a xmp to fire.
I usually play on another phone, but I have to send it in for repairs so my Optimus G is my only phone for a week or so and I'd love full functionality in the game.
Click to expand...
Click to collapse
I haven't played ingress in quite a while so I wouldn't be able to help you out. Rains far too much in Portland for me to want to fry my phone.
Sent from my LG-E970 using xda app-developers app
I noticed a section across my screen, approx 1/2 in tall, that I is not registering touches. I used ScreenTouchTest from the Play Store to test touches.I got it to go away for a little bit by pulling the battery a couple times but now it is persistent.I tried resetting my phone to factory settings and no luck. I am on stock ICS. Of course I don't have warranty, I was just curious if anyone else had this happen.
udz2002 said:
I noticed a section across my screen, approx 1/2 in tall, that I is not registering touches. I used ScreenTouchTest from the Play Store to test touches.I got it to go away for a little bit by pulling the battery a couple times but now it is persistent.I tried resetting my phone to factory settings and no luck. I am on stock ICS. Of course I don't have warranty, I was just curious if anyone else had this happen.
Click to expand...
Click to collapse
I'm 99.999999% sure it's a hardware problem. I had the same problem, and had to replace my phone. Unless you're willing to replace the touchscreen, I think it's unfixable.
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
I'm 99.999999% sure it's a hardware problem. I had the same problem, and had to replace my phone. Unless you're willing to replace the touchscreen, I think it's unfixable.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Ya that is what I was afraid of. It was just weird that it will work after a few reboots. Oh well, eligible for an upgrade tomorrow, probably grab the HTC One.
udz2002 said:
Ya that is what I was afraid of. It was just weird that it will work after a few reboots. Oh well, eligible for an upgrade tomorrow, probably grab the HTC One.
Click to expand...
Click to collapse
Oh, nice! I'm on contract until November (a family member stole my early upgrade), but probably would've chosen that phone, too.
Sent from my ADR6425LVW using xda app-developers app