I know call recording on WM devices has been beat to death and that the issue lay with the hardware limitations of the audio line when in a call... But I had a thought, would it be possible to create a dummy bluetooth device that simply wrote the audio to a file? How hard would this be?
While probably not easy, with some of the other accomplishments that already exist (e.g. Bluetooth audio router software), it would seem possible. Ideas?
insol said:
I know call recording on WM devices has been beat to death and that the issue lay with the hardware limitations of the audio line when in a call... But I had a thought, would it be possible to create a dummy bluetooth device that simply wrote the audio to a file? How hard would this be?
While probably not easy, with some of the other accomplishments that already exist (e.g. Bluetooth audio router software), it would seem possible. Ideas?
Click to expand...
Click to collapse
Hi,
Call recording is easily done with Vito AudioNotes.
Dirk
dirlan2001 said:
Hi,
Call recording is easily done with Vito AudioNotes.
Dirk
Click to expand...
Click to collapse
*yawn*
Please don't post incorrect stuff. No, not even AudioNotes is capable of fixing these issues.
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