Google’s new Android 5.1.1 Lollipop update for Nexus devices brings fixes for lingering Android Lollipop problems. However, it also appears to deliver some problems of its own. With that in mind, we take a look at five things you need to know, right now, about Nexus Android 5.1.1 Lollipop problems as we push further away from its roll out.
In November, Google released an Android 5.0 Lollipop update to replace its Android 4.4 KitKat upgrade. The Android 5.0 Lollipop operating system is a massive change from Google’s previous version and it’s one that many Nexus smartphone and tablet users have installed in the months since its arrival.
While the new operating system brought a lot of new features and functionality, Android 5.0 Lollipop also delivered a collection of problems to owners of the Nexus 5, Nexus 6, Nexus 4, Nexus 7, Nexus 10, and Nexus 9. Lollipop problems have been a problem since November though Google’s attempted to smash those issues out with a series of bug fix updates.
First, Nexus users received Android 5.0.1 Lollipop. A few days later, Google rolled out Android 5.0.2 Lollipop to select Nexus devices. After those, Google rolled out a more substantial bug fix update in Android 5.1. While these updates did tackle some Lollipop problems, they failed to correct every single one and they even brought some problems of their own.
Android 5.1 in particular brought a number of Lollipop problems to Nexus users, so many, that Google decided to issue an Android 5.1.1 update to Nexus owners. Android 5.1.1 was confirmed last month and recently it started rolling out to big name Nexus devices.
The update is slowly making its way to Nexus users and we’re slowly starting to see feedback about Google’s latest Android 5.1 update emerge. Unsurprisingly, that feedback includes complaints about Android 5.1.1 Lollipop problems.
Over the past few days, we’ve started to see chatter about Nexus Lollipop problems pick up and today, we want to sift through that noise and offer you a glimpse at the most important things to know.
This roundup will walk you through what you need to know about these initial Android 5.1.1 problems, what you can do to prevent Nexus Android 5.1.1 Lollipop problems and what you need to know about Android 5.0 Lollipop’s future.
Android 5.1.1 Problems Plaguing Nexus Users
The first thing Nexus users need to know is that Android 5.1.1 problems have already started to plague owners of select Nexus devices. The Android 5.1.1 Lollipop roll out is still very young but we’re already starting to see negative feedback from users who have installed Google’s brand new software, software that’s supposed to help, not hurt, the Lollipop experience.
Nexus 7 2012 users are complaining about horrible lag after making the move to Android 5.1.1 Lollipop. Lag and performance issues have been a problem for many Nexus 7 2012 users since the release of Android 5.1 and it looks like Android 5.1.1 is also causing problems for some users.
@admillios Horrible lag. Horrible! Freezing on black screen. The good news though, is that battery life is incredible. 😉
— Joe Beardsley (@JoeBeardsley) May 7, 2015
Nexus users are also complaining about broken applications including Gmail problems, Android 5.1.1 installation problems that some users have been able to fix with a factory reset, a problem with the GUI, tricky issues with internal memory, problems with Google Music another app that was causing problems for users with Android 5.1, and the usual smattering of battery drain complaints.
It’s important to note that most of these problems appear to be very isolated. It’s also important to know that we could see Android 5.1.1 problems pick up as we push deeper into Google’s roll out. The update is only available for the Nexus 7, Nexus 9, Nexus Player, and Nexus 10.
Now, we don’t point these Android 5.1.1 issues out to be annoying or mean, we point these out because Nexus users will want to take stock of these issues before installing Android 5.1.1 Lollipop.
If you’re experiencing relative calm on Android 5.1 Lollipop or below, you’ll probably want to wait a few more days to see if more problems pop up. Minor issues will always emerge but it’s the major issues that you should be worried about. So far, we haven’t seen any widespread Android 5.1.1 Lollipop problems hit Nexus devices but the update is still in its infancy and there’s a long way to go.
Android 5.1.1 Problems Aren’t a Problem for Everyone
While Android 5.1.1 Lollipop problems are affecting some Nexus owners, it’s important to note that they’re not affecting everyone.
We recently installed the Android 5.1.1 update on the Nexus 7 2013 and after spending a number of days with it, we haven’t run into any significant problems. Connectivity is very solid, battery life is holding up, we haven’t noticed any lag, and we also haven’t stumbled upon any catastrophic, game-changing bugs. The Android 5.1.1 update on our Nexus 7 2013 is very stable.
Nexus users have been offering feedback and a lot of it has been positive. One Nexus 7 2012 user tells us that his battery life is excellent after the Android 5.1.1 update, a big plus given that this might be the last update the aging former flagship gets from Google.
Other Nexus 7 2012 users are saying that Android 5.1.1 has delivered an improved experience. Some of the issues that plagued them with Android 5.1 have dissipated after the release of Android 5.1.1. This doesn’t come as too much of a surprise given that Android 5.1.1’s sole purpose is to fix Android Lollipop problems.
We’re also hearing that memory leak problems that plagued users on Android 5.1 seem to have vanished for some Nexus users. We haven’t seen any reboots or app crashes on our Nexus 7 2013 and we haven’t seen any widespread complaints from Android 5.1.1 users, at least not yet.
We will almost certainly continue to see feedback (both positive and negative) emerge as the Android 5.1.1 Lollipop update makes its away to more Nexus smartphone and tablet users. With that in mind, you’ll want to do your research before diving in with the Android 5..11 Lollipop update. Ask around, find a forum and gather feedback before making the move to Google’s latest software.
As of right now though, we’re seeing more positive feedback than negative and that’s a very good sign for the future.
Fixes for Android 5.1.1 Problems
Nexus users should know that there are some potential fixes for some of these Android 5.1.1 Lollipop problems and bugs. If you head to the Nexus Help Forum, you’re going to encounter a series of threads dealing with Android 5.0 issues, maybe none bigger than this one. Many of those threads contain potential fixes for your device. We’ve discovered a number of possible fixes on there over the years and they’re a great place to start.
We’ve also put together a list of common Android 5.1 problems along with fixes for those problems. Keep in mind, those fixes aren’t guaranteed to work for your Android 5.1.1 issues but there’s always a chance that they’ll work or at least get you heading in the right direction.
We also have an extensive list of smaller tips that could help improve your performance. Take a look at all of those before slamming the device into a wall.
You Have Options
If you are currently on Android 5.1.1 or if you’re on Android 5.1, Android 5.0.2, Android 5.0.1 or Android 5.0 Lollipop thinking about making a move to Android 5.1.1, know that you have options available to you.
First of all, those of you on older versions need to know that you do not need to install Android 5.1 Lollipop right now. In fact, there are some reasons why you might want to skip the update when it arrives. (The same reasons apply to Android 5.1.1.) Those of you on older devices like the Nexus 7 2012 will want to consider holding off for the time being, at least until you can get more prepared. Older devices typically run into the most trouble.
If you are on Android 5.1.1 Lollipop already and the experience isn’t up to snuff, you can always flash to another piece of software or a more stable ROM out there in the development community. It’s the gift and the curse of the Nexus program. You’re a guinea pig for Google’s new Android software but you also have access to an unlocked bootloader and a device that’s easily rooted.
If you’re unsure how to flash to another version of Android, check out our guide. It’s a great starting point for beginners and it will fill in a lot of the questions you might have about the process.
Finally, you Nexus users also need to know that you’re most likely going to need to rely on these options and temporary fixes for the foreseeable future.
Google hasn’t announced an Android 5.1.2 update or an Android 5.2 Lollipop update. Google rarely announces details ahead of time and at this point, given the rapid succession of Android updates, we’re not expecting to see Google roll out another Lollipop update tomorrow or the next day.
Android 5.1.1 appears to be fairly stable and the update appears to have tackled some of the more glaring Android 5.0 Lollipop problems. In other words, there appears to be no reason for Google to release another version of Lollipop in the near future.
With no Android 5.1.1 replacement in sight and rumors non-existent, you’ll need to be extremely proactive if you do run into Android 5.1.1 problems.
Google I/O 2015 is expected to be the launch pad for Android M, the successor to Android Lollipop. While Google has released major Android updates at the mid-year in the past, there’s no reason to believe that Android M will arrive anytime soon. Android M will almost certainly come with bug fixes but there’s a good chance that it won’t arrive until November.
If Android 5.1.1 problems persist, we could see Google roll out at least one more update to shore up issues ahead of the Android M release. If not, you could be stuck with third-party fixes as we push deeper into the year.
Samsung Galaxy Android 10 Update Info (2020)
With the Samsung Galaxy Android 10 update rolling out and new info starting to emerge, we want to take you...
61 Exciting Things You Can Do With the Apple Watch
The Apple Watch is a smartwatch that connects to your iPhone to deliver notifications, make calls, send texts, and run...