I'm having a problem with Moto Voice. Every morning I stream Spotify for a few hours at work with my earbuds in. The phone is in my pocket. For some reason Moto Voice activates by itself and stops the music. When I pull my phone out of my pocket it has that blue screen that is prompting me for a command. This happens randomly every day (maybe 5 or 6 times). I've tried re-training my voice and even did a factory reset. Any idea what the problem could be? I'm on Verizon.
My Moto X has done the same about five times in the 28 hours I've owned it. I'm thinking of recording a new trigger phrase just in case mine's too simple and is getting triggered accidentally by ambient noise.
SiliconS said:
My Moto X has done the same about five times in the 28 hours I've owned it. I'm thinking of recording a new trigger phrase just in case mine's too simple and is getting triggered accidentally by ambient noise.
Click to expand...
Click to collapse
I tried that a couple of times. Didn't work for me. Right now I'm using "Wake up Moto X".
I'm experiencing the same problem with two different Bluetooth devices: an LG Tone headset and a FlexSmart In-Car Transmitter. Moto Voice seems to activate whenever Bluetooth is disconnected or in my case when I power off either device.
As a test, while connected, I disabled Bluetooth through the Settings toggle and a few seconds later Moto Voice proudly exclaimed, "Please say a command".
I changed to the default "OK Google Now" this morning to see whether it helps.
I did wonder whether the Moto Assist screen was appearing for other reasons and not actually being triggered by my voice (such as when the phone switches to car or sleep profiles), but I'm not yet sure.
All the podcasts I listen to think it's hilarious to say the trigger phrases and set off everyone's phones in their cars.
Figured out what the problem is. The headset jack is faulty. If the plug on the ear buds moved a little while it was in the phone, the sound would cut in and out and sometimes activate Moto voice. Got a new phone on the way!
Has anybody solved this issue? Every time I get out of my car, Voice starts up, whether I was streaming or not. I have turned off the Driving part of Moto and it didn't make a difference. It's not a huge deal, it just times out after a while but it is frustrating.
I'd forgotten about this. Changing my wake-up phrase to "Hey Moto wake up" seems to have fixed it - I think I've only had one unexpected trigger since I did that.
I think I solved my issue. I had installed "Bluetooth Connect and Play." I thought it might be the problem so I disabled it - the issue continued. I deleted it entirely today and the problem has stopped. I guess I'll finally have to figure out Tasker and set it up. I bought it on sale a couple years ago and have never spent enough time with it to figure out how to program it.
Related
I just recently bought a brand new moto x off contract. Great phone. This should've been the nexus 5. Anyway, I am having a problem with touchless control. Whenever I wake it up by, ok Google now, and hit the back to cancel. It makes the usual sound but with static. I uninstalled the updates since I can't delete it and downloaded it again. It fixed it. I noticed that with just Google search by tapping and canceling the mic, it doesn't give me this problem. Anyone else have this?
Techno Droid said:
I just recently bought a brand new moto x off contract. Great phone. This should've been the nexus 5. Anyway, I am having a problem with touchless control. Whenever I wake it up by, ok Google now, and hit the back to cancel. It makes the usual sound but with static. I uninstalled the updates since I can't delete it and downloaded it again. It fixed it. I noticed that with just Google search by tapping and canceling the mic, it doesn't give me this problem. Anyone else have this?
Click to expand...
Click to collapse
Don't have that kind of problem. But I've noticed something else: the voice recognition is way too sensitive. Not only that I don't have to say "Ok Google Now" - OK is enough, but sometimes it reacts to my other words too.
piskr said:
Don't have that kind of problem. But I've noticed something else: the voice recognition is way too sensitive. Not only that I don't have to say "Ok Google Now" - OK is enough, but sometimes it reacts to my other words too.
Click to expand...
Click to collapse
I also had this problem, but with time, its less and less often. But if you've setup your voice recognition some time ago, you should try it again and wait a couple of weeks to see if the problem is solved.
Never had any static though. Do you have any third party equalizer of something like that? Also check if you have any open background app that can interfere with your audio.
Wow didn't realize topic title till now. Toothless. Lol. Auto correct. The voice recognition is very sensitive. Activated by others talking in public.
Techno Droid said:
Wow didn't realize topic title till now. Toothless. Lol. Auto correct. The voice recognition is very sensitive. Activated by others talking in public.
Click to expand...
Click to collapse
Yeah, I was wondering about the 'toothless'
I had a similar issue: Touchless control was activating on ambient noise, or even a loud TV. The key was to re-train the launch phrase in a VERY quiet room. My friend trained his X and there was a barking dog next door while he did it. It activated all-the-time, seemingly out of nowhere.
Once we re-trained carefully, in an extremely quiet environment, it no longer activates un-intentionally.
You might give this a shot! To Re-Train, go to Settings > Touchless Control
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
gakio12 said:
Something I noticed today while driving was my Bluetooth audio would cutout every few minutes. It only happened on my Nexus 5 with an alpha ROM, but was fixed later. Anyone else notice this?
Click to expand...
Click to collapse
On the new moto x? No, I just had a couple hour car ride with zero issues listening to Play Music and Slacker Radio. Made a few calls, no issues either.
This happened to me on a 20 mile bike ride. Horrible having choppy audio for almost a few hours
I just noticed this too. I do have a Moto 360 as well so maybe that is messing with the blueooth? I have gone a couple car rides and it's perfect, and others it's really choppy.
This does seem to be a problem with me too. Sometimes perfect and sometimes not. When connected to Bluetooth I notice that Google maps speaker goes in and out as well as moto voice while driving
I can confirm that if you have a 360 this is the cause. You can verify this by disconnecting the 360 through wear and the problem going away. For now what I have due is set up an IFTT to disconnect wear when by car's Bluetooth is connected.
I actually don't have anything else connected via Bluetooth and it still happens to me.
I figured it out. I was driving and I turned off Bluetooth completely and the voice worked perfectly. As soon as I connected back to Bluetooth the voice got choppy again...
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
I'm experiencing the same issue, really sucks.... I'll try disconnecting the Moto360 on my drive today and see if that fixes it - although I swear I've had the issue before while it wasn't connected.
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
SetCPU could possibly do this. You can definitely set the minimum CPU clock, but I'm not a 100% whether you can get it to do this WHEN a bluetooth device is connected. SetCPU has a profiles where you can define certain parameters based on conditions.
Of course, before you can get SetCPU working you'll need to root your phone and I have a suspicion that all other CPU clock apps will need root access too.
Has anyone had any luck resolving this?
gakio12 said:
I looked over in the Note 3 forums, and users were experiencing the same thing. Someone said to listen to music with the screen on to fix it. Today I listened to music with the screen left on and sure enough my music didn't stutter once the whole car ride.
This leads me to think either the processor is getting clocked too low for playing music through A2DP when the screen is off, or perhaps active display makes it stutter whenever it activates. I will look into it further today.
In the mean time, does anyone know of a processor control app that will change the minimum processor clock if bluetooth is connected? Perhaps there is one with a tasker plugin.
Click to expand...
Click to collapse
I'm hoping that either an OTA or Android L will fix this. My Moto X is fine when I'm using my Motorola S11-HD headset, but when connected to my car it goes in and out every few seconds.
So it isn't the processor. So far i have it down to either Wi-Fi or active display. Will report more when i find it.
Turning Wi-Fi off while connected to my car Bluetooth has fixed the issue for me. At least, so far it has.
I'm using PowerAMP for playing music and when I enabled the "high priority" setting in the headphone/bluetooth settings it seems to have resolved the problem until today. This morning on the way from work it started to cut out every few seconds. grrrr...
I have 2 bluetooth adapters in my car, one which takes only phone audio and one which takes phone and media audio, the latter one continously drops and reconnects phone audio (even after forgetting the other device), which makes me believe it is some hardware compatibility issue
I have posted on the official Motorola Forums but I though I should re-post here as well becuase well....XDA fixes things.
So I just purchased a Moto X 2nd Gen Pure Edition as an upgrade to My 1st Gen Moto G. Both phones have the same problem with the Bluetooth Audio sounding like a scratched CD skipping and studdering and it seems to be way worse a problem on the Moto X than I ever had on the Moto G. It's not buffering it happens with music on the phone. It doesn't happen every time I'm in the car but I'd say 50% of the time.
I would think it's the car but before the Moto G I owned a Galaxy Nexus and never had the problem as far as I remember. I'm sure I would remember it's really really annoying. I have even tested with a friends HTC M8 over a long road trip and there seemed to be no issue there. In my car (2011 Subaru Impreza) with the G or X after a time it eventually starts skipping even if it takes a couple hours.
So I did some research before and have tried various things.
I have disabled the Wifi while connecting to BT as Motorola has recommended to owners of other phones. That didn't help them it doesn't help me.
I have removed all other BT devices from the phone while connected. Nope
I have removed the Phone in the profile so my car doesn't try to use it as a phone as well at the same time. Nothing
I have done all of the above at the same time stopped every other program other than Google Music and added the phone to my car fresh and I still have this issue.
During my research about my car the only complaints similar I found seem to come from someone else with Moto phones. I dont' know what they do special with their Bluetooth but it's not helping me out.
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
godutch said:
You could try to upgrade your car's firmware. Some dealers do this for free, with some cars it is easy to do yourself
Click to expand...
Click to collapse
This is what fixed the audio in my Mustang with Sync. The Ford dealership did not charge me anything for them to do it.
Sent from my XT1095 using Tapatalk
Has anyone experienced this? Seems to happen often where Moto Voice will activate and ask for commands.
wrecklesswun said:
Has anyone experienced this? Seems to happen often where Moto Voice will activate and ask for commands.
Click to expand...
Click to collapse
I've seen in on disconnecting from car bluetooth.
Once or twice.
Sent from my XT1095
Any way to lessen? or what causes this to happen?
I've had this happen 3-4 times since I got it on Thursday, so they definitely need to tweak the software to be a little more accurate.
Re-record your voice launch phrase in a very quiet environment.
Restola said:
Re-record your voice launch phrase in a very quiet environment.
Click to expand...
Click to collapse
Yes, this is the answer. My first turbo never randomly activated with my very basic phrase (Okay Turbo). My second one did it all the time and it became very frustrating, until I re-recorded it.
rgerrans said:
I've seen in on disconnecting from car bluetooth.
Click to expand...
Click to collapse
I found the cause of mine. I use Tasker and had it doing a Media Stop Key emulation which seems to be what was triggering it.
I too had the moto voice randomly activating. I just picked a more complex phase and that did the trick.
it seems shutting down Google now solves alot
I had moto voice pop up while at the movie theater during Interstellar last night. Had my phone on silent and everything, but it made the loud ding noise anyway. It must have thought someone in the movie said "OK Google." This is the only time I've had it come up without my voice command, but just a heads up to movie-goers.
My activation phrase is Hey Turbo Turbo, it seems to trigger repeatedly when in the car, usually with the radio on, sometimes with it off. It gotten so bad I had to disable voice activations.
For me in the car, moto maxx wake up like if I said my phrase "ok moto maxx" even watching my tv too..
Definitely it's a bug
Sent from my XT1225 using XDA Free mobile app
Use "OK Google Now"
No problems!
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
I kept my ringtone to the default (The Big Adventure in Pixel Sounds)
When I get an incoming call, the ringtone stutters/drops out quickly several times for the first few seconds, then it seems to calm down and play normally!
The speaker itself seems ok (ie. youtube etc, and when I play the ringtone manually when selecting a ringtone)
Is anyone else getting this too?
I also have a Huawei GT2 watch connected (bluetooth) so it could well be related to this.
I have the same issue. It started on my Pixel 2XL earlier this year. I bought a Pixel 5 for my mom and hers doesn't have this problem. Edit: My Amazfit Verge watch was causing this. I shut it off and called my phone and didn't have this problem anymore. That watch was on it's last leg anyways so I ordered a new smart watch today. It wouldn't hurt to try the same thing with your Huawei GT2.