Hi there:
am I the only one that has problems with the screen not coming up (turn on) during calls if you separate it from the ear. And most of the times when I touch the screen it goes back off ignoring the touch command. This creates a great problem when I am in a call and have another call coming in. Also although using the power button works sometimes, it does not work all the time and I end up loosing the call. It is really frustrating and is happening in both CM9 and Official ICS. I think is a kernel problem or a hardware problem. Anyone experimenting the same??
I don't have that problem.. Official ics..
Sent from my ICS Moto Razr XT910
ellopr said:
Hi there:
am I the only one that has problems with the screen not coming up (turn on) during calls if you separate it from the ear. And most of the times when I touch the screen it goes back off ignoring the touch command. This creates a great problem when I am in a call and have another call coming in. Also although using the power button works sometimes, it does not work all the time and I end up loosing the call. It is really frustrating and is happening in both CM9 and Official ICS. I think is a kernel problem or a hardware problem. Anyone experimenting the same??
Click to expand...
Click to collapse
I had the same problem also. Apparently, it happened after I put the screen protector. To solve the problem, I cut the area around the proximity sensor and the no more problems during call. (official ICS)
ellopr said:
Hi there:
am I the only one that has problems with the screen not coming up (turn on) during calls if you separate it from the ear. And most of the times when I touch the screen it goes back off ignoring the touch command. This creates a great problem when I am in a call and have another call coming in. Also although using the power button works sometimes, it does not work all the time and I end up loosing the call. It is really frustrating and is happening in both CM9 and Official ICS. I think is a kernel problem or a hardware problem. Anyone experimenting the same??
Click to expand...
Click to collapse
I have a LATAM from Claro PR. This is driving me crazy. I am thinking of getting rip of the phone. Is causing me too many problems.
veryagung said:
I had the same problem also. Apparently, it happened after I put the screen protector. To solve the problem, I cut the area around the proximity sensor and the no more problems during call. (official ICS)
Click to expand...
Click to collapse
+1
Sent from my XT910 using xda app-developers app
Related
Overall i am pleased with the update, but i believe i uncovered an issue that others are expriencing as well.
When i have a second line calling me the screen does not wake up allowing me to switch to the second call. In the past, when a second call comes in the proximity sensor would wake the screen and allow me to take or reject the call. Now i cant even see who is calling. Since i use the phone for business, this is a big, big issue. It still works but the screen only wakes up after like the third ring, whereas before it would wake up immediately Anyone else experience this? I tried this on my buddies Vibrant and its the same thing.
So the question to you guys is how do i get the old dialer app back which i believe controls call waiting. Does anyone else know a way around this annoying issue?
Is there something stopping you from pressing the power button to turn the screen on when you hear the call waiting beep?
The prox sensor is not perfect.
-bZj
_____
-sent from my Samsung Vibrant via XDApp
down8 said:
The prox sensor is not perfect.
Click to expand...
Click to collapse
Obviously, if it was perfect this thread wouldn't exist.
nermie said:
Obviously, if it was perfect this thread wouldn't exist.
Click to expand...
Click to collapse
Thank u. I tried the power button, but unfortunately it does not wake the screen.
Thread moved to Q&A.
bump - me too!
pressing the power button results in a lagged response. that is: call waiting call comes in, screen is black. press the button screen stays black. 5-6 seconds pass and then the screen comes on finally and shuts right back off. whereas NOT pressing the power button, the screen stays black for 5-6 seconds and then comes on and stays on.
I am experiencing this problem too. Just started since coming from stock to JI6.
bump... me too, but this happened on a friend of mine's vibrant who was using stock JI6 from the ota, no root nothing and every incoming call if she is on a call has the same behavior.
This issue has gotten so annoying for me, I have unfortunately decided to sell the phone. I loved it, but is failed in the function I use it most as, a phone. Got a g2. Not as glamorous as the vibrant, but it works as a phone.
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
Im on cm10 newest version. everything work perfect but i have one problem.
everytime i try to call somebody, screen blacks out and cant operate my phone. but its not freezing. i can hear friends talking and i can talk back but i just cant operate it.
But as soon as phone call gets done, if i hit power buttun then the lock screen comes out and i can operate it again.
what im saying is when i hit the wrong person and phone starts calling them then i cant cancel it. if i wanna cancel it i have to force power off my phone and gotta reboot.
anybody help plz?
Sounds like a proximity issue, try the fix in the paranoid android thread
thanks
om4 said:
Sounds like a proximity issue, try the fix in the paranoid android thread
Click to expand...
Click to collapse
where is that??
could u give me a url ???
thanks!
http://forum.xda-developers.com/showthread.php?p=30671790
Also under accessibility in settings, you can set the power button to end call.
In case the fix doesn't work.
I haven't had that problem on any of the new builds, but it seems like it's a bit phone specific. Also try taking off any case or screen protector, it has worked for some people.
Sent from my EVO using xda app-developers app
Not just that but clean up the prox sensor issue extremely well with a smooth cloth. It's extremely sensitive. I had this issue personally until removing a piece of the Zagg HD screen protector around the prox sensor with nail clippers, then cleaned out the goop.
thanks everyone
thank you everyone.
I am rooted, and currently runny no-name ROM but rom doesnt seem to matter. My proximity senser is giving me issues. Testing it showed that if i cover it it will recognize it but then is stuck not sensing me removing it. I dont have any case or screen glass that is covering it. Anybody else having this issue?
Yes I have had this issue since day 1. Stock not rooted
Sent from my LG-H901 using Tapatalk
Have had the same issue since day one, 11/10/15. Not rooted. Aside from an ok battery life, this is the only problem I have with the LGV10.
i have this problem also.. its happening more and more when hanging up a call. I have to press the back button to get the screen back on.
Ludeape said:
i have this problem also.. its happening more and more when hanging up a call. I have to press the back button to get the screen back on.
Click to expand...
Click to collapse
Now it does it every call on mine, but test with app Aida64 works fine
Me too .. Any Fix can solve that ?
₪HuEx₪