• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Confirm before dialing?

trowpa

Member
Does anyone know of a setting or app that will prevent one-touch dialing? Many times when scrolling through a contact list i have accidentally tapped a contact and the phone immediately starts dialing.

Ideally I'd like to have the phone not dial until i hit "send" confirming that i do indeed want to place a call.

Any way to do this?
 
I have the same problem. I got the phone Thur and almost instantly called 5 people I did not want to call.
Went to Vzm store yesterday and ask them and they did not know of an app or a switch in the phone to allow double click before sending a call.
Otherwise, no other issues. Really fun phone.
 
This is the only method I have found so far and you have to set each contact or whatever contacts are showing up on the widget.

Open People
Select a contact
Hit Menu
More
Set Widget Action
Select "View Contact"
 
I have Google Voice but this still happens when scrolling through call history. If you simply touch any call, it will automatically dial and call that person.

Under the 'people' or contact list, it will open the contacts details but in 'call history', it dials immediately.
 
I've done this a few times too. Then I panicked and hit the home key, which I found out doesn't end the call. Guess I gotta be more careful.
 
When I use Call Confirm, it says the right number but says "unknown contact" on the confirmation screen where the name of the contact should be. Is this normal?
 
Hi, I'm the developer of Call Confirm. Thank you for using my app.

The bug mentioned above, that the app always say "unknown contact" even the number is in the list, is fixed in the new version 1.0.1.

It occurred in some environment (en + Android 2.1 or above, I guess).
Please try it out.

As I can not see en_US user's comments in my phone (with lang:ja),
I would appreciate if you contact me by email when you had some troubles.

Thanks.
 
Is V 1.0.1 available?

UPDATE Never mind, I JUST got a notification to the new version

Just tried it and it still shows Unknown Contact.

It does not matter, the program does what I want.
 
I tried Call Confirm WITH Google Voice, which has an independent confirmation screen for choosing which number you wish to dial with. It just bounces back and forth between the dual confirmation screens, unable to actually call out. Just experimenting, not really needing Call Confirm with my current Google Voice setup.
 
I tried Call Confirm WITH Google Voice, which has an independent confirmation screen for choosing which number you wish to dial with. It just bounces back and forth between the dual confirmation screens, unable to actually call out. Just experimenting, not really needing Call Confirm with my current Google Voice setup.

Thank you for the experiment. I wish I could work around, but Google Voice is only available in US. (I live in Japan). I tried to setup GV on my emu with lang:en_US, but could not register.

My plan is this: lookup the Activity history (getRecentTasks ?) and if an Activity which belongs to GV's package is detected, pass the call (do not popup).
However, I can not know the actual package/Activity name of GV's dialer..

If GV began in Japan, I will try.
 
Hey guys just wanted to pass along that 7bit should have a fix for both the unknown issue as well as the photo. I just got the update from him and it's working like a charm.
 
^ great! How do the rest of us get that update?

The amazing power of forums...

Thank you, 7bit!


I was told that the new version 1.0.3 (build 5) should appear in the market soon. 7bit isn't sure, but it may require uninstalling 1.0.3 (debug build 4) before updating.

It seems the issue was simply a matter of programming for USA based telephone number formats. 7bit is in Japan and wasn't familiar with the ###-###-#### format.
 
Hi, I'm the developer of Call Confirm. Thank you for using my app.

The bug mentioned above, that the app always say "unknown contact" even the number is in the list, is fixed in the new version 1.0.1.

It occurred in some environment (en + Android 2.1 or above, I guess).
Please try it out.

As I can not see en_US user's comments in my phone (with lang:ja),
I would appreciate if you contact me by email when you had some troubles.

Thanks.

I uninstalled and then re-installed and it works perfectly. Thank you!
 
Back
Top Bottom