I upgraded to the S7 from a Droid Turbo. Before the Turbo, I had a first gen moto X. Both of those devises worked perfectly with the SYNC system in my Ford Edge. With the S7, calls come through to my car but messages to not. My car says SMS over bluetooth not supported on current device. I can't imagine that is the case, is there a setting somewhere that I may be missing? I don't understand why any modern phone wouldn't allow sms over bluetooth let alone a phone of this stature. There has to be a way in there somewhere.
The problem is this phone has the newest Bluetooth. And your edge probably has an older version that isn't fully compatible. It dosent work perfectly with my pioneer either. But my turbo 2 did.
Sent from my SM-G930V using XDA-Developers mobile app
Related
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.
Hey guys i just got a new vehicle the other day and i am running into an issue with my bluetooth.
The vehicle is recognizing incoming calls right when they come in but when making a phone call the phone tries to connect to the vehicle but the vehicle does not react. Media plays fine using bluetooth as well, only issue i am having is with outgoing calls... From the little bit of research i have done i have come to the conclusion that the issue is the phones Bluetooth modem (not sure if that is the correct terminology).
Things i have done:
I have tested the incoming and outgoing of phone calls with my work phone (blackberry 9930) and i have had no issues at all.
I have also reset the uconnect system and repaired the S5 but not having any luck.
Vehicle.
2015 Wrangler with Uconnect 130 system.
Phone Specs:
Sprint Galaxy S5 (rooted without custom rom)
Android version running is 4.4.2
NOTE: Phone will not alloy me to upgrade due to the root...
All help is appreciated. Bluetooth is kind of a necessity for me during long travels and i would love to get this working 100%
Thank you in advance.
Ordered the 6P last night, who knows when it will arrive. Wanted to see if anyone has paired a Gear S with the device to see how it works, what features don't work, etc. I currently have a Gear S paired with my Galaxy Note Edge.
I would like to know this as well. I have my 6P, and I am thinking about buying the Gear S.
I kind of got it working. Issue: if it's connected via bluetooth to your phone, any incoming calls you answer are through the watch (although incoming calls display on both devices). So, for now, I have bluetooth turned off. Since the watch has its own number, that's the only way to receive/make calls if you're not connected to your phone. I'm trying an SMS forwarding app so that text messages go to the watch as well as the phone, however the text shown on the watch comes from your phone's number, not who originally sent the text. Basically, I have the watch as a stand-alone device. The Gear Manager app doesn't work although you can get it installed on the phone..........just doesn't find the watch. There's a way to get your watch past the screen that says "use the Gear App to connect". On that screen you see an icon of the watch, tap on that about 25 or so times until you see the bluetooth message, afterwards, press and hold that watch icon until the next message appears and you're ready to go.
Question for anybody using any of the other ROMs, will the Gear S work with any of the rooted custom roms?
I got a gear s2 working on my Nexus 6P rooted rom
Sent from my Nexus 6P using XDA Free mobile app
Were you able to have it working prior to rooting?
ycats said:
Were you able to have it working prior to rooting?
Click to expand...
Click to collapse
I'm on a stock, bootloader locked 6P and have a Gear S2 working perfectly with it. However, there's a caveat. When I first got the watch, it pairs up just fine, but there's an update that you're prompted to take but can't because the phone is encrypted. What you need to do in that case is pair it with a phone that's on the Gear S2 supported list (http://www.samsung.com/global/galaxy/gear-s2/device-compatibility/), in my case a Nexus 6 that's stock and encrypted, take the update, then reset the watch and pair it with the 6P again. If you don't have this update, any time the watch and 6P become disconnected, whether because they're out of range of each other or because you intentionally disconnect them, you have to reset the watch and pair it again. After this update, that's fixed.
It seems odd because both the 6P and Nexus 6 I have are encrypted, but because the Nexus 6 is on the list of compatible devices, it works while the 6P has the connection issue without this update. But simply pairing the watch with any of the phones on the compatibility list above, taking the update, then resetting the watch and pairing it with the 6P again fixes this.
Other than that issue, the Gear S2 works flawlessly? Receives notifications for email, text, calendar reminders, phone calls, etc.?
Would pairing it to my son's Galaxy S4 receive the Gear S2 update?
I tried the workaround in the Gear S forum, and couldn't get it to work. I wonder if Gear Manager needs to be updated for 6.0?
If there isn't a fix soon, I will probably sell my Gear S.
The Gear Manager app was updated for Android 6.0., but appears they only have it working for the Gear S2, not the Gear S.
ycats said:
Ordered the 6P last night, who knows when it will arrive. Wanted to see if anyone has paired a Gear S with the device to see how it works, what features don't work, etc. I currently have a Gear S paired with my Galaxy Note Edge.
Click to expand...
Click to collapse
As far as I'm aware, the gear s is only designed to work with galaxy devices. I had the gear s2 & had nothing but problems with it. The disconnect>reset bug did my head in. Wasn't worth the hassle in the end. Got rid of it to a mate who has a Samsung phone & bought the Sony smartwatch 3 instead. I'm happy, he's happy. Everybody's happy.
Does the Sony Smartwatch 3 have a speaker?
I recently purchased the N6P to replace my dying N4. The transition from one device to the other has gone pretty well, except for one issue. My N6P is unable to find the bluetooth signal from my Ford Fusion. Upon turning on bluetooth and searching for devices, the N6P cannot find the Ford Sync signal. I've rebooted the phone many times, Ive tried it many times in safe mode with no success, Ive turned the Sync's bluetooth on and off numerous times, the phone is still unable to detect it. I have also tried deleting all the paired devices on the Sync settings and had no luck with the N6P working. Aside from a factory reset of the phone, what else can I do?
My N4 was able to connect to the Sync right up to when I stopped using it. My fiancee's Samsung Galaxy (something) can detect, connect, and function with the Sync's bluetooth. I am beginning to think its something with the N6P. Ive tried it on all three versions of the OS Ive had on the phone. The original OS version didn't work when I first powered up the N6P, the next version of the OS i updated to didn't work, and this morning the phone ran the latest update and the bluetooth doesnt work.
I'm at a loss, I'm ready to return this phone and go back to my dying N4.
Edit: I am currently running Android 6.0.1.
My wife's N5x has the same problem with our ford sync, I think its related to the bluetooth disconnection bug I've had since the may update.
You can still connect it by opening the bluetooth screen on your phone so that it is visible to other devices and in the sync setup tell sync to search for devices and select your nexus phone.
My wife and I both own Nexus 6p's. I just bought a brand new Ford F-150 and my wife has a 2014 Toyota mini van (forget the model name off the top of my head, but still a fairly new vehicle). Neither one of our Nexus 6p's will connect to with vehicle. Prior to our Nexus 6p's (which I really had to talk my wife in to getting a Nexus 6p) our LG G4 and Note 5 connected flawlessly. I even bought a Bluetooth thing that plugs in to my trucks aux and that works after turning the Bluetooth on and off a few times. Totally freaking unacceptable. We both have Nexus Protect on both devices, but don't think a new Nexus 6p will fix the issue. No problem at all with Google maps other than audio coming through my brand new trucks speakers. Smh. Both of our phones are not rooted or changed in anyway. Out of the box stock.
Sent from my Nexus 6P using Tapatalk
Sent from my Nexus 6P using Tapatalk
Confirm working in Nissan Frontier. Wonder why its certain auto manufacturers?
Works in 2014 Toyota Camry.
Mine works with zero problems in my '13 Fusion Ti. I also have a bluetooth adapter for torque plugged in with no hiccups. Is your sync software up to date?
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
desilva79 said:
Mine detects fine , but once connected I loose all system sound. i.e I can't hear map prompts anymore. Anyone knows a fix for this ?
Click to expand...
Click to collapse
I can verify that I have this experience as well in one of my cars with an aftermarket bluetooth Sony head unit (that supports A2DP streaming). Haven't checked in the Nissan yet (no A2DP), but I will tonight.
Bluetooth on this model sure has some "quirks".....
I have a 2015 fusion Ti & N6P I have had zero issues. however i will say my bluetooth connection is much more stable after updating SYNC to the latest version. Bit of a pain because you have to create a ford account to gain access to the instructions/files. but here is the URL to get you started: https://owner.ford.com/tools/account/how-tos/keep-your-sync-up-to-date.html
I also have a Ford Fusion 2015 and I have no problems connecting to SYNC. It also connects just fine with my wife's Ford Escape. Which month's build are you using? Is your radio up to date? I don't think I've ever updated the SYNC software in either vehicle so I'm not sure it's that. Make sure BT is on and you have the BT page in settings open so that both devices can see each other. Then go into the car's phone menu and add a device. That's how I did it. Make sure the vehicle is not moving or preferably in park. Good luck.
It magically connected right after I posted above. Now I'm afraid to install the June security patch lol. Working flawlessly in my F-150 though.
Sent from my Nexus 6P using Tapatalk
Is anybody having experiencing Bluetooth issues when streaming music or phone calls to your car radio or portable speakers? This seems to be a major problem with many people on the Sprint variant of this device and I wanted to know if any of the AT&T folks are facing any similar issues..
none here, I use my Samsung level BT speaker and it works fine. im on the 930fd model tho.
I was having the issue when I was with Sprint. I switched to At&t a week later and I haven't had the issue since. I'm not sure if it was Sprint related or device related. I got my wife the Note 7 on AT&T too and there have been no issues.
I reset all my network settings on the Sprint version though and it did seem to help quite a bit.
i use a bluetooth headset and the bluetooth in my car every day with no issues.
my ATT note 7 rooted with spirit firmware lost its paired device log every time its rebooted, forcing me to pair it with my car again every a few days.
No problems connecting and staying connected to a Subaru STi '17 stock system (starlink) and a pioneer aftermarket one.
I've had horrible issues with the note7. Twice. First when I moved from a note4 and then again when I moved from the AT&T-provided S7 interim device back to the non-exploding version of the note7. Whatever Samsung changed bluetooth-wise between the S7 and note7 has made it completely useless in several situations.
A few examples:
Witti Designs' Beddi alarm clock is displayed in the Beddi app but will not completely pair.
Automatic v2 adapter had to about stand on my head to get it paired (multiple resets, unplug / plug adapter, etc)
Plantronics Voyager Legend Call quality is completely worthless.
All three devices worked flawlessly with the Note4 and the interim S7. I could list more craptastic behavior but I think that suffices to prove my point.