Yesterday I started having a strange problem with voice dialing.
When I hold the answer key button to start the application, it automatically double-clicks (this can be heard as well) so I don't even have a chance of saying the voice dial name. Instead, it just puts up an error message and that's it.
Anyone have any idea what could've caused this, or how can I fix it? I have a feeling one of the beta programs that are changing the key functions could be causing it, but I deleted all and can't seem to fix it.
Related
Ok... I think i need some help here. I wrote an app that would screen save and trap all the keys (even the red and green phone keys). I did this according to the following post.
http://www.xda-developers.com/forum/viewtopic.php?t=3665
Then i wrote some tapi stuff to listen for an incoming call and restart cprog.exe after the first ring. Only problem is, cprog.exe seems to need the LINEDEVSTATE_NUMCALLS (0x0800) notification or it will not log the call as missed. It can never get that notification, cause that is the first thing i can trigger off of. So... cprog.exe does not log the call as missed. If i answer the call, then it is logged...
I was hoping i could do one of the following:
1. Write the missed call to the log myself.
2. find a way to trap the keys without killing cprog.exe
3. Fake a LINEDEVSTATE_NUMCALLS (0x0800) dev state change message to cprog.exe
or worse case (which i don't like at all)
4. Keep my own call log which means i will have to write my own call log app.
or even worse still...
5. Just be happy with the screen saved, but the keys unlocked and hope that i don't make 3 hour "prank" calls of me singing along in the car to the radio on some friend's voice mail.
Any help here would be greatly appreciated. Also, if anyone needs to see the code that i used to detect the ringing and stuff... let me know... i can post it up.
thanks,
John
Being as you know you missed the call, you could just put the relevant information into the call log database.
Thanks... i didn't realize that existed, but i figured something was there like that.
Unfortunately for this app... but fortunately for everything else, i upgraded to WM2003... so now, i don't need this as much because the now the GPRS stays connected even in suspend mode (which locks the keys).
It also seems that 2003 behaves differently with respect to screen power. It seems 2003 automatically turns screen power back on in the event of a window focus change... so my app needs to be rethought now.
thanks for the help,
John
Hi John
Did you ever find how to add/insert your call into the log?
It seems that ther is no API to do it (there is an API to query the log...).
Any thoughts?
I have the HT630.
Has anyone experienced the phone function of the TyTn to just quit working? Or maybe the speed dial and voice command to stop working? It seems to be real random, but I can power down and boot back up and it works for a while. I really haven't put a pattern to it yet, but I will start tracking the events as they occure.
ive been searching for a thread on this subject, and i havent found precisely the answer to the problem im having. i am unsure of the cause, but every so often, my phone, by itself, tried to call the last number i dialed in rapid succession, dialing and then hanging up and re-dialing. i often have to soft reset or close out everything for it to stop.
any ideas or suggestions on what it could be or what to do to prevent it??
Enable devicelock so the buttons are disabled till you want them enabled.
Hi,
I have a very strange problem. Even when I have my phone locked when I click the answer button located on the headset (those which original came with the device) it reacts as if I press the answer button on my phone so if it is pressed two times I would call person which is first in my call history.
So what do you think might be the problem? Do anyone had a simmilar problem with your device?
In fact I have never used this button for anything so the solution might be to disable this button.
Thanks.
I have the same problem too , No idea
The same here ) however I´ve installed this (forum.xda-developers.com/showthread.php?t=492947) app. Now it skips a song by doublepress (you can also set no action).
If someone knows a better solution (only changing registry value), it would be appreciated )
Thanks Jaitni, it is even better to just disabling the button, what I wanted to do
And btw I have found a very simmilar and I think simpler app here http://forum.xda-developers.com/showthread.php?t=502881
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
pissinguoff247 said:
I just installed Google Voice on my Epic 4G and received my first phone call on it - and was unable to answer. Two problems - first, when I answered, the greeting telling me to press "1" to accept was cut off at the beginning (all I heard was '...all from [spoken voice]. Press 1 to accept".
I can get past that, but then when I pulled up the dial pad to press 1, I was unable to. I pounded on the "1," was sure it was showing up, but it would not answer the call. I tried enabling audible touch tones but that didn't work, and I don't think there's a setting on the epic to change between long/short touch tones.
Does anyone know what's going on with this?
Click to expand...
Click to collapse
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Bigger problem
fookxixi said:
I think the second problem is a bug. It's not related to google voice but the phone itself. The dialpad is not very responsive when you take the phone off your face and the screen is back on. Wait a few seconds, and it'll be back again.
It happened all the time when I called any customer service number and tried to use the dialpad to choose in the menu.
Click to expand...
Click to collapse
I never had the phone to my face when I did my test calls - this was always phone in my hand and calling from my office phone.
I think I just came across a bigger problem - the dialpad doesn't work on incoming calls. I just called my phone from my office on the regular (not G-voice) number and pushed a bunch of buttons, and couldn't hear the tones.
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
bojackson63044 said:
You can disable the initial greeting and go straight to the call when you pick up. It is under Voice Setting in your google voice account. I know this doesn't address your unresponsive screen issue, but it's a temporary work around until your dialpad gets fixed.
Click to expand...
Click to collapse
Is this actually a bug? I posted another thread here and am trying to have people verify whether or not this is a real issue - if it's not a bug then I definitely need to replace the phone, 'cuz it's been factory reset as of last night.