While Google is busy getting Android M ready for release, the various Android Lollipop updatesare still rolling out worldwide - and in some cases they're causing problems. While for some (myself included) the Android 5.0 Lollipop update has been a buttery, svelte, velvety fairytale, there are a few gremlins lurking beneath the bright colors. So if you want to know how to fix Android 5.0 problems, here's the solutions to the bugs we've heard about so far. We'll add more as more issues come up, so stay tuned as we share more Android 5.0 solutions.
Awful performance
For most people, updating to Android Lollipop has made their hardware happier, their teeth whiter and their days just dandy. But some users have encountered a range of issues, including freezes, crashes, stutter and lag. In-place upgrades can be the cause of that. Installing updates on top of updates on top of updates can eventually cause problems, so a factory reset might be on the cards, but have a look at your apps to check they’ve been updated to Lollipop. As with any performance issues, try switching off anything you don’t need to see if you can identify a specific cause.
One problem discovered in Android 5.0 is a bug that makes apps restart in the background. Though recent apps should remain running in the background for when you return to them later, even those apps with persistent notifications are being affected.
This eventually hurts device performance the longer it is up and running. So far, the only known way to fix this issue is, somewhat ironically, restarting your device.
Missing system.img error
Lollipop issues can begin even before it is on your device. Some Nexus 5 owners flashing the factory image are experiencing problems with the installation of Android 5.0. During the procedure, they are informed of a missingsystem.img error.
It's actually not such a big deal. If this happens to you, you can flash the img files manually one by one instead of by using the flash-all.bat file. If you want a walkthrough, here's how to install Android 5.0 on the Nexus 5.
It seems that we can't have an Android update without something going wrong with either Wi-Fi, Bluetooth or both. There's the usual range of solutions: toggle airplane mode on and off, forget and reconnect to the network, reboot your phone, restart your router or switch between the Wi-Fi frequency bands. As you can probably tell, this is the 'clutching at straws' list of solutions. You may have to wait for a patch from Google for the permanent solution.
Android 5.0 overheating
Assuming you haven’t left your device in direct sunlight or near a wicked child with a magnifying glass, overheating is often a byproduct of really hammering the phone with apps such as 3D games. Your case might be contributing to the problem too - phones are designed to be case-free, and heavy cases can interfere with heat dissipation. It’s also worth trying Safe Mode to see if the culprit is an app that’s misbehaving.
Every new installation of Android firmware results in some battery drain for some users. This is almost always because the update was applied over the top of existing firmware rather than installed 'clean'. There are a few things that could go wrong when everything is set up one way on your phone, and then the world shifts beneath its feet.
So now may be the time to bite the bullet, do a full backup and do a factory reset. You can do this via the Settings > Backup & Reset section or manually with the hardware buttons. Just search the site for your particular device and 'factory reset'.
Nexus 7 (2013) owners have reported some bugs with video playback following the update to Lollipop. The issue doesn't seem to be restricted to any particular app, but YouTube is, of course, at the center of the furore. Any app that uses the default Android video player suffers though.
If YouTube is the issue for you, hit Settings > Apps and find the entry for YouTube. Clear the cache and try again or do a reboot for a temporary fix. You can always try uninstalling and reinstalling the app if problems persist. Some users are reporting that this has solved the problem, while others continue to suffer.
If you have a better fix let us know in the comments below. Worst case scenario: backup all your data, do a factory reset and clear the cache partition.
Nexus 9 owners who got the update patch immediately following the public rollout of the Android 5.0 update have been experiencing some issues with installing the OTA update. Basically, everything hangs up and then reverts back to the previous version without installing the update.
If you know what you're doing, it's a simple procedure to flash the latest factory image for the Nexus 9 yourself, otherwise you're going to just have to wait until Google issues another bug fix to fix the bug fix. Sound familiar?
If you leave the flashlight on for a while, like when you're struggling to find your keys in the dark, and it automatically times out, then both the flashlight and camera will be busted until you do a reboot. This is pretty weird stuff but it occurred in the developer previews too. It's odd that Google didn't bother to iron this one out, as it's a pretty well known issue on the Nexus 5 already.
No silent mode, status bar ticker or Power button menu
Sadly, these are 'improvements' rather than problems. You can't simply volume down to silent mode (only to vibrate), there's no option other than Power Off when you long press the Power button, and the status bar ticker – that little scrolling preview of notifications – has been killed with fire in the latest version of Android.
We expect the masses to rise up shortly and some changes to be made, or at least some workarounds figured out if you're willing to tweak your phone a little. In any case, we've already explained how to enable silent mode on Android 5.0.
This probably shouldn't come as too much of a surprise, but Google doesn't necessarily want your rooting or otherwise modifying your device or firmware. So if you've modded your Android a bit, you may not be able to install the OTA update.
Fortunately the solution is pretty straightforward: simply flash a stock image again and OTA will be hunky dory once again. Check our article on broken OTA updates for Android 5.0 Lollipop for more info.
This could be explained away by raised expectations: while Android supports Qualcomm's QuickCharge 2.0, not every phone does - and those that do don't always ship with a QuickCharge charger. There are also known incompatibilities with some third party fast chargers, so if you’re encountering issues with one it’s worth trying another charger (if you can) to see if the problem goes away.
Android 5.0 Recent apps switcher
The recent apps card stack is a nifty new addition to multi-tasking in Lollipop. But not everyone is a fan. Some users are claiming that, the more apps they have stacked, the slower their performance becomes, while others are noticing that even when a card has been removed from the stack, it mysteriously returns. Even after a reboot your recent apps list will persist, so the only way to fix this one is to simply keep on swiping. Forever.
Chrome Browser on Lollipop is set by default to store new tabs in the recent apps list, but for many this represents one of the biggest Lollipop fails of all. Fortunately, all you need to do to change this is head to your Chrome settings and disable 'merge tabs and apps' to return to the more familiar 'number in a box in the URL bar' that brings up your tab list, as it always has.
What other Android 5.0 problems have you found? Got any solutions we missed?
This is a short description in the author block about the author. You edit it by entering text in the "Biographical Info" field in the user admin panel.
0 comments:
Post a Comment