I've been having issues pairing/connecting to one of my bluetooth devices. I currently have 2 devices paired with my phone and they work flawlessly. The third device worked fine for about a month before it stopped connecting. It was still listed as a paired device, however it would not auto-connect nor manual connect (it would flash connecting for a second, but that was it).
My next step was to unpair and try and start from the beginning. If I unpair and try to pair again, it will say "pairing..." indefinitely. Afterwords, I will toggle bluetooth and the device appears again as a paired device, but I am still not able to connect. I've also tried unpairing and toggling bluetooth, but as soon as it comes back on the device is still listed as paired. I've also tried rebooting the device, but the results are the same.
For the record, I was able to pair and use the trouble device with an Evo without issue. I was also able to unpair from one of my working devices, and pair again with no problems. I'm really at a loss as far as what to do short of formatting the device. Does anyone have any other ideas I could try?
Thanks
I sometimes get the same problems but there's nothing we can do about it. DK28 is a beta build that's bound to have problems.
I get the same problems occasionally. DK28 is known to have several issues with Bluetooth.
Is there any way for you to do a hard reset on any of the bluetooth devices?
I know I had to do this with my Jawbone Prime for my Epic.
I also have a big issues with the bluetooth pairings.
Can't pair any device, actually
But I have a backup data with all my pairing bluetooth devices. I've made that backup from 2.1 Eclair. I can restore it, but it is old backup. So, when I've tried to backup all of my bluetooth pairings with the Titanium Backup I can't restore it with the new data. That is very interesting because I can see all of my bluetooth pairings backups after I'm restoring the new data but there is no restore button. I can see those backups but I can't restore it.
Can somebody give me the Idea what to do and how can I make bluetooth pairings?
Help me, please?
Thank you!
antila said:
I also have a big issues with the bluetooth pairings.
Can't pair any device, actually
But I have a backup data with all my pairing bluetooth devices. I've made that backup from 2.1 Eclair. I can restore it, but it is old backup. So, when I've tried to backup all of my bluetooth pairings with the Titanium Backup I can't restore it with the new data. That is very interesting because I can see all of my bluetooth pairings backups after I'm restoring the new data but there is no restore button. I can see those backups but I can't restore it.
Can somebody give me the Idea what to do and how can I make bluetooth pairings?
Help me, please?
Thank you!
Click to expand...
Click to collapse
I had some bluetooth problems as well when on some of the current EXT4 ROMs.. i have reverted back to RFS and an older ROM build and things work better.
Guys, I would seriously try looking up a way to do a hard reset on your bluetooth devices. I had to do this with my Jawbone Prime earpiece with my Epic running Quantum 2.7.0. I have it converted to ext4 via cwm3 and it works fine. I would suggest giving it a shot. The worst that can happen is you still have an unpaired bluetooth device.
For my Jawbone Prime I had to do a specific pattern of hitting the talk and Noise Assassin buttons. It paired up immeditately with my phone. You may have to do similar with yours, depending on what you have.
Sent from my SPH-D700 using XDA App
samuraiinblack said:
Guys, I would seriously try looking up a way to do a hard reset on your bluetooth devices. I had to do this with my Jawbone Prime earpiece with my Epic running Quantum 2.7.0. I have it converted to ext4 via cwm3 and it works fine. I would suggest giving it a shot. The worst that can happen is you still have an unpaired bluetooth device.
For my Jawbone Prime I had to do a specific pattern of hitting the talk and Noise Assassin buttons. It paired up immeditately with my phone. You may have to do similar with yours, depending on what you have.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I installed a brand new Parrot MKi9200 in a van for one of my customers. This parrot piece would pair with my phone but not connect. This was running an EXT4 version of Bonsai. I grabbed my boss' Fascinate (stock 2.1) and it paired up just fine. I went back to an RFS only version on my phone and it paired perfectly.
Also as was previously mentioned, resetting your bluetooth device after a ROM flash can help with connectivity issues.
I think I found a fix for the pairing issues on DK28+
I had to turn off bluetooth, the adb shell, su, go into /data/misc/bluetoothd/ then I renamed/added _ to the file there. "mv xx:xx:xx:xx:xx to xx:xx:xx:xx:xx_" (which should be the MAC address of the phones bluetooth radio)..
Then turned back on bluetooth.. And that fixed pairing. Good luck.
darkfire79 said:
I had to turn off bluetooth, the adb shell, su, go into /data/misc/bluetoothd/ then I renamed/added _ to the file there. "mv xx:xx:xx:xx:xx to xx:xx:xx:xx:xx_" (which should be the MAC address of the phones bluetooth radio)..
Then turned back on bluetooth.. And that fixed pairing. Good luck.
Click to expand...
Click to collapse
This worked for me.
Related
I've come to find out I'm not the only person that has a panasonic kx-th1212b telephone in my home. I use this to link my cell with the house phones after work. I just recently rooted my phone and put on the vanilla new sprint leak modified by damage to keep root access. This rom paired but did not connect to my phone. I'm going to try fresh 2.1.1 today when i get home but I am assuming this is the same issue since its based of the newest sprint leak. Has anyone found a good rom that will allow for hands free bluetooth pairing?
Does it pair as a regular blue tooth headset or does it do something above and beyond that. I haven't had luck with the new leak gettin ANYTHING to connect, everything just about pairs, but nothing connects.
as far as i know it pairs just like a bluetooth headset. Obviously it can make calls and answer the phone. It says it paired correctly, but it never connects.
I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero
waltkap said:
I know it doesnt help with the panasonic, but I have the Vtech and it synchs flawlessly with my hero
Click to expand...
Click to collapse
and what rom are you using?
the only rom i got to sync with my bluetooth system built in my car is aloysius and the new fresh toast and fresh rom if that helps with anything.
Well, now that the leak is the same as the official rom i guess my bluetooth will never work on this phone again. I just restored my nandroid backup to go back to stock 1.5 and my phone will connect to my phone no problems. I guess that the 2.1 release is what is killing my connection to my bluetooth phone. great work htc. I'm going to write to them and sprint about my issue. glad i didnt use the official 2.1 because then i would never be able to use my home phone again.
Hi Guys,
I'm having this problem that is driving me nuts, don't really know how to proceed.
I have a car stereo a Kenwood DNX8120, which has parrot bluetooth hands free. It has worked very well in the past on an LG, SonyEricsson and the Nexus One.
On the Nexus S (I bought this used and rooted with CM7, so I don't know about a stock model) the bluetooth connects, then after some time, like 20 seconds, it disconnects. I can play this game forever, it won't stay connected.
I can use one of two methods to connect
1- put the phone in BT discovery and let the kenwood connect to it, or
2- Have the phone connect to the kenwood.
I've tried both with the same results.
I got a.logcat and I see a whole bunch of red entries at the time this happens but I don't know what to make if it and I don't know how to grab these entries to a file.
I have also tried a phone wipe and installed infin1ty's ROM and also the latest CM nightlies. Same friggin result.
I see in recovery there are options to delete dalvik and data but I don't know if they'll help.
can you guys help?
Thanks
Tried another device. The actual hardware could be messed up on either device causing this. Try your LG again to the radio and the try another headset to to the phone. Last but not least try the stock Rom .
P.s. cm7 had an issue on the evolution where by was not given a unique Mac address which caused issues for me connecting 2 cm7 EVOs (they would over write each other).
Hope that helps
Sent from my Nexus S 4G using XDA App
Hi Thanks for the help.
Both LG and SE phones still work fine. I'm unable to find another nexus s so I dunno if this particular one.
But here's a new discovery.
I paired them using the HU. Now when I start the car, the BT connects then after a bit it disconnects. Well now I can go to the *phone* and manually connect to the kenwood and the connection holds!!! I have no idea what is going on with the autoconnect but it can apparenlty hold a connect if I manually initiate it from the phone.
All this time I had been trying to get the kenwwood to do the manual connection (after the auto connection faills) and that never held.
sigh...
Have you tried a headset with the nexus to see how well/bad it works? Also are you on the stock rom? If so take it down to your carrier and ask if you can try it on one of their units.
Good morning fellow forum member. I've recently begun having some significant bluetooth connectivity issues with my continuum and Ford Sync system in my 2011 Fiesta. Now, before you start ranting about your loath for microsoft or Ford please hear me out. In theory, the Sync system, combined with bluetooth technology, is a great way to go hands free. It also allows for the coordination of the system and Pandora & Stitcher Radio on an Android phone.
Anyway, lately my bluetooth connection to my car has been causing FCs on my phone. They are the type of FCs that cause the "long-short-short-short" haptic feedback but doesn't throw a pop-up message describing the cause of the FC. So, when the feedback occurs the phone will sometimes lock up but it always disconnects the bluetooth. I don't use bluetooth in any other fashion so I can't be positive that it's not an issue with the car's bluettoth system.
With all of that said, is there an inherent issue with the bluetooth system on our phone? If so, is there a fix for this? I'm currently running the EC07-clean_new ROM. This was installed over the SCH-I400-EC07-FROYO-REL-PRODUCTION ROM. My broadband version iss:i400.0.6v.EC06, Kernel 2.6.32.9 and build SCH-I400.EC07.
Any help that you brilliant folks could offer would be much appreciated.
Thanks,
Ray
I run bluetooth constantly (it's the only way I talk on my phone, driving or not.) I've never run into this issue. Have you recently downloaded any new apps? I found that there are some apps that simply don't play well with our phones. Especially radio based apps (I.E. the issues a lot of us were having with gps based apps, or gps losing it's lock, after a while. Wireless tether 3.06 beta completely screwed my phone up... etc). The only other thing I could suggest is to drop your phone from the sync, and reconnect it... I do this with all my bluetooth devices at least twice a week as a matter of course. And if you want to experiment to see if it's sync or your phone, assuming you have bluetooth stack on your computer, you could connect it to your phone. Other than that, maybe find a friend that has bluetooth and connect it?
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Reborn627 said:
Thanks for the suggestions. The most recent app I have installed that uses a radio is the new Stitcher, though I have been having some issues with "My Tracks" FCing but I think that is another issue. Anyway, prior to your reply I found an app on the market called "bluetooth fix repair" It's free and I gave it a shot. I've also deleted the phone from my car's list and repaired them. So far so good. I have a bluetooth stereo headset I'll have to try. I probably have too many apps to begin with. I'll see about deleting some of the ones I don't really need.
Thanks again,
Ray
Click to expand...
Click to collapse
I think you should be good with rourine disconnect/reconnect. Asfor too many apps, the only thing rhat matters there is storage space. Android wint let you run "too many" at once. Itll delete from ram as needed. I was just saying that certain apps dont seem to play well with others. But that is an android issue, not your phone in particular.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
I'm totally stumped here. Yesterday I decided to reflash my phone. I figured any issues might be ironed out. It must be an app issue, although it is going to be a PIA to uninstall then reinstall each app and test the BT after each app install. I thought that it might be the trailblazer101 car cradle, desk cradle or the sticher apps that were giving me the problem but that doesn't seem to be the case. Maybe I'll try replacing the BT files with the ones from eclair to see if I end up with the same trouble. Any idea if that might cause more problems? Are the BT files android version specific?
Peace
EDIT: I've not swapped the BT files from eclair but I did spend an hour or so listening to Stitcher radio via a bluetooth headset. It doesn't seem to be a BT issue. More likely an issue with the connection to the Sync system itself. Connecting via bluetooth is no problem in the car. It's not until I attempt to engage a function other than the phone that an issue occurs. I may try to reflash the EC07-clean ROM and see if there was something with the EC07-Clean_new version that I've been running for the last few weeks.
OK, the BT issue seems to be corrected. I flashed adrenalyn's EC07-clean ROM and that seemed to do it. Something must have gotten corrupted. So, issue resolved...i guess.
Hey all,
Recently got my n4 and am currently running cm10 nightlies on it, but today I picked up our new car (Hyundai i30 premium) which has bluetooth built into the audio system and I can't get my n4 to sync with it properly. My partners Desire HD syncs no problems and all her contacts phone book everything shows up fine. My n4 wouldn't even sync originally then I just kept retrying and eventually it synced but nothing really works, music won't play through the speakers (the audio system just sits there waiting for music and nothing happens) my phonebook etc don't show up (after me allowing them permission) I can't even make calls.
I have heard that the n4 has some bluetooth problems but nothing this bad, anyone have any suggestions that I can try? Happy to go to another ROM if that will help??
Thanks,
Hosh
this build has serious BT issues. i can't even find a mouse that works. wait and see what the 4.2.2 update brings.
I own a Hyundai Elantra GT which is the US version of the i30 - I didn't seem to experience any issues when I paired it this morning, but I"ll double check when I get out of work this afternoon that the contact sync is working. I am, however, on the stock rom.
I own a 4 day old Dodge Journey and it pairs with no issue to Uconnect.
Try a different rom?
If thats not it, then its your hardware.
The new bluetooth stack in Android 4.2 is causing a lot of issues. Personally, I don't have any problems connecting to UConnect (Jeep Grand Cherokee) or my SmartMini (bluetooth music streaming).
I am waiting on delivery for my MetaWatch, there have been complaints that 4.2 isn't connecting well with it but I guess we'll see. CM10.1 users don't seem to have as many problems. I'm running Xylon w/ Franco r53.
I had the same problem with Chevrolet captiva until I have installed custom ROM and is working perfect now.I have tried every custom ROM and is OK with all.
I have this problem but there is a way around it (for me anyway).
Download Bluetooth file transfer from the market.
Delete the connections with your car. Both on the phone and your car.
Open Bluetooth file transfer. Select the Bluetooth screen.
Make a connection. The default android Bluetooth will ask for a password. Don't enter it. Instead go to your recent apps and select Bluetooth file transfer. Put the password in the request screen the app supplies.
Bluetooth file transfer should pair the devices and make a connection.
Once done. Kill Bluetooth file transfer as you won't be able to exit.
You can then uninstall Bluetooth file transfer if you want (although I tend to keep it for when I change ROMs or have to do a factory reset etc).
Hope this works for you
Sent from my Nexus 4 using xda premium
Hey all,
Sorry for the late reply, been away for the weekend. Thanks for all the advice, tried them all and no luck. Will try out a mates n4 tomorrow and see if he has any luck syncing with the car, if he does might just flash roms again.
after flashing a new rom, I had problems pairing w/bluetooth and connecting w/wi-fi. I fixed the problem by restoring my system settings w/titanium backup thanks to someone's suggestion.
Seems the only thing that worked for me is when it asks to sync my phonebook I have to say no, if I say yes it seems to freeze the whole thing. Makes me think if I click yes I might just need to give it 10-15 mins to sync, might try that tomorrow. But for the moment at least it's half working!
I was having problems with Bluetooth dropping while on Marshmellow. After upgrading to Nougat my Bluetooth worked great for a few weeks. In the last week, I am having problems again with dropped Bluetooth connections. The problem is only with my Plantronics headset. I tried the headset with my wife's iPhone and it seemed fine. On my XT1575, after about 5 minutes of use the BT connection suddenly drops.
I have tried the following:
1 Forget and repair the headset
2. Clear cache on the BT apps
3. Booting phone into Safe mode and then pairing with headset
4. Clear cache on the whole phone​
None of these changes have solved the problem. I am thinking about going back to an old NANDROID or even trying a factory reset. Before I try either of those extreme changes, I want to ask this knowledgeable community for its advice.
EDIT, Also tried turing off BT scanning location and turning off Media Audio. Still getting disconnects!
thanks,
Have you done a Network Settings Reset?
acejavelin said:
Have you done a Network Settings Reset?
Click to expand...
Click to collapse
Yes. I have tried Network Settings reset, at least twice.
Thanks for the suggestion. Any others?
Sent from my Nexus 7 using Tapatalk
Full factory reset.
autosurgeon said:
Full factory reset.
Click to expand...
Click to collapse
I am going to try a NANDROID restore first.
If that doesnt work than I will do a Full factory reset back to Nougat stock!
swieder711 said:
I am going to try a NANDROID restore first.
If that doesnt work than I will do a Full factory reset back to Nougat stock!
Click to expand...
Click to collapse
You could reload the stock firmware too... it is available now, check the link in my signature.
Still trying to fix my problem where my Plantronics Savi 720 base station loses it connection with it's DECT headset. This only happens when my XT1575 phone is connected to the Savi base via Bluetooth. The headset and base stay connected when I use it with a landline or USB port. The BT connection seems to stay up, but the connection between the base and the headset is dropped. I ordered a new Savi 720 and still had the same problem (will be returning it soon). I tried my existing Savi with my wife's iPhone and did not see the problem.
Late last night I reflashed the whole -22 ROM which seemed to make the problem go away! After a NANDROID restore back to my previous 22 set-up, the problem came back!
After all the testing, the finger is pointing at some app or setting on my XT1575 causing the problem. Although, I still have the problem when I booted into Safe Mode.
I now tried just reflashing BTFM.bin. For my first test, the connection was solid for 15 minutes. It usually drops in less than 10 minutes. This is encouraging. Will report back upon further testing.
Any thoughts or ideas on what could mess up Bluetooth?
Was on a 30 minute call today with no drops from Bluetooth. Looks like reflashing BTFM.bin fixed the problem.
After 2 days of reliable behaviour, the BT connection problem has reappeared. I had two calls get dropped this morning. I reflashed the BTFM.bin file and still had the problem.
Im going to try to have Plantronics review the log file from their headset to see if that shows any information.
Can anyone suggest other options for testing or debugging?
PS: I am considering moving to another phone, like the Pixel XL 1st gen.
I'm assuming you have updated the firmware on the Savi as well and disabled wide-band audio? I had issues with my Plantronics Voyager Pro until I disabled wide-band audio.
acejavelin said:
I'm assuming you have updated the firmware on the Savi as well and disabled wide-band audio? I had issues with my Plantronics Voyager Pro until I disabled wide-band audio.
Click to expand...
Click to collapse
Savi firmware is running the latest. Will have to check the setting for wide band audio when I get back home.
Thanks for the suggestion.
I turned off wide-band audio for deskphone and PC audio. I dont see a wide-band audio option for Bluetooth. Problem still persists.
I called Plantronics today. THe customer service rep has a Moto Phone, not a XT1575, and he has the same problem where the headset disconnects from the base. Even though the BT connection stays up. The rep claims that it is a problem the the BT chipset used in Moto phones. I sent him a log file from the Plantronics based. Hopefully, this issue can get escalated with Plantronics engineering.
I read the Nougat .23 has some updates to BT. I wish there was a way to try that. I am running .22. Isnt there anyway to downgrade back to MM so that I can than upgrade to .23? I know Acejavelin said it would brick the phone. Has anyone come up with an downgrade/upgrade workaround from .22 to .23?
Might be time for a Pixel XL 128GB upgrade (1st gen and not the 2).