At the start of this month, a minor software update was available for the Google Nexus 5 users with version number “MOB30P”. In addition to bringing some security improvements, it also messes up with the Nexus 5’s volume control. Users cannot adjust the volume control during phone calls which have become quite an issue. Most of the users consider such minor updates to be painless. Google has built this update to secure its devices. Every month, new security patches are available for an update which causes no problems whatsoever. Nexus 5’s Andriod 6.0.1 update in early July has created a bug.

Nexus 5 Volume Control Bug Fixed in an Upcoming Update

Talking about this recent update earlier this month, it contains security patches for Nexus 5, Nexus 9 and the Nexus Player. Google had to bring this update because Samsung and OnePlus 3 may have become faster than their devices. Nexus 5 is already running the latest Marshmallow OS. It takes 40 minutes to install the latest software on Nexus 5. The size of Android Marshmallow for the Nexus 5 is 400MB so having at least 1GB free space is recommended. The new Marshmallow update on Nexus has lots of improvements. Nexus 5 is going to be three years old and it is still working great with new OS. Battery improvement is the best feature that every Nexus 5 users has applauded.

Nexus 5 Volume Control Bug Fixed


Another issue users are facing is that they cannot move the volume slider down to the second lowest side of the phone screen. It is quite annoying for the users who travel often. Continous echo sound is heard during calls. Many Nexus 5 users have registered complaints about this bug on the Google community manager. Google must take this seriously and release the latest update to remove that bug.

READ  New ASUS G Series Notebooks with 'Pascal' GPUs Teased
You may like: Huawei Maimang 5 Now Available for Sale

You can see few reports on Google’s Official forum which show that latest update is on its way. It won’t take a long. The Nexus 5 volume control bug is going to be fixed in the upcoming update.