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
I didn't see any other threads on this and I'm not sure if it might be specific to the Verizon Galaxy Nexus or Lexus/Toyota cars. Since Jelly Bean, I've already had my car's bluetooth connectivity go into a weird state with the phone three times.
The car will be playing music (default music app) and the navigation app, playing just fine through the car's bluetooth, and then, both the car and phone will indicate connected, but the sound will stop. If I turn off the car, the bluetooth on the phone thinks its still connected. The only way to clear the condition is to turn off the bluetooth on the phone and turn it back on. So much for that "extra" Verizon testing. This all worked fine for me with ICS.
Anyone else see a problem like this?
Thanks!
I am having occasional problems connecting since jb. Was rock solid on ics. I am on sprint and have a Lexus.
This is my only issue with 4.1.
Sent from my Galaxy Nexus using xda premium
Samsung Galaxy S3 running Omega JB 4.1.1 - Driving a Toyota Prius
Greetings
I myself have experienced odd bluetooth issues with my Samsung Galaxy S3 running Omega JB 4.1.1 version 30 whilst driving my Toyota Prius.
Every 5 mins or 10 mins or so many minutes the audio from my podcast, for example, stops dead and I have to open up the app and hit play for it to continue.
Bizarrely I also experienced this the other day whilst driving a VW too.
Was fine on ICS.
I've you to find a solution.
I've been using Omega since version 25 and have also experienced the same issue on the Wannam custom stock rom.
Tonight I placed the device into Aeroplane mode and kept bluetooth running and the problem persisted.
I have no idea with regards I'm afraid.
Thanks
Dave
Update: I found that the audio issue I was experiencing was not bluetooth specific. I tried direct in to the car audio via the AUX jack and the problem persisted. But I also noted that after a clean install of a rom the issue did not exist so I worked my way towards the removal of the Deezer app and since then I have not experienced the problem. Go figure?
I am not having this problem with my Nexus and my myford touch sync setup. I do, however, get a lag between video and sound, where the sound is behind of the picture and out of sync. *shrug* Wish I could help more.
I can't even do more than phone on my 2012 BMW. No mobile office but calls work fine. When the CSR is turned off it doesn't switch to headset like it will of my wife's 2004 lancer.
Is it possible at all to take the new bluetooth stack from JellyBean 4.2 and apply it as a mod to either the stock 4.0.4 Sense ROM or the upcoming (eventually) 4.1 Sense ROM? Or maybe even CyanogenMod 10?
I know that the new stack is actually quite broken for a lot of people, but I have the opposite problem. The existing bluetooth is broken for what I use it with, but the new one works fine. So I'd love to be able to backport it, since I doubt we'll be getting 4.2 for quite some time.
Just FYI the issue is with a Sony car head unit MEX-BT2500. Media/A2DP won't connect with Android 4.0/4.1 bluetooth unless the phone is the one to initiate the connection.... but the default behaviour is for the head unit to initiate it on ignition. So the only way to get it to connect is to start the car, wait for Bluetooth to be ready on the unit, turn bluetooth off on the phone and then turn it back on again. Obviously this is a bit of a faff, and even then the audio skips and sometimes just gets stuck. So it's really not usable.
Related bugs:
http://code.google.com/p/android/issues/detail?id=24012
http://code.google.com/p/android/issues/detail?id=29564
However I've tested my Nexus 7 (running 4.2) on this unit and it works 100% fine. Which is why I'd quite like to get the same bluetooth stack.
Has bluetooth connection been fixed for Kit Kat?
I am looking to switch to some of the new Kit Kat room (like carbon, slim, etc)
But bluetooth would keep disconnecting
and they don't mention anything about bluetooth on their known issue sections, so could someone verify if bluetooth works on kit kat.
sirx7 said:
Has bluetooth connection been fixed for Kit Kat?
I am looking to switch to some of the new Kit Kat room (like carbon, slim, etc)
But bluetooth would keep disconnecting
and they don't mention anything about bluetooth on their known issue sections, so could someone verify if bluetooth works on kit kat.
Click to expand...
Click to collapse
I have been running HellKat and have had no issues with bluetooth.
I think it depends highly on your usage pattern. Most people don't seem to have any problems but then most people don't use bluetooth that often. I'm also on HellKat (01/30 release) and bluetooth crashes regularly. I keep my Pebble connected 24/7 and bluetooth will crash every 1-2 days. If I use bluetooth for tethering, it will crash within minutes. In all cases, bluetooth stops responding and eventually turns itself off. I can't re-enable it until I reboot the phone.
I've tried CM 10.2 stable and 11 nightlies before trying HellKat and they all have the same problem. I think it might have to do Android moving from bluez to bluedroid stack upon JB 4.2. Bluedroid seems to have some nagging bugs (particularly on the Nexus 4) that Google hasn't solved yet. Yes, I've tried that Nexus 7 bluetooth fix floating around - no dice.
If bluetooth matters to you, my advice is to stay away from JB 4.2+ for now.
I experience exactly what you describe. i will stick with Jelly bean for now as i used bluetooth for my headset and it dropping the connection and blasting the music for my work is not very pleasant.
thank you for your post most helpful
ithildin said:
I think it depends highly on your usage pattern. Most people don't seem to have any problems but then most people don't use bluetooth that often. I'm also on HellKat (01/30 release) and bluetooth crashes regularly. I keep my Pebble connected 24/7 and bluetooth will crash every 1-2 days. If I use bluetooth for tethering, it will crash within minutes. In all cases, bluetooth stops responding and eventually turns itself off. I can't re-enable it until I reboot the phone.
I've tried CM 10.2 stable and 11 nightlies before trying HellKat and they all have the same problem. I think it might have to do Android moving from bluez to bluedroid stack upon JB 4.2. Bluedroid seems to have some nagging bugs (particularly on the Nexus 4) that Google hasn't solved yet. Yes, I've tried that Nexus 7 bluetooth fix floating around - no dice.
If bluetooth matters to you, my advice is to stay away from JB 4.2+ for now.
Click to expand...
Click to collapse