There were a couple of updates that were supposed to have fixed that problem. Of course AT&T sat on the updates for months, and the get-warm-and-die issue was never truly fixed. The feedback loop is on the order of six months, if not longer.
The carrier is clueless about how to deal with firmware issues other than doing lots of up-front testing before releasing updates (and it's really unclear how effective that testing actually is). If you're in warranty they'll offer to replace the phone (gee, thanks) but of course they are powerless to truly fix anything.
So my experience with a showstopper bug was (a) over a year to a non-fix, (b) utterly useless support from the carrier, and (c) no indication that MS even knew about the issue, other than rumors from my friends in the WinPhone division that the next patch would fix it (and it never worked).
Is there a way to get support from MS on this? I have to admit that I never checked. (The issue is moot for me, but shortening the feedback loop would help WinPhone quality a lot).
I never waited for the carrier to update the phone. We've been able to get updates via the free "developers" program within short windows after announcements of said updates. e.g. Just installed the update yesterday that was announced at Build 2 weeks ago? I have a device on each platform and my Note 3 gets used for consumption, my iPhone collects dust, and my Lumia 920 does most of the daily business. Still my favorite.
The carrier is clueless about how to deal with firmware issues other than doing lots of up-front testing before releasing updates (and it's really unclear how effective that testing actually is). If you're in warranty they'll offer to replace the phone (gee, thanks) but of course they are powerless to truly fix anything.
So my experience with a showstopper bug was (a) over a year to a non-fix, (b) utterly useless support from the carrier, and (c) no indication that MS even knew about the issue, other than rumors from my friends in the WinPhone division that the next patch would fix it (and it never worked).
Is there a way to get support from MS on this? I have to admit that I never checked. (The issue is moot for me, but shortening the feedback loop would help WinPhone quality a lot).