Allegedly false "exploding Note 7" report causes Samsung to spend extra cash on 3rd party tests
So, the exploding Galaxy Note 7 saga is nearing its end, as the replacement program is in full effect, and Sammy is even gearing up to re-launch the phone across all markets in October. Now, in comes the next wave — the uncertainty and fear over whether the new Notes are as safe as advertised. And make no mistake — the company is probably more concerned over this than owners of the phablet themselves, as Samsung's reputation will probably not be able to withstand another hit from the combustion saga.
So, naturally, the company was startled when a report from South Korea said that one of the exchanged units has caught on fire. According to the user, the phone was plugged in to charge overnight. After unplugging it in the morning, the Note 7 started smoking and melting. The owner's husband took a short video of the burning phablet and even provided a photo of the box, showing the black square near the IMEI, which should mean that the unit is of the revised, "safe" batch.
Samsung reacted by taking the phone and sending it out to the South Korean branch of SGS — a multinational testing and certification company — for independent tests. SGS performed an X-Ray and computerized tomography (CT) scan and concluded that the combustion was not caused by the battery. According to the SGS report, the phone was damaged by a physical strike so strong that it pierced through the back of the case that the device was in.
source: Joins (Translate) via Android Headlines
Black square on the box shows the flaming Note 7 was a revised unit
Interestingly enough, Samsung had to request the device be handed to it for testing twice before the user finally obliged. In the meantime, the online community in South Korea was passing on the news that the new Notes might not be as safe as promised. After the SGS tests were concluded, Sammy came out with an official stance, revealing the details around the incident, and reiterating that the Note 7s are perfectly fine to use.
source: Joins (Translate) via Android Headlines
Things that are NOT allowed: