So, this little device behaves as if ANY bad CRC is 'good'. I am constantly forced to reload web pages that either come up as gibberish, so the web browsers attempt to 'download', resetting the DNS cache 'poisoned' by corrupted results, being forced to re-re-re-re-try connecting to VPN or over SSH, and of course, any download larger than a few dozen megabytes is guaranteed to be CORRUPTED.
You sure as heck aren't saving any bandwidth by making me do everything TWICE (and occasionally even more often). But you burn through my fixed bandwidth at double the rate, too.
Repositioning the router never helps. This is pure protocol. Someone has DISABLED (or the device is incapable of) error correction. When a 'bad' UDP packet comes in, TCP/IP is supposed to be 'smart' enough to send back and re-get any blocks of data that contain errors. Yet 'somewhere' every packet is getting stamped as 'A-OK', whether or not it's corrupted.
In other words, in any implementation of internet protocol, if you receive a UDP packet, it's 'guaranteed' to be correct, and TCP/IP is supposed to be BULLET PROOF. What I send to the server, and what the server sends back, should always be THE RIGHT DATA. Yet T-Mobile sends GARBAGE all the way through to my computer(s). It looks like compressed data with errors that cause it not to unpack, most of the time.
What this device seems to do is send every bit of bad data through to the OS. Making updates take longer. Making file downloads practically impossible. Basically rendering the entire experience of using T-Mobile an embittering one.
So far, I haven't figured out WHY error correction appears to be completely disabled. I can't find any settings that would disable (or more importantly ENABLE) this critical functionality.
And of course, now I have to 'copy' this post to the clipboard before posting it, because there's a better than 10% chance that IT WILL NOT WORK.