I have had the "other-person-hears-an-echo" on bluetooth a2dp in my truck since at least November. Running CM10. While it is mentioned periodically, most say the problem has been fixed on their handsets. It's driving me insane. The short version:
I think it was a perfect storm of a) CM10 bugs and, b) interface between the ville and the Clarion CZ500 in my truck. Note 1: My wife has the same audio in her car, and a stock HTC One S. No problems at all. Note 2: I always do clean flashes, wipe 3x, etc.
I am sure that whatever minor bugs in CM10 that influenced this have been fixed (NO complaints about CM10 - I've been using it since CM6 on my old MT3GS) - I can now talk to people without the echo on their end - IF...
I use a combination of tweaks to a) the Bluetooth volume on my phone, and b) the volume on my cz500. Where I place my phone (nearer or further away from the cz500 or the microphone) seems to effect things. So I'm getting closer, but...
I cant figure out a reliable pattern of tweaks to fix the problem. Some combinations work at one time, and then another some other time. The most reliable tweaks involve turning the volume on my cz500 so low that I can't hear the other party.
I've already traded the phone in (thanks TMO for an easy process and for taking a rooted phone). Before I buy another car stereo, does anyone have another idea?
Thanks very much in advance for anyone willing to take a minute here. If I've missed a post or discussion about it, it isn't for lack of trying - I've spent hours reading through the forums.
Related
Hi all.
Recently got myself my first smartphone, the Nexus S on Telus. (Well, had a Samsung Omnia before, but getting a WM6.1 phone in 2010 can hardly be considered smart )
Everything was going swimmingly. I have a penchant for changing up the software innards on the devices I own, so naturally I rooted my shiny new phone and had a good time trying out all these ROMS. This was approximately a month ago.
About a week ago my phone inexplicably began to act up. My in-call volume dropped to barely a whisper, and my touch-sensitive search button would for some reason go off on it's on.
After a bit of Googling, I found out that the search button issue is affecting many other Canadian users also, something about a bug in the new radio (AUCKD1).
But I've yet to find anything conclusive about the in-call volume. There are threads who are complaining of either low or high volumes, but no workable solutions.
So as a last resort I have restored my phone to fully stock 2.3.4. One to see if it was my messing around that caused it, and to also prepare for the possibility of having to return my shiny. It may just be my imagination/denial, but the call volume seems slightly better. Not good enough for me to hear outside, but inside, with no background noise it's just slightly quieter than normal.
Another thing that is very odd. Skype volume is much louder than voice calls. To be frank it's still not loud enough to be considered acceptable, but it is definitely louder. They use the same speakers right? Why would that be?
If at all possible I'd like to avoid having to take the phone back since Telus will no doubt charge me exuberant fees for having touched the phone for more than 3 seconds and moving more than 18 millimeters away from the store I bought it from.
Please advise, XDA!
U can try install kernel voodoo sound from supercurio and apps. U can see the different.
I had try most of the custom rom. There is one rom who give me loudest call volume, but I can't remember which ROM it is. U should explore more rather than bring it to the store.
Now I'm on liquidnexusbread, but not giving me a good volume in call.
I knew it sucks... but I love this rom performance.
Sent from my Nexus S I9020T
Hey guys,
I've just got droid charge last week and I like everything about it (only after rooting and installing Gummycharged), but there is one huge problem for me. Well, it might be 2, but one of them is slightly better with Gummycharged and voodoo lagfix.
Here's the issue - I love listening to music in my car through bluetooth and until recently I've been using my Ipod touch 4g and it has been working flawlessly and music quality was great. Now, once I got the Droid Charge, I've noticed 2 things - every minute or 2 the songs would skip (interrupt), and the sound quality was pretty terrible (mainly with the high end - sounded like tweeters were being overloaded).
Rooting the phone helped with skipping - it now happens once in 10 minutes or so, so that's acceptable, however the sound quality is still pretty horrible. I've looked around on these forums and people had similar issues with quality with their stock phones and most people suggest CyanogenMod. I'm not all that familiar with what different ROMs are available for Charge, but as far as I can tell this one isn't. Does anyone know if there is way to fix/configure the quality of bluetooth transmission on this phone? Is there any mod I can install? Anyone having similar issues?
Any help is much appreciated!
FuriousOne said:
Hey guys,
I've just got droid charge last week and I like everything about it (only after rooting and installing Gummycharged), but there is one huge problem for me. Well, it might be 2, but one of them is slightly better with Gummycharged and voodoo lagfix.
Here's the issue - I love listening to music in my car through bluetooth and until recently I've been using my Ipod touch 4g and it has been working flawlessly and music quality was great. Now, once I got the Droid Charge, I've noticed 2 things - every minute or 2 the songs would skip (interrupt), and the sound quality was pretty terrible (mainly with the high end - sounded like tweeters were being overloaded).
Rooting the phone helped with skipping - it now happens once in 10 minutes or so, so that's acceptable, however the sound quality is still pretty horrible. I've looked around on these forums and people had similar issues with quality with their stock phones and most people suggest CyanogenMod. I'm not all that familiar with what different ROMs are available for Charge, but as far as I can tell this one isn't. Does anyone know if there is way to fix/configure the quality of bluetooth transmission on this phone? Is there any mod I can install? Anyone having similar issues?
Any help is much appreciated!
Click to expand...
Click to collapse
Have you looked at this thread? It's more about disconnections, but the fix they list might help you, too.
http://forum.xda-developers.com/showthread.php?t=1099603
chadness said:
Have you looked at this thread? It's more about disconnections, but the fix they list might help you, too.
http://forum.xda-developers.com/showthread.php?t=1099603
Click to expand...
Click to collapse
Thanks, but the problem is more fundamental, I suppose. Looks like HTC and Samsung use some custom bluetooth code in their ROMs. Apparently it limits the bitpool value at 32, which makes the audio quality terrible over bluetooth. Surprisingly, everyone knows what the problem is but so far the only reported solution is the cyanogenmod.
Here's more about it:
http://forum.xda-developers.com/showthread.php?t=708685
http://code.google.com/p/android/issues/detail?id=9888
Wow, nasty and long standing! Glad I didn't buy one of those headsets like I was going to. *sigh*
Hey guys,
I'm running GummyCharged 1.85 w/ the voodoo kernel (pbj) and also getting skips over bluetooth to my car stereo. It's seriously distracting and annoying. My Droid 2 worked flawlessly in this respect, but it seems like any time the Charge does any "thinking" it makes the BT audio skip.
Any hope of a fix for this?
My Charge is stock and I haven't had a chance to try the bluetooth audio streaming yet, but when I plug my phone into my car to listen to music through the aux jack it does the same thing, about once every song it skips. Seems odd. I'll try bluetooth today on my way to school and see what happens. You'd think with Bluetooth 3.0 on board the signal would be strong enough to stream decent quality music...
I can confirm this issue is there and in your face a lot. I tried it on the way to school (about a 40 minute ride), it skipped once or twice every few minutes, no big deal. The quality was acceptable for wireless transfer, nothing to write home about. Not a lot of low end, and just a hint of static and slightly over-boosted highs. However I tried it again on the way home once I realized I had forgotten my aux cable, and it skipped so often I just switched to FM. It was so annoying. I can confirm your suspicions that it seems to happen when the phone is trying to do something. Switching towers, background apps, turning on data and checking traffic with Google Maps really freaked it out, but it was fine once I was done. Kinda sucks for those who wish to use the feature regularly.
Update?
I have a droid charge, and the bluetooth streaming quality really sucks, like the OP pointed out, highs are really bad.
Tried with my friends iphone and it worked flawlessly.
CyanogenMod is still unavailable for the droid charge as far as I can tell.
Is there any other fix that anyone has found that will fix the bluetooth sound quality when streaming music?
Any help or places to look is appreciated.
[RESOLVED] Hardware issue, please see this post for repair instructions: http://forum.xda-developers.com/showthread.php?p=29615619#post29615619
Setup: Hellfire ICS v1.9, and flashed the newest Harsh non-OC kernel on record as of yesterday. Baseband is 21y, RIL matches BB (it's built into Hellfire ICS). Used GetRIL to verify.
Problem: All is perfect except for in-call audio (keep reading....), but takes a bit to surface. 5-10 minutes into a call the audio clicks and drops but comes back, missing a few words of conversation. This may happen 1-5 times a minute. Then it will eventually cut the audio and not come back but leave the call in progress. If I call the person back, the process happens but much quicker next time, within the first minute of the call.
I'm hoping someone would be willing to try the same setup on their G2x to see if this is just a gremlin in my phone, or if the Harsh kernel is doing something odd with Hellfire ICS. I've looked over several of the baseband issue chains we have here but I'm not finding any additional gems that can explain why this is still happening with the matching BB/RIL. (Hoping I missed something simple) I may just have to abandon this mix of ROM-kernel.
If anyone knows how to read the logcat files to figure this out as well it would be nice (there is alot of junk in them on these ICS builds). I was thinking of making a call with it connected to ADB. But it would be nice to see if another user has the same issue on this config.
Major step forward after last night. Logs said the phone was flipping into headset made and enabling the headset jack. I know this may seem odd but I have never used my headphones on my phone in the last 7 months I have owned it so headset mode never crossed my mind. Which leaves me with the final problem.
Why the heck is my device stuck in headset mode after never before using it? I have tried blowing the jack out, and inserting a pair of headphones into the jack about 50 times now. I can only hear audio with the headphones plugged in. Crazy thing, the Hellfire boot sound works, just no sound after the ROM is loaded.
Off to do more searching/research...please let me know if anyone has any ideas.
I want to take a minute and share a bluetooth issue I've had with my Galaxy S6. Maybe others have observed the same thing, and while I'm not specifically looking for a solution, suggestions are welcome. The S6 is about 3 months old, Andriod 5.0.2, unrooted, and other than Apex launcher pretty vanilla.
For the record, with the exception of the issue I'm about to describe, this phone has been phenomenal.
I use the phone in my car over bluetooth to and from work every day. For the first two months this worked great, no problems at all with podcast addict or poweramp. Then, I noticed the audio would dip momentarily. As if someone turned the volume down and back up. The bluetooth connection never gets lost, just the audio dip. Then, eventually the problem became perpetual. I will describe the symptom the best I can, as if the volume were being turned up and down. This wasn't the case, more like the bluetooth stream was somehow going away and coming back.
I tried all the obvious things, like re-pair the phone to the car, clear the bluetooth cache, Volume Up + Home + Power button and then "wipe cache partition". As a last resort I did a factory reset. This last step actually solved the issue, for a while. This was a few days ago, but this morning I noticed the same periodic blips in the sound, so I suspect over time the same problem will once again return.
<rant>
I was in touch with Samsungs customer support, who is supposed to "values you as a customer and want to insure that we have provided you with the answer you were looking for". Unfortunately, the blunt truth was they ended up being useless with an offer to allow me to send my 2 month old phone to them and wait for an undisclosed time, for what might end up being a refurbed replacement.
</rant>
Since I don't see mention of this in the forums, maybe it's not a wide spread problem. Maybe a compatibility problem between these two specific chipsets? Whatever the issue, hopefully some future update comes out that fixes things. Defaulting the phone every few months would be a considerable drag.
Has anyone experienced issues with Bluetooth devices? I have 2 devices (that are somewhat obscure) that I'm having problems with. First, what does work:
1) Beats Wireless Headphones
2) Bluetooth in my car
3) Unify Roverbeats (For bluetooth via A/V receiver that doesn't have it built-in.
4) Fitbit Surge (Had a little trouble getting it paired initially, but it's been fine since.)
The two items I'm having the trouble with are:
1) Omron 7 Series Wrist (BP654) Blood pressure cuff.
2) Vicks SmartTemp Bluetooth thermometer.
I have gotten both to pair, though it seems to be hit and miss. Once I need to actually use them, though, I'm having little to no success in getting the phone to see them. Unfortunately, I have to take both my BP and Temp every 3 hours (due to recently diagnosed, extremely rare immune system disorder.) This would be a deal-break for me, with the Blu Pure XL, it I didn't have 2 other android tablets I can use. However, I'd sure like to have these working on the phone! (BTW, they all worked seamlessly on my LG G4.)
Has anyone else experienced bluetooth issues with the Pure XL?
More Bluetooth problems....
The Bluetooth problems I mentioned earlier have only worsened. My car sometimes will, sometimes won't connect. The surge connects 90% of the time. Everything else is touch and go, with my BP Cuff only connecting once (during the pairing sequence.) Also, when selecting "un-pair" on any device already paired almost never un-pairs it. I usually have to reboot, then try again to actually get it to un-pair.
Aside from the Bluetooth issues, I've not really encountered anything else that is a show-stopper. I'd like to have Android pay, but it's not a necessity. I want root more (which disables Android pay anyway.)
DannyHammons said:
Has anyone experienced issues with Bluetooth devices? I have 2 devices (that are somewhat obscure) that I'm having problems with. First, what does work:
1) Beats Wireless Headphones
2) Bluetooth in my car
3) Unify Roverbeats (For bluetooth via A/V receiver that doesn't have it built-in.
4) Fitbit Surge (Had a little trouble getting it paired initially, but it's been fine since.)
The two items I'm having the trouble with are:
1) Omron 7 Series Wrist (BP654) Blood pressure cuff.
2) Vicks SmartTemp Bluetooth thermometer.
I have gotten both to pair, though it seems to be hit and miss. Once I need to actually use them, though, I'm having little to no success in getting the phone to see them. Unfortunately, I have to take both my BP and Temp every 3 hours (due to recently diagnosed, extremely rare immune system disorder.) This would be a deal-break for me, with the Blu Pure XL, it I didn't have 2 other android tablets I can use. However, I'd sure like to have these working on the phone! (BTW, they all worked seamlessly on my LG G4.)
Has anyone else experienced bluetooth issues with the Pure XL?
Click to expand...
Click to collapse
I've only paired a Metawatch so far but no issues. I keep forgetting to sync it to my car. I'd say the connection with the XL is better than with my M9, which dropped/reconnected randomly.
So far it seems to work fine with my car but when I use it with moto x sol deck it starts breaking up after 15-20 minutes. The only way to fix it is to turn on and off bluetooth.
Pure XL bluetooth serious problem
I have a Pure XL also, originally i only had problems occasionally with playing media through my LG Tone+ headphones. then i also tried connecting my Fitbit Charge HR it would shut down the bluetooth and lock the bluetooth off. i tried uninstalling the fitbit app and only running the headphones and the bluetooth ended up locking up. when i go to the bluetooth settings it shows it as constantly turning off and turning on. i cant stop it. tried rebooting. and also tried turning off and leaving off for awhile and still when i turn it back on it is still locked up.
Issues with jawbone up3, screwed up bad
Also having issues maintaining a sync without a reboot. In my wild attempts to fix this issue I ended up uninstalling Bluetooth Share.... Would any of you fine gentlemen be kind enough to post a copy of the apk from /system/bluetooth for me?
edit: found it github*com/acheron1502/android_vendor_BLU_BLU_PURE_XL/tree/master/proprietary/system/app/Bluetooth
thanks to acheron1502!
I only use Bluetooth for me FM transmitter in my car.... I never seem to have any problems at all as far as connection and playing music/sounds.... But the hands-free doesn't seem to work.... I can hear them but they can't really hear me very well.... I just put it off to the mic on the FM transmitter....
Just got my blu pure xl today and Bluetooth sucks, its not much better than my blu vivo air. Signal cuts off only being like 5 feet from the phone using my brand new jbl reflect mini Bluetooth earbuds. Hooked to my 4 year old kindle fire hd left on my second floor I was still getting reception in my basement. I'm so pissed I thought that this specked out phone would have good Bluetooth reception but nope ****ty. Blu/gionee needs to start putting way better Bluetooth transmitters in there phones.
I've got to reboot my phone several times a day to keep synced with my runtastic orbit. definitely the phone, had no issues with my LG. Its a nuisance, not a major issue.
Bluetooth woes followed by total meltdown!
After all of my initial issues with Bluetooth on my pure XL, I put a Samsung 200 GB MicroSD card in. It worked for a while, but I think I somehow damaged the card moving it in and out of the phone. Finally, I left the phone charging with card inserted. After an hour or two I came back to get it and it was fire hot...so hot that the plastic back cover had started to melt right below the memory card slot. After it cooled down I removed the SD card. The went on to work half the time, but eventually completely died. I contacted BLU and they sent me an RMA, so I sent the phone to them. I figured they would come back and say the phone was not covered anymore because I had the TWRP recovery and root installed. However, after they received the phone, I got an email with tracking number on the return to me. They ended up sending a completely new phone (off the shelf with all the goodies included.)
Since the new one has been back, and I got the march update, I haven't had any Bluetooth issues save 1: it won't connect to my Denon AVR receiver's Bluetooth mode. Everything else that I listed at the start of the thread is all working correctly now. Every once in a while I have to do a reboot to reset it, but it's way better than it had been!
BLUETOOTH CLICKING NOISE (handsfree)
Is anyone having issues with when using their BLU Pure XL in the car when using handsfree? I have an issue when about 1 minute into the phone call, the person I am talking to hears a loud click every 2 seconds and will not stop until I turn off the bluetooth or put on speaker. If i switch back to bluetooth, same thing happens. The longest I've gone on a call is probably 4 minutes before it started to happen. If i hang up and call the person back on bluetooth, same thing happens.
Anyone has a solution with this as its so bad that I am considering buying a new phone because of this issue!
Thanks