Related
Sometimes my Moto will recognize my voice as I'm saying it an execute the command quick, like I think it should all the time.
Sometimes I'll say something and it'll take forever, and sometimes completely fail. I can then open my phone and do a voice command with immediate results, so it's not my connection.
I removed commander and autovoice which seemed to help some at first, but I'm not sure it made a long term improvement. Removing some apps I didn't use from the watch also seemed to help some, freeing up RAM.
Is too much of the voice processing happening on the watch instead of the phone? Or is there a bluetooth issue? My S4 processes voice very quick almost always.
Anyone else experiencing this? I can't seem to find any time this does it more than others. Quit or loud room, doesn't seem to matter.
Any suggestions would be a great help. I use the moto for voice commands a lot and it defeats the purpose of not pulling my phone out when it takes so long.
ThePublisher said:
Or is there a bluetooth issue?
Click to expand...
Click to collapse
That one.
My old, decrepit galaxy s2 has what you describe but worse, sometimes phone bluetooth just turns off and can't turn back on... but mine is probably broken and dying.
Try re-pairing, cycling bluetooth on phone, or changing roms to one with a better bluetooth stack
If your S4 processes it fine, then it certainly is the connection between it and the watch. If cycling the antenna doesn't work try resetting either device, and if you're running a custom ROM check its dev thread for any BT related issues.
Going to try flashing an updated ROM. Currently on GoldenEye NB1 and going to update. I will let you know if this fixes the issue. Thank you two for your help.
Problem fixed
So I deleted the 360 from my phone's bluetooth. Then reset the 360. Upon reconnecting this time it worked great and has been excellent in recognition for a couple days now. Not sure what the difference is now, but it kept me from flashing my phone.
If I try to navigate from the Zenwatch, the phone brings up google navigate even if the phone is sleeping. I would think that might be an issue in a pocket, but that's not the biggest issue.
The destination seems to get set correctly but neither the phone or the watch continues to navigate. They both seem to lock up.
Subsequently any other Nav app (I hope Waze gets Wear support soon) is unable to navigate as they are unable to get GPS lock. Looking at other GPS helper apps shows zero sats in range. Stopping/Restarting location services doesn't solve the problem. Only resetting the phone does.
Maybe it's just me. Sprint HTC One Max, stock. Anybody else?
I noticed this the other day when I was testing out navigation for fun. Once I took my phone out of my pocket, it seemed like it was able to get a lock again and things went more smoothly. I know gps can be a bit sensitive sometimes and maybe having it right next to your leg like that blocks the signal?
When the problem (GPS lockup) manifests there is nothing that will get it going other than a phone reset. I normally have my phone in a holder high on my dash where gets good reception, but when it gets in that state, not even one satellite shows a hint of a signal. Today I even made sure to stand outside holding my phone up in clear sky just to be sure.
Even if I don't access nav Google maps or Micro Maps from the watch it still locks up at some unknown point. I normally keep GPS on all of the time and have a number of apps that store locations from time-to-time. When I get in my car, Waze automatically starts but I can't get any sat signals until I reset my phone.
I'm experimenting with a theory that another member brought up in a different thread that there may be a connection with using a watch face that also includes weather and the number of GPS requests it makes. I've changed to the basic face that is in all of the marketing photos and continuing to test. I guess my next step will be to leave the watch at home :crying: to make sure that something wonky hasn't happened with the phone itself.
Are there any other frequent GPS users out there that can confirm or haven't experienced the problem? It doesn't seem to matter if you use the nav functionality on the watch.
The updates this morning seem to have fixed the problem.
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.
I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.
Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.
Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk
I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently
I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.
I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!
Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.
BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.
I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.
Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.
I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol
Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
gadgetgaz said:
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
Click to expand...
Click to collapse
No fixes but same problems here
I'm having the same issue also very frequently with WiFi dropping all the time. These two reasons are linked from what I been told. Google telling me to RMA. The pain of that
Mine has done this with my Gear S3 watch since I first got the phone a few months ago, it had me seriously considering returning it for a while. Sometimes it would just disconnect from the bluetooth, but often it would unpair causing me to have to go through the whole set up process again. It did this on Android O, various DP builds of P but so far (touch wood) has been good with the latest version of the Samsung software and Android P.
I'm having the same issues as well and currently searching for answers.
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger?
I'm having the same issue with the fingerprint sensor. The only workaround I've found is to reboot the phone, then it will start functioning again for a little awhile. Very bizarre.
I also recently started having issues with the fingerprint scanner. Since a lot of people have this issue I'm starting to think it is software related.
andygold said:
My LG G7 is a Verizon Wireless model that is not rooted. Over the last few weeks, the fingerprint sensor has been working only part of the time. Mostly, when I hit it with the phone locked, it will do nothing. Then I push the power button to get the screen to light up, and it leaves me at the knock code screen. 95% of the time, the fingerprint sensor will work at this time (yes I know I need to use the knock code when I boot the phone, before the sensor will work). A couple of days ago, the sensor would not work at all, so I went in and deleted some stored fingerprints. When I tried to enter new ones, I instantly got a message on the screen telling me the sensor was not working and to contact a customer center.
So, I did a factory reset and set the phone up as a new phone, figuring some setting was wrong, or an app messed with things. No luck. Still a partially working fingerprint sensor. Strange thing is, I then booted into safe mode and the sensor works 100% of the time. In regular mode though I may be able to wake the phone 5 times in a row, and then for the next 10 times nothing.
A short time after these issues started, I started getting a WiFi issue in that my phone will not connect to my work's "Public_Access" WiFi. It connects up to my home WiFi, and other WiFi, but not at work anymore. My tablet connects at work, and everyone else's phone connects, but not mine. I get a "Obtaining IP Address.." message, and every once in a while it will flash the word "Saved", but no luck in connecting. Signal strength is "good" to "excellent". Link speed is normally around 144 Mbps or higher, frequency is either 2.4 or 5Ghz, and security is "None". None for proxy, and I'm DHCP. If I go to static settings, the IP and gateway look like numbers from home.
Anyone else having these issues? anyone found any workarounds?
Click to expand...
Click to collapse
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
OnceAMatrixMan said:
By any chance are you using VZW Messenger? It was an update to VZW Messenger that caused the issue for me. Next update resolved it.
Click to expand...
Click to collapse
I do have Messenger on the phone. It is NOT set as my default messaging app as I do not like it. Only reason I have it is because too many of my colleagues send me messages through it, which I can't open any way else that I know of. I'll look for an update and see if that helps. If not, I'll delete it and check again.
Thank,
Andy
Last update to Messenger I have is from April 9th. I looked for a more recent update but no luck.
Just deleted Messenger, and rebooted. After the initial need to enter the knock code, I slept the phone by tapping the power button (sorry if my terminology is off). 4 different fingers then and no joy (from the sleeping phone). If I hit the power button, the screen lights up and leaves me at what I guess is the lock screen showing recent email and calendar events. From there, I can successfully (still about 95% of the time) use the fingerprint sensor or the knock code to unlock the phone. But from a screen-off, sleeping mode, the fingerprint is still in a maybe it will work, maybe it won't situation.
If I have the same problem for about two weeks approximately install youtube vanced and yowhatsapp I do not know if it will be that but it is very annoying I hope lg update soon but I do not think I have the Indian version
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
redbar0n11 said:
Have same model and had same issues. I recently found out that I was missing 3 updates. December update started these issues. I'm now on the 10j version and so far haven't noticed the issue. But it's only been a day or so.
Click to expand...
Click to collapse
I am also on 10j, and the issues are still there in regards to the fingerprint sensor....although for some unknown reason, after weeks of no WiFi at work, my phone finally decided to hook up to my work WiFi yesterday afternoon, and this morning when I got into work it instantly hooked up to it again. So, hopefully the WifI issue has been rectified. I guess I should somewhat count my blessings as WiFi is more important to me than fingerprint sensor, in the big scheme of things!
There has to be a software/firmware issue going on though as the sensor seems to be most troublesome when the phone is sleeping. Once the lockscreen is on, although there are still issues, it works 95% of the time. That makes me believe it's not a hardware issue.
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
My G7 EAW is the same, fingerprints flicker. However, I removed the back cover and corrected the fingerprint, and it worked normally
netookska05 said:
I have Verizon also. It may help if all of you download the latest kdz for Verizon and reflash it vs factory reset. Using the lg up method by lamemonster. I do it all the time when I cross flash kdz as well as flashing back to Verizon. Hope this helps.
Click to expand...
Click to collapse
can you link to or specify that exact flashing method? nothing works for me, second piece of new hardware, no results.