Page 13 of 42 FirstFirst ... 38910111213141516171823 ... LastLast
Results 241 to 260 of 836
  1. #241  
    Quote Originally Posted by chazman View Post
    Is it ironic or suspect that these problems really started kicking in the same week the 750v threaded SMS hack came out. Maybe sprint was trying to be witty and block the 750 hack?

    Just another theory,

    Chaz
    These problems started the week of October 2nd. Not the week the 750 SMS app came out. Nice try Columbo
  2. #242  
    lol....Columbo
  3. #243  
    If you guys were to switch phones or service providers, where would you go, and what phone would you get into? I am having trouble finding a phone on another network I like as much as my WX...unless I went to a blackberry
  4. #244  
    Motoracer,
    That is a tough call, and one that I am debating myself. I left Cingular about 2 months ago and had an 8700 series blackberry that I liked very much. I left specifically for the 700wx - primarily because it is a better phone and I really like the today screen (I have a tendency to not actively check my schedule and quickly dismiss reminders.) I didn't like the 3rd party today screens for the blackberry. I think that if this doesn't resolve, I'll go back to the 8700 series blackberry - but that would really p!ss me off. That would be a grand waste of money, just to switch from Cingular to Sprint (I paid an ETF to do this). I'm hoping this will be resolved soon and be a moot point. My $0.02

    -AV
  5. #245  
    Quote Originally Posted by Motoracer View Post
    If you guys were to switch phones or service providers, where would you go, and what phone would you get into? I am having trouble finding a phone on another network I like as much as my WX...unless I went to a blackberry
    with the blackberry you will have twice as much money in data. plus not as many apps for blackberry.

    altho it was a stable device.
  6. #246  
    I dont know what to do. I want to try to tough it out, but after speaking with sprint AGAIN today, no one has any estimated time of when anything will be fixed...

    Any other ideas would be apprecitated.
  7. #247  
    Codyppc,
    That is a good point about the data costs. For now, I'm sticking with the 700wx - but not happy about the current situation. Fortunately, we can still email and text to some people. Could be worse - but certainly not acceptable for much longer. Is there anyone that we can complain to other than CS and ecare who will actually listen. I can't imagine that Verizon customers have to deal with this
  8. #248  
    My latest email to Sprint. We will see what they respond

    Is there any update on the status of this issue (Treo 700wx sending text messages to other carriers). It has been over 2 weeks and none of us are able to send to TMO or Verizon. Unfortunately, most of us bought this device (at a hefty price, I might add) specifically for the ability to communicate with email and text. So, this is really defeating the purpose of our purchase and Sprint is starting to offend a very large customer base who incidentally likes to pay a lot for devices and data plans. If there is an estimated fix date, please let us know.
  9. #249  
    Well, I was debating getting the 6700, but I really need the ability to use a device one handed completely. I'm not going to lie I'm really impressed with the 700p, if you guys need an option you could switch to that. I might go for awhile until they get the WX all figured out and sell the P on eBay and get the WX or something. I'm so surprised this cannot be fixed quickly or that Sprint even seems concerned. "Sorry we don't know when it will be fixed" WTF, that's what pisses me off! And whatever noob thinks this is the result of the threaded SMS is a day late and a dollar short.
  10. bmargolis's Avatar
    Posts
    67 Posts
    Global Posts
    68 Global Posts
    #250  
    Quote Originally Posted by TreoMeat View Post
    Well, I was debating getting the 6700, but I really need the ability to use a device one handed completely. I'm not going to lie I'm really impressed with the 700p, if you guys need an option you could switch to that. I might go for awhile until they get the WX all figured out and sell the P on eBay and get the WX or something. I'm so surprised this cannot be fixed quickly or that Sprint even seems concerned. "Sorry we don't know when it will be fixed" WTF, that's what pisses me off! And whatever noob thinks this is the result of the threaded SMS is a day late and a dollar short.
    I switched FROM a 6700 and feel that even a crippled 700wx is a far better device than the 6700 was. I absolutely hated it for the half year that I used it. My personal needs for text messaging are pretty small. I only use about 60-70 messages per month and at least half of those are to my own family, that is all on Sprint. For the few messages that I have to send to TMO and Cingular users, I'll live with the full messaging work around as I have to. I do agree that Sprint is dropping the ball here in a HUGE way and I hope they compensate us all for this. I won't switch, not at this time and probably not at all...but I do hope this is fixed very soon.

    Bob
  11. #251  
    I called sprint...talked to several people....FINALLY got through to someone very helpful. She was not aware of the problem, but I gave her the link to this thread and she's reading it right now with me on the phone...hopefully we can get somewhere...this is INSANE!
  12. #252  
    This is the response to the email I posted above. What is so crazy is that we are almost 3 weeks into this & very few people at Sprint are acknowledging that this is a problem. I may leave just because of that fact alone.

    Response :"I can understand your frustration and I apologize for the inconvenience. I will resolve your issue with text messaging.
    I apologize for the inconvenience that this issue has been causing. I'm sure everything is being done to fix this issue. However the problem may not even be with sprint it could be with one of the other carriers. So I suggest that you contact the other service providers to check to see if there are any known issues on their end."
  13. #253  
    Just got off the phone with Sprint, went up a couple of levels and got someone who sounded like he knew what he was talking about. Take all this with a grain of salt, because he could have just been BS'ing me... but here is what I was told today.

    The problem has been isolated... It effects most, but not all 700Wx's because some still are working. The problem is in the SMS send, when it sends the message to the network, there is an encoding process. I'm not sure what that entales, but there are several flags that get populated by the device before the message is sent out. One of those is not being coded correctly. Apparently its a flag that tells the system how the message is encoded.. a 0 means its not encoded and a 2 means its encoded a certain way. He said the problem is that our devices (those with this issue) are encoding the messages with a 0, not a 2. He said they had sent the logs of these messages and such over to Palm and have been working with them the last few days to get a resolution. Palm is supposedly going to be coming back with a solution mid-week next week in the form of a firmware update of some sort. He didn't know if it was going to be an update that we load, or an over-the-air type of update however.

    I asked him directly..."Can you tell me why my device worked since release, but then all of a sudden stopped working?" He said he couldn't answer that and I repeated my BS call on it being a device issue since NOTHING has changed internally on the device since I got it. Still he had no definitive answer only to say they know what the problem is and its being worked on. He also sounded a bit frustrated.. which is good.. apparently MANY people have called about the problem.

    Anyway... in addition to the previously posted national alert, he also gave me this one #871665 that is reportedly the 700WX issue itself.

    That's the latest I was given.. for what its worth.
  14. #254  
    here's what Sprint been saying to me..

    Thank you for contacting Sprint together with Nextel
    I would like to apologize for your frustration in this matter
    The service you are mentioning is only for sending messages to current
    Sprint customers. I had a look at the link and one of the other users of
    that chat, mentioned what I mentioned to you regarding this service only
    being for Sprint customers. I will contact our tech department to mention
    the above concerns and see if there are any other customers complaining
    about the same problem. I thank you for your patience in this matter and for
    bringing this to our attention.

    We, at Sprint together with Nextel appreciate your loyalty to our business,
    If you have any further questions or concerns, please don't hesitate to
    email us back. We would love to hear from you. Have a terrific weekend!

    Nicholas L.
    E-Care
    Sprint together with Nextel
    "Where our customers come first!"
    _________________________________________________________________

    Next one..

    Thank you for contacting Sprint together with Nextel. I will be happy to assist you regarding your SMS Text Messaging problems. I apologize for the disappointment in not being able to send SMS Text Messaging.

    I have checked for service alerts on SMS Text Messaging and came across none as of October 21, 2006. The only way to determine your problem is for you to call our technical support. I am unable to resolve your issue through the e-mail venue. I apologize for this situation being unresolved to your satisfaction. In order to determine the problem with your phone, we may need to perform a few simple tests on it. Please contact us at 1-888-211-4727 from a phone other than your PCS phone.

    When you hear the voice prompts, say ?Wireless Web?. You will be forwarded to Technical Support where a specialist will be glad to assist you.

    Thank you for choosing Sprint as your wireless communications network. Sprint values our customers. Have a wonderful day!

    Ruthanne W.
    E-Care
    Sprint together with Nextel
    "Where our customers come first!"




    If any of you would like to email sprint here's the email:

    ecare1@cc.sprintpcs.com

    The more people we get emailing and calling, the more, hopefully some resolution to this problem!!

    Sprint is denying any problem at this point!!!
  15. #255  
    Your answer is in my opinion almost perfectly correct. I saw there was a glitch in the treo 700wx's texts which could sometimes lead to a message being left in a encoded base64 state when it shouldn't be, or encoded sometimes when it shouldn't be. Sprint had a minor part of that, they fixed it around the time this new bug began. The problem is palm's side has a equal mistake... It'll require a palm update to fix correctly, though sprint could patch their systems "incorrectly" again to fix it also... It's a matter of perspective.
  16. #256  
    Quote Originally Posted by shadowmite View Post
    Your answer is in my opinion almost perfectly correct. I saw there was a glitch in the treo 700wx's texts which could sometimes lead to a message being left in a encoded base64 state when it shouldn't be, or encoded sometimes when it shouldn't be. Sprint had a minor part of that, they fixed it around the time this new bug began. The problem is palm's side has a equal mistake... It'll require a palm update to fix correctly, though sprint could patch their systems "incorrectly" again to fix it also... It's a matter of perspective.

    That would explain why it stopped working for us then... Sprint fixed their portion of it and it left Palm as the remaining factor. Have to say that if they KNEW it was a problem and didn't coordinate things with Palm, that is a big screw up on their end since it effectively killed the service for a sector of their subscribers.. unless the fix was geared towards other devices etc in which case, we were the smaller group to offend.
  17. #257  
    I got another email response from tech support...here is is just to keep everyone posted!

    As of now..the word on the issue is that it is a software issue on the device and we are waiting on microsoft to come out with a software patch/ resolution updater download to resolve this issue. Apparently somewhat like a software bug. Will keep you posted!
  18. #258  
    Quote Originally Posted by shadowmite View Post
    Your answer is in my opinion almost perfectly correct. I saw there was a glitch in the treo 700wx's texts which could sometimes lead to a message being left in a encoded base64 state when it shouldn't be, or encoded sometimes when it shouldn't be. Sprint had a minor part of that, they fixed it around the time this new bug began. The problem is palm's side has a equal mistake... It'll require a palm update to fix correctly, though sprint could patch their systems "incorrectly" again to fix it also... It's a matter of perspective.
    Shadowmite - any theories on why the new threaded app still causes the problem? Is the code base shared for the message apps and still setting the wrong flag? I was hoping the threaded app might fix the problem.
  19. #259  
    The threaded app does not fix the sms encoding problem. I was hoping it would also.
  20. #260  
    At least there's a CS rep. or two that actually sound like they know what they are talking about in terms of the encoding.

    Assuming everything is true as stated above, we now have to wait for Palm...yay

Posting Permissions