15 replies to this topic

[tesanov]

Hi,

I've just installed CW on my Optimus One.

The selected reject calls mode is "Reject cancelling". I turned all rules to "red" (so that all incoming call are rejected) - just to test how it looks like.

I was very disappointed to see that CW writes "Rejected" to its log, while the phone is ringing and vibrating, and I actually able to answer the call.

What do I do wrong? Or isn't CW compatible with LG P500?

Thanks,
Alex.

P.S. The "Reject muting 30s" method works as expected.

[Miguel]

This is the first reference that I've about this issue on the LG.

I've tested this mode in several 2.3.x devices and works fine in all of them. What Android version are you running?
Does the log shows any error?

[tesanov]

The requested information has been sent via e-mail.

Thank you for a quick turnaround!

[tesanov]

Any news? Any additional debug information you need me to provide?

[Miguel]

Unfortunately not.

I'm working on an alternate method, but it istill under development.

[tesanov]

Thanks.
If you need me to run any sort of diagnostic patch/build so that you can gather information you need - I'm ready to help.

[tesanov]

I upgraded to 1.2.1

• Method "Reject muting 30s" works well.
• Method "Reject cancelling" works as "Reject muting 30s"
• Method "Reject Answering and hunging up" answers the call but doesn't hangs on

So - still doesn't work for me.

[Miguel]

Method "Reject muting 30s" and Method "Reject cancelling" may seem the same because reject cancelling also mute the ring until the call cancel is done. But the first method will not cancell the call until the calling phone or the carrier does it.

Please, try again the third method. Activate the log first, and if it fails send me the sdcard/callweaver/callweaver.log file (miguel@sbsh.net)

[tesanov]

Method "Reject muting 30s" and Method "Reject cancelling" may seem the same because reject cancelling also mute the ring until the call cancel is done. But the first method will not cancell the call until the calling phone or the carrier does it.

Interesting.
So, doesn't the 2nd method cancel the call immediately? I would expect immediate "busy" tones in response to an incoming call.

Please, try again the third method. Activate the log first, and if it fails send me the sdcard/callweaver/callweaver.log file

I will do.

[Miguel]

Yes. But the cancel method (the second one) is the most tricky... It uses some hacks that may not work on all devices. I've tested it on many phones and only failed on a Galxy Tab but perhaps there are more failing phones..

[tesanov]

I sent the log file via e-mail.

I tried all methods in this order:
- answer & cancel
- cancel
- mute for 30s

The 1st one just answers and keeps the call active until I hang on manually.

The 2nd one mutes the sound and displays the incoming call screen silently for about 1.5 minutes, then the call gets cancelled (by carrier, I guess).

The 3rd one behaves exactly as the 2nd one - it mutes the sound for 1 minute and 30 seconds; then the call gets cancelled.

So, I don't see any difference between "cancel" and "mute for 30s". Which is strange, because I thought the "mute for 30s" method mutes the sound for the first 30 seconds and then restores the original volume, so that I can hear an incoming call.

[Miguel]

The log shows clearly that none of the modes are working well for you.

Do you have any other program installed that could be "call aware", I mean any program that could need to be informed about call entering?

[tesanov]

Do you have any other program installed that could be "call aware", I mean any program that could need to be informed about call entering?

I don't think so. However, I'll send you the list of all programs installed on my phone. (via e-mail)

[Miguel]

Seems that Galaxy s2/S+ under some circumstances can do a small ring before being muted on a rejected call. Can be solved on most modiiing the reject system and we are working on improving it.

[tesanov]

Hi, I've found a call blocker that works on my LG P500: https://play.google....inker.punchback

You could try to use the same method.