Related
Hi
I have been trying to pair my N1 to my nissan altima 2008 bose bluetooth system but it wouldn't pair. I tried countless number Of times but it won't work.
Does anyone else have this problem?
I think I read in the Google Nexus One forum that there are issues with Nissan/Infiniti cars and the bluetooth of the Nexus one.
hmmm... I have got mine paired with Chinese all in one DVD/SATNAV/DTV unit... it works very well.. It even automatically switches on the unit when It detects a bluetooth signals from my paired Nexus One....
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Weees said:
Well, Im guessing its something to do with compatibility with the Nissan Bose Unit. Because I also had a difficulty pairing my Previous G1, But ONLY after updating to Donut 1.6. It eventually connected but after many many tries.
I have beeen doing some googling about this and it seems that many users are having problems pairing with different cars with 1.6 and above.
Click to expand...
Click to collapse
Well the other option you have is to change your car... and get a car which is compatible with Nexus One...
see here: http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
this issue is known to carry through android 2.0 and 2.1.
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
jeffokada81 said:
I have the 2010 Mazda 3 sport with the Bose package and it pairs fine.
Click to expand...
Click to collapse
Yeah, I have the 2010 Mazda 3i touring and no problems either.
ID have a kenwood deck in my mazda and all works good. is there some kind of factory reset switch on your stereo, that's what I have to do t get new phones working on mine.
I have a Parrot Mki9100 and I have some problems...when I am on the car my Nexus One connect itslef with the Parrot, but it disconnect and try to reconnect many times. At the end it stops trying...
So every time I have to go to Settings->BT->Long press on Parrot device and click connect. After that it works...very annoing...
Hm... I have an '08 Infiniti G37 with the Bose system and it pairs and works just as well as it did with my G1. I would have assumed that Nissan is using the same or a similar unit for the audio system for most of their cars.
Mazda 6 gt-m 2009 here, BT carkit has no probs with the N1
Tried to pair it with the parrot in my gf's car, but same probs as described by other users. Seems it's the Parrot; my iphone had issues with it as well.
Ah well, i'd rather drive my car then hers, so good excuse to use mine
I dont get how they end up making things worse by upgrading rather than making things better !!! I mean according to : http://code.google.com/p/android/is...ct&colspec=ID Type Status Owner Summary Stars
This problem has been known since 1.6 and I can defenitly confirm that since It took me forever to pair my G1 previously. But with my N1 , it just never pairs, so they even made it worse. Such an important option, you would think Google would have fixed it in 2.0 but to drag it to 2.1. This is just messed up.
That is very frustrating.
@OP, someone mentioned changing your car to accommodate your nexus one, that sounds like a great idea, but if you can't get it to work you can always go with a bluetooth add on option.
At Volkswagen there were some phones that were not connecting with the manufacturer add on and customers were pissed because they paid over $400 for the option. Another thing just as bad is purchasing the unit and not being able to use the bluetooth steering wheel controls because of compatibility issues.
My conclusion is that there are too many products out there and sometimes they are just not compatible with each other. In this case it sucks that it was your car...or should I say your phone?
Well, the Nexus connects fine to my VW premium bluetooth (from 2005) but the cars system can not access the phonebook.
Not even the sim contacts which the HTC Hero could do.....
Google support suggested importing the sim contacts into the Nexus.
I wonder if they read the mails before they answer....
I've always found OEM bluetooth to be pretty uncompatible, and yet to see an update for one.
I've got a kenwood unit, which works with my steering controls, connects handsfree and audio when I turn on my ignition, and it syncs the phone book fine, showing the callers name when the phone rings. (it cost £80....) and I updated it (it's a parrot bluetooth unit in there) from my laptop via bletooth.
The N1 works best of all the phones I've had (6 htc's in 3 years) with it.
I never had an issue with my old g1...until I flashed a 2.0 ROM. Everything pairs fine, music player worked, stereo would switch over, but no sound came from speakers on phone calls. Now my nexus is the same way. I've asked Cyanogen if he would be kind enought to look into it and hopefully he will.
My N1 (locked bootloader, not rooted) routes the audio just fine, did it work before you cyanogened it?
ck3100
Wel I tried to connect my N1 to the parrot ck3100. it will see it fine, but the moment I try to link it it says paring failed. Anybody had any better luck with the ck3100 and N1?
mgymnop said:
Yeah, I have the 2010 Mazda 3i touring and no problems either.
Click to expand...
Click to collapse
I've got a 2010 Mazda 3 sport - it pairs/plays fine etc with my Nexus, but the person on the other end of the line always complains that I sound *really* quiet. I never had that problem with my G1. Do you get any complaints?
i've paired a few things (bt headset, parrot car hands free, computer) but it won't automatically connect to anything. i have to manually tell it to connect. is there a setting that i'm overlooking, or a tweak to allow this?
thanks.
Yeah I noticed the same thing in the car today. Maybe because of whether it is discoverable or not? When you turn that on it only does 120secs. I haven't played with it, but i sure hope it can auto connect, or at least with froyo.
It auto-connects to my car, but not to my home phone. I think that's because the car itself initializes the connection... Would be nice to figure out how to fix this, so I wouldn't have to connect manually every time I come home.
wgarrido said:
Yeah I noticed the same thing in the car today. Maybe because of whether it is discoverable or not? When you turn that on it only does 120secs. I haven't played with it, but i sure hope it can auto connect, or at least with froyo.
Click to expand...
Click to collapse
In my 10' BMW, I had to check mark to always allow the car to access my contacts. Once I did that, it would automatically connect to my car upon startup of the car.
Hope that helps.
rajsharma714 said:
In my 10' BMW, I had to check mark to always allow the car to access my contacts. Once I did that, it would automatically connect to my car upon startup of the car.
Hope that helps.
Click to expand...
Click to collapse
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?
What I figured out is that auto-connect on this phone just doesn't seem to work at all. The only time it auto-connects is to my 06 Acura when I start it and only if it's not already connected to anything else. But that's because when I start my car, it's the car that initiates a connection, not the phone. If I'm connected to something else (like my home phone, for example), when I start my car, and drive off, Bluetooth connection to my home phone will get dropped after I get away for more than 100 feet, but it will never connect to my car after that. And it never connects to my home phone on it's own. Very painful!:-(
My Captivate will automatically connect to my Parrot hands free device when I get into the car. I don't know which device is pushing the connection. However, I also have a Miccus BluBridge Receiver in my car plugged into the Aux jack. This device doesn't auto connect.
To get things working I have to go to the home screen, settings, wireless, blue tooth, then click on the device. A friend of mine was talking about Tasker as a possible app to use, but I don't really want to spend the money on it until I know it will do what I want. The other annoyance I have is that speaker, headset, and bluetooth volume are all the same. It looked like Tasker would solve my second problem, but perhaps not my first. Has anyone else investigated this?
Bluetooth auto connect
I too thought I had an issue with this. Mine is now working OK most of the time. One thing I discovered is that if there is more than one BT device available the phone sometimes will not connect automatically.
I wonder if this has to do with the fact that it will not connect to more than one device at a time. This is big downside for me that I hope get corrected (but please GPS first)
It won't conect correctly because there is no setting for always visible. The handsfree device searches for your phone to initiate the conection and if it can't see it it won't try to conect.
jbl7979 said:
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?
Click to expand...
Click to collapse
I also have a Genesis Coupe 2010 (3.8 in case you care) and my vibrant connects just as well as my TouchPro2 and my Nexus One running Foyo.
The Nexus One stock 2.1 never worked, reconnecting every couple of minutes.
My first Vibrant (same as captivate) did not work well either. I expected it was because the BT stack in Eclair did not support car profile, but after I exchanged my Vibrant due to a rattling volume key, it has worked very reliably with the GC'10. It autoconnects ad soon as I turn on the engine, without having to do anythong, followed by "transfer complete".
I leave BT on all the time. My phone is not rooted or modifief in any way, running stock software for everything.
Sent from my SGH-T959 using XDA App
thumper_1151 said:
It won't conect correctly because there is no setting for always visible. The handsfree device searches for your phone to initiate the conection and if it can't see it it won't try to conect.
Click to expand...
Click to collapse
That is not true and it is not necessary, not even during pairing, ad the connection is initiated by the phone. Once passkeys are echanged, visibility is not required.
Please verify your answers prior to posting to prevent other people from getting confused.
Sent from my SGH-T959 using XDA App
jbl7979 said:
in my '10 Genesis Coupe, I cannot get it to auto connect, even though i reset it two times and checked "always allow." This is the first phone this has ever happened with, every other one auto connected (HTC Touch Pro2 with winmo 6.5 AND a hacked android 2.0, htc hero w/ 2.0 and 2.1, n1 w/ 2.1 and 2.2, and a feature samsung phone) so I know its not the car.
Any more ideas?
Click to expand...
Click to collapse
What firmware do you have on your GC? Have you deleted all phones?
Things to try:
Delete all phones from the car (setup/delete all phones)
Restore the phone to factory settings.
Upgrade the car's radio/BT firmware (see dealership for details or try gencoupe.com)
Call ATT support (?)
Wait for froyo
Get used to
Return/sell the phone
Hope this helps
Sent from my SGH-T959 using XDA App
I have the same issue with my Plantronics Voyager Pro . Can't get it to auto-connect! Anyone have an idea what the problem is?
Sent from my SAMSUNG-SGH-I897 using XDA App
I am a tech for mercedes and we have to set the phone to always visible or it wont auto connect. It is the same way with pioneer bt radios. I am just speaking from what mercedes told us and personal experience with pairing phones. I have had the problem probobly 100 plus times at work where phones wont auto connect evan though they are paired corectly and when you change the phone to always visible it fixes it every time. I know the phone can initiate the conection, i just know they don't all do it automatically.
thumper_1151 said:
I am a tech for mercedes and we have to set the phone to always visible or it wont auto connect. It is the same way with pioneer bt radios. I am just speaking from what mercedes told us and personal experience with pairing phones. I have had the problem probobly 100 plus times at work where phones wont auto connect evan though they are paired corectly and when you change the phone to always visible it fixes it every time. I know the phone can initiate the conection, i just know they don't all do it automatically.
Click to expand...
Click to collapse
Never had the problem with any of the Pioneer radios we've had, and my Eclipse doesn't have that problem either. To be fair, I've no experience with MB cars, but that shouldn't be the case.
I know with my Eclipse HU, I had to initiate the connection while in the phone menu otherwise it would connect for BT audio but not for the phone. After setting up the phone it will connect as its supposed to regardless of what input I'm using.
just as an update to my initial problem... my parrot system in my car auto pairs all the time now (it just takes ~30-45 sec to do so), but the phone still will not auto pair to bt headset or computer...
I don't think its supposed to auto connect to the computer. I think its a need based connection.
And on that note, when i send a file my phone does connect. I don't use a dedicated bt headset so i can't talk about that unfortunately.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lucke said:
just as an update to my initial problem... my parrot system in my car auto pairs all the time now (it just takes ~30-45 sec to do so), but the phone still will not auto pair to bt headset or computer...
Click to expand...
Click to collapse
When you say 30~45 sec, does it mean from powering the car up until BT is usable through the car system? That's is normal and the duration depends on how many contacts you have in your phone book and how many phones per contact. Mine take about the same.
BigJayDogg3 said:
I don't think its supposed to auto connect to the computer. I think its a need based connection.
And on that note, when i send a file my phone does connect. I don't use a dedicated bt headset so i can't talk about that unfortunately.
Click to expand...
Click to collapse
I agree. It is only supposed to autoconnect to devices that support the handfree profiles, if the handfree profile is set as default.
I tired turning visible on right before i started the car and it connected no problem. Really annoying. I have a pioneer as well. Too bad you can't set it to visible always. Other than that it works much better than it did with the Fuze/Any WinMo phone. Never had a phone that worked right in the car, except for my GF IPhone, works great.
I hope it works better in Froyo.
I picked up my new car yesterday (Seat Ibiza) only to find that my N1 will not pair with the installed bluetooth handsfree system. I can find the kit when searching for bluetooth devices (picks up as Seat_BT with a headphones symbol alongside) however selecting the 'pair & connect' option results in a messagebox stating "There was a problem pairing with Seat_BT" - no PIN code is requested.
I've tested the car with other devices (laptop, other phone) and the pairing is successful.
I've checked the compatibility listing with Seat and they list (from Dec 2009) the Hero and Magic as compatible (as at Android v1.5). I've also seen posts in Seat forums indicating that the HTC Desire pairs successfully with the Ibiza handsfree option.
My N1 is stock, unbranded running 2.2.1.
Can anyone here give me some insight into the differences in the bluetooth stacks / known issues with N1 bluetooth that may help me resolve this?
Is there a way of logging bluetooth pairing requests that will help me find the root cause of this issue?
TIA
CodeMonkey said:
I picked up my new car yesterday (Seat Ibiza) only to find that my N1 will not pair with the installed bluetooth handsfree system. I can find the kit when searching for bluetooth devices (picks up as Seat_BT with a headphones symbol alongside) however selecting the 'pair & connect' option results in a messagebox stating "There was a problem pairing with Seat_BT" - no PIN code is requested.
I've tested the car with other devices (laptop, other phone) and the pairing is successful.
I've checked the compatibility listing with Seat and they list (from Dec 2009) the Hero and Magic as compatible (as at Android v1.5). I've also seen posts in Seat forums indicating that the HTC Desire pairs successfully with the Ibiza handsfree option.
My N1 is stock, unbranded running 2.2.1.
Can anyone here give me some insight into the differences in the bluetooth stacks / known issues with N1 bluetooth that may help me resolve this?
Is there a way of logging bluetooth pairing requests that will help me find the root cause of this issue?
TIA
Click to expand...
Click to collapse
I've resolved my own problem, so here's the approach for anyone else..
To pair the Seat kit with a Nexus One you need to do the following:
1. Find an app on the Android Market called "Bluetooth File Transfer" by Medieval Software
2. Install
3. Using the app (on the 'Remote Devices tab) initiate the pairing with the car
4. You will get the PIN prompt - enter the 1234 PIN
5. Once paired the app will begin transfering something (I think it's call history but not sure).
It will then report an error - don't worry about that.
6. Shutdown the app and uninstall it (it is no longer required).
7. Reboot the N1 (to clear out any remaining dregs of the app).
8. Phone should then connect and disconnect using the standard bluetooth functionality.
Not sure why this works, perhaps the app extends the default bluetooth stack, resolving the issue that prevents the prompt for the pair passkey.
I've not fully checked the level of functionality available, but I can definitely initiate a call to the last dialled number and answer incoming calls.
Hi Guys, Newbie here in need of some help.
I have searched high and low for an answer to this and whilst people have had similar issues, none quite the same and as such I have not been able to fix it yet.
Basically I have a Galaxy S which I bought about 6 months ago. It is running Android 2.2 Froyo 'Firmware version' 2.2.1. (let me know if you need any more info on build etc).
The problem is that I bought a Belkin Bluetooth Music Reciever so I could play music remotely from my phone to my stereo.
I made sure I carefully read the reviews and some bloke called Dan who is a regular reviewer had tested it with the Samsung Galaxy S so I thought I was all set.
I can send you the links to see the item and the review if you like.
However when I followed the Belkin's instructions the phone was supposed to ask me to enter 0000 to complete the pairing. The phone seemed to pair automatically, without asking for a code. So I assumed everything was fine. but then the music came out the phones loud speaker rather than the stereo.
I have also noticed that whilst the phone pairs with the BT reciever, it doesn't seem to connect.
I have successfully used the Belkin with my wife's 18 month old Sony Ericsson C905 and an HTC Desire so I know the Belkin works. I just reckon there is a glitch which is stopping me pair with it properly.
The remedies I have tried:
1) Unparing and Re-Pairing Bluetooth
2) Rebooting Phone, Rebooting Belkin
3) Going into Bluetooth Options and selecting Play Audio via Bluetooth. (When I also press the 'Connect Now' tick box, it tries and fails although it does still think it is paired.
4) I also double checked to see if there was a firmware update for the phone via Kies and there was so I installed that and it still won't work.
5) Samsung Support have simply said -"It must be a compatibility issue and we can't help you." - if that was so, how come someone else used a Galaxy S when reviewing it!?
This is driving me insane! Can anyone help me with this? Any help appreciated.
It's probably not much help, but as a datum I'm using some sennhieser PX 360 A2DP bluetooth headphones with my i9000 and they're fine. I didn't have to enter a pairing code as 0000 is the default for accessories these days and it's automatic
Sent from my GT-I9000 using XDA App
HarpingOn said:
It's probably not much help, but as a datum I'm using some sennhieser PX 360 A2DP bluetooth headphones with my i9000 and they're fine. I didn't have to enter a pairing code as 0000 is the default for accessories these days and it's automatic
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks HarpingOn,
So the plot thickens then...
Can anyone help?
I had a problem recently where I thought my Galaxy S had stopped pairing properly with my Motorola T505 - the music playing bit worked fine, but the phone connection, voice dialling etc just wouldn't work at all.
Turned out I'd left the bluetooth on on my work phone (old Nokia) and that was connecting preferentially as that was the last thing connected. Once I turned that off it all worked again. Don't suppose there's anything like that happening?
Barkotron said:
I had a problem recently where I thought my Galaxy S had stopped pairing properly with my Motorola T505 - the music playing bit worked fine, but the phone connection, voice dialling etc just wouldn't work at all.
Turned out I'd left the bluetooth on on my work phone (old Nokia) and that was connecting preferentially as that was the last thing connected. Once I turned that off it all worked again. Don't suppose there's anything like that happening?
Click to expand...
Click to collapse
Thanks Barkotron, its a good thought but I don't think there is anything that would cause it. The nearest other bluetooth device which is switch on is the B/T keyboard for my iMac which is upstairs at the other end of the house.
Stumped!
Bump...any ideas?
Same problem here with a BeeWi BBR100-A1.
Device works fine with a iPhone 3GS but not with my i9000. Don´t know why and where to search. Installing now the Android SDK and hopefully there is a errorlog.
I have the same problems that you describe, pairing starts - the BBR100 restarts and it looks like the pairing fails. Galaxy S i9000 displays that it is connected to the bluetooth receiver...
That sucks!
Belkin was my backup, but now end of all hope.
Looks like it´s a problem with the BT-Stack, with my Senheiser MM100 it works just like a charm!
Any news or tips with another receiver?
I tried with a Creative bluetooth speaker in a shop today. No pairing code required.
One thing I did notice though, I had to pair the Galaxy with the Creative speaker, then go back into the bluetooth devices list and select the speaker to connect it. The audio then switched from the built in speaker to the bluetooth device.
I have to do this with my headphones too. The devices automatically pair when the headphones are powered on but the headphones don't produce sound until I also go to the bluetooth list and connect them.
Hope it helps.
Sent from my GT-I9000 using that XDA App thingie
All I tried ends up with more questionmarks then before.
1. HCITOOL
Downloading and copying hciconfig, hidd and hcitool to /system/xbin and set it to 755. Doing a hcitool scan and recieved:
#hcitool scan
Device is not aailable: No such device
Trying a hcitool dev and get "Devices: "
Looks and sounds like that samsung modified the bluez
Installing Android SDK and doing a logcat getting:
Code:
I/BTL-IFS ( 4253): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTR
L) 11 pbytes (hdl 19)
W/BTLD ( 4253): btui_security_cback( LINK FAILURE:: hci status: 22) 8==link super to
W/BTLD ( 4253): for bd_addr: x00:x18:x96:xa0:xy:xx
I/DTUN_CLNT( 4273): dtun-rx signal [DTUN_SIG_DM_LINK_DOWN] (id 48) len 13
D/DTUN_HCID4( 4273): dtun_dm_sig_link_down()
I/DTUN_HCID4( 4273): dtun_dm_sig_link_down device = 0xeca8 handle = 274 reason =
22
I/BluetoothEventLoop.cpp( 2713): event_filter: Received signal org.bluez.Device:
PropertyChanged from /org/bluez/4273/hci0/dev_00_18_96_A0_xx_xx
D/BluetoothEventLoop( 2713): Device property changed:00:18:96:A0:xx:xx property:
Disconnected
D/BT HSHFP( 2808): Received intent Intent { act=android.bluetooth.device.action.
ACL_DISCONNECTED (has extras) }
I/BT HSHFP( 2808): ACL disconnected
I/BluetoothService( 2713): ACL disconnected, mAclLinkCount = 0
D/BluetoothA2dpService( 2713): Received intent Intent { act=android.bluetooth.de
vice.action.ACL_DISCONNECTED (has extras) }
I/BluetoothHIDService( 2713): Received intent Intent { act=android.bluetooth.dev
ice.action.ACL_DISCONNECTED (has extras) }, device = 00:18:96:A0:xx:xx
I/BluetoothHIDService( 2713): ...ACL disconnected
can somebody make sense out of this?
Only thing I see is the ACL disconnect and the line:
W/BTLD ( 4253): btui_security_cback( LINK FAILURE:: hci status: 22) 8==link super to
please guys?
A2DP problem with JS5?
Until recently i was using a2dp to connect my sgs to my handsfree car kit and listen to music: it worked perfectly and the sound was great. Then i upgraded from JPF to JS5 (stock rom from samfirmware), and now music is always jumping forward. Normal connection for answering calls works perfectly...
sounds like another problem...because pairing works for you...right?
but anyway, there must be a way to change the bluetooth-stack like the windows way...
I have this problem too, pairing works but no sound via bluetooth. I am on JS3.
Edit: IT IS WORKING!
Unpaired and paired again. Works like a charm.
Sent from xda-powered Galaxy S
Slightly tangentially, do we know if the Galaxy S is supporting the Apt-X A2DP codec? The galaxy sounds better than my iPod touch using Apt-X headphones, but it could be something else making the difference
Sent from my GT-I9000 using that XDA App thingie
Mhm, hopefully I can do some more search this weekend.
Searching around the i-net brings some threads with the blueZ (bluetooth-stack) from canonical. Some people say that Samsung has modified the stack. Hopefully cyanogenmod brings a solution, afair. they use another stack then the stock rom.
@HarpingOn:
My old iPhone 3G and a iPhone 3GS works with the BeeWi BBR100 perfectly, but the new SGS not....???....so your suggestion with apt-x could be a idea, but why the hell SGS pairs and plays music over my Senheiser MM100?
More questions then ever, but I don´t have a clue what could it be. Thats the damn old problem with IT. If you don´t know where exactly the problem is you can´t fix it.
Today I unpaired the phone, reseted the car kit, paired again, and it's working ok. Sound is not as good as before, but may be it's just some equalizer setting. If this procedure doesn't work for you, try a phone factory reset.
I can confirm that everything is working ok. Unpair and reset did the trick for me.
Don´t work here... same as before.
Pairing seems to work, but finally you notice that it wan´t pair correct.
Bump
I have the same problem with the Belkin Music Player - has anybody found a solution ?
I have send my problem to BeeWi with complete error log and all other things that I have found.
Their reply:
Dear sir,
We have tested BBR100 on galaxy S and it works perfectly.
Easy pairing without entering 0000 code. After pairing you need of course to ask for connection because Android phones don't connect automatically.
Best Regards,
BeeWi
-> I´ve got a solution, send BBR100 back to sender and buy a cable. Works now for me!
I also have had the problem to connect the Belkin BT media streamer but just got it to work!
My solution
1. Pair ( When I do this at first I get the same problem as many others, the SGS pairs but does'nt connect).
2. Unpair the devices
3. Pair again - now it also will connect.
4. The music plays trough my bluetooth to my stereo.
The only problem for me now is that the sound really SUCKS. No bass what so ever etc. Any1 knows how this could be fixed?
Hi - new here on the site. Thanks in advance for any help and or advice.
I just picked up an NIB unlocked N6 off swappa loaded my sim from my Droid Turbo and everything is going good EXCEPT for the bluetooth. I have the latest Lollipop update and still having issues.
The phone does not sync with any of my bluetooth devices. It's not even "discoverable". I performed some of the troubleshooting methods; clearing cache, factory reset, etc.... and still no luck.
The seller on swappa said it may be because it's on CDMA (Verizon). But that doesn't make sense to me??
Any help would be greatly appreciated!!
@Motivated1,
There is no such thing as a "Verizon" CDMA version. They are all the same. So when you go to Setti ngs/Bluetooth and enable it, it's not visible to other decides, and it doesn't discover other devices?
Thank you for the clarification Cam30era.
Yes, that is correct. I'll turn on the bluetooth toggle and it's not discoverable nor does it discover my BT devices. I tried to pair it with my Bose Colorsound speaker, my Droid Turbo, and some bluetooth headphones...all unsuccessful.
I have had a new Nexus 6 from the Play Store. for 3 days (Activated on Sprint, but I think that is irrelevant.) I am running 5.1.1, build LMY47Z.
My one issue is that the N6 Bluetooth, which I have successfully paired with my 2012 Subaru Forester, does not automatically connect. Also, sometimes it will connect to the car, but only for audio, not for phone functionality.
I usually have to fiddle with it to force a good connection. The easiest method I have found is to toggle Bluetooth on/off on the Nexus. It sometimes takes several attempts.
Thanks boomerbubba for the response.
So, I took it to a friend of mine with a moto watch and a Note 4, the N6 connected with both of them instantly. I went home and tried to pair it with my Bose Color Soundlink and once again was unsuccessful. Since I knew the bluetooth had the capability of working, I just messed around with the speaker, holding down the bluetooth button for several seconds, turning it off and on, toggling my N6 bluetooth, and sure enough it worked!!!
So I tried to pair it up with my Droid Turbo and that worked as well.
So I really don't know what the actual problem was...maybe just a finicky unit. But all is good now!
In my experience with my previous phone (a Galaxy S4), and the same car, the Bluetooth discovery "just worked" automatically. Once I had the initial pairing set up, I never had to do anything but bring the phone into the car and it connected.
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
boomerbubba said:
So IMHO, this flaky behavior is a bug with the Nexus 6 -- or with the LMY47Z build of Android Lollipop.
Click to expand...
Click to collapse
I now attribute this to pilot error. I must have screwed up the initial pairings between my car and my Nexus 6. I deleted those pairings and redid them. Now my phone connects automatically when I start the car.
So, in the words of the late, great Gilda Radner on SNL: "Never mind."
I have the same problem. PITA!
My new (10 Dec 2015) 6P will not discover any of my Bluetooth device, must less connect