Starting yesterday, I find that my AT&T Note 5's recent-apps list occasionally disappears--pressing the recent-apps button just shows "No recently used apps" and continues to do so no matter what apps I subsequently start. The only way I've found to restore the recent-apps function is to reboot the phone. When I do that, I can immediately once again see all the previously-listed apps that had disappeared from the list.
A web search shows this to be a widespread problem, especially in the past two weeks, across a variety of phones and carriers. Some users report that using the "OK Google" feature of Google Now seems to trigger the bug. My own occurrences of the bug have always been preceded by a recent "OK Google", but I can still use "OK Google" without difficulty most of the time, so I'm not certain that's the trigger.
It appears that today's beta update of the Google App (6.3.29.21.arm64) may have fixed the problem. So far so good, anyway.
Related
Hi all,
I have sometimes the problem, that at first the watch reacts properly after saying "Ok google". It records my command and also displays the recognized text correctly, but after that it does not execute the command but displays "offline" (e.g. calling a contact or setting the alarm clock).
The connection to the phone itself (using Bluetooth to my Samsung Note 4, Android 5.1.1) is stable. I have read about this behavior also on other forums with different smart watches (e.g. Moto 360). There is some indication that the problem is caused by the phone being unable to access the Internet at the time, although it has a stable and strong 3G connection with no data restrictions set (e.g. allow background data). It also happened when the smart phone was connected to my local WiFi.
The problem is not 100% reproducible. Most of the times the command gets executed by the first try, sometimes the problems disappears after repeating the voice command several times and sometimes it disappears by unlocking the smartphone.
Have you experienced this problem as well sometimes? If yes, are you using a Samsung smartphone and which Android version are running? I somehow have the feeling it is related to the android wear app and maybe to Samsung smartphones.
I also use smart unlock, which means I can simply unlock my phone by swiping the homescreen as long as my phone is connected to the watch and have to use fingerprint unlock otherwise.
foo said:
Hi all,
I have sometimes the problem, that at first the watch reacts properly after saying "Ok google". It records my command and also displays the recognized text correctly, but after that it does not execute the command but displays "offline" (e.g. calling a contact or setting the alarm clock).
The connection to the phone itself (using Bluetooth to my Samsung Note 4, Android 5.1.1) is stable. I have read about this behavior also on other forums with different smart watches (e.g. Moto 360). There is some indication that the problem is caused by the phone being unable to access the Internet at the time, although it has a stable and strong 3G connection with no data restrictions set (e.g. allow background data). It also happened when the smart phone was connected to my local WiFi.
The problem is not 100% reproducible. Most of the times the command gets executed by the first try, sometimes the problems disappears after repeating the voice command several times and sometimes it disappears by unlocking the smartphone.
Have you experienced this problem as well sometimes? If yes, are you using a Samsung smartphone and which Android version are running? I somehow have the feeling it is related to the android wear app and maybe to Samsung smartphones.
I also use smart unlock, which means I can simply unlock my phone by swiping the homescreen as long as my phone is connected to the watch and have to use fingerprint unlock otherwise.
Click to expand...
Click to collapse
I had an LG Urbane that had this issue. I did a lot of reading and found that pretty much every Android Wear watch model has this issue, but it is seemingly random wrether or not you will experience it. I read the same thing about the Huawei watch but took a chance and swapped it for my Urbane and it has been working fine. I would try and return it for another Huawei or a different model, and also downgrade the Android Wear app on your phone to version 1.3.0.2369832 (didnt fix the connection prob for me, but did help with other issues)
On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.
Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
repsol89 said:
Hi everyone,
I'm using OnePlus 3 for 4 months and through every update (3.2.1 --> 3.2.2 --> 3.2.4 --> 3.2.6 --> 3.2.7) I've experienced this strange issue.
Sometimes (like once in 2 days) the voice search, the one that normally activates with "Ok Google", self-activates and waits for a command, eventually saying "I didn't understand".
It happens when the screen is on or when the phone is charging, usually when there are other noises (people talking at work, television, etc).
Did it happen to anyone, too? I never experienced this behaviour in none of my previous phones, I even tried restoring voice recognition but the problem is still there.
Thanks in advice!
Click to expand...
Click to collapse
I never had the issue on my LG G2 but it happens now. Also happens often on my Galaxy Tab S2 really often. I think its a Google thing and they have made things too sensitive.
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
natboy said:
Go into Google Now, Settings, Voice, "Ok Google" detection. Turn off From Any Screen.
Click to expand...
Click to collapse
Well, actually that's not a solution, more like a "workaround"... I like the "Ok Google" From Any Screen feature, I use it once in a while.
It's like asking "I have bad call quality, what can I do?" and receive "stop doing voice calls" as an answer...
Update: I flashed 3.5.4 yesterday, same issue experienced today.
I tried to install google assistant, but it showing "This account is not eligible for the feed"
I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.
... and has a way to fix them?
1. the phone will decrease its refresh rate from time to time and stays there, and the "stuttering" is only fixed by rebooting. Yes, I am aware, that Whatsapp and Telegram voice messaging is occasionally linked to it, and can be handled by removing the apps from memory. But not in the mentioned cases.
2. "Ok, Google" accessing the assistant doesnt work from now and then. And is back to normal a few tries later.
3. When talking over the phone with speaker mode and browsing on the phone, the notification bar cannot be pulled down any more, which is annoying cause I cant easily open the phone tab to end the call.
Anyone, guys?
2. I have a similar bug with quick tap, it seems that a system app freezes/crashes, and without knowing the exact culprit the entire system needs to be rebooted to enable the function again.
Plus my "Ok, Google" also stopped working in the past, found no way to fix it yet. It's probably an Android 12 bug.
Since yesterday I noticed my AOD does not work when on a call, screen goes dark. I go into AODsettings and it still turned ON.
There's only been one update since the phones been released, besides the FPS update, after a few updates it'll be fine
I have noticed "OK Google" not responding at times as well.. not as bad as my 2XL was at times, only a reboot would fix that...but is annoying to say the least especially when driving. And I don't think it works while using Waze or Maps for navigation either which stinks, maybe I need to use Android Auto for that integration to work right.