My stock GS5 won't stay connected to my Honda Pilot. I had a 2013 and got a 2014 (long story), and it wouldn't pair with either. However, it has no problems pairing to my other car (Acura TSX), nor to any other car I have had (I travel for work and rent a lot) nor to any other bluetooth device I have. My question is: if I root the phone and install CM10, will that completely replace the bluetooth stack, or does it use the same one that Samsung put on there? I thought about just reinstalling the stock OS to reinstall the stack in case there was something off, but Samsung got rid of my two favorite features (shortcuts on the lock screen and swipe-to-call/text favorites) so I no longer have a reason to stick with stock. Therefore, if I'm going to wipe and start over, I'm just going to root it and get rid of the stock software. HOWEVER, if it will just install the same bluetooth stack, I won't bother at all.
Related
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
My Acura handsfree works like a charm. Perhaps you have too many contacts that are syncing?
awee man... I was hoping that there were no nissan/infiniti bt issues w/ this phone
I'll find out Saturday when I finally pick it up from the fedex place
rossiscatch said:
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
Click to expand...
Click to collapse
haha yeah, i don't have a "bluetooth settings manager" on my car, and i don't think i can update the firmware...which is ridiculous.
also, to the acura guy, my contacts aren't even syncing
niiiick said:
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Click to expand...
Click to collapse
I also just got an N1 and my Nissan handsfee bluetooth lets me voice-dial but the call doesn't get routed through the handsfree system. I have to take the phone out of my pocket and activate the speakerphone. Any solution would be much appreciated.
I don't have teh same system. Like the previous poster I use the N1 with my Ford Sync. If a call is initiated from the phone it starts out in "private" mode using my phone's speakers. If initiated from the car it uses the car's sound system. There's also an option in there allowing you to choose the default sound output of calls. I have the latest firmware installed.
That actually makes sense.. my previous phone always used the speakers which was a bit of a shock sometimes when I was sat in a car park wanting to make a quick call. Clearly it still has some rough edges on some cars.
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!
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
I am guessing that it isn't built on the 444 kernel, so, don't get too discouraged yet
Sent from my Nexus 7 using Tapatalk
ghstudio said:
For those anxious to get 4.4.4 you might try liquidsmooth which now incorporates it and runs on most if not all moto-x's. It's been upgraded to 4.4.4. Unfortunately, bluetooth is still not working correctly for me and if I try to pair the phone with my car, the car's system goes into a slow endless loop where the phone is connected and then disconnected. I am going to try to see if there is some way to get the phone working with my car....it's very frustrating because the moto-x has never connected correctly (galaxy nexus was flawless in this regard).
Click to expand...
Click to collapse
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
jaykresge said:
What year make and model do you have? I have a 2011 Ford Edge and 2011 Ford Fusion, both of which use Ford Sync (Suck), and I have no issues with either.
Also, are you stock, or running a custom ROM? You seem to be running a custom ROM, and in that case, all bets are off.
Click to expand...
Click to collapse
It is 4.4.4 kernel. I think I've found the issue and it's unique to "techies". I have a pebble smart watch which uses google...the connection to the car system (2014 MB) uses bluetooth. If I don't wear my watch, the connection to the car works...no loops/etc. When I wear the watch in the car, the car/phone link goes all screwy. I suspect that one of the bluetooth stacks doesn't like to share....and I'd bet it's the moto-x stack which can either use the bluetooth or the car link, but not manage both together, even though everything is paired correctly. I haven't checked to see if pebble and the MB use the same protocols...it may be that they both share txt even though I only need phone on the car link.
I'll post more when I get further into this....I just stumbled on the cause today when I didn't wear the watch and repaired the phone with the 4.4.4 kernel.
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
abuttino said:
Next time, get a Cadillac.
FORD -Fix Or Repair Daily
Click to expand...
Click to collapse
I've heard them all, but we've had precisely zero issues with the Fusion, and one with the Edge that was fixed free of charge due to silent recall.
My only issue with Sync is that my Fusion has the Gen 1 version, and the most recent software update removed the key reason I chose this car over the then comparable Sonata. Without that feature, I would have gone with the Sonata.
So when connecting to my main car I get no phone but media does play. Other cars it's 50/50 if I get whole phone or just media.
While researching I found that oplus3t had this issues with certain ROMs and sometime made a flashable zip that changed the bt stack. Was wondering if that existed for the axon7. I know it worked with my car with stock, hate stock though.
I don't know about a different Bluetooth stack, but I've tried every ROM on this forum. The only one that has fully functional BT for me is NucleaROM.
I have an Atoto S8, and this is my first Android powered head unit (coming from their linux-based F7, which was more of an appliance UI instead of a smart OS). I love the extra functionality it gives me, running apps and video players directly on the unit. But Bluetooth support is wonky.
My wife and I share the car, and ever since swapping to the Android powered unit, it only reconnects to whoever drove last. So if I drive the car all the time, its fine. But when my wife drives, she says bluetooth isn't working, so I have to go into settings on the BT app (BT1 as they call it) and see the three phones listed as paired (my old phone, my new phone and my wife's phone), and click on hers. Wait a bit, and then she is good to go. But then next time I drive, I realize my phone isn't connecting now, so I have to go do it again. Which means she's going to complain next time that her phone isn't working again.
I've installed a few bluetooth powered head units before, and even the Android Auto supporting F7 before this one, worked as expected: If the last device isn't available, try to connect to another recent paired one. It seems to just get stuck on the last one for some reason. Is this a limitation of how bluetooth works on these units?
have you solved this issue
i am finding it very frustrating
i thought i would solve it using the app "automate"
this would star a sequence of checks and sytematic attempted connections
but, oddly enough you cant automate the triggering o fthe flow
so it would only start if actioned
Yes, or rather THEY solved it.
Reach out to customer support. There is an update to the Bluetooth module that makes this work the way I described.
I got an A6pf in my other car and had them make an update for that one too. Much happier now.