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.
Related
Here's the scenario.
I have my blueangel in my pocket.
It's off and the button lock is engaged so that it wont turn itself on accidentally. There's nothing I hate more than when it switches itself on in my pocket and goes berserk with random screen input.
My bluetooth headset is connected.
(I'm not even gonna start on how appaling the blue tooth on the blue angel is !!!!!, but that aside.....)
The phone rings and I press the answer buton on my headset to answer it.
The damn phone is now on in my pocket and the screen is active and receiving input during the call. Quite apart from anything else, there is a great big red END CALL button on the screen just waiting to be touched.
Assuming the call survives any problems, at the end of the call I have to get the phone out of my pocket to turn it off again because it wont turn itself off unless the activity timeout occurs which is not going to happen if the screen is being brused by anything in my pocket.
Is there some configuration or tool or utility or something that can detect when the phone is in handfree mode and disable screen input unless a certain button is pressed (like the green phone buton) and then switch the phone off again when the call is terminated ?
http://www.trancreative.com/nicestart.aspx
Have a look at this.
Im using it, and its the one that does the job best of them all out there, well in my opinion anyway
What about a case?
I had an alu one... no problem!
OK. I got NiceStart and had a play with it.
I think I have got it configured to work OK now.
Seems to solve most of the issues I raised.
I can't believe I had to get extra software to do that though.
I mean, it's not as if any of those probelms are either unforseeable or hard to solve.
It makes you wonder if the people who design these devices ever actually use them for real for any length of time.
The worst thing about it, is that i can buy a 1$ phone with a locking thats even better than this.
People have been screaming about this since the birth of WM, but M$ dont seem to be hearing this.
I have set Start->Settings->System->Button Lock-> Lock all ........power Button
Set a 4 digit password in NiceStart and mapped it to the 4 action buttons right under the screen.
Works great, but the screen will from time to time light up (M$ thing that it must do) to check the battery status. This cant be stopped in any way.
Hi All,
Does anyone know how to get this working on our beloved HD's? I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
So this seems like the ideal solution - but i can't get it to work!!
I've copied over the file to the windows folder, then soft reset. Changed the registry entry for phoneLockEnable to 1 in HKLM/Software/HTC/Phone but still no joy!
All help would be greatly appreciated.
Regards
DF
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Sorry, i don't have the cab file, i just saw the screenshot and thought 'that's what i need'!!!
Hopefully some bright spark here can help us both (and others probably).
Regards
DF
Beside this transparent canvas, where can I get the orginal canvas?
I am using a offical ROM but I don't see this function!
I hate the way the screen goes completely black during a call, we can't use the light sensor to tell the phone that the call has finished and it is away from your ear (so screen comes back on a la iphone), and i keep doing things during a call with my ear!!
Click to expand...
Click to collapse
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
take55 said:
that's interesting, because my screen doesn't go blank during calls and it happens quite often that i accidently disconnect a call (i suppose because i hit a button with my ear).
so in search for i solution i found in Advanced config a tab Light sensor > Light sensor polling which i set enabled. the explanation says "uses light sensor to automatically turn screen off when the phone come near from your ear to answer a call". so this should set it like the i-phone does, right?
hence when i tested it, the screen still was on, even when i put my thumb onto the light-sensor.
is this because i don't have a stock rom (i use Duttys HD V1.9b XTREME) or is there something i can do about it.
it would be really nice to have the screen locked when i answer a call and to outomatically unlock it if i remove it from my head to use some function on the screen..
Click to expand...
Click to collapse
Hi take55,
Yes, i'm aware of the advanced config tweak (also in HD Tweak), and as you correctly state, the screen should/will go blank on call connection (i'm running kwbr's A Touch Of HD 3.3.4 and mine doesn't, even with tweak applied!!).
Unfortunately, when the call ends and you move the phone away from your ear, the screen still stays blank????? I've read somewhere on these forums that it never will work like the iphone (not sure why, as the light sensor should recognise that we've moved the phone away from our ears).
So that is why i'm trying to get this other method to work. What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
It also might be the fact that this was designed for the Diamond (found the cab on the Diamond forums).
Just hoping some genius here might now how to sort this.
I've attached the cab file i've found, give it a try and see if you have the same issue as me.
Regards
DF
chanmama said:
hi, where you found out this software? it look's great, can you share the link to me? recall i saw some post like this, but just for diamond, i'm looking one for my hd, is there anyone have?
Click to expand...
Click to collapse
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Datafanatic said:
What i have noticed is that with the bmp copied over to the windows folder or with a cab i found by A-Math installed, my dialler locks up after every call (as if the transparent phone lock is in place) but i can't actually see it. None of the screen works and i have to soft reset. Maybe something is stopping the bmp to show on the phone....who knows.
Click to expand...
Click to collapse
It has nothing to do with the BMPs but with the registry setting that the CAB also makes. It sets HKLM\Software\HTC\Phone\PhoneLockEnable to 1, in wich case you'll have to press the power button to unock (no need to soft reset). For the BMP to work the phone/dialer software will have to support it, otherwise it just locks the phone in the usual way: black screen, power button to unlock.
Datafanatic said:
Hi chanmama,
Found the cab file for you, see previous post.
Regards
DF
Click to expand...
Click to collapse
tks but your cab only for the canvas skin only, do not contain the original software (slidable canvas), anyway, tks for your help
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
rubbermonkey123 said:
I've also found this problem to be quite annoying during a phone call but have found some sort of way to deal with it.
Firstly my ROM isn't tweaked, its just the basic one already installed.
After a call is connected, the screen switches off. But if you need to access the screen again during a call, I just press the "Back Arrow" key, one of the four hard buttons on the bottom which brings the screen back up again.
If you press the phone button instead whilst the screen is off, the screen lights up again but it puts the call on hold.
This probably isn't the best way to deal with this, but it seems to work for me for the time being, hope this helps anyone else here.
Click to expand...
Click to collapse
Useful info - I found this particularly annoying yesterday during a ouple of calls.
Also discovered Gyrator tries to turn the phone screen and was laggy - which was even more annoying!
Everyone!!!
CHECK THIS OUT - http://forum.xda-developers.com/showthread.php?t=489034
Answer to all our prayers - a screen lock which uses the g-sensor and not the light sensor.
Now, when a call is connected, holding the phone to the ear blacks the screen, but when you bring the phone down (to use the keypad or something), THE SCREEN COMES BACK ON!!!!!!!
Tried and tested on kwbr's A Touch Of HD v3.3.4 (probably the best manila2 ROM out there!)
Regards
DF
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...
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.
Dear all,
Is there any way to add a confirmation dialog for the number I am dialing from my Touch Pro2? I have accidentally dialed a few calls when I touch the contact quick links on my home page, and when I scroll through the call history or my contact list. I notice that this is a common problem for quite a few people but I have not been able to find a solution. Note that I am NOT asking for screening locking.
Thank you very much.
Welcome to forums
I have never made an accidental call...
You can always block your device
This is not about blocking. I have S2U2 installed and there is no pocket dialing or anything like that. What I am talking about is that when I look through my call history, scroll through my contact list or quick contact links, my finger action may not be a perfect scroll action to the phone so it start dialing right away.
I am new to the forum and can not post links here but if you google "touch pro2 dial confirmation", or "touch pro2 accidental dialing", this is a common problem, at least to new touchphone users.
I'm not a new touchphone user, and I completely know/agree with what you are talking about.
thank god. I thought it was me. For the first two weeks of owning this phone I actually would tell people who called me or that I called "I just bought a brand new phone so if you get a phone call from me and I do not leave a voice mail, it it because I dailed you by accident, sorry". Pretty embarressing especially for a business phone.
It is my first touch phone, but still .....
When you are on phone, do not try to scroll through recent call, especially with the keyboard up. And do not try to do it one handed, where you use your thumb to scroll. It doesn't work for me. My thumb is terrible at scrolling.
I then I don't realize that I am already on the phone screen and press the phone button.
Really cannot figure out all the ways I accidentally call someone. And it has mostly stopped. But still ....
I can usually press "End Call" before it starts ringing on the other end. But I agree that since the scroll gesture, and pressing to select/call are almost the same gesture, there should be a confirmation screen. Or they should make a scroll bar on the side (but that might clutter things up).
I have the same problem, and the end call button is to slow to stop the call. Calling happens so fast that even if I press the end call button immediately it rings at least once.
I've had touch phones for years.... This is just something you get used to. It will happen regardless of whether you are using an Iphone, Windows Phone etc etc.
You just have to be carefull I suppose, no other way around it. You would get very tired of having to confirm EVERY call you make I would think. I dont get any "accidental" calls any more. I havnt for years actually. It's just a matter of training your gestures I would think. When scrolling dont push your finger on a contact and hold it there but start at the bottom or top of the screen and start swiping your finger down (or up) before your finger touches the screen. The only time you get a "accidental" press would be if you start by pressing your finger down and leaving it there a second or ending with your finger on a contact for a second or so.
I'm somehow able to leave my finger on a contact and swipe up or down and it doesnt select the contact untill I actually hold my finger there so. It must just be a way you guys are doing whatever it is you are doing.
That's my two cents though!
I guess people get over this problem sooner or later so xda-developers, who are certainly experienced users of touch phones, do not feel a need to add such a confirmation box.
Anyway, confirmation box is not the only way to prevent accidental dialing. For example, if pressing end-call in 2 seconds actually stops dialing, I do not mind waiting 2 extra seconds for each call. Right now, even immediate end-call cannot stop a call.
XavierGr said:
I have the same problem, and the end call button is to slow to stop the call. Calling happens so fast that even if I press the end call button immediately it rings at least once.
Click to expand...
Click to collapse
I just noticed something, in Advanced Config, under "Phone", there is an item "End Call Delay". Its set to 3 seconds by default, which seems like a long time to delay ending the call. I've just changed it to 1 second, and going to see how that works out.
Advanced Config is here, if you don't already have it:
http://forum.xda-developers.com/showthread.php?t=418151
I must have had at least 50 accidental calls in the last month. Everytime I scroll through my recent history it somehow takes it like I clicked on a number to call...
can somebody please make a fix where I can click YES OR NO right before I make a call.. or maybe a 5 second timer with a cancel button before a call..
thanks a lot!!
btw.
i had an android and i used to use google voice so it would prevent accidently calling someone
google voice app for android has a message that pops up when you make a call that asks which number to use for the call (google voice, or phone)
something like that would work nice
Another thing that might be worth considering is tweaking the amount of pressure required with a touch to simulate a click. If you can find a sweet spot where you're able to select an item when you need to, and scrolling is still possible, could be worth a look. I think I've seen reg entries or tweaking programs that cover this, though it is possible they were for different HTC models, and perhaps ours doesn't register varying amounts of pressure? In which case, is it possible to alter how long you need to press on an item before a click is registered?
Not an answer re. wanting call confirmation, I realise, but something to consider, possibly.
I have the same issue with accidentally dialing numbers. Android has an app, think it's called "Confirm Call". A similar Windows Mobile app would be appreciated and used by many.
The trick is, to apply even pressure to the screen when scrolling up or down. Try not to let your finger press and release to quickly.