Hacker News new | ask | show | jobs
by cosarara97 3526 days ago
I expected the article to say what made the phones catch fire.
2 comments

This is why I check the comments first. Thank you.
Saved us all a click. In the end doesn't even matter because I can't read the article anyway. It's behind a sign-in wall.
Use the "web" link to avoid the WSJ paywall.
That's getting old. I don't use the web link anymore either.
Why is it getting old? Still working for me at least.
Most posts, I'll open the article and comments. Read the article, then the comments. For WSJ posts, I'll load the comments, then decide if I want to bother with the Google trick. If I'm at work, I'll probably skip the whole post, because even if I'm interested in the topic, the Google trick doesn't work there.

They're the only place I see regularly where I have to do some workaround to view the content. They clearly have the intention of finding paying users, and I have no interest in paying. Using work-arounds to bypass that brings it more starkly to mind, with a little twinge of almost-guilt each time. It's easier to just skip the story, unless it's something extraordinarily interesting.

Clicking the link, then backpedaling to click the 'web' link. It works but it's not generally worth it.
Defective battery according to CNet: https://www.cnet.com/news/why-is-samsung-galaxy-note-7-explo...

Even replacement phones caught fire, they blamed the batteries.

Even this article is inconclusive... There has been no definitive cause.

My initial presumption was shoddy batteries+ quick charge 3.0 extra fast charging + hot Qualcomm 820 just to add.

It was first Samsung phone to use quick charge 3.0. If there was a battery defect, rapid charging didn't help.

This is what I'm wondering. Did they fail to adequately test the quick charge feature or do they have a supply chain issue? The Nokia phone explosions were caused by Nokia accidentally buying counterfeit batteries because they sold more units that they had anticipated. A startup I worked for back then was created to solve that particular problem (Verical).
No sh&t, battery? Who would have thought? I assumed it was CPU heated to sillicon's ignition temperature.