As everyone may know already, while in a call when we put our ears to the ear piece the screen turns off, but when taking the phone away from the ear to look at the phone the light sensor detects it and lights up the screen.
My question is does everyone's phone go back to the TF3D homescreen when looking at the phone during a call, such as when you want to press number selections during voice prompts? Mine goes back to the TF3D homscreen everytime, and doesn't stay on the call status screen unless I physcially press the phone icon. I find this annoying especially when I need to input number selections. Anyone else experience this?
Nevermind, I found the solution and that is to turn off the password lock feature on the phone, and the phone stopped reverting back to the TF3D home screen during calls....must be a glitch...Blah...
Related
I was reading the user reviews of the Fuze on another website when I noticed one saying that the Fuze requires you to press the power button to reactivate the screen each time you need to press a phone number button on the screen while you are on the phone. Is this a requirement on the TP2? As someone who has to deal with phone trees and other automated phone systems alot for business calls I was thinking that I should ask about this as it would be extremely inconvenient.
The proximity sensor will automatically turn on the screen if you move your face away from the device during a call. There's a big button to bring up the keypad to use. If the keypad is deployed and you put the device back to your face, the screen will turn off. But if you turn the screen back on, the keypad will still be deployed, so that's pretty useful.
Thank you very much for this information, it in nice to hear that this problem was resolved on the TP2. I was also wondering if it is possible to run the speakerphone with the TP2 in face up so one could type on the dialpad on the screen while hearing the responses from the phone call? I'm guessing this is possible as my old 8525 does it fine but I just thought I should confirm it. Thanks in advance.
During a call, you can also take out your stylus, it will start notes.. makes it available to write on the screen during a phonecall.
coscom said:
I was also wondering if it is possible to run the speakerphone with the TP2 in face up so one could type on the dialpad on the screen while hearing the responses from the phone call? I'm guessing this is possible as my old 8525 does it fine but I just thought I should confirm it. Thanks in advance.
Click to expand...
Click to collapse
Yes, there's a large button during a call for you to tap to switch to speakerphone as an alternative to putting the device face down on a table. Dialpad works the same in speakerphone mode as in normal mode.
More than half the time I take my phone out of it's case in my pocket to check texts or call somebody, it's always on and eating battery. Alot of the time I have the phone in vibrate or silent because I can't have it going off most of the day, and whenever I get any kind of notification the screen comes on (text, alarm, call, ect.), and then the screen ends up staying on because it's constantly being bumped and never has the time to shut itself down.
Is there any way I can make the screen stay off at ALL times (except on an incoming call), and ONLY come on when I press the unlock/power button on the top of the phone?
I have a TMobile TP2 and I'm running the Nov. 19th, Photon Energy ROM. Upgrading to the Nov. 27th version when it's done downloading but I don't think that will fix the problem as I've changed ROMs before. Thanks to any help.
you will find that when in the case it should be off, on taking the phone out of the case (i assume the HTC one that came with the phone?)
the magnet in the case triggers the keyboard sensor which turns the screen on.
otherwise, you can change the display time out in power options under settings.
Cheers
Steve
That's interesting, I've heard about the case doing that but never thought about it. Would you recommend any cheap cases, or is there a specific magnet location I should be careful of? And do you know if there is a way to keep the screen off when I get a text message for example?
There is a way to fix this... it is to disable "Wake on Slide." I have done this and no more problems.
Here is a link to what to do:
http://forum.xda-developers.com/showpost.php?p=2945249&postcount=3
Hope it helps you, as it did me.
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
illusion of progress said:
Thanks for the reply and I appreciate the help, but I don't really have a problem with the wake on keyboard slide, it seems that if the phone is in my pocket locked, and I get a text message, the screen comes on to notify me that I have a text message. Then, it's usually being bumped around in my pocket and since the touch screen is usable with any object, it will stay on because something will tap it in my pocket. The phone then heats up over time and drains battery. I want to find a way to keep the screen off at all times unless, I either receive a call, or push the power button. Thanks.
Click to expand...
Click to collapse
Try:
go to HKLM\Drivers\BuiltIn\RIL
change DisableSMSWakeUpEvent to 1 (0 will wake up the device)
On my Rhodium, it does not wake up by default. I hear the notification, but my screen remains dark
Or try this cab file ... soft reset after install
Thanks for the .cab, I'm restarting now to see if it fixes the problem. Kind of random, but I might as well ask here before starting a new thread. I started using Mobile Shell instead of TF3D and so far I love it, but when setting a wallpaper, the wallpapers that I would normally use in TF3D, (480x800), it makes me select or crop out part of the photo to use as a background in Mobile Shell. I can't tell if it actually gets blurry (I would think so, because it's stretching the picture), but does anyone know why it wants me to only use a certain portion of the background instead of just setting the entire picture? Thanks,
More than likely, the version of Mobile Shell you have is either not designed for WVGA or there is a setting somewhere in there that allows you to change it and you haven't found it yet.
Am not a expert on mobile Shell, but according to their website, the latest version (3.5) does support WVGA.
Another option is to, if you have Adobe Photo shop or something similar, scale down the entire picture to the size it reccomends.
Otherwise, if you have a version earlier then 3.5, maybe you could upgrade and see if it makes any difference.
The reason for this is when I am in the car and am using the bluetooth to answer the phone is in my case on my belt. When I get a call the screen comes on and even after the call is completed it stays on for 2 minutes. I then end up calling someone in the last called list if the screen bumps the case. I don't notice because my dumb car always wants to download the phonebook after every call and the stereo doesn't connect the outgoing call. Then someone tells me that they got 2 minutes of my music on their voicemail if they didn't answer. Ended up being very embarrassing when call went out and I made some comments that "someone" was not supposed to hear.
I looked with the advanced config tool but could not find anything.
Any ideas appreciated.
Tks
Perhaps stopping the screen from waking is too drastic. This means you effectively disable caller-id. I would suggest looking into installing a screenlock tool.
I am trying pocketshield for now. I was going to look at su2u but I was told that incoming calls still turned the screen on. Will see how this works for a few days.
Thanks
Well I tried pocketshield and it doesn't really do what I need. It still lets the damn phone call after I have hung up. It leaves the screen on and at the lasted called screen. bump the screen and it calls one of my last called list. Going to try Touchprolock now and see how that goes...
I have "locked" (AT&T stock ROM - using long press end key to lock) my device and then hit the power button momentarily.
This turns off the screen. When an incoming call hits, screens lights up. After call is terminated, screen turns off.
Hi all,
This is probably on here somewhere but could not find it, so if i duped this issue i am sorry, but all the time when im on a call on my tilt 2, my ear must hit the notification bar and when i go to look at my phone to hang up or whatever, the notification menu thing is showing. I am ok with the notification messages when i have them just not ok with the menu opening by my ear. is there a way to disable this when im on a call or something.
I did see ways to turn of notifications, but will that disable the menu from opening?
Thanks guys,
JC
I also have this problem. Any fixes for it? Im running Stock Sprint 6.5 ROM. It's pretty annoying.
JRocca said:
Hi all,
This is probably on here somewhere but could not find it, so if i duped this issue i am sorry, but all the time when im on a call on my tilt 2, my ear must hit the notification bar and when i go to look at my phone to hang up or whatever, the notification menu thing is showing. I am ok with the notification messages when i have them just not ok with the menu opening by my ear. is there a way to disable this when im on a call or something.
I did see ways to turn of notifications, but will that disable the menu from opening?
Thanks guys,
JC
Click to expand...
Click to collapse
The TP 2 has a proximity sensor that should turn off the screen when it is close to your face. The screen should be blank if you bring it from your ear to look at it. Does this happen?
The screen SHOULD be unresponsive when held to the ear...
I think what happened is the phone was moved to the face too quickly before the proximity sensor can respond. I have tmo tp2 with stock wm6.5 and has the same issue.
I have used the rhodium keyboard customizer and reassigned the long hold back button to lock, so I often lock the phone before I actually put it near my ear.
Sorry for the delayed replay, what button is the long hold?
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Bmerz said:
Sorry if this has already been posted, I did a search and couldn't find anything.
Anyway, this is a new issue for me as I didn't have this problem before getting my OTA of 4.0.4 last week. When I was on 4.0.2, I didn't have this issue - but I do now that I am on 4.0.4.
My phone will let me dial the area code + 7 digits, but if I am required to input numbers after the call is connected (like when calling your credit card company) the dial-pad screen and phone shuts off as soon as I click the 1st number.
I then have to turn on the phone, swipe to unlock, go back into the phone dialer and do this for each number input.
Anyone else having this issue? Any ideas/and or suggestions how to fix, or at least a workaround until Google gets it fixed?
Not sure if this matters, but I am stock GSM/T-Mobile.
Thank you.
Click to expand...
Click to collapse
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
ingenious247 said:
This happens to me, however I only have to pull my hand away from the phone to bring it back to the dial pad.
I am guessing you have your phone set to lock "immediately" when the screen goes black (I have mine set to five seconds, so this does not happen to me)
What is happening (in my case at least) is an overly sensitive proximity sensor. It catches your hand, thinking you're putting the phone to your face, and darkens the screen. I have to be careful where I place my hand when I use the dialer after I am on a call (say, checking voicemail and entering password)
If your phone is set to lock immediately, try setting it to five seconds, and see if that helps.
This also happened on my GS2..
Click to expand...
Click to collapse
Thank you, I will look into my settings and change it. But as for the other thing, one has to have their hand on/near the dialer in order to input more numbers. Perhaps I can angle the phone and my hand in a way that the sensor doesn't see my hand over the dial pad. (What a PITA! lol)
Nonetheless, thank you for chiming in!