Database Develop

Touchless Control WAY Too Sensitive

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

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.

Bluetooth Constantly Becoming Disabled

Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28

I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.

Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.

Post deleted

Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL

Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?

I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.

As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk

I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).

Don't google test their sofware?
This is a poor show by them.

Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?

Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.

danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?

@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk

I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.

@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once

semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!

semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
Thanks

Cannot get Ok Google to work after Wear 2.0 upgrade. Anyone else?

So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!

Having that same issue. Not only does not "Ok Google" work, even after enabling it in the watch's settings, even when pressing down the crown, the whole thing is extremely slow. Furthermore, for sending a message, the "Ok" doesn't time out after a couple of seconds in order to send the message automatically. It requires me to tap the screen.
All in all, its looking more like a downgrade for me. The whole system feels sluggish and incoherent from a usability standpoint of view.
Edit: Didn't factory reset the watch after update

I have an another problem. Google Assistant isn't launched in Czechia yet and there isn't Google Now in Android Wear 2. So, I lost any speech control.

I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?

Mr.Caution said:
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Click to expand...
Click to collapse
So another issue is that even after going to the stupid settings where you actually have to enable Ok Google from any screen on your watch, it STILL wont work. I can only get it to work by using the power button which has a huge delay and then only when I am connected on Wifi. For some reason it no longer works when on my normal cellphone connection.
The phone is super laggy, battery dies fast...its a MESS.
Basically my watch is useless now for all the things I need it to do daily

Mine only works if i go and disable Bluetooth and enable WiFi else it complains it can't contact Google. Play store is the same too. Slow lagging assistant is not good especially sending txts with no auto send
Sent from my Moto G (4) using Tapatalk

Same issue here. "OK Google" is the most important feature...

You need to give permissions for the OK Google to work. Didn't notice about it until I read this thread (I think most particularly Phone access)

shaolin95 said:
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Click to expand...
Click to collapse
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.

venzislav said:
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
Click to expand...
Click to collapse
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3

shaolin95 said:
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
Click to expand...
Click to collapse
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?

venzislav said:
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
Click to expand...
Click to collapse
I want to find out as its annoying to see the upgrade message over and over

shaolin95 said:
I want to find out as its annoying to see the upgrade message over and over
Click to expand...
Click to collapse
Pfff this 2.0 is a big s**t !!!

Doesn't lag on mine using the 2 core or 4 core kernel

almostthere said:
Doesn't lag on mine using the 2 core or 4 core kernel
Click to expand...
Click to collapse
Does OK Google work with voice commands and when not connected to Wifi???

shaolin95 said:
Does OK Google work with voice commands and when not connected to Wifi???
Click to expand...
Click to collapse
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)

almostthere said:
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
Click to expand...
Click to collapse
Would you look at that! It works but WTH is google making it so complicated now for users? Most people dont hang around XDA to know these things. Like for instance apps now need to be downloaded on the phone as its not autmotically done, etc.
Really weird approach.
Thanks for the tip!

After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.

Isham.padron said:
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Click to expand...
Click to collapse
Responses time is horrible on the initial due to it running on single core at lower clock speeds and on conservative core governor.
Therefore you'll have to give it sometime for it to settle down or if you can't deal with it, you'll have to unlock the bootloader and flash in the dual or quad core enabled kernel file
Running in quad core kernel, battery life seems decent and response real snappy

Well that's just stupid because it worked fine on the previous android wear build. This is dumb on LG's part.

Bluetooth audio playback issue due to wifi?

Hi Everyone,
Recently started having an issue with my moto g5s plus. Ill be playing audio over bluetooth to any of my various bluetooth speakers / car then all of the sudden audio will stop being transmitted to the device and it will start coming out of the phone. One way to solve it is re-do the pairing which is a no brainer as to why that "solves it". But another way is to turn wifi off, wait a bit, then turn it back on and walla, audio stops playing out of the phone and goes back to the bluetooth device that was never disconnected!!?!?!
This is REALLY odd, has anyone else had this issue, if so what was your solution.
Latest 7.1.1 android with June 1st security update (NPSS26.116-48-18). The issue has started within the last few weeks, doesnt matter what audio app (pandora / play music etc) and doesnt matter what bluetooth device it is hooked to. Wifi Location scanning has been turned off, same problem.
WHAT TO DO!??!

no one

This is happening to me too this is so annoying as I use phone for car audio. I re did the pairing but no luck. And I have had huge Bluetooth battery drain too.
So tempted to flash custom rom as its taking so long for Oreo or even a security update 4 months behind here in NZ for security

right, im in the same boat. I dont know if it was the security update with the June 1st security update (actually i know it wasnt this as i have been running this for a long while without issue). So this begs the question what the hell changed to make it start popping to speaker audio when listening to bluetooth audio and wifi disconnects?!?!

It's been happening to me since I got this device, and it also happened on my older Moto G3, it's a ROM optimization problem as far as I know. If I'm not mistaken, the Bluetooth and WiFi chips are the same, and the ROM does not handle pretty well both active connections at the same time. Custom ROMs seem to do this pretty well, so if you really want to fix this I suggest you install a custom ROM, or maybe wait for the Oreo update and see if that fixes the problem.

I have had this phone since it came out over a year ago. This issue has just started to happen within the last month or two. My vehicle, wifi at home and work, bluetooth devices i hook to in and around the office and home have not changed.

Yay oreo has landed in new zealand lets see if this fixes the problem

williamsjp said:
Yay oreo has landed in new zealand lets see if this fixes the problem
Click to expand...
Click to collapse
yes no maybe so?

Oh it did fix the problem it's like a new phone

williamsjp said:
Oh it did fix the problem it's like a new phone
Click to expand...
Click to collapse
.... question is how much longer do i have to wait to get freaking oreo here in the USA.

That's not cool I thought we were behind here

nd4spdbh said:
.... question is how much longer do i have to wait to get freaking oreo here in the USA.
Click to expand...
Click to collapse
I got it today, I'm on retus channel. I'll test the Bluetooth and report back if the problem is solved.
UPDATE: Problem still there.

Others are claiming that updates are starting to roll in for retus. So hopefully your wait will get shorter.
Moto G5S Plus XT1806, Liquid Remix v9.1.4 ROM, MultiROM, XDA Legacy

Just got notified this morning on my phone. Downloading as we speak with fingers crossed.
also...
FREAKING FINALLY getting oreo.... bout a year late.

Update, looks like it solved the issue!!!! THANK GOD. that was annoying as hell, lets hope it stays fixed.