Android Lollipop Update Causes “Unusable Devices” Problem
Newest Android member, Android Lollipop is causing crashes on various smartphones and tablets even if it was designed to connect with all other Android versions in a revolutionary manner. People who upgraded their devices to Android 5.0 Lollipop have complained about various problems including slow response from input commands, broken apps or error messages which claimed “unusable update”.
The latest Android update was introduced last month, and it is designed to be used on different devices, even powering smart watches, TVs and cars. However, since its release, many Android users complain about the problems they encounter with their devices once the upgrade was done.
These issues are more present on Google’s Nexus range of smartphones and tablets – but not limited to Nexus -, including the latest additions to the series, Nexus Phablet and Nexus 9 tablet. Both devices were unveiled last month alongside Lollipop update.
Many users reported problems also with Wi-Fi connectivity and sound quality while running apps created with Adobe Air tool have been removed from some Nexus devices without any possibility to re-install them,
Adobe program manager Chris Campbell stated that Adobe has passed the problem to Google, suggesting that only G is responsable for this issues. Campbell was also clear about the involvement of Adobe on fixing this major issue with Google by firmly pointing on Google’s fault.
On the other hand, Google spokesman confirmed that “some Android users are facing issues” and they are “looking into what might be the cause”. Before a fix will be announced, it is recommended not to upgrade your device to Android 5.0 Lollipop.
Those who already performed the update should check which apps are running in the background and to maintain a low level of usage by killing any undesired app; this will increase its performance and reduce the risk of this issue to appear until a fix is being released. If you happen to find yourself in this situation, the best thing you can do is to downgrade to Android 4.4 KitKat until this problem is solved.
