Develop Bugs

[req] AVRCP 1.3 Bluetooth profile in source mode

Is there any possibility of implementing AVRCP 1.3 or 1.4 on our own instead of waiting for google? I pair my Incredible to my car stereo via Bluetooth and it would be nice to see the track information appear on the head unit display. It looks like it currently supports AVRCP 1.3 in target role, just not source.
http://source.android.com/porting/bluetooth.html

I would love this feature! I'll be willing to test anything.
Even more so, I would love for my phone to pair properly with my Alpine BT. If the phone has had the BT turned on fresh, and I get in the car - it will pair up without interaction and I can initiate a call from the radio. If I stop the car, get out and do something (gas station, errand, whatever) and get back in, turn the car on - the phone looks like it's paired but I will not be able to initiate a call from the radio. I have to do it from the phone or wait for a phone call to come in before it kicks over to the Alpine BT... (no previous phone had this issue, including the Eris, HTC Touch running Android or Windows, and Moto Razr)

I second this request.

Agreed. Hoping for a fix daily, but understand this may be a serious challenge.
For now, I've been switching back and forth between stock ROM and Cyanogen, where Cyanogen bluetooth without sense UI works fine for me. Specifically, I use the Wii remote software to control various emulators.
Sent from my ADR6300 using XDA App

bump......

Bump as well..

I don't have a way to test this, but just a thought --
In CM6, the latest nightly,
edit /etc/bluetooth/audio.conf
At the very top under [General] you see this:
Code:
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
Try putting source under Enable.
Worth a try <shrug>
You'll need to reboot after making the change.

Did anyone try tdiman's suggestion? I'm currently reading up on AVRCP and the compatibility with my N1 (this DInc thread popped up on google).
I haven't bought my BT Head unit yet, but I'd be interested to see if we can get metadata via CM

I would love to see this implemented in CM Roms

I tied to edit my audio.conf changing the lines suggested above and it doesn't work. I'm guessing because the version of bluez included with android is only 3.69 and AVRCP 1.3 wasn't even a glimmer in the authors eye at that time.
Our only hope of getting this working is either someone compiles the latest version of bluez into a ROM or wait until google does it. Unfortunately from what I have read even Android 4.0 is going to have bluez 3.69 so it may be a long wait.
Total bummer
Edit: what it does do is make A2DP unstable, after editing this file my A2DP kept randomly disconnecting.

CarpeNoctem said:
I would love to see this implemented in CM Roms
Click to expand...
Click to collapse
My guess is that since bluez is part of the core android OS, CM won't have support for it either anytime soon. Hopefully I am wrong though.

No support in bluez, yet...
Well, currently bluez (the bluetooth stack of Android) does not support AVRCP 1.3. But I have started to work on this (google: Fixes for AVRCP 1.0 and preparation for AVRCP 1.3 bluez)
So, in the following months you will have the proper support in Android, which I'll eventually announce in my blog.

Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?

http://blog.gmane.org/gmane.linux.bluez.kernel

jiggytom said:
Any update on this? I am looking for this on my Moto Atrix as well. From what I have heard, the Moto Droid X supports it?
Click to expand...
Click to collapse
I have the X and I do not get any track info. My original Droid did display the song information on my head unit.
I have tried every music player on the market and each one says avrcp 1.3/1.4 coming soon...

Google? Bueller? Google? Bueller?

thanks for the amzing post

So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung

well some devs got it into their ics roms, but we are looking for avrcp support for jelly bean now

trungvn1790us said:
So anyone can create a pack to port into ROM code for AVRCP 1.3 updated instead waiting Google release?
I'm using my ONE X and it just work with Track ID displayed on CyanogenMod 9 ROM code with Birdplayer as below link
Player download:
http://dl.dropbox.com/u/78817430/Songbird_ mediaplayer_Ver1.3.apk
(share to any buddy still find this player )
Tks/Trung
Click to expand...
Click to collapse
This is what im looking for, something universal that can be flashed over a rom to give it AVRCP 1.3 support. BTW, BlueZ now supports AVRCP 1.3

[Q] bluetooth handsfree issues with DevNull 1.0.1 ROM [ROM-AOSP GRJ22 2.3.4]

(new member so can't post to the thread for this ROM on Development forum - hope the devs see this).
It seems that with this ROM the Bluetooth handsfree functionality is broken. I have a Bury Crystal CC9060 hands free in the car. It was working fine with Oxygen 2.0.3, after moving to DevNull 1.0.1 I can only hear very very very quiet, distorted audio over the hands free kit. In both cases I'm running the stock kernel from the ROM in question.
I noticed there have been changes in the Kernel around bluetooth audio levels which sounds suspiciously like it could be related. Again I'd post a link to it but I can't due to new member - it is in commit c4805fb1f35152ff1672 and a38cca7b061228d950f9 on thalamus / kernel (github).
Anyone experiencing this - any ideas how to fix or how to get the info to the people in question?

There is a 1.0.2 update now released with all issues fixed - I hope this solves the problem
http://forum.xda-developers.com/showthread.php?t=968504

Thanks, I had looked through the revision history on post 2 of that thread and nothing jumped out at me as being related to the bluetooth audio. I will give the 1.0.2 update a go.

1.0.2 did indeed fix the issue I was seeing with bluetooth handsfree not working correctly. Great!

jfinnie said:
1.0.2 did indeed fix the issue I was seeing with bluetooth handsfree not working correctly. Great!
Click to expand...
Click to collapse
Excellent. I will be flashing this myself very shortly!

I've just now gone S-OFF using the AlphaRev.iso from a virtual machine on my mac and installed the Oxygen hboot - why couldn't the phone ship like this to start?!?! Much better now

[Q] Bluetooth Track ID (AVRCP 1.3)

Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?

did u manage to find more info about this? Anybody else knows some more details? 10q

zombiefly said:
Hi,
I had an old desire and a car head unit that didn't support BT streaming via ad2p, so when I got my new OneX, I quickly sold the old head unit on ebay and replaced it with a newer model that supported streaming. I am now able to stream over BT which is fantastic as my plays are now recorded on the phone (i use player pro & mediamonkey desktop pc to organise my collection). Plus now I can also scrobble to last.fm, which is something i've not been able to do since time began (in the car).
but now there's one thing that's quite annoying, the lack of info being sent to the head unit (track ID, etc). I did a bit of research and it turns out that the BT stack used in base android doesn't support AVRCP 1.3, which is the version of the protocol that supports track ID. Then I found that cyanogen started supporting this....
https://github.com/CyanogenMod/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Is it possible for this to be included in the custom roms? I'm asking this in general first before asking a specific ROM dev to attempt to implement. Will this need an entire cyanogen base?
I'd love to see this implemented if at all possible
EDIT: oops, i think i've posted this in the wrong place as it's a question?
Click to expand...
Click to collapse
I'll have a quick go at answering, If anything is wrong then please correct me
HTC have written their own Bluetooth stack that doesn't support AVRCP 1.3 (stupid really if you ask me). This stack will be found in the stock rom, as well as all sensed based custom rom's and possibly in some unofficial AOSP roms.
The Official CM roms should have the standard BT stack with AVRCP 1.3 drafted into it, meaning that it should push the track ID's to all receivers that support it.
To answer your question: Unless HTC's BT stack can be dissected and modded to support AVRCP 1.3, or the CM BT stack can be ported over to sensed based roms (both highly un-likely as HTC's BT stack is closed, and CM's BT stack wont work on sensed based roms) then this is not possible, unless you flash a CM rom on your One X

teky.co.uk has it covered above.
the htc BT stack is (as you would expect) half complete and doesn't support anything but basic connectivity and streaming. The cyanogen mod team added this functionality around cm7 (i think). so for phones that are supported by CM, you can flash a rom built around Cyanogen and you will have track ID.
Because we cant get S-OFF, we cant flash a pure CM mod, which presumably explains why there isn't one available. There is a port in the works by TripNRaver, however the last time I checked the BT streaming was on the issues list as not working, so regardless of it using AVRCP 1.3 or not, it wouldn't work anyway.
I'm quite frustrated by this. I bought the One X thinking it would be the best (and most up to date) Android phone available. Instead i'm stuck half way to removing the HTC crap from the phone for the first 3 months of owning it. I was able to get this functionality on my ageing HTC Desire (with custom rom)...
If you can get something to work, the music player pro application has recently added support for AVRCP 1.3 on phones that support it. So when we eventually get someone to implement a new BT stack in a custom ROM, or when HTC decide to support 1.3, we can actually use the feature!

This has been bothering me for some time; I actually sent an email technical support request to HTC for followup regarding this issue.
Maybe this will be fixed by the time Jelly Bean comes out? Or possibly that could be too adventurous.
I will reply back to this thread when I hear anything from the other side. I actually submitted a link to teky's great informative post in the ticket.

This is the response from HTC when I contacted them about it.
Thanks for your patience.
I can sadly confirm, after a long discussion with a senior technical agent, that Google have not yet implimented AVRCP in there Android O/S. It would seem to be avaiable for Windows based devices, possibly due to the amount of time Microsoft have been in the mobile firmware market. But, sorry to say, it is not yet part of Android.
The only advice I can offer, would be to post on the Google official forums about this as I'm sure you will not be alone with your requirement.
Thanks for your time and for contacting HTC.
Click to expand...
Click to collapse
Sent from my HTC One X using xda premium

help us cm9, you are are only hope.... bzzzzzzt
maybe a ROM developer could help re: porting the BT stack to a custom rom?

Here's what HTC sent to me, I have since followed up.
Thank you for contacting HTC.
With reference to your query, currenty we AVRCP 1.3 is not supported by One X. If you see that some of the function on your bluetooth is not working its because of the compatibilty of the phone and the bluetooth.
Sincerely,
Sammy
HTC

This is the best I could get out of them.
Thank you for contacting HTC.
With reference to your query, yes, HTC is looking forward to this. However, we cannot provide any definite detail at this time when will this be available to the phone. That is the reason why as well we are creating new and improve phone here for our customer. Plese refer to our website for any update to our product and service and we do apologize for the inconvinience.

So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!

trungvn1790us said:
So, anyone know how to porting the BT stack to stock rom? or any package to do that feature?
Tks All!
Click to expand...
Click to collapse
if someone created a universal zip file to flash to any android phone, that would be awesome. How in the world did cyanogenmod do it? maybe if someone asks, they can tell you how to code it into any device's rom.

some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.

Really can't wait for this feature!

zombiefly said:
some further info on this.
tbalden's CM9 port works with avrcp 1.3
http://forum.xda-developers.com/showthread.php?t=1706001 this rom is reasonably stable (battery drain is quite bad so far, the worst rom i've tried) BUT! it works fully with ACRCP 1.3
the CM10 port by tbalden does not work. I've posted many times in the thread and even messaged him directly, but nobody ever responds to my questions.
Given that Cyanogen mod supports 1.3, i'd expect this functionality to be added soon as the rom develops. I hope so as it's a fantastic rom but it's a bit flaky at the moment (as it's alpha)... if you really need avrcp 1.3, the the above linked CM9 is a decent compromise.
I'd still like an answer on how this works? is it a driver? can it be packaged and added to any rom? I think not to be honest but would still like to know.
Click to expand...
Click to collapse
Yes, agree with u guys and really need a package that supported to install to stock ROM
Tks and appreciate for any Hero help to do this!

this functionality is now in CM10. i dont think it can be ported to other roms as i think it has some dependency on the kernel? (but what do i know?)
I've been running tbaldens CM10 for some weeks now and it's very stable

I also would like to have AVCRP 1.3.
As far as i understood the bluetooth stack must be compiled with the kernel. The blueZ stack does support AVCRP 1.3.
But we need a custom kernel compiled with it?
I now also wrote a support inquery to HTC. Perhaps they will implement the complete bluetooth stack if enough customers ask for it.
Regards
Kai

+1
need this feature, please...

makes2068 said:
+1
need this feature, please...
Click to expand...
Click to collapse
its in the main CM10 roms now.

Sorry to dig such an old topic. But has anybody been able to find some patch to get this feature on sense 5. I feel sense 5 is awesome, (sorry to sound selfish) cannot switch over to CM10.. is there anyway I can get it .
on ARHD 31.2
If HTC has been blaming google due to this feature not being available in android itself, I feel cheated.. because have seen this same feature on all other android devices.
Also this feature is there in HTC one , the current flagship with sense 5.. One of my friend has it. If only some dev can compare files and bring out some patch for OneX.

How can I tell when apt-X is being used for the bluetooth codec?

Currently running CM10 B13 by Lloir, however this is a generic question for the One V.
As the topic says, how can I tell when apt-X is being used for the bluetooth codec?
I traded my HTC Desire for a One V so I could use apt-X with my new MM 550-X Sennheiser headset. It has yet to arrive but how can I confirm that it is using the apt-X codec and not SBC when I end up pairing the device?
I'd rather not just plug in the headphones and attempt to diagnose if it is running on apt-X, but rather have some sort of visual confirmation or notification, or way to check if apt-X is being used.
Thanks,
Sam

Hi
CM ist using the open source bluetooth stack Bluez
AFAIK this is not supporting aptx at the moment.
Since aptx http://www.csr.com/products/technology/aptx is properitary
I doubt there will be support at any time.
So if you want to use aptx you may need to stick to stock ROM
or a stock based ROM
max

maxwen said:
Hi
CM ist using the open source bluetooth stack Bluez
AFAIK this is not supporting aptx at the moment.
Since aptx http://www.csr.com/products/technology/aptx is properitary
I doubt there will be support at any time.
So if you want to use aptx you may need to stick to stock ROM
or a stock based ROM
max
Click to expand...
Click to collapse
Fair enough, in which case I would have two final questions
Looking at the dev forum, these two ROMs appear to be stock based, am I correct?
http://forum.xda-developers.com/showthread.php?t=1647052
http://forum.xda-developers.com/showthread.php?t=1640995
Secondly, assuming they do support apt-x that does bring me back to my initial question, how will I know it is enabled? I'd rather not plug in my headsets and leave it to my own judgement "sounds like aptx".
Thanks,
Sam
EDIT: This has been cleared up in PM by maxwen. Thanks!

Hi, can you post the answer you got from maxwen please? I am interested in hearing about it.
Thanks.

ricav said:
Hi, can you post the answer you got from maxwen please? I am interested in hearing about it.
Thanks.
Click to expand...
Click to collapse
Excerpt from the PM, I hope maxwen doesn't mind.
You are forgetting why we want to use something like CM
We want open source without any properitary parts
And the HTC bluetooth stack is properitary so there is
no source code for it. Its even not in the kernel but
a user-space only implementation.
Click to expand...
Click to collapse

Cm 10.1 avrcp 1.3+

Does anyone know when AVRCP 1.3+ will be merged into CM 10.1? It appears to be an essential feature and is present in the stock ROM; however, missing in CM 10.1.

wrong section...

cpu999 said:
wrong section...
Click to expand...
Click to collapse
Why is it a wrong section? I have AT&T Galaxy S III with CM 10.1 installed and missing this feature

This isnt originao development its a question..
Belongs in q/a so wrong section
trolol and awayyy!! Expect typos this is my phone.

PashaF said:
Does anyone know when AVRCP 1.3+ will be merged into CM 10.1? It appears to be an essential feature and is present in the stock ROM; however, missing in CM 10.1.
Click to expand...
Click to collapse
to answer your question:
It is unknown. With 4.2.2 google decided to change the Bluetooth stack to a broadcom source. IMO it's absolute garbage. Althought it is open-source, code is bad, performance is bad, and 4.2.2 has has pretty much shotty bluetooth AT BEST. Thanks to devs like Task and, others, we've been able to have decent AVRCP1.0 (Device Control)/A2DP (BT Streaming).
The that added AVRCP 1.3 to the previous stack by Bluez is known, which should help in the implementation of 1.3 into the Broadcom stack, but really, broadcom is garbage. Any driver that i've ever had from broadcom has been garbage and I quickly replace. We'll either see a reversion to the 4.2.1 bluetooth stack (crossing my fingers for) or a manipulation of the Broadcom code (like Bluez) to give us 1.3. Until then, suck it up with 1.0. We've never had solid 1.4 , that's where it starts getting good.
It's sad cause the iPhone has 1.4 support..maybe that's the reason why most good head units stay away from true android support. Even the newer one coming out are still pretty lacking when you compare iPhone to Android features.

PashaF said:
Does anyone know when AVRCP 1.3+ will be merged into CM 10.1? It appears to be an essential feature and is present in the stock ROM; however, missing in CM 10.1.
Click to expand...
Click to collapse
If there is any dev out there who wants to earn himself some fame, please do register yourself here:
https://jira.cyanogenmod.org/browse/CYAN-20