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.
hey guys, I got a serious question but I don't know where to go.
I am using this (Charmeleon Rom v5.0.0) rom on HTC X one originally delivered by the German Telekom.
Now I don't know cause I never used my phone without this rom. (I wanted to get rid of the ugly magenta branding asap )
Now, after running my phone for a while on this awesome rom I encountered some minor issues which I do not what they are related to.
1) Bluetooth connection often drops (link with car) but not every time used
2) Bluetooth audio quality is not present, regardless if using audio playback or doin voice calls. It always sounds totally scratched and stuttered regardless of bluetooth device linked to listen to (tried PC, Ford Audio, Jabra BT Headset)
The bad side is, bluetooth is pretty much unusable to be.
3) When on Carrier Internet (WiFi disabled) often the download or connection seems to get stalled/hung and will not recover redering downloads to idle infitively. They work fine after restarting them manually though.
4) Sometimes background apps (like the SystemMonitor) exit unexpectedly before they get restarted by the services automatically. Weird thing but not a big issue at the moment as it seems to happen to this background process only.
5) Beats audio sometimes shows up sometimes it doesn't (yes, always with packaged headset of course)
Does anyone face similiar issues? Does anyone of you know about this issue? Do you have any suggestions on what I could try to fix these issues?
Do you need a screeny of any system details of my phone?
Some help very appreciated.
Hi everyone, I'm hoping someone has a suggestion for me wrt to audio problems with my wife's Sprint Galaxy S3.
On a fully stock up to date S3, about 3 days ago all sound stopped working, this includes alarms, answer calls, key press sounds, playing music. However after a reboot, it would start working again for 6 hours or so, and then quit again. I assumed this was a software issue of some sort. I have an older rooted phone which I love and have had for years, I suggested that we finally root her S3, so she could get all those benefits plus fix whatever little software problem this was.
The rooting process when fine, and the phone now has CWM and CM 10.1.2 (Android 4.2.2). However the audio issue is still there and in fact a reboot no longer fixes the issue.
I have tried pluggin in the ear buds w/ built in mic, and those too fail to work. I also have paired various bluetooh devices like mini boom boxes etc.. they all pair fine however there is no audio output from them. No audio in the dial pad when hitting the numbers. When trying to play music the DSP Manager will crash, and then the music app crashes (tried Apollo and Google music). If I go to the sound recorder and hit record, it pops up with "Internal application error.".
So it seems all audio (speaker, mic, bluetooth, and headset) is broken which again makes me think software, but even after rooting and installing a new rom like Cyanogenmod the issue is here.
Any thoughts on what else I can try? Any firmware updates that I could apply specific to audio issues like this, or perhaps it is some sort of hardware issue that is preventing the software drivers from behaving properly?
thanks,
fishtek
I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.
Same problem
metalfan78 said:
I would Odin back to complete stock and see if the issue still arises. If it does then it could be hardware related.
Click to expand...
Click to collapse
I have that sane issue and nothing I do seems to work.
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.
Hi. Wondering if anybody could help. When I connect my oneplus 5T to my car I have problems. When it starts to call it disconnects the bluetooth from the car completely. However the call continues on the phone which is a complete pain as you cant use it through the hands free. Car is a BMW 630CI with pro nav if that helps.
Many Thanks
i first had problems to connect to my audi A3 bluetooth ... it simply didn´t find it
after trying again and changing the bluetooth audio codec it suddenly worked ...
Idk if it will work for you, but you can try changing the codec and se if it helps
Hi. Ive tried all 3. It connects fine and I can see my contacts but as soon as I hit dial it disconnects from the car.
Very strange.
Thanks for the suggestion tho
with mine in my car it every now and then gives me this a crackling sound.. Kind of irritating, I'm hoping a software update down the road fixes this.. I've tried all 3 codecs
Having issues with Bluetooth connection on my Prius Prime as well. It always disconnects, I had to disable Bluetooth on the phone and re-able it for it to work.
I experience the same with my Boss QC35. First connection, audio breaks with lots of noise and had to disable it and re-enable it.
Still found no solution. Hope the next update sorts it out as the bluetooth seems a mess.
So after looking around, there are issues with certain codecs and devices connecting being posted in the OP community forums. My Sony WH1000xm2 headphones stutter when using AptX HD. My JBL Everest 750NC's - if you turn the volume up too high, they disconnect from the phone. In my Cadillac ATS, whenever you place a call it'll stay connected, but you won't hear anything, and the other user can't hear you either.
I think they've acknowledged the issues and are working on them, but after putting Oreo on my Moto G5 Plus and Oreo's ability to change between all codec's on the fly (including native LDAC support!) I'm anxiously awaiting Oreo to be 'officially' released.
I'd say just be patient.. I'm sticking with this phone because I think it'll be worth it in the end. Wish I had better news!
so I resolved my Bluetooth issues by flashing FreedomOS. Now there is no intermittent crackling sound now and there is no issues at all ymmv, this was just my experience.
Thanks. Will wait for Oreo and then try different roms if it continues.
on FreedomOS before, it was giving me headache re-connecting to my Subaru car bluetooth, like after you shutoff engine, go somewhere and come back, unless you manually force connecting to the car, it barely auto reconnect back.
And also takes so long to get data sync from my Fitbit chargeHR to the app.
I don't think this kind of bluetooth issue related to what rom we have but the kernel and more specifically BT firmware.
-----edit-------
My friend also got BT issue when he tried to connect to BT headset. Hope Oneplus get something fixed on new oreo or updates
Just an update. Since upgrading to the official Oreo rom my problems have disappeared and my phone now works fine with the car Bluetooth.
Chris
I still have problems. Pause and unpause, and the track restarts. After ending a phone call the track restarts. 2018 RAM, Uconnect
With stock ROM 4.7.2 bluetooth connected only for a few seconds with my Audi A6. With every following stock ROM version it didn't even connect.
I tried every single Audio-Codec and the different settings in developer options - nothing helped. Once I cleared data & cache from the bluetooth system apps followed with a soft brick
Hi all,
Had same issues with my Hyundai ix35 and oneplus 5t (Nougat), tracks skipping, distorted audio in calls, etc... Tried emptying bluetooth cache, switching audio codecs without success. Now I just received the OTA update to Oreo (8.0), Oxygen rom 5.0.3 and it solved the issues!!! Yeay, no more auxilary cable hanging around !
fx_viper said:
Hi all,
Had same issues with my Hyundai ix35 and oneplus 5t (Nougat), tracks skipping, distorted audio in calls, etc... Tried emptying bluetooth cache, switching audio codecs without success. Now I just received the OTA update to Oreo (8.0), Oxygen rom 5.0.3 and it solved the issues!!! Yeay, no more auxilary cable hanging around !
Click to expand...
Click to collapse
I started from scratch but the issue persists.
I am having the same issue in my car. It no longer displays track information and the connection is not very stable. I will try switching the codec and report back.
i don.t have any volume control from the phone basically when i connect it to my car stereo
i can control the volume for the first 4-5 clicks ... and then the slider moves but there is no difference in the volume
i have to turn the volume from the stereo almost to the max
whit my old samsung tablet works great ... i have maybe 50% more volume then with my phone
tried all codecs ...