It doesn't help when our expectation for performance keeps increasing over time. It seems to be a pretty common problem people have with technology. My 2 year old phone always seems bogged down and slower than my new phone. My new phone is nice and zippy and everything works wonderfully. It will work the exact same way in 2 years, but my expectations will be different.
There could be more to it than that (amount of apps installed, and I wonder if the device's flash memory slows down after so many read/write cycles).
Belazor, on 08 January 2013 - 20:00, said:
Yeah, I've heard the bit about iOS multitasking - IIRC apps can request to run for up to 10 minutes after they've been "closed" (brought out of focus), and they can only register to receive / display Push notifications past that limit. I'm not entirely sure if I see the benefit of having an app actually running perpetually in the background, though. Then again, I'll freely admit that my ability to think outside the box for these things is quite limited.
I wish it was easy to use the stock UI while still having display enhancements like the BRAVIA Engine and such - from my understanding they bake it into the kernel or other system files...
I guess I'll wait for the phone to come out and get someone to tell me the kernel it's running at and such before making a decision. My contract doesn't expire until the 26th of March anyway.
I'm no expert, but it seems like newer Android apps in 4.2 behave very similarly to iOS apps when it comes to multitasking. That is apps in the background disappear from memory when they haven't been accessed for some time and have to be reloaded. There are probably lots of different things going on under the hood.
iOS no doubt has a stricter multitasking API. I think only apps specifically designated as being used for navigation or VoIP are able to truly operate in the background.