So my dad just picked up a Moto X today on Verizon, I've had my DE edition on VZW for about 2 weeks now. Well, I was over at his house today showing him some stuff, and I noticed his phone announced calls and texts all the time, even when not driving, and asked him if he wants to answer. I of course turned off Moto Assist, but it still announced calls and asked if he wanted texts read back. (It would announce who texted and ask if he wanted to listen, or ignore. Not sure if mine does this, I had Assist off before today) I went through every single option on his phone. I'm guessing the Moto Assist is bugged into thinking he's always driving, but the little icon never shows up in his notifications, and I actually turned off Assist and it was still doing it. Cleared data too. I tried everything. Reboots, turned on and off GPS, etc.
The rub is, we both actually LIKE it on all the time. It's nice to just have the phone on the desk and hear who's texting and the message without having to touch the phone. It's nice to be able to answer the phone on the coffee table without grabbing the phone, or even moving.
Is there anyway to enable this functionality all the time? (Or disable it on my dad's phone for that matter) Has anyone else run into this 'issue'? (If my dad hadn't seen my phone, he would have never known it wasn't supposed to be like that all the time.) Any ideas?
I too would like to see this 'feature' as a option, and I hope it can be enabled [on purpose] in the future. (If Motorola doesn't have sense enough to make it an option, maybe a ROM developer can.)
I searched and found this:
We're aware of a rare condition when calls and text will be announced even when you can't see the "drive mode" notification on the status curtain. We're fixing this in the next upgrade. (The simplest way to get out of this situation -- and it's not that simple -- is to leave Assist's drive mode settings on, get in a vehicle, allow drive mode to kick in again. When you do that, Assist will get back to the correct state. After the issue is fixed, you should rarely encounter the issue again. Yeah, I know. Not something anyone is eager to do but we wanted to put it out there.)
Click to expand...
Click to collapse
http://forums.androidcentral.com/motorola-droid-maxx/314715-assist-driving-problem.html#post3072243
FWIW I first thought your dad's phone might be stuck in "car mode" as thought it was in a car cradle, but that would have a steering wheel icon in the notification area. I actually tried car mode by using the "car mode on" app to force it on. It seemed to put my phone in car mode, but that alone did not cause the phone to announce calls, etc.
Thanks man! I actually found that post as well earlier today, it looks like it is indeed a bug with Moto Assist. Funny thing is, my dad has it left on and I called him this morning after he drove to work, and it's still working. IDK lol, but he likes it so whatever.
I would LOVE to be able to do this while playing video games, or working, or whatever though. Motorola better just make a toggle switch... it's not like it's hard.
Related
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
FSRBIKER said:
Is anyone experiencing their phone waking up and waiting for you to ask it something? It's happened just sitting on the counter, my pocket or streaming music/podcasts. It happens at least one or more times a day, I tried retraining it for my voice a few times but still happens.
Click to expand...
Click to collapse
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
natezire71 said:
Go retrain it once more in a completely silent room. You should be able to hear nothing except air moving (fan, a/c, etc.). Then report back.
Click to expand...
Click to collapse
jhnl33 said:
Biggest thing is keep it at arm's length. Like really, extend your arm to the fullest, and then speak normally. Try it.
Click to expand...
Click to collapse
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
Good luck! I had the same issue as you in the beginning. I uninstalled updates and reinstalled to try to make sure previous cache and settings were cleared and re-trained at arms length and now it works pretty well!
FSRBIKER said:
The last time I walked out to my garage to be away from any noise, I'll try again today and make sure I hold it at arm's length(tried that on initial setup)
Click to expand...
Click to collapse
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
jayboyyyy said:
also, make sure you use the same pitch and cadence when saying it. If i want the phone to pick up my voice easier, i can say ok google now when training it in slightly different ways. But then my phone also comes on and thinks im saying it when no one has said anything close to ok google now. If you make sure everything sounds the exact same when saying it, i didn't run into any problems. But i can't wake the phone up when i first wake up in the morning lol. I always try but i apparently sound like death whenever i first wake up.
Click to expand...
Click to collapse
I agree, try using the same voice for all three samples. I know that early on people were suggesting you say it with slightly different speed etc but I have found it is best to try to say it the same all three times and let the software in the Moto X handle slightly variations automatically.
Mine wakes up all day sitting on my desk at work. I do talk about Google a lot, but I never say my phrase. It's funny some of the stuff I see it type...
Sent from my XT1060 using Tapatalk
This is an interesting thread for me. I had the Note 3 (hi galaxy) and Nexus 5 (ok google). Both of them would think I was talking to them when I wasn't, and I have almost the opposite problem with the Moto X. I have a hard time to get it to listen. I re-trained, re-trained, re-trained.. My wife's phone works flawlessly. I do love that we train our voices because she uses here touchless control all the time right next to me and my phone has yet to mistake mine for hers.
Maybe I need shorter arms.
OK quick update, I uninstalled the Touchless Control update and retrained my Moto X again in my garage this morning. It's been about 7 hours and it hasn't once yet turned itself on. I streamed music, have been in congested areas with people, a business meeting and it's working perfectly now.
I'm going to wait for 24 hours to make sure it's still working correctly and then install the update to the app.
About ready to scream!
The touchless control on my Moto X Developer Edition is extremely sensitive. Anytime anyone talks in the office that I work in, the dang phone comes on and waits for someone to give it a command. All anyone has to do is say "OK" and it does this even when I don't want it to. I've tried retraining the phone multiple times and it doesn't seem to help me out at all. I'm going to be so glad when the Lollipop update finally rolls out for this phone so I can get retrain this with a different launch phrase that will not be so easy to trigger on my phone. In the meantime, has anyone been able to get the sensitivity adjusted on this phone? If so, how? I'm thinking of going to Cyanogenmod 12.1 until Lollipop rolls out for the XT1060,
Any help that I can get on this would be greatly appreciated.
Cindy
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
kcraptor82 said:
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
Click to expand...
Click to collapse
First off I'll say that ML2 had been known to be buggy. For your first problem, did you make sure Glove Mode is disabled? For your second problem I have no idea. Sorry I can't be more helpful.
If it is in fact stock, do a software update to KitKat and it should fix your stability issues. I can't because of root.
I have owned pretty much every Galaxy phone so far and though I've loved each one, there's a few completely annoying issues that I end up having solve through a custom ROM, launcher, a developer script, or something along those lines. I thought for once with the Note 4 I would be able to for once keep everything stock besides having it rooted but it looks like I was wrong.
The issue I'm having right now is driving me through the wall. My phone answers phone calls AUTOMATICALLY ON ITS OWN when connected to BLUETOOTH.
It happens consistently, the exact same way, every single time. When I'm connected in my car it answers after exactly 2 rings (2 seconds). It is getting ridiculous and sometimes I just want to toss the phone out of the window while I'm driving down the freeway. Its extremely annoying to have your phone answer a call that you absolutely no intention of answering, ESPECIALLY WHEN I'M DRIVING. I'm tremendously busier in the past year and don't have time to sit and tinker like I used to or I'm sure I would've either solved this or gotten a new phone by now.
I already made sure auto-answer is OFF: Settings > Call > Call Accessories > Automatic answering [Box is not checked]
THIS IS DEFINITELY AN ISSUE WITH THE PHONE BECAUSE IT HAPPENS ON ALL 3 OF MY CARS & 2 OTHER CARS I'VE TRIED.
Please, if anyone knows how to fix this issue or anything about this completely ridiculous issue, please share.
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!
My phone randomly talks something about the time, I'm not getting what she saying (woman voice).
Talkback option is off, I checked that one.
What is this, this is so annoying and creepy.
This is not the first bug, since I bought this phone.
Anyone can help me?
Something put into clock settings?
I found this similar problem, I have exactly the same:
"A couple days ago I started hearing a womans voice at random times, like I had butt dialed someone, but I could Identify where it was coming from. Then while I was scrolling on my phone I hear something something "time". Finally in the middle of the night when everything else was quiet I hear it clear as a bell. A robotic female voice saying "it is time". No notification. No background apps running. I've done a few things to check those things and can't find anything. It is slightly annoying. But more so, creepy AF. Any help would be appreciated."
It's Big Brother sending you subliminal messages
Don't see what it could be other than a notification related thing...something you already forgot that you enabled. There are SO many settings, I doubt I could bring my phone to the same exact config after a factory default.
Try using the notification history feature to track this ghost down.
This sounds like an accessibility setting turned on to me
mpore14 said:
This sounds like an accessibility setting turned on to me
Click to expand...
Click to collapse
Ah, yes. That must be it. Good thinking.
I'm betting that you will find the culprit in Bixby Routines. It's under Advanced features.
your question is your phone talks about time, for that u will have to search on google ..
I tried everything, but couldn't helped. I did a factory reset. I always hate to do that, because It takes to much time to put back everything and set up, but at least it helped.
Thanks to everyone.