One of my Google minis stops on the middle of a sentence

[KAV]

I have several Google minis. One of them has stopped in the middle of a sentence while answering a question. It has a good connection to my Google router. What can I do to fix it?

[Muddi · Accepted solution]

Hey folks,

My apologies for the lack of updates here. I understand this issue has been happening for quite some time, and has been a rather frustrating experience. The team is looking into this issue at hand and I haven't received any updates as yet. I'll continue checking in with the team and share any updates I receive.

We just need a little help so we can move forward with the investigation. Please send a fresh feedback using the keywords: "GHT3 Cutting out in the Middle of a Sentence." Make sure to replicate the issue first before sending feedback so we can check the crash logs. For instructions on how to send feedback, you can visit here.

Thank you for your patience while our team works through this.

Cheers,

Muddi

[Muddi · Accepted solution]

Hey folks,

My apologies for the lack of updates here. The team is still investigating this issue and I haven't received any updates as yet. I'll continue checking in with the team and share any updates I receive.

I understand this issue has been happening for quite some time and has been a rather frustrating experience. Thank you for your patience while our team works through this. 

Cheers,

Muddi

[Muddi · Accepted solution]

Hey folks,

I'm checking in on this thread since it's been a while since it was last updated. There's no new news to share at this time, but I'll continue monitoring the thread and updating it as I know more. 

Cheers,

Muddi

[wajobo8]

Hi. Originally I did a lot of the steps mentioned here - resetting to factory and rebooting. Then I did the steps below and my mini's have been working since. I think there were two key problems, old info stuck somewhere and 5G. They are now working properly with my Pixel phone and tablet. I still think it is an issue that Google needs to address. But, this work around was effective for now. I also think it was important to reset the router ID to ensure I was actually on a new setup and 2G. 

What I did:

Okay. So I seem to have made some progress. I gave it one last try before I permanently donated the mini speakers to the trash can. The short of it is - it seems to be related to 5G and potentially the last update as far as it was coincidentally about that time it quit working properly.

Here is what I did. I disabled Google Assistant on all devices. I deleted Google Home app on all devices. I changed my router passwords and ID so I could be sure I wasn't pulling any old info. I renamed them to 2G and 5G so they were easily differentiated.

I rebooted/reset everything. I factory reset the mini speakers.

I avoided using my Pixel phone to set things up to eliminate it from the problem. I have a Lenovo phablet and I downloaded Google Home - opened the app and went through the steps of making rooms and finding devices. I SET UP EVERYTHING ON 2G. 

And it worked for me. The response is no longer truncated. I did not go back and try to replicate the problem only using 5G - some other day when I have nothing better to do I might try it. Another reason for not using my phone to set up Home is because it always seems to default to 5G even though I purposefully switch it. So my swag is that it is somehow related to 5G and update.

[Fladge]

The problem is not only still happening with all of my devices, but it now does it when it asks me if I want more context about something and I answer "yes".
The device's more context response is inaudible every single time for weeks now.

Irritating is an understatement.

Every once in a while an alleged google employee comes on here and pretends to be connected to those at google working on a solution.
Soon after they either mark their own post as the solution or mark some well-meaning contributor's post as the solution.  It's not solved.  It likely hasn't even been investigated based on the weak company information posted here.

They write well --- it staves off complaints for a while, then the "community specialists" swoop back in and mark it as solved.
Any responses here by seemingly connected people are obviously a housekeeping maneuver to close out open threads.

There has been no acknowledgement by Google of the problem even after all this time.

If someone at Google, "the team", engineers, whoever - is on it, (which is doubtful) they should be fired for ineptitude for not keeping their customers informed at a minimum.  

The fact that the lack of a solution can be counted in years now is incomprehensible.  

[StaceyJill]

I just opened a new thread about this turning off after we say yes to more context to a question.  I figured it was happening to others. 

[obxa]

Agreed.   And well said. I’m tired of the troubleshooting.    I gave up thinking they’d ever fix the  first problem a long time ago.  This is the equivalent of a piece of paper with “turn over “written on both sides.    I started the transition to a Bezos  Box a few weeks ago after this latest glitch

[Techie1970]

Turn OFF motion detection.  Fixes the problem.

[StaceyJill]

Did you read this thread?

This is happening not only with the new generation (nest) but the FIRST (2017) generation of speakers. Minis and Talls. There is NO "motion off" In the first generation.

[StaceyJill]

P.S.

And we did replace our 2017 speakers with 2021 devices.  We don't have nest hub.

[imslickk]

Hey everyone, I appreciate the updates. I found out what was causing it on my end. It was likely proxy filter related. I created a custom rule for that device to use packet filters for traffic and have not had the issue since. I appreciate all the advice.

[StaceyJill]

I would guess whatever you did, didn't take care of anything. The "stopping mid sentence" and "not answering us when we are asked if we want more information and say yes" has gotten so much better, I believe Google found a fix.