You consented to it, sure. This bug affected millions of phones. It's more like a car manufacturer decided to put a particular explode-y gas tank in a car, because it provided greater performance.
Nitpick: there's a big difference between an app crashing (which is what this sounds like) and an app crashing your phone (rendering it unusable or forcing a reboot).
The difference between android and iOS and windows phone is that android has an open bug tracker, making issues like this a lot more visible. Maybe this issue doesn't affect many people, or google determined that it only happens for phones on a certain carrier and can't disclose that publicly. Sure, the bug could have been closed with a friendlier message, but an open bug tracker seems like a good thing to me
On the side note I thought Android has very few bugs probably because I don't use my Android phone a lot but I encountered one pretty annoying bug last week and I was unpleasantly surprised.
Yeah just try using your phone while Google's updating some crap in the background again... Doesn't depend on the newness of the phone either — this happened on every Android phone I've owned since 2011.
There are _a lot_ of ui bugs. I easily hit 24 an hour with some products.
I probably hit at least 24 bugs a day on my phone. Apps crashing. Back not working right. Apps popping up and disappearing. Unexpected latency causing wrong things to be clicked on. They're all just papercuts, but there are so many of them.
reply