Related
I've been having a weird experience with my Moto 360. I listen to music from Spotify or Google Play Music in my car (Audi) over Bluetooth every day and have done for months with every phone I've had - Nexus 4, Nexus 5 and most recently, my OnePlus One. Everything has always worked flawlessly - audio quality is good, no disconnections and generally perfect.
Now my Moto 360 is connected to my phone as well, it seems to occasionally "interfere" with the Bluetooth audio stream periodically. It's more pronounced when I lift my wrist and turn the watch to activate the display, but sometimes happens without this going on too. The audio starts to skip and jump as though there's not enough bandwidth to both communicate with the watch and the car. It usually lasts around 10-15 seconds and is very frustrating. If I put the watch in airplane mode, the issue goes away, but it will restart when I take it out of airplane mode. I've had some success with disabling and re-enabling Bluetooth on the phone to force reconnections, although there is still occasionally some interference after this too. It doesn't always happen and is usually worse in the evenings than the mornings - almost feels like after the watch has been connected to the phone for a long time, there isn't room for anything else to use the connection.
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
webvictim said:
I've been having a weird experience with my Moto 360. I listen to music from Spotify or Google Play Music in my car (Audi) over Bluetooth every day and have done for months with every phone I've had - Nexus 4, Nexus 5 and most recently, my OnePlus One. Everything has always worked flawlessly - audio quality is good, no disconnections and generally perfect.
Now my Moto 360 is connected to my phone as well, it seems to occasionally "interfere" with the Bluetooth audio stream periodically. It's more pronounced when I lift my wrist and turn the watch to activate the display, but sometimes happens without this going on too. The audio starts to skip and jump as though there's not enough bandwidth to both communicate with the watch and the car. It usually lasts around 10-15 seconds and is very frustrating. If I put the watch in airplane mode, the issue goes away, but it will restart when I take it out of airplane mode. I've had some success with disabling and re-enabling Bluetooth on the phone to force reconnections, although there is still occasionally some interference after this too. It doesn't always happen and is usually worse in the evenings than the mornings - almost feels like after the watch has been connected to the phone for a long time, there isn't room for anything else to use the connection.
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
Click to expand...
Click to collapse
My plantronics legend is multipoint paired to my HTC one max and a blackberry. Since getting the 360 I have noticed a crackle in the audio. If I reboot my phone I can usually clear it up. Seems like interference isn't causing Bluetooth channel hops like it should.
I am having the exact same issue. Moto 360 connected to LG G2 (Verizon) running Cloudy G3 ROM and every time I play a song to any Bluetooth device it stutters for the first 10-15 seconds of the song, then plays fine until the next song. It resolved for a bit when I re flashed, but started again a few days later. Can't correlate it to any changes or installs. Totally stumped.
This is a huge problem! I can't even use Google maps in the car if I have my moto 360 and phone connected to Bluetooth at the same time. I could not use moto voice or Google now as well. Even when my phone rings in the car my speaker crackles.
All this is cured as soon as I leave the car. It's obviously a big Bluetooth issue and moto needs to know about this! This thread should be pinned!
I am having the same issues with my Moto 360 and OnePlus One. It is very annoying and I'm seriously considering returning the Moto 360 now!
It's every phone that does this not just the OnePlus one. Also in my moto x. It's clearly linked to the moto 360 and it's Bluetooth issue.
Yes, that looks like the case and so I'm returning the Moto 360 before the 30 day return window expires!
I was experiencing this issue as well in my Q5. But after experimenting, I don't think it's actually interference with the Bluetooth radios. The issue only seems to happen when my phone is asleep and when it is happening, all I have to do is wake up the phone and it stops. I wonder if maybe the governor is causing the CPU to sleep too quickly after the kernel gets a wakelock from the Bluetooth stack. Oddly enough, the issue hasn't happened since I updated to KGW42R on the watch.
If you're still experiencing the issue, maybe try changing your CPU governor to performance (if supported by your kernel/ROM) just to see if you get any improvement.
Yep, experiencing this as well with my HTC M8 + Moto 360 on my Volvo.
I had intermittent stuttering issues with the M8 in the past, but now I could never get a flawless playback whenever I have the Moto 360 connected. Big problem..any solutions yet anyone?
Motorola probably has no idea about this problem. Can/does anyone know how to make them aware of this horrible bug?
stu5797 said:
Motorola probably has no idea about this problem. Can/does anyone know how to make them aware of this horrible bug?
Click to expand...
Click to collapse
I just contacted them about it in Live Chat and the person was completely dumbfounded, then cut me off. Going to try to call them tonight. Oddly, I didn't have the issue with My Nexus 4, but it did surface with my new Moto X, which was around the time of the most recent update to the 360.
I have the moto x and the OnePlus one and this darn issue happens on both phones. So frustrating!
Bad audio issues
I have the same issue with my new Moto X, Moto 360 while using my car audio. I do have a fitbit as well so that means three bluetooth devices while trying to stream audio. Even music that is downloaded on my phone has the same issues.
I have the exact same issue with my Moto X 2014! Extremely frustrating.
Solution..connect your phone via 3.5mm jack (wire/cable) to your vehicle audio, to free up the frequency/frequencies..
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Yeah, unfortunately that's not a solution at all. My car doesn't have a 3.5mm input for me to use and besides, the whole point of Bluetooth audio is not to have any wires.
I agree that the issue seems to be present on either downloaded or streamed music. Sometimes disabling and re-enabling Bluetooth on the phone will help, sometimes it won't. Often I won't have any trouble when driving to work in the morning but will have constant interruptions going home in the evening. Sometimes it's the other way round. There isn't really a consistent pattern.
I tried to call Motorola support yesterday but they were closed.
I didn't have any problem with bluetooth at first, but now my car audio skips at random times and then goes back to normal. Feels like the '90s all over again. Additionally, sometimes my calls through the car will sound like I am underwater. I disabled the HTC bluetooth low energy profiles on my phone in hopes this will resolve it. Will test and report back later. Hopefully it won't have any impact on my phone's battery life.
Newest version of Android Wear came to my Moto 360 yesterday, and I was in high hopes that it would resolve this issue, at least to some degree. With the bluetooth updates it seemed like they made some serious changes, but the issue has gotten even worse. I can barely get any audio now, the skips are no longer short, and are now just 1-2 seconds of silence. I reported this issue numerous times to Motorola, and they refuse to respond to me. This is a huge letdown, and had I not passed my 30 days, I would return the device.
Official response from Motorola forums.
forums. motorola. com/posts/167e5af808?page=2
"We've spent some time looking at this. The team feels it's a matter of overloading the BT capacity of the phone. There is simply a limit to the traffic it can handle, and the extra link is slowing it down. Not a very satisfactory answer, but this seems to me a case where the simplest explanation is probably the right one."
Anyone know if the new Bluetooth LE changes in Android 5.0 would possibly improve this?
webvictim said:
Has anyone else experienced issues like this? I run nightly builds on my phone (which are otherwise absolutely flawless) and I've tried several different ones without any improvement. The 360 is on the latest OTA software update but had connectivity issues before that too. It's definitely the watch causing the issues as when it's nowhere nearby or is disconnected from the phone, there are no audio quality problems at all.
Click to expand...
Click to collapse
Oh my god.
It's exactly the same issue I have!
I turn on my 360 in the morning and connect to my alpine car audio, 90% of the time no problems.
I leave the office at 5pm, the watch has been connected the whole day, I notice lags in audio playback like whenever a new song begins for the first 5-10 seconds.
When my 360 stays on over night I get this issue in the morning too.
Putting the 360 in airplane mode solves it - but turning airplane mode off brings the problem back.
Restarting car audio, moto 360 and oneplus one while driving is a pain but works...
I also noticed that the lags occur more often when I turn my wrist (just like you said).
When navigating to the settings menu on the 360 while playing music it totally messes up the sound until I turn the display off again.
My setup:
Alpine CDE-178BT
Moto 360 4.4W2
OnePlus One 4.4.4 (Update 38R) Stock Kernel / Franco Kernel - same **** on both kernels
A bit of google told me that the problem can occur with every bluetooth LE device (like fitbit wristbands)
I hope this will be fixed but don't really know what the problem is... Bluetooth stack in ROM? Moto 360?
Hi guys,
I have a Galaxy S4 T-mobile SGH-M919 and it's Android 4.4.4 from Samsung (Original ROM) right now. I also have a Moto 360 Running the latest Android Wear 4.4w.2.
I encountered a serious bug.
So when my S4 is paired to my Moto 360, and if I am in a phone call, after a few mins (usually after 5 mins in), the sound would suddenly disappear. The other party whom I'm talking to can still hear me but I hear nothing. Complete silence.
When the sound goes off, I can just hang up and redial and then the call would be fine for a few mins before the same issue happens again. This is annoying.
I'm not sure if anyone has ever encountered this. I tried googling this and it seems no one has experienced the same issue with the same devices (Galaxy S4 T-mo and Moto 360). I've read that some people had similar issues with other bluetooth devices and their phones (or cars) and some say that it has something to do with my phone being connected with another device (in my case, the Moto 360) via bluetooth. I think when my Bluetooth is off, there is no issue at all.
If any of you has the same devices (Galaxy S4 T-mobile and Moto 360) and preferably the same firmware versions installed in both devices, give this a try. Simply connect your phone to your smartwatch and make a phone call. Try to wait for about 5-7mins into the call and see if if you experience this issue as well.
Is there a fix or workaround for this? This is ridiculously stupid. I should be able to make calls while my phone is connected to my Moto 360 as well.
Hi,
Recently I'm experiencing an issue with my Samsung Icon X headphones and my XL. I am on the 7.1.2 Beta build NPG47I. The phone connects with the earphones and I can change options via the Gear App but music will not play. It will not work with my usual Spotify App or another Mp3 player app that I use to play music stored on the phone. I have isolated this issue to the phone since the Icon X works fine with my wifes S7.
I can't say for sure but I suspect it started occurring around the time my phone updates to the 7.1.2 March Beta. I have tried reinstalling the Gear app. Factory resetting Icon X both through GEAR and holding the physical reset button on the headphones. Re-pairing the bluetooth connection. All to no avail.
I was wondering if anyone has had this issue and knows a fix. My next step is a factory reset on the phone but I'm hoping there is a fix before doing that.
Thanks
Hi all...need some help with Bluetooth issues on my pixel 2 XL. I updated to the official Android pie today and noticed that my jbl Bluetooth earphones are having issues with calls. I cannot hear anything thing from the other side and the person on the other side can only hear some weird distortion. However I tried playing music on it and it works fine. Issue is only with calls. Anyone else facing this? I tried unpairing and pairing it again, restarted the phone, tried safe mode too but no luck.
Also I had sound echo issues with wired earphones (connected through dongle) on Oreo so I bought the jbl Bluetooth earphones and the echo was gone...and now after updating to Android pie my Bluetooth earphones don't work
Please help!
wazza1991 said:
Hi all...need some help with Bluetooth issues on my pixel 2 XL. I updated to the official Android pie today and noticed that my jbl Bluetooth earphones are having issues with calls. I cannot hear anything thing from the other side and the person on the other side can only hear some weird distortion. However I tried playing music on it and it works fine. Issue is only with calls. Anyone else facing this? I tried unpairing and pairing it again, restarted the phone, tried safe mode too but no luck.
Also I had sound echo issues with wired earphones (connected through dongle) on Oreo so I bought the jbl Bluetooth earphones and the echo was gone...and now after updating to Android pie my Bluetooth earphones don't work
Please help!
Click to expand...
Click to collapse
I have no issues wtih LG HBS730 BT headphones on calls or music with Pie. I've had four calls total, incoming and outgoing. I listened to music for about five hours too, no glitches.
I've had issues with the anker brand ones.
I have the same issue
Having issues connectingy to my car Bluetooth which has always worked before updating. Also experiencing WiFi drops.
Edit: went to stock Pie unrooted, and not as many wifi disconnects but my phone doesn't even see my car's Bluetooth connection . Fitbit connects just fine though. Weird..
Android Bluetooth is flakey as hell. Everyone gets a turn with incompatibility. P fixed my car with the first Dev preview. On O it was crud. There is a massive ongoing thread about it.
https://support.google.com/pixelphone/forum/AAAAb4-OgUsiJeDphsoOJ4/?hl=by
I had the same issue on my pixel XL on dp4 and dp5. Bluetooth worked fine for music but only crackled a little bit for phone calls. Both headsets and car were affected. Troubleshot it with Google rep and they told me my phone was broken. I also had multiple sensors stop working so auto brightness was broken and auto rotate was also broken (And a few other features like tap to wake screen). I ended up buying a pixel 2 xl and sending the other to Google as a trade in yesterday. Now I'm wondering if it wasn't just the software. I actually reset the phone and everything worked for a day or so before it failed again. I then exited the beta and everything worked on 8.1 Oreo for about a day before it all broke again. At that point I concluded it must be the phone. Hopefully the software didn't burn something up. I'm going to be ticked if this phone starts giving me trouble.
Are there any troubleshooting steps I can follow to see if solves the issue? Because it only happens on calls but music seems to be fine.
You can try rebooting in safe mode (long press the power off icon when you press the power button). I will restart with only minimal apps to see if it's being caused by a non Google app.
nukeruss said:
You can try rebooting in safe mode (long press the power off icon when you press the power button). I will restart with only minimal apps to see if it's being caused by a non Google app.
Click to expand...
Click to collapse
I tried this on my device but even in safe mode i faced the same issue
Ever since upgrading to PIE, I can no longer connect my my pioneer appradio head unit.
Phone works, but media Spotify or Pandora does not
Having the same issue, also, my "disable absolute volume" in developer settings doesn't work. I guess this is what to expect for early adopters.
I have had no issues with connectivity to my bluetooth headphones or to my car's bluetooth
However I have noticed that twice when I had phone call before entering the car and I connect to the car's bluetooth and the call is transferred to the car's audio, I get disconnected for a couple of seconds (after initially connecting correctly) and then it automatically reconnects and call continues normally ..
Android pie broke bluetooth for calls
abidhill said:
I tried this on my device but even in safe mode i faced the same issue
Click to expand...
Click to collapse
Stock Pixel XL: All bluetooth devices worked for all purposes on Oreo. After updating to Pie none of my bluetooth headsets will connect for phone calls. Bluetooth music broadcasting to speakers is unaffected. I'm going to call them about it tomorrow.
williamgrahamiv said:
Stock Pixel XL: All bluetooth devices worked for all purposes on Oreo. After updating to Pie none of my bluetooth headsets will connect for phone calls. Bluetooth music broadcasting to speakers is unaffected. I'm going to call them about it tomorrow.
Click to expand...
Click to collapse
Are you having any other issues. My original pixel XL had the same issue show up on the beta but it also affected some of my other sensors as noted in previous post. I now have a pixel 2 xl with no issues whatsoever.
williamgrahamiv said:
Stock Pixel XL: All bluetooth devices worked for all purposes on Oreo. After updating to Pie none of my bluetooth headsets will connect for phone calls. Bluetooth music broadcasting to speakers is unaffected. I'm going to call them about it tomorrow.
Click to expand...
Click to collapse
Do let us know what they say
wazza1991 said:
Do let us know what they say
Click to expand...
Click to collapse
Well, they seem to think that the problem is an app from the play store that doesn't play nice with Pie. Frustratingly, the problem corrects itself sometimes (but not all the time) after a reboot. They had me reboot into safe mode and this time it worked. After 20 minutes our support call was over. 30 minutes later one of my three headsets (with the oldest bluetooth version) didn't work, but two of the three did.
The tech (Jen, who was super nice but sounded like she was overseas and had to repeat herself a few times for clarity) said they only have 2 support options for this issue: 1) boot into safe mode and blame one of the apps from the play store or 2) FACTORY RESET THE PHONE! Once I explained that the phone was my google authenticator she suggested that to further troubleshoot I should turn off two factor for my google account (Ummm, no thanks. And that is why you should always PRINT OUT the QR code and put it in a fire-proof box in case you need to recover it)
I'll post back if it breaks again, but right now at least I can live with it.
Only "issue" for me is my wife's ILX doesn't seem to update the music information anymore. With the betas it did for a fee songs then seemed to stop. Now it's nothing at all but will double check today since I only drive it on occasion. Other than that, playback on our cars, Bluetooth speakers and headphones has been just fine. Love that it remembers the volume set per each device. No super low or super loud volumes on the start of playback.
Sent from my Pixel 2 XL using Tapatalk
I also have Bluetooth issues with Pie when connecting to my car (2017 Audi A4 with MMI+) I never use Android Auto by the way:
- Music playback is flaky: I have to start Play Music before connecting to the car, otherwise it cannot stream anything. Sometimes even this doesn't work and I have to repair again. This sucks, you always have to spend some time to check if everything works!
- My Radar trap warning app blitzer.de only works when streaming Audio from the phone to the car, even though I set Audio to HFP. With Oreo, the app started a phone call, it looked exactly like an incoming call. Now it only adds the warning to the phone's Audio Stream, so when listening to radio or streaming from a HDD I get no warnings.
- Phone calls work flawlessly, though
Try removing or 'forgetting' paired device and add it back again. It worked with my AirPods.
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
I may not have the answer that you want to hear but I did find a temporary solution. There's an app in the play store nRF Connect that works. Slide over to bonded, put devices in pairing mode and hit scan and wah lah. Any questions I'll do the best I can to help.
I've noticed the same on my galaxy buds, but when I connect another pair of wireless earbuds that i sometimes use they connect as soon as i turn them on when Bluetooth is activated, without me manually having to go into the settings and do it. Not sure the reason for this. Would've thought the earbuds that's actually made by Samsung would be the ones connecting right away.
hotshot646 said:
Hi everyone,
I'm having a problem that I think shouldn't happen on this phone.
I'm stock with the latest January update on Android 10.
Info: this problem was present before the update to 10.
Whenever I connect any Bluetooth device (airpods, car, moto intercom ,etc) I have to manually unpause the music to get it to start.
This happens on every player (Samsung Music, Google Play, YouTube premium, etc)
This is the first Android phone I have that doesn't do this and that shouldn't be seeing it's top tier.
I've looked online and it seems that all Samsung phones have this feature and the only topics I get are how to disable it !?
Can anyone shed some light ? Is it happening to you as well ?
Thanks
Click to expand...
Click to collapse
Hej...
I don't if this would help You...
When I got the Note 10+ there's Was, out of the box on initial settings, active few Bixby Routines... and that, till i figure out this, was driving me crazy... When I turn Bixby Routines off everything back to normal...
Well I've had a similar problem. For me the issue is that it always autostart even tho I have BT autoplay unchecked in the car. If I have listen to any music, audio books, podcasts and turn them of when I exit the car, not leave them in the background, they will start playing even if the cars media system is offline.
Works perfectly with my wifes OnePlus 6, but not for me. Extreamly annoying to noticed that the audio book is playing after a 60min drive and I haven't heard anything..
I tried the app Tasker, it was a compleat waste of $4 for me anyway, didn't work, will try nRF Connect now.
I don't want to have BT of due to that I aways have my Jabra buds with me so that I can talk while driving if needed.