[winterswift]

I kind of wonder if that's because a lot of updates are rolled out poorly to older devices. On my previous two phones, I've ended up running CyanogenMod or another third-party ROM, even at the same base Android version at the stock OTA updates, because many times even the RC versions run better than what's getting pushed by the carrier. Verizon customer here though, so I don't know if other networks are better about that. I also wouldn't be terribly surprised if that effect (wanting a new phone over an update) is intentional.

[derekp7]

Part of it is just change. One day, I needed to pull up the map on my Nexus phone -- and it had a completely different interface to it. I had to sit in a parking lot for an extra 15 minutes to get it to do what I wanted.

Now I've got KitKat, and the phone dialer has changed -- I have to hit an extra button to get all my contacts, and I don't like the "premium" spots being automatically populated (there are only 3 large icons, and room for two smaller icons, in the quick-access screen). The most important contact is the one I need right then.

Oh, and I also have to re-agree to the license terms on a number of apps whenever I launch them the first time after an upgrade. And my tethering is no longer working. And the flashlight app that worked fine is now rebooting the phone randomly after it is on for a few seconds. At this point, I'm ready to wipe and re-install the older OS version.

[lostlogin]

Depending on what flashlight app that is, crashing might actually improve it. http://m.fastcompany.com/3023042/fast-feed/this-popular-flas...

[derekp7]

In this case, it was the free/free one from F-droid -- I always go there first for utility-type apps, before hitting one of the app stores. I think this is actually why I was so upset, is I don't want to have to resort to a flashlight app (or any utility for that matter) that may be doing other things behind the scenes.