Related
Hi,
i have a very disapointing situation with my NOKIA HS-12W. I have this gadget from 2 months, and now everybody started to complain, that they cant understand our conversation when i am using my headset. It is only 70 cm from my device when i am driving, it is in th holder. But the sound quality is good only when there is less than 20 cm between the device and the headset.They said, that the sound is noisy and they hear only parts of the words. Do you have the same experience, and is there any solution for that? Or i should reconsider the value of the bluetooth feature of this devce.
Many thanks for any help
jep same situation here. got a t-mobile Rom installed and also using Nokia HS-12W. only the first week i reached the +- 9 till 10 meters distance. I have changed some registry settings and now it doesn't work any more. just 20 cm for stereo sound and a lot of stuttering.
i get almost 30 feet from my HT820 and i-take bluepro headphones. i haven't tested my Jabra250, but it's probably pretty good.
Yes, i tought the same, that i have made some registry changes which caused this. But now, after a hard reset , without any registry changes i have the same problem
kucsi said:
Yes, i tought the same, that i have made some registry changes which caused this. But now, after a hard reset , without any registry changes i have the same problem
Click to expand...
Click to collapse
same here... I've set my registry setting to medium quality so I've reduced the stuttering when it's on my side on my belt. When it's in headset mode I can move further but I can not move as long as 10 meters... s..cks.
Other choice was the SE HBH with the same design I think a 'normal' headset cannot be worn on the streets...
I have the Sony Ericsson stereo bt headset (simliar hang-around-the-neck style as the Nokia). When listening to music, I can't move the phone any further than my belt-clip without having the sound break-up.
So, in my experience, the maximum effective range is 10-20 cm. :x
wich ROM versions does everybody using?
Mine is: UNI_TMNL_130115_130233_11003_WWE_BL101_Ship
this is the latest T-mobile Rom what i know.
I am so sad. Until this i was so proud of having tis device.Today i talked with the QTEK service here in Hungary, and what they told, made me disapointed.They told, there was no solution for that.The Bluetooth antenna is too small, and there is nothing to do. So what is in the specification is a big lie. And they knew it. All we could do it to sue them . This device is to big for using as a standard phone.But with this bluetooth feature there is no other option
The Bluetooth Antenna on the Universal is fine, I can use Bluetooth ActiveSync to connect with my PC and it keeps signal even if I stand in the next room - so the problem is probably your Bluetooth headsets having a weak antenna, not the Universal...
sl9 said:
The Bluetooth Antenna on the Universal is fine, I can use Bluetooth ActiveSync to connect with my PC and it keeps signal even if I stand in the next room - so the problem is probably your Bluetooth headsets having a weak antenna, not the Universal...
Click to expand...
Click to collapse
I also have no problems with the bt range for transering files & synching. I also was satisfied with the range & quality with mono bt headsets for telephone calls. However, for bt stereo the range has been quite disappointing.
hello where in the registry did you change those setings ?.. i want to try it out
me too wanna try this.
(Update: 2/23/10: To replicate the problem, use a bluetooth headset, make a call, then walk away from the phone until you're almost out of range. That's exactly the problem I have when I'm holding the device, it doesn't matter where I am distance wise, the best audio call quality I get STARTS where most phones get when you're too far from the device. Ideas?)
After weeks (3 straight) of searching, I have to finally ask.
Does anyone else have an issue with the quality of their bluetooth connection (calls only) regardless of brand and distance from the phone?
I've purchased nearly 13 different bluetooth devices trying to fix this. Changing the distance from the actual handset (experimenting if there's a different to if the Hero is plugged in or not), the price of the bluetooth unit, what type it was (speaker phone unit only, carkit, headphones, ad2p or not, etc etc), and I still have a poor call quality call.
Reception isn't an issue, I've tried from full bars to almost no bars, and in every instance, when I disconnected the bluetooth and went back to using either speakerphone, headphones, or directly on the device, the noise went away.
You can only hear the noise when the remote party speaks, and it really sounds like the old analog bag phones in bad reception. Is there anything as far as changing settings on the bluetooth to improve the audio quality?
not really. the BT module sends information to the receiver and the receiver decodes that into audio. so you cant really set an EQ for BT with android at least so it basically depends on the receiving unit. while music is playing turn the volume down to 75% on the phone and thats the best quality you will get. im an audiophile and it works for me.
I have a Plantonics Stereo BT.
It works great on my Hero... Much better than my HTC Diamond!
Haven't had any trouble from my Jawbone 1. The sound quality isn't as good as it was on my TP, TP2 or Pre but it's ok. Haven't had any weird noises. But it does randomly disconnect from my Hero. Well the phone says it is still connected but I get no call notifications through it and when I answer, the audio is through the handset. Even right after I finish talking to someone through the BT. Gonna have to chalk it up to the Hero cause I've had no issuse with it on any other phones. Best BT ever in my opinion.
Yeah, I don't know. I have used the Jawbone II, Jawbone Prime, Moto H12, Moto H790, and Plantronics Voyager Pro all with no problems in sound quality, also audio quality is very important to me because I do have some hearing loss. My call quality with the Hero isn't quite as good as with my old Blackberry Curve, but it is still very functional as I use it at least an hour everyday. If you have gone through that many headsets it is quite possibly the device itself.
I don't know, I have 3 Hero's and I honestly don't like the quality of sound on any of them. One of them is just straight stock. I just wish I could get it with a clear quality as my old dumbphones have. I think I've been helped to discover the answer to my question, thank you all!
Hi guys
i read xda so much, but i don't write as well
i have a big issue with my galaxy s 2
i use a bt car stereo, with a2dp and avrcp support
i used to stream all my music collection from my iphone4
now i got my sgs2 and i love it... but
the audio stream looks "limited"
it seems a bandwidth issue, or i don't know a quality issue
with iphone4 i streamed at full quality, now the sgs2 sounds a lot worst
other than that, i have to disable wifi because if on, the music is choppy and skips a lot
with wifi off, the stream goes well, but it sound bad...
sorry for my not so perfect english... i hope there is a way to improve sound quality because i "live" with a2dp on in my car...
That's strange. My a2dp stream actually sound better from sgs2 than it does from my ipod touch 2nd gen, iphone or my computer (bluez).
Receiver is a belkin stereo a2dp receiver.
Are you sure that it's not in handsfree mode? Long press the a2dp device in bluetooth settings and there should be an option to select it to be a media device, make sure it's checked.
thanks for the reply gvoima, no it's in media device mode
i think the problem is the bitpool
i've got the same problem of this guy: http://forum.xda-developers.com/showthread.php?t=708685
there is an mp3 sample of the problem in the first page
gvoima said:
That's strange. My a2dp stream actually sound better from sgs2 than it does from my ipod touch 2nd gen, iphone or my computer (bluez).
Receiver is a belkin stereo a2dp receiver.
Are you sure that it's not in handsfree mode? Long press the a2dp device in bluetooth settings and there should be an option to select it to be a media device, make sure it's checked.
Click to expand...
Click to collapse
I got a belkin stereo receiver as well, but it sounds bad and choppy, just like the topic starter described. Though still compressed (this is a known issue for A2DP due to bandwidth limitations) songs sounds much better from my Nokia E52 work phone.
rikc said:
I got a belkin stereo receiver as well, but it sounds bad and choppy, just like the topic starter described. Though still compressed (this is a known issue for A2DP due to bandwidth limitations) songs sounds much better from my Nokia E52 work phone.
Click to expand...
Click to collapse
The "but my (insert phone) worked better" isn't really valid. For as many people who make that statement there are an equal number who are shocked that the SGS2 works where other phones haven't. This is kind of like the Wi-Fi issue. When two pieces of equipment don't interact well you can't just blame one of them.
In my car and on my Yamaha YSP-4000 the SGS2's Bluetooth works better than any phone I've used. That includes the HD2, G2, and G2X. The sound is much more defined and headset controls (random and repeat) show available for the first time. The SGS2 also feeds track info to the car which none of the others did.
Bluetooth connections and sound quality are always a big YMMV.
My Sony MW600 sound great, I use to have a Motorola Defy , and it use to have an "Enhanced Stereo" option in the blue-tooth menu, the Samsung S2 does not have this option.
@BarryH,
Oh I know, I not blaming the SGS2. I only think the SGS2 out sound to it's output module which is somehow less suitable for the kind of compression, maybe set by the Belkin module. Actually I'm currious if there would be ways to change the way the SGS2 sends sound signals via A2DP
rikc said:
@BarryH,
Oh I know, I not blaming the SGS2. I only think the SGS2 out sound to it's output module which is somehow less suitable for the kind of compression, maybe set by the Belkin module. Actually I'm currious if there would be ways to change the way the SGS2 sends sound signals via A2DP
Click to expand...
Click to collapse
LG's implementation of Bluetooth drove G2X owners crazy. Check out this thread from the G2X forum...
http://forum.xda-developers.com/showthread.php?t=1117769
Maybe it will help. The only other solution for the G2X was installing an AOSP ROM.
Well, I tried it (Bluetooth Fix Repair), but off-course that tool is for a problem the SGS2 does not have.
From the tinkering I've done now I know.
- Having MusicFX installed does not make a difference
- Video players running ffmpeg codec do also not make much difference in sound quality
- The -type- of file does make a difference, i.e. low bitrate files play better
This makes me think, is there a music program which can resample/recode music before playing. I'd rather have software do that than A2DP do it badly, or is mono output (other than all the tools enabling playback on mono headsets which is for pre-A2DP headsets and thus something else) possible?
Edit /system/etc/bluetooth/audio.conf
Uncomment "Master" option and set it to "True".
Uncomment "MaxConnections" and set it to 3.
Most Android devices have this file configured poorly by default, those 2 settings should help though.
I'd suggest also enabling HFP and AutoConnect.
Great! That definitly reduced creaking/noises and even the occasional stuttering music!
Since you seem to know your stuff, would there be a way to send a mono signal to (only) the A2DP stack and would this decrease the 'tin can' effect? I'd rather have better upper tones than stereo.
knightnz said:
Edit /system/etc/bluetooth/audio.conf
Uncomment "Master" option and set it to "True".
Uncomment "MaxConnections" and set it to 3.
Most Android devices have this file configured poorly by default, those 2 settings should help though.
I'd suggest also enabling HFP and AutoConnect.
Click to expand...
Click to collapse
Thanks for the suggestions...going to try this and see if the sound quality improves in my car stereo.
Till now the best A2dp sound quality was on my Nexus S, but that was with the help of custom rom development and vodoo sound. Worst was the g2x.
Sent from my GT-I9100 using XDA Premium App
Ok guys, I think I might have... accidentily... run into a phenonemon.
I tested my phone on a Creative D100 wireless speaker it it went great, no tin can sound, no hickups.
This proved to me that there had to be something wrong. Now when I was posting here earlier I was listening a lot to music and at a certain moment I thought... wait I'm not hearing a tin-can sound anymore. However, later on while testing I heard it again so I thought I imagined it.
Powering off the phone and powering on again I was able to create this again. No tin can sound... however a lot of hickups (as if a lot of data had to be sent and it didn't quite fit). I made a call to my work phone (sound on the handset) to test and then the tin can sound was there again, no hick ups anymore though. Strangely enough a haven't been able to replicate the 'no tin can sound but hickup situation' though by powering off and on again. Tried after playing on the Belkin on the D100 again and no problems at all, great sound and no hickups whatsoever.
It appears to be a bigger issue with android connected to the bitpool setting the bluetooth receiver desires...
http://forum.xda-developers.com/showthread.php?p=14944891#post14944891
Let's hope the upcoming Cynogen can fix this issue.
I too felt that the A2DP sound quality on the Nokia BH103 is crap as compared to my Nokia 5800 (sounded even better than stock wired headset). It also uses a lot more battery, I find mediaserver using a lot of battery.
How do we escalate this to Samsung?
knightnz said:
Edit /system/etc/bluetooth/audio.conf
Uncomment "Master" option and set it to "True".
Uncomment "MaxConnections" and set it to 3.
Most Android devices have this file configured poorly by default, those 2 settings should help though.
I'd suggest also enabling HFP and AutoConnect.
Click to expand...
Click to collapse
Sorry, i'm on darky rom and i don't find this file, could someone help me out ?
Thanks
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
Is there any way to fix the bluetooth audio quality other than switching to a CM-based ROM?
My old phone over bluetooth sounds fine. My S4 via a wired connection sounds fine. My S4 over bluetooth sounds like everything was sampled at 32 kHz. All other equipment is the same, so I'm relatively sure it's a bluetooth-specific issue. My girlfriend's S4 does the same thing.
So, any fixes? I'd really like to avoid switching to an aftermarket ROM right now.
Edit: L337 on AT&T
Tourney3p0 said:
Is there any way to fix the bluetooth audio quality other than switching to a CM-based ROM?
My old phone over bluetooth sounds fine. My S4 via a wired connection sounds fine. My S4 over bluetooth sounds like everything was sampled at 32 kHz. All other equipment is the same, so I'm relatively sure it's a bluetooth-specific issue. My girlfriend's S4 does the same thing.
So, any fixes? I'd really like to avoid switching to an aftermarket ROM right now.
Click to expand...
Click to collapse
Random guess: Could this issue be caused by the adaptive sound feature? I'm not a true audiophile, but I haven't noticed a problem through my receiver in the car or at home.
Try playing something with cymbals and a lot of treble. Turn the volume up a bit higher than normal while still maintaining a reasonable level. The cymbals sound like someone is smacking a plastic grocery bag with a stick instead of being crisp and clean like they should be. I can then disconnect the S4, connect my old phone, and play the same mp3 without any sound distortion. Or I can play the same mp3 from the S4 via aux and it sounds fine.
Try it on both bluetooth and aux. If you truly don't notice a difference, I guess it must just be my phone. If it does do it however, you definitely don't need to be an audiophile to hear it.
My old phone had the exact same problem until I moved to JB on a CM build. The problem there is well-documented as existing on the S3 (try looking up bitpool settings), but I kind of figured they would have fixed it by now. I'm coming from the world of HTC, so I was hoping there is a fix for Samsung.
Sorry to revive this thread, but I have an update.
My car has built-in bluetooth for phone only, so no a2dp. I have a third-party bluetooth adapter that I'm using for music.
I've found that when both of these are connected, the audio quality (especially on trebles and guitars with distortion) is absolutely terrible. That was the point of my original post. Since then, I've determined that this happens ONLY when I am paired with both my car and my third-party bluetooth. I can actually pair and unpair from my car in real time and hear the audio quality immediately get better/worse. The quality gets worse immediately when it pairs, even if the car bluetooth is not in use (but still connected).
I've verified this is the case with both my phone and my girlfriend's S4. Can anyone with such a setup verify this does or does not happen for them? I'm thinking this is a bug with the bluetooth stack, and it'd be nice if it could be fixed. If anyone can try pairing to two different devices and confirm my problem, I'll start a bug report with Samsung. Otherwise I'll try another bluetooth adapter for a2dp.