The problem I am referring too is bluetooth devices not automatically connecting to AOSP 4.X.X roms. This happens with my bluetooth 4 out of 5 times I try to connect it. My bluetooth is a Blackberry Stereo Gateway (hereafter referred to as BSG) that I use in my car. I have seen this bluetooth behavior on every 4.X.X AOSP rom I've ran so far, including any cm10 roms that have been floating around. I am currently running CM9 for stability over cm10. Afaik AOSP kernels are basically interchangeable between ICS or JB, my cm9 rom has linux 3.0.43.
I just logged some bluetooth connections using ddms. These are not full logcats, they were captured in real time so I could offer more specific information. I am not a kernel developer, but I am a power user. Any other types of bluetooth need logging I can pull it off.
bluetooth connect crash.txt: I had just powered on the bluetooth in the phone, then I powered on the BSG. On the phone it showed Connecting, followed by Connected. Then it dc'd. The bluetooth icon showed blue briefly.
bluetooth power on dmsg.txt: Just a log of the bluetooth turning on.
bluetooth a2dp connect failed.txt: Powered on the BSG after the phones BT had already been on for a while. Phone says Connecting and then nothing. no bt icon changes. This one is the most common problem.
bluetooth a2dp connect succede.txt: Both phones BT and the BSG have been on. Connection initiated from the phone by tapping on the BSG's entry in the bluetooth screen. This one was logged right after the failed connection.
NEW bluetooth a2dp autoconnect success cm9.txt: Got in my car tonight and for once it auto connected. Pulled the log when I got home.
Related
Hi ppl,
I'm having issues with bluetooth on mytouch4g phone.
To connect it to hands free set I have to every time turn off and then turn on bluetooth on my phone.
Anyone have similar issue?
Is there a setting somewhere to set default device?
Thanks
Do you mean "Hands free mode" or do you mean pairing a stereo BT headset?
With the stock OS -- "Hands free mode" can be set by either 1) starting the Car Dock application, or 2) Using the BT headset phone button or the Genius button to enable speech commands, and saying "Hands Free On" once the phone is ready.
With the stock OS -- pairing of the phone occurs automatically whether the phone or headset is powered up first. Pairing of media (for stereo headsets) will only occur automatically with any degree of regularity -- from experimentation and observation by others, reported on forums like this -- if the phone's BT is powered up =after= the headset. One can manually disable and enable media connectivity after long pressing on the device in the BT settings window, and that will establish the media connection -- but it is probably easier to have a BT power toggle on your home page somewhere.
If neither of these answers the question you were asking, please rephrase it. And of course, for a custom ROM (non-stock OS), ask in the appropriate ROM's thread in the development subforum.
I mean bluetooth at car. I'm able to pair my phone with car and connect with no issues.
If I get into the car with my phone and bt on - it will not establish connection. I have to turn off bt on the phone and turn it back on. Then it will establish connection. It works fine with my old Fuze.
alex_gim said:
I mean bluetooth at car. I'm able to pair my phone with car and connect with no issues.
If I get into the car with my phone and bt on - it will not establish connection. I have to turn off bt on the phone and turn it back on. Then it will establish connection. It works fine with my old Fuze.
Click to expand...
Click to collapse
i have the same exact problem except i can't use any of the bt features on my car.
2010 infinit G37
any help would be greatly appreciated
every time i use wireless tether after i have switched it off none of my bluetooth devices will connect to the phone until I reboot.....anyone else experience this?
Have not tried that yet - But I di have a Bluetooth - WiFi issue. If i try to uese Bluetooth on a WiFi call, it usually does not work right.
I had similar problems CM7 on a different device, but not with stock. Am on stock now and not happy
Bluetooth working excellent!
WiFi calling working excellent!
I will try to use wireless tethering....
5 min, please
Yes I have experienced BT connection issues. Even after a reboot. It sometimes will take 2-3 mins for my headset to connect.
No issues here
Sent from my LG-P999 using Tapatalk
No issues here either. I was actually just saying to myself this phone has one of the best Bluetooth implementations I've ever seen so far. I've used with BlueAnt S4 car speakerphone and my car's A2DP audio bridge simultaneously as well with other devices by themselves such as a Bose BT1 headset, a Motorola DC800 A2DP audio bridge, and various Broadcom based adapters in computers... no issues at all (which really surprises me). I've used WiFi tethering extensively and leave Bluetooth enabled and never have any issues when I go to connect.
I had a similar problem on CM ROM's on Mt4G, but that was because of poor strength of WiFi in CM kernel - it would disconnect the WiFi.
With G2X, it stays connected, and the Bluetooth is connected when on WiFi calling, but sound only on the device - not through the bluetooth. Calling on Network - Bluetooth works fine.
I am in home office, so use WiFi most of time.
Another issue - but probably not the G2x- Google voice dialing really sucks. Also was the case on MT4G - used Dragon Diction/Genus App - much better. Trying a market app, but not as good as D&G.
Works for me. I turned Bluetooth on first, and then Wi-Fi calling.
i syned my earpiece to BT had to restart the phone now it wont pair or find the device when i hit scan
BarryH_GEG said:
Works for me. I turned Bluetooth on first, and then Wi-Fi calling.
Click to expand...
Click to collapse
May not have tried it that way yet - will give it a whirl.
I have a similar issue relating to bluetooth and wifi...here is my issue:
If I have both BT and wifi tether on it works, but as soon as i turn off WiFi tethering none of my BT devices will connect untill I reboot
I am also having trouble with my blue tooth. I use a handsfree device in my car. It syncs the blue tooth but seems to mute the sound. It doesnt work.
I am running CleanROM 7 (touchwiz basec ICS ROM) on my S3 and I've been using it in my car with a tunelink auto BT adapter that outputs to my aux port.
Lately, for seemingly no reason, the phone has stopped connecting the tunelink to media audio. The device is paired but never connects to media audio. When I have both devices on, under the BT menu on the phone I go to the tunelink device settings and try to check the box that says "media audio" it blinks for a second, sometimes it will say "connecting..." but then just stops and the check box never sets and it never connects to the device (the BT icon in the status bar never turns blue)
I just tried installing the latest firmware (modem) with no luck. I've rebooted, fixed permissions, with no luck. I just gave up in a battle to get BT audio to work with AOSP based ROMs (it was distorted and skipping) so I've just about had it with BT problems. I went back to CleanROM because I had been using it before I tried AOSP for a very long time with no issue. Does anyone have any ideas how I can fix this? Any insight is appreciated!
Any luck with this? I have a new Nexus 6 that I'm having the same problem with. Before my old Nexus 5 I had no issues.
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
nickelnine said:
Hi all,
I have a 2008 vehicle in which Bluetooth seems to be a problem depending on which ROM I have installed on the device.
I'm currently on Android 9 OB 7 and Bluetooth connects and stays connected through incoming and outgoing calls. Works flawlessly.
However, with for example Lineage (among others), the Bluetooth pairs, but connection drops soon after or drops after the first call with the car stereo showing "Net Search", meaning the car BT lost service but the phone Bluetooth is still connected. I've tried restarting and resetting network settings but no luck at all. Changing dev options doesn't work either.
I'm thinking it could be a Bluetooth stack difference?
Is there a way to replace the lineage Bluetooth with OOS?
There is no bluetooth.default.so file that I could find
Any help or direction is appreciated.
Click to expand...
Click to collapse
I am having the same issue with 9.0.2 OOS. So not sure if this us a compatibility issue with more than 1-2 years old vehicles or something else? Glad to hear that OB7 is working fine for you. Hope fix is coming soon. It's simply annoying.
I am having car connection issues as well. I have a 2010 Ford Edge. Just moved from Sony Xperia XA1 Ultra on Orea to my first OP device - OP6 Pie 9.0.2 - I can connect to my car initially but once I turn off my car, I have to go through a series of reconnect steps. I called tech support and we spent about 45 min troubleshooting - of course I was told I was the only one who had complained of this issue - anyway no resolution. The only way I can "reconnect" is to go into my car's system settings and select "connect to BT device" then toggle bluetooth off and on in the phone - sometimes this works with the first go, other times I have to repeat this cycle 5 or 6 times. Simply selecting "previously paired devices" in the phone app doesn't work either.
Really a pain in the tush, because I am usually in a hurry and don't have time to go through all this scenario to get a connection.
On the other hand, I have a bluetooth ear piece (made by Samsung that is like 5 or 6 years old) that reconnects every time I turn it on, no problems.
Car connections too but was not present in omni
I found for stock, performing a network reset (mobile, wifi Bluetooth) then restarting the device fixed the Bluetooth connection issue.
For custom non-stock ROMs, for my issue at least, I found its not a Bluetooth issue at all but rather the mobile network drops and the car Bluetooth cannot reconnect. The same network reset as above does not work but what does work is toggle off the "automatically select network" and manually select the mobile network from the menu that pops up. This keeps the mobile network intact (until the next device reboot, at which point repeat the steps) with the car and all is good.
I only figured it out by accident; hope this helps others.