Quote:
|
Originally Posted by sean48238
If its just the encoding then why did it work at one point? I know Verizon and Tmoible didnt decide to simutanously to turn off recieving binary messages. So what changed? We were never issued update so it wasnt the way the phone delivers the message. This seems like a BS answer to me. I know how the text messaging works and our messages are sent to sprint decode and then forwarded to the recieving company in there format. If thats the case it would seem like a sprint issue and there are just being some lazy asses and not fixing the problem. I am going to call sprint and dig real deep and see if I can get a logical answer.
|
According to one rep from Sprint (and this actually makes sense) Sprint was upgrading/fixing their SMS system during the last couple of months, hence why even devices like the 700P were running into days without SMS, others experiencing no messages or repeated messages...
Basically, Sprint's network was patchy and so was/is the 700wx on SMS. Both canceled each other out re: this ASCII/Binary issue. It looks like Sprint's network USED TO convert the messages from binary to ASCII before it went "outside" the system, but that's the "old" way. Almost everyone now uses straight ASCII and guess what the 700wx
can't do? Proper conversion.
Sprint fixed their end and low and behold, Palm's method of SMS on the 700wx was 100% incompatible w/the new system (every other phone handled it just fine)
I mean, think about it:
- ONLY the 700wx is affected, therefore is seems odd to say "it's Sprint's network".
- We can send/receive on the Sprint network
- We can receive from anyone with no problems
- ONLY thing we can not do is send to Verizon or T-mobile (presumably Cingular still can read binary)
That to me sounds 100% to do w/ something not coded right on the 700wx. And I don't think Sprint would be keen on
nationally rolling back their SMS network upgrade, which was patchy and inefficient just for the 700wx, imo.
From
Shadowmite (who is
very reputable on these issues)
"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."
also
Sprint has had a SMS system in place for quite a while now that had some improperly done parts. WM5 has also been a little flakey on it?s SMS handling. Appearently, at some point someone ?patched? the problems on sprints side I would imagine and as a result, broke the 700wx. So we now have to wait and see if the problem is fixed on the wm5 side, or if it will be re-fixed on the sprint gateway side.
In another interesting bit before this fix happened we appearently had a issue with improper base64 encoding or decoding at the wrong times. This is what was ?fixed? and broke the system as it now is.