Ever since installing the September update I have had troubles with Bluetooth connecting and staying connected to my Galaxy Watch 3 and my hearing aids. Everything worked flawlessly until that installation. Is this a known issue or has anyone else observed this?
Quite the opposite for me, this update has made my phone more reliable to Bluetooth connections.
My BT headphones disconnect all the time. I think my Fitbit does too
With A13, the Bluetooth stack used by Android was changed. I saw some issues early on (problems pairing, needing to forget and repair, pairings simply disappearing), but after redoing some pairings, things seem to be getting better. Still some odd stuff, like impossible options enabled (like "Input Device" and "Contact Sharing" on speakers without that capability).
It's obviously a work in progress.
As mentioned above by Mike, I did also do a fresh start no restore for Android 13 since I thought I was having issues with other things that was really annoying me with android 13 after upgrading to that, all the problems that caused me to fresh start were still present but almost all of these have gone after Sept update
Related
After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.
I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.
I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d
I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).
If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.
Bluetooth cuts in and out when connected to 2 devices (car's "phone" and "media")
I have a GSM Galaxy Nexus on stock Jellybean, and bluetooth streaming works great in my car (Chevy Sonic) until I also connect the "phone" connection. When it's connected, the music cuts in and out constantly. Phone calls seem to do the same thing if "media" is connected.
If I kill 1 connection, the other works great. Is this a Galaxy Nexus problem or Jellybean? I've tried stock, franco's, trinity, etc kernels but I'm guessing this won't matter (since the source was JUST released for JB).
Does anyone else pair to multiple BT devices simultaneously? Do you have issues?
I just came from an iPhone 4S, and it paired nicely with both connections without them cutting out. I hope this is something I can get working because I use both functions all the time.
Thanks!
I connect to 2 devices in my truck and it actually seems to work better since installing Jelly Bean. On ICS I had a similar problem. My truck connects via the "phone" profile and I connect to a bluetooth adapter for the "media" profile. I could use either of them independently without a problem, but with both connected, my call quality was awful and my music would cut out periodically. I believe that the truck "phone" profile was disconnecting and reconnecting every couple minutes as I would see the display on my truck indicate that a bluetooth device had just connected.
Since installing JB, that behavior seems to have stopped. I can't say for sure as I haven't driven very much yet since installing it, but early testing seems to indicate the problem has gone away. I know this doesn't help in your situation, but I did want to share my experience as it was similar to yours.
My Pixel XL is having a hard time connecting to my car's Bluetooth (Mazda 3). I had no problem pairing, but connecting seems to be hit or miss. Once it connects, things seem to work fine. Any advice?
My advice is get used to it. Not being mean saying that, its just that Android bluetooth has been hit or miss for a long long time now. Some will work well with some devices and some will not. And it will change every once in awhile after an update.
Toss a Bluetooth toggle on your home screen
Aqua1ung said:
My Pixel XL is having a hard time connecting to my car's Bluetooth (Mazda 3). I had no problem pairing, but connecting seems to be hit or miss. Once it connects, things seem to work fine. Any advice?
Click to expand...
Click to collapse
If you're not on the latest security update, I'd suggest that you install it. Older GM vehicles had an issue connecting to BlueTooth. It was resolved with the December 7.1.1 update.
cam30era said:
If you're not on the latest security update, I'd suggest that you install it. Older GM vehicles had an issue connecting to BlueTooth. It was resolved with the December 7.1.1 update.
Click to expand...
Click to collapse
Yes, I am currently on 7.1.1.
Is there an official Google PixelXL forum where I can voice my concerns so that Google/Pixel people come in contact with my grievances in a more direct manner?
Thank you!
Aqua1ung said:
Is there an official Google PixelXL forum
Click to expand...
Click to collapse
Here > productforums.google.com/forum/#!forum/phone-by-google
I think I've noticed a pattern that might be relevant for this issue: After rebooting, connection happens pretty much instantly. It gets gradually slower everytime i connect afterwards, until the A2DP profile stops connecting altogether, after the 4rd or 5th connection attempt. Rebooting the Pixel resets this cycle.
Interestingly, these connection issues happen only with my Mazda car. No other BT devices have problems connecting to the PixelXL, which makes me think that this might be a Mazda issue rather than a Pixel issue. But then again, I had no such problems when connecting my Mazda to my Galaxy S6. Not sure what to think.
http://www.androidpolice.com/2017/0...-random-bluetooth-disconnects-pixel-pixel-xl/
Just got a Robin to replace a N5X that was killed while on vacation in MX. The bluetooth pairs just fine the first time to all four of the bluetooth devices I routinely use. Despite them now being listed in 'Paired Devices' none of them will automatically connect to the Robin. Each acts as if its the initial pairing again, asking to be included as a trusted source, and the device being connected to requiring a confirmation on the pairing. And even then getting them connected again has about a 50% success ration (if that). The N5X never had issues automatically connecting to the same four devices. Is this a known bug and is there any work around?
***UPDATE***
Well, nothing I've tried could make bluetooth work properly on stock 7.1.1. Deleting all paired devices, factory reset, you name it. Fed up, I decided to flash Omni Rom and now bluetooth works as well or better than any device I've owned. As such, it's definitely a software issue with stock 7.1.1.
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Daimonion1980 said:
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Click to expand...
Click to collapse
Have tried different ROM's on this Pixel 3 XL so I completely understand the Bluetooth issue. Have grown to rely on turning off Bluetooth before using the passcode; kind of helps with the new ViPER4Android FX,
Since using ScorpionROM, haven't had any Bluetooth issues. Maybe give it a shot and see if it helps