My car has bluetooth for for phone conversations, but not for media, so I also use a Blackberry Bluetooth Adapter. TW Roms consistently only auto connect to one of these devices and I have to manually connect to the 2nd. AOSP roms will always auto connect to both without intervention.
I know there have been apps like "Bluetooth Auto Connect" that help address the issue, but they still require you to turn on/off bluetooth. It's tough to seamlessly automate this in Tasker.
Is this something that can be addressed by devs of TW roms? It works just fine in AOSP!
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
I'm not sure when these problems started (which ROM or version or even which phone) but it's pretty consistent now. I have a Jabra Cruiser that doesn't connect regularly. If it doesn't connect I have to re-pair the device to my SGS4G (currently Valhalla-Black Edition). Often it doesn't pair the first or second or third time, which sort of defeats any safety benefits as I am fumbling with the phone and speaker while I drive.
So what I am wondering is the following:
Is anyone using this device successfully and consistently with the SGS4G?
Are there settings to clear for Bluetooth pairings that might help?
Is there a Bluetooth speakerphone for the car that people like?
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.
I never really bothered to thing about this until recently, but I personally have three ways I use bluetooth.
1) My car, when I get in my car I want my phone to connect to bluetooth
2) My headphones, when I turn on my headphones I want my phone to connect to bluetooth
3) My home stereo, I only want this connection to happen when I initiate it
Is there anyway to manage bluetooth connections per device like this in Android? As it stands my only thought is to have my home Tasker profile disable bluetooth, but that's a hacky workaround and I'm hoping something better exists (also something that doesn't require tasker so I can make it work on my wife's phone too).
Trigger app should do the trick. You can create profiles for each BT connection.
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.