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.
Related
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'm having a very similar problem with regards to #1 but it's doing it with Bluetooth for me!
At midnight on the dot, it will disconnect my connected Bluetooth devices. It doesn't shut Bluetooth off, it just drops the connection. I posted about it here: http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-disconnects-midnight-t2973187
Your phone sound possessed! Call 1-800-Exorcism now.
You right, weird/unusual.
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
erickh0 said:
Hello. Does anybody have an idea why there is no sound whenever I send/receive calls? Also, the UI/related app crashes whenever I do the same.
No problems when I uses SMS though, so I don't think it's a signal problem.
Click to expand...
Click to collapse
Maybe a theme issue?
Nope. Just reformatted the phone and did not install any theme/launcher apps
Same issue
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
same here
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Me too. Bumping in hopes of a fix.
Same. I'm running a custom ROM and haven't upgraded to 8.0 yet. Does the issue persist with 8.0? Google told me today to revert to stock and upgrade to see if that fixes it.
Sent from my Pixel using Tapatalk
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Having the same issue on a regular Google Pixel. Also Google Assistant is not working using the "Ok Google" voice command and the phone app - answering and ending calls lag - same issue mic and speaker do not work. In Safe work, they work but on rebooting same issue persists.
xbiggyl said:
Same thing started happening for me yesterday!
I was sending a voice message on Whatsapp.
The msg was sent but no audio was recorder.
I received a call but there was no audio (both in & out)
I tried making a call and the same happened.
The "Phone" app would even hang after hangup and would crash. I get a white screen with the G logo and a loading bar beneath it, then it would start.
Starting the phone app is also sluggish.
If I make a call (and get no audio) I try to switch to loudspeaker and I could hear the other party but for a couple seconds then it's muted, then comes back for a couple seconds, and keeps doing it intermittently.
Sound from music app and videos works fine.
SOMETIMES after a reboot phone audio&mic would return but temporarely.
SOMETIMES when I try rebooting and it doesn't work, I try safe mode and it work (not all the time though)
SOMETIMES switching from LTE to WCDMA only fixes it temporarly.
This is really unpredictable.
I reverted back to a 7.1.2 stock. At first the issue persisted then it was fixed for a couple hours.
I updated back to O and audio worked for some time but after a few minutes, the issue returned.
Now I am on a clean stock install of O. without any apps installed. The audio comes back for a few minutes, then it's gone for hours.
Hopefully this thread will grab the attention of someone who might be able to help
Click to expand...
Click to collapse
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
me too
jasona08 said:
I've starting having this problem too... its very frustrating. Im on Stock O (OPR3.170623.008), Verizon,with unlocked bootloader.
Click to expand...
Click to collapse
stock O, Rogers.
bump - hoping someone has heard something somewhere.
Same here for my regular pixel, this is really annoyed. It just starts happening after almost 12 months since I got it.
Andre... said:
I've been having the same issue and I have no idea why. Performed a factory reset. Tried running the phone in safe mode. It seems like it works briefly after a restart but then cuts out after a few minutes. I never had any issues like this before the update.
Problem for me goes as follows.
Receive phone call
Try to answer
Either the phone answers the call and there is no sound (mic or speaker) but otherwise acts normal or the phone refuses to answer the call and the "swipe up to answer" UI keeps reappearing. When the later happens the phone crashes and goes through a restart that takes longer than a normal one.
Make a phone call
No sound (mic or speaker)
The issues with the microphone seems to affect other parts of the system as well, such as ok Google and voice typing.
Speaker seems to work fine other wise
Putting the phone in safe mode seems to delay the problem sometimes.
Click to expand...
Click to collapse
I have been having these same issues with my phone. I noticed it happened after I downloaded the what's call app to make a WiFi call. I noticed another user had the problem after installing what's app to her phone. Could this somehow be the problem? I am not super tech savvy but I am convinced it is related to my downloading the what's call app. I have uninstalled the app. Still the problem remains. Any ideas? Thanks.
Has anyone that posted in this thread was able to resolve this issue? I also have this problem, I'm currently waiting for it to happen again so I can pull logcat but no idea what I should be looking for since I have no idea what can cause not being able to hear the caller so randomly.
I was originally suspecting V4A, but last night I flashed stock system img, did not install V4A and same issue occurred.
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.
My Pixel 6 Pro has a similar problem ever since the Mar 5 update has been installed. Since then, every phone call I made comes with the non-stop notification tone literally every second. For now, I managed to get around it by enabling the "DND Mode", but it isn't a long-term solution.
Is there a way I can re-apply the same update? or flashing a new one would help?
To be clear, you're saying that you keep getting the notification tone even after answering the call? If so, is it the same as your ringtone?
Is your bootloader unlockable? If so, Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
It wouldn't surprise me if that doesn't fix the issue, however. Have you tried rebooting? Maybe clear the cache and app data for the Phone app (but then you'd have to re-customize the settings for the phone app to your preferences).
I'm not on the March update, but I also don't receive many phone calls anyway.
that notification tone, during normal time, represents incoming message. It is very short, unlike a ringtone..
Tried rebooting and clearing cache and app data of the Phone app. In fact, that notification could likely come from anything like WhatsApp, Messenger, Twitter...
I noticed that the repeating tones would not happen if the phone is on silent mode. So for now this is my workaround.
Very interesting, and strange. There have been settings in some OEM's phone apps you could enable to get notification tones at regular paces - usually once a minute - while on a phone call, but the issue on yours is only similar since it's constant / every second.
I stick with my recommendation of clearing the app cache and data for the Phone app. I also assume you're using the stock Phone app that Google provides.
In my previous phone (OnePlus 6T), the very same tone happens once in a while, but only at the moment an incoming message arrives. Pretty sure I am not getting a new message every second this time around, and I think it was triggered by apps other than the Phone app. I just noticed that the same symptom showed up when I tried to play video clips from certain apps as well.
And yes, I am using the stock Phone app.
Sounds like a factory reset and only selectively installing and configuring apps, or trying to figure out which app is causing the issue.
If you factory reset, I would first not even restore any apps at all, so you can verify if you have the same problem without any third-party apps installed at first. I would suspect you won't have issues then. And then when you install apps, do it in groups of your most important ones first, maybe at the most 10 at a time, then re-verify each time if you have the same issue or not, then the next batch of app installs. It could be a particular setting in a app as well, so it's possibly merely installing an app might not be enough, so each group of apps you install, make sure and configure them as well.
If you don't factory reset, go the opposite way, uninstall your least important third-party apps and see if the issue disappears. Keep track of which apps you're uninstalling in each group. Keep doing this in reasonably sized groups of apps until you narrow down when the problem stops happening.
Once you find which group of apps being uninstalled keeps the issue from happening, you can reinstall in even smaller batches, among the ones you most recently uninstalled, and eventually find the one causing the issue. In some ways I think it's easier to go the other way around, though, start with a factory reset.
Found the culprit!
Kind of silly: I have installed this app "Internet Speed Meter Lite" when I first started using my P6P, which is for me to monitor my real-time network usage (courtesy of that endless WhatsApp - Google Drive restoring process....). It basically refreshes itself every second and this morning I tried temporarily disabling it, the problem goes away even when the phone is not set to silent mode.
Glad I didn't have to come to the point of factory resetting the device, as I really don't want to go through the WhatsApp restoring process.
Thanks for all the input, much appreciated.