Re: Kevin Rush
No, probably not, but I'm not much of an Android enthusiast, although I have run pre-release builds on Android phones before, doing dev. work. There were issues, but usually not quite like this.
I've been running Alpha and Beta builds since Win 3.1, some of it as part of work, some just for my own edification. I get the issues involved, over all those years/releases, really, I do.
I think it comes down to things like 14393.5 on Release Preview, and the stability issues pushed out there. While I don't expect perfection, by any stretch, I also don't expect my phone to nuke its battery in a matter of a couple of hours, so that I have to hard-reset to get out of the loop, given that the reporting tools aren't accurately depicting the actual drain source.
If I had been on the Slow or Fast rings, I wouldn't have been so irritated, but RP shouldn't exhibit issues like this, particularly on the latest flagship models, which are certainly part of the test bed.
Not having WiFi calling/texting is more likely to make me jump ship, eventually, this is killing me on a lot of my winter weekends now, when I could have regular connectivity, but can't, because no carrier that supports Windows phones has coverage where I'm at, and no carrier really supports WiFi calling on Windows phones either, in the US (okay, so T-Mobile supports one phone, a one-off, doesn't count, IMHO).
Right now, I run a hokey, forwarded VOIP solution, which sort of works, maybe, on a good day, and drains my battery like crazy, by its polling nature.
MS should work with the carriers to get this ironed out, and use some of their influence, if they really want to showcase the OS, going forward.