I apologize for re-posting -- I had originally posted this in the "Jellyverse FK23 ROM thread" and have yet to receive a response. I have parsed as many pages of threads as I can bear to read, and searched over and over. I refuse to believe that no one else uses bluetooth headsets!!
I recently tried several FK23 ROMs (including this one), by ODIN EL26 safe recovery and installing the ROM from SD.
Everything went great, running smoothly, etc... until I received my first phone call. Turned on my headset(s) and either can't hear the other party at all, or it is very muffled.
It appears to be an inherent problem in Android 4.1.* with various reports.
Have I missed something? Does anyone know if it would work to copy the bluetooth drivers/stack from a previous, working ROM? I really like the updates otherwise.
My headsets are 1) Jabra Supreme and 2) Plantronics Voyager Pro 3) Plantronics Voyager Pro HD
In regards to the problem being related to the "contact picture" or "mute bug" -- I tried several calls after a full wipe, with the stock leak, before even entering my Google account info, so no pictures (or phonebook) were present.
I was optimistic when I read this thread and comment #11 -- but I tried the suggested modifications with no luck.
Have tried disabling "Media audio" completely to no avail, although the A2DP media itself comes through fine (at least the clicks and such)
Thanks in advance!
Josh
Samsung h840 runs fine
Same issue with motorola HX550 BT earpiece
Having same issue with my earpiece on E4GT
Symptoms:
- digitized chipmunk sounds out of earpiece during call
- person on other end of call gets massive of static
+ media (on the other hand) sounds/works fine
this bug is NOT/B] present on FI27/earlier builds, and also not present on AOSP 4.1.1 build.
Noticed issue on FK09, FK23, and FL04
does same thing on friends E4GT with FK/FL builds
and friends earpiece (moto 720) works fine on his & my E4GT
My Plantronics Voyager works just fine.
Josh, I know nothing, so I use garwynn's one-clicks and so far no issues with anything on JB. I use the Aliph Jawbone and it has worked fine on fk09 fk23 and fl04 builds.
Maybe try that, if you haven't.
Sent from my SPH-D710 using xda app-developers app
Thanks for the responses... Foodbaby, glad to have some affirmation of the issue, unfortunately I've yet to come to a determination/fix. Can someone who uses A2DP (media audio) on their headset, confirm that FK23 is working fine for them on phone calls?
P.S. The way to check and see if you are, in fact, using A2DP is go to to Settings -> Wireless -> Bluetooth and click on the settings "gear" to the right of the headset in question. See if you have "Phone" and/or "Media". If "Media" is present, then you're using A2DP.
I have a hunch, probably incorrect, that the A2DP is throwing a wrench in things. I've since flashed to the miui ROM but it's starting to irritate me. I'll probably try to use the Plantronics headset updater app and disable media audio on the headset. I know for sure that just "unchecking" the media box has no effect.
Headsets tested: Plantronics Voyager Pro, Plantronics Voyager Pro HD, Jabra Supreme, BlueAnt Q2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-D710 using xda app-developers app
I have the exact same problem with FL04 and a Plantronics M50...
When I switched to FK23, I used the no data option and had to re setup my bluetooth connections (car, Bose Series 2, Jawbone Era). They didn't work initially, so I removed the pairing and redid them, and they worked fine the second time around. The only anomoly is that my car connection, and the Jawbone don't show in the list unless they are connected. Not a big deal since everything was working. Yesterday I got a JBL Flip bluetooth speaker (very nice portable speaker BTW), connected it, listened to some music, and though all was well... Until I tried using it for the speakerphone function. It would ring normally, but as soon as you connect, the caller gets nothing but horrible static, and there is no incoming audio at all. Then to top it off, after the phone has connected to the speaker, bluetooth phone audio will no longer work with any headset correctly until I reboot the phone. No issue with A2DP, but phone audio is borked until a reboot (I did a battery pull as well, but that might have no been necessary. I tested the speaker on another phone and it worked fine... I hope this is sorted out on FL16...
BTW, A2DP and phone audio work fine for me with the Bose, Jawbone and the car...
I had the same thing happen maybe I should try again without the jbl flip so that the plantronics discovery 975 will work
For now, I have just disabled the phone profile for the JBL Flip (I don't really need the speakerphone function anyway) and am just using the media profile. The setting is sticking for now and all works.
same exact issue here
josh7143 said:
I apologize for re-posting -- I had originally posted this in the "Jellyverse FK23 ROM thread" and have yet to receive a response. I have parsed as many pages of threads as I can bear to read, and searched over and over. I refuse to believe that no one else uses bluetooth headsets!!
I recently tried several FK23 ROMs (including this one), by ODIN EL26 safe recovery and installing the ROM from SD.
Everything went great, running smoothly, etc... until I received my first phone call. Turned on my headset(s) and either can't hear the other party at all, or it is very muffled.
It appears to be an inherent problem in Android 4.1.* with various reports.
Have I missed something? Does anyone know if it would work to copy the bluetooth drivers/stack from a previous, working ROM? I really like the updates otherwise.
My headsets are 1) Jabra Supreme and 2) Plantronics Voyager Pro 3) Plantronics Voyager Pro HD
In regards to the problem being related to the "contact picture" or "mute bug" -- I tried several calls after a full wipe, with the stock leak, before even entering my Google account info, so no pictures (or phonebook) were present.
I was optimistic when I read this thread and comment #11 -- but I tried the suggested modifications with no luck.
Have tried disabling "Media audio" completely to no avail, although the A2DP media itself comes through fine (at least the clicks and such)
Thanks in advance!
Josh
Click to expand...
Click to collapse
Everything went great, running smoothly, etc... until I received my first phone call. Turned on my headset(s) and either can't hear the other party at all, or it is very muffled.pleeeaaaaaase heeeeeelp
Fine with my Motorola H730 but I wish I could get rid of the dialog that pops up every time I turn bluetooth on.
I FOUND A FIX for FK23 bluetooth problems 4.1.2
josh7143 said:
I apologize for re-posting -- I had originally posted this in the "Jellyverse FK23 ROM thread" and have yet to receive a response. I have parsed as many pages of threads as I can bear to read, and searched over and over. I refuse to believe that no one else uses bluetooth headsets!!
I recently tried several FK23 ROMs (including this one), by ODIN EL26 safe recovery and installing the ROM from SD.
Everything went great, running smoothly, etc... until I received my first phone call. Turned on my headset(s) and either can't hear the other party at all, or it is very muffled.
It appears to be an inherent problem in Android 4.1.* with various reports.
Have I missed something? Does anyone know if it would work to copy the bluetooth drivers/stack from a previous, working ROM? I really like the updates otherwise.
My headsets are 1) Jabra Supreme and 2) Plantronics Voyager Pro 3) Plantronics Voyager Pro HD
In regards to the problem being related to the "contact picture" or "mute bug" -- I tried several calls after a full wipe, with the stock leak, before even entering my Google account info, so no pictures (or phonebook) were present.
I was optimistic when I read this thread and comment #11 -- but I tried the suggested modifications with no luck.
Have tried disabling "Media audio" completely to no avail, although the A2DP media itself comes through fine (at least the clicks and such)
Thanks in advance!
Josh
Click to expand...
Click to collapse
after doing lots of reading and a little bit of luck finally all 3 of my bluetooth headsets working flawlessly.i hope this will fix your problems also...
first connect your bluetooth device to your phone and unpair your device.then turn your bluetooth device off then on phone go to settings>application manager>go to all>find bluetoothshare>click on clear cache if you can or/then clear data and turn bluetooth off and restart phone.do not turn it on till you reset your bluetooth device.
now reset your bluetooth device ( not every brand and make the same when it comes to reseting so do your research and reset your bluetooth device) and pair it again and things should work fine.
when i did my first try fixed the problem partially ( I heard them but they could not hear me) so I did it like 3 times and everything ended up working great.
some headsets like moto hx550 and moto elite flip have up to 6 settings when you are resetting them.I turned all those futures off when I reset mines so also might help to know...
my phone is S II and on FK23 4.1.2.
I did this fix on my brothers evo 4g lte and fixed his bluetooth problems also.
I love my phone more then ever now with this rom.It runs super fast and smooth.the only complain i have now is the battery drain.i have 4 batteries and I use an average of 2 to 3 batteries a day but i use my phone all day non stop due to my business and personal needs...
I also had the wifi dropping and reconnecting every 5 to 10 seconds like others.I fixed that by resetting the modem and the router ( turn them off and turn off everything that uses internet.wait at least 3 to 4 minutes and turn modem on first and wait for all the lights to come on modem and just then turn router on and reconnect everything one by one which you can connect your phone first if you like).
I wanna thx xda and the all the developers here.
I hope these fixes will work for you all and good luck...
Mr Z
Thx Z
gqmandq said:
after doing lots of reading and a little bit of luck finally all 3 of my bluetooth headsets working flawlessly.i hope this will fix your problems also...
first connect your bluetooth device to your phone and unpair your device.then turn your bluetooth device off then on phone go to settings>application manager>go to all>find bluetoothshare>click on clear cache if you can or/then clear data and turn bluetooth off and restart phone.do not turn it on till you reset your bluetooth device.
now reset your bluetooth device ( not every brand and make the same when it comes to reseting so do your research and reset your bluetooth device) and pair it again and things should work fine.
when i did my first try fixed the problem partially ( I heard them but they could not hear me) so I did it like 3 times and everything ended up working great.
some headsets like moto hx550 and moto elite flip have up to 6 settings when you are resetting them.I turned all those futures off when I reset mines so also might help to know...
my phone is S II and on FK23 4.1.2.
I did this fix on my brothers evo 4g lte and fixed his bluetooth problems also.
I love my phone more then ever now with this rom.It runs super fast and smooth.the only complain i have now is the battery drain.i have 4 batteries and I use an average of 2 to 3 batteries a day but i use my phone all day non stop due to my business and personal needs...
I also had the wifi dropping and reconnecting every 5 to 10 seconds like others.I fixed that by resetting the modem and the router ( turn them off and turn off everything that uses internet.wait at least 3 to 4 minutes and turn modem on first and wait for all the lights to come on modem and just then turn router on and reconnect everything one by one which you can connect your phone first if you like).
I wanna thx xda and the all the developers here.
I hope these fixes will work for you all and good luck...
Mr Z
Click to expand...
Click to collapse
Thanks Z,
This helped me with my HX550.
Defaulted the HX550, turned off all settings, then followed instruction approx 3 times, then it worked.
I was able to turn back on all the settings except the WBA(wide band audio) on the HX550. Dont know for sure, but turning WBA on reproduced the issue, then turning back off fixed it again.
Also, I'm currently on GA10 of the E4GT - rooted. issue was present on this build stock & rooted
Thx again YO!!!!!!!!!!!!
EDIT: dont go to GA10, there is a major call bug unrelated to bluetooth issue found in post on sxtp forums. would post , but apparently im too new to forums.
going back to FL16 and/or 24 to test bluetooth fix again. will post after
.
foodbaby.mw said:
Thanks Z,
This helped me with my HX550.
Defaulted the HX550, turned off all settings, then followed instruction approx 3 times, then it worked.
I was able to turn back on all the settings except the WBA(wide band audio) on the HX550. Dont know for sure, but turning WBA on reproduced the issue, then turning back off fixed it again.
Also, I'm currently on GA10 of the E4GT - rooted. issue was present on this build stock & rooted
Thx again YO!!!!!!!!!!!!
Click to expand...
Click to collapse
How do you turn off the settings on the hx 550? Any help is greatly appreciated I have been going crazy tryin to get bluetooth working.
Sent from my SPH-D710 using xda app-developers app
AAAR1126 said:
How do you turn off the settings on the hx 550? Any help is greatly appreciated I have been going crazy tryin to get bluetooth working.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
hold up hx550 to your ear and hold the call button while turning on, it will talk you through it
fix worked on FL16 also
foodbaby.mw said:
Thanks Z,
This helped me with my HX550.
Defaulted the HX550, turned off all settings, then followed instruction approx 3 times, then it worked.
I was able to turn back on all the settings except the WBA(wide band audio) on the HX550. Dont know for sure, but turning WBA on reproduced the issue, then turning back off fixed it again.
Also, I'm currently on GA10 of the E4GT - rooted. issue was present on this build stock & rooted
Thx again YO!!!!!!!!!!!!
EDIT: dont go to GA10, there is a major call bug unrelated to bluetooth issue found in post on sxtp forums. would post , but apparently im too new to forums.
going back to FL16 and/or 24 to test bluetooth fix again. will post after
.
Click to expand...
Click to collapse
Same worked on FL16(JB):
-turned off WBA on HX550
-paired to phone, verify crappyness
-unpair
-clear blueshare data
-reboot phone
-pair to phone again, verify goodness
issue not present on FL24(ICS), assuming Sprint/Jellybean build issue. i dont think AOSP-4.1.1-A6 had this bug either.
Thanks Mr Z
gqmandq said:
after doing lots of reading and a little bit of luck finally all 3 of my bluetooth headsets working flawlessly.i hope this will fix your problems also...
first connect your bluetooth device to your phone and unpair your device.then turn your bluetooth device off then on phone go to settings>application manager>go to all>find bluetoothshare>click on clear cache if you can or/then clear data and turn bluetooth off and restart phone.do not turn it on till you reset your bluetooth device.
now reset your bluetooth device ( not every brand and make the same when it comes to reseting so do your research and reset your bluetooth device) and pair it again and things should work fine.
when i did my first try fixed the problem partially ( I heard them but they could not hear me) so I did it like 3 times and everything ended up working great.
some headsets like moto hx550 and moto elite flip have up to 6 settings when you are resetting them.I turned all those futures off when I reset mines so also might help to know...
my phone is S II and on FK23 4.1.2.
I did this fix on my brothers evo 4g lte and fixed his bluetooth problems also.
I love my phone more then ever now with this rom.It runs super fast and smooth.the only complain i have now is the battery drain.i have 4 batteries and I use an average of 2 to 3 batteries a day but i use my phone all day non stop due to my business and personal needs...
I also had the wifi dropping and reconnecting every 5 to 10 seconds like others.I fixed that by resetting the modem and the router ( turn them off and turn off everything that uses internet.wait at least 3 to 4 minutes and turn modem on first and wait for all the lights to come on modem and just then turn router on and reconnect everything one by one which you can connect your phone first if you like).
I wanna thx xda and the all the developers here.
I hope these fixes will work for you all and good luck...
Mr Z
Click to expand...
Click to collapse
I can finally use my Bluetooth again with Jelly Bean Thank you, Been driving around using speaker phone since first leak PITA but liked the new TW so much couldn't go back to ICS.:highfive::good:
Sorry I wasn't around.I'm glad it worked for you.You are very welcome...
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!
Ok so it's been a while I didn't use my phone with a wired headset, but some time ago I would always use it to listen to music on my daily commute. Lately I started using it again. I've always used it with some Soul SL99 for music and calls with no problems.
But since 2 days ago I noticed it stays on headset mode even after disconnecting the headphones. when I make a call the built in mic and speaker don't work and the proximity sensor disabled. I can use it on speaker with no problem, and if I connect the headset people don't here me clearly. I have to restart the phone to exit headset mode on it, but whenever I connect my headphones it'll stay in headset mode no matter what until I restart it again.
Only weird thing I've done is try out different audio mods, like AwesomeBeats, Ac1d audio and Noozxoide. So I can't tell if it's damaged hardware or software. I've tried full wiping my rom, I've tried 3 different Roms including going back to 4.1 and on every single rom it does the same thing.
So basically my question is, could it be software driver related? Or most likely hardware? If software, would there be a fix? And if hardware, what piece would it be, the loud speaker/headphone module, or the headphone flex cable?
Has anyone experienced this before?
I have no experience with it, but maybe this will fixed in the next update to fix Bluetooth streaming.
Can you try cm10 stable or another 4.2 rom and see if that helps
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
I have no experience with it, but maybe this will fixed in the next update to fix Bluetooth streaming.
Can you try cm10 stable or another 4.2 rom and see if that helps
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I did, I tried AOKP latest build, XenonHD, CNA 3.8.0, and some others. Still does the same thing. Hopefully it is software and I won't have to buy replacement parts.
No one can help?
....
Mods can close this thread, obviously there's no support in GN forums whatsoever,
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Still no one can help?
I've bought a Nexus some days ago and it already came with 4.2.1. I have just added root and CWM.
Yesterday I tried for the first time to connect it to my car's bluetooth handsfree kit. I activated Btooth, but I've not found any way to make the phone visible. Tapping on the phrase "your phone is not visible" did nothing. It was searching for devices but found nothing. Later at home I've found on google forums many people that have problems with bluetooth on 4.2.1. I also found that in some situation it is impossible to turn it off, and it does not work correctly. I have found this advice:
Go in settings - applications. swipe to the right last page "ALL". Search for bluetooth pairing app. Click on it and terminate it. Maybe you have to tap twice. Now your BT is off. Now go in application again (or use your favorite widget, like widgetsoid) and turn BT on again. Now it should work (for some time, only !!) This way I was able to pair Nexus with handsfree and also I've made some calls.
From forums, it seems a software bug. Found in other phones also, not only on Nexus.
Cheers
Sergio
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.
Has anyone encountered issues with connecting with a car bluetooth? My wife phone conntects with no issues.. She can use the cars remotes to make and receive calls.. Mine I have to pick a contact from the phone for it to work, it will not work with the car or my work truck controls.. It seems everytime it ask if my car or truck can access my contacts, I always choose allow, but nothing happens, but it works with the wifes.. This is with the Lollipop update, that we both have...
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Rom-Addict said:
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Click to expand...
Click to collapse
Got one to work, in my truck.. The car it worked for a while, then quit.. I will try it agian to see if it will stcik... Most likely caused by the 5.0 update..
I've noticed a Bluetooth problem that suddenly started in the last week or so. I upgraded to Lollipop when it first hit, and didn't have any problems.
Now, however, after Bluetooth works fine for awhile (I can connect to a Pebble watch, Bluetooth speaker, car Bluetooth, etc) all day long - then all of a sudden it can't connect to ANYTHING. Toggling Bluetooth off\on doesn't fix it.
Restart the phone, then everything works just fine for awhile. Until it doesn't, and I have to restart again.
Anyone else experiencing this pattern?
I've actually had the opposite happen. I have a iSimple bluetooth box in my car. I've never been able to auto connect with either VZW Note2 or 4. The CS rep told me it had to do only with VZW phones and he couldn't help me out. On another forum, another member mentioned he didn't have any issues with his older phone, so I dug out my old HTC Incredible. Sure enough, it would auto connect. Something changed with Lollipop, and now my Note4 will finally auto connect to the iSimple box. I tried using a third party Bluetooth app prior, but it didn't fix the problem.
Finally got the one in the car working as well... Because the wife and I have the same phone, I just simply changed the name of my phone and it works fine..
If your talking about the developer edition one rom update.. YES.. What fixed mine was wiping everything and redoing the one rom lollipop, then twrp, then installing Ricks Rom Lollipop, things have been perfect. I even addressed it in the ricks rom thread the week.
I haven't had any issues connecting devices but since Lollipop, when I am connected to a bluetooth speaker (car, bose, other bluetooth speakers) the audio gets choppy randomly.
I have done some searching and found others (LG g3) who had the exact same issue after updating to Lollipop.
I have tried rebooting, using different music apps, unpairing/pairing, forgetting the device ect and nothing seems to work. Anyone else having this problem after updating to lollipop? Anyone know how to fix it?
Hello everyone,
My LG G3 is giving me a hard time, when I connect a headset, its microphone isn't working or it does but it's barley audible compared to the device's own mic.
The headphones part is working as usual and when the headset is connected sounds goes only through them like it should.
I've started using this headset a few days ago and it worked like a charm but then it's suddenly stopped working like it had been.
Fortunately I have another LG G3 on hand, so first I checked the headset with it and it works perfect.
So then I've replaced the 3.5 audio jack from the other G3 into my own to figure out if it is causing the problem and it is NOT,
since I got no improvement in my own phone and I also put MY jack in the other G3 and it worked there flawlessly with two different headsets.
I've been trying to record into / monitor with two different apps (lg audio recorder and another another one).
I've killed all apps running in the background. I've restarted numerous times, ran CCleaner to clear cache memories and whatever.
At one point a few days ago, maybe it was just before it started (and this might be a clue) the "plugged device" icon or "headset" icon on the notification bar stayed even after I've disconnected the headset and I think I needed to restart the phone but if i'm not wrong the headset kept working after that.
I was trying to find any kind of audio service to restart or anything like that but I didn't find any, I just killed them all to see if it helps.
I've also tried using "soundabout" app to try to force the audio path to the headset and played with some settings but to no avail (I disabled soundabout service after that attempt).
Right now I see no other option but a hard reset and I'm pretty sure it will solve the issue. but I hate going through backing up and restoring everything. and even so, who said this issue won't happen again? I've tried to search for an answer but found nothing like my problem on the web.
I just read something old from 2013 that mentions a bug in android audio. not sure it's related. something about "AudioPolicyMangerBase" (it seems I can't post links yet) from an app that had a switch to switch between headset mode or phone mode. but in any case it's no longer maintained. again, not sure it's related.
Update: Now I got no sound with two different headsets on the SECOND LG G3 as well. it seems messing with it around, plugging and unplugging messes with it's software somehow and maybe it locks the audio route in a way that it's can't work.
Any way to reset all audio ins/outs routes in the device?
I'll appreciate your help. Thanks a lot!
Roy.