What helped me fix my Bluetooth pairing. - Hero CDMA General

So with the new update I was having all sorts of problem trying to get my phone to pair with my Jeep Grand Cherokee's U-Connect. The only way I got it to work was to delete the phone on my Jeep in with U-Connect setup. Then start the whole pairing process over like it was the first time. Once I did that, it worked like a champ.
Every time I flash a new ROM I have to do this whole process over. With 1.5, I was able to just pair it up without deleting it from my Jeep. But not in 2.1. I'm wondering if this process might help others getting their phone paired with other devices.

Related

Bluetooth Audi help

Hello all. This is my first time posting a new thread although I've been lurking around here for a while soaking up all the information from this wonderful site. That said, I have been researching my problem for days now both here and on google and have found no solutions that work. So I'll see if there's anyone here who can help. Here goes....
I have recently flashed DCD's 3.2.6 ROM on my Verizon XV6800 and it works great (love the aGPS too, Thanks GC14) in every area but my car. I have a 2004 Audi A4 with the RNS-E Nav system with integrated bluetooth. Before I flashed to DCD, I had the original stock ROM (2.09.605.8 with Radio 1.30.00) which gave me full functionality with Jetware Mobile (Phonebook and Recent, Received & Missed Calls all transferred). Now, with DCD, it'll only connect to the car and won't transfer anything. If I try to load Jetware, it'll just lock up my phone while I'm connected to the car. Thanks in advance for any help you can provide.
No one else has this problem or a fix for it?
TGabriele said:
No one else has this problem or a fix for it?
Click to expand...
Click to collapse
I wish I was rich enough to afford such a car, then I could maybe help you out. LOL
But I would gladly accept such a car as payment for figuring out your problem.
Nevermind that the car is an Audi. Does anyone else have this problem with a factory BT system that transfers the phonebook to their car.
I had this same issue on my X3 and it seemed to be the way the PPC wanted to transfer the phonebook was by using some file transfer protocol the car did not understand. I could sync it and make and receive calls but no phonebook. Took it to the sprint store and we tried a blackberry and a standard moto handset. The blackberry did not sync the phonebook either but the standard moto phone did. I don’t think it’s possible based on the profiles in the car so I gave up on the phonebook. Try changing the bluetooth stack in the rom, you will have have to make your own rom and beware of the stack you use to make sure it is one for your phone.
I flashed DCD's rom using the kitchen, so making a custom rom from there is no problem to me. What I'm not sure of is how to change the bluetooth stack. I thought it is part of the hard coding for the OS? If you or someone else reading this thread has any information on this or can point me to some info on this it would be greatly appreciated.
I have the 6800 with DCD 3.2.6, and an Audi, with full phonebook transfer so I'll try to help you out:
1. Which 6800 radio are you using? I have found 3.42.50 to be the best as far as Audi bluetooth compatibility is concerned.
2. Jetware will not work with WM 6.1 on the 6800, but you don't need it, since 6.1 included phonebook transfer enhancements.
3. What version of Audi software are you at? There have been several releases since your year. You should be able to get more info from www.navplus.us and of course from your stealer.
4. You do have your bluetooth settings set for "discoverable", right? And, (I don't know why this is the case) it seems when OBEX is on, the phonebook and other items transfer quicker.
If you have the 6800 radio and Audi software updated, you should have no problem. Jetware is no longer necessary.
1. I am using radio ROM 3.42.50
2. The reason I loaded Jetware is to have it sort my contacts by Last,
First. Is there another way to do this?
3. I am running sw0200 on my RNS-E, but was considering moving up to
sw0260.
4. I haven't tried this, but I will.
Lately I've also had the issue where if the phone is connected to the car for a while, the bluetooth on the phone will shut itself off and not turn back on until I do it manually. I'm beginning to wonder if I should just hard reset and start from scratch. Any ideas? Thanks in advance.
I'm sure there's a reg tweak for listing First name first in contacts. Hunt around here or at ppcgeeks. If you want to stay on 6.1 jetware will not work (unless they release a new version).
Definitely update the Audi software to the newest version.
DCD has done nicely fixing power settings in the last few ROMS to solve the bluetooth shutting off issue, although when memory gets very low, it may still happen. You must have some other program or process running that sucks up memory if you are still experiencing this.
It never hurts to hard reset, as long as you have the time.
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
TGabriele said:
So, I've updated to SW0260 and done a hard reset and I'm still experiencing problems. Do you have any more suggestions? Thanks in advance.
Click to expand...
Click to collapse
I'm running an after market HU (Pioneer AVH-P4000DVD) and DCD's latest ROM, and Jetware works fine on mine. Just re-transfered my phone book earlier today....

can someone help with bluetooth?

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.

N4 bluetooth won't sync with car

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!

ROM that doesn't have Bluetooth audio problems?

I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
djmasters said:
I *REALLY* don't want to buy a different phone, but.... I recently swapped out the headunit in my truck from a Clarion to a Kenwood due to phone audio problems with the Clarion. So now the phone over BT with the Kenwood works great but the audio over BT is skipping and breaking up. Seen lots of posts about this being a problem, but no solutions. Sometimes rebooting the phone helps, but not usually. Sometimes forcing Bluetooth Share to close will help, but not usually. I've deleted and re-paired the devices.
I am currently running the stock 6.0 ROM, build 24.49-18, only rooted. The phone says it's up to date.
On to my point... do any of the alternate ROM's seem to have the BT audio issues worked out??
Click to expand...
Click to collapse
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
djmasters said:
Answering my own question.....
I ended up trying another ROM, AICP for clark, and so far AVRCP is working fine, it has connected/disconnected several times and has always come back quickly and without any skipping/stuttering. I haven't tried the phone over BT yet. And it's a pretty good ROM beyond that!!!
Click to expand...
Click to collapse
I was wrong, after a couple of days AICP started doing the same thing. Replaced XT1575 with an HTC 10, I wish the screen was larger but it's a really nice phone!!! And no Bluetooth troubles.
My phone is connected to my car radio any time I'm in the car, and not having this issue. I'm still on 5.1.1 stock but rooted. Headunit is a Alpine CDE-W235BT. I've had it hooked up 5+ hours at a time. No issues with media or phone calls.
Yeah, it works for some but not for others... I think it's more headunit dependent... my Clarion was OK for music but the phone was jacked up. Reverse with my Kenwood, phone OK but audio jacked. Either way, it had to go.....
Factory rom is the only one I can get to work properly with BT in my Mercedes
I haven't tried it on the Moto X Pure, but on the 2nd gen Moto X, Cyanogenmod had infinitely better bluetooth strength than the stock rom, or any other rom I tried. I'm not saying it's the same for the Pure, because they're probably maintained by different people, but worth looking into at least.
Bluetooth usually connects between my Moto X Pure and Mazda3, but there is a 35% chance that when I turn on my car the audio will connect in this really strange manner where tracks skip and the audio sounds horrific. The only solution is to disconnect and reconnect again, which takes another 30 seconds.
Every ROM I have tried on Moto X Pure has had this problem:
Stock, CM13, AICP
It's gotten so annoying that I've decided I am going to sell my Moto X Pure and revert to my Galaxy S4. Never have ANY problems with my old Galaxy.

Bluetooth and WIFI Discovery Issues

Hi All,
New here and first and my first Android headunit (Dodge 2009 Ram truck).
Purchased this unit ebay.com/itm/282734637463 on ebay Hizpo using android 7.1.
Got it and installed. While it came with no install directions, it was straight forward and went in easily. First off would like to say the quality and what does work I really like. But, I really purchased it to have Bluetooth in my truck. Being purchasing a new headunit versus adding Uconnect to stock radio, thought this was the better value.
I am having problems getting Bluetooth and WIFI to discover any of the phones I have tried (apple and android phones). After 50+ atemps Bluetooth and WIFI discovery and connection was successful only twice and only once lasted as long as about 8 minutes then failed and no longer able to see bluetooth devices again. This was on achieved after going into factory settings and changing BT adapter to No rebooting and then changing adapter setting in factory settings back rebooting. That is when it worked, but as I mentioned for a very short time and would have to go through the same process all over again for discovery and connection to only be short lived.
Have bee in contact with the ebay seller. They have been very little help. He did send me an update of which I tried to install. After I plugged USB in it found the update and reboots but on black reboot screen almost immediately I get just Error! message then reboots and tells me would I like to retry. Again after many attempts same results will not update.
Needless to say seller now making very dificult to return. If I can find a solution I really like the radio and would like to keep but being the main reason I bought for Bluetooth if I can not get it to work a $300.00 dollar waste of money.
I am hoping it is a firmware issue and can be corrected.
Any help would be much appreciated.

Categories

Resources