More Bad News for Android 5.0 Lollipop As Problems Come In for Nexus and Other Devices
It has not been a smooth sailing ride for Android 5.0 Lollipop as more problems reportedly arise. As the Nexus line has been the first series to receive the update most of the reported issues were observed in Nexus 5, Nexus 7 and Nexus 10 giving other Android users an insight of what they may run into.
Android 5.0 Lollipop has not reached all devices but it has been causing problems already according to BBC's recent report. Some users claim that their devices repeatedly crash and run slow making them almost "unusable." Adobe has also been having problems with some users saying that the Android code tends to remove apps based on the Adobe air. Reinstallation is also not possible. Adobe clarified that it was not aware of the situation before and has already taken the matter to Google.
The hype and demand for the Android 5.0 Lollipop update mainly stemmed from positive reviews prior to its release. Many analysts praised Google for overhauling its OS following a flatter design and a more interactive approach. Some went as far to say that the latest firmware is a quantum leap from what Google has been doing all these years. The improved user interface also reportedly gives more control over notifications. Google even promised that there should be fewer temporary glitches compared before. However, it may not be true for devices updated already.
In fact, a Google forum was entitled "Android 5.0 - A not so sweet lollipop for Nexus 7 2012" reflecting the problems that have been plaguing users since their installation. A user named "viranica" posted: "Once the device was up and running, I noticed that just browsing through the apps installed in my tablet and going through the new settings made it hot. Also all that useless animation made every action that I performed sluggish." The user has a Nexus 7 2012 edition.
Mobilesyrup also reported that Android 5.0 Lollipop showed some instability issues when the device's language switches to French Canadian. The bug causes the SystemUI to bootloop when the unit is either in the process of turning on or charging.
Google has yet to issue a list of fixes for the mentioned problems.