9to5Google reports that Assistant stops recognizing commands after it responds to the user’s query. In its original form, the feature keeps the microphone on for around 10 seconds for follow-up commands, but that does not seem to be the case.
Measures like rebooting or toggling the feature on/off won’t fix the issue
This means that users will have to either tap the microphone or say “Hey Google” again to pass down a follow-up command. The problem persists even if the feature is enabled from Settings – Apps – Assistant. Rebooting the phone or toggling the setting on/off doesn’t appear to fix the issue either. It’s likely that the bug appears only on Pixel phones. 9to5Google adds that they could get the feature to work on smart speakers, including the Nest Hub, Nest Hub Max, Nest Audio, and others. On the other hand, it reportedly wouldn’t work on the Pixel 5 and Pixel 6 running Google app beta version 12.45. Google claims that Continued Conversation is compatible with the Pixel 4 series and newer. Since this bug seemingly impacts every compatible Pixel device, Google is likely to take action swiftly. However, the company hasn’t offered an explanation as of yet. Speaking of Pixel phones, the Pixel 6 release has been rocky, to say the least. In addition to screen-related issues, some users also experienced slower fingerprint recognition. Google urged customers to get screen protectors bearing the “Made for Google” certification to remedy this problem. Additionally, some users found that their fingerprint data was erased whenever the phone ran out of battery. The only plausible solution was to factory reset the Pixel 6 or 6 Pro and register fingerprints again. The earliest reported concern with the Pixel 6 has been the “display residual light” bug. Google later said it is working on this issue, with an update arriving in December. Launch-day issues for Pixel phones are not particularly new. Last year, the Pixel 5 faced a couple of problems soon after its release. One bug broke all the on-device sensors, while another brought an audio-related bug.
