cancel
Showing results for 
Search instead for 
Did you mean: 
Replies are disabled for this topic. Start a new one or visit our Help Center.

Google Nest Mini charcoal Gen 2: frequent popping noise (no solution)

Metoo132323
Community Member

Mods: please don't merge this thread with the one below. I want you all to look into this. 

The previous topic has been marked as "Answered" or "Solved" by the original poster despite the issue not being resolved as shown in this thread: Strange popping sound in my nest mini.

I like others have tried all the known workarounds and fixes but none work. I have done my part and sent "feedback" .

The issue only plagues my Gen 2 Mini not my first gen version. It doesn't matter if I'm listening to anything such as Spotify or YT Music, the popping happens randomly whilst the Mini is silent. I can't keep this Mini on at night because it awakens us.

Can we have the mods lean on Google tech support to address this major issue, once and for all?

@marcolopes 

@Hmm_8888 

@MaunaKeaMama 
@seanwoodward33 

 

15 REPLIES 15

DirkGG
Community Member

I'm having the same issues with my mini and audio. Can't return them, but I did switch to sonos... 

Yorkshireguy
Community Member

Strange popping noises when streaming music . On YouTube music , radio player, tunelin, global player etc . Getting very annoying, submitted feedback but nothing gets done . Only on the nest mini gen 2 . 

 

 

Dickie
Community Member

Experiencing the same issues.

Sick of giving feedback.

Sick of Google not caring. 

Doubt this thread won’t get merged….

RobinTurner
Community Member

Similar issue, makes my speaker sound like a popcorn machine. Switching off ultrasonic does nothing.

Can we please get an update from the team? My worry is that the radio silence points to a hardware issue. If that's the case there needs to be a recall.

Sometimes "popcorn machine" is the real way to define this HUGE problem!

marcolopes
Community Member

marcolopes
Community Member

Just a NOTE to clarify that the thread title might be misleading, because ALL GEN2 devices POP (not only the "Charcoal")

Gen1 = No problems (so far)

Gen2 = POPPING problem

Gen2 has several COLORS... (Charcoal, Chalk, Sky, and Coral) They all pop!

You're right! I have a coral and a charcoal, and they're both popping. I hadn't noticed it when I only had the coral one first, until I bought the charcoal one then differently it became obvious. Both are gen 2

I can confirm. The issue only plagues Gen 2. 

Lauras89
Community Member

Google don't care, they're still selling these devices knowing there's a software issue.

Got an echo dot for Christmas. That's the problem solved for me...  Fed up of Google ignoring the problem and saying the same thing over and over again. 

Well, I contacted several major AUDIO publications and internet blogs so they can be aware of this, and hopefully help with the issue (at least, publish some article about it) because it's NOT ACCEPTABLE that an AUDIO DEVICE like this is plagued with this annoying problem for such a long time (at least 3 years!)

Also, Spotify is (at least now) aware of this (because it's not good for anyone paying for a Spotify subscription)

JelleGo
Community Member

Same issues here!

popping quite a lot. 

buttr_toes
Community Member

Same issue for months and no sign of a fix from Google. We're talking about a bug that affects the audio output of the device, which is basically its main feature. How can that take months to fix?

Metoo132323
Community Member

What's even more troubling is finding current threads or topics on this issue. The board layout is intentionally designed not to display threads and comments in a NON-logical forum order. In part, I suspect this may be why this issue isn't getting the traction it deserves. 

Anyway, at least @marcolopes got a star from Google for his posts 😉

(sorry for the late response... i was "momentarily moderated / banned!)

Well, that was one of the first things i did when i started using this forum... configure it to display messages by DATE (the default configuration is utterly confusing and i could not locate any of the replies, they were "buried" within the sub-threads)