LightBlog

dimanche 16 avril 2017

Google Facing Potential Lawsuit Over Nexus 6P Early Shutdown and Bootloop Issues

After LG was taken to court over the infamous bootloop issue on its devices like the LG G4, LG G5, Nexus 5X, LG V10 and LG V20, it seems Google may be next in line to face the court’s gavel.

A law firm in the US, Chimicles & Tikellis LLP (C&T), is investigating a potential class action lawsuit against Google. This lawsuit relates to reports of early shut off as well as the bootlooping issues present in the Nexus 6P.

The shut off issue in the Nexus 6P pertains to the device powering down randomly despite the battery showing anywhere between 10-60% of charge left. The issue is primarily associated with Android 7.0 on the device, but the firm claims that even those users who have downgraded to Android 6.0 Marshmallow continue facing the issue. The problem has its own entry in Google’s issue tracker, but the issue bears the ‘low priority’ tag with ‘no indication of an incoming fix’. Customers who approached Huawei for a fix were turned away empty handed as Huawei shifted the blame onto Google’s software instead of its own hardware.

The bootlooping issue is the classic case of bootloop that we see on LG’s devices, but this is on the Huawei-made Google Nexus 6P. Once the phone randomly goes into bootloop, there is no way to fix the issue as none of the software fixes like wiping data or reflashing the system work. On this issue, Google shifts the issue on Huawei, but Huawei passes the buck back by saying it is a software issue. Customers are left running pillar to post with no solution in sight.

The law firm is inviting users with the issues to contact them through the form on their website. We suggest exercising your own discretion on moving ahead with participation in the lawsuit.

What are your thoughts on this issue? Where do you think the issue lies, and which OEM should take responsibility for it? Let us know in the comments below!

Source: Chimicles & Tikellis



from xda-developers http://ift.tt/2oEaZml
via IFTTT

Aucun commentaire:

Enregistrer un commentaire