Database Develop

Car Bluetooth

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?

Unresolved Bluetooth issues since 4.2

The issue of Bluetooth devices not connecting and speakers dropping out was a hot topic when the 4.2 OTA came out, and to the best of my knowledge, the 4.2.1 update did nothing to fix it. Since then, I've read dozens for reported "Bluetooth fixes" for various Nexus devices (and I've tried most of them), but this is still a major unresolved issue for a lot of people. My gamepad and mouse refuse to hold a connection since the update, so after banging my head against the wall for a few weeks I reverted to 4.1.2.
Has anyone found an actual fix for the Nexus 7, or have there been any reports of when Google might respond (I've read several reports that Google tech support claims to not even be aware that a problem exists)?
For the record, I've tried the following:
- Fix permissions
- Disable all devices, clear Bluetooth Share cache... reconnect devices
- Perform a full wipe and install the 4.2.1 OTA.
- Install custom ROMs or kernals
- Disable wifi when establishing the initial device conection.
- Sacrificed a young goat at midnight on the winter solstice.

ED2O9 said:
- Sacrificed a young goat at midnight on the winter solstice.
Click to expand...
Click to collapse
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2

I also had big bluetooth issues in stock 4.2.1. I have since changed quite a few things on my nexus7. Somewhere along the way, something I did seems to have fixed the issue. I didn't do any tests along the way, so I can't tell with any certainty which changes had any affect. All I can say is stock 4.2.1 bluetooth was completely and utterly broken, and what I have now doesnt have any bluetooth issues that I've noticed. I am able to stream music over Pandora (WiFi) and listen to it over bluetooth now without any interruptions.
So, here's a brief description:
CM10.1 nightlies + gapps, using the default kernel, no over/underclocking or anything like that.
wifi is always turned on, gps is always on, nfc is always turned off
About half of the gapps and a few of the default apps I have disabled. I have no proof to back it up, but I believe constant syncing and phoning home from these apps may have something to do with the issue. Calender, Exchange Services, Face Unlock, Calender Sync, One Time Init, Partner Setup, Play Movies & TV, and Play music are all the apps I disabled.
I also purposefully avoid other apps that run constantly chewing up battery and sending data to the internet like the facebook app.

Nope, nothing fixed it for me, aside from downgrading to 4.1 (which uses the Bluez bluetooth stack, rather than the Broadcom one in 4,2)
It's possible that CyanogenMod 4,2 (CM10.1) uses Bluez, and not Broadcom. I asked in the dev section, but nobody knows it seems.

bsoplinger said:
Did you check and make sure it was a virginal young goat before you sacrificed it? :angel:
Sent from my Nexus 7 using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.

ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I have had success with an old Dell XPS bluetooth mouse. Scrolling was fast and paired immediately.
No luck with Plantronics M100 headset. Nexus 7 could see it but no joy...
Maybe we need a list of what really works after 4.2.1?

More bluetooth
ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
Got my N7 2 weeks ago. Never had a chance to run on anything but 4.2.1 since first thing it updated. My bluetooth is not usable. If trying to stream video the audio is so bad that you cannot decipher anything. With music it is better but will start stuttering and becomes unusable. Same devices work fine with my Verizon Galaxy Nexus running 4.1.1.

ED2O9 said:
The goat said she was a virgin, but you never know.
I'd be very interested to see exactly how widespread this issue is. Are the people reporting issues the small minority, or are they just the only ones attempting to use a bluetooth device? If you're reading this and are running 4.2.1, but have never connected a Bluetooth device, please try to do so in the near future and post your results. Based on the number of forums claiming that Bluetooth is flat-out" broken, I'm thinking that most people don't even realize that it's a problem.
Click to expand...
Click to collapse
I for one was completely unaware of the 4.2 bluetooth problem until I got a pair of bluetooth stereo earbuds from Audiosynq for Christmas. I got them paired and working, but the audio kept dropping out, only to come back a few seconds later. Very annoying when you are trying to listen to music But the earbuds worked flawlessly when I used them with my Samsung Galaxy Player running Gingerbread. That was my first clue that something was amiss....

Same stuttering for me with my jambox. Clearing blue share data helps it and seems to keep the problem away for a while.
Sent from my Nexus 7 using Tapatalk HD

The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars

I've been using Paranoid Android with my Bluetooth controllers and my new Motorola stereo headset.
Honestly I expected problems with the audio and have not. In fact I'm very impressed by the range. I can pretty much walk anywhere in my house without the music skipping. Of course this is streaming Pandora... so the bitrate may be lowered for streaming but whatever. Still impressed.
I'm not saying Bluetooth doesn't have its problems with 4.2 but perhaps a wipe will fix it. They did change Bluetooth protocols and there could be some remnants leftover screwing with us.
My moga controller had lag but I found that problem being caused by the Moga Pivot app. Using the universal driver fixed it right up.
Sent from my Nexus 7 using XDA Premium HD app

I had the same problems with stuttering Bluetooth over audio, then I thought it was fixed with the latest update - but I was wrong.
In my case at work I have a very weak WiFi signal, and it drops in and out and that's when my Bluetooth over Audio plays up. If I disable WiFi it's better a lot better but still not 100%. I get better results in the same environment with my Desire HD running ICS than the Nexus, which is quite disappointing

gianptune said:
The issue is widespread enough to have 400+ comments on the bug tracker.
http://code.google.com/p/android/is...ed&colspec=ID Type Status Owner Summary Stars
Click to expand...
Click to collapse
People should click the star and leave it at that, rather than whinging, complaining, and making **** up. But yeah, 620+ stars on that bug.

4.1.2 works, had to go to that

A2DP snicking and distortion driving me crazy!

Hi all, I have tried searching around and haven't managed to to find anything even remotely similar (if such a thread exists, I apologise and I would appreciate being pointed in the right direction), So i'm posting as a last resort, I really hope somebody is able to help me.
I am experiencing a lot of random "snicking" and clicking over btaudio A2DP between my xperia Z and my 2010 camry hybrid. The snicking is not present in bt calls, just bt audio playback. I have not experienced this problem with any of my older phones in the same car (iphone 4, 4s, sgs, sgs2, sgs3 have all been without issue).
The snicking is most noticeable in quiet or silent parts of a song, although lately from time to time it will progress from quiet snicking into full terrible distortion on every beat requiring me to pull over, unpair the phone, powercycle both the car and the phone and re-pair everything to get it back to something that is listenable.
I am using poweramp, but have tried several different music players to rule out the possibility of it being the player.
Has anybody encountered this, or able to help me troubleshoot it?
I am using a completely stock xperia Z, no mods whatsoever.
Thank you in advance for your time and assistance.

*bump*
surely there is somebody here that has an idea of whats going on?

dvcelica said:
*bump*
surely there is somebody here that has an idea of whats going on?
Click to expand...
Click to collapse
Are you using the Walkman app to play songs as a default player or at least have you tried... then I if problem is still there I would seek the advise of the shop from where bought ...

zalman360 said:
Are you using the Walkman app to play songs as a default player or at least have you tried... then I if problem is still there I would seek the advise of the shop from where bought ...
Click to expand...
Click to collapse
Thank you for your reply, I have tried with poweramp, and the standard walkman app, both have the same problem. I tried my wifes xz on the car and it was much much worse (dropping out, freezing etc) So I can only assume sony (or telstra) have screwed up the a2dp as it works completely fine in calls.
I might try dropping something non branded on it and see how it all goes.
Thank you for your time.

Bluetooth audio - No Sound since OTA update to 4.1.7

Hi guys,
I searched the web and found a few references to this but for previous versions and no real solution
I have used Bluetooth audio in my car daily with Spotify on my 3T but since I OTA upgraded to 4.1.7 from 4.1.6 the other day there is no sound when Spotify or any other media player is playing in my car via Bluetooth audio. The car says Unknown Track and Unknown Artist but the car can still control going to the next and previous songs in the Spotify app on the phone meaning the connection is working. The 3T thinks it is playing the songs in Spotify and I can pause and play it from the car controls. There is just no sound. Is this a common issues or is it just me? Is there any way to fix it? I saw somewhere it was a Nougat issue, does that mean even another ROM might have it? I'm hoping there is a fix that doest mean wiping my phone
Thanks

Hi,
I have exactly the same problem. I tried everything, but no sound comes out of my speakers. Any ideas?

For everyone consulting this Thread for the same issue, It has been noted by Devs at OnePlus, and they're working on it. It has been affecting many users.

thes3usa said:
For everyone consulting this Thread for the same issue, It has been noted by Devs at OnePlus, and they're working on it. It has been affecting many users.
Click to expand...
Click to collapse
Thanks. Is there a thread somewhere for that info, so I can keep an eye on it?

brimur said:
Thanks. Is there a thread somewhere for that info, so I can keep an eye on it?
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/bluetooth-audio-issue-after-4-1-7-update.617395/
https://forums.oneplus.net/threads/bluetooth-problem-3t-since-4-1-7-update.615482/
https://forums.oneplus.net/threads/no-bluetooth-audio-in-bmw-since-update.613055/
Appears to affect certain car (head unit) makes. 4.1.7 works fine on my Subaru (Kenwood head unit).

Bluetooth to car no track ID

Just got my pixel 5. When connecting to the car via Bluetooth it's not coming up in the car display what track it is and I'm unable to skip to next track using steering wheel controls. Worked perfectly fine on my Mate 20 pro. Any ideas please? It's driving me mad.

Have yours all connected correctly those that are trying it in cars? This is a deal breaker for me so if not a simple fix it's going back.

Same thing happened here, using Spotify. Weirdly it works on my Pixel 2 XL but not on my Pixel 5.

I've reached out to Google to try find out why. Glad it's not just mine at least.

I have just come across this thread before I posted my own. thank God I'm not the only one who is annoyed as I started to think I was going crazy.
This is an absolute deal breaker for me as well. OP what have you done in the meantime? Have you found a workaround? I have even tried downloading 3rd party bluetooth "manager" apps from the play store but had no luck.
Skip, restart, steering wheel functions don't work and options are greyed out on cars infotainment touch screen.
Didn't have this issue on Pixel 2 Android 10.

Yes i found a work around today after reading through many other forums about other phones.
Basically enable developer mode and then change the AVRCP Bluetooth version to 1.3. Turn off Bluetooth then back on again and hopefully yours will work like mine.
I'm not sure what this does or the disadvantage to doing this but I've found connection better this way also. Let me know how you get in.

You can thank android 11 for that.

I think that what is happening here is that some apps haven't yet caught up with changes and advances in the underlying subsystems in Android 11. One that has is VLC. It is working perfectly for me. (I've tried others that didn't so I'm sure this isn't a bug per se)
It's a little disappointing that more effort wasn't put into maintaining backwards compatibility. However, that can often be very difficult, and sometimes impossible, to achieve.
Personally, I don't think that reaching out to Google about this will do any good.
Sent from my Pixel 5 using XDA Labs

Tcukcufc said:
Yes i found a work around today after reading through many other forums about other phones.
Basically enable developer mode and then change the AVRCP Bluetooth version to 1.3. Turn off Bluetooth then back on again and hopefully yours will work like mine.
I'm not sure what this does or the disadvantage to doing this but I've found connection better this way also. Let me know how you get in.
Click to expand...
Click to collapse
I have done this and it had started working. Massive relief, thank you.

Tcukcufc said:
Yes i found a work around today after reading through many other forums about other phones.
Basically enable developer mode and then change the AVRCP Bluetooth version to 1.3. Turn off Bluetooth then back on again and hopefully yours will work like mine.
I'm not sure what this does or the disadvantage to doing this but I've found connection better this way also. Let me know how you get in.
Click to expand...
Click to collapse
You are my absolute saviour! I didn't realise there was a way to revert the Bluetooth version. I thought I was just going to have to wait for a patch!

Tcukcufc said:
Yes i found a work around today after reading through many other forums about other phones.
Basically enable developer mode and then change the AVRCP Bluetooth version to 1.3. Turn off Bluetooth then back on again and hopefully yours will work like mine.
I'm not sure what this does or the disadvantage to doing this but I've found connection better this way also. Let me know how you get in.
Click to expand...
Click to collapse
Thank you for this info. I'm not sure it's necessary, but I'd also recommend after changing this setting, reboot your phone and delete and re-pair the phone to your radio.