Related
I've used many ROMs (Viper, Bonsai, Nebula, currently ACS Syndicate) and I've had this problem on all of them. I've even ODIN'd back to stock before and it still didn't fix my problem.
After disconnecting my Epic from my Jawbone Icon headset, the sound often gets stuck inside the earpiece. Music, movies, games, ringtones will all play from the earpiece instead of the speaker behind the phone.
Is there some software fix to correct this? Can any of the devs point me in the right direction as to how I might troubleshoot this (maybe at the kernel level)?
Thanks in advance!
This doesn't really go in Development, and I suspect it will be moved soon.
I can tell you, though, that I've experienced similar problems, intermittantly, and here's what I've observed.
If I'm listening to music through bluetooth, before I disconnect, I'll stop the music. Then I'll turn the bluetooth device off. Then I'll turn bluetooth off on the phone. If I do it in that order, I don't seem to get the bug.
If you do still get the bug, rebooting fixes it.
Hope that helps!
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
This is a known issue. It's a bug that has to do with being connected to a device for both media and phone calls. If you use only one or the other it doesn't happen.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
daddymikey1975 said:
It's very annoying for me as well.
The other bug that I noticed is after taking a call over BT, when I end the call, the earpiece on the phone starts randomly popping. rebooting fixes it but it still really irks me.
I think the OP is wondering if there's a way to dig around in the BT stack and fix it ?
Click to expand...
Click to collapse
This stuff has been going on since DK28 and before. I believe Rodderick was looking into fixing it from the kernel side, but I'm not sure how much progress has been made. I know it's not as bad as it was on DK28, but still very annoying. It used to happen to me all the time (audio going through earpiece instead of speaker after disconnecting Bluetooth) when I would turn my car off and it would disconnect the Bluetooth to my car stereo. Now that I have the Samsung Car Dock, I just connect Bluetooth for phone only, and use the audio out on the Car Dock for Navigation and Media.
Moved to Q&A.
i am having a simular issue but mine is that when i connect to bluetooth headset i have to have media playing before i get a call or i will not hear the other person in the call.
it seems to me that ANY bluetooth headset with A2DP is doing this and i have tried 3 diffrent headsets. Jabra Stone, Jawbone Icon, and the Blueant T1.
all 3 of these headsets do this. does anyone have any solution yet?
Even if there isn't a fix, I wish there was an app to reset the sound settings post facto. Anyone know of one?
I just want to add my name to the list of those who are affected by this. Glad it's not just me, though. Hopefully it can be debugged easily.
For the record, a Quickboot Hot Reboot (reboot of Android only, not phone) does NOT solve the issue. Only a full reboot works for me. Seems like it may not be a software issue but something hardware-related.
Sent from my SPH-D700 using Tapatalk
Just want to add this happened to me the first time just now. I'm on rooted EC05. I was scared for a bit that the speaker had blown. Then when I discovered it all coming from the earpiece, I remembered this thread. A reboot did make it go away.
I wonder if it has any relation to the issue I see once in a while since the upgrade where my BT devices need re-pairing and ask for a passcode, when they really shouldn't.
I Also Have This Issue
I have had this exact issue since DI18.
After I hang up a Bluetooth call, I have popping sounds coming out of the earpiece. Turning off Bluetooth doesn't fix it. Turning Bluetooth back on after turning off doesn't fix it. In addition, after this happens, all devices sounds (phone ranging, notifications) all come through the earpiece and *not* the main speaker.
I've had all of the stock ROMs up until EC05 loaded on this Epic and have had the same issue throughout. I am now running midNIGHT ROM, which has cured most problems I’ve had with my device, except this issue.
I was just poking around trying to find some sort of tool or the name of the service(s) that I need to restart to fix this issue.
Same issue for me. Quite annoying as I listen to audible over bluetooth quite a bit, and then pretty much know I have to reboot when I turn bluetooth off.
SRF users have reported Bluetooth issues being cleared vs. stock builds. I can't say exactly why, but it does seem to work.
What are SRF users?
Nope...
Syndicate Rom Frozen...
Well, I'm on SRF 1.1.1 and I've got the same incredebly annoying audio issue.
Please, someone, come up with a fix!
There are a number of problems with bluetooth on the Galaxy Nexus. Some may be Galaxy Nexus specific, some may be Ice Cream Sandwich specific, I am not sure... Bluetooth performance has been very inconsistent since the launch of Android. (Well, actually it worked perfect in the early days of the G1, but more recent updates seem to make Bluetooth performance more inconsistent.) I would really like to see Google focus on fixing these Bluetooth issues, and I do not know of any way other than starring these issues on code.google.com to bring this to their attention. I have personally experienced the following issues:
1. Rogue phone call upon bluetooth headset connect. This one is very annoying: sometimes the phone will dial the last-called number when a bluetooth headset is connected. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=26004
2. Galaxy Nexus Bluetooth and BT-button become sometimes unresponsive, BT button blackend out (dark gray), needs restart to fix. If you have ever experienced this, you know what I am talking about: sometimes you have to reboot the phone to get it to connect to a bluetooth headset or car. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=24522
3. Apps other than "Music" not receiving Bluetooth Play/Pause commands after 4.0 update. I think this is the cause of apps such as Pandora not auto-pausing upon bluetooth disconnect. Please star this issue if you'd like it to get fixed: http://code.google.com/p/android/issues/detail?id=23172
These issues have a very low number of stars, and do not have an owner assigned to them yet. Please help improve bluetooth performance by voting for these issues. Thanks!
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Number 3 is app specific. Those other apps need updates.
I had an issue similar to number 2 when my Nexus was on stock. On custom ROMS, my bluetooth works fine. Are you still on stock?
Sent from my cm_tenderloin using Tapatalk
bekyndnunwind said:
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Click to expand...
Click to collapse
I am on stock 4.0.2 (rooted) on a GSM yakju. I've been waiting for a more feature-complete CM9 before switching ROMS, but if you say AOKP doesn't have these issues then I might just switch to AOKP and try it out in the next day or two!
Updated: Problem persists after installing ROM AOKP M4.
adrynalyne said:
Number 3 is app specific. Those other apps need updates.
Click to expand...
Click to collapse
Ahh - good to know, though it is weird that Pandora v 1.5.12 still auto-pauses on bluetooth disconnect.
Bluetooth
I haven't had any issues with my Jawbone bluetooth. I do noticed that different bluetooths work differently with different phones which a big history and swapping different phones and bluetooth headsets. I would try a different bluetooth.
mralexsays said:
Ahh - good to know, though it is weird that Pandora v 1.5.12 still auto-pauses on bluetooth disconnect.
Click to expand...
Click to collapse
I could be wrong.
mralexsays said:
There are a number of problems with bluetooth on the Galaxy Nexus. Some may be Galaxy Nexus specific, some may be Ice Cream Sandwich specific, I am not sure... Bluetooth performance has been very inconsistent since the launch of Android. (Well, actually it worked perfect in the early days of the G1, but more recent updates seem to make Bluetooth performance more inconsistent.) I would really like to see Google focus on fixing these Bluetooth issues, and I do not know of any way other than starring these issues on code.google.com to bring this to their attention. I have personally experienced the following issues:
2. Galaxy Nexus Bluetooth and BT-button become sometimes unresponsive, BT button blackend out (dark gray), needs restart to fix. If you have ever experienced this, you know what I am talking about: sometimes you have to reboot the phone to get it to connect to a bluetooth headset or car.
Click to expand...
Click to collapse
I get #2. Usually it occurs with turning bluetooth on and off multiple times over a period of days or coming out of Airplane mode. I have got around it by leaving bluetooth on all the time. I found that BT does not actually use a much battery.
bekyndnunwind said:
Strange...I'm on AOKP and I don't see any of these issues...
Are you on 4.0.3?
Click to expand...
Click to collapse
I just flashed AOKP, so I should know within a few days if 4.0.3 really solves these issues for me. Thanks!
mralexsays said:
I just flashed AOKP, so I should know within a few days if 4.0.3 really solves these issues for me. Thanks!
Click to expand...
Click to collapse
Whatever is causing these bluetooth issues for me wasn't solved by switching to the AOKP 4.0.3 ROM. Got in my car this morning and bluetooth would not connect - had to reboot my GN. Upon reboot, bluetooth connected and dialed the most recently dialed number. I can't imagine that an app would be causing this, but I'm going to try stripping down my installed apps to the bare minimum and see if that helps. My car bluetooth is a Motorola T605 that worked flawlessly from the original launch of the G1 up until sometime around the Gingerbread releases started coming out, so I don't think it's an issue with the T605 bluetooth unit. I'll keep this ticket updated as I learn more about the issue.
mralexsays said:
Whatever is causing these bluetooth issues for me wasn't solved by switching to the AOKP 4.0.3 ROM. Got in my car this morning and bluetooth would not connect - had to reboot my GN. Upon reboot, bluetooth connected and dialed the most recently dialed number. I can't imagine that an app would be causing this, but I'm going to try stripping down my installed apps to the bare minimum and see if that helps. My car bluetooth is a Motorola T605 that worked flawlessly from the original launch of the G1 up until sometime around the Gingerbread releases started coming out, so I don't think it's an issue with the T605 bluetooth unit. I'll keep this ticket updated as I learn more about the issue.
Click to expand...
Click to collapse
AOKP M4 + Parrot MKI 9200 2.0.2 working fine here.
Checked for firmware updates to the T605?
Sent from my Galaxy Nexus using Tapatalk
No issues here with stock 4.0.1 yakjuux when pairing with Jawbone ERA bluetooth headset. I've seen other posts about issues with pairing with car software tho
daern said:
AOKP M4 + Parrot MKI 9200 2.0.2 working fine here.
Checked for firmware updates to the T605?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I searched, but there is no update for the T605 - I doubt Motorola will ever release one either since the T605 is a very basic bluetooth device - only supports phone and A2DP media - pretty standard.
Would certainly appreciate support for avrcp 1.3/1.4 - my Parrot looks a little sad when doing A2DP as it just displays a little scrolly thing on the display - would be mucho cooler if it displayed track name / artist.
Would be /awesome/ if I could browse the device's media from the Parrot...
One of the apps I uninstalled was the Google "Car Home" app - I suspect that Car Home is what was causing both the "unable to turn on bluetooth" and the "bluetooth dials the most recently dialed number upon connect sometimes" issue. Not 100% sure yet, but seems plausible since Car Home ties in to bluetooth as a system app and I haven't had the issue since uninstalling Car Home. It'll take a few more trouble-free days for me to be sure though... Does anyone who use the Google Car Home app (which must be installed as a system app) NOT have this issue?
It's definitely a hardware or driver problem and does not come from an app. I have this issue since day 1 on my Nexus and I have experienced it on all ROM's I have tried or baked until now. I hope Google or Samsung will do something with our complains.
Planet X said:
It's definitely a hardware or driver problem and does not come from an app. I have this issue since day 1 on my Nexus and I have experienced it on all ROM's I have tried or baked until now. I hope Google or Samsung will do something with our complains.
Click to expand...
Click to collapse
I wonder why some people never see this issue while we do. Is there any other way to draw attention to the bluetooth issues besides starring these defects at code.google.com? Before I made this XDA posts, there were 42 stars for what I consider to be the most important defect (Issue ID 24522 - "Galaxy Nexus Bluetooth and BT-button become somtimes unresponsive, BT button blackend out (dark gray), needs restart to fix"), but as of today, there are still only 49 stars for that issue. That means that only a small fraction of us experience this issue or that not many people care about it.
Although I'm not having any of the problems you describe, I have always found BT on Android to be incredibly unreliable. But then, I have always believed that BT is an absolute joke, the best example of a failed standard in the history of the universe.
The problems I have had consistently with my G1, N1, and now GN:
- Paired headset simply won't connect. Have to reboot to fix. Doesn't happen too often.
- Headset connects, but only media or phone audio, not both. For me this is the most common and happens a LOT. Multiple power cycles on the headset will sometimes fix, but sometimes have to reboot phone.
- Headset connects and will control the phone and music player, but no audio. This happens with some regularity. Have to reboot phone.
Same problems with three brands of headset: Jawbone original, Plantronics Voyager 510, and currently the Moto S305.
I haven't searched the db to see if these bugs are reported. I just quietly despise BT and Google's failure to implement it better.
I don't have these problems with my iPod or iPad, so fully believe it's Google's poor implementation of a poor standard.
More power to you getting the issues addressed, but I think that since BT, which is truly a joke, and yet has been accepted and is widely used by the general public, they are not going to care. Google sets their pain threshold for system failures and bugs fairly high and does not trouble themselves at all with issues that don't rise to that level. For example, here in Puerto Rico where I live, Network Location Services stopped working on TMO a year ago and Google has not fixed it yet despite several solid reports. Until they receive a cacophony, they don't care, and they won't receive a cacophony on something like NLS, because the general public has no clue that it even exists, even though it impacts their daily experience with location aware apps. It's quite frustrating.
GR
GR,
I agree that bluetooth has its share of shortcomings, but basic phone and a2dp audio is something that has been around a long time and really should "just work." I like bluetooth in the fact that I can choose to keep my phone in my pocket and just hop in the car and it's connected for phone and media. A built-in service such as bluetooth should never get stuck in this unusable state that requires a reboot to get it working again. (Especially in the car - that really sucks...) I like the fact that Google is constantly adding new cutting edge features like NFC, but it seems that this comes at the cost of overall stability for some of the basics like bluetooth.
Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
chadillac3 said:
Ok, I've read of 1-2 other people who've had this same issue. Tried contacting them with no results.
Issue: When on a BT call in my car, the person on the other line hears themselves speaking...i.e. echo. If I mute the microphone on my phone, it goes away...but obviously they can't hear me.
ROMs tried: Calk's v1.4 and AOKP Milestone 5. Flashed both twice; tried method of going to ODIN and loading stock EL29, rooting, adding CWM, then going to CM7.2 as well as the stock to EL26 and then flashing. Cleared data/cache/delvik cache multiple times.
Went back to EL29 stock and works great.
Any ideas of what I could do to fix? Really liked AOKP.
Click to expand...
Click to collapse
My girlfriend complained about the same issue with my phone, and my "fix" was to lower the BT volume on the device, and max out the volume in the car, and she said the echo was gone.
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Ok, going to ask what's most likely a stupid conceptual question:
For both my Calk's ICS 1.4 and the AOKP Milestone 5 installs I followed qbking's video's to the letter.
Now, to the best of my understanding, this ROMs come packed with a kernel such as FD26. However, you can load different kernel's such as the new FE07 which could very well affect my BT and potentially fix it (or not...)
So, to flash a new kernel, I'd have to use ODIN to install the EL26+CWM to get back to a GB recovery. From there I flash the new kernel, then reflash the ICS ROM.
Here's what I don't get...if the ROM comes packed with say the FD26 kernel, won't that overwrite the FE07 (or whatever) kernel I just flashed? What am I missing here?
Thanks!!! Really trying to see if my BT issue is something I can fix. Want AOKP back again, bad!!
chadillac3 said:
If I did that I'd go deaf with the hang up beep in my car.
Glad to hear it's a little more widespread than I thought. Hopefully this gets fixed with newer releases of ICS.
Click to expand...
Click to collapse
Lol...it won't be so loud, at least, not for me it isn't.
I'm an over the road truck driver and the only time I experience this is if I, or the person I'm talking to is in a really poor service area, i.e. South Carolina anywhere on I-95. Other than that I never have echo, & I'm on the phone for hours & hundreds of miles at a time spanning multiple states.
So it's not a ROM problem, kernel or modem related maybe, but I'm usually running the latest modem & kernel & have been on Team Nocturnal's ICS Blend "The Goodness" since about version 1.5, we're on version 8.0 right now. That would lead me to believe it's also not kernel or modem related
Fwiw, I use a Blue Parrot BT250-XT+, or Planatronics BB903, or a Blue Parrot VXi2 Expressway.
Sent from my E4GT packed full of "The Goodness" of TNz Blend ICS on Tapatalk 2 Pro
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
I have not noticed this with any ics leak and my car built in bluetooth. My only complaint about bluetooth is that the volume is too low when streaming audio.
I know of three people from my searching who did...one person said they went to the latest version of CM9 and that fixed it...going to try this weekend.
chadillac3 said:
So you're not using a vehicle's BT system but rather an earpiece?
The earpiece would not be an issue as the issue is the microphone on the phone is still on. So, over a car's stereo system it's plenty loud enough to feed into the phone. In a BT earpiece there wouldn't be enough volume to cause a problem.
Click to expand...
Click to collapse
I was using a vehicle one, that I installed myself.
http://www.crutchfield.com/p_113BT300/Kenwood-KCA-BT300.html paired with http://www.crutchfield.com/p_113DDX512/Kenwood-DDX512.html?search=ddx512&tp=20217
I reduced the echo by lowering the BT volume during the call on the handset, and raising the volume on the car receiver.
I know, I know the thread title is BT echo with ICS ROMs...I am not running ICS, but for what it's worth, same issue here often, though NOT every call... I am running completely stock (still GB 2.3.6). Phone BT is paired with Motorola T215 that's clipped to the visor in my truck. ...and for me also, turning down the volume down a notch or two helps...In my case, I was actually thinking it is a feedback issue, where the other person hears their voice picked back up through the mic...that's why turning down the mic helps (or why they don't hear it when the mic is on mute)...
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
Really? That's weird. In my car, adjusting the handset volume affects the system volume coming out of the speakers.
chadillac3 said:
That would probably help, but what's weird is that adjusting the handset volume doesn't seem to affect my BT volume...at all.
I've always assumed it had to do with the BT module on the car.
Click to expand...
Click to collapse
When I press the volume on the BT module, the phone will display "Bluetooth In-Call Volume" and adjust accordingly. Conversely, the phone will display the same when pressing the volume on the phone during a call. It could be relative to your BT module - if I understand correctly the BT module needs the Audio/Video Remote Control Profile (AVRCP) - as what allows for volume control via BT (as well as the play,pause,etc. on music over BT). Does your device support it?
I also found that if I slightly lower the visor, the sound doesn't "bounce" off the roof of the truck and helps not create echo as often, so I can turn the BT module volume up higher, if need be.
Just an FYI - when I used to plug a line from the headphone out from my HTC Hero to the truck stereo aux in , I would use the truck's speakers and the phone's mic...but there would definitely be echo issues if I cranked up the volume on the stereo...which of course let me to believe the similar issue occurs with my BT device and the phone itself because the mic is close to the speakers on the BT device.
Yep, module is AVRCP 1.3 compatible...which is part of the reason I like AOKP. Bitpool on the BT is set much higher than stock, and the metadata is transferred correctly. Everything is wonderful except for the damn echo.
What's weird is stock works totally fine; AOKP M5 had the echo, and Calk's 1.4 had an echo and static per my parents on their ground line and their ET4Gs. Wife's iPhone didn't seem to have the issue, so I wonder if it had processing built in to cut out the echo.
Going to try the latest versions of the ROMs to see if it magically fixes it.
Ever since ICS came along I have been experiencing linking issue with my car's Bluetooth.
While it can detect the phone, problem is every time it's connected as a media speaker device only. To remedy that, I have to manually go into the phone settings and enable the phone calls too... Every single time.
Is anyone else experiencing this problem?
Bumpers.
No issues on multiple builds and roms both ICS and JB stock and AOSP all work fine. Try deleting the phone profile from the car bluetooth and the car profile from the phone, reboot phone and pair again. Look for the message that pops up just after pairing asking for permission and check yes.
I have done precisely that. However I have experienced this on both of my cars bluetooth. This started after a certain OTA update.
maxspiderx said:
I have done precisely that. However I have experienced this on both of my cars bluetooth. This started after a certain OTA update.
Click to expand...
Click to collapse
Bumpie.
Sorry, another bump hoping for an answer.
I,m running stock/rooted JB gb08 was on GA10 before, no issues with BT. are you connecting to a factory car radio or aftermarket?
I have a kenwood DDX719 and it works flawlessly, music, calls no problem.
ICS is outdated you should try JB, it may just solve your issue. There is a new one/click in development sextape's GB08 stock/rooted build.
Pp.
Thanks for your reply.
I am having issues with both the factory car bluetooth and my Motorola bluetooth speaker.
I have deleted the profiles from both devices and re-setup everything. This time, car automatically recognizes the phone as a media device. However, I still have to reach into my pocket to take out the phone and manually connect it as a phone.
Your issue could just be the Motorola bt unit. Try pairing to a different phone and see if it works.
Pp.
sent from a jellybean filled epic touch.
No, I am experiencing the same issue with both the car bluetooth and Motorola.
It looks like your options Are a Gb el29 stock build or a Jb Gb08 stock build and then test.
These JB builds are very stable, I recommend the Gb08, it may solve your problem. This has only been an issue with some of the unstable/experimental builds and ics qualifies as that.
Time to one click your problem away.
Pp.:thumbup:
sent from a jellybean filled epic touch.
Having an issue with no sound emitting from any audio output on the phone, but sound will play through Bluetooth-connected device. No sound from front speaker (phone calls, dial pad), no sound from rear speaker (notifications, ringer, alarm, media) and no sound from wired earpiece/headphones. Seems like it's stuck in Bluetooth/headset mode, but turning off Bluetooth doesn't restore sound. Problem is intermittent, haven't determined pattern to the behavior.
Phone was rooted long ago but kept stock ROM. Flashed Paranoid Android 3.99 RC2 about a month ago, and problem seems to have started shortly thereafter, but not sure if related. Haven't tried to reflash.
Any suggestions? Tried searches, but didn't locate this specific issue.
SGH-T999 (US/T-Mobile Galaxy S3)
Is it a T999 or a T959? And flash back to stock.using Odin. If it still is a problem it's likely hardware related.
Sent from my SGH-T999 using Tapatalk
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
yardsale said:
Sorry, phone is T999.....got rid of the T959 long ago, but must have been stuck in my head.
Will reflash this weekend and hope the sound issue is resolved. Thanks.
Click to expand...
Click to collapse
Did some more investigating last weekend before flashing ROM (never did the reflash).....seems that often, not always, if I turn off the car ('13 VW) while still connected to phone Bluetooth, the phone's sound quits working (all sound). Rebooting phone and turning off Bluetooth does not restore sound. The only solution I've found is to reconnect to car's Bluetooth, then turn Bluetooth off before shutting down car, and that only works about half the time, but sound is instantly restored. My estimation is that this wouldn't be hardware related, is that a fair assumption?
I also have a Tasker profile set up on phone to disable PIN lock when phone is connected to Bluetooth device (enables Sena Bluetooth headset used with motorcycle helmet to function properly), could that be causing the problem? Anyone else experience this issue?
Please try another Rom. Some of the Custom Roms may not be uptodate with CM Checkins. This issue was reported a bit back. There were CM Code Fixes that may not have been incorporated in that rom.
I am using Slimbean 2.0 (Android 4.3.1) and have seriously tested its bluetooth capabilities.
its also been reported thst msny car manufacturers did not bother to put any time or money into their BT capable systems. they just threw it together so they could add to feature lists.
Lots of peopke have problems with BT in the car, especially on cm roms. but those are notorious for BT issues to begin with.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
Thanks for the replies. I flashed to Paranoid Android 3.99.1 RC1 but the problem still exists. I never had this issue with any of our vehicles, until switching to PA from stock ROM. If problem becomes unbearable, may go back to stock. Thanks again.
@yardsale
I should have mentioned in the previously. Please read this post of mine. Yes its a different Rom. However, here primarily the issue is that of hardware antenna of the T999 talking to the Car's antenna. Doc is 100 % correct, the manufacturers do use substandard Antenna. On that thread, someone else reported issues with two '13 VW for themselves and their brother's.