Hello, I recently bought a 32 GB g4+ and everything was awesome so I decided to upgrade to the 64GB version of it. Ever since I switched to the larger model I have not been able to connect to my JBL charge 3 Speaker (recognizes it but says it cannot connect) or my LG tone+ headphones Can’t find them to pair at all, other phones can see and connect), although it connects fine to my pioneer deck in my car and my Samsung sound bar. When I was using the 32 GB model it worked fine with all these devices and my note5 works with all these devices. I have tried factory reset, resetting network settings, factory reset JBL charge 3, none of these things have worked. has anybody else had connectivity issues? any solutions?
This phone is on the newest factory firmware, have not rooted yet. Sprint network.
Related
Hello
My Peltor Workstyle5 headset was working fine before with:
Samsung Galaxy S2
Motorola XOOM
Then i broke my SGS2 and bought LG G2 D802. Bluetooth was working fine with the LG too.
One day bluetooth just stopped working with any device i tried. So i sent my headset to service as warranty is still on.
Got back the headset today. Description said earpiece has been replaced. Still could not connect to the LG.
Tried with my wifes SGS2, nothing.
With Motorola XOOM headset does connect. Also XOOM pairs fine with LG.
Headset has been reset multiple times before and after service. Havent reset LG to factory since connecting to XOOM works fine.
Seems that problem is with LG, but what should i do now? Reset LG?
Not rooted
Android version: 4.2.2
Software version: D80210a-EUR-XX
Thanks in advance.
//edit Reset LG to factory default, no help
Anyone? Any ideas?
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
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
Right after the DP5 installation, I had to unpair the phone and car (2016 Mazda) because the phone would never connect. It was no where near as easy as that sounds, took me the better part of 30 minutes because of repeated "unknown errors" coming from the car.
The phone paired up just fine but I still have frequent and completely unexplained dropouts on literally every Bluetooth device I have (headphones, Moto 360, car and the list goes on). So far this has been the absolute worst of the previews for BT that I have ever seen.
But then, if you read around here, it sounds like there were a lot of these that had flaky BT hardware. Have not exchanged mine, but that has certainly been my experience since I bought this back in December.
I have no issues with Bluetooth and the latest DP. I have my phone connected to a Kenwood deck.
Sent from my Nexus 6P using Tapatalk
I wonder if I have flaky BT hardware? Mine was a launch phone and it has worked perfectly in my Toyota since day 1. However I've recently bought a fitbit type band and with that application (veryfit 2.0) installed and connected to the band then if I make a call in car it drops the BT after about 30 seconds with an error message on screen saying 'corrupted probe message'. I can manually reconnect the call (it's still active on the phone) but after another 30 seconds or so it repeats the cycle. Have upgraded to Nougat Dev Preview NPD90G but still the same. Removing the app and its binding (it binds in the app not the phones BT devices in settings) and rebooting the phone resolves the issue. Tried again with a proper fitbit and the issue is identical.
I will RMA it to see if I get another one that works. Now to figure out how to put it back to stock marshmallow. gulp.
I have the same issue pairing to my car's Bluetooth keep pairing failed
bongostl said:
Anyone else on the newest 7.0 preview and unable to pair their bluetooth with their car?
Driving me nuts...hoping someone found a fix...
Click to expand...
Click to collapse
I had this same issue, I flashed the system file again and wiped the cache and dalvik. It seems to be ok now.
Check this solution. Pair with '0000' worked for me.
http://forum.xda-developers.com/nexus-5x/help/issue-android-nougat-bluetooth-issue-t3446073
Since switching from my Nexus 5 with 6.0.1 to a Nexus 6P with 7.0 I am also suffering from bluetooth issues. Pairing itself is not a problem but the connection sometimes drops, controls in my car don't work properly, remaining track time is not shown, etc. Haven't even tried to make calls yet. If I can't find a solution I'll probably be going back to 6.0.1.
The proposed '0000' solution is not working for me as I cannot change the PIN on my Seat Leon (2016). The PIN is autogenerated and shown on both displays to be confirmed upon pairing.
Has anybody tried flashing the latest 6.0.1 radio image and use it with a 7.0 system?
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.
Since the previous two updates on my Verizon V20 were installed (VS99518A & VS99519A) running 7.0 , I have been having bluetooth issues where there are momentary pauses while connected to BT earphones and random "rustling" sounds when I am connected to my car stereo (A2DP). There are even times the bluetooth does not reconnect (have to manually select the paired device at the pop-up).
I have already performed a factory reset and it still happens. These issues do not occur on other android phones so it can't be my stereo and bt earphones' at fault.
Any ideas? What should I check?
Thanks.
I really wish I could help you. Ive been having the same issues. Please follow up if you figure it out and I will as well
Same here
The 7.0 update took a while to get to me but now that it has, I'm not impressed and wish I could revert.
Immediately after I started noticing the same issues as OP. In addition, I can no longer BT FTP send to my desktop but I can receive from the desktop.
I've tried quite a number of things to resolve but none have. Several soft resets, hard reset, network reset, factory reset, reset of desktop settings (although apparently not needed a SIM-less Galaxy S4 does NOT have issues with BT FTP to the same desktop....
Attempting to pair the two, the S4 can see the V20 but the V20 does not recognize the S4.
I believe it is 7.0 update related because all was fine prior and the issues were noticed just 20 minutes after.