I've searched here for hours and haven't found a fix for this. Unlike many of the posts I've found and read here, I don't have any issues with skipping with my bluetooth earbuds.
On my 8525 with 53 decimal set for bitpool and max bitpool and jointstereo=0 I get tinny hissing artifacts. not worth using.
these are no-name earbuds similar to the itech clip ones. don't know who made em-came from ebay. they worked great with my widcomm stack harrier.
increasing the bitpool numbers further has no effect on these. they don't seem to skip at all though. am I missing another reg setting change?
are there off the shelf headphones that don't skip without the a2dpfix service and work well with hermes? I see mixed answers on many of them.
just when I think this phone is pretty stable it locked up this morning and didn't alarm. I overslept...
I'm also having same annoying hiss issue, afaik only another bt stack (namely widcomm) or maybe new aku update would solve this problem.
don't know where they are going with porting widcomm to hermes,
but hope they have some progress...
-kha
Hacks, registry tweaks section of Wiki, search "A2DP" or "stereo". I use sony-ericsson hbh-ds970's and after the tweak, sound as good as my old wired earbuds. Only shortcoming is the occasional sound drop (millisecond or two, but still annoying). Setting PocketPlayer priority to "normal" virtually eliminates the problem. An extreme solution is applying Sleuth's A2DP fix... search the wiki for more details.
Cheers
aquanaut88 said:
Hacks, registry tweaks section of Wiki, search "A2DP" or "stereo". I use sony-ericsson hbh-ds970's and after the tweak, sound as good as my old wired earbuds. Only shortcoming is the occasional sound drop (millisecond or two, but still annoying). Setting PocketPlayer priority to "normal" virtually eliminates the problem. An extreme solution is applying Sleuth's A2DP fix... search the wiki for more details.
Cheers
Click to expand...
Click to collapse
You mean skipping issue rather than hissing sound issue ?
-Kha
The hiss is a known artifact of the M$ BT stack. My testing with the Widcomm stack eliminated this issue. However, out of the box version 1 Widcomm tests showed decreased fidelity and noticable buzzing on the high end. However, I believe there's a number of A2DP fidelity tweaks that can be applied to correct this. I will start working on this when superdave gets the handsfree issue solved .
Well, I was unsure if I should post this under one of the old posts, but I decided to start it as a new clean post...
Many are having problem with "hissing" noise, joint-stereo and low bitrate(or bitpool). For my sake, I've tried "fit4cat - Hermes Tweaker", "Sleuth255 A2DP fix" and several other methods, but without beeing able to get the soundquality I want from my headset.
Now, this is what worked for me after tweaking around with the registry a while, and endless pairing sessions
Download a registry editor(I use PHM, http://www.phm.lu/Products/PocketPC/RegEdit/ <- Download the PocketPC 2002/2003 ARM/PXA)
1: Turn off bluethooth on the Trinity
2: Unpair the Trinity with the headset(Delete the headset from the list!)
3: Change the following registry settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2 DP\Settings
MaxSupportedBitPool=80
MinSupportedBitPool=40 (or more if you want)
(if these arn't there, add them!)
And DELETE:
UseJointStereo = 0/1 (depending on whatever you have put there before)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
Priority256=149
(let the rest be as it is)
4: Reboot
5: Now, DO NOT use the headset for direct pairing!(since you've already added your phone to the headset, pressing a button on it will useually pair it back with the Trinity) <- This seems to be the function that triggers the sound-problem...
Instead, set the headset in visible mode, and use the trinity to pair(search for new devices), when you find the headset and pair it, you will hear the pairing-sound from the trinity-speaker, and NOT the headset.
Now you can enjoy high quality stereo sound without any disturbance
But, the problem comes when you turn off your Trinity, or the headset. If you try to connect the headset and the phone by using the connectbutton/playbutton on the headset, it will pair, but this time you will hear the pairing sound in the headset, and then you have all your problems back... So then you have to turn of bluethooth, delete the headset from the trinity, and add it back once again by turing the headset in visible mode again.
So the solution to this, is to go to the device list on the trinity after you have lost connection with the headset(this is if you have turned of the trinity or the headset), and hold the stylus on it and choose "Use as wirelss stereo" and "use as handsfree"...
Thanks to all of you guys here who have posted solutions to the A2DP problems And if anyone have suggestions to other values that are better fit then the onces I've supplied, share them with us
And if all of this have been posted in another thread that I've missed out, the moderators are free to delete this one
Good grief, I can only imagine how many times you had to pair the headset before you noticed what was going on LOL, hope you didn't turn blue in the face
I imagine a ROM update could fix this problem.
Tiemen said:
Good grief, I can only imagine how many times you had to pair the headset before you noticed what was going on LOL, hope you didn't turn blue in the face
I imagine a ROM update could fix this problem.
Click to expand...
Click to collapse
Hehe! The thing that made me going was that I was able to get perfect sound once or twice, and since I made it work those few times I just had to find out what I actually did that made this work (And paying 175$ for the headset also keept me fueled for a while ) hehe!
I think I've used about 5-6 hours total these two days sitting pairing, adjusting settings, rebooting(ARGH!), untill I found out that the problem actually occurs when you use the headset to pair instead of the trinity
I don't understand what is it with bluetooth stereo:
quality is not good enough to listen to music 64 kbps... no bass, no medium, nothing just a hiss.
and plus you get 80% cpu (with a 400Mhz...), just to encode this crappy 64 kbps.
Yes exactly for all people having so many skipping problems check your cpu with taskmgr.
So you cannot play video with A2DP unless you have 1Ghz!!! good for battery life.
If you like music you want good earbuds. There's none with A2DP.
So what's the point again apart from having to charge one more device?
meroupow said:
I don't understand what is it with bluetooth stereo:
quality is not good enough to listen to music 64 kbps... no bass, no medium, nothing just a hiss.
and plus you get 80% cpu (with a 400Mhz...), just to encode this crappy 64 kbps.
Yes exactly for all people having so many skipping problems check your cpu with taskmgr.
So you cannot play video with A2DP unless you have 1Ghz!!! good for battery life.
If you like music you want good earbuds. There's none with A2DP.
So what's the point again apart from having to charge one more device?
Click to expand...
Click to collapse
1: Well, I'm not sure on the bluetooth 2.0 specs, so If there is a spec limit on 64kbps, then this is new to me.
2: And the skippingproblem is not just connected to the CPU-usage.. But if you have some info on this issue, then please; do share it with us.
3: A2DP headset with minijack is available many places, even HTC has one. And if you take a look at DS970, you will see that it's the same as Sony MDR-series.
4: And well, the CPU usage is a issue, but that is the only part that I agree with you on..(but let us be frank, I've bought a pair of A2DP headset, so I do smell a bit "conflict of interests" here...)
And to the bottom line, I've bought the Trinity because it's one hell of a gadget, and so is bluetooth stereo So if anyone want to shoot me for that, well hell yeah, go ahead
Edit: And FYI meroupow: I do feel you are a bit rude in the way you wrote that response, or at least a bit arrogant when you post a comment like that. Trying to mock people who have bought A2DP headsets and are tweaking and fixing issues to make them work correct(this also goes for GPS on the phone, black coating comming off, improving camera quality, getting the ATI ImageOn to work correctly... etc) . And I must honestly say that yes, you do have some points there, but you should be able to present your views in a much more polite way...
Sound better but discontinuou. Impossible ear music. The sound goes on and off continuously. Why?. How can I do?
I am sorry if you felt I was being rude.
That was not my point and It was probably the wrong place to say what I said.
It is just that just like you I bought this A2DP stuff with my Wizard.
Just like you I tweaked it as much as I could and managed to get it work.
The problem is when it comes to sound quality is important and just working is not enough.
When you show your happiness because it's finally working, people think you are happy because it's good and they are buying it. And get disappointed too.
I just wanted to warn people on the fact that it's not working to watch movies because of cpu and that a 5$ earbud will have far superior sound quality.
It's just a toy and by no way a mature technology.
I've got a CB2530, hard to pair and I still don't know what do I do for the pairing to be successful, but I do manage to pair it after a few attempts, on the registry I just disable jointstereo, set the MaxSupportedBitPool to 320 and the quality is quite nice and with minimal skipping. High cpu usage of course, but if I set the MaxSupportedBitPool to 80 the quality is quite crappy and the device gets equally sluggish(gets worse when you touch on the screen, as K-Rally does even with the new ROM).
As for the pairing, I still haven't confirmed, but I think the registry setting that enables the bluesnarf option on BTCrawler has something to do with it(the bluetooth ISC mode thing), because right after setting it I managed to pair the headset right away, the thing is, I was also successful in other occasions when I hadn't set that reg. option.
Hearing the pairing sound from the trinity or headset doesn't indicate anything on my case, and I think I've already tried these reg settings you mention, but I'll try them again as soon as I get home to see if there's any difference and post the results.
meroupow said:
It is just that just like you I bought this A2DP stuff with my Wizard.
Just like you I tweaked it as much as I could and managed to get it work.
The problem is when it comes to sound quality is important and just working is not enough.
Click to expand...
Click to collapse
Install the Widcomm BT stack. With that, you won't have complaints - neither have I.
meroupow said:
I don't understand what is it with bluetooth stereo:
quality is not good enough to listen to music 64 kbps... no bass, no medium, nothing just a hiss.
and plus you get 80% cpu (with a 400Mhz...), just to encode this crappy 64 kbps.
Yes exactly for all people having so many skipping problems check your cpu with taskmgr.
Click to expand...
Click to collapse
Switch to the Widcomm BT stack.
neofix said:
5: Now, DO NOT use the headset for direct pairing!(since you've already added your phone to the headset, pressing a button on it will useually pair it back with the Trinity) <- This seems to be the function that triggers the sound-problem...
Instead, set the headset in visible mode, and use the trinity to pair(search for new devices), when you find the headset and pair it, you will hear the pairing-sound from the trinity-speaker, and NOT the headset.
Now you can enjoy high quality stereo sound without any disturbance
But, the problem comes when you turn off your Trinity, or the headset. If you try to connect the headset and the phone by using the connectbutton/playbutton on the headset, it will pair, but this time you will hear the pairing sound in the headset, and then you have all your problems back... So then you have to turn of bluethooth, delete the headset from the trinity, and add it back once again by turing the headset in visible mode again.
Click to expand...
Click to collapse
Does anyone know what is changed when you DO pair with the button on the headphones? With some models, you MUST do it because, otherwise, the music will be muted after about a second (see http://forum.xda-developers.com/showthread.php?t=282008 for more info).
I've searched around in the Registry for changes, without any success. It's possible we could directly edit the headphone connection-dependent parameters set AFTER the headphone's initiating the connection to avoid sound problems. If we knew where they're stored, that is.
Menneisyys said:
Switch to the Widcomm BT stack.
Click to expand...
Click to collapse
On trinity?
meroupow said:
I am sorry if you felt I was being rude.
That was not my point and It was probably the wrong place to say what I said.
It is just that just like you I bought this A2DP stuff with my Wizard.
Just like you I tweaked it as much as I could and managed to get it work.
The problem is when it comes to sound quality is important and just working is not enough.
When you show your happiness because it's finally working, people think you are happy because it's good and they are buying it. And get disappointed too.
I just wanted to warn people on the fact that it's not working to watch movies because of cpu and that a 5$ earbud will have far superior sound quality.
It's just a toy and by no way a mature technology.
Click to expand...
Click to collapse
BTW: is it the profile and software on the phones/PDAs that arn't handling it, or is it the standard itself that sucks? (or in other words, should I keep my headset for later usage or return it to the store)
I use Plantronics 590a and the skipping problem appears very rarely, mainly when I use volume/track buttons on headset. However, yesterday I also connected the headset to a normal stereo (via the 3.5mm adapter) and noticed the same occasional skipping. So in my opinion the skipping issue problem might be from headset, not Trinity.
I also tried a Nokia stereo bluetooth headset and noticed serious skipping problems - unusable.
PS: there is indeed a skipping problem if I open/close other applications while listening to music. It looks like the processor is very busy - system very slow etc.
PPS: any suggestions for a player that has equalizer? WMP doesn't and the sound is not that great (especially when compared to my old SE P900 which had an excellent player - best I've heard so far... )
Originally Posted by Menneisyys
Switch to the Widcomm BT stack.
Click to expand...
Click to collapse
If you tell me how I'll be glad to try...
I've never managed to do it sucessfully with my Prophet (witch had the same A2DP sound quality problem as it come with taht Fu***g, crappy, buggy, foot-coded MS BT stack)
Stereo BT experience is very positive
Hi all,
As always, someone has to have a different view of the issue. I got my trinity a couple of weeks ago and went and bought a Plantronics Pulsar 280 stereo headset. Mostly because of the stereo jack. I have not updated trinity nor have I applied any fixes, just paired right out of the box, as always from trinity BT manager. It really sounds great, particularlly the base is fantastic because of the earbud design. Even you may choose the actual headset of your dreams by using the standard 2.5mm jack. I have owned a "no brand" headset (still do) but it is not BT 2.0 and I think it makes a difference. The plantronics does not skip and it sounds great. Most of my MP3 is 128k and above so no limits with that. I have not checked my registry settings as they are default rom image set. I am using ROM 1.15.412.2 and Radio 1.20.00.11 (my trinity only speaks spanish for now, hope to change that soon).
Point being that the software and quality of the headphones makes all the difference, don't be so quick to blame trinity, just a piece of my mind. Keep it up guys!!!
baramuse said:
If you tell me how I'll be glad to try...
I've never managed to do it sucessfully with my Prophet (witch had the same A2DP sound quality problem as it come with taht Fu***g, crappy, buggy, foot-coded MS BT stack)
Click to expand...
Click to collapse
Yes, how do you change the BT stack on the Trinity?
Thanks.
danosimo said:
Hi all,
I have not updated trinity nor have I applied any fixes, just paired right out of the box, as always from trinity BT manager. It really sounds great, particularlly the base is fantastic because of the earbud design.
Click to expand...
Click to collapse
If you haven't changed anything it might sound great but it definitely sounds MONO!
aZooZa said:
Yes, how do you change the BT stack on the Trinity?
Thanks.
Click to expand...
Click to collapse
Up to now, I haven't managed to do it; see http://forum.xda-developers.com/showthread.php?t=291605 and http://forum.xda-developers.com/showthread.php?t=286094 . Sorry for telling you it might be possible - I assumed it would, as it is on most other HTC models.
anonimo said:
If you haven't changed anything it might sound great but it definitely sounds MONO!
Click to expand...
Click to collapse
set UseJointStereo to 0
I was wondering if any of you who has access to this device tried to see if it also suffers from high pitched noise like other devices when used with A2DP devices?
Is this using the sandard WM bluetooth stack or have they used an improved one?
Thanks
the Bitpool could be set as high as possible, dont know why MS set the default at very low since many devices support high data streaming.
without tweaking program, average people would think bluetooth quality is poor on this device.
Lurking around for years, I would expect anyone to search and apply suggested fixes in this forum before coming to a conclusion and askind this question.
Actually, I have applied most of those settings in both polaris and diamond. Even yough it is reduced, you still notice the noise during silence. Especially id device volume is lower and receiver volume is higher. This wasn't the case in n95 and SE m600.
Similarly in Vista with built in bluetooth stack there is some noise. Using a different stack such as Widcomm produced totally different results with same receiver.
if it was good in the m600... sony ericsson...
but it's made by HTC so????
Hi all !
I'm looking around for ways to better my audio experiences in A2DP with my HTC Touch Diamond. I keep hearing these high pitched metallic noises, and based on your posts, it could be an issue with Bluetooth stack. Is it the same with Xperia ? I mean, does A2DP sucks ?
These noises are a nightmare... I am using Diamond Tweak for my Diamond, any setting ideas ? Didn't try anythng so far...
Thanks a lot !
hi
i am using sony ericsson bt headset - hbh-pv740
on my previous phones (iphone 3g and se w910i) the volume level was good enough to feel comfortable - on my hd2 it is on the 100% level but still quiet.
any ideas how to improve bt voice level?
masi0 said:
hi
i am using sony ericsson bt headset - hbh-pv740
on my previous phones (iphone 3g and se w910i) the volume level was good enough to feel comfortable - on my hd2 it is on the 100% level but still quiet.
any ideas how to improve bt voice level?
Click to expand...
Click to collapse
had the same issue, its due to the none standard bluetooth stack, i just changed to a new nokia bluetooth headset with volymecontrols on it, theese work 100% but my old ones without volyme conrol is so quiet i bearly hear the one im talking to, i got it a little better by doing the following..
use advanced config 3.3 goto bluetooth settings and put ALL values to max, reboot and thats it.
please tell me how this affected volyme for you!
smaberg said:
had the same issue, its due to the none standard bluetooth stack, i just changed to a new nokia bluetooth headset with volymecontrols on it, theese work 100% but my old ones without volyme conrol is so quiet i bearly hear the one im talking to, i got it a little better by doing the following..
use advanced config 3.3 goto bluetooth settings and put ALL values to max, reboot and thats it.
please tell me how this affected volyme for you!
Click to expand...
Click to collapse
Shjena! my BT does have volume control, however I will date to try this soft to gain BT settings
Thx
I have a chinese bluetooth rearview mirror without digital volume control (only an analog knob like a fm radio volume one), and the output volume was extremely low with my new hd2 (with a nokia n97 was perfect).
Tried to modify registry settings without any results.
Then I discovered that disabling "single volume" for ringtone/system in settings i was able to raise the conversation volume using the hardware volume button on the left of hd2. Now i'm totally satisfied with the output power.
you might set the volume with the volume keys on the phone when connected to headset.
We have been using the Sennheiser CC550 professional wired headsets for years with a range of phones, Nokia, SE, Iphone (you can buy different endplugs). But to my astonishment the sound from the microphone is crap with the S2. After extensive research we haven found out that this is a general problem with Samsung, Google/Samsung telephones and S2, no professional headset (call center type) that we or our supplier have tried (we tried a lot). We also checked the wiering scheme to exclude any "grounding" problem, and can't find a problem there either.
Anyone got a wired call center type headset to work?
I have done some reserach and it seems that the condensator microphones used in electronic headsets have to voltage standards (someting like 1,5 V and 2,3 V) - could it be that Samsung uses the lower voltage or someting.
To add on the burden the bluetooth implementation in S2 is crap (tried Plantronic Discovery - doesn't work at all and SE WM600 works but not very well and doesn't have a micrphone "boom".
Any suggestions?
I am using Plantronics Discovery everyday from the very first day I bought
my SGS2 without any problems whatsoever. I have still stock 2.3.3 fw on my
phone, plus the matching cf-root. Are you on stock fw as well, or have you
flashed a custom ROM - maybe this is to blame?
As for the wired headset issue in general, it is a fact the the Android
implementation (in general - regardless of manufacturer) is, to say the least,
mediocre. No wired headset with in-line remote works (i.e. volume control,
skip/forward, etc) without custom apps and ridiculous button press combinations.
Thanks four your reply. I have uppgraded a few orginal ROMs, currently on Cognition 1.6. The problem with Samsungs bluetooth stack on S2 seems to be widespread, we bouth the WM 600 as it seemed to have the least issues and it's headset sond is ok if not good (don't mix the headset profile up with the A2DP bluethooth "music" profile which is not engaged in hedset mode) . The CM7 ROM seems to have sorted out the bluetooth stack problem, but have other issues. Our wired headset problem is not related to in line controll buttons (or anything with media playback for that matter). This is another aspect of the headset functionality that we don't use e.g. the CC550 don't even have any buttons - as it is a "call center" headset. Our focus is pure "talk" sound quality - and particular microphone (outgoing) sound quality as the CC550 (and other wired headsets) relays the speaker at the other end normally (i.e. good). As a sidenote maybee Android 4 supports USB headsets, it seems possible to connect a DACT anyways, this would solve our issue /Regards voz
Don't know if you have the same problem as I do; here is what happens with my microphone issues. Maybe related?
When using any wired headset, everybody will complain that I am "too loud". Not just painful volume, but distorted. At first I thought it had to do with the frequency of my voice or something, but apparently people can hear my car radio at a volume so low I have forgotten that it is on.
Another thing I have noticed is when I am using headphones with a microphone (not necessarily talking on the phone) I hear buzzing noises, usually when interacting with the phone. For some reason when I use Twitter it's really bad. Once, while I was on the phone somebody said they could hear it too.
My only solution to the mic-gain issue was to enter service menu and lower mic gain levels, of course when I reboot settings are lost and to be honest when I forget to re-enter them, my friends and coworkers take the opportunity to ream me out.
*#197328640#
[5] audio
[1] nb (voice call)
[2] headset
[1] volume
[4]dst speech tx volume: i put 60 here, default is 88, but that is too loud. tx = transmit, many instructions say to adjust rx value, but that is to receive, so that would be your earbuds, not mic.
If anybody knows another fix, or way to make an adjustment permanent I would love to know.
Interesting, I cranked it up to 100, see how it goes. There are some other interesting settings, eg. Tx Gain - do you know what that is for?
A hassel to enter them again after reboot thoug!
Vozie_Stockholm said:
Interesting, I cranked it up to 100, see how it goes. There are some other interesting settings, eg. Tx Gain - do you know what that is for?
A hassel to enter them again after reboot thoug!
Click to expand...
Click to collapse
My value for that and the 2 things before it are "0x6132"
I know this service menu isn't really meant for end-users, but it would be great if there was a little more documentation we could find regarding these values and what it all means.
[4]dst speech tx volume: tried 100 - increased the volume, tried 60 decreased the voluem - so it does work. However, the problem with the Sennheiser cc550 is that the Galaxy S2 changes the frequency response or something - so the volume is actually ok with the default setting at 88, but the sound comes out "high pitched" at the other end. To me it seems like the microphone in the headset is not feed properly from the handset. For an article on the subject see http://www.hobby-hour.com/electronics/computer_microphone.php