LightBlog

mercredi 28 septembre 2016

Replaced Galaxy Note 7 Reportedly Catches Fire

Samsung just hasn’t had much luck with the Galaxy Note 7 this year, and this latest report suggests that things might not be changing anytime soon. Samsung has been dealing with their voluntary replacement program for the device since the start of this month. The South Korean conglomerate was hoping this program was all that they needed to do, but they were forced into doing an official recall just a couple of weeks ago.

It was estimated that this Galaxy Note 7 battery defect would cost the company upwards of $1 billion in parts and labor alone. This isn’t even factoring in the negative perception the public has about the device after the scratch test, and even after the multiple fires that were started from the Note 7. A device that was called the best smartphone available today by many Android publications, and one that our own Daniel Marchena called a remarkable phone for life.

So Samsung has been replacing and refunding defective Galaxy Note 7 devices for a couple of weeks now. Just yesterday we talked about how replaced Galaxy Note 7 units were continuing to have battery issues. At the time, it was reported that some units were being charged while they were plugged in, while others were having overheating issues when the device was plugged in. Still, at that time there weren’t any reports of replaced units catching fire or exploding. . .until now.

Hui Renjie is a 25-year-old from China who received a replacement Galaxy Note 7 Sunday afternoon that was delivered to him from the JD.com commerce website. Less than 24 hours after receiving the unit, the new Galaxy Note 7 reportedly caught fire and caused minor burns on a couple of his fingers while also burning his MacBook. The man says he has refused an additional replacement and simply does not trust the company anymore.

Samsung has received the defective unit and is currently examining the device to find out what happened.

Source: Bloomberg



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

Aucun commentaire:

Enregistrer un commentaire