Database Users

Waveform audio interface problems (waveIn* waveOut*)

Hi all!
Now I'm working on small audio library for PocketPC. Library using waveform audio interface (waveIn* and waveOut* functions). I have big problem with full duplex audio. Whem I'm open audio device for input, the sound from microphone is playing on the speaker. If I start playing some another sounds - they are mixing with input sounds. I want to separate input audio stream from output audio stream. Device doesn't have mixer, mixerGetNumDevs returnes 0, and mixerOpen also fails.

I have just the same problem. One workaround is to lower the sound volume level, the second is to use some echo canceller. The only echo canceller source code I have uses lots of floating point functions, so it is extremely slow on Pocket.

Blueplayer - A2DP Stereo Greatness - What's it made of?

Those who tried it before, give this another chance.
I have made a modified .cab file (Go to the BOTTOM)
- No 30 seconds limit
- Remote control works ( AVRCP)
- No skipping (Convert all MP3 to 192kbps or less)
NOW ONTO SERIOUS BUSINESS
Normal A2DP causes some hissing, sound deterioration (depending of your bitpool capacity) and hogs the phone's resources making it nearly unusable without having to pause the playback to be able to accomplish something like send a SMS.
Blueplayer has NO DETERIORATION – It uses it’s own special codec / technology
###I wish to know WHAT codec/technology is used by Blueplayer?! :O###
PROOF that Blueplayer uses a “SPECIAL” technology instead of normal A2DP
- INDEPENDENT from WM5 / WM6 A2DP drivers.
#To use Blueplayer, you need to DISCONNECT /UNCHECK the “Wireless stereo” from the phone’s Bluetooth settings (paired devices).
- NOT ALL STEREO HEADSETS CAN BE USED! ( i.Tech R35 for headphones)
WM6 A2DP stream to Laptop PC : WORKS
WM6 A2DP stream to Stereo BT Headphones : WORKS
Blueplayer stream to Laptop PC : DOES NOT WORK
Blueplayer stream to Stereo BT Headphones : WORKS
So, only special hardwares can decode whatever is the technology used by Blueplayer. It's not normal A2DP.
- AUDIO QUALITY TEST
WM6 A2DP stream to Laptop PC : Hissing
(Insanely high BitPool has no effect, and wont do skipping)
Laptop Widcomm BT A2DP to Stereo BT Headphones : Same Hissing
(BitPool can't be changed)
Blueplayer stream to Stereo BT Headphones : AWESOME!!
(skips if above 192kbps, so quality has an impact)
Blueplayer stream to Laptop : DOESNT WORK
BACK TO THE POINT !!!
I wish to know what's that technology.
Why?
Blueplayer is a HORRIBLE HORRIBLE MP3 player. All I care for is the CODEC.
The Blueplayer ITSELF is very difficult to manage.
- To pick a NEW track, you cant just click/tap it. You got to press STOP, then select the track, then press PLAY. (Or use NEXT/PREVIOUS over and over to navigate to it)
- The buttons can only be TAPPED, not clicked, and they are SO TINY that you cant just press them while walking around. You literally got to AIM your fingernail on the button, or use the stylus.
- You cant browse folders by clicking, you got to tap on a TINY TINY (+) to expand folders
- Cant select all subfolders, you got to add each folders individually to the playlist.
- No ID3 support, only a raw file list
etc etc, it's an ugly GUI.
But I want the sweet codec that makes the music sound so great.
OK HERE'S THE FILE!!!
Follow these steps to Pair your BT Headphones with Blueplayer
1 - Delete BT Headphones from your paired devices list in Bluetooth settings
2 - Set your BT headphones in discoverable/pairing mode.
3 - Launch Blueplayer
4 - Tap on "SelectDevice" at the bottom left of the screen
5 - Click on "Refresh" at the bottom middle of the screen
6 - Select your device and press the "ok"
7 - It will ask you to Pair/Add the device (WM6 Bluetooth settings does that)
8 - Once paired, UNCHECK "Wireless Stereo" from the services
9 - In Blueplaye, click on the folder icon near the top/right
10 - Browse for a folder containing directly some MP3 (it will show in the bottom list if it sees the MP3, no sub-folders allowed)
11 - Got to click the "ok" at the bottom left.
12 - Press the tiny tiny tiny "play" button and enjoy.
If you get driver errors, or the music doesnt play in your headphones and the software crashes, you dont have the hardware required to use Blueplayer.
Othewise, ENJOY THE FABULOUS QUALITY STREAMING and the CRAPPY GUI

A2DP supports several CODECs that can be used to transfer the audio over the Bluetooth link.
There is only ONE mandatory codec to support -SBC.
For SBC, normally the sound processing goes like this:
MP3 (source) --WMPlayer--> "decoded WAV" --A2DP--> SBC --wireless--> WAV (Headset)(earphones)
There is another commonly supported codec - MP3. MP3 is a much better codec for sound quality than SBC, but its much more CPU intensive to encode and decode MP3. Most A2DP headsets dont support the MP3 codec, but some (like the i.Tech) do.
My guess is Blueplayer is able to use the MP3 codec for A2DP, if your A2DP headset supports it.
Blueplayer probably does this:
MP3 (source) --Blueplayer A2DP--> MP3 without re-encoding --wireless--> WAV (Headset)

(Sorry to post in a new post - the edit post doesnt work for me using Firefox 3.)
One thing about using the MP3 codec in A2DP is that the player probably cannot do changes to the sound (no volume control, equalizer/bass boost, etc.) without having a huge impact on CPU load.
So essentially what you get is almost the raw MP3 file being streamed wirelessly using A2DP to the headset to decode. Which is a very good way to preserve the sound quality of the MP3 file.
Good find though, I'm glad to see a WM MP3 player that actually supports the MP3 codec for A2DP.

My issue is that blueplayer has a horrible GUI. While it is a great concept to stream the MP3 without reencoding, it's just... horrible.
I've always wondered why a lot of A2DP headsets can decode MP3 directly, yet there are NO software players that take advantage of it other than blueplayer.

does it work on wm smartphone

Bluetooth A2DP Headphones Problem

I recently upgraded from a Nokia N95 to a Touch HD. I've been trying to get my Sony DRBT21 bluetooth headphones to work with the touch HD. The phone pairs with the headphones, but the sound quality is poor with no bass and sounds crackly.
Additionally when I turn off/on the headphones, only the headset and microphone profiles connect back to the phone, not the A2DP stereo part. The only way I've found to get it to reconnect is to repair them.
Any idea if this is a known issue with A2DP headphones on the Touch HD? I'm not expecting to get brilliant audio quality, but as it is right now with crackles and distortion it isn't worth listening to.
Just wondering if anyone has any ideas on how I can fix or optimise this?
Cheers

Was the device properly paired? Were you prompted for the PIN? If not, do so manually by going to Bluetooth settings and pair the headset from there.
As for the A2DP not being available when reconnecting, this seems to be a known issue as I experience this intermittently with HTC's own Bluetooth and another third-party one, too. This issue was also observed on my previous HTC Polaris! A workaround for this issue for me is to power off Bluetooth and then power it back on: not a good solution!

It prompted for the PIN which I entered, and looks to be set up correctly. The main issue seems to be the background static when listening to music (hissing and crackling). Is there anything in Advanced config that could be tinkered with to try and alleviate the problem?

This won´t help you:
My Motorola S9 and HT820 (Both A2DP/AVRCP) working fine with HD and Diamond. Also I had some difficulties reconnecting the first times, due to the not used pairing-PIN. The motos doesn´t need it. The HD and the diamond needed some time to accept this
Now they reconnect as Hedset and Stereoheadphons.
Maybe there is another BT-Master (your old phone) active that occupies the A2DP connection with your headset.

I have one HD and S9, sometimes it's a little hard for them to connect but the sound can be very good, the only problem is that with high BitPool values above 30 (medium quality) it's very easy to break the sound when the HD is in our pockets and we are outside the house.

hi, im using the same headphone with you. you got that cracking noise with no bass because it's playing via the headset function, not as stereo headphone.
try disable the heatset option in the bluetooth, then open your music player and try again.
And yes, when u turn off your headset improperly. i.e. turn off from the power button, and not through bluetooth -> disconnect, then turn off... you will have to go to setting -> set as stereo headphone...

I had a play around with Advanced config and found that if I change the max bitpool from 30 to 50, the crackling and static disappears. It seems better now. Many thanks!
Edit: Changed to Max Bitpool 80 and Min 65 and the quality is brilliant. Found some further information from a post on another site (PPCSG) which may be useful to any with a similar issue:
Using ACT (Advance Config Tool), go to BLUETOOTH:
*below are my settings->
-Use Joint Stereo: Yes (default)
-Bitpool: Very High
-Max supported bitpool: 80
-Min support bitpool: 65
-Sample rate: 48000Hz
*My settings may not be the best, therefore you may want to trial and error.
The following shows the named values for the A2DP\Settings key.
By default, A2DP uses a bitpool of 48. A lower bitpool value improves system performance. Increasing bitpool to a higher value causes an overhead on Bluetooth and system resources.
Microsoft suggests the following bitpool values for optimal buffer sizes.
30 - Low audio quality
40 - Medium audio quality
48 - High audio quality
58 - Excellent audio quality
-The maximum reported bit pool value, which can be negotiated with the peer device. Default value is 80.
-The minimum reported bit pool value, which can be negotiated with the peer device. Default value is 14.
-SBC sample rate to use. Default value is 44.1 KHz.

least of your worries...
what bothers Me more is that the old A2DP bug from the HTC Diamond has made its way to the HD ROM, in that if you listen to music via A2DP and recieve a phone call, you take that call and end that call then your music continues playing through the phone speakers! You have no idea how embarassing this is on a train!

that doesnt happen on mine, go straight back to my headphone again...

Even though it doesnt happen on mine, to be safe I plug a dummy headphone jact to the phone so even if bt gets disconnected, no sound goes through decice speakers. Makes me feel comfortable on the train. This was also an issue with Cruise which was addressed by a hotfix later on.

gurluver said:
try disable the heatset option in the bluetooth, then open your music player and try again.
Click to expand...
Click to collapse
Tried that, and the difference is staggering!
I can now confirm that it isn't a hardware issue, that these phones (Sony HBH-IS800) are capable of sound quality just as good as other Sony in-ear jobs. Thanks for that!
Now, all I have to do is try to sort out the drop-outs. It seems as though the slightest barrier can cause drop-outs, for instance, putting the phone in my jacket pocket, or passing my jacket sleeve in front of it. Not sure whether it's the particular material of my jacket, or the metal in the buttons, or what, but it's hugely irritating.
Funnily enough, seems to make a difference if I have the connecting wire behind or in front of my neck. More to follow on this one....
Cheers
Pete

noise ?
For people using the HD and motorola S705 as bluetooth A2DP : do you have also an annoying background noise when listening to quiet music ? Or before the sound starts. You know a noise like pffffffffffffffffffffff

HTC P3600
Hello,
I already installed the tornado_a2dp.cab on my PDA HTC P3600 with WM5. but I can't sincronize MP3 (Windows Media Player or TCPMP) with my headphones Nokia BH-206.
Anybody help me to solve this problem?
The mp3 sound only worked (10seconds) in Windows Media Player when I press the button to do a call

Hi.
I have done the changes mentioned in this thread and got much better sound when listening to music.
But i still have a static noise when im in a call.
Is there a way to fix this?

mugis said:
I had a play around with Advanced config and found that if I change the max bitpool from 30 to 50, the crackling and static disappears. It seems better now. Many thanks!
Edit: Changed to Max Bitpool 80 and Min 65 and the quality is brilliant. Found some further information from a post on another site (PPCSG) which may be useful to any with a similar issue:
Using ACT (Advance Config Tool), go to BLUETOOTH:
*below are my settings->
-Use Joint Stereo: Yes (default)
-Bitpool: Very High
-Max supported bitpool: 80
-Min support bitpool: 65
-Sample rate: 48000Hz
*My settings may not be the best, therefore you may want to trial and error.
The following shows the named values for the A2DP\Settings key.
By default, A2DP uses a bitpool of 48. A lower bitpool value improves system performance. Increasing bitpool to a higher value causes an overhead on Bluetooth and system resources.
Microsoft suggests the following bitpool values for optimal buffer sizes.
30 - Low audio quality
40 - Medium audio quality
48 - High audio quality
58 - Excellent audio quality
-The maximum reported bit pool value, which can be negotiated with the peer device. Default value is 80.
-The minimum reported bit pool value, which can be negotiated with the peer device. Default value is 14.
-SBC sample rate to use. Default value is 44.1 KHz.
Click to expand...
Click to collapse
I am having the same problem as you on my HTC Incredible. Any idea of an app that lets you configure those settings for Android?

Jack for music, bluetooth for calls

Hi *.
Default output order for Touch HD is: external speaker, 3.5mm jack, bluetooth headset. So when I connect bluetooth headset while listening mp3s, jack output or external speaker will be turned off. But that's not what I want. Is there any way to have mp3s [or any other non-call audio] played throught jack, but incoming call throught blue headset? I really need this.

mietekxxx said:
Hi *.
Default output order for Touch HD is: external speaker, 3.5mm jack, bluetooth headset. So when I connect bluetooth headset while listening mp3s, jack output or external speaker will be turned off. But that's not what I want. Is there any way to have mp3s [or any other non-call audio] played throught jack, but incoming call throught blue headset? I really need this.
Click to expand...
Click to collapse
In the settings for the Bluetooth headset, there should be two check boxes ... one for "Wireless stereo" and another for "Handsfree".
I am guessing you have both ticked when you only wnat the Handsfree ticked, perhaps? Would that work?
HTH
Mal

Works like a charm Thanks.

Stereo bluetooth problems

When listening to music on my stereo bluetooth headphones and I get a phone call the ringtone will play through the headphones but will not play on the phones speaker,which makes me miss calls, this didn't happen until I updated my phone to the official froyo through mini kies,i have to keep shutting the phone on then off to get the sounds back on the phone. I have both the media and phone options checked on bluetooth options, anybody else notice the problem

I've noticed the exact same thing and am trying to narrow down the issue. Right now, I'm off a factory reset and haven't had the problem yet. I'll slowly be adding back the apps I normally use to see when I can reproduce the issue.
I've also had the issue present after talking over a bluetooth headphone as well. I haven't tried with a phone-only Bluetooth device, so it might be something related to being connected to media audio for all I know.
Instead of rebooting, you can fix the audio issue with any wired headset. After disconnecting the bluetooth device, plug in the wired headset and then press a volume key on the phone. The beep will then play through the speaker. Once this happens, you can unplug the headphones and the speaker will continue to work. Bit of a pain, but saves a power cycle.
Are you using anything fancy on your phone? Say, a different launcher than stock? I'd really like to narrow things down and if you can help find some exact way to reproduce the issue then maybe Samsung can get a fix out.

motokochan said:
Instead of rebooting, you can fix the audio issue with any wired headset. After disconnecting the bluetooth device, plug in the wired headset and then press a volume key on the phone. The beep will then play through the speaker. Once this happens, you can unplug the headphones and the speaker will continue to work. Bit of a pain, but saves a power cycle.
Click to expand...
Click to collapse
Instead, I just use the free headset toggle widget which does the same thing without needing to plug anything in. Perhaps it will be fixed in the 2.2.1 update.
Download here: http://code.google.com/p/toggleheadset/ and install through your favorite file manager.

I'm not using any special launchers or anything I did a hard reset to make sure and the problem still exists,I hope they send another update to fix this problem because I use Bluetooth alot!!!

Even when you make a call and start talking it happens it does the same thing, they definitely need to address this problem I love froyo, don't won't to revert back to 2.1!!

If we can narrow down the problem, it'll probably help Samsung to fix the core problem. Can you run an adb logcat and reproduce the issue then post the log?

I will give it a try!!!

Wait....so the problem is that when you are listening to music, it rings in the earphones but not the speaker, which in turns causes you to miss calls?
How would you miss the call if it rings right in your ear?
Sent from my SPH-D700 using XDA App

A_Flying_Fox said:
Wait....so the problem is that when you are listening to music, it rings in the earphones but not the speaker, which in turns causes you to miss calls?
How would you miss the call if it rings right in your ear?
Click to expand...
Click to collapse
Not quite. The issue is that after disconnecting the bluetooth device, the speaker will not issue any sound.

Okay, so i was finally able to reproduce the issue today. I paired my stereo bluetooth headphones and the issue started again. However, it's not limited to that as I can reproduce it with my car's bluetooth connection as well.
Interesting bits from a logcat:
I connect the headphones and play a music file (using Meridian player):
Code:
I/AudioHardwareALSA( 2385): Initialized ALSA PLAYBACK device AndroidPlayback_Bluetooth_normal
D/AudioHardwareALSA( 2385): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Little Endian)
D/AudioHardwareALSA( 2385): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2385): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2385): Buffer size: 2048
D/AudioHardwareALSA( 2385): Latency: 46439
Looks normal. So, I disconnect the headphones and try to play out the speaker:
Code:
I/BTL-IFS ( 2874): send_ctrl_msg: [BTL_IFS CTRL] send BTLIF_DTUN_SIGNAL_EVT (CTRL) 11 pbytes (hdl 15)
W/BTLD ( 2874): btui_security_cback( LINK FAILURE:: hci status: 19) 8==link super to
W/BTLD ( 2874): for bd_addr: REMOVED_BT_MAC
I/DTUN_CLNT( 2956): dtun-rx signal [DTUN_SIG_DM_LINK_DOWN] (id 48) len 13
D/DTUN_HCID4( 2956): dtun_dm_sig_link_down()
I/DTUN_HCID4( 2956): dtun_dm_sig_link_down device = 0xfa28 handle = 275 reason = 19
I/BluetoothEventLoop.cpp( 2497): event_filter: Received signal org.bluez.Device:PropertyChanged from /org/bluez/2956/hci0/dev_REMOVED_BT_MAC
D/BluetoothEventLoop( 2497): Device property changed:REMOVED_BT_MAC property:Disconnected
D/BT HSHFP( 2595): Received intent Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }
I/BT HSHFP( 2595): ACL disconnected
I/BluetoothService( 2497): ACL disconnected, mAclLinkCount = 0
D/BluetoothA2dpService( 2497): Received intent Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }
I/BluetoothHIDService( 2497): Received intent Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED (has extras) }, device = REMOVED_BT_MAC
I/BluetoothHIDService( 2497): ...ACL disconnected
E/MediaPlayer( 2497): message received msg=2, ext1=0, ext2=0
E/MediaPlayer( 2497): callback application
E/MediaPlayer( 2497): back from callback
I/AudioService( 2497): AudioFocus abandonAudioFocus() from [email protected]
W/BTLD ( 2874): dm_pm_timer expires
W/BTLD ( 2874): dm_pm_timer expires 0
W/BTLD ( 2874): proc dm_pm_timer expires
I/AudioHardwareALSA( 2385): Output standby called!!. Turn off PCM device.
...
D/AudioHardwareALSA( 2385):
D/AudioHardwareALSA( 2385): ALSA OPEN mode 0,device 128
I/AudioHardwareALSA( 2385): Try to open ALSA PLAYBACK device AndroidPlayback_Bluetooth_normal
I/AudioHardwareALSA( 2385): Initialized ALSA PLAYBACK device AndroidPlayback_Bluetooth_normal
D/AudioHardwareALSA( 2385): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Little Endian)
D/AudioHardwareALSA( 2385): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2385): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2385): Buffer size: 2048
D/AudioHardwareALSA( 2385): Latency: 46439
Looks like it's still trying to play out the disconnected BT device...
I plug in a pair of wired headphones (not a full headset), press the volume rocker button and see this:
Code:
V/HeadsetObserver( 2497): Headset UEVENT: {SUBSYSTEM=switch, SWITCH_STATE=2, DEVPATH=/devices/virtual/switch/h2w, SEQNUM=16078, ACTION=change, SWITCH_NAME=h2w}
I/HeadsetObserver( 2497): HEadSetObserver : newState =2, newName = h2w
I/HeadsetObserver( 2497): HEadSetObserver : newState == BIT_HEADSET_TV_OUT newState =2, newName = h2w
E/HeadsetObserver( 2497): tvout start
V/HeadsetObserver( 2497): Intent.ACTION_HEADSET_PLUG: state: 1 name: h2w mic: 0
I/FMRadioService( 2497): mReceiver: ACTION_HEADSET_PLUG
I/FMRadioService( 2497): ==> intent: Intent { act=android.intent.action.HEADSET_PLUG flg=0x40000000 (has extras) }
I/FMRadioService( 2497): state: 1
I/FMRadioService( 2497): name: h2w
V/TtySettingReceiver( 2595): state tty : false____state headset : true
...
E/AudioService( 2497): sendVolumeUpdate VOLUME_CHANGED_ACTION streamType = 2
D/BT HSHFP( 2595): Received intent Intent { act=android.media.VOLUME_CHANGED_ACTION (has extras) }
D/BluetoothA2dpService( 2497): Received intent Intent { act=android.media.VOLUME_CHANGED_ACTION (has extras) }
I/FMRadioService( 2497): mReceiver: VOLUME_CHANGED_ACTION
I/FMRadioService( 2497): stream: 2
I/FMRadioService( 2497): volume: 7
D/WindowManager( 2497): removeCallbacks-mVolumekeysInCallLongPress
I/KeyInputQueue( 2497): Input event
V/WindowManager( 2497): Dsptch to Window{47d565d0 com.sec.android.app.twlauncher/com.sec.android.app.twlauncher.Launcher paused=false}
E/AudioService( 2497): sendVolumeUpdate VOLUME_CHANGED_ACTION streamType = 2
D/BT HSHFP( 2595): Received intent Intent { act=android.media.VOLUME_CHANGED_ACTION (has extras) }
D/BluetoothA2dpService( 2497): Received intent Intent { act=android.media.VOLUME_CHANGED_ACTION (has extras) }
I/FMRadioService( 2497): mReceiver: VOLUME_CHANGED_ACTION
I/FMRadioService( 2497): stream: 2
I/FMRadioService( 2497): volume: 7
D/AudioHardwareALSA( 2385): AudioStreamOutALSA::setParameters() routing=10
D/AudioHardwareALSA( 2385):
D/AudioHardwareALSA( 2385): ALSA OPEN mode 0,device 10
I/AudioHardwareALSA( 2385): Try to open ALSA PLAYBACK device AndroidPlayback_Speaker_Headphone_normal
I/AudioHardwareALSA( 2385): Initialized ALSA PLAYBACK device AndroidPlayback_Speaker_Headphone_normal
D/AudioHardwareALSA( 2385): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Little Endian)
D/AudioHardwareALSA( 2385): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2385): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2385): Buffer size: 2048
D/AudioHardwareALSA( 2385): Latency: 46439
Now it's playing out the speaker.
Looks like something's possibly forgetting to switch to the right playback device. I could be wrong in the suspicion as I'm very inexperienced with Android internals. I welcome review by someone more experienced and would be glad to provide a full logcat output in private if needed.
I'll also be sending this data off to Samsung.

Hopefully Samsung will take this information and issue a fix or an ota for this because bluetooth is very important function,maybe there's a way to fix this with 2.1 J16 when it was working properly!!

Wow, I'm really glad I'm not the only one experiencing this!
This is a serious bug. Hopefully Samsung does fix this.
Thanks for posting the logcat results!
Sent from my SGH-T959 using XDA App