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.
Related
Hey guys,
I've got a Kenwood KDC-BT945U car stereo and I'm curious what other people's experiences are using the bluetooth for music. For all of you using a bluetooth receiver in the car, when you play music, does the deck display the Song/Artist/Album/etc.? Mine plays fine. I can pause/play, skip forward/back, etc. The only problem is when it comes to actually displaying the information on the car stereo.
Any similar experiences?
Ps. Besides this problem, the deck is a great complement to the phone. If I can get this problem solved, I can stop using the USB altogether.
I was going to post a similar thread about my issues with the KDC-BT945U. Thanks for staring it. Are you running a custom ROM?
Music for me shows no tag info. My main issue is that foryo is a nightmare when it comes to this deck. Both the deck and the nexus has major pairing issues using froyo. I have not tried 2.1 stock or Cyan's 5.0.7, I assume they work fine. I am no expert, but I think it's the new Radio in froyo causing the problem.
Surprisingly, Paul's desire ROM and this deck work very well for me.
Checking the website, there is a Bluetooth compatibility section. They do not list the nexus. I'm hoping for a firmware update for the deck.
I do have a 30gb iPod in the glove box hooked up via the rear USB and it does display track info on the deck.
Yeah. In my infinite wisdom, I bought a ZuneHD rather than an iPod touch. . . The only Kenwood stereo I could find that was compatible with the Zune was like twice the price. Not exactly doable when I'm 28 days away from being a daddy. lol That said, I'm just using a jump drive for the USB. That's been working flawlessly, tags included. If I can figure out how to get the phone to transmit tag info, then I can drop the need to carry an mp3 player (or have a jump drive hooked up) altogether. I love listening to music from the phone while using the navigation, for the sheer fact that it cuts the music off to make announcements. . .just need to get it working right.
Edit. Btw, I an running eViL's latest FroYo. Noir Tri.
Mi|enko said:
Edit. Btw, I an running eViL's latest FroYo. Noir Tri.
Click to expand...
Click to collapse
Can you tell me what firmware your deck is running? Mines 3.11
Also can you tell me what Radio you are running? Mines 32.36.00.28U_4.06.00.12_7
Thank you
verboten said:
Can you tell me what firmware your deck is running? Mines 3.11
Also can you tell me what Radio you are running? Mines 32.36.00.28U_4.06.00.12_7
Thank you
Click to expand...
Click to collapse
Same as you. Latest FroYo radio and 3.11 on the deck. Have since wiped and flashed Evil's latest Noir IV (FRF83 based) and still the same results. I have a 16 gig jump drive in there, so I have plenty of music. . . it just kind of sucks for the navigation piece. Phone calls are fine, because they'll interrupt any of the inputs. . . nav doesn't have that luxury. :-\
Thank you for the reply,
I have switch over to Kang-o-rama 0.9 Final (Froyo FRF83). My BT registering is a bit better, but nothing like Paul's R22 desire ROM was. With Paul's ROM, I was able to just keep my phone in my pocket at all times and when I started my car, as long as BT was turned on, my phone and deck synced every time. Now i'm lucky if it syncs at all. I have to constantly re-pair with the phone, and even that is very flaky.
Also, During audio, only 'BT audio' is displayed, no tags.
verboten said:
Thank you for the reply,
I have switch over to Kang-o-rama 0.9 Final (Froyo FRF83). My BT registering is a bit better, but nothing like Paul's R22 desire ROM was. With Paul's ROM, I was able to just keep my phone in my pocket at all times and when I started my car, as long as BT was turned on, my phone and deck synced every time. Now i'm lucky if it syncs at all. I have to constantly re-pair with the phone, and even that is very flaky.
Also, During audio, only 'BT audio' is displayed, no tags.
Click to expand...
Click to collapse
Did the desire rom display tag info? I have to repair all the time too. . .might be worth switching just for that.
Mi|enko said:
Did the desire rom display tag info? I have to repair all the time too. . .might be worth switching just for that.
Click to expand...
Click to collapse
Unfortunately, the desire ROM does not display tag info.
Unfortunately I'm pretty sure that sending the tag info for songs over Bluetooth isn't currently possible. It's a limitation in Bluetooth though, not your head unit.
I have a stock Nexus One and a Kenwood KDC-X994 and after trying unsuccessfully to figure out how to get my song info to show on the head unit I contacted Kenwood about it. They informed me it wasn't currently possible to do this via Bluetooth and that it was Bluetooth that had the limitation, not my head unit.
On a side note, ever since upgrading to Froyo (stock) my phone will only stream music via BT to my head unit with the stock music app, and this is very aggravating. Seems to be an issue with Froyo from seeing other user posts about this topic. I sincerely hope Google fixes this ASAP!
ranphi said:
Unfortunately I'm pretty sure that sending the tag info for songs over Bluetooth isn't currently possible. It's a limitation in Bluetooth though, not your head unit.
Click to expand...
Click to collapse
not true, my blackberry storm 2 sends all the song info to my kenwood kdc-bt945u. so the problem is in the phone software not the hu or bluetooth
where are we at on this? im curious as i should have an eris by friday and want to know how compatible it will be with my head unit
Huh. Interesting. I guess Kenwood was wrong, then.
NFrank89 said:
not true, my blackberry storm 2 sends all the song info to my kenwood kdc-bt945u. so the problem is in the phone software not the hu or bluetooth
where are we at on this? im curious as i should have an eris by friday and want to know how compatible it will be with my head unit
Click to expand...
Click to collapse
kenwood kind of pisses me off, i dealt with them a lot after i purchased the hd radio unit for the 945u. i was trying to find out why you cannot access the equalizer or any audio settings in hd radio mode (extremely annoying) he said you just cant. i wanted a more detailed explaination and he just made some bs up to get me off the phone. but yeah, just so you guys know, if you get the hd radio for you head unit you wont be able to adjust the terb/bass or anything on the hd radio src. all you get it the direct signal.
but does anyone know if this song info problem has been fixed? in an update or anything?
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.
I am having some very frustrating BT issues.
I only use one bluetooth device, a Kenwood KDC-BT945U car stereo. When using any vanilla android rom, the phone and deck struggle to work. They hardly ever pair and once it does, they never reconnect later and I must go through the process of trying to re-pair again.
Here is what I find odd. Any SenseUI rom that I have tried, the phone and the deck connect without issue.
My question is, would it be possible to take the bluetooth from Modaco's R23 and use it on CM6? Any advice?
Verboten
UPDATE.
I got brave and took the bluetooth.apk from Modaco's R23 ROM and pushed it to my phone running CM6 RC2 and my issues are 95% better. It works great but the phone wants to pair every time I get into the car. I wish it would auto connect but at least it is working.
That sucks. I have similar issues with stock Froyo. Just coming in to see if rooting and a custom rom would fix the issue.
Everytime I get into my car I have to turn off my bt on my phone and turn it back on for the radio and the phone to pair.
Not sure if its an Android issue(my Milestone did the same exact thing) or my radio(Clarion)
Even more annoying, is half the time as soon as the phone pairs with the radio it starts playing music. Not my preference that is for sure.
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
czechmate said:
Hi guys,
I am having problems with car BlueTooth hands free and Samsung Galaxy S:
With Eclair 2.1 it was working flawlesly, connected automaticlay after paired, I could make phonecals, receive phonecals, no quality issue, phonebook worked fine etc... The only problem was that once I did not swithced the BT on my SGS before starting to drive, for some security reasons the car was not searching for phones while driving, so I had to turn the BT in car off and on again and then it connected well. But overal problem free...
With latest 2.2 Froyo (i9000xfjp7) and also previous Froyo distributions (i tried JPA if I remember correctly), the phone can be paired, it connects to the car but after one phonecall it looses connection and works no more. The strange thing is, the BT icon on the phone shows brackets (like when connected) and also the car shows the phone is still connected. But phonecalls cannot be made via car HF and also cannot be received through it. Only by manualy accepting or dialing on the phone. And naturally the sound goes only via the phone, no HF.
The strange thing is, when I turn off the car and leave it, the phone says it is still connected to it, which is impossible.
Any ideas?
Thank you!
Click to expand...
Click to collapse
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Monu123 said:
Had exactly same issue I changed to Doc Rom JP8, for last 3-4 days didn't face any issue.
Click to expand...
Click to collapse
That is weird... When I switch back to Eclair, it works OK, back to Froyo, no HF after one phonecall...
I dont know how to work with ROMs, I managed to find out how to flash firmwares, I even handled many problems with Odin and its moods, incomplete flashes, etc... But I dont know how to use these custom ROMs...
Anyway, i would appreciate if someone told me how to resolve it without custom ROMs, as I plan to use offical Froyo when it becomes available, but with this issue, it is useless for me, as I travel a lot...
No one else?
I'm having a related problem.
I'm getting music stream cut outs (1 sec max) when streaming bluetooth to caraudio WHILE wifi on.
If i disable wifi, bluetoothaudio works fine. I know they share range bt/wifi, but this is unacceptable. They should negotiate. Everytime wifi scans, i get cutouts. Unusable. Only workaround is disabling wifi (and thats annoying because i have to be constantly activating/disabling it everytime i enter somewhere with wifi etc.
Using Docrom xxjpo v8 with voodoo.
Anyone has some software fix that makes wifi behave better when bluetooth musictream on?
I Drive BMW 328XI and for some reason when i pair the car with my LG Thrill, i lose the phone signal and the bluetooth disconnects for about 10 seconds then the ATT signal comes back on the phone then about 10 seconds later the phone pairs again for about 10 seconds and then the whole cycle all over again, and it will stay on for hours ..
no luck looking up anything online, i did find few ppl have issues on BMW and Audi cars with bluetooth, but nothing like my case tho!
any ideas or hints other than pair and un-pair the phone and deleting the phone profile from the car .. cuz i did that over 10 times and still no go!
Thank You!
!!!
anyone !!! ?? !!!
Sounds like an incompatibility issue between your car and the phone. I've seen issues with some of the phones and vehicles at my dealership (not BMW) that are almost exactly what you are describing. There won't be a fix unless the dealer (BMW) or the phone manufacturer comes up with an update. Hopefully Gingerbread will help you out.
Tried Thriller? I had bt issues with my headset dropping and reconnecting on its own on the stock rom. Haven't had an issue since I flashed Thriller.
Sent from my LG Thrill Faux G
Gr8Danes said:
Sounds like an incompatibility issue between your car and the phone. I've seen issues with some of the phones and vehicles at my dealership (not BMW) that are almost exactly what you are describing. There won't be a fix unless the dealer (BMW) or the phone manufacturer comes up with an update. Hopefully Gingerbread will help you out.
Click to expand...
Click to collapse
thats true .. i looked up everywhere and it said the same thing online, i have to wait most likely for the dealer to issue and update.
i even tried my trill on a rented car last weekend ( Camero RS 2011 ) and it was working fine.
so its the Car now, im sure.
quarlow said:
Tried Thriller? I had bt issues with my headset dropping and reconnecting on its own on the stock rom. Haven't had an issue since I flashed Thriller.
Sent from my LG Thrill Faux G
Click to expand...
Click to collapse
i had the same issue on
Stock
Root
Triller
i tried on every case and still the same issue!
moe87 said:
thats true .. i looked up everywhere and it said the same thing online, i have to wait most likely for the dealer to issue and update.
i even tried my trill on a rented car last weekend ( Camero RS 2011 ) and it was working fine.
so its the Car now, im sure.
Click to expand...
Click to collapse
Yea, it kinda sucks. I wish the car manufacturers would be more on top of these things.
My problem with my setup is that the Thrill's AVRCP is still at version 1.0 and only supports basic music streaming. It doesn't even support metadata. My 2 year old Tilt2 supports that. I wonder if custom ROM can fix that. iPhone updated the AVRCP from 1.0 to 1.4 with iOS5