Does anyone know of a 4.2.2 ROM that has working 4G/LTE and supports Bluetooth AVRCP?
(I.e., when you play music in car over bluetooth, you get artist/track info on your dash.)
Last I checked only TW had this, CM was working on it ...
AVRCP for 4.2 roms
Same issue for me as well. Using the recent version of Liquidsmooth hoping it had it but not so much. Such a Debbie downer in the car especially when your ROM kicks ass. The quest continues.
Related
I searched and couldn't find another thread about this so here goes...
Got a new bluetooth car stereo and my music and calls sound great, but my EVO doesn't transfer the track title/artist/album info to the stereo for some reason. I know it's not the stereo itself as my friend paired his BlackBerry and it showed the track titles. Tried this in stock music app, DoubleTwist, PowerAMP and unrooted on 2.2 and rooted w/CM7. Thanks in advance!
EDIT: Possibly just answered my own question but if anyone can confirm that would be great...it looks like the EVO only supports AVRCP v1.0 so far?? And if so, is there any way to upgrade the BT profile to 1.3 or 1.4 to allow for metadata transfer? Again, thanks in advance.
Yeah... the evo bluetooth profiles fail.
I'm currently using PowerAmp and love it...I know that metadata xfer is and has been working for stock player for a while, but does anyone know if this feature is available on any ROM besides AOKP? They're dropping support for us :crying:
bwaredapenguin said:
I'm currently using PowerAmp and love it...I know that metadata xfer is and has been working for stock player for a while, but does anyone know if this feature is available on any ROM besides AOKP? They're dropping support for us :crying:
Click to expand...
Click to collapse
bump
If you're using a new phone with bluetooth 4.0, AVRCP 1.3, metadata transfer will not work until the music player devs update their programs. A rooted phone may work. For non rooted we are at the mercy of the devs, and poweramp has been promising an update for over a year now.
I have a problem with my Bluetooth headset Jawbone Icon with all firmwares on Android 4.0.4 with Sense 4.x.
For example, last Sabsa 10.1, I pair my headset with the phone, it works fine with music or video players, but the do not send any voice signals while talking. My opponent can't hear me and I can't hear him by Jawbone Icon.
Instead of this my old headset works fine, it is Nokia HS-4W.
Nokia HS-4W has Bluetooth 1.1 - works fine.
Jawbone Icon has Bluetooth 2.1 - does'nt work while calling.
Has this trouble a solution?
gpa_76 said:
I have a problem with my Bluetooth headset Jawbone Icon with all firmwares on Android 4.0.4 with Sense 4.x.
For example, last Sabsa 10.1, I pair my headset with the phone, it works fine with music or video players, but the do not send any voice signals while talking. My opponent can't hear me and I can't hear him by Jawbone Icon.
Instead of this my old headset works fine, it is Nokia HS-4W.
Nokia HS-4W has Bluetooth 1.1 - works fine.
Jawbone Icon has Bluetooth 2.1 - does'nt work while calling.
Has this trouble a solution?
Click to expand...
Click to collapse
you should flash another rom, like jellytime or codefirex periodical, if you want to use ICS you must flash aospX by existz
good flash
Superuzzu said:
you should flash another rom, like jellytime or codefirex periodical, if you want to use ICS you must flash aospX by existz
good flash
Click to expand...
Click to collapse
But I want to use Sence 4.x
Superuzzu said:
you should flash another rom, like jellytime or codefirex periodical, if you want to use ICS you must flash aospX by existz
good flash
Click to expand...
Click to collapse
Watchout for changing roms.
In this Your BT connection failed (wierd, my car phone set connects, and I can talk all the time) but in another, like R29 cm10 based ROM http://forum.xda-developers.com/showthread.php?t=1778202 YOU'RE NOT ABLE to change GSM NETWORKS MANUALLY. So it's worse.
In http://forum.xda-developers.com/showthread.php?t=2003273 there is still no BT developed...
bestfil said:
Watchout for changing roms.
In this Your BT connection failed (wierd, my car phone set connects, and I can talk all the time) but in another, like R29 cm10 based ROM http://forum.xda-developers.com/showthread.php?t=1778202 YOU'RE NOT ABLE to change GSM NETWORKS MANUALLY. So it's worse.
In http://forum.xda-developers.com/showthread.php?t=2003273 there is still no BT developed...
Click to expand...
Click to collapse
mmmm....
now headphone button a Bt. work fine on Sabsa Prime with new Kernel Beastmode (here ) or if you want tou should flash a new Viper Rom 1.2.2.
Have a good flash
Bluetooth headset issue fix (no call sound):
Delete your headset name from the list /system/etc/AudioBTID.csv
For example, for my Jawbone ICON i deleted the string "Jawbone ICON,1411,1511"
Now my headset works fine, I can call and speak through my headset.
Can anyone get audio data to stream on to their car via Bluetooth? I've never been able to get it to work regardless of player, phone, or rom.
Samsung Galaxy Nexus
Running CM 10.1 toroplus nightlies (20130224)
Car: 2013 Ford Mustang using SYNC
Tried PowerAmp
Tried Pandora
Tried PlayerPro
Tried Play Music
Tried Winamp
Tried Apollo
It is my understanding that CyanogenMod 10.1 (Android 4.2.2) has Bluetooth AVRCP 1.3+ so this stuff should work.
RandoTheKing said:
It is my understanding that CyanogenMod 10.1 (Android 4.2.2) has Bluetooth AVRCP 1.3+ so this stuff should work.
Click to expand...
Click to collapse
CM10.1 does *not* have 1.3+, yet. Have a look at this: https://jira.cyanogenmod.org/browse/CYAN-20
RandoTheKing said:
Can anyone get audio data to stream on to their car via Bluetooth? I've never been able to get it to work regardless of player, phone, or rom.
Samsung Galaxy Nexus
Running CM 10.1 toroplus nightlies (20130224)
Car: 2013 Ford Mustang using SYNC
Tried PowerAmp
Tried Pandora
Tried PlayerPro
Tried Play Music
Tried Winamp
Tried Apollo
It is my understanding that CyanogenMod 10.1 (Android 4.2.2) has Bluetooth AVRCP 1.3+ so this stuff should work.
Click to expand...
Click to collapse
I had it working on my Galaxy Nexus running CM 10.0. I was using the Gonemad player on my JVC unit that I had installed in my Toyota Matrix. But now with 10.1 it no longer works as per the link mentioned above.
All I can suggest, is starring the issue... maybe google will eventually listen.
https://code.google.com/p/android/issues/detail?id=5450
It's currently the 20th most starred issue. I think it should be right up the top.
Same issue. Can only get music to play but no song title/album/etc. I did hear of one guy on a prius forum that got it to show, he used a different rom though. Thinks its liquidsmooth.
So is the reason it wont work because of an outdated bluetooth version?
roadrunnerx7 said:
Same issue. Can only get music to play but no song title/album/etc. I did hear of one guy on a prius forum that got it to show, he used a different rom though. Thinks its liquidsmooth.
So is the reason it wont work because of an outdated bluetooth version?
Click to expand...
Click to collapse
Actually a completely new bluetooth stack is the main reason the existing code can't be ported.
Sent from my Galaxy Nexus using Tapatalk 2
So its a software fix though right? Im hoping it gets with the whole google IO event coming up..
I have been running SkyNote 8.2 for a while now and have really liked Sean's ROM. I flashed Liquid last week (also a great ROM) and noticed something that I found confusing. With the TW Bluetooth (including the stock ROM), my 2009 car didn't really react well to the Bluetooth in my Note II. The connection between the car and phone would constantly connect and then drop off, connect again then drop off. Once I was on the phone (call), after initialing disconnecting me, the connection would stay but once I hung up it would go back to the on off cycle. My contacts would not sync either and yes I did grant access to the contacts. I just assumed it was because the phone has a newer Bluetooth profile (4) than my car (3). But after flashing Liquid my Bluetooth connection was fine, never dropped off and my contacts were all visible. I don't know much about the inner workings of Bluetooth, is the difference a TW thing?
Just looking for some insight from folks smarter than me.
Bump.... I would also like to know
AOSP only has Bluetooth 3.0 right now, so that's probably why you get more information. I have a FitBit and it only works with TouchWiz since it uses Bluetooth 4.0.
This is a fairly well known issue, but I haven't see a good summary anywhere, so I'll try here.
The problem isn't so much TW vs AOSP, it is Jellybean versions 4.1.x vs 4.2.x. Touchwiz is 4.1.2 and most maintained AOSP ROMs are 4.2.x.
Google, though their ultimate wisdom, decided to effectively castrate 4.2 by switching the Bluetooth stack.
From Android.com
New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
So...
Jellybean versions 4.1.x use the opensource BlueZ stack
Jellybean versions 4.2.x use the quasi-opensource Broadcom/Google stack called Bluedroid,
4.2.x has documented issues with audio streaming which are attributed to A2DP, or the Advanced Audio Distribution Profile. Google has proposed a fix, but the community consensus is that the issue remains.
Another problem with 4.2.x is that it doesn't support AVRCP 1.3 like 4.1.x did. This means that track metadata is not available to devices on 4.2. This is bad for me since I like to see track information when I connect the phone to my BMW M3.
I'm sure there are some workarounds on this problem, but I am not aware of a single, silver-bullet solution to make BT work flawlessly on 4.2.x Roms.
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Anyone know of any updates to this? There are so many 4.2.x ROMs out there that i love, but without a good BT A2DP connection, i just cant use that as the regular ROM.
ZoinksS2k said:
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Click to expand...
Click to collapse
I have been using the Google Edition ROM (4.4.2) on my M919 and things seem to be working great.
However, on calls, my call receipients notice a huge amount of echo/noise when I use Samsung bluetooth headsets WEP460 and HM 3700.
I tried a regular wired headset (Sennheiser CX275), and things work great! Even my car's built-in bluetooth from circa 2007 (which I believe has noise cancellation) works fine.
Could someone please give me some suggestions on apps to install or settings I could tweak to fix this issue?
Thanks in advance!