The Inquirer-Home

Samsung Galaxy S3 handset catches fire

Samsung and Carphone Warehouse are investigating
Thu Jun 21 2012, 09:51
Samsung Galaxy S3 fire

IT'S NOT GOOD NEWS for Samsung today, as reports have surfaced that one of its flagship Galaxy S3 smartphones caught on fire.

The phone's owner, forum user dillo2k10, said his HSPA+ Samsung Galaxy S3 that he bought from UK retailer Carphone Warehouse caught alight while in an in-car holster - reminiscent of the Iphone catching fire incident in July 2010.

"So I driving along today with my Galaxy S3 in my car mount when suddenly a white flame sparks and a bang came out of the phone," he said. "I pulled in to look at my phone, the phone burned from the inside out. Burned through the plastic and melted my case to my phone. The phone kept working but without any signal."

Samsung Galaxy S3 fire

"The phone was destroyed and it slightly burned a piece of plastic on the inside of my car."

The phone has been sent back to Carphone Warehouse, which have sent the phone away to be investigated. Poor dillo2k10 wasn't even given a replacement phone however, which has left him disgruntled.

"And they are refusing to give me a replacement, they had to send it off. Probably nothing I can do, but Im really annoyed," he said.

In a statement to The INQUIRER, a Samsung spokesperson said it is aware of the case and is looking into it. They said, "Samsung is aware of this issue and will begin investigating as soon as we receive the specific product in question.

"Once the investigation is complete, we will be able to provide further details on the situation. We are committed to providing our customers with the safest products possible and are looking at this seriously."

While it was widely anticipated that the Samsung Galaxy S3 would set the smartphone market alight, we don't think anybody expected it to take that expectation so literally. µ

 

Share this:

blog comments powered by Disqus
Advertisement
Subscribe to INQ newsletters

Sign up for INQbot – a weekly roundup of the best from the INQ

Advertisement
INQ Poll

Coding challenges

Who’s responsible for software errors?