Once my Bluetooth Headset is connected to my Prophet, all my notification sounds come through my Bluetooth Headset instead of the phone speaker.
The sound for normal incoming call works as it should though (through the speaker).
The only way i've found how to solve this problem, is to uncheck the "Wireless Stereo" option under:
Settings > Connections > Bluetooth > i.Tech Clip R35 > Partnership Settings
And then when I want to listen to music through the Windows Media Player, I have to do the opposit.
So, my two questions...
1. Is there a way to map notification sounds to always use the phone's speaker? (or)
2. Is there a small shortcut / Today-plugin that can switch "Wireless Stereo" on/off in one click?
Cheers!
Eric
Mortscript could be used for to create a script that would toggle Wireless Stereo" & then a shortcut to this script could be put on the today screen or mapped to a button.
Do a search on scripts for wifi as many people have done this type of thing already.
Also have a look at this link, might be of some use.
http://www.vijay555.com/?Releases:VJVolubilis
Mister B said:
Mortscript could be used for to create a script that would toggle Wireless Stereo" & then a shortcut to this script could be put on the today screen or mapped to a button.
Do a search on scripts for wifi as many people have done this type of thing already.
Also have a look at this link, might be of some use.
http://www.vijay555.com/?Releases:VJVolubilis
Click to expand...
Click to collapse
Thanks Mr. B.
Interesting idea.
But it seems like the VJVolubilis only supports BlueTooth on/off at this stage, and not switching a BlueTooth service on/off.
And from what I understand the "agon" command passes the audio through the "Headset" service of a BlueTooth device.
Well, I solved it by creating a Mortscript...
It's not beautiful, but it works!
overone said:
Well, I solved it by creating a Mortscript...
It's not beautiful, but it works!
Click to expand...
Click to collapse
It may look ugly in notepad but the beauty is watching it work.
Have fun with your scripts, its a useful tool.
@overone, can u share the script???
shantzg001 said:
@overone, can u share the script???
Click to expand...
Click to collapse
Yes, sure! If you promise not to laugh?
I'm sure there's tons of ways to make this better, but I never used this script language before, and I didn't want to waste an eternity fixing my problem.
Removing the sleeps would be the first things on my mind for an improvement.
As for the shortcut "BluetoothSettings.lnk"; it just a simple shortcut that opens the bluetooth setting panel.
And YES, it's hardcoded to be located in Program Files...
Code:
# Open Bluetooth Settings
Run("\Program Files\BluetoothSettings.lnk")
WaitForActive("Settings",5)
# Go to i.Tech Clip R35
SendDown
SendCR
Sleep(1000)
# Mark/Un-Mark Wireless Stereo
SendDown
SendDown
SendCR
Sleep(1000)
# Exit and Save
SendRightSoft
Sleep(2500)
SendOK
That worked wonderfully for me, and is the only solution I have found so far to automatically turn on my BT Stereo Audio headset.
Download Mortscript from http://www.sto-helit.de
Create a new file ToggleBTStereoAudio.mscr in any folder on your PPC with the following text in it
Code:
# Open Bluetooth Settings
Run("\Program Files\BluetoothSettings.lnk")
WaitForActive("Settings",5)
# Go to i.Tech Clip R35
SendDown
SendCR
Sleep(1000)
# Mark/Un-Mark Wireless Stereo
SendDown
SendDown
SendCR
Sleep(1000)
# Exit and Save
SendRightSoft
Sleep(2500)
SendOK
Create a new file "\Program Files\BluetoothSettings.lnk" with the following in it
Code:
23#ctlpnl cplmain.cpl,23,1
To toggle your BT Stereo simply click on the ToggleBTStereoAudio.mscr file. You will be able to see the mortscript run and toggle the stereo audio for the device.
There's a program called A2DPToggle - freeware
Just came across it myself and it does the job very well - has a Today plugin that can even start A2DP then launch your media player as well as other BT management and speakerphone toggle, or an app that just toggles Wireless Stereo when run
The homepage for it is at http://www.teksoftco.com/index.php?section=freeware
Does anyone know how to update an audio.config file? I found a thread over on the Motorola forum where they are talking about being able to use a bluetooth headset for voice audio over video chats. Some are saying that we just need to be able to update the audio.config file located here: /system/etc/bluetooth/audio.conf
They are saying that maybe if we remove the # before HFP=true then we can activate the voice audio for a bluetooth headset and use it for video chats.
Here is the link for the original thread. Let me know what you all think.
Well for anyone interested, I was able to modify the audio.config file from Root Explorer with the Text editor so that the Xoom now recognizes the bluetooth voice profile of my Jawbone Icon and successfully pairs with it and shows the media profile and the voice profile. But when I try to use Google Talk, the app doesn't seem to send the audio or voice to the headset. So I have made one step forward but now it seems that this is another step backwards because now it seems that I have to find a way to get the app to see the headset but there are no settings for this feature.
In the audio.config file there is this section:
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
If I changed it to this, would this enable the app to use the headset:
[General]
Enable=Sink,Control, Headset,Gateway,Source
#Disable=
Now I just compared the audio.config file on my Droid X and my Xoom and found that the only difference between the two was at the bottom of the file. The example I am showing the the Xoom audio.config file with the last two lines added from my Droid X.
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Do not require master role for incoming connections
Master=false
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
MetaDataSupport=1 <-------------- only difference on DX
ControllerSupport=1 <-------------- only difference on DX
Other than those two changes everything else is the same. So it does not seem to the the HFP=True since my DX can use the headset just fine. So now I just seem to be spinning. Any thoughts?
dimitri407 said:
Now I just compared the audio.config file on my Droid X and my Xoom and found that the only difference between the two was at the bottom of the file. The example I am showing the the Xoom audio.config file with the last two lines added from my Droid X.
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Do not require master role for incoming connections
Master=false
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
MetaDataSupport=1 <-------------- only difference on DX
ControllerSupport=1 <-------------- only difference on DX
Other than those two changes everything else is the same. So it does not seem to the the HFP=True since my DX can use the headset just fine. So now I just seem to be spinning. Any thoughts?
Click to expand...
Click to collapse
Where did audio.conf go in Android 4.2.2?
dmwoods said:
Where did audio.conf go in Android 4.2.2?
Click to expand...
Click to collapse
Same question here.
The audio.conf file is part of the BlueZ stack, and since Bluedroid has now taken it's place it is no longer used.
Though, has anyone made any progress on this using the BlueZ stack. Bluedroid is becoming a huge PITA.
So... finally got to test out the bluetooth A2DP with my Sensation and I was very disappointed. Sound quality is like listening 64kbps MP3 :-(
After googling and searching this forum I found that this is not the first Android phone which has the issue, but so far didn't any solution on how to "fix" it.
Allthough I did some digging in the filesystem and found that /etc/bluetooth/audio.conf hold these values:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Do not require master role for incoming connections
Master=false
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
But since there's no root (only temp root) I'm not allowed to edit the file. I'm just wondering if changing these values would make the quality better:
#AutoConnect=true
(I'm having issues to auto-connect to my A2DP receiver, have to manually connect every time)
#SCORouting=PCM
(don't know what this is, but sounds like it's related to compression used to transfer the audio?)
SBCSources=1
MPEG12Sources=0
(maybe disabling the SBCSources and enabling the MPEG12Sources would force the A2DP to use MPEG12 so there would not be any re-encoding?)
I'm really disappointed with my device when coming to this. My six years old Nokia was capable to play music via A2DP with full quality.
I have two receivers, one is LiquidAux from Kensington and one is "OEM" receiver from local electronics store. Both sounds like crap with Sensation
I have to agree, however, I have had mixed or rather inconsistant results, perhaps a bt3 a2dp could improve quality? I dont know. Other HTC devices I owned have same issue, Sensation via headphones however is simply second to none! not even my ipod sounds as good, not nearly!
Flashmore said:
I have to agree, however, I have had mixed or rather inconsistant results, perhaps a bt3 a2dp could improve quality? I dont know. Other HTC devices I owned have same issue, Sensation via headphones however is simply second to none! not even my ipod sounds as good, not nearly!
Click to expand...
Click to collapse
I think the case here is that the audio is re-compressed to SBC with very low bitrate. It also seems to re-encode MP3-files even the receiver is capable to receive them directly without re-encoding.
Can't believe this is possible in 2011, like I sais, half decade old Nokia can handle the A2DP flawlessly and my brand new 550€ "MULTIMEDIA SUPERPHONE" (quote from HTC's website) can't
That's strange, I don't usually use a2dp, I've opted to use Btmono with my old bt headset (better battery life) and I haven't had a single issue with calls, alerts or music/videos...the only "downside" is mono audio, but the app says it all
Sent from my HTC Sensation 4G using XDA App
Solidus_n313 said:
That's strange, I don't usually use a2dp, I've opted to use Btmono with my old bt headset (better battery life) and I haven't had a single issue with calls, alerts or music/videos...the only "downside" is mono audio, but the app says it all
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
You can't really compare a mono headset to professional Hi-Fi system which I use outputting the music to my ears.
I know that Bluetooth ain't a HiFi solution in the first place, but it still would be nice to listen some random music from my phone while driving. Now the quality is so bad that it's not even usable and I know this is not normal, A2DP is capable of transferring audio with decent quality (my other devices can do it).
I've posted about this several times but never got any interest. I'm glad it is not just me. The quality is shockingly bad on Sensation A2DP. My last HTC device (Legend) had varying A2DP quality with certain stock ROM updates, but it was never as bad as this. The difference in quality between the Sensation and, for example, a Sony A series walkman is staggering.
With a good bluetooth headset, A2DP can actually be better quality than a cabled connection (especially with the crappy d2a and amp components on most phones).
d-iivil said:
So... finally got to test out the bluetooth A2DP with my Sensation and I was very disappointed. Sound quality is like listening 64kbps MP3 :-(
After googling and searching this forum I found that this is not the first Android phone which has the issue, but so far didn't any solution on how to "fix" it.
Allthough I did some digging in the filesystem and found that /etc/bluetooth/audio.conf hold these values:
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Do not require master role for incoming connections
Master=false
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
But since there's no root (only temp root) I'm not allowed to edit the file. I'm just wondering if changing these values would make the quality better:
#AutoConnect=true
(I'm having issues to auto-connect to my A2DP receiver, have to manually connect every time)
#SCORouting=PCM
(don't know what this is, but sounds like it's related to compression used to transfer the audio?)
SBCSources=1
MPEG12Sources=0
(maybe disabling the SBCSources and enabling the MPEG12Sources would force the A2DP to use MPEG12 so there would not be any re-encoding?)
I'm really disappointed with my device when coming to this. My six years old Nokia was capable to play music via A2DP with full quality.
I have two receivers, one is LiquidAux from Kensington and one is "OEM" receiver from local electronics store. Both sounds like crap with Sensation
Click to expand...
Click to collapse
need that 2.0 to 3.0 compatibility fixed, pronto...
the sensation is bluetooth 3.0 and I have 2.0 stereo headphones. They worked great with the hd2. Now the sensation is mucking it up. I can hear music and movies great. I just can't use it to talk like I used to - which is my primary reason to have it. Need a fix or an explanation...
Odd, my Motorolla S9-HD's sound fantastic with the Sensation. Just today I listened first to some music using the paid Pandora, then a few MP3's, then a podcast while cleaning up the yard and lawn. Bass was deep and lows/mids were very good, from what I could tell. Maybe the S9-HD's have a chip to make it sound better or something, dunno.
howetechnical said:
Odd, my Motorolla S9-HD's sound fantastic with the Sensation. Just today I listened first to some music using the paid Pandora, then a few MP3's, then a podcast while cleaning up the yard and lawn. Bass was deep and lows/mids were very good, from what I could tell. Maybe the S9-HD's have a chip to make it sound better or something, dunno.
Click to expand...
Click to collapse
what about talking on it? does the person on the other end hear an echo?
I've noticed very bad A2DP quality as well. With my N1, I would play music all day through the same Bluetooth receiver and not notice anything. With the Sensation everything is extremely 'muddy'. It sounds exactly it is being transcoding in to SBC, instead of using the mp3 passthrough stream which is what my N1 was doing. I'm just assuming this since I can't figure out a way to verify other than the crappy sounding audio now... This is using a Sound-Fly BT receiver.
Now, I also have a Motorola S10-HD a2dp headset and both the N1 and the Sensation sound just fine there..
My only guess is that the Sensation is not able to establish an mp3 channel with the SoundFly-BT (like the N1 can), but it can to the S10-HD.
BTW, regular calls using the HFP profile seem just fine.
steve austin said:
the sensation is bluetooth 3.0 and I have 2.0 stereo headphones. They worked great with the hd2. Now the sensation is mucking it up. I can hear music and movies great. I just can't use it to talk like I used to - which is my primary reason to have it. Need a fix or an explanation...
Click to expand...
Click to collapse
I had the same problem - I got music, but phone audio didn't work.
I went into Settings>Wireless & Networks>Bluetooth Settings, long-pressed on the bluetooth device I was using, selected options, unchecked both "Phone" and "Media", then re-checked them both.
After that, I got both A2DP media audio, as well as phone headset functionality.
Hope this helps!
Hmm. I'm not having a muddy audio issue with mine. It sounds exactly the same as my N1 with Stock/CM6/CM7, the only difference is I did not have to apply a hacked up audio.conf to keep it from skipping all the time as I do with the N1.
I'm using a FIPO A2DP audio reciver plugged into an ipod cable. The handsfree goes to the vehicles OEM adapter.
I've yet to try actual phone calls though. It does occasionally loose the handsfree connection, something that never happend with the N1, so something is dfnitly amiss.
I was just about to start a thread on this very subject. I'm glad I'm not the only one having issues with A2DP. I stream podcasts all day at work & the connection is terrible. Sound quality is fine, but it skips & stutters like crazy no matter what headset I use(though my S9s are the worst. They've sucked since I bought them & I literally threw them at the wall yesterday in a fit of rage). I even bought a new headset today & it's a BIT better, but still spotty. I think it might just be all the EM radiation at work(I work in a computer shop) b/c it isn't nearly as bad at home, but either way it's super annoying.
For such an expensive phone, problems like this really piss me off >:|
lol...Geez you guys should at least thank HTC. On the G2x, the damn BT stack is a joke. One minute the BT is connected and the next it is LOCKED up. The only way to rectify the problem is a reboot. I for one can not do without BT. I hate holding phone up to my ears.... I would take a muddled sound any day to a not so good BT stack that you don't even know when it locks up or just plain does NOT work.
The Sensation seems capable of great audio over BT - when using my Belkin AirCast in the car, the audio is crystal clear and free of drop-outs or other problems.
With my Jabra BT8010 stereo headset, however, the drop-outs are frequent and annoying.
Don't know if it's the receiver's BT abilities (2.0 vs. 3.0), power levels, or what, but the Sensation is capable of amazing audio over BT, but only with the right devices it seems...
It's truly amazing how good it sounds in my car over bluetooth, but I've gone back to using the wired headset while walking.
kevsteele said:
The Sensation seems capable of great audio over BT - when using my Belkin AirCast in the car, the audio is crystal clear and free of drop-outs or other problems.
With my Jabra BT8010 stereo headset, however, the drop-outs are frequent and annoying.
Don't know if it's the receiver's BT abilities (2.0 vs. 3.0), power levels, or what, but the Sensation is capable of amazing audio over BT, but only with the right devices it seems...
It's truly amazing how good it sounds in my car over bluetooth, but I've gone back to using the wired headset while walking.
Click to expand...
Click to collapse
could you elaborate on the drop out? Does it disconnect and reconnect? i hope not.
cenwesi said:
could you elaborate on the drop out? Does it disconnect and reconnect? i hope not.
Click to expand...
Click to collapse
By "drop-out" I mean the audio cuts out, then continues. There are "blank" portions in the playback, like someone muted the sound for a split-second.
The BT stays connected.
thanks as long as it doesn't hangup
BTW, any issues with the bluetooth driver that you can think of? G2x one is just plain BAD!
cenwesi said:
thanks as long as it doesn't hangup
BTW, any issues with the bluetooth driver that you can think of? G2x one is just plain BAD!
Click to expand...
Click to collapse
I haven't had any problems at all with the bluetooth stack - no disconnections or crashes.
Yeah coming from my N1 this is a real bummer. Mine just has a lot of crackling. I'm playing it through my 2011 subaru's BT audio.
For those that researched other Android phones with this problem, were they Sense phones? Because I'm pretty sure HTC doesn't use the same BT stuff that stock android does. I know that my friend's have had trouble pairing their sense phones but then flashed an AOSP rom like cyanogen and the problem was resolved. So maybe something similar can be done here once we get S-OFF
Can someone post their audio.conf code? It is locateed in /etc/bluetooth/
The reason I am asking this, is because I am trying to troubleshoot my bluetooth connectivity issues with my car radio. It supports 1.3 AVRCP yet I'm getting no meta-data. This is the code my phone is showing below. (Also, my playback pauses randomly)
Code:
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# request master role for incoming connections
# so as to reduce the number of piconets and
# allow lot more incoming connections
Master=false
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
MetaDataEnable=true
[WBspeech]
#for wide band speech hci commands arguments
WBSEnable = false
I2sEnable = 0x01
IsMaster = 0x00
ClockRate = 0x02
PcmInterfaceRate = 0x00
Any help with this is greatly appreciated.
197 Views and not one person willing to post? Just want to see the audio.conf from a person with working streaming meta data...
BungeBash said:
197 Views and not one person willing to post? Just want to see the audio.conf from a person with working streaming meta data...
Click to expand...
Click to collapse
Here you go
# Configuration file for the audio service
# This section contains options which are not specific to any
# particular interface
# NOTE: Enable=Sink means that bluetoothd exposes Sink interface for remote
# devices, and the local device is a Source
[General]
Enable=Sink,Control
Disable=Headset,Gateway,Source
# Switch to master role for incoming connections (defaults to true)
Master=false
# If we want to disable support for specific services
# Defaults to supporting all implemented services
#Disable=Control,Source
# SCO routing. Either PCM or HCI (in which case audio is routed to/from ALSA)
# Defaults to HCI
#SCORouting=PCM
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
# Headset interface specific options (i.e. options which affect how the audio
# service interacts with remote headset devices)
#[Headset]
# Set to true to support HFP (in addition to HSP only which is the default)
# Defaults to false
#HFP=true
# Maximum number of connected HSP/HFP devices per adapter. Defaults to 1
#MaxConnections=1
# Set to true to enable use of fast connectable mode (faster page scanning)
# for HFP when incomming call starts. Default settings are restored after
# call is answered or rejected. Page scan interval is much shorter and page
# scan type changed to interlaced. Such allows faster connection initiated
# by a headset.
FastConnectable=false
# Just an example of potential config options for the other interfaces
[A2DP]
SBCSources=1
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
# The Sony car stereo Ford is using under their brand as '6000 CD' has a
# completely broken AVRCP 1.3 implementation. After recognizing AVRCP 1.3 TG
# capabilities and exchanging a few PDUs, the car stereo disconnects and
# reconnects BT, also resetting USB devices if connected to it.
# To avoid that and allow at least HFP and A2DP to work, prevent any AVRCP 1.3
# PDUs from being sent on those models - add the device to the black list.
# Since 2012 Ford models have it fixed, removing the device from the list
# will result in full functionality.
MetaDataBlackList=Ford Audio
Sent from my SGS3 running Eclipse 2.1
I appreciate the response. I was hoping there was going to be more different than the little excerpt at the bottom :-/ Maybe it is just going to be an issue with uConnect in dodge cars. Unfortunately I have no other car to test with.
Hi all!
I wanted to open up a discussion about the new Oreo features for Bluetooth codecs in the developer section. I haven't been able to find a comprehensive guide or info anywhere that covers how it actually should work, and I don't believe it's working correctly - I would like to explore more with you.
I'm on a Google (carrier free) Pixel, using a fresh install of OPR6.170623.012 - which is working brilliantly by the way.
It seems to me that I can't make the settings stick, if I for example change the Bluetooth Audio Codec to aptX, or modify any of the other settings when I go back in it always reverts to the 'Use System Selection (Default)' option. I'm typically trying this with Bluetooth off, changing the setting and turning Bluetooth on. I've also tried rebooting in-between, as well as different variations. The developer toggle is set to on of course.
It may be my misunderstanding of how this works, but it even if I stay on the developers screen and change the codec, if I turn Bluetooth on and it connects to a device, for instance my in-car Bluetooth audio, which I believe supports aptX, it doesn't care what the codec setting is and displays 'Streaming: SBC', which is of course what I'd expect would be overridden.
The only thing that seems to stick is the AVRCP version. I'm wondering if the Bluetooth HCI snoop log will provide any information?
Have any of you had any experience with this, or have anything to add to the conversation?
Many thanks in advance,
OK so it seems this codec list doesn't allow you to set a 'default', it just allows for modifying the codec during playback?
What I've experienced so far is that it does work with 'Use System Selection' to use the best codec available on the device you are connected to. It also allows you to change the codec to another while streaming/playing. The sub-text under Bluetooth Audio Codec does dynamically change from SBC to AAC.
Example: My headphones support SBC and AAC, the Pixel defaults to AAC on establishing a Bluetooth connection but does allow downgrading to SBC by picking from the list (as a test).
It however doesn't retain whatever you pick in the list if bluetooth is turned off then back on, it basically always defaults to system selection, then auto-picks on every connection. Perhaps this is by design, it is developer tools after all.
I haven't been able to get this to work with aptX in my car yet with my Pixel, even though it is apparently supported?
Also of note: To achieve AAC on my Bluetooth headphones I had to put them into a 'Priority on sound quality' mode and also turn off the Bluetooth phone (i.e. call connectivity, music ONLY) on the Pixel connection to achieve AAC.
are you sure that your car supports aptx? before this developer option it was very hard to actually see the codec being used.
I believe so, the Bluetooth product states that it supports EDR and aptX, but yes, I cannot be 100% certain.
Are you suggesting it should be possible with Pixel and the Oreo build as-is?