Guest JoePro82 Posted November 5, 2004 Report Share Posted November 5, 2004 Every once in a while, I'd guess around 1 out of every 10th call, when I go to answer the phone by flipping it open, it will beep and show on the screen "ERROR - Unable to Answer Call." and thats it. No reason or code as to why, and then it will return to the Home Screen like nothing happened. ATT doesn't have a clue and I am reluctant to return the phone due to having updated the ROM, figuring that they would consider it modified and thereby void the warranty. Any Suggestions... Link to comment Share on other sites More sharing options...
Guest martin Posted November 5, 2004 Report Share Posted November 5, 2004 It could be that the phone is trying to make a connection just as the caller hangs up or a timeout occurs. It's it happens too often then it's also possible that it could be related to signalling problems. I suppose you could run numerous test calls to yourself and see if any fail to connect. You just need to dial (from another phone), connect and hangup, and since will be charged by the second it won't cost you much :wink: You can then at least eliminate any network or phone problems :lol: Link to comment Share on other sites More sharing options...
Guest ronny Posted November 6, 2004 Report Share Posted November 6, 2004 martin is right, maybe the person calling you just hangs up. or maybe your in a low signal area. Link to comment Share on other sites More sharing options...
Guest JoePro82 Posted November 6, 2004 Report Share Posted November 6, 2004 Thanks for the replies... However for one thing I know that most of the time it isn't caused by someone hanging up, because 9 times out of 10 it is my girl and she just calls right back and says she was kicked into my voicemail. I don't know for a fact that everytime this has happened I have had a signal, and if it only happened at those times then problem solved. However... I very, very rarely do not get a signal, or anything lower than 2 bars, since I switch between ATT's and Cingular's networks and it happens on both. I was just hoping it was a bug I hadn't heard about. Link to comment Share on other sites More sharing options...
Guest Rivernet1 Posted November 23, 2004 Report Share Posted November 23, 2004 Your problem is the ROM. 2003 was never a 'legal' much less supported update for the MPx200. What you're going through is one of many problems that can happen with running WM2003 on a WM2002 designed phone. Solution? Roll back to to 2002. Link to comment Share on other sites More sharing options...
Guest awarner [MVP] Posted November 23, 2004 Report Share Posted November 23, 2004 I do not think it is 2003 related as I have had this with 2002 I have seen this hen there is a blip in the signal strength which my area suffers from quite a lot. Link to comment Share on other sites More sharing options...
Guest Rivernet1 Posted November 23, 2004 Report Share Posted November 23, 2004 I beg to differ. We're 1/2 mile from the tower here when we toyed around with 2003 and the "rejected call" error was a big pain in the arse. Why you got it in 2002 - might be a signal problem, but 2002, you'll get it if you're standing right next to the tower. Link to comment Share on other sites More sharing options...
Guest ronny Posted November 24, 2004 Report Share Posted November 24, 2004 I beg to differ. We're 1/2 mile from the tower here when we toyed around with 2003 and the "rejected call" error was a big pain in the arse. Why you got it in 2002 - might be a signal problem, but 2002, you'll get it if you're standing right next to the tower. huh?!, I don't think so. i've been using WM2003 for a while now, but have not suffered from this drop calls unless if i'm in an area with a low signal. Link to comment Share on other sites More sharing options...
Guest Rivernet1 Posted November 24, 2004 Report Share Posted November 24, 2004 How long is "a while"? We're not talking about dropped calls - just calls that the phone decided to reject, or not connect to. I've even had a few where I'm in the middle of a call and it drops and I hear it ringing on the other side again. You're one of the very, very few that it might actually work on. What other problems have you encountered? Link to comment Share on other sites More sharing options...
Guest ronny Posted November 24, 2004 Report Share Posted November 24, 2004 How long is "a while"? We're not talking about dropped calls - just calls that the phone decided to reject, or not connect to. I've even had a few where I'm in the middle of a call and it drops and I hear it ringing on the other side again. You're one of the very, very few that it might actually work on. What other problems have you encountered? i've been using it for about 4 months now. and somehow i've not experienced "calls that the phone decided to reject, or not connect to" exept in a low signal area. basically i dont really encounter problems that much, except for the "task manager exiting problem" http://www.modaco.com/viewtopic.php?t=115628 which i think i'm the only one suffering from it, but seems to have lessen when i flashed my phone with the hello moto version. so far WM2003 Rom works good for me. :lol: Link to comment Share on other sites More sharing options...
Guest Rivernet1 Posted November 24, 2004 Report Share Posted November 24, 2004 Good luck to ya. Link to comment Share on other sites More sharing options...
Guest niallc Posted March 29, 2005 Report Share Posted March 29, 2005 (edited) Every once in a while, I'd guess around 1 out of every 10th call, when I go to answer the phone by flipping it open, it will beep and show on the screen "ERROR - Unable to Answer Call." and thats it. No reason or code as to why, and then it will return to the Home Screen like nothing happened. ATT doesn't have a clue and I am reluctant to return the phone due to having updated the ROM, figuring that they would consider it modified and thereby void the warranty. Any Suggestions... <{POST_SNAPBACK}> I would be interested to know if you resolved this issue. I am getting this problem with non-modified Mpx220 purchased a few weeks ago. I have the following configuration: Sw Ver.: 1.150-0 Dec 8 2004 HW Ver.:0006 OS Build No.:1088 Hw Build Info.:4 Windows Mobile 2003 Second Edition Version 4.21.1088 Radio Version 1.00 ROM Update Version Operator: 0.300.4060.0 Manufacturer: 1.150.0.0 Microsoft: 4.21.14315.0 Language: 0.190.16.0 File System: 4.21.143 This is driving me nuts! I doubt if it is a signal issue as it could happen while I am sitting in the same area; that is, I can answer one call and then on the next call I get the error. Person on the other end is not hanging up! Would appreciate any advice/fix! Edited March 29, 2005 by niallc Link to comment Share on other sites More sharing options...
Guest madmaxedcn Posted March 30, 2005 Report Share Posted March 30, 2005 Every once in a while, I'd guess around 1 out of every 10th call, when I go to answer the phone by flipping it open, it will beep and show on the screen "ERROR - Unable to Answer Call." and thats it. No reason or code as to why, and then it will return to the Home Screen like nothing happened. ATT doesn't have a clue and I am reluctant to return the phone due to having updated the ROM, figuring that they would consider it modified and thereby void the warranty. Any Suggestions... <{POST_SNAPBACK}> try hard reseting and dont install any software or programs and try it out, i had that same problem with 2003 on incoming and outgoing calls. Link to comment Share on other sites More sharing options...
Guest DAK ATTACK Posted March 30, 2005 Report Share Posted March 30, 2005 Hiya. I have had this with 2002 and 2003 and it is not a ROM or version problem. This only happens to me when I have just missed the call as Martin said, they are hanging up while I am answering. Link to comment Share on other sites More sharing options...
Guest chrisc28 Posted April 1, 2005 Report Share Posted April 1, 2005 I'll add my bit here. Having used 3 Windows Mobile flip phones before (Mitac 8380, MPx200, MPx220), I can verify that it is a problem with the OS design. I faced this problem when: 1) The caller hangs up just when I open up the phone. 2) I open the flip really quick. I noticed that when I open the flip slowly and carefully, it will pick up the call fine. However, if I do it really really quick, this error happens more frequently. There is a "delay effect" when active flip is applied and this is inherent in all Windows Mobile flip phones. Guess the OS isn't built with flip phone compatibility in mind since CE started off as a PDA platform, which is essentially candybar in design. Link to comment Share on other sites More sharing options...
Guest craig4wd Posted April 22, 2005 Report Share Posted April 22, 2005 2 cents worth. I've tried three different ROMS on my xphone and the all do the same thing. Question: does anyone have any of the following running who are experiencing this problem? I have: XBar 2 Fizz Software Codewallet The MMC card is always in the phone (haven't checked without it) I've tried O2, imate and Orange ROMS (still happens) I have 2000+ contacts synchronised I sort of suspect either Xbar or the number of contacts that I have might be contributing to the problem. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now