Skip to main content
  1. Home
  2. Phones
  3. Android
  4. Mobile
  5. News

Samsung says it’s now investigating reports of new Galaxy Note 7 phones overheating

Add as a preferred source on Google

Just when we started to think Samsung was finally getting on top of its exploding-Note-7 debacle, we started to hear that some of the replacement phones were also overheating, with at least one owner claiming his new Note 7 device caught fire.

In a number of cases, the replacement handset was actually “too hot to place next to the ear during a phone call,” according to the Wall Street Journal.

Recommended Videos

The fresh complaints have been coming from a number of users in the U.S., as well as Samsung’s home market of South Korea, and pile even more pressure on the tech giant as it fights to limit damage to its reputation.

Samsung is clearly, and wisely, taking the reports seriously, announcing on Wednesday that it’s now investigating the complaints.

In a statement to the Journal, the company said that “in normal conditions, all smartphones may experience temperature fluctuations.” However, a temperature so hot that you can’t hold the device to your ear clearly falls outside of what can fairly be described as “normal,” and Samsung is now endeavoring to get to the bottom of it.

The Galaxy Note 7 launched to rave reviews in August, but some users soon started noticing their phone overheating, with at least 35 of the devices suddenly bursting into flames. The issue was put down to faulty batteries, prompting Samsung to issue a global recall of around 2.5 million units, with more than a million of those belonging to U.S. customers.

Seoul-based Samsung revealed last week that around half a million American owners of the Note 7 had exchanged their handset, with 90 percent opting for a new Note 7 rather than another smartphone.

Recent reports of the replacement handsets overheating come as the company grapples with another serious issue, this one concerning some of its top-loading washing machines. The United States Consumer Product Safety Commission warned this week that some models of the company’s washing machines could break up during a spin cycle, sending nuts, bolts, plastic – and water – all over the place.

Trevor Mogg
Contributing Editor
Not so many moons ago, Trevor moved from one tea-loving island nation that drives on the left (Britain) to another (Japan)…
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more