I wanted to start a thread where can have an on going discussion, research and ideas to fix the problems with A2DP Streaming on MTCD/E Units.
Im not even sure if ALL MTCD/E units have problems with this. Seems like its a small subset. but I'll describe the problem as a sort of clipping, fuzzy distortion that happens in the upper frequency. It seems to only happen at a particular frequency and that's it. Typically its really easy to hear the distortion if a piece of music has cymbals or something of the like. The distortion is only present when these frequencies are present, and otherwise a2dp sounds fine.
Thus far I haven't found a single solution to this, nor a root cause. I've gone as far as removing the MD-725 on my motherboard and getting a Comfast WU-725, as well as countless other things that dont help such as changing the BT Volume in factory settings, 7thfloor mod, etc.
From a technical perspective, it seems that A2DP on MTCD/E is a digital stream that is passed through USB but not sure where it goes to from there.. Where it is processed, I am not familiar with this.
There HAS to be a reason for this happening. Maybe its MCU related? Maybe its a bad high pass filter? I'd like to get to the bottom of it.
I was hoping some of the guys, in the know can help come up with a solution., such as Wadzio or 7thfloor or others. To those that have reverse engineered the MCU, is there anything A2DP related in there? Maybe the solution is patching something the MCU or fixing a hardware issue on the main board. There HAS to be something we can do to fix this issue.
This is also interesting for me, As I tottaly stop using A2DP because of this distortion.
Maybe is good idea to record this distortion and share it here and maybe some "compression" experts can find out, what can be the root cause.
Also minor issue is, that the player app itself is really poor to control (no track information in notification bar to provide to widgets,no albumart, no track position...)
wizzsb said:
This is also interesting for me, As I tottaly stop using A2DP because of this distortion.
Maybe is good idea to record this distortion and share it here and maybe some "compression" experts can find out, what can be the root cause.
Also minor issue is, that the player app itself is really poor to control (no track information in notification bar to provide to widgets,no albumart, no track position...)
Click to expand...
Click to collapse
If anyone is capable to edit it so that metadata information is shown, I am willing to donate to the project.
Looking forward to an answer to this as well.
Related
Ok, we have some smart people here at XDA-Developers so why has no one been able to come up with a hack for the low volume on many of these units? The SX-56 has really good volume in both the earpiece and the speakerphone but it seems all other HTC units do not!
When using the media player the volume on the speaker is adequate (not great); however the same speaker as a speakerphone can barely be heard unless one is in a quiet room. The earpiece volume is terrible in a noisy environment. If you compare this to almost any tiny phone it sucks to put it bluntly. Take my LG 4500, it is so loud that you have to turn it down (this is as it should be).
From what I have seen, changes in the ROM can effect the volume so this tells me that there has to be some value stored away in a .dll that limits the max volume. I have searched for a registry value but none seems to solve the problem. The same hardware used for Media player has to be used for everything else, i.e. amplifier and speaker for spearkerphone and just switched to earpiece when in normal phone mode. Thus the amplifier is capable.
Can someone identify the .dll used for audio? Is it different for the various models? Does one work better than another? Is there a hacked version that would work better than all of the others? Is it in the volume control .dll?
Anyone that can solve this problem will be a hero in my eyes and a true hacker in the best sense of the word. I have the new HP IPAQ HW6510 (also made by HTC) and it has some improvements in the version of Windows it has, such as the Bluetooth stack really seems to work well; however, since the unit supports Bluetooth 1.2 I'm not sure whether it would work with version 1.1 phones.
Thank you for any help you can provide. I searched the site first and found many other complaining but no solutions.
Doesn't anyone have a clue? Is there anyone that can explain the workings and which .dlls do what relative to audio? Surely there is some bright person that has been able to figure this out.
pda2k user here. NEVER had volume problems. lucky?
So there's a reported bug that I am experiencing that is at the least a pretty major inconvenience and at most a complete lack of core functionality...
Basically, when making a call with a wired headset, the other party's sound echoes back to them. It's been reported here: http://code.google.com/p/android/issues/detail?id=23482
The echoing is bad enough that it's useless to even try to make calls with the wired headset. And yes, I'm talking about the headset that came with the phone, as well as other third party headsets.
Does anyone know if this has been fixed in the yet to be pushed updates? Also, does anyone know how else to get Google to take notice of this bug? I'm no expert but I have been around android since the G1 and this has all the makings of a software bug, especially since reportedly unplugging and plugging back in the headset seems to be a somewhat successful workaround, leading me to believe that something is not triggered at the right time on the software end until you unplug and plug in the headset.
Anyone find a fix for this? I was reading some other forums about the echo being from over noise cancellation..
I have the same issue—no different from the rest of the (righteous?) whiners who commented in the URL you posted. ICS is RIDDLED with many annoying bugs—we can only hope the Google Android developers get their heads out of their a*ses and start rolling out bug fixes instead of focusing on Jelly Bean, which will likely be riddled with many annoying bugs as well.
Anybody found a fix for this? So annoying that I can't use my headset...
does anyone have a flasable zip of the stock music player before they made it quieter, thanks in advance
Shaun27 said:
does anyone have a flasable zip of the stock music player before they made it quieter, thanks in advance
Click to expand...
Click to collapse
It's not just the player that needs changing, it's a whole bunch of libraries that have been changed and are incompatible with future versions, the old system files and libraries needed to make xloud louder have already been packaged up and put into a zip but none of them have worked so far.
TL;DR
Tried to be done, didn't work
It's really interesting that they would lower the volume. I personally think that the only solution you might have (although I really don't know if this will work) would be to turn on the Hearing Aid option. I have to use that option because I actually wear hearing aids, and it does help. I don't know what it does though. The good news is that my hearing aids have an adapter that allows them to stream audio from the phone via A2DP or use it wired ! It helps me a lot because I can finally hear the music in a normal way and all. I would say though that if the hearing aid thing does not work then i'm at a loss for what to do. Perhaps someone has a solution?
beez1717 said:
It's really interesting that they would lower the volume. I personally think that the only solution you might have (although I really don't know if this will work) would be to turn on the Hearing Aid option. I have to use that option because I actually wear hearing aids, and it does help. I don't know what it does though. The good news is that my hearing aids have an adapter that allows them to stream audio from the phone via A2DP or use it wired ! It helps me a lot because I can finally hear the music in a normal way and all. I would say though that if the hearing aid thing does not work then i'm at a loss for what to do. Perhaps someone has a solution?
Click to expand...
Click to collapse
where is the hearing aid option ?
Hi.
I'm having a weird problem with the z1 compact and its sound enhancement features.
After a while of use, the sound enhancements stop working completely. Surround effects do absolutely nothing, eq and bass controls are equally ineffective. The sound is really flat. No amount of booting or trying different versions of apps helps, only factory reset temporarily resolves the issue. I haven't been able to isolate any specific app or app version to why this happens.
Used apps are stock walkman app and music unlimited (with subscription).
I made some adb logcat available should anyone want to take a closer look (at ta.iki.fi/xperia/z1c/)
The logs show music playing with walkman app and trying to adjust "clear bass" setting for both working and failing scenarios.
Anyone else experiencing this? What's causing it? How to remedy?
Thanks.
I've found that some headphones stop being recognised sometimes while plugged, not sure why. The buttons on the HTC E240s sometimes stop working, for instance. In all cases, unplugging and replugging the headphones fixed it.
What headphones are you using?
ghtop said:
I've found that some headphones stop being recognised sometimes while plugged, not sure why. The buttons on the HTC E240s sometimes stop working, for instance. In all cases, unplugging and replugging the headphones fixed it.
What headphones are you using?
Click to expand...
Click to collapse
Just regular old passive "button" type stereo headphones with normal 3,5mm stereo jack. No extra control buttons, nothing special.
There are known issues with the sound enhancements at the moment, they are non-functional in third party apps entirely! It's likely that the issue you are seeing is related.
I saw over at the Sony forum that they were aware of the issue and fix is anticipated in next update.
stevo_125 said:
There are known issues with the sound enhancements at the moment, they are non-functional in third party apps entirely! It's likely that the issue you are seeing is related.
I saw over at the Sony forum that they were aware of the issue and fix is anticipated in next update.
Click to expand...
Click to collapse
Thanks for the tip.
I tried your suggested solution, didn't help for me. There was something weird in the audio output during this so something did happen.
Original thread modified after i finally figured out what the problem was, original text can be found in the quote below this post.
Edit:
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Dinger558 said:
In the last 2 days for some reason Google Now keeps being randomly triggered. Sometimes for a whole minute without end.
When the device is locked I keep hearing that woman's voice of how I need to unlock the device to use Google Now.
it's getting incredibly annoying.
I tried killing it, it just restarts itself. In settings it's already set to "Off" and it still pops up. Uninstalling it just resets it to factory and solves nothing.
Please someone tell me how to get rid of the damn thing.
I'm having exactly this problem on my G3:
android.stackexchange.com/questions/62417/google-search-appears-out-of-nowhere
android.stackexchange.com/questions/66135/google-now-launches-when-headphones-are-plugged-in
Click to expand...
Click to collapse
If you're rooted install greenify and xposed. Greenify will tell you what is triggering Google now to start. And you need xposed for that added feature in greenify
Sent from my LG-D850 using XDA Premium 4 mobile app
3085
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Dinger558 said:
Ok so this is a very old annoying HARDWARE glitch.
...
Click to expand...
Click to collapse
First of all, thank you so much! Your trick helped
But are you sure that this is a Hardware Problem?... If I just need to plug my headphones in and out, doesnt that imply that this is more of a software issue?
Kalaidos said:
First of all, thank you so much! Your trick helped
But are you sure that this is a Hardware Problem?... If I just need to plug my headphones in and out, doesnt that imply that this is more of a software issue?
Click to expand...
Click to collapse
It could be a software but likely both at fault.
Android OS appears to mistake regular headphones for a headset, this does not happen consistently making a hardware aspect to this problem certain.
A very simple fix would be to include in a future android the option to disable headsets entirely or allow manual switching by tapping the icon.
But they probably wouldn't do that, after all, why care about a minority?
Wait is that what the little microphone icon is? I've had that a few times, was wondering what the heck it was.
Dinger558 said:
It could be a software but likely both at fault.
Android OS appears to mistake regular headphones for a headset...
Click to expand...
Click to collapse
I cant convince myself that this is a hardware issue, the G3 is a flagship and they just can't use faulty hardware that affects everyone
Kalaidos said:
I cant convince myself that this is a hardware issue, the G3 is a flagship and they just can't use faulty hardware that affects everyone
Click to expand...
Click to collapse
It's a very old issue. You can find mention of it in smartphones going back years.
I can't be sure but I think the headphone jack gets a faulty contact with a non-existent third contact point that only headsets use. Thereby convincing the OS that it's a headset and not headphones,
This doesn't appear to happen to all headphones.
Dinger558 said:
Ok so this is a very old annoying HARDWARE glitch.
For some reason android detects regular headphones as a special headset sometimes and this causes many annoying problems such as a nonexistant contact point causing random headset special functions to trigger. (skip music, open google voice, random volume changes, even make random calls)
Software solutions to this problem either don't work on latest Android versions or cause numerous problems and resource overhead.
Solution:
Keep plugging and unplugging headphones slowly, quickly, forcefully, etc etc until you see the headphones icon appear instead of a headset icon. Once this happens the problem is GONE until you unplug headphones and plug them back in again and don't get lucky.
It will presumably not happen with most headphones or else manufacturers would have been made to care by millions of pissed off customers. As it is they don't appear to give a damn to the plight of some of us.
Click to expand...
Click to collapse
My issue is a little different. Whenever I insert headphones (have tried 3 now). The only thing I've not yet tried was unrooting. I had Viper installed as well as Xposed and a few modules all of which I've since removed. All with no improvement. Anyone ever seen this or find a post I may have missed?
This is crazy, one day I just put my headphones that I always use in and they just worked, and every time I put them in they register as normal!