Galaxy Buds Pro and Buds 2 cause ear infections!

If you are looking for headphones in the market, it is undoubtedly an important piece of information. This is because the internet woke up to the news that Samsung’s Galaxy Buds Pro and Buds 2 could cause ear infections. Plus, they’re two of the best headphones out there. But what is causing this problem? And why these models and not others? There can be an answer.

Galaxy Buds Pro and Buds 2 cause ear infections!

Information provided by the Android Central website shows that an alarming number of users have suffered from ear infections after using the Samsung Galaxy Buds Pro and Galaxy Buds 2, returning the money for the headsets to users and, in some cases, even paying medical bills .

Infections with Galaxy Buds Pro

Infections with Galaxy Buds Pro

At this point it is not known what is causing the infections. It is said that they could be related to the new building materials. The Android Central site says the old models are no problem and in fact this is limited to new headphones. All of this is ultimately because the Galaxy Buds Pro’s charging contacts contain nickel which causes skin irritation in some people. In addition, Samsung used a new material called acrylate, which could also be one of the culprits.

Given that Samsung is offering some returns, it can be assumed that they are aware of the situation. However, since there is no official position yet, all of these models are still on sale.

Infections with Galaxy Buds Pro

Obviously, if you look at the dimensions, some people are already thinking about filing a lawsuit against Samsung. Because a supposed defect leads to allergic reactions such as itching, burning, redness and even fluid from the ear.

If you are having problems with Galaxy Buds Pro or Galaxy Buds 2, you can visit Samsung Community Forums and see the solutions offered.

It’s not the first time that we’ve had problems with Samsung’s TWS headsets. Earlier this year it was said that some Galaxy Buds Pro would not turn on after a few days of inactivity. However, this has been fixed.

Leave a Comment