I have a google unlocked galaxy nexus phone with JB installed. Sometimes when making a phone call using the dial pad, the display will not turn back on when removed from my ear. Today I was on a call and needed to use the keypad and all I had was a blank display. Nothing I did could get it to display. I had to remove the battery to end the call. Sometimes this happens and all I have to do is tap the power button to bring up the display. Is this a known problem? Is there a setting that I can adjust? Thanks.
Hi jjthenovice,
did you find a solution for this behaviour - I posted a similar experience, but so far nobody responded to my post.
Having the power button set up to end the call is A solution - but not a very good one.
Related
Hi Guys,
Ive noticed that sometimes when i use the speakerphone (either by pushing the on-screen button or flipping the phone over), it works fine. However, once the call is over, the touchscreen is deactivated it seems. Nothing works. Cant press anything. As for the hardware buttons, the windows button works, and the power button works. The volume, call, and end call buttons do nothing.
Not sure if this is relevant, but I only notice it if the phone was flipped over (with touchscreen down). If i used speakerphone with the phone facing up, doesnt seem to happen.
The only ways ive found to fix this are to soft reset with that little button under the cover, or to miss a call. (obviously, if a call comes in, I cant answer it as none of the ways you'd use to answer a call still work). After the call is missed though, the touchscreen comes back to life.
any ideas??
thanks
havent notice quite this.. but something similar...
when i wanna make a quick phone call
i open the keyboard type name of contact,
select the contact and hit enter to make the
phone call.. when i close the keyboard to turn
the phone to my ear, half of the screen looks
normal and have of it looks all MESSED UP...
im sure is not a hardware problem or anything.. ( well i hope so )
i think is not bcuz it only do it on that situation..
besides that my screen is normal..
bump
phone been around a while now...maybe someone else noticed this problem...
I've noticed that sometimes my phone will go into "sleep" mode like when you quickly press the power button. Maybe a quick tap of the power button to wake it up will help.
When I swapped from the iPhone to android, I really missed the button on the top of the phone to end calls. It was very convenient, I think.
I was therefore delighted to see that the desire had a button on top that I upgraded from my hero immediately (amongst other reasons of course!)
Problem is, when you press it while in a call, it just turns the screen off. Does anyone know if someone has developed a hack to end the call with the power button?
BTaylor927 said:
When I swapped from the iPhone to android, I really missed the button on the top of the phone to end calls. It was very convenient, I think.
I was therefore delighted to see that the desire had a button on top that I upgraded from my hero immediately (amongst other reasons of course!)
Problem is, when you press it while in a call, it just turns the screen off. Does anyone know if someone has developed a hack to end the call with the power button?
Click to expand...
Click to collapse
Download and flash the Defrost 0.9 ROM from richardtrip. In Accesibility in settings, you can then enable the end the call from power button
While froyo is cool, I'd prefer to do this in my current sense Rom.
-------------------------------------
Sent via the XDA Tapatalk App
BTaylor927 said:
when you press it while in a call, it just turns the screen off. Does anyone know if someone has developed a hack to end the call with the power button?
Click to expand...
Click to collapse
Strange that it doesn't work when in-call. I know it (the power button) disconnects/hangs-up a call whilst ringing, because I often accidentally press it whilst pulling it out of my belt case and it hangs-up the incoming call. Grrrrrr
Hi,
I love my HTC One X but one thing drives me insane. Once I've been on a call for a minute, the screen goes to sleep and I can't get in to any of my apps like Calendar etc that I need to check during a call. The only button that responds is the power button which ends the call!
Can you please let me know how to prevent sleep during a call?
I've just bought Tasker, so I'm hoping that I can do something with that, is that the best place to start?
Thanks,
JD
It shouldn't be doing that by default.
You can turn on/off the 'power button ends call' option in accessibility
jaypday said:
Hi,
I love my HTC One X but one thing drives me insane. Once I've been on a call for a minute, the screen goes to sleep and I can't get in to any of my apps like Calendar etc that I need to check during a call. The only button that responds is the power button which ends the call!
Can you please let me know how to prevent sleep during a call?
Click to expand...
Click to collapse
I'm facing the same problem, other than the Power button terminating the call.
This is getting on to my nerves now!
Is there a fix to this?
[solved] Prevent sleep during call
wintermute000 said:
It shouldn't be doing that by default.
You can turn on/off the 'power button ends call' option in accessibility
Click to expand...
Click to collapse
Perfect, that fixed it, thanks!
How do I prevent the screen from going to sleep, while on a call?
If I am on a call and I get a call waiting tone, I look at my screen and it's blank. Similarly, like I said earlier, at the end of the call too, I can't end the call because the screen is again blank!
The Power key seems to wake it up, but it is annoying to keep pressing it all the time.
I just got my new AT&T S3 a few days ago, and there's a problem I seem to be having with every single phone call I make or receive.
During the call, the screen goes dark, and none of the buttons seem to be able to wake it up again until the other party hangs up. I've literally had to rip my Otterbox off and yank the battery out to hang up during one call to an IVR system that just wouldn't hang up on its own (I guess I could have pressed the right combination of buttons to force a reboot, but at that point I was in no mood to spend 5 minutes experimenting with different permutations of power, vol-, and vol+ to find the magic combo).
Here's what I think might be happening. Note that I haven't exhaustively spent lots of time debugging it yet, on the theory that if it's a common bug, somebody else already has:
Call begins.
Hall Effect sensor triggered by proximity to face. Screen turned off, touchscreen input disabled.
Display settings ticking away in the background force timeout after N seconds. Ignores the fact that the display is already off, and puts the phone to sleep "for real" (at least, the part handling the UI), neglecting to re-enable the power button first.
I'm done with my call. I move the phone away from my face to hang up (or pull up the keypad to enter a selection). Hall Effect sensor broadcasts intent to turn on screen and re-enable touchscreen, and its intent falls on deaf ears because the phone is officially asleep and ignoring it.
Panic. Press power button. Seemingly ignored (though the phone might be waking up enough to see a note telling it to ignore the button, and going back to sleep without further action).
Anger. Press home button. Press volume buttons. Swear violently, and get really mad.
(other party hangs up; lock gets released, phone is awakened and problem seems to go away)
or...
(furiously press various two- and three-finger combinations of power, vol+, vol-, and home until either the call terminates or the phone reboots)
For what it's worth, the same bug show up if I make a call in my car, but the bluetooth call-control button DOES work, even though the phone itself appears to be a darkened unresponsive brick, and triggering a hangup via bluetooth wakes it back up again. I KNOW this isn't due to Tasker or anything, because I've had this problem literally since I made my first call on the new phone to terminate my Sprint account, when it was 100% stock and virgin.
I had the same problem with my white s3 . Then I changed the screen protector and cleansed the proximity sensor with a dust free cloth and haven't had any problems since
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well, I found the root of my problem: the S3's proximity sensor isn't a Hall Effect sensor, it's near-infrared... and the plastic shell on my case is yellow, which meant it was reflecting too much near-infrared light back into the sensor and triggering it continuously from the moment the LED turned on. I ended up blackening the plastic that surrounds the sensor using a Sharpie marker, and it solved the problem.
Samsung S3 won't hang up
I have the same problem and found that I can insert earphones to phone to make light come back on. After looking at this forum I also noticed a setting (which I haven't tried yet). It's the 3rd from last under settings. Settings-Accessibility-Answering/ending calls-The power key ends calls.
I'm hoping that will work.
Just got my Optimus G Pro a week ago, coming from several years of iPhone usage (and upgrades).
As of yet I've not rooted or anything, it's totally stock aside from some play store downloads.
Here's my question. (I don't know if it's by design or if my phone's messed up.)
When on a call, if I hit the lock button, it darks the screen but the phone is not really locked. Any button press takes me straight to the call screen. Is this by design?
The problem I'm running into because of this is; randomly while on a call I'll hear two faint beeps and the screen will turn on. But there is no notifications (no mms, no emails, etc) and I don't have minute minder (plus the beeps are random, not on the minute) so I don't know why the screen is coming back on.
Both of these issues basically means the phone is going to call screen when in my pocket (I use headphones a lot on calls) or on my desk or whatnot and I have accidentally hit buttons.
I'm used to the iphone where when I hit lock, it's really locked. You cannot accidentally activate the phone unless you first unlock the phone. This is a big deal to me because I'm on conference calls a lot. I need to be able to trust when I lock the phone that it's locked (lockscreen).
Outside of calls it works fine, I lock it and I have to do the unlock action to get back to the phone from the lock screen.
Anyone have any insights or suggestions? And is the no lock screen while on a call by design? (cause that'd be a little lame)
I love this phone and really don't want to root (/ custom rom) yet, at least not until I have vetted all the stock issues to make sure custom romming later didn't cause these issues. To me, the lock button should always lock no matter what the phone is doing. It's such a basic expectation that had I rooted or rommed before this I would swear it was cause by that and not a stock function.
The first question yes it does that by design you can hit the home button in call and go back to the.home screen......and if the phone sees light it.thinks its away.from your.face and wakes back up to.do stuff like text or input numbers for call centers and stuff
Sent from my LG-E988 using Tapatalk
Hitting the home button while on a call does take me to the home screen, but the phone still doesn't lock. Lock button takes you to a blank screen but the phone is still not locked (at the lock screen).
I believe it's by design, but it sure doesn't make sense. Why would a developer think "Hey, you know that dedicated hardware lock button that all phones have? How about we just not let it work while people are on calls? Why would anyone want to keep their phone from being messed with while on an important call, that'd be silly... Maybe next update we can make the home button randomly take you somewhere other than the home screen."
nelsonator1982 said:
The first question yes it does that by design you can hit the home button in call and go back to the.home screen.
Click to expand...
Click to collapse
DrChi said:
Hitting the home button while on a call does take me to the home screen, but the phone still doesn't lock. Lock button takes you to a blank screen but the phone is still not locked (at the lock screen).
I believe it's by design, but it sure doesn't make sense. Why would a developer think "Hey, you know that dedicated hardware lock button that all phones have? How about we just not let it work while people are on calls? Why would anyone want to keep their phone from being messed with while on an important call, that'd be silly... Maybe next update we can make the home button randomly take you somewhere other than the home screen."
Click to expand...
Click to collapse
I don't know but why would you lock a phone during a call? you won't be able to input numbers during a call or just remove it from your year for a second to glance at the call time.....and when the call ends the screen lights up to show you call info and reminding you if you want to lock your phone............so what i am trying to say if i cannot understand the usefulness of locking during call.......if you want the screen to turn off the proximity sensor does that.................can you please give me an example of its use.....thank you