S2U2, Samsung Dialer, and CallerID

[Guest dwallersv]

If possible, has anyone figured out how to disable the native WM/Samsung callerID, other than disabling the OEM dialer skin?

So far, the only way I've found to get S2U2's callerID (which I prefer) to play nice is to disable the Sansung OEM dialer (which disables the default callerID, so the two don't fight each other). This renders the "call" button dead.

With Google Maps' new voice feature, activated through the "call" button, this is now more of a problem than a mere minor annoyance. So, I've had to disable CallerID in S2U2, re-enable the OEM dialer (which I like better anyway), and live with the native CallerID panel (which is fine, I just like S2U2) better.

Not that big a deal -- I've traded one minor asthetic annoyance for another but gained voice search in GM, as well as the preferred dialer, so net net I'm better off.

Still, if I could have it all, that would be great :huh:

Edited May 2, 2010 by dwallersv

[Guest WebReaper21]

Have you tried installing the JC2 dialer?

Works great with S2U2, but I don't know if it also works with google...

[Guest Vostradamus]

That's sorta weird...

I'm using S2U2 and its caller id is great

Currently I've disabled samsung dialer (just 'cause I like those 10Mb ram more lol) but:

- s2u2 caller id was working perfectly even with samsung dialer enabled

- even with samsung dialer disabled my call button is still working fine

:huh:

[Guest WovW]

S2u2 CallerId "hangs" my device... Now I'm trying with JC2 dialer...

[Guest lucasjohny]

S2u2 CallerId "hangs" my device... Now I'm trying with JC2 dialer...

jc2 dialler really soft the problem im on jd5 rom now everything working fine

Edited May 3, 2010 by lucasjohny

[Guest Khisha]

I installed JC2 dialer over twu2's JD3 rom due to incoming calls inconsistent behavior, but it causes my phone to get into sleep-to-death

Has anyone experienced such an issue?