The last generation of Nexuses (Nexus? Nexsi?) were unfortunately plagued with hardware problems. The Nexus 6P suffered from early shutdowns due to a faulty battery sensors, and the 5X had the famous bootloop bug (which my own 5X eventually fell victim to). The 6P suffered from bootloops as well, to an extent, but now there's a possible fix for the problem on both phones. Read More
Representatives from Girard Gibbs LLP, the firm previously handling one of the LG bootloop lawsuits, contacted us late yesterday with news about the case. On June 29th the court gave an order granting the defendant's motion to compel arbitration, dismissing the lawsuit. That means that right now the suit has been forced into arbitration. Read More
Back in March, we learned that Google may be working on a third device for 2017, called 'Taimen' (Google traditionally names products after fish). This third model would be bigger than the next Pixel and Pixel XL, codenamed 'Walleye' and 'Muskie' respectively. It's not known for sure that Taimen will be a larger Pixel phone, just that it will be larger in size than Walleye and Muskie.
Earlier today, we reported that Muskie has likely been cancelled, leaving Walleye and Taimen the only phones Google will reveal this year. Now it seems that Taimen may be manufactured by LG. Read More
Chimicles & Tikellis LLP, the law firm which was previously involved in a suit against LG for the Nexus 5X bootlooping problem, has filed a notice for voluntary dismissal of their case as of May 4th. Note that this is a different suit than the one by Girard Gibbs LLP that we reported on back in April, which (to our knowledge) is still ongoing. Read More
The Android hardware space is fast beginning to look like a watered down episode of Suits. Following on from news earlier in the week that LG is facing a bootloop lawsuit regarding several of its phones, Huawei's Nexus 6P could be responsible for Google encountering a similar inconvenience. As well as being accused of the same bootloop problem that has blighted LG devices, there are reports from consumers that the Nexus 6P has a premature battery shutdown problem. Read More
It looks like LG can't catch a break. Hot on the heels of our news about the G4 and V10, it looks like the attorneys in that suit may be doing research into other potentially affected devices, including the G5, V20, and Nexus 5X. Read More
LG's bootloop problems have become the butt of the joke online over the past few months. While Samsung was busy cooling down the fire of its Note7 fiasco, LG was getting heat over its freezing LG G4 and V10, among other devices (like the Nexus 5 and 5X). Many reports were surfacing of these phones getting stuck in a bootloop vicious circle, turning on and off, not properly booting, and leaving the owners without any recourse but to ask for a replacement unit... if they were still under warranty.
Now these owners are seeking their day in court thanks to a new class-action lawsuit filed to the California federal court. Read More
The most recent over-the-air update for the Nexus 9, the one that totally wasn't what you were actually waiting for, has apparently bricked the device for some owners. A couple folks affected by this 5.0.2 issue have taken to Google's product forums to ask what gives.
The person who opened this thread was told to perform a factory reset in recovery mode (as well as the bootloader, which has a separate factory reset option). It didn't fix things. Nor did it work for our very own Cameron Summerson, who went through this headache this morning. He was able to fix his Nexus 9 only after flashing the factory image manually. Read More
The OnePlus One has had its share of bugs, but there has been one issue that effectively breaks the phone without the owner being even accidentally at fault. One minute you're swiping through the app drawer looking at the best way to kill time for a couple of minutes, the next you're hit with a spontaneous reboot and staring at a phone that boot loops indefinitely, leaving you with a bricked device.
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. Read More