Related
Hi everyone,
I have an issue with Autovoice Continuous vocal recognition (a great tasker plugin, which basically makes your phone listening to you at all time - or at the times you want if you're concerned about battery usage) since I updated to KitKat a few days ago.
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Thanks
nuts77 said:
Hi everyone,
I have an issue with Autovoice Continuous vocal recognition (a great tasker plugin, which basically makes your phone listening to you at all time - or at the times you want if you're concerned about battery usage) since I updated to KitKat a few days ago.
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Thanks
Click to expand...
Click to collapse
It might help you: http://www.youtube.com/user/taskertutorials/videos
nuts77 said:
I finally got it to work (activating Google Voice Search in Keyboard & Language settings, which took me almost one hour to find out!) but now, when Autovoice continous is enabled, I hear the google voice search beep "notification" every 5 seconds... Which is a bit annoying
Just wondering if anyone using autovoice has had the same issue (and better, how to solve it!)
Click to expand...
Click to collapse
I have/had the same issue and it took me some time to dig it down.
On my Note 10.1 2014 LTE it is caused by the latest update of Google search which I installed yesterday via PlayStore.
After reverting that (luckily my device is rooted and I use Titanium backup), the beep is gone.
So somehow, Google has introduced that and AutoVoice can (yet) not disable it.
akxak said:
I have/had the same issue and it took me some time to dig it down.
On my Note 10.1 2014 LTE it is caused by the latest update of Google search which I installed yesterday via PlayStore.
After reverting that (luckily my device is rooted and I use Titanium backup), the beep is gone.
So somehow, Google has introduced that and AutoVoice can (yet) not disable it.
Click to expand...
Click to collapse
Yes, solved it by reverting to an older version of google search as well and there is no other way around yet.
The problem is that in the latest versions of GS, the "beep" notification sound is pushed through the media sound channel instead of the notification one (which autovoice is muting and unmuting, since continuous mode is basically just a voice search triggered every 5 seconds).
I have the same problem. Currently, there is no other solution then reverting google search to previous version. Hopefully next autovoice update will solve this issue.
There is already an update.
Unfortunately, the change of google in the search function (together with the update) causes parallel running apps using the speakers to be muted every 5 secs for a moment. That is anoying (eg. Internet radio).
Yes, there is new version, I was using an old one. It's all good now.
Послато са LG-D802
Question
If someone else has screen-off Google Now set up can you test and see if this lag exists after the phone has been dozing for awhile? I know Google is doing server side voice updates to the English language but I am trying to determine if this is a device issue or as server side issue.
Issue
When using the screen-off Google Now function, the screen will turn on and acknowledge my voice and my search terms but the voice feedback and the actual feedback takes several seconds to register. For example, from screen-off I asked Google to set a timer for 15 minutes. It turned on, showed my search terms, and the colors spun for almost 20 seconds before launching the voice feedback and performing the task. Cannot replicate this issue with the screen on and using the OK Google command.
Conditions
Model: Nexus 6P 64GB
ROM: [ROM]【6.0.1】MMB29V -【Stock】【Lite】- 03/07/2016
Bootloader: MMB29V
Radio: 32R
Xposed: No
Rooted: Yes (2.68 Systemless)
TWRP: 3.0.0.0-1
Kernel: Stock
Mods: None
Wi-Fi: Yes
Carrier: T-Mobile
I just did a search now. Once Google Now recognized my voice, after not speaking loud enough the first time, it displayed my sample question in less than 5 seconds.
That sample question? "Why is the sky blue?"
Thank you for running the test. I ran the exact same question on my device and I can tell that my device is hanging when I issue the command. I had to unlock the device to cancel the search and then I was able to re-run it. I'm going to clear app data and see if that helps in some way.
Since Marshmallow dropped, I haven't been able to use Google Now with the screen off. Every once in awhile it will work, but most of the time it won't. Half the time it won't even work when the screen is on and I'm in an app.
So, haven't had much time to play and learn yet, and this is my first smart watch. But I did try sending emails and text via the watch. If my screen is on, it works, if it is off it fails.
My phone is a Note 4, with an MM Rom. I'm wondering if Doze or something is the problem.
When I was setting up the app, it did go through an option to let the Zen software run in the background, and I allowed that.
Any thoughts?
ewingr said:
So, haven't had much time to play and learn yet, and this is my first smart watch. But I did try sending emails and text via the watch. If my screen is on, it works, if it is off it fails.
My phone is a Note 4, with an MM Rom. I'm wondering if Doze or something is the problem.
When I was setting up the app, it did go through an option to let the Zen software run in the background, and I allowed that.
Any thoughts?
Click to expand...
Click to collapse
I am not sure if I really understand your question.. are you talking about phone screen or watch screen?
Also for notifications like text you don't need to have Zenwatch app at all, its a core feature of AW. I am using it (& Moto 360 gen 1 before) with my S7 on MM and doze shouldn't cause any issue.
Ah, I just read the thread title, it gives more info
I would say factory reset your watch from the Android Wear app on the phone and try to pair again. I have done it a bunch of times with my Moto 360 but haven't tried with this one yet. It should work though, I'll try on mine and report back.
jainanshal said:
I am not sure if I really understand your question.. are you talking about phone screen or watch screen?
Also for notifications like text you don't need to have Zenwatch app at all, its a core feature of AW. I am using it (& Moto 360 gen 1 before) with my S7 on MM and doze shouldn't cause any issue.
Ah, I just read the thread title, it gives more info
I would say factory reset your watch from the Android Wear app on the phone and try to pair again. I have done it a bunch of times with my Moto 360 but haven't tried with this one yet. It should work though, I'll try on mine and report back.
Click to expand...
Click to collapse
Well, I reset my watch. I still get the message "Try again on your phone" . But, I found that the email in fact did send. So not sure what's up with that. Will be interesting to see what you find.
Oh, another thing. I find quite a delay between my phone ringing and it ringing at the watch. I'll have to do some experimentation, but I'm not sure it will ring long enough for me to answer it at the watch. Not that I plan to do that much, but, anyway...seems like maybe the interaction time between the watch and phone is not very good.
Hey sorry for replying so late, but as expected, calls and texts work just as they should. Were you able to sort out issues on your end?
About the delay, I think there has always been a little delay for calls to show up on watch (at least that was the case with my moto 360), delay on this is the same. It does vary a little bit from time to time, sometimes it very little sometimes a bit longer but that's just wireless connectivity imo. But in no case its long enough that call would stop ringing and go to voicemail.
jainanshal said:
Hey sorry for replying so late, but as expected, calls and texts work just as they should. Were you able to sort out issues on your end?
About the delay, I think there has always been a little delay for calls to show up on watch (at least that was the case with my moto 360), delay on this is the same. It does vary a little bit from time to time, sometimes it very little sometimes a bit longer but that's just wireless connectivity imo. But in no case its long enough that call would stop ringing and go to voicemail.
Click to expand...
Click to collapse
I need to do some testing with calls. I don't even know for sure how to answer at the watch.
I find that the watch gives me the error message, but does send the text.
I'm having real problems with my phone when hooked to the watch. I'm going to open a thread on that topic now.
I just got Android Wear 2.0 on my Zenwatch 3 and I'm sorry to say Assistant and gestures are lot worst now.
First of all, i'm italian, and Assistant poorly recognise italian lenguage.
I use to use smartwatch especially when i'm driving or when i'm on my work bike (i'm a pony express) so I need a device I can use touchless.
Wear 2.0 lost some gestures as the on to go ahead to funcion like "reply" or "delete" in messages (the ones used pushing down or pulling app your wirst) so now i must to touch the screen for everything.
About Assistant: i often use it to send Telegram messages just by telling Google Now (obviously in italian) "send Telegram message to SomeoneX" followed by the message instead.
Now, if i tell "Ok Google. Send a Message to (ex.) Mark" assistant shows me "to whom?"... anda I say "Mark"... "to whom?"... "MARK!"... "to Whom?"... IN A FU****G LOOP!
jUST i CAN'T USE MY SMARTWATCH WITHOUT MY HANDS ANYMORE!
Hi All,
I just recently encounter the following error on my Huawei P9 Plus, when I use an application that requieres the need to record (Shazam, cámara, sleep as Android) I pop up message appears showing that "com.android.googlequicksearchbox:interactor" will not be able to record right now, I read in other forums that the main problem is with the OK Google functionality to identify in any screen, if I turn it off the message disappears, the thing is that I use the OK Google functionality heavily, so the solution does not work for me, I have cleaned the cache of the apps, uninstalled and installed and even wipe cache partition with no help...
Anyone with the same problem?
This just recently started, noticed it yesterday
I have attached a image for your reference.
Same thing happened to me. In order to resolve this, i've disabled the "Ok Google" detection from any screen.
Somehow with recent updates of Google Play or whatever it is might have triggered this error.
Clear cache & Reset Factory doesn't solve this either.
I got the same problem on P9 lite. With some search I found that almost all the guys reporting this error seem to be using Huawei phones. I would also like to see a fix, hope someone comes up with something like disabling "ok Google" detection when another app starts recording audio.
Seems to be due to an update with the Google app, as it happened to me all of a sudden (a few months back), without any changes other than app updates. All i've managed to find on it are from fellow Huawei users as well.
For a phone that is aiming at other, more established, flagships, they really do seem to **** up on the little details (not counting the 'shoot with a DSLR and claim it's a P9' debacle or the more recent emmc/ufs outright lie, which aren't so 'little'). After paying so much, why should I have to choose between having OK Google available on all screens (as it was designed to be), but have to deal with error messages, or disable the feature (basically making it next to useless) just to clear the errors?
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
ratola said:
Hello to everyone there,
I have next problem on my Nokia 8:
When somebody calls me or when I call someone on viber, I turn on speakers and other side can't hear me. Also when I put it on video call the same issue conitnuous to take. Regular GSM calls or viber VoIp calls works great as well as video calls with headphones.
I open ticket to a viber about this problem, and they told me I need to contact my manufacturer.
Yesterday I installed an Android pie from beta labs, but the problem still exists. How do you think the problem is hardware?
Click to expand...
Click to collapse
Hi ratola,
you can dial *#*#372733#*#* for a hidden FQC test menu, here you can test each mic seperated, i guess in your case it's the second mic in the top-speaker.
- Joeigel
Joeigel27 said:
Good afternoon,
I have had a Nokia 8 for a few weeks now and have now found that my microphone only works during calls. While I'm on the phone everything works normally but in all other apps nothing happens, e.g. in Whatsapp you only hear a short crack when you hear a voice message and then nothing, although you have said something (see attachment), also other apps that use the microphone like the Google Home App or a guitar vocal app don't work. Of course the permissions are set correctly for all apps but apparently this has no effect (see attachment). I've already written with Nokia Support, but after 14 mails about permissions, emptying caches and doing softresets they couldn't help me. Finally I was told to wait for the next Android update and hope that my problem was fixed there, or I should send my phone back to the dealer. My hope now is that one of you has an idea what could be the cause of the problem.
Thank you for your time!
- Joeigel
Attachments:
picload.org/view/dclcpodg/screenshot_20181201-165257.png.html
picload.org/view/dclcpodr/screenshot_20181201-165237.png.html
Audio Message from Whatsapp:
instaud.io/30ZI
Click to expand...
Click to collapse
Hi Joeigel, unfortunately I have the same issue (and story regarding contacting support). The only way I can make calls via for instance WhatsApp is by using a handfree headset, or setting it to speaker-mode.
Waiting for the Android 9 release, if this isn't fixed with it, I'll send it in for warranty.
I do have another issue with the phone, and that's when I unlock my phone using the fingerprint scanner, 1 out of 4 times or so, the phone enables split screenmode. Do you (or someone else here) have similar experiences. It's quite annoying.
Update: Installed Pie, and no improvement. Issues still persists. Returning the phone today.
Sorry for the late response, my phone is also on it's way back to GB...
Joeigel27 said:
Sorry for the late response, my phone is also on it's way back to GB...
Click to expand...
Click to collapse
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
odyon said:
Ok, just got an update from the repair-center, they replaced a part and it should work OK now. Curious to see what they did and if it's resolved. Have to wait until it's shipped back. But keep us also posted about your progress
Off-topic: another issue I sometimes experience is when I unlock my phone with fingerprint, it sometimes switches automatically to the split-screen mode. It happens quite often and it's a bit annoying. Did you experience something similar with your Nokia?
Click to expand...
Click to collapse
I didn't experienced something like this. Did they send it back to you yet? Maybe they fixed both... ^^'
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
nagesco said:
Microphone issue here too.
Internal mic on front facing camera is the culprit. I noticed a few weeks back that my 'ok google' hotwords were no longer working. This became a problem after I installed the december security patch. I rolled back to the november security patch and this did temporarily fix the issue, after I had gone through the initial setup of the phone, my 'ok google' hotwords worked, until i went to use the camera to see if the issue still existed... unfortunately it does. Contemplating rolling back to july to see if the issue is resolved, or trying to move forward and installing pie.
Click to expand...
Click to collapse
Could any up or downgrade fix it?
Joeigel27 said:
Could any up or downgrade fix it?
Click to expand...
Click to collapse
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
nagesco said:
I've tried going up or down, I have oreo and pie on each of my A/B partitions and it does nothing. When i downgraded to oreo it worked for awhile but updating the google app or some sort of background service broke it again. Its definately mic 3 that has a fault, it has background interference noise when i do the test, it also occurs when recording video with the front facing mic on camera, the problem with the mic never goes away, after up/downgrading, I can't say whether this is related since it works prior to updating. rolling back/disabling doesn't solve the problem for the apps. Microphone/earpiece holes are clean and undamaged.
Click to expand...
Click to collapse
After further testing of this issue, the 'OK Google' issue is still present, if I want to ask google assistant 'ok google' the microphone barely picks up anything or even my question, practically screaming into the microphone is the only way to activate it, this matches with the results on my google activity, listening to my recordings of my queries shows evidence that the microphone sensitivity is way too low.
HOWEVER, when using google assistant by means of pressing the microphone and then asking the question, the result is clear and understandable and doesn't suffer from volume issues, I can't pinpoint if this is an issue with the Nokia specifically, it is not a problem with any other application that uses the microphone.
Having the same issue with Mic 3. It means I can't use it in speakerphone mode during calls or in Skype. It doesn't prevent me from using the Google assistant though.
My smartphone was sent in and repaired (complete motorboard replaced). During the time it was gone Android 9 came out, so I'm not sure if it was the repair or the software update.
But it works again without any problems
Kind regards
Joeigel