I just got off the phone after talking for 30 mins with Sprint advanced tech support (based in Florida).
I reported the 1X PushMail/Call ended Issue. The tech tracked it down to a complete network-side bug. ACharles25 (the tech) informed me that this issue has nothing to do with my handset and is completely on their end. ACharles25 started a service record about this issue, and said it was not a 72hour tech fix (not the normal service ticket issue). It will take up to 2 weeks and a small team of network techs to troubleshoot the issue. He also said upon completion this problem should be fixed nation-wide, not just in my area ( like he first thought).
Maybe us in the 1X area will see this Call Ended issue clear up in 2 weeks. The record was flagged as high priority, as it causes "dropped calls" for everyone. I would release the record number, but it has my account number within it.
Someone else should try to get to the adv. tech support and verify the record. Reference ACharles25, and describe the issue.
I wonder if Verizon will get the message. I just spent a few days in Park City and encountered this for the first time (it's a 1x area, I'm normally covered by EVDO). It was annoying though not a dealbreaker for the weekend, but I can see how those of you who have to deal with it day in and day out would be at wits' end.
I thought it was reported that it was a WM5 ROM issue and it would be fixed in the next ROM update? You are talking about placing a call, and it doesn't go through, you get three beeps and have to try again, right?
I think it looked to a be a ROM update issue for the fact that activesync opened an HTTP connection, which caused the call to fail. I can use agile messenger with the old rom and it also opens an http connection, and it would cause the call to fail just as the new rom does with activesync.... i hope this does get fixed. i have a trouble ticket open with microsoft too about this. they called and had me send a log to them.... never heard back after about 10 calls to the techs cell phone, so i dont know if they just blew me off or what......
I really dont think this is a network side issue, it seems that the phone itself seems to place a higher priority on making the network connection and drops the call to do it when in 1x mode.
I would have this occur every once in awile in virginia (dont remember how often it would happen when I came home to park city) but I experienced it repeat itself (on every call) when I spent the last week in St George (southern Utah) while looking for a place to move to.
hmmm I hope it doesn't persist until they get evdo going there (supposed to begin in the next month). I also am having issues getting my phone to access the net without making me turn my phone radio on and off after using pie or poutlook and egress is useless. it says answering modem has been disconnected. no hard reset or roam update has seemed to cure it, neither has traveling north to baltimore or out to st george. since resets aren't working I am thinking I might need to get a new phone. good thing for insurance(also having issues with headset hole so speaker and earpiece are twitchy as of late).
I just spent a few days in Park City and encountered this for the first time (it's a 1x area, I'm normally covered by EVDO). It was annoying though not a dealbreaker for the weekend, but I can see how those of you who have to deal with it day in and day out would be at wits' end.
Login
Panel
