Saturday, July 1, 2017

One Class Action Lawsuit Against LG’s Bootloop Issue Has Been Compelled Into Arbitration

Bootloops on LG devices are as infamous as they are common, often being used in arguments against the merit of devices manufactured by LG. LG had admitted that the bootloops were hardware related on the G4 and had promised to repair the affected devices "under full warranty". But despite LG supposedly figuring out the issue, the same problem continued to plague other LG-made devices such as the Nexus 5X, LG V10 and LG V20.

With very little respite in sight from the OEM, consumers had to approach the Court for justice. A Class Action Lawsuit was filed against LG when LG continued to manufacture smartphones with the defects and did not follow through with a recall to fix and repair susceptible devices. The lawsuit even claimed that LG replaced bootlooping devices under warranty with devices that once again succumbed to bootloops.

Initially, this particular lawsuit was filed against LG over the LG G4 and the LG V10. Subsequently, the LG-made Nexus 5X, the LG G5 and the LG V20 were also added to the case.

The latest development on the case comes as a heavy blow to the affected consumers and to those who wished to see an end to the bootloops for once and for all. The California Central District Court has passed an order to compel arbitration in this case, thus dismissing the class action lawsuit. LG had filed for a motion to compel arbitration, and based on the facts of the case, the Court saw it fit to grant the motion and dismiss the lawsuit without prejudice (an "open door" to file the case again later).

The grant of the motion in LG's favor came through a smart legal technicality that LG incorporated in its sales strategy. AndroidPolice has uploaded a copy of the Order, which mentions that the Court has adopted the standard laid down in the [famous] case of Hill v. Gateway 2000, Inc. The Hill case basically lays down that additional terms can become part of the contract between parties even if they were not specifically spelled out at the time of contract, provided that the parties had an opportunity to inspect the terms and their acceptance of the additional terms can be assumed from their lack of refusal.

In LG's case, each of the purchased phones came in a box which contained documentation related to LG's Limited Warranty. The Limited Warranty contained a provision for arbitration which makes it binding upon the parties (LG and the purchaser) to resolve disputes through binding arbitration instead of in Court, unless the purchaser chooses to opt out. The ability to opt-out of this arbitration clause (a clause that prohibits class action lawsuits and jury trials) is time-limited, giving the purchaser the option to send LG an email or call a toll-free number within 30 days from the date of purchase.

Applying Hill's case to the carefully drafted Warranty Agreement, the additional terms of Limited Warranty become applicable and binding on the parties. This is irrespective of the purchasers even knowing about the existence of these additional terms prior to purchasing, nor is it affected by the simplistic human nature to ignore all documentations inside of our phone boxes. Since the agreement to refer to arbitration and waive off a civil lawsuit hinged on the explicit refusal to accept the clause, the purchasers were deemed to have accepted the arbitration clause when their 30-day period ended. Under the laws applicable in LG's case, silence did constitute assent in this context.

The state-specific law discussed above {in the Order} makes clear that each of the three states recognizes that shrinkwrap or "in-the-box" agreements, such as Defendants', can be accepted through silence or inaction. The agreement here, which could be found inside the box of the product, gave Plaintiffs 30 days to return the product or opt out of the arbitration clause. Plaintiffs chose to keep the phones without opting out. As a result, the Court agrees with Defendants that Plaintiffs have assented to the agreement found inside the box, including the arbitration clause.

AndroidPolice states that arbitration is not likely to result in as much relief or compensation for the plaintiffs as compared to the class action lawsuit that was existing. To an extent, we agree, as forcing arbitration in this matter breaks down the collective nature of a class action lawsuit, and acts in the advantage of the big corporation and to the detriment of smaller consumers. Every plaintiff now has to undergo arbitration procedure, making this a barrier for those seeking justice but not possessing the inclination to involve themselves in complex, expensive and time-consuming legal disputes.

But just because the case has been compelled towards arbitration does not mean that all hope is lost. The arbitrator in his review of the case and the evidence can impose a decision that comes out in the favor of the bootlooped parties. Also, since the case has been dismissed without prejudice, an option to file the case in court at a later time still exists.

If you are a US citizen, have been affected by the bootloop on the mentioned LG devices purchased by you through LG or its authorized retailers and would like to join the suit (the arbitration proceeding, in this case), you can contact the attorneys involved. XDA-Developers advises readers to use their own discretion when deciding on their participation.


Even though the LG bootloop class action lawsuit did not turn out favorably towards the consumers, it does teach us one important lesson. While unboxing your phone, installing software or entering into any sort of agreement in any other scenario, always look for the fine print, and read and understand its implications. The existence of a legal 'loophole' allowed lawyers to craft a way out of a big and ugly mess, and something like this could have been avoided if more purchasers knew how to opt out of such forced arbitration agreements. We recommend readers to take some time out and read through the Warranty Agreements on their recent purchases.

What are your thoughts on the outcome of LG's Bootloop lawsuit? Let us know in the comments below!

Source: AndroidPolice

 



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

XDA Begins Regular PC Hardware Coverage, Designed For Our Audience

At the tail end of 2015, I started writing for XDA-Developers — it wasn't a big jump given my involvement on the site for many years, but until then it was all on the forum side. Since then there have been a lot of changes, capped off with a new geographical location and work schedule. It's been challenging to get back on the path after that and a lot of work was done behind the scenes to keep that going. Thankfully it started to come together again in May with our review of AMD's Ryzen processors.

And at the end of that article, we asked: What did you think of that review? And how would you feel about more of this type of coverage? Here's a few of the responses:

Redditor (I have corrected a few spelling errors):

" Honestly, I was quite surprised to see that it was XDA of all outlets who first brought a broad comparison of the whole Ryzen lineup on Linux weighing cores and threads against price and performance. There were a couple of contenders I would have expected to be interested in compiling something like this. I am following XDA for it's android content and open software focus, but if articles like this one keeps popping up, I have one more reason to follow it."

Ryzen review comments:

" This maybe a wise direction to look at. Custom pc building will be around long after devices are locked down."

" Do more of these articles. This is where performance starts for our phones and new hardware coverage, desktop or otherwise, is welcomed on a site all about getting the most from your hardware."

The one that strikes me the most is a comment on Reddit yesterday after we released news about the screen inversion on the OnePlus 5, given it came out of nowhere.

"Yeah, please get into computer hardware too"

What we didn't mention was that at the same time readers were offering feedback, so were members of XDA's own staff. And what did we learn over that time? It says we've tapped something we probably should have done a while ago.


For all of the discussion about how we focus on developers,  why are we not focusing on the tools they use to produce the software that we love so much? Android isn't programmed on smartphones, nor are the apps that we all love to install and use. Many of our developers are college students or seasoned professionals. Where do they turn to help get advice on how to better tune their systems or, when it's time to look for a new purchase or upgrade, what to look for?

Thanks to you, the readers, we have the attention of many folks globally — honestly higher than most tech outlets, and our audience has grown tremendously in just a few years. We still want to keep the mentality of "By developers, for developers" and mobile content that we're known for. In fact, readers have put an exclamation point on that over the past few days. But that doesn't mean we should be tying our hands behind our back, and limiting what we cover just because we haven't done it before. And what if we could do a lot of potential good by covering things where there is very little attention right now?

After two months of work largely behind the scenes, it's time to finally say it. XDA will start covering PC hardware on a regular basis. This will have a lot of obvious questions. So let's get into discussing this a bit further and help set some mutual expectations on the new coverage.


What We'll Cover

News Coverage & Analysis: Articles of this nature will not be as constant as you may see on other sites. The reason for this at the moment is simple: Our readers don't just read XDA. We're not the only site out on the Internet that can offer this either. If news seems relevant enough to our readers or we believe we can add insight or analysis that may be missing from the general tech site coverage, you'll likely see us cover that. We remain, above all else, a site designed for mobile technology. We're also dedicated to supporting developers at all levels joining the open source scene.

Product Analysis & Reviews: If we're going to do this right, this means we do this, and that we strive for the same level of detail and insight as the rest of our content. The goal has already been agreed upon – major hardware releases will be covered. It may take a bit to get caught up – but here's a few of the in-depth topics we will be covering in the month of July.

  • A review of Intel's Kaby Lake i7-7700K. It was one of the missing pieces to really consider during the Ryzen review. And our thanks to the folks at Intel who are willing to work with us on this new journey. And for those curious, we intend to review both Core X and Threadripper fairly soon.
  • A follow-up to the problems we noticed in Gigabyte's AM4 motherboards and how they stand now. We'll also take a look at one of their Intel motherboards as a part of this.
  • At the end of the month, news from SIGGRAPH. At the moment we know of at least one big release during this time frame: AMD's RX Vega. We expect there will be more news there relevant to our audience.

Reviews will largely focus on the Linux operating system and continue to have a developer focus in them. We decided to keep our reviews on Linux for two primary reasons. First up was the lack of dedicated Linux coverage for new PC hardware in the global market. We hope that this will help introduce corroboration to findings of other Linux reviews, of which there are not many beyond Phoronix. The other half is one that I have heard several times and experienced on my own: A lack of information on how to get most PC hardware working on the day of release. As part of our reviews we will be including notes on any issues with using hardware as well as any solutions and/or workarounds available.

So what about Windows? Given the many choices of alternate sites to offer this coverage it seems that, in many cases, it does less for our readers to offer a review of PC hardware on Windows. The immediate exception to this rule will be the upcoming ARM on Windows. We know and love the Snapdragon SoC quite well here and so it makes every sense that we would cover devices powered by it, independent of the platform on which they run.


There's obviously a lot more to be said here. Much of it still has some fine details left to straighten out before we announce further information. But we'll continue to share relevant news on the topic as this new venture develops. We again thank our readers for the (very) vocal support on these efforts and hope you will continue to offer that support as we continue our coverage!



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

Sailfish OS Community Port Available for the Xiaomi Redmi Note 4

XDA Senior Member piggZ has released a community port of Sailfish OS for the Xiaomi Redmi Note 4. The build is currently in alpha state so there are quite a few things either missing or broken at the moment.

The port is based on Lineage OS 13.1 and requires you already have an unlocked bootloader and custom recovery installed. The list of things that are currently working fine include calls, data, Wi-Fi, GPS, and Bluetooth. If you're looking to try something new on your Redmi Note 4, give it a shot. Be sure to check out all the instructions before you attempt to install it on your device.

Check out Sailfish OS for the Xiaomi Redmi Note 4



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

Report: Samsung to use Solid-State Batteries for its Galaxy Phones within Two Years

Samsung will be able to produce solid-state batteries that are safe enough for use in smartphones within one to two years, one of the company's executives said. Solid-state batteries are far more durable and provide better longevity than standard Lithium-Ion batteries.

One of the Samsung's SDI executives told The Korean Herald:

"Our technological level to produce a solid-state battery for smartphones will be mature enough in one to two years. However, it depends on Samsung Electronics whether it will be used for phones. (…) As far as I know, the level of battery technology of our rival firm (LG Chem) is also similar to us."

Solid-state batteries do not use liquid to conduct ions, which is how Li-ion batteries operate. Li-ion batteries can ignite and even explode when liquid inside the battery contacts air or water outside. On the other hand, the solid electrolytes found within solid-state batteries are much less likely to ignite. If you'll recall, Samsung was forced to discontinue the Galaxy Note 7 after a series of reports on its Li-ion battery exploding.

"Solid-state batteries are a realistic alternative to lithium-ion batteries in solving the chronic safety issue as the development has been relatively faster than other next-generation batteries over the last 10 years."

Choi Jung-deok, Analyst at LG Economic Research Institute

Solid-state batteries can be used in smartphones and electric vehicles. While we should see the first smartphones with this battery type within the next two years, vehicles will need more safety testing. The predicted premiere of a vehicle with a solid-state battery is expected to occur by around 2025.


Source: The Korean Herald



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

LineageOS 14.1 is now available for the Samsung Galaxy J7 (SM-J700P)

While developing for Samsung devices has proven to be a tough task over the years, there have still been a handful of developers who have been able to accomplish a great feat by porting functioning AOSP-based builds. XDA Recognised Developer minz1 is one such developer who recently released LineageOS 14.1 based on Android 7.1 Nougat for the Samsung Galaxy J7.


Installation

For those interested in flashing the custom ROM, here's a quick run-down of the installation steps:

  1. First off, make sure you are running the TWRP build contained at this link. It will be continually updated with support for this ROM's features.
  2. Secondly, ensure you're on the "J700PVPS1AQD1" update for the Galaxy J7. If, by any chance, you are not on said update, you should flash the stock ROM (with the help of Odin) and perform a system update.
  3. After booting into TWRP, perform a factory reset.
  4. Now flash the custom ROM and the latest Google Apps package.
  5. Reboot. The first boot could take anywhere between 5-10 minutes.

Future updates to the ROM can be found on the forum thread linked above. Keep an eye out on the thread for any news related to the ROM.



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

Jolla to Begin Testing Sailfish OS on the Sony Xperia X this Month

During Mobile World Congress 2017, Jolla announced a new collaboration with the Sony Open Devices program to bring Sailfish OS for Sony Xperia smartphones. Now, the company has just released a new post to inform us that Sailfish OS would be available for the first Xperia devices starting in this month.

The first Sony device to officially support Sailfish OS will be the Sony Xperia X. Initially, only a small number of users will get Sailfish OS 2.1.2. Jolla plans to use its Cbeta, a small community development group, for alpha and beta testing. The team consists of developers, translators, and attendees of various community events. The first few members of the Cbeta group are expected to get resources from Jolla sometime this month.

The Finnish company is not in a hurry, though, and plans to test the new OS on the Xperia X thoroughly before the first public release. One of the biggest challenges is retaining compatibility with Android apps. Also, given the fact that the Xperia X is the first 64-bit ARM device to run Sailfish OS, some flaws need to be fixed. Jolla is also working on an easy and more convenient way of installing any future updates. The company does not want to force its users to use a custom recovery install updates.

While the Sony Open Device program is huge and supports many devices, Jolla will only be focusing on bringing Sailfish OS to the Xperia X, at least initially. The company completed its work on the Xperia X single SIM model and will consider how to proceed with other Sony devices.

Finally, Jolla has also addressed the idea of offering Sailfish OS for Sony Xperia software as a type of compensation alternative in the Jolla Tablet refund program. As a reminder, over 20,000 contributors backed the highly anticipated device in late 2014. Despite collecting $2.5 million, Jolla faced severe financial problems and had to cease production. The company is still recovering from the situation and is evaluating the possibility of offering Sailfish OS as a form of compensation.


Source: Jolla



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

You Can Buy the Moto E4 from Amazon, Ting, and Republic Wireless for as Little as $99

There's no doubt that high-end smartphones like the Samsung Galaxy S8, LG G6, and HTC U11 are great to use, but for a lot of people, shelling out over $600+ is out of the question when it comes to these premium gadgets. The mid-range smartphone market has blossomed as flagships have steadily risen in price over the years, but even at $200-$500 a pop, devices like the OnePlus 5, ZTE Axon 7, and the Moto G5 Plus are still too rich for some people's blood.

Motorola and Lenovo announced the Moto E4 and E4 Plus this past month, with the phones costing $129 and $179 respectively. The E4 made its debut on Verizon back on June 22nd for $70 with a service plan through the carrier, and the phone is now branching out to a few other carriers/retailers.

If you want to buy the Moto E4 outright and not through any carrier, Amazon is now selling the phone as well. You'll need to be an Amazon Prime subscriber as this is a Prime Exclusive version of the handset (meaning that the lock screen features advertisements from Amazon), but if you are, you'll only pay $99 for the phone. While that's still technically more than what Verizon is charging, you aren't forced to buy a service plan and can use the Moto E4 on all 4 major U.S. carriers.

If you aren't a Prime subscriber, you can also now buy the E4 through Ting and Republic Wireless. Ting is selling the E4 at its normal price of $129, but Republic Wireless will let you buy the phone unlocked at the same price as Amazon's Prime Exclusive model but without any of the advertisements on the screen. Although, you will need to purchase a no-contract plan if you choose to go the Republic Wireless route, but you could always just get one month's worth of the cheapest plan ($15/month), cancel it, and then use the phone on whatever carrier you choose.

As a quick refresher, the Moto E4 has a 5-inch 720p IPS display, Snapdragon 425 SoC with 2GBs RAM and 16GBs of internal storage expandable via a microSD card. Add this together with a 2,800 mAh removable battery, water-repellent nano-coating, a front-facing fingerprint scanner, and Android 7.1 Nougat – the E4 packs a lot of punch no matter if you pay $99 or $129 for it.


Buy the Moto E4 on Amazon Buy the Moto E4 on Ting Buy the Moto E4 on Republic Wireless



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