Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Sent from my Pixel 2 XL using Tapatalk
Have paired to 4 devices without any issues
No issues with pairing here either.
Recently I just read an article from Lifehacker about Bluetooth issues. Maybe it will help you: How to Fix Bluetooth Audio Stuttering
If the issue is still there, you should contact with support asking for a replacement.
TBarb169 said:
Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've had a few issues with connecting my 2XL. Pairing went find, but then wouldn't connect. I did a restart on the phone and all was well. This happened with a bluetooth speaker and then in my car (accord).
ame29 said:
I've had a few issues with connecting my 2XL. Pairing went find, but then wouldn't connect. I did a restart on the phone and all was well. This happened with a bluetooth speaker and then in my car (accord).
Click to expand...
Click to collapse
Well that worked! I feel ashamed that I didn't try rebooting...
Sent from my Pixel 2 XL using Tapatalk
TBarb169 said:
Well, never knew that Google was having issues with Bluetooth. My pixel xl was fine. Just got the 2 xl and here is what happens : I can pair my LG hbs-760 headphones but they don't connect. Shows them in the Bluetooth devices but that's as far as I can go. Same with my Bluetooth Panasonic headsets we have in the house. Will pair but will not connect. My pioneer car stereo will not connect either. Shows it paired and that's it.
Now I do have 2 devices which seem to be fine. I have Jaybird bluebuds x and a garmin approach x40. Both pair and connect.
Searching, but not finding any solutions except to wait for the November or December updates... My pixel 2 xl is still on the September update.
Any ideas?
Click to expand...
Click to collapse
This thread is a joke no problems here
evocalante said:
This thread is a joke no problems here
Click to expand...
Click to collapse
Thanks Captain Obvious! Please move along and troll some where else.
Sent from my Pixel 2 XL using Tapatalk
I've had Bluetooth issues with only one of my cars. The phone pairs, but then stutters on and off playing any audio. Eventually the bluetooth stack crashes. I had similar, though not exactly the same issues, with my Nexus 6p. Those were resolved by the October security update, which the Pixel XL 2 hasn't received yet. Hoping that resolves the problem again when it arrives.
Headphones/Truck have been fine for me but I have a gamegolf device which connects via bluetooth and every time I get a text or call while playing golf the gamegolf device disconnects. I'm still testing and don't know if it's a gamegolf issue or phone issue but it's annoying.
Related
I have a JVC head unit in my car paired up to my Galaxy S III, and no matter what I do (tried a different SIII, resets, different music apps, etc.) the Bluetooth drops when I go to skip tracks from the radio (AVRCP). I have been forced to go to the CM10 ROM to get a reliable connection (although I'm stuck on a build from about a month ago, as some Bluetooth bugs have introduced there as well). Anyway, I'm eyeing up the Note II, but I'm wondering if anyone can confirm/deny if the Note II (stock ROM) has a different Bluetooth driver than the SIII. I hate to say it, but I actually really like Samsung's new interface, but the Bluetooth issue I'm having is a deal breaker. The other question is if anyone knows if the 4.1 update coming out for the SIII will have the same BT driver as 4.0.
Thanks!
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Russ77 said:
had you ever flashed the KT747 kernel on the stock ROM of your s3? it changes the WiFi and Bluetooth drivers.
OR, if you haven't, maybe give it a try since it changes the WiFi and Bluetooth drivers.
Click to expand...
Click to collapse
I have not tried that. I would prefer to keep it stock, but that's something to try.
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
J-ROCK said:
I thought I was the only one with this issue. I can relate as well . I too have a JVC unit and also experience the same bug on JB TW Rom. It tends to disconnect after I skip a few tracks and reconnects again . It does F*** up the mood when jamming to your music. At the moment im trying a different kernel to see if it does the same. But like you said CM10 doesn't disconnect.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I emailed JVC on it, and they gave me the whole "did you try a reset" business... Infuriating. At this point I just want a stock ROM that works. My S & S II worked perfect on the same head unit...
How can you tell if the stock S III and Note II use the same BT driver? Oh, and let me know what your experience is with the new kernel.
It's a few more days until Jelly Bean is released. There are changes to the Bluetooth stack in Jelly Bean. I'd wait and give that a try before getting a new phone.
I had the same problem on my JVC receiver. Had the issue with Task's ROM too. Would happen when you skip through the songs fast. I switched to an Alpine deck and it still has slight issues but not as much. I also have an issue of it disconnecting and reconnecting right after I make a call. Hopefully Monday will bring a fix for us Canadians.
Sent from my SGH-I747M using xda app-developers app
Bluetooth has been messed up on the S3 from day one. I think it's an ICS issue because my gf's OneX has the same issues. I have a Mercedes B200 and I can't get sound through the car's speakers at all. Tried a bunch of different ROMs and kernels, including some JB (4.1) builds, all to no avail. I'm at this point waiting for 4.2.
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
nani4215 said:
I dont see any problems with my SG3 connecting my hyundai sonata car(2013 model) and honda CRV via bluetooth. No problems playing songs, phone calls and Google navigation.
Same phone didn't work with kia soronto SUV.
I feel the car bluetooth software has issues, not the phone software.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
It could be, but I've used a Captivate, Infuse, & S2 on the same radios (two different JVC decks), and they've all worked perfect. Those all had stock ROMs (to start). I flashed CM9 and then CM10 on the Captivate & SII, and they still worked perfect. The only phone (stock/not stock ROM) that has ever had problems for me is the S3. My gut tells me it's a problem with the Bluetooth stack on the stock ROM, seeing as BT on CM9/CM10 works perfect on the S3 (other than the bass-less sound bug on the "stable" release and after - nice "stable" release).
Somebody on XDA should start hacking the software on these touchscreen head-units (they are update-able :good, then I'll be impressed.
Note 2 BT
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
rytymu said:
Anyway, has anyone tried a Note 2 on one of the radios you had problems with? If not, I might try a re-post over in the Note 2 forum...
Click to expand...
Click to collapse
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
rytymu said:
Well I bought a Note 2, SAME DAMN PROBLEM! I'm 95% sure I'm returning it, the only other option is to buy a different head unit. Anyone else have a GS3 and an aftermarket radio that DOESN'T drop the bluetooth connection when skipping tracks?
Click to expand...
Click to collapse
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
mixxy said:
i have a kenwood ddx 418 and ive got no issues with bluetooth, best bet would be to go to a bestbuy and try out the display units there imho
Click to expand...
Click to collapse
funkydude101 said:
Bluetooth audio for music and calls works fine with my Ford Edge...however there is no track information (avrcp) sent to the headunit which is annoying. No change with the Jellybean update either.
Click to expand...
Click to collapse
But are both of you running bone-stock ROMs? If so, I may have to start looking at radios again.
Returned it. I guess that's a $35 experiment (thank you AT&T for the restocking fee). Either the Sammy BT stack is too advanced for my basic A2DP radio (as in ALL BT radios), or the Sammy BT stack is just horribly developed (which I've come to believe is true). Now I just have to wait for an apt-x head unit to come out, then I can try this experiment again...
Hey all I've had my 360 for a few months now and just started noticing a problem. When I have my watch connected to my phone my phone has a hard time connecting to my Chrysler Uconnect in my stereo. I can't tell if it's a phone problem, Uconnect problem or the watch. It'll drop connection from the car on and off and sometimes not connect at all. I'm pretty sure the watch stays connected the whole time. Once I disconnect the watch, the car connection works just fine.
Anyone else run across this?
These issues are seen with lollipop on phone....
or some people whose phone is moto x or one plus one
Sent from my SM-N910C using Tapatalk 2
It's a Bluetooth low energy issue. Same exact problems with my nexus 5 and my pebble, also exists with my nexus 6 and moto 360. It's very very annoying as it appears to be an issue with android itself somehow. I'm hoping with more Google engineers using wear and a nexus they'll get annoyed and finally fix it...
Sent from my Nexus 6 using XDA Free mobile app
i have no such issues with pairing a nexus 6 connected to a moto 360 in the ride.
i mainly use poweramp and the connection to the HU is a few seconds SLOWER than i noticed on the htc one max i used prior, but it connects and displays the music data on the ride with no issue. steering wheel buttons also work normally.
stock and not rooted. both devices.
It seems to be select car kid or a2dp devices. My car has the issue but not my Bluetooth speaker. So the Bluetooth device also matters somehow
Sent from my Nexus 6 using XDA Free mobile app
Never had the issue on my Samsung Galaxy note 2 even on any custom ROM... But had this issue when I flashed CM12 lollipop
Sent from my SM-N910C using Tapatalk 2
pakure said:
Never had the issue on my Samsung Galaxy note 2 even on any custom ROM... But had this issue when I flashed CM12 lollipop
Sent from my SM-N910C using Tapatalk 2
Click to expand...
Click to collapse
Were the other Roms aosp or TW? Maybe it's an aosp specific issue
Sent from my Nexus 6 using XDA Free mobile app
Just got a Moto 360 this week-end and in the car on the way home, my phone calls over bt to my BMW dropped repeatedly. Would connect and disconnect. Rebooted my phone, same issue. Did not happen with original galaxy gear. This is a deal breaker from me. My phone is a stock Samsung Note 4. No car phone issues with a Striiv Touch.
mjposner said:
Just got a Moto 360 this week-end and in the car on the way home, my phone calls over bt to my BMW dropped repeatedly. Would connect and disconnect. Rebooted my phone, same issue. Did not happen with original galaxy gear. This is a deal breaker from me. My phone is a stock Samsung Note 4. No car phone issues with a Striiv Touch.
Click to expand...
Click to collapse
Unpair them and pair again.
Sent from my SM-N910C using Tapatalk 2
I have an older TomTom Toyota Head-Unit on my Toyota Yaris, and it doesn't support Bluetooth Audio. But bluetooth phonecalls are working exactly as before pairing the Moto 360 to my HTC One.
I just disconnect my watch when I get in the car. Annoying that I have to do that.
So I have a Bose bluetooth speaker that I've been using flawlessly with all of my phones for the past few years.
Then Samsung pushed out its latest update, PHE. My bluetooth connection drops very frequently, and I have no idea what to do about it.
The connection has been dropping frequently even after I exchanged my Note 7 on Sunday. So to be clear, this problem has occurred on two separate Galaxy Note 7's.
Before Samsung's latest update, I was playing music on this speaker flawlessly.
Anyone run into a similar problem with Samsung's latest update?
Bump
I use 4 different BT devices, connections working fine
Guys, we've been discussing this in great length over in the Sprint Q&A. Here's the link. http://forum.xda-developers.com/sprint-note-7/help/choppy-bluetooth-t3445131
I've also posted a link to a youtube video where I've captured the lag...join in over there.
Just curious why Bluetooth on this phone doesn't display the streaming information across the radio (Uconnect if it matters). My sons s8+ does it as well as my previous Note 8. Just curious if theirs something I'm not doing right.
MHB1638 said:
Just curious why Bluetooth on this phone doesn't display the streaming information across the radio (Uconnect if it matters). My sons s8+ does it as well as my previous Note 8. Just curious if theirs something I'm not doing right.
Click to expand...
Click to collapse
I've got the same issue. Its not just you.
I'm connecting to a Honda bluetooth system, if that makes a difference.
After 8.1, it works better with my BMW at showing the data, but it's hit or miss. It also stops working if you switch music apps, so only the first one works.
Sent from my Pixel 2 XL using Tapatalk
It's because everyone implements Bluetooth items differently and there isn't a "standard" that everyone uses for even basic stuff. Since phone manufacturers implement things differently, device & car manufacturers also need to try and accommodate all the various implementations.
Sent from my Pixel 2 XL using Tapatalk
Well I'm still waiting on the Verizon OTA. But i definitely don't like the lack of info on the screen. I have the note sorting beside me... Test driving both... And send like such a simple thing.
imnuts said:
It's because everyone implements Bluetooth items differently and there isn't a "standard" that everyone uses for even basic stuff. Since phone manufacturers implement things differently, device & car manufacturers also need to try and accommodate all the various implementations.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Actually, for this kind of thing there is a standard called AVCRP, and the Pixel should support 1.4, but it seems to be the buggiest implementation ever since Android 7
Sent from my Pixel 2 XL using Tapatalk
I've noticed in developer options there are numerous settings for Bluetooth... Should i change these for display information?
MHB1638 said:
I've noticed in developer options there are numerous settings for Bluetooth... Should i change these for display information?
Click to expand...
Click to collapse
Try adjusting the AVRCP version.
Sent from my Pixel 2 XL using Tapatalk
I have the same issue connecting to a Honda. For what it's worth, it never worked with my 6P, either.
Devhux said:
Try adjusting the AVRCP version.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Nothing worked. Just don't understand this, everyone else does it, why can't Google!
Has anyone been able to connect wirelessly to the Android Auto in their car? I have a Honda CR-V 2017 and it connects with the USB cable, but not wirelessly. I have tried all settings multiple times but cannot figure out why it won't connect. I was under the impression that Pixel 3 XL phones had this capability. Can anyone share if they have it working, particularly on a Honda CR-V 2017. If so can you share your settings?
Sent from my Pixel 3 XL using XDA-Developers Legacy app
I have a 2018 crv and 2018 accord and I didn't think that could be done. I connect with usb on both.
Eudeferrer said:
Has anyone been able to connect wirelessly to the Android Auto in their car? I have a Honda CR-V 2017 and it connects with the USB cable, but not wirelessly. I have tried all settings multiple times but cannot figure out why it won't connect. I was under the impression that Pixel 3 XL phones had this capability. Can anyone share if they have it working, particularly on a Honda CR-V 2017. If so can you share your settings?
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
The wireless connection is a car feature not a phone feature. Very few makes support at the moment
micks_address said:
The wireless connection is a car feature not a phone feature. Very few makes support at the moment
Click to expand...
Click to collapse
I guess I thought most new cars which have Android Auto would be able to connect wirelessly. I thought it depended on the phone model instead.
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Eudeferrer said:
I guess I thought most new cars which have Android Auto would be able to connect wirelessly. I thought it depended on the phone model instead.
Sent from my Pixel 3 XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
It depends on both, really. The phone and car both have to support it. Phones (like the Pixel 3/XL) have the ability now, but very few head units (especially OEM from car manufacturers) support it. A few aftermarket units are starting to get it, but it's still very few.
I bought a Kenwood HU that has wireless AA and to be honest I'm disappointed. It works half the time and usually I end up just plugging it in cause it's quicker than messing around with my phone trying to get it too work
I have a pioneer 4400nex and wifi Android auto works flawlessly. Love it.
MoeDaddy said:
I have a pioneer 4400nex and wifi Android auto works flawlessly. Love it.
Click to expand...
Click to collapse
I have the 8400nex and it works well too and I used the cars speed signal to control the volume and the screen works well. The Kenwood screen was not sensitive enough and had dust under the screen and had trouble connecting but it did auto switch between the front and back camera when backing up and then driving forward. Not a big deal but cool. Both the new ones got rid of the camera mirroring and backup lines that the pervious units had. Can't win but overall the Pioneer is better.