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?
It's like the elephant in the room around here. The bluetooth service on 2.1 is some crazy, broken crap. No matter how many times and how many ways I try to get it to pair to my brand new Kenwood x994 it refuses to save. It will eventually link up BT audio if I search for devices and let the pairing fail, but what a PIA to mess with every time I get in the car. I rolled back to Fresh 1.1 today and I had it paired and working perfectly in 10 seconds.
So here is the question, can we put the 1.5 BT stack into the 2.1 ROM? I already tried the 1.5 libbluetooth.so in the /system/lib filesystem, but it didn't change anything about the pairing problem (obviously I have no idea what I am doing and stabbing blindly at anything bluetooth related).
Anybody have any ideas? Is the BT compiled into the kernel? Can we recompile it with the 1.5 version?
I've asked this question a few times already and the answers are usually 'no'. Gawd I wish we could as no 2.1 roms (I've tried almost all of them) will pair voice (audio is OK) with my Pioneer Avic D3 car radio. 1.5 works perfect
Mine works exactly the opposite. The hands free phone works perfectly, but the phonebook doesn't download and BT audio fails to connect.
It sounds like it may be your phone, your should update with the official 2.1, then take it to a sprint store and have them replace it.
My phone has worked flawlessly to my jeep stereo with any 2.1 rom I have used in the last several months.
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
djorijun said:
So this whole time I thought it was because we had a leaked version, but is this the official ROM that still has this problem. It's not the device cause I've had it replaced twice and my wifes doesn't work either.
I am not able to connect to my Pioneer AVH btw.
Click to expand...
Click to collapse
I agree, if it was the hardware it wouldnt work with 1.5 either. Besides, Dan Hesse is my boss. He'd get hacked if I took back my phone
Thread moved.
I recently got my new Renault Scenic car and discovered a rather strange situation.
The phone pairs with the carkit and connects the first time without issues and works like a charm.
But however when I start the car and thus also the carkit the phone connects also but no audio is heared trough the carkit when calling or getting called. The phone says it transfers the connection to the carkit but nothing is heared.
It only works when I have bluetooth off, starts the car and then turning bluetooth on the phone on. Wait till it connects and make a call. With this procedure the connection is good till I step out the car.
Its a work around but hmmm not the one i would love to.
I have a nexus one rooted with the latest MCR (21) and an intersect kernel. Though I tried different kernels also but no go.
Hopefully one of you guys have an idea
Ok I searched a bit and found out the Bluetooth is done with the opensource code Bluez. So I wonder which version of Bluez is in the froyo roms and how it can be updated if possible to a new version.
Anyone knows ?
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
igalan said:
I feel your pain, I have a Renault Grand Scenic III (purchased last December) and the hands-free is unreliable, but music streaming (A2DP) is even worse as most often than not it will fail to connect.
I have to say that the hands-free works fine most of the times (for the phone part, not for music), but some days it will refuse to work no matter what. Since it isn't working much better with my wife's Nokia (BTW, which I had to do a firmware update or else it went into a permanent reboot loop when connected to the car-kit), I assume the problem lies on the car, not on the phone. I have yet to see if my Hero, which has been recently updated to Android 2.1, behaves any better. A firmware update on the Bluetooth car-kit seems a better approach, but I'm unaware if one exists since after some digging it seems my car doesn't use the OEM Parrot kit that other earlier models carried.
Click to expand...
Click to collapse
Hi,
I've just come across your post. Did the situation improve ?
I'd just point out that for me it comes from the Android system : I own a Renault Mégane 3 and was able to fully use the bluetooth system with my HTC HD2 (Windows Mobile 6.5). Now, I've just installed Android 2.2 on it and I encounter a similar behavior... and the car can't connect to the phone directory either...
Looks like I'll boot back on Windows Mobile when driving...
Regards,
Stéphane
My Hero with the official 2.1 ROM is now 100% reliable. The Nexus One with Froyo isn't, A2DP is still hit & miss.
Well... I'm getting the same but not with Renault ones.
I have LiquidAUX on my car and to have both phone and a2dp synced, I have to restart phone BT and LiquidAUX every time I go into car. And most of the times I can only have 1 connection each time, or phone is on and a2dp is off or a2dp is on and phone is off. It's really annoying since I had an HTC Hero with Android 2.2 and it used to work with no problems...
Hello, I've the same issue with my new Renault and Nexus LG. The phone pairs with the carkit and connects the first time without issues and works like fine. Once someone calls, the connection is terrible or lost! I checked the phone compatibility list at Reanoult and the NEXUS LG is on that list. So it should work. Updated R-link2, same issue. I went to the Renault garage and they told me that this is a bug in the Renault software, they can't do anything about it. Can't believe this, there should be a solution or fix.
Any of you guys, who experience problems with your bluetooth headsets? I've got a Plantronics Discovery 925, which i've have paired, but the sound want passthrough it. When i pair it, it normally doesn't ask for the passcode, but have gotten it to, but either if it get the passcode or not, it's only working if i make a call directly after pairing it. After that, all other calls aren't pass through. I'm running on MaDaCo custom rom, but the problem was the same on stuck rom.
Works perfect A2DP using my Bury Hands free car kit 9020
seems like i got i working, have updated my baseband, but don't know if that could have had an effect on it. But quite happy to get it working
My N1's a year old, and recently it's developed an issue where A2DP stereo headsets stutter profusely with any sort of music, even when I'm right next to the device.
My headset and car audio pair fine with both my N1 and my Desire, but the N1 stutters like hell even in close range, whereas the Desire works freely throughout a room or the car.
I'm using CM7 and even switched to CM6 to test after numerous people reported it's a new BT stack in 2.3.3 that's causing the issue, but the problem still thrives.
Any suggestions on what to do?
Even flashed back to a stock EPE54B unrooted image. Same problem.
Radio issues, perhaps?