Owners of Nexus 6P misleading from the battery failure with 7.0 Nougat – ITbukva (press release)

Details

Published 01.11.2016 08:14

Author: Super Roman

Hits: 94

With the development of smartphones there are certain aspects of the device often get better for a long time. Some flat panels can sometimes become boring, the performance is not always as smooth as it was before, but the batteries seem better. Even after owning the phone for only a year or a few months, it is not uncommon to notice that your battery performance dropped quite a bit compared to when you first took the phone out of the box reports ITbukva.com.

Some owners of Nexus 6P – phone, which was released September 29, 2015 – reported visible low battery on their phones. However, the problem with batteries, which they report is much more serious and severe than the normal wear and tear.

In a video on YouTube from user TheRedyTedy, he demonstrated that his specific Nexus 6P has a tendency to just shut off at random times for no apparent reason. TheRedyTedy repeats the question in the video, just took a few photos using the Google Camera application and the phone immediately sat down soon after. When the phone is turned off, TheRedyTedy shows that pressing the power button once and holding it has no effect on the phone due to having no choice but to 6P plug in the charger, it waits until the charging indicator POPs up on the screen, and then includes it in the same way. The video says that Nexus 6P works on non-beta 7.0 Android Nougat, and he has already passed through the system reset.

TheRedyTedy shared this video with the YouTube sub-forum dedicated to Android, on the website reddit on Sunday, October 30, and since then it has caused a lot of comments from other users reporting similar problems with their 6P. Looking at the comments, some users reported that the system reset worked in their case, while others say that Android OS 7.1.1 has returned all into place. One user reported that 7.1.1 was actually the cause of the battery problems, so at the moment does not seem to be any specific solution to this problem.

One user reports that they have contacted Google about this problem, received a refund of the goods, and that the replacement is now working fine. If you have a 6P with this issue, try to reset it to factory settings or roll back to 7.1.1 can work, but it seems that perhaps you have no other choice but to contact Google for a replacement.

Like the news? Share it

Posted