I posted this on the CM7.1 stable thread, but I think it would be better answered here.
On stock rom, I had my phone setup to my car's nav system. When I streamed audio over bluetooth using the stock Music program, the car's display showed the artist, track, and album. CM7 nightly did not, and neither does this version. Is there some way I can get that functionality back? The streaming works perfectly though. Just no information is sent over.
My previous phone (Jailbroken iPhone3GS) automatically connected to my car when I turned her on. (the car). This phone running CM7.1 stable does not. Anyway I can change that? I have to go to wireless settings, go to bluetooth, and then connect to my car manually. I haven't changed any settings in my car since I used it on the stock rom (which auto-connected)
Blaze9 said:
I posted this on the CM7.1 stable thread, but I think it would be better answered here.
On stock rom, I had my phone setup to my car's nav system. When I streamed audio over bluetooth using the stock Music program, the car's display showed the artist, track, and album. CM7 nightly did not, and neither does this version. Is there some way I can get that functionality back? The streaming works perfectly though. Just no information is sent over.
My previous phone (Jailbroken iPhone3GS) automatically connected to my car when I turned her on. (the car). This phone running CM7.1 stable does not. Anyway I can change that? I have to go to wireless settings, go to bluetooth, and then connect to my car manually. I haven't changed any settings in my car since I used it on the stock rom (which auto-connected)
Click to expand...
Click to collapse
Probably one of the limitations involved in how they got A2DP working in the first place.
Remember that A2DP didn't work at all until a few days ago (and I think it was nonworking on the I9100 for a few months.)
Alright, so there's nothing I can actually do to fix the issue? That's fine, it's not a huge inconvenience.
Sent from my Galaxy S2 i777 CM7 Nightlys
Yeah, you're just going to have to wait for CM to be updated.
Related
Scroll down I resolved other problem, but I have another now lol.
My 2012 Yaris stock radio bluetooth will not let me adjust the volume on my radio when I am streaming music.
When I use anything with sense on it, it is okay, but when I try using ASOP or anything without sense; it is not
Suggestions?
Did you try reflashing the ROM after a full wipe?
Thanks! That worked!
I just need to figure out why my car volume for music streaming through bluetooth isn't working
Would you know? ^_^?
EDIT: It was working with the HTC music player no problem, but when I switched to liquid; my phone uses google music now, so that could be a reason. Any ideas how I could switch to the HTC music player or some other one to set as default?
Do phone calls work through Bluetooth?
Typically when you flash/re-flash a ROM you have to re-pair the phone to the car. The car will most likely remember the phone but you would have to Allow the car to read data from the phone.
emptyshell said:
Do phone calls work through Bluetooth?
Typically when you flash/re-flash a ROM you have to re-pair the phone to the car. The car will most likely remember the phone but you would have to Allow the car to read data from the phone.
Click to expand...
Click to collapse
Yeah I re-paired it. Still no good
I have a 2012 Yaris with a stock radio that has bluetooth. I am going to try a ROM with sense on it and see what happens.
Going with InfectedROM eternity to see first.
EDIT: Okay with sense the streaming works no problem and my radio says streaming audio, but without sense or on liquid; my radio only says BTA
I don't know anyway around this I really like liquid too!
Okay, so I somewhat figured out the problem.
My phone running on liquid does not let me put the "pairing code", so this might be stopping my phone to directly connect to my car stereo.
Any suggestions on fix?
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
I just installed CyanogenMod 10.1.2 Stable (via SafeStrap 3.11), everything went perfect. A couple days later, I finally went to re-sync my phone to my PriusV's Entune system to play music via Google Play Music (with playlists stored locally on the phone).
Music plays back OK, however my issue is that no song details (Track title, artist name, disc name, playback position) will display on the Entune screen, and none of the car's control buttons (play/pause/next track/prev track) will do anything. I don't want to have to pull out my phone to change tracks or see what song just came on while i'm driving when this is what the details and controls on the car are supposed to do for me.
Anyone out there have any thoughts/ideas/suggestions/possible fixes?
neoramasay said:
I just installed CyanogenMod 10.1.2 Stable (via SafeStrap 3.11), everything went perfect. A couple days later, I finally went to re-sync my phone to my PriusV's Entune system to play music via Google Play Music (with playlists stored locally on the phone).
Music plays back OK, however my issue is that no song details (Track title, artist name, disc name, playback position) will display on the Entune screen, and none of the car's control buttons (play/pause/next track/prev track) will do anything. I don't want to have to pull out my phone to change tracks or see what song just came on while i'm driving when this is what the details and controls on the car are supposed to do for me.
Anyone out there have any thoughts/ideas/suggestions/possible fixes?
Click to expand...
Click to collapse
I have a Highlander without Entune (Stock Stereo), so it's not a direct comparison but here's what I found. Music details don't display on the stereo. I've tried countless apps/hacks but nothing has worked. They spent all their dev $$ on getting it to work on the iPhone and left Android users in the dust. So I'm not sure music details have ever worked with Android.
The steering wheel controls however work fine for me, so that's strange. In the bluetooth settings on the phone, when connected to the stereo, is 'media' connected? It should be.
I wonder if an updated bluetooth controller for android would fix this issue for everyone?
I suppose I should clarify a bit - when i mentioned this being after installing CyanogenMod 10.1, I was assuming that one would take it things were working under stock, which was the case.
So: Stock - bluetooth playback showing track/artist/disc information, position in the song, and car controls worked (though stock had an older version of Google Play Music, so this could also be a source of conflict)
CyanogenMod: bluetooth only plays music, does not display any of the other information, and controls do not work. (Cyanogen 10.1 comes pre-built with the newer version of play music, so downgrading would be.... difficult and i'd rather try and make it work without doing so)
I guess what I want to try and find out is if it is CyanogenMod or Google Play Music's new version that is next to incompatible with Entune. With Stock, I had near 100% functionality (only shuffle/repeat toggles did not work - but even those don't work right with my wife's iPod, so i'm not worried about those functions).
Since i'm essentially dual-booted through SafeStrap, I may try going back on Stock, updating Play Music, and testing - if updating Play Music causes Stock to loose functionality equally, then i guess i'll have my answer - obviously i'll post back with results.
If functionality is still present on Stock after updating play store, then that traces it back to being something with Cyanogen, and the bluetooth driver it uses.
OK - sorry for the back to back posts, but I got lucky on some digging and found my answer.
CyanogenMod does not have something called AVRCP (Audio Video Remote Control Profile) revision 1.3+ built into it's bluetooth stack. This is because that is not something that is included by default under AOSP 4.2.x. So unless you want to build your own bluetooth stack and put it into Cyanogen, you're not going to get track info/controls.
Google has announced that under AOSP 4.3, they will be building Bluetooth version 4 support into Android, and version 4 supports AVRCP 1.3+ natively, thus Cyanogenmod's next version based off of AOSP 4.3 will then contain AVRCP support.
So, the short of it is, hang in there for the next major release of Cyanogen and all will be resolved!
Most manufacturers build AVRCP support into the bluetooth stack for their devices, hence why stock worked and now CyanogenMod does not.
Huh good to know. I knew that Android 4.3 included an upgrade to BT, but I didn't realize it would fix this issue. I wouldn't even know how to build my own BT stack, but it would be useful in the long run.
+1 on this
I have a Nexus 4 with CM 10.1.2 connected to my Skoda Octavia built-in bluetooth. I play music with Apollo (Cyanogenmod's music player) and I get to hear the songs and can skip to the next/previous songs with steering wheel controls but don't get to see the song title/artist info.
My Nexus One with CM 7 however does play music fine and shows all song details and steering wheel controls work fine.
So based on 1.) the fact that my 3.5 year old Nexus One (with CM 7 - Android 2.3.7) shows song details fine and 2.) the excellence of the CyanogenMod team, I think this can be resolved with some coding rather then waiting for Android 4.3 or CM 10.2 with an updated bluetooth stack.
Unfortunately I can't say if this issue only started appearing after the 2 security updates (10.1.1 and 10.1.2) since CM 10.1.2 was the 1st ROM I flashed on my Nexus 4. Although in this post goo.gl/KQ6J7H some guy who encounters the same issue, also experienced the issue on CM 10.1 (so before the security updates 10.1.1 & 10.1.2).
Apart from the song details not showing, I also noticed that sometimes I can't enable bluetooth at all and need to reboot my phone for it to work again. When tabbing the bluetooth icon in powercontrol widget or even directly in Settings it simply won't enable bluetooth. Also experienced by the guy from post goo.gl/KQ6J7H
I'm hoping to see this annoying bluetooth issue resolved asap.
Strange new problem...
I use a bluetooth car stereo, and on my phone I have "Smart AudioBook". Basically what happens it, when I start the engine, the phone and stereo sync automatically and it starts playing my audiobook from where it left off. When I turn the car off, it stops.
This all worked fine when I was using a previous ROM (one of the SuperNexus ones, 4.2.2 I think).
I recently changed my ROM though and upgraded to the CM10.2 jellybean 4.3 rom.... but there was some pretty terrible battery issues, and the bluetooth problem started. (Which ill describe below).
I thought it might be a ROM issue though so I tried SlimBean (another jellybean 4.3 rom) and that fixed the battery problem, but the Bluetooth issue was still there... but I couldnt see ay other references to 4.3 causing bluetooth problems (they were apparently all in 4.2, though I never had an issue before..)
THE PROBLEM:
The book will play normally, for a couple minutes or so, but then suddenly the audio will stop, and the stereo screen will say "paused". But if I look at my phone screen, the audiobook is still running (silently thought). I cannot unpause it using the stereo button.
BUT.. if I actually pause it on the phone screen, THEN I can unpause using the stereo and it will start playing through the car speakers again.
This cant be a problem with the stereo, as nothing has been altered on it. This is clearly an android thing.
I am considering one of the 4.2.2 ROMS to install next, and see if that solves anything, but I was wondering if anyone out there had any thoughts on other ways to fix this?
Thankyou
Bluetooth and cm dont mix. 4.3 is still in early stages. Best bet is custom stock based 4.1.2
This has bin covered alot.
--------------
alliances+siyah
I'm going backwards on the CM builds until it stops, but based on info from their wiki it doesn't work on any version so I might be wasting my time...
The big question is has anyone got a ROM with stable bluetooth or am I going to be stuck with going back to the AT&T ROM ? I was also hoping someone baked in the power saving menu/settings from the ATT ROM into something else?
What are you connecting over Bluetooth?
Most the 4.3 roms I've tried had little to no problem with Bluetooth. At most I had to reboot once a day to connect my Bluetooth stereo headphones.
Just A2DP profile devices, my vehicle and 2 speakers and a set of headphones. After about 6 connections/disconnects is when it dies, usually after I connect and hit play; there's no audio and shortly after the app pauses and the BT status icon vanishes. Going into the control panel it acts like BT is off and won't turn back on.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
BlownFuze's AOKP rom is supposed to be very good on bluetooth. At least that's what I've read in that thread. I'm just not a fan of AOKP so other than flashing it and going through the settings to see if it has what I want I really haven't used it more than a couple of hours at a time.
unless something has changed in the last month it looks like new roms are all going to have this issue. It is my understanding that we dont have teh proper "driver" support for 4.2+. I remember this being an annoying issue seeing how i connect and disconnect from bluetooth min of 6 times a day. 4.1 roms and earlier do not have this issue.
I've never had any bluetooth issues with BlownFuze's AOKP build.
I hate to jinx it but I've been downgrading incrementally using the built in CM tool (no wipes) and on the oldest version its finally stable with BT.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
another +1 for the KK version of AOKP.
i'm also not a huge AOKP fan, but it's the only rom i've used with stable bluetooth
edit: patch adams' liquidsmooth has the bluetooth working, but it does seem to die on me from time to time, listing bluetooth as off, and attempts to turn it on are futile. it just switches right back to "bluetooth off"
Padawan (4.1.x) has stable bluetooth
Current CM versions that I tested (Beanstalk and liquid Smooth) crash instantly when my car tries to access messages via BT
PAC Rom is the first kit kat 4.4.3 version that doesn't crash immediately with my car's bluetooth but I LOVED some of the Beanstalk mods.