View Single Post
  #23 (permalink)  
Old 08-25-2007, 11:41 AM
letsgoflyers81's Avatar
letsgoflyers81
Regular 'Geeker
Offline
Location: North Wales, PA
 
Join Date: Jun 2007
Posts: 471
Reputation: 145
letsgoflyers81 is keeping up the good workletsgoflyers81 is keeping up the good work
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via AIM to letsgoflyers81
Quote:
Originally Posted by wowthatisrandom
Quote:
Originally Posted by letsgoflyers81
Quote:
Originally Posted by wowthatisrandom
Quote:
Originally Posted by letsgoflyers81
I uninstalled completely and then installed 1.20 from scratch. I still can't answer the phone, same as before. Can someone that has it working post up their registry settings for Slide2Unlock? Maybe I have something set that's causing the problem.
i have mine working perfect...

CallerID = 2
Slide2Answer = 1
IncomingText = Phone - Incoming

i have the mogul
I tried that, with CloseApp set to 0 and 1, it didn't make a difference.
i dont know what to tell if you have that then you should be set... do you have any other app that controls the Caller ID like cityID or anything like that if not i dont know what to say...

the only thing that i can think of is 1 a typo or 2 you dont have the Incoming Text string correct... also make sure that key was entered as a string and not a Dword

my CloseApp = 0 as well if htat matters
I never installed anything that would control caller ID to my knowledge. I've always used WM's built in caller ID functionality.

The IncomingText string was there on its own when I installed 1.20 and I haven't touched it. I just double checked, it is indeed a String Value and says exactly "Phone - Incoming" with no quotes.

I'm stumped.
Reply With Quote