At the end of the day, the blame falls more on T-Mobile. They gave the 810 the EOL treatment after a few months of being out in the market. What came next was the 521, which is inferior to the 810, and then soon after the 925, which is superior. They decided to support those phones and leave the 810 in the dust. In this case T-Mobile screwed up. Here's why I know it's not Nokia aka Microsoft's fault... Both the 820 (AT&T) and the 822 (VZW) are almost the same phone as the 810 with the exception of LTE supposedly. Both the 820 and 822 are slated to get 8.1 Cyan in the near future. SO in this case it's not MS or Nokia's fault. This one falls solely on T-Mobile. If people can install the WP Developers Preview on the 810 and work with little to no problems, then that there is proof enough to go after T-Mobile. I would have done it myself but I ended up getting an unlocked 920 and never looked back.
1. Did you read what I said just a few comments above you?
2. The 810 is actually more varying in hardware than the 820 and 822. For instance, support for the 1700MHz frequency, combined screen tech from both the 820 & 822 (the 820 has a polarization filter while the 822 is Corning Gorilla Glass 2), uses a different Bluetooth module (based on BT3.0 rather than BT4.0), and likely other underlining changes that are harder to notice (most of above can be ascertained by comparing the spec sheet of all three devices.). For instance, the 521 has an additional sensor on the back of the device, that when compared to the 520, the 520 does not have one (
view this thread post for more). As such, it is possible that there is a fundamental difference in the underlying hardware that makes this phone different enough that one can't simply 'tweak n go' the firmware for the 810.
3. The blame can be anywhere from T-Mobile refusing to allot resources to test the firmware to Nokia refusing to allot time and resources without an incentive to do so from T-Mobile, to the other, very possible reasons I listed above. We have no
solid proof of blame for either party. All we have is a couple of varying customer service rep responses with questionable reliability (I'm sorry, but as Walmart Family Mobile is an MVNO powered by T-Mobile, I highly doubt they would have more info than T-Mobile themselves, especially when it comes to a service rep.), and the fact that the device is EOL (due to poor sales, most likely), meaning neither party is required to provide updates of any kind to the device.
______________________________________________________________
Honestly, this thread should be closed,
EXCEPT for the fact that it would become of use in the case that any headway is made on the issue, or in the case that it actually receives a new firmware update.
I couldn't care less about firmware. In fact, Cyan removes bar code scanning, and the Nokia System apps bring 90% of the new features as long as you have the latest OS, firmware or not, so to it I say good riddance.
Facebook
Twitter
Instagram