This story was originally published and last updated .
Over the last week, a photo has been making the rounds at venues like Reddit and Twitter. It's an attractive mountain lake with the sun rising (or setting) through the dense clouds. Perfect for a phone's wallpaper, right? Not unless you like bootloops. Certain aspects of the image trigger an inescapable, repeating crash in Android's system UI, and most recent Android phones are likely susceptible, including Samsung phones and Google's Pixels. Thankfully, both Samsung and Google are aware of the issue and looking into a fix.
Following a recent update to the Zenfone 6, some owners have been reporting system stability problems including frequent crashes/restarts, network connectivity problems, and bootloops. According to a recent statement issued by an ASUS representative on the company's ZenTalk forums (spotted by PiunikaWeb), the issue is a hardware fault in affected devices which is triggered by the update.
Android Q Beta 4 came out earlier today, and though there don't seem to be as many new things as with prior Beta releases, it's nice to have notification swiping as God intended and the rotation lock button back. However, it's not all good news; some people are reporting issues with bootlooping when attempting to update to Q Beta 4, primarily those with Pixel 2 XLs.
Slow and delayed updates are nothing new for Android devices, but T-Mobile and Samsung seem to be having more issues than usual. Back in April, T-Mobile had to halt the Note 8's Oreo update for several weeks, but it turns out the Galaxy S9 and S9+ had some botched updates of their own. The carrier paused an update in April, and it hasn't restarted more than a month later.
If there's one thing sure to ruin your day, it's a crashing smartphone. Even worse if the bug proves so bad that your phone eventually insists you do a factory reset, losing data in the process. This is exactly the situation that has befallen a number of Nexus and Pixel owners in recent days, and it's all to do with an adaptive icon bug that was discovered by the developer of third-party Facebook wrapper called Swipe.
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.
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.
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.
The Nexus 6P lawsuit we previously reported on twice in April has been recently amended, and the venue of the suit seems to have changed to northern California. The latest filings have expanded the total number of actions in the suit from 10 to 23, with claimants hailing from 11 different states. It's still early days, and this more recent filing doesn't mean that the case has advanced, merely that the attorneys involved have decided to expand and tweak things after the initial filing. Those who are participating in the suit have a long way to go.
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.