WM 6.5 Dialer Problems

[Caswell]

My problem is the default WM 6.5 dialer keeps trying to pop up when using a different dialer.

Here is the series of events:
- Loaded MightyROM 6
- Had pocket answer/dial problems
- Loaded pocketshield
- WM 6.5 dialer would try to pop up (flickers twice)
- Reloaded S2A
- Problem remained
- Uninstalled Pocketshield
- Problem remained
- Uninstalled S2A
- Installed S2U2 (with call display and S2A turned on)
- Default dialer still flickers and tries to pop up

Is this a known problem? Something I could have caused? Known solution? I know Pocketshield doesn't get along with non-default dialers...so I'm guessing that was the root of my problem.


Once I have the default dialer gone...is there a way to make S2A work with Pocketshield? I tried turning off "Lock on Incomming..." but the S2A mute button was getting press in my pocket, and I was missing calls.

Originally Posted by Caswell

My problem is the default WM 6.5 dialer keeps trying to pop up when using a different dialer.

Here is the series of events:
- Loaded MightyROM 6
- Had pocket answer/dial problems
- Loaded pocketshield
- WM 6.5 dialer would try to pop up (flickers twice)
- Reloaded S2A
- Problem remained
- Uninstalled Pocketshield
- Problem remained
- Uninstalled S2A
- Installed S2U2 (with call display and S2A turned on)
- Default dialer still flickers and tries to pop up

Is this a known problem? Something I could have caused? Known solution? I know Pocketshield doesn't get along with non-default dialers...so I'm guessing that was the root of my problem.


Once I have the default dialer gone...is there a way to make S2A work with Pocketshield? I tried turning off "Lock on Incomming..." but the S2A mute button was getting press in my pocket, and I was missing calls.

What rom and or kitchen are you using?

Use calks newest kitchen you shouldn't have any problems.

[Caswell]

Using MightROM 6.

I know even just reloading MightROM would probably fix the problem, but I was trying to avoid that.

[jdmsleepr]

its a known problem, and to date has no fix...to my knowledge anyway!!

cheers!!