Linked by Thom Holwerda on Wed 6th Jun 2012 23:34 UTC
Thread beginning with comment 521233
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Where does this leave Sprint?
by Morgan on Thu 7th Jun 2012 19:27
in reply to "RE[3]: Where does this leave Sprint?"
You're right, it's that tight control that likely leads to the stability and responsiveness of the device. It's a trade-off, and one I'm willing to make when it means the difference between keeping a client satisfied or not. Speaking of, I just got a call from the same client my Admiral had hung up on several times last week, and the first thing she asked was "did you get your phone fixed?" That speaks volumes to me.




Member since:
2011-05-19
You may have less crashes in more tightly controlled environments (iPhone) or envirnments with less (interesting) apps (Windows mobile).
On the contrary, Windows Mobile was very easy to kill. I had an HTC Windows Mobile phone that would freeze up multiple times a day. Even doing a hard reset wouldn't solve it. Finally, I read up on the XDA forums and did a hard reset -- but also skipped the carrier customizations. That left it in a state in which it was running only stock Microsoft code + drivers, the thing would stay up for a month.
That was when I concluded Windows Mobile had no future. Having OEMs preload craplets on Windows PCs is bad enough -- but doing the same thing on a phone, and preventing me from receiving calls? I simply don't have time to baby my phone like I do my computer.
And that was only the carrier preloads! I didn't install anything else on that phone!
Or perhaps you meant Windows Phone. That falls into the iOS category of "tightly controlled."
Edited 2012-06-07 19:18 UTC