Android Lollipop or Lolliflop?
Officially announced at November 2014, Google had us excited for this new version of Android even since the Developer Preview came out. It was a major update that came with a new brighter, more colourful, and more beautiful UI. Something that Android fans had been wanting since Apple released iOS 7, a major UI overhaul.
Not only on the UI design department, Lollipop is also said to come with several under the hood improvements such as the ditching of Dalvik for ART Runtime, better battery usage, better application performance, and many more. It had many Android fans jealous of the Nexus users who had their hands on Lollipop first.
Fast forward a few months, it has been about a year since then and there have been more and more devices that either comes or are updated to Lollipop. However, Lollipop user experience has been more of a mixed bag. Here are several issues that showed up on devices that are running Lollipop.
Memory Leak
First noticed on Google's own Nexus 5, the memory leak on Lollipop is when the device uses up so much RAM that it slows down the device and kills apps that are supposed to be running. The only way to fix it is by restarting the phone. The 5.0.2 update is supposedly to fix this problem but yet it appeared again on 5.1 update. But after the 5.1.1 update was released, many people claim that this problem disappeared. Let's hope it won't show up ever again.
 |
| "Yummy, gimme more RAM!" |
Bigger Battery Drain
Wait what? Turns out the battery performance thing mentioned in the new features is a Battery Saving Mode which turns off animation and lower performance when the battery reaches certain point. It's cool and all but it turns out it gets turned on faster than expected. Stand by time has been worse than KitKat and if seen from the battery usage information in Settings, the main culprit seems to be Google Services. Not only on Lollipop though, I've noticed that almost every Android device is affected. It may have to do with the newer version of Google Service which came out after Lollipop.
 |
| Google Apps, the source of all evil |
Lower Gaming Performance
When you have the latest OS while apps are still not updated yet, this is bound to happen. There were a lot of performance issues in many games when Lollipop recently came out. But usually these problem disappears once the app is updated. That's a good thing but there are a few lazy developers who won't bother updating since the number of Lollipop users isn't that much yet, hell there are some that won't even bother updating at all (Batman The Dark Knight Rises, The Amazing Spiderman 1, etc..). So if you want stable gaming performance, it's better to stay put in the previous OS version until all apps are updated.
 |
| Y U No 60fps?? |
I think the jump to Lollipop is similiar to the jump from Gingerbread 2.3.4 to ICS 4.0. A huge leap that causes many issues. It took a while for 4.x series to get really good, 4.4.4 to be precise, which would've been perfect if it weren't for Google screwing up with the external storage access. Let's just hope it won't be that long before Google polishes up Lollipop. The 5.2.x update, code named Android M, should be released in Q4 soon.
Source
Comments
Post a Comment