03-04-2010 07:49 AM
Following various bug reports i have discovered that callInitiated is called only once (for the first time) and never thereafter.
All other methods of the call listener perform fine and are called reliably.
Tested OS are 220.127.116.111 and 18.104.22.168
Rebooting the phone allows the listener callInitiated to be called once again, but it will not work the second time.
All other tested OS (4.2.1, 4.5, 4.6.1, 5.0) do not show this behavior.
03-04-2010 07:57 AM
I have found a workaround for this:
In callDisconnected i call
I feel dirty now, but at least it works.
03-16-2010 12:15 PM
Not working on 22.214.171.124 on a 8220 pearl flip. callInitiated is never called.
I am looking for global events that indicate the call initiated.
On the 8220 it seems to be GUID 5961289116197897667
On a 4.5 device it was GUID -3502867315182341540
I wonder if the guid is changed, my hope was to have found a workaround. anybody has a clue?
03-22-2010 07:17 PM
I just wanted to say that GUID 59612289116197897667L seems to be happening for me when nothing to do with the Phone is going on. It seems to be something to do with the UI... object0 is an XYRect and object1 is an Integer. It's being fired when native dialogs are popped up.
03-23-2010 08:07 AM
thanks for the update, matches my own observation.
the initiation of a call triggers the element, maybe because the phone app goes to the foreground.
i use it with the check of an active call.