Related
In case anyone was curious, A2DP really doesnt sound any better between these builds. I'm starting to give up hope, maybe it's just my phone. The sound quality difference is night and day between my Vibrant and the myTouch 3G I have. I've tried on both my Kenwood head unit in my car and a pair of bluetooth headphones so I'm certain it's not the device I'm pairing with.
Ugh, just needed to vent, thanks.
pardon my ignorance, but i keep reading about A2DP and I finally want to find out what it is.
What is it?!?! thanks!!
A2DP is a bluetooth connection profile that supports high quality stereo audio. In the Vibrant's case however it is far from high quality. I was finally able to try another Vibrant today and it sounds just the same so now I know it's not just my phone. Some songs actually pass as decent bust most have a scratchy sound in the background and just lack overall depth. It really sounds like the bitrate is set too low on the Vibrant. Sabotage by the Bestie Boys for example has constant background noise/distortion that is not present when listening with wired headphones.
I've been digging around and swapping files around with the Korean Rom that has a supposed fix but I haven't made any progress.
One of the reasons I'd really like the Vibrant to sound better is because my Head Unit in my car supports A2DP. I have an app on my Vibrant called Tasker set to automatically fire up Pandora when a bluetooth connection is detected. So basically I can start my car and have my phone automatically start playing Pandora through my stereo, I can even advance songs with my dash controls. The audio quality can make it difficult to enjoy, My wife's myTouch3g on the other hand sounds superb on this same setup.
thanks for the response. i don't have a bluetooth set so that's probably why i haven't noticed this.
It really gets me down that my GPS, Compass, and A2DP are all broken on this phone. I'm gonna try and hold out for another month on a fix. If they released it in Korea hopefully they will release it here. Maybe I can talk Eugene or another dev to look into it
Audio quality is one of those subjective things and I really think a casual listener might not notice the problem but once you do you can't ignore it.
Strange, my BT sounds great streaming music through A2DP. I'm just on the stock Eclair build and streaming music through a Sony BT receiver, MW600. It's not an audiophile solution, but pushing music through some high-end IEMs sound perfectly fine for mobile listening. Maybe your hardware is bad?
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/korean-galaxy-s-receives-update-version-dg07-samsung-expects-to-sell-10-million-worldwide/
chadti99 said:
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/korean-galaxy-s-receives-update-version-dg07-samsung-expects-to-sell-10-million-worldwide/
Click to expand...
Click to collapse
Honestly, the quality of sound threw my A2DP is better than threw my headphone jack
jz9833 said:
Honestly, the quality of sound threw my A2DP is better than threw my headphone jack
Click to expand...
Click to collapse
Hi jz9833, what bluetooth device are you pairing your Vibrant with? Also what firmware, music app, file format are you using?
Have you considered going back to the stock ROM?
BT on mine is virtually identical to the headphone jack output. With Ety ER4p I can detect a little bit of digital hiss, but it's not really noticeable in a mobile environment.
Kubernetes said:
Have you considered going back to the stock ROM?
BT on mine is virtually identical to the headphone jack output. With Ety ER4p I can detect a little bit of digital hiss, but it's not really noticeable in a mobile environment.
Click to expand...
Click to collapse
Just today I tried a friends brand new out of the box Vibrant and I could still hear distortion/crackling at high frequencies. I then paired my headphones to my other friends iPhone4 just seconds after testing the new Vibrant and guess what, no distortion.
Man, I don't know what to say to you. My Vibrant sounds better out of BT than my iPod does out of its headphone jack. What BT headset are you using? For some strange reason they may just not get along. I've got a Sony MW600 and it's fantastic.
chadti99 said:
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/kor...samsung-expects-to-sell-10-million-worldwide/
Click to expand...
Click to collapse
There is no word on if this fixed it or not and according to your link this has nothing to do with Samsung.
Look, if you don't know that Samsung has acknowledged GPS by now, has already fixed the compass in the JI4 series you mentioned in this thread, you should just jump over to Android 2.2 and it's problems.. sounds like you won't be getting a fix either way according to your own links
chadti99 said:
Hi jz9833, what bluetooth device are you pairing your Vibrant with? Also what firmware, music app, file format are you using?
Click to expand...
Click to collapse
I am on stock vibrant, using the stock music/video app, playing mp3s, mp4s, avis, all going to my Sony MW600s.
heygrl said:
There is no word on if this fixed it or not and according to your link this has nothing to do with Samsung.
Look, if you don't know that Samsung has acknowledged GPS by now, has already fixed the compass in the JI4 series you mentioned in this thread, you should just jump over to Android 2.2 and it's problems.. sounds like you won't be getting a fix either way according to your own links
Click to expand...
Click to collapse
The first link confirms that other Android devices are having the same issue. Again my wife's myTouch3G doesn't suffer from the problem so I think it could be a simple bit rate setting that some manufacturers are overlooking.
The second link confirms that there is an A2DP problem on the Samsung Galaxy S and a fix exists.
chadti99 said:
The first link confirms that other Android devices are having the same issue. Again my wife's myTouch3G doesn't suffer from the problem so I think it could be a simple bit rate setting that some manufacturers are overlooking.
The second link confirms that there is an A2DP problem on the Samsung Galaxy S and a fix exists.
Click to expand...
Click to collapse
No it doesn't. You don't know if the "fix" is not a "fix". The myTouch 3G has Android 1.6 stock and if she hasn't changed it, it's still running Android 1.6.
heygrl said:
No it doesn't. You don't know if the "fix" is not a "fix". The myTouch 3G has Android 1.6 stock and if she hasn't changed it, it's still running Android 1.6.
Click to expand...
Click to collapse
I'm not sure what point you are trying to make, I still hear the distortion on a bone stock Vibrant. The reason I tried these beta builds was because I was hoping that Samsung would have incorporated the A2DP update. And yes the mytouch3g is running Android 1.6.
What does "You don't know if the "fix" is not a "fix"" mean? I think the fact that Samsung released an update for the Korean Galaxy S that improves A2DP quality pretty much sums it up, there was a problem and they fixed it.
This reminds me of the Oscar Rogers skit on SNL, "Sombeody needs to look at this mess and fix it!", lol.
chadti99 said:
I'm not sure what point you are trying to make, I still hear the distortion on a bone stock Vibrant. The reason I tried these beta builds was because I was hoping that Samsung would have incorporated the A2DP update. And yes the mytouch3g is running Android 1.6.
What does "You don't know if the "fix" is not a "fix"" mean? I think the fact that Samsung released an update for the Korean Galaxy S that improves A2DP quality pretty much sums it up, there was a problem and they fixed it.
This reminds me of the Oscar Rogers skit on SNL, "Sombeody needs to look at this mess and fix it!", lol.
Click to expand...
Click to collapse
Have you heard the purported fix on your phone? Have you seen what other people have said about it? No and no.
heygrl said:
Have you heard the purported fix on your phone? Have you seen what other people have said about it? No and no.
Click to expand...
Click to collapse
This is true, I have no idea what the A2DP fix does besides doing what Samsung claims it does, improve A2DP playback quality, which is exactly what I want. What is your point again?
Bluetooth audio still sounds poor on the new JI5 build. I've tried on three different Vibrants and three different bluetooth audio devices and have had others hear exactly what I hear. My wife's exact words, "Your phone sounds like a radio broadcast and my phone sounds like a CD."
I spoke to Samsung and they acknowledged there was a problem and said it was due to my devices not being Bluetooth 3.0 compatible. To my knowledge you can't even buy headphones that support 3.0 yet. I really wish they could fix this, I really like the phone overall.
New to the Vega as of 4 days ago so decided to jump straight in and run it on vegacomb 1.7 from the off. Working great apart from the really poor quality of the sound when using the headphone jack. Ive done a couple of searches and cant find many other having this issue. Really liking vegacomb but am considering a different ROM as its that bad, out of the speakers its what i expected but the sound from the headphone jack is tinny as hell. Ive tried using poweramps EQ to improve it but no joy it just sounds distorted.
Any pointers
cheers D
Hi the sound is tinny with vegacomb at the moment. I saw someone say using a power amp type application and set it to mega bass or something and that helps otherwise were all waiting for the new release which is coming along over on modaco site but a little slower than I had hoped due to memory issues being only 512mb ram but looks like they are getting around it and have come a long way in a short time.
Sent from my Desire HD using Tapatalk
I'l maybe hold off then for a while just getting to grips with vegacomb and the fact its working with my 3g dongle straight away is a real bonus. Bought it for work and need the headphones for videos etc. Maybe i'l try playing with the EQ a bit more and get it listenable.
Tinny audio is a known bug with all current versions of vegacomb. There is no fix for it yet.
Hopefully when the versions of vegacomb with the new kernel will fix this and the cameras force close problem when they are released.
just ordered a pair of these so has anyone used them on their s4,if so,any good?before i open them next week lol
tonybhoy said:
just ordered a pair of these so has anyone used them on their s4,if so,any good?before i open them next week lol
Click to expand...
Click to collapse
I have Jays One+ for a while and are great! Yesterday I have also bought SGS4, and I have to say - the sound is stunning! I'm using PowerAmp Pro and I had to adjust the sound just only a bit. Before that, with HTC Desire, it required more work to get the sound right for me.
Unfortunately, the Jays' App is useless - Android captures the long button press and can't be used to adjusting the volume. Nevertheless one, double and triple press work great! (at least on Desire, but AFAIK it is Android > 4 feature)
Another annoying think is the cord shape and sound it makes when you walk... this scratchy sound can be heard during music play. You need to set the cord, i.e. under the clothes, so it doesn't make noise.
I hope you'll like it anyway!
I've had them for a while. Awesome sound quality
Sent from my GT-I9505 using Tapatalk 4 Beta
I had the One for a while (not the +), fantastic sounding piece of kit. I got them while I had my Galaxy S with Voodoo Sound, and as I mostly listen to music with a lot of bass, these absolutely killed it, phenomenally deep and clear bass.
I might just get the One+ (the One died at the jack ).
Hey there,
I'm no audiophile - but this has been bugging me ever since I unboxed my Galaxy Gear and paired it with my Note 3.
I listen to music a lot on my phone using my bluetooth headphones. I noticed that whenever my Gear is connected, bluetooth audio quality suffers a lot - it feels like the bitrate is cut in half or something (shouldn't be necessary, I know BT 4.0 has much more bandwidth than SBC encoded music requires). Highs crackle and feel tinny, and the lows become shallow.
Is there a way to remedy this? I'd hate to have to disconnect my Gear everytime I want to listen to music, which is what I've been doing for the last eight and a half months. Custom ROMs don't help, and it doesn't seem to matter either whether my Gear runs Tizen or Android.
Thanks in advance, I'm psyched to try anything anyone has to offer.
-odd
PS. Even if you can't offer a solution, if you've noticed the same thing please reply to this thread so I know I'm not insane or anything. Thanks
oddbehreif said:
Hey there,
I'm no audiophile - but this has been bugging me ever since I unboxed my Galaxy Gear and paired it with my Note 3.
I listen to music a lot on my phone using my bluetooth headphones. I noticed that whenever my Gear is connected, bluetooth audio quality suffers a lot - it feels like the bitrate is cut in half or something (shouldn't be necessary, I know BT 4.0 has much more bandwidth than SBC encoded music requires). Highs crackle and feel tinny, and the lows become shallow.
Is there a way to remedy this? I'd hate to have to disconnect my Gear everytime I want to listen to music, which is what I've been doing for the last eight and a half months. Custom ROMs don't help, and it doesn't seem to matter either whether my Gear runs Tizen or Android.
Thanks in advance, I'm psyched to try anything anyone has to offer.
-odd
PS. Even if you can't offer a solution, if you've noticed the same thing please reply to this thread so I know I'm not insane or anything. Thanks
Click to expand...
Click to collapse
Same thing on my Xperia Z2.. Try Google bluedroid android Bluetooth stack..
shareonline said:
Same thing on my Xperia Z2.. Try Google bluedroid android Bluetooth stack..
Click to expand...
Click to collapse
Thanks for the suggestion.
CSR diagnostics revealed that bitpool was indeed dropped from 52 to 35 whenever Gear was connected, however this problem counts as solved because I actually managed to enable the hidden aptX support in my headphones, so low bitpool is no longer an issue.
In short: Stop using SBC and the problem will go away.
I don't know how you do that. I got the same issue with my gear and galaxy s5 paired with my sol republic track air. those headphone are supposed to use aptx but my music still suffer a lot when connected to Gear
Sent from my Galaxy S5
MaLiXs said:
I don't know how you do that. I got the same issue with my gear and galaxy s5 paired with my sol republic track air. those headphone are supposed to use aptx but my music still suffer a lot when connected to Gear
Sent from my Galaxy S5
Click to expand...
Click to collapse
Yes, same thing here. This really grinds my gear(s).
But seriously, I am quite angry about this.
rytymu said:
Yes, same thing here. This really grinds my gear(s).
But seriously, I am quite angry about this.
Click to expand...
Click to collapse
I got the gear as a gift and I didnt use it anymore ... my music is more important that a watch ....
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
cfn87 said:
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
Click to expand...
Click to collapse
I had a nightmare with my note 4 and it's bluetooth, it was awful.
I got a Note 5 and bluetooth was absolutely awful, I had to return it and got a new one and all is good. Very good bluetooth
Having bluetooth issues with my Note 5 and an my Chevy Equinox. The phone works perfectly with all my other bluetooth devices though. I think its the car but my wife's iPhone works perfectly with the car. Who knows.
I have a thread in the Troubleshooting sub-forum looking for help with my BT.
See here.
Any ideas would be greatly appreciated!
Also - OP - what carrier are you with?
I have a nexus 6 and thinking about getting a note 5 but I have never had any issues with Bluetooth on my nexus
About every 20 minutes mine chooses to disconnect from my bluetooth speaker.
I haven't had a single issue with BT yet in my car or with my speaker at home. I use both daily.
Bluetooth on this phone (A2DP streaming specifically) is fantastic. I have had problems with horrible sounding overly compressed bluetooth audio streaming in my car (old head unit, no Apt-x or anything supported) since Android switched bluetooth engines after version 4.1. All the nexus devices (I've had a few) apparently only support SBC streaming, so this leads to the horrible sounding audio with some receivers, I presume. I just returned a Nexus 6 because of this very issue. I couldn't tolerate it in the car, music sounded like garbage. This was an issue with the Note 4 when I bought it last year as well. I don't know what Samsung did on the Note 5, but BT audio sounds pretty damn good again. I'm so glad, because nobody seems to care about this issue so I had almost lost hope. Props to Samsung for improving it.
Thats great news! I was to the point of wanting to beat my Note 2 with a hammer after every bike ride with my Bluetooth headphones! - Every time I would turn my head they would cut out. I'm looking forward to trying with my new Note 5 on my ride tomorrow.