Related
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.
Hi everyone,
The bluetooth on my GSIII has been a complete failure. You can follow the saga here (http://www.benzworld.org/forums/w245-b-class/1662643-2009-w245-samsung-galaxy-s-iii.html), but basically it connects to my car and has no sound with the stock ROM and refuses to connect to the car at all with the AOKP JB build. It suggests an android problem, so I'm wondering if the bluetooth stack can be reloaded to reflashed with something different. If anyone has any ideas, I'm all ears. Thank you!
I have a problem with one of my Bluetooth devices dropping and reconnecting. Not sure why is just one. It works fine on an iPhone. I'm guessing your GS3 isn't the international version?
Sent from my SGH-I747M using xda premium
Nope not international, SGH-I747M from Bell.
I'm trying this. Will report back.
evilmonkey1987 said:
I'm trying this. Will report back.
Click to expand...
Click to collapse
Sweet! please let us know!
I'm having a different issue. it connects and stays connected, plays music but it doesn't list the song/artist info on my eclipse screen but the SG2 will..
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
evilmonkey1987 said:
Update: no change with the new kernel. The phones pairs but there's no sound, just as was the case before.
Click to expand...
Click to collapse
Try CM9. Bluetooth works much better with it. CM10 should have it fixed as well in a day or two.
Here's a 'six months later' update. My phone went through various android updates and I'm now on Android 4.1.1 (up from 4.0.4). The problem was still not solved, but instead of no audio, I now have one way audio, where people hear me but I don't hear them through bluetooth. I have also gone through a number of custom ROMs and kernels for my phone (including CM9/10 and AOKP) and nothing helped with the issue.
A couple of days ago, my girlfriend's HTC One X (finally!) got its Android update, also from 4.0.4 to 4.1.1. Her phone now works like a charm with the in-car bluetooth.
The solution I ended up with was a car cradle and a couple of NFC tags to control my phone in the car. My NFC tag that's stuck to my car cradle turns off WiFi, starts car mode, starts a car home app and turns my volume to max. All I have to do after that is connect the 3.5mm audio cable and I use my phone in place of the car's infotainment system. That way the phone integrates into the car as well and the only thing I lose are the steering wheel controls (they still work for volume).
My less technologically inclined girlfriend now has everything work auto-magicallly with bluetooth. So I guess all's well that ends well, but to anyone considering a US-spec Galaxy S III, watch out: the bluetooth issue is still not fixed. If bluetooth is critical, consider the HTC One X (but be warned: it has awful battery life!)
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
colbynmeghan said:
I have no issues with stereo Bluetooth and mono Bluetooth. Everything and everyone hears and plays fine. It might be an issue with your headset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
luncht1me said:
Colby. What version of android, kernel / rom combo are you using?? There's SOOO many people having problems with JB and bluetooth, regardless of rom or kernel setup.
If you're on stock... just nm then.
Click to expand...
Click to collapse
What's wrong with stock? I have no major issues with streaming BT from my phone to my Mazda 3 head unit, or to my Sony MW600 earphones. Even track titles work (the only thing that doesn't work is time display). In my experience, Bluetooth works best on the stock ROM.
Stock Rogers ROM (DLK4 - JB 4.1.1), rooted
KT747 (1/9/2013) kernel
CWM Recovery 6.0.2.3
PlayerPro Music Player
On my old Xperia X10, I had CM7 and had no end of issues with BT:
- Sometimes it would connect and there would be no sound
- Sometimes it wouldn't connect at all
- Sometimes it would cut out after switching songs
- It would stutter a lot whenever Wi-Fi was enabled (but I think that was a problem with the Xperia).
When I tried CM10.0 on my S3 I had similar connection issues, just not as bad. Also, the volume gain over BT was much lower, so I had to turn the car speakers way up. Stock 4.1.1 doesn't have any of these problems. The only problem I had was the audio switching over to speaker after turning off the car, but I fixed it.
Also, BT is apparently broken in 4.2.1 in general, not just CM10.1. Google confirmed a BT patch that works on the Nexus 7, due for release with 4.2.2: http://www.expertreviews.co.uk/smar...confirms-android-4-2-bluetooth-streaming-flaw
TIP: Don't forget to turn up the volume on your phone. I don't know how many times I accidentally turned down the volume and thought that it wasn't working. Now I have Tasker do it for me whenever I connect. :good:
4.1.2 has Bluetooth working use it everyday. (Stock and ROM.) Can't tell u which combo I use at a time. I flash a different ROM everyday. As 4.2.1bluetooth is broken expect for task's AOKP. He has it workingish.
Now as connecting to a car. Depends on what it connects as. And I've learned going to and from ROMs when u connect a source hit the volume up 9/10 times it works
Sent from my SGH-I747 using Tapatalk 2
[SOLUTION IN THIS POST]
There seems to be a compatibility issue with the new Bluetooth 4.0 of my HOX when pairing with some devices that have BT 3.0 version.
My own issue is with the Car Audio System of my 2008 C350 Mercedes Benz. The Bluetooth telephony worked perfectly with my DHD.
Now, I can pair my HOX with the system, but when I receive a call I can hear the other party only for 2 seconds then the voice is gone. As if we've both muted the call.
On the other hand, when I call someone, the phone call goes through just fine.
I've been reading a lot concerning this subject, and it seems that people are having the same problem with their SGIII.
A software update of the SGIII that was released for some carriers seems to have fixed the issue.
Also, my sister's iPhone 4S works fine with the system, even though it has BT 4.0.
So I believe this issue can be fixed, but it needs one of the Gurus on XDA to come up with a fix
My issue was slightly different (phone would pair but not connect) and I got onto my car kit manufacturer (in this case was a parrot system used in a mitsubishi) and found out I could update that. Since updating my car kit have had no problems at all.
That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.
xbiggyl said:
That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.
Click to expand...
Click to collapse
there might be nothing wrong on the phones side, have you checked to see if you can update your devices that are having problems as suggested?
i've had no issues running even bt2.1 stuff
Updating did not fix the issue.
Other phones (with older versions than BT 4.0) work perfectly.
I don't have access to updating my car's audio system atm, so I'm hoping something could be done on the phone's side.
But since this isn't a very wide spread problem among XDA users, I'm thinking it's not going to be an easy task.
Update:
Today, I tried something. After answering a call, the same thing happened (after 2 seconds I could no longer hear the other party but the call didn't drop)
On my HOX I chose Speaker and I was able to hear the other person talking; switched it back to BT handsfree (my car's audio system) and it worked.
Even though this is not a solution, but at least now I can answer a call when I'm driving. I just have to switch to Speaker then BT... Still better than nothing
Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.
p5x said:
Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.
Click to expand...
Click to collapse
Which ROM/Kernel are you using? And which car audio system are you trying to connect to?
bmw car
viper x rom but tried it on others and had the same problem
p5x said:
bmw car
viper x rom but tried it on others and had the same problem
Click to expand...
Click to collapse
After reading about this subject extensively, it seems that updating your car audio system is the best solution.
I suggest you take an appointment with the BMW service station and have them update your system.
yeah, i'm going to look into it. did you get yours sorted?
Bmw bluetooth 4.0
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
p5x said:
yeah, i'm going to look into it. did you get yours sorted?
Click to expand...
Click to collapse
No I haven't yet. But I guess I'll try to get an appointment for next week.
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
Does the call drop completely? or you simply stop hearing the other party?
I noticed something new today.
During a phone call (connected to Car Audio System), and I receive an SMS, the same thing happens (but the workaround still works).
staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
have you checked with them recently?
Have you tried other phones with the car? wondering if the SGS 3 would have the same problem...
---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------
xbiggyl said:
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
Click to expand...
Click to collapse
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect
p5x said:
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect
Click to expand...
Click to collapse
Have you tried a custom kernel? I recommend Faux
SOLVED
Even though this is an old thread, I wanted to let you know that this issue has been fixed.
By updating my Hboot to 1.31 and using a jelly bean ROM, I no longer have a problem with Handsfree over Bluetooth.
For those of you who are still facing this issue, I hope this helps.
NOTE: Before updating to new Hboot, you need to make sure your CID allows it. Check here.
Also you need to flash a jelly bean ROM afterwards, I use ARHD and it's pretty good!
.
Cheers!
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...
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.