hey all
loving the 1 year+ with the atrix, but a few problems still affecting me. On neutrino 3.02 is anyone is wondering.
1)most of the time, when i take calls, the screen turns off as normal due to the proximity sensor, but refuses to turn back on after i take the phone away from my ear. no amount of pressing any buttons, physical or capacitive, will turn it on, and a battery pull is required.
2) im pretty sure i've read that this is a manufacturing defect with the atrix, so please correct me if i'm wrong. sometimes the screen will randomly press buttons, even when my hands and the screen itself is dry.
any solutions to the above?
thanks in advance
AFAIK, no to both
andresrivas said:
AFAIK, no to both
Click to expand...
Click to collapse
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
sidewinder_x5 said:
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
Click to expand...
Click to collapse
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
andresrivas said:
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
Click to expand...
Click to collapse
Ah okay, i see. thanks for the clarification. its a shame the stock rom isn't any good for me then, otherwise i wouldn't be having this problem!
as for the screen, my experience is that it happens when the screen first turns on, no matter what app i'm using. doesn't happen when the screen is already on, which is interesting. i remember reading a thread which said that the digitizer wasn't properly attached for this phone, meaning that it's destined to go bad at some point. i'll have to see if i can find the thread again.
once again, thanks for the clarification!
Related
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Pig Vomit said:
My Vibrant is currently running stock KB5.
About every two days or so, I will be using the phone, and the colors on the screen will suddenly wash out, screen goes to max brightness, whatever is on the screen at the time stays up, and there will be two or three horizontal thin lines on the screen. The Menu, Home, Back, and Search keys all light up. The touchscreen and all buttons, including the power button, become unresponsive. Screen will not timeout. Only way to get out of it is to remove the battery and reinsert. If I am in the middle of a phone call, I am still able to continue speaking on the phone.....but can't hang up, adjust volume, etc.
I haven't tried any other ROMs since KB5 was released, so hard to say if another ROM would solve the issue. Don't flame me for sticking with KB5. I don't need my phone to do a lot....really just use it for calls, music player, Sirius, Google Maps/GPS, light web browsing. I'm not really opposed to running another ROM, I just found it to be a pain in the butt to be constantly switching ROMs as they are updated.
Anyone else experience this problem? Hardware or driver problem? If anyone else did have this problem, did switching to another ROM solve it for you?
Click to expand...
Click to collapse
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
ECOTOX said:
thats usually what happens when I OC too high or dont have enough voltage =3 is it just plain KB5, no mods right?? if so it shouldnt be doing that =/
Click to expand...
Click to collapse
No mods whatsoever. Completely stock, not rooted.
I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
WongJames said:
I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
I also face this problem, after updating my rom to arctic 2.0 rom, which uses some stuff from 2.3.6.....power does not help, have to hard reboot. any idea why?
I've had this problem happen to me on my Droid RAZR (CDMA Verizon), can't remember if its before or after I was rooted... I just had to hard restart and its only happened once since then.
pswin09 said:
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
Click to expand...
Click to collapse
The power button does not work for me
I had try to press the power button, but then the screen still not responding, so I cannot pass through the lock screen, and have to hard reboot......
I am on stock rom, 2.3.5, the Asian version.
But it seems it does not matter to different region's razr since the cdma one had the same issue
Sent from my XT910 using XDA App
I get this too. I had 3 razrs, first two had dead pixels so I had them replaced, all had this issue. Has not happened in awhile and I can't remember if it was always with a game, but at least one time it was with a game. Anyway, I don't think this has to do with rooting because my first one I never rooted and it did this. Don't remember if power button worked or not, but I had to reboot as well with power and volume down, or up, whatever it is, to get it to respond again.
No problems here.
I have had this happen about 4 or 5 times for me as well - got it day of launch. Mine says it is the XT912 though - is that right?
XT912 is the Verizon specific one, so yes.
Seems to be a fairly common issue. What is the chance that this is a software problem as opposed to a hardware one and so will be fixed with an update?
I had it happen for the first time yesterday after about 5 weeks or so, strange cause I wasn't doing anything. Battery was at about 15% though...
I only encounter this bug when I open Rom Toolbox for the first time and the superuser permissions screen shows up. My screen doesnt respond to touch anymore. I have to use the power button to make it work. Thats it. It happens nowhere else.
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
opensourcefan said:
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Happened to me today...any need to panic?? On official Stock ROM 2.3.5...
Also, is this a hardware issue or software??
My problem is bit different, on a 4 month old unrooted razr.
Touch screen will start to fail recognizing my sywpe typing and start jumping all over the place, or it will end the word while I'm still sywping the word...
Sometimes it types in different letters (1/2 keyboard away) when I'm not sywping to avoid this BS when it happens.
Unfortunately, I cannot reproduce this result whenever I want to, I'm currently trying to reproduce the situation.
I believe this happens more often when my battery is low... or when I have been using it for an extensive time.
I go to draw program to test if it is the hardware problem and it is jumpy too, but not by much.
The problem does get better with reboot, but not 100% of the time, so I can't conclude it is SW problem
I also have issues with this. I think the problem is software side. It seems to be poorly responsive often after I unlock my phone and try to swipe screens.
Also while typing quickly with two hands it often does not input all the letters I type, although it flashes the keys and acknowledges that I touched them (this one might be a keyboard issues, not sure yet)
And ya, on an all black screen, I'm noticing some dead pixels- a lot of rectangular patches of dead pixels. I don't really notice it anytime else except when it's all black.
Been making me double think my choice, but I will wait for ICS update and possibly bootloader bypass. But.. I might be getting another phone shortly just because of the size (bezel mostly), these touch screen issues, and the performance isn't exactly where I anticipated it to be.
Razr XT910 touchscreen randomly jumping or not responding
I'm having all the problems mentioned earlier:
- touchscreen stops working randomly
- touch "jumps", like someone is touching it in random places
- some letters on the keybord stop working randomly
- phone gets quite hot at the top
My XT910 is not altered in any way, stock android 2.3.5, as updated as possible.
This happened when it was up-to-date and the very clean one.
This happens really irregularily. At first it happened when I played multitouch games - at some point the touchscreen just stopped responding and could only go back or lock the screen (but not unlock it, obviously).
Twice it happened when I was just going through messages or contacts.
I sent it to Motorola to fix it - they just reset it, benchmarked it for 45seconds and sent it back.
The very evening I got it back I tried to "heat" it myself - I installed a lot of apps, played a lot multitouch games on 3d graphic and voila! - it started freaking out like never before (vidoe in zip file attached).
My last idea is that it happens because of a low quality generic anti-scratch foil on the screen. So I threw it away and tried to "heat" the phone again - nothing.
I used a different foil - anti-reflecting + benchmarking apps - nothing.
If it happens again I'll send it with this video + the one I'll make then.
Hope it gets Motorola specialists off their ass and back to work .
Hey there, my maxx has this weird issue with it's screen too.
Take for example, a game with on screen controller like reckless racing. If i push the screen too long, it won't recognize my press anymore in the pressed area. I tried to go back home, thinking this is the game issue, but it's not, the home launcher button that coincidentally in the same location with game control button is unclickable. i tried with phone tester app and it show the same symptom, the pressed area indicator will disappear within 1-2 minutes.
The only solution is to turn off display and turn it on again. Should i bring it to service center?
Sent from my XT910 using xda app-developers app
Hello, I've recently having this exact same problems with my Motorola Droid Razr Maxx.
The screen sometimes doesn't respond as it should:
-Random touches.
-Not detecting swipes.
-Not detecting anything at all after long press.
-Detecting the touch location wrongly...
When this happens, sometimes a reboot fixes everything. Others, I just have to stop using the phone, and come back later.
Has anyone managed to find a possible cause and/or solution to this problem?
I've tried diferent roms, full reset, rsd flashes... But still the same problem
Does anyone else have this problem? On previous CleanROM builds and now on the latest ICS leak I have to turn the power on to see my screen. It is very frustrating when wanting to hang up or mute and unmute calls.
thanks.
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
mjones73 said:
I just gave it a quick test on the latest build and my screen is turning back on fine when I take the phone away from my head.
Click to expand...
Click to collapse
Interesting. Thanks for the response.
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
tCizler said:
I had the same problem on the original leak. And even worse yet, my screen would lock out until i hung up the phone call. I couldn't surf while connected to a phone call. I was beginning to think i was the only one having this issue. It's extremely frustrating when dealing with an automated service. Every single time i needed to press a button, i would have to hit the screen unlock/power button. And occasionally it would stop working and i would have to hang up and start over.
I just flashed the latest leak but haven't tested to see if it's fixed.
Click to expand...
Click to collapse
Not seeing any issues like that either. I was on a 40 min call this morning where I had to dial in an access code after making the initial call, I was able to mute/unmute multiple times and towards the end I was checking my email and facebook before it was over without any lock ups or anything.
I cannot find a setting for using the proximity sensor during phone calls. I thought my old EVO had a setting like this!?
I am having the same issue. Proximity sensor shuts the display off, but doesn't turn back on after moving away from head.
Started with latest "official" leak. 3.14.605.5 71ORD
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Thanks for the response. I am gaining confidence that it is not my phone.
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
jayochs said:
newest leak? put phone to head, screen turns off...pull phone away,s creen turns back on. i'm running RUu here.
Click to expand...
Click to collapse
I have had mixed results. Seems to be better after a reboot.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
If you really want to know whats causing it, make a phone call while you're plugged into your computer, and run logcat. It will show you whats going on with the prox sensor.
flying_pigs said:
Have you tried reverting to GB to ensure that your proximity sensor really did not fail?
Click to expand...
Click to collapse
No but I was thinking about trying it, but it's a lot of work just to test it.
Sent from my ADR6425LVW using Tapatalk 2
works fine here too... fully stock 3.14 leak, frozen bloatware.
I had this problem and like the rest of you thought it was the rom/leak I was using.
It wasn't. The HTC proximity sensor is extremely sensitive. It is right above the left end of the checkmark next to the verizon logo at the top of the phone.
If you are using a screen protector and it does not have a cutout for the proximity sensor, you're going to cause problems. I used both a crystal clear, then an anti-glare screen guard and even though they are obviously quite clear they both screwed with the proximity sensor.
I found the RND Power Solutions screen protectors DO have a cutout for the sensor and work flawlessly. No more issues.
I have this problem too I'm on the .22 ICS leak if I go back to GB it works fine might try the 5/7 leak and see if it happens on that.
Sent from my ICS Rezound
I had this problem but then soon realized it was my screen protector.
I would get a call and as soon as I answered it, without even putting my phone to my ear, the screen would shut off.
flying_pigs said:
Sorry to say, but if you experience this issue, you need to get a replacement. I had the exact same thing happen to me, and I thought it was the ICS leak, but it ended up being a dead proximity sensor.
The issue has come up in various other threads as well.
Click to expand...
Click to collapse
tCizler said:
The proximity sensor isn't working for me on any ics leaks. I'm hoping it will be fixed when we get the source code. And my sensor worked fine on ALL GB roms, so I wouldn't suggest rushing out to replace a phone, just wait for the official release. If you had a dead sensor, I would think that's an exception more than the rule. Too many people have this issue ONLY after updating to ics
Click to expand...
Click to collapse
Well, i stand corrected... I took my screen protector off, no luck. I reverted back to GB, no luck. I downloaded several sensor testing apps and all said the proximity sensor was dead. I got a "new" phone coming in the mail tomorrow. As much as i didn't want to hear it was a hardware issue, you were correct. And after a very easy google search apparently this is almost an epidemic with the rezound. Oh well, here's to hoping my replacement doesn't have way more problems than just a proximity sensor.
Thanks again flying_pigs
Last week i flashed my Vibrant to 4.0.3 and i found some times i can't use half left vibrant's screen, but when i turn off screen and turn on i used ok. Then i tried another ics 4.0 custom but this problem happened again. But when i used stock rom or 2.x.x mod my vibrant is ok. Can you help me what happen with my vibrant.
I'm sorry because i'm not good at english
Siri.nguyen said:
Last week i flashed my Vibrant to 4.0.3 and i found some times i can't use half left vibrant's screen, but when i turn off screen and turn on i used ok. Then i tried another ics 4.0 custom but this problem happened again. But when i used stock rom or 2.x.x mod my vibrant is ok. Can you help me what happen with my vibrant.
I'm sorry because i'm not good at english
Click to expand...
Click to collapse
Just to be clear, do you mean that your phone doesn't register your fingers touching the screen on the left side of the phone sometimes?
I would suggest downloading the free app "Touch Test" which shows a grid that not only shows where you are touching, but the path of your slides across the screen. If the phone begins to act up again, you can open the act and see if and where the screen is cutting out in the grid. Aside from that, it might simply be that you need a replacement and its coincidental that it was acting up along side you running a 4.0 rom.
Xenoism said:
Just to be clear, do you mean that your phone doesn't register your fingers touching the screen on the left side of the phone sometimes?
I would suggest downloading the free app "Touch Test" which shows a grid that not only shows where you are touching, but the path of your slides across the screen. If the phone begins to act up again, you can open the act and see if and where the screen is cutting out in the grid. Aside from that, it might simply be that you need a replacement and its coincidental that it was acting up along side you running a 4.0 rom.
Click to expand...
Click to collapse
Ok i have tried touch test. I found when i sliced from the left to right, i saw the line appeared from the middle of screen, but when i sliced form the right to the left, the line appeared all screen? But it's not happen usualy. Just 10 to 15 second. May some hardware problem
Siri.nguyen said:
Ok i have tried touch test. I found when i sliced from the left to right, i saw the line appeared from the middle of screen, but when i sliced form the right to the left, the line appeared all screen? But it's not happen usualy. Just 10 to 15 second. May some hardware problem
Click to expand...
Click to collapse
That is the oddest thing I have ever heard lol
It really might be a hardware issue man...I can't think of how it could be the rom. I mean, sure you might occasionally
have an unresponsive touchscreen....but only half the screen working?? That's just weird Oo I'll keep looking around for answers though man
but thus far I've found very little.
Good luck
Xenoism said:
That is the oddest thing I have ever heard lol
It really might be a hardware issue man...I can't think of how it could be the rom. I mean, sure you might occasionally
have an unresponsive touchscreen....but only half the screen working?? That's just weird Oo I'll keep looking around for answers though man
but thus far I've found very little.
Good luck
Click to expand...
Click to collapse
Ok! Thanks you so much. I will make a short video when it happen again.
Siri.nguyen said:
Ok! Thanks you so much. I will make a short video when it happen again.
Click to expand...
Click to collapse
I have a video but i'm new member i can't send link to my post. I will sent to your inbox. tk
Okay, so that anyone else that happens to come to this thread is on board, here is the video that shows his problem:
http://www.youtube.com/watch?v=5xDolJhmDog&feature=youtu.be
As you can see in the app, if the origin of the trail is on the right side of his screen, the swipe is recognized across over to the left without problem...if however the origin is on the left side of the screen, no touch is recognized until he reached the middle of the screen, at which point it becomes recognized.
I am still looking around for a similar problem, but thus far have few ideas. Typically, the screen either is totally unresponsive or momentarily unresponsive...never half and half, and especially with such weird rules. By this, I mean that obviously the left side of the device is capable of recognizing touches, since if he begins at the right side, it does just fine....the only problem is if he originally touches the left side, then it doesn't recognize it.
My guess: it could be a kernel issue.
I would try the following:
Pull battery and reboot. Take out any external SD card.
Back up what important apps or data you have and try a factory reset.
You can also try some the options below:
1. Reflashing the kernel.
2. Try a different kernel if available.
3. Factory reset and full wipe and flash a different ics or cm9 rom to see it the problem persist. You can try to isolate the issue to hardware or firmware.
4. Full reset and flash back to complete stock to see if the problem persists. If you are fully reseted and back on stock eclair or froyo and the problem persists, you may have to open up the device to check all the connections.
sometimes a bad battery may also creates some problems
Now i'm using xerxes custom 2.3.6 gingerbread. It's ok but i don't know why when i use ics. I can use half left screen
Sent from my SGH-T959 using xda premium
My Atrix's screen has become unresponsive in a vertical column (if the phone is in portrait mode) that lines up about with the W, E, and S keys. Restarting fixed the problem for maybe 20 seconds or so after the phone became usable, but doesn't seem to have made a difference after about the third time or so. I also removed the battery and held down the power button for ~45 seconds and then put everything back together, which also seemed to have helped for a minute or less before the stripe became unresponsive again. I also restored to yesterday's backup a couple different times (CM 7.2 stable), which also temporarily helped.
So after a brief search, it seems that the digitizer may be the issue. Is there any way to tell for sure? At first it seemed like a software problem, but it could also just be the digitizer acting erratically because it's going out, so I'm not really sure, and I'd rather not attempt a repair that may not be necessary.
ErrorCode680 said:
My Atrix's screen has become unresponsive in a vertical column (if the phone is in portrait mode) that lines up about with the W, E, and S keys. Restarting fixed the problem for maybe 20 seconds or so after the phone became usable, but doesn't seem to have made a difference after about the third time or so. I also removed the battery and held down the power button for ~45 seconds and then put everything back together, which also seemed to have helped for a minute or less before the stripe became unresponsive again. I also restored to yesterday's backup a couple different times (CM 7.2 stable), which also temporarily helped.
So after a brief search, it seems that the digitizer may be the issue. Is there any way to tell for sure? At first it seemed like a software problem, but it could also just be the digitizer acting erratically because it's going out, so I'm not really sure, and I'd rather not attempt a repair that may not be necessary.
Click to expand...
Click to collapse
there are some screen tester apps on Play which you could use to see if, in fact, your digitizer is a problem.
barry_ said:
there are some screen tester apps on Play which you could use to see if, in fact, your digitizer is a problem.
Click to expand...
Click to collapse
Do you have any specific recommendations? I downloaded the touch test app from here (http://www.freewarelovers.com/android/app/touch-test) to see how much of the screen was misbehaving and discovered that it was a perfect stripe the whole way down, but because I'm not terribly knowledgeable about troubleshooting phone hardware, I don't know if that's telling me it's the digitizer or something else. I attached a screenshot that shows where the stripe is.
ErrorCode680 said:
Do you have any specific recommendations? I downloaded the touch test app from here (http://www.freewarelovers.com/android/app/touch-test) to see how much of the screen was misbehaving and discovered that it was a perfect stripe the whole way down, but because I'm not terribly knowledgeable about troubleshooting phone hardware, I don't know if that's telling me it's the digitizer or something else. I attached a screenshot that shows where the stripe is.
Click to expand...
Click to collapse
#
From what I've seen on here it does look like your digitizer is at fault. I have never had to change mine but there are plenty of posters on here who have and you can look at their experiences to assist you. Also, here's a video I found so you can see what you'll have to do. Good Luck!
http://www.youtube.com/watch?v=grqz-3LdIEk
barry_ said:
#
From what I've seen on here it does look like your digitizer is at fault. I have never had to change mine but there are plenty of posters on here who have and you can look at their experiences to assist you. Also, here's a video I found so you can see what you'll have to do. Good Luck!
http://www.youtube.com/watch?v=grqz-3LdIEk
Click to expand...
Click to collapse
That's unfortunate, but at least I know that's what's wrong. Thanks for your help!