Nexus 4, Nexus 5, Nexus 7, Nexus 10 New Paranoid Android 4.5 Beta 2 Update Guide
By Precious Silva | August 31, 2014 9:46 AM EST
Nexus users can now access the initial Paranoid Android 4.5 Beta 2. Supported devices include Nexus 4, Nexus 5, Nexus 7 and Nexus 10. The firmware has been released for a couple of weeks but this time it was different. The PA often puts out Beta builds weekly. While the Beta 3 was supposed to be released within this period, the team revealed that they will be releasing another Beta 2 build with additional minor fixes.
Sundar Pinchai, Google's senior vice president of Android, Chrome and Apps, speaks during his keynote address at the Google I/O developers conference in San Francisco, June 25, 2014
According to Android Geeks, the latest Paranoid Android 4.5 Beta 2 update offers a range of changes including fixed transparent status bar, fixed blank screen in recents and a number of themes engine fixes. Once users install the latest firmware then they should see accessing beyond Hover sends to hide swiftly. The feature expands too.
According to the PA team, they have also provided fixes for random wake up on 1+, proximity sensor including Oppo. Reports note that the Paranoid beta 4.5 Beta Builds have been targeting to offer Android L design experience on the mentioned devices. It is one way of experiencing the Android L aesthetics.
Update: In an update posted on the PA team's blog, the team discussed about the BETA 3 issues. To fix the issues, people can now access the BETA 4. According to the changelog of the BETA 4, people can find what the BETA 3 was intended to be. Other things to expect include:
-Fixed issue for wrong kernel under mako
-Fixed issue via Theme Engine themes
-Resolved flashlight or light bulb for hammerhead users
People who wish to see what the Android L and the update offers can download and install the Beta. Despite the Beta label, Android Geeks reported that there weren't any inconvenience note mentioning.
Disclaimer: Providers of the update cannot be held responsible for what happens to the device following update. Users can update at their own risk.
To contact the editor, e-mail: