Mogul problem answering calls

[slickjestap]

I may go with the kitchen then just haven't ever done the kitchen. I may try to brave it and see how that works. Looks like ill have something to do on my day off. That delay makes me miss like half of my calls though its really pissing me off wonder if that would be a reason to trade in my phone if it is an internal mogul glitch type thing? I kinda want the diamond ( like everyone).

[guitarpager]

Originally Posted by slickjestap

I may go with the kitchen then just haven't ever done the kitchen. I may try to brave it and see how that works. Looks like ill have something to do on my day off. That delay makes me miss like half of my calls though its really pissing me off wonder if that would be a reason to trade in my phone if it is an internal mogul glitch type thing? I kinda want the diamond ( like everyone).

Sounds like if I were having such trouble that I would be willing to at least try a custom rom. I've been reading your posts and you sound like you hate custom roms, but now it looks like you've never tried one. Whatever glitch you might get with a custom rom sounds like it couldn't be much worse than missing half your phone calls. IMO

[nameeri]

Originally Posted by andrewcgrimm

im having kinda the same problem, but mine is when i press the green phone button it wont answer the phone. I have to press the answer soft key. If i press the green phone button, it will not let me answer the call with either button

I started having this exact same issue with my phone yesterday. I tried to fix with a hard reset, still the same problem. Im wondering if the button is just toasted and doesnt work anymore. Probably not worth taking it back to Sprint and going through all the hassle. Im using an official Sprint ROM with WM 6.1

[andrewcgrimm]

Originally Posted by nameeri

I started having this exact same issue with my phone yesterday. I tried to fix with a hard reset, still the same problem. Im wondering if the button is just toasted and doesnt work anymore. Probably not worth taking it back to Sprint and going through all the hassle. Im using an official Sprint ROM with WM 6.1

im on my second mogul with the same problem, each mogul i reciecved from a sprint store was new in box. i tried using the stock wm6, and am currently using the HTC SPRINT WM6.1, and the problem occurs on both. So ive accepted the downfall and just use the answer button on my bluetooth.

[scott@mac-pc-assist.com]

Originally Posted by nameeri

....Probably not worth taking it back to Sprint and going through all the hassle....

No, no, no....

I have been through SEVEN Mogul refurbs that each have crapped out after two weeks since June.

The only thing you get is a refurb...basically someone dried out your neighbor's Mogul after it hit the drink. If it turns on, then it is a valid working phone regardless of what works on it.

I am really getting ready to go back to paper and pen for calendering my clients, and maybe write an Acess Database for their numbers.

I now have a Treo 800W that lasts just under 5 hours...

I am wondering if Verizon's phones might be better and the $400 hostage fee getting paid will end this PDA nightmare.

[MrObvious]

My theory is that it has to do with CPU load on the phone and Kitchens are cleaner and so it can do the phone operations quicker.

[shaggylive]

every time i've had this happen to me, there was a data connection when the phone rang. but agree'd it is a sporadic problem that effects some rom's more than others.

my theory is that both data and phone calls use cprog.exe and somewhere that gets confused. it seems like there is an extra one running when/after this happens.

[weedahoe]

Mine will do this sometimes, i will ge an incoming call i cannot answer and it ends up getting missed. my entire phone will lock until the call is missed and then i have to go to missed call to see who it was. very aggravating

[shaun0207]

could also be caused by a program you have installed. It could be taking over the data connection. Which would slow the phones reaction time.

[Akkubb]

I'm in the same boat here my only solution is soft reset and call back the last number