I'm using homeassistant to track mine (oneplus 5) and my wife's (nokia 6.1) phone via bluetooth. I'm using both the pi's built in BT and also the two google home mini's we have. The Pi sees both of our phones fine. The google home mini's sees my phone fine as well. However, my wife's Nokia 6.1 isn't being recoginized by the google home mini's unless I do pair device. I have Bluetooth scanning turned on in the advanced settings under location on the device. Any thoughts on why the home mini's don't see the device unless I go into pairing mode? Like I said, the minis see my Oneplus phone without having to go into pairing mode. I'm not sure if there is another setting I should look at on the Nokia.
Related
Hi, I'm trying to connect my Evo to my Windows 7 laptop so I can use the laptop as a hands-free (better speakers and mic).
It was really easy to pair the Evo, but after that there are no options for connecting?
If you press and hold the computer's name in Bluetooth Settings, the only option is give you is to Unpair. Unless my car and BT handset, where it shows 3 selections (Connect, Unpair, Options).
Has anyone been able to successful pair AND CONNECT their Evo/Android phone to Windows 7?
I got mine to connect once, did it on the laptop side after making phone visible, just transfered some files, doubt it will do what you want without a program on laptop with those drivers that will let it, I doubt it could native
Thanks, yea, on the PC side, there isn't any option to actually connect it?
I can see my phone and it has all the services checked but there's no actual option to connect. Not sure if this is a Win7 or Android issue?
It's the default Windows 7 bluetooth driver; it's not very compatible with smartphones or anything other than some OBEX, headsets, A2DP, etc.
Third-party Bluetooth drivers work OK though, like Blue Soleil.
thanks, that sucks.
hopefully, M$ will improve their bluetooth stack to work better with mobile now that winMo 7 is out.
Hi, I've got a small issue with my bluetooth a2dp device. The device is this one:
BlackBerry Remote Stereo Bluetooth Gateway. It is made by RIM, but works with any device supporting a2dp. My issue with the Galaxy Nexus is that it no longer auto connects.
My setup is in my vehicle, I keep the bluetooth receiver connected to the aux power jack and aux audio in in the center console. This way, when I start the car, the receiver powers up and tries to auto-connect to the last device. On my vibrant with Android 2.1/2.2 this worked fine. When I dabbled with CyanogenMod and some other custom roms, it stopped working but I chalked it up to some problem with the custom rom.
Now, I'm seeing the same sort of problem: if I keep the screen of my nexus on, I can see the bluetooth icon change blue, and then immediately change back to gray. To me, this indicates that the receiver succeeds in connecting but is then disconnected for some reason. The device only supports a2dp, not the handsfree profile. When I looked into the Android kernel code, I found a place where the kernel will try to connect the handsfree profile if the a2dp profile is auto-connected, but it wasn't clear if that was the actual problem or not.
Anyone else have any similar experiences?
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
bigdawgr6 said:
I have the same device in my 2008 Accord coupe which is placed in the center arm console. I had an Evo 3D that would automatically connect when I would start the car and BT was already enabled on my phone. I too switched to a different ROM and would have issues auto connecting so I switched back to a different ROM. Now on my stock GN, I have to manually go into settings and click the device to connect. I see no settings about auto connecting when in range. I will have to see if the BT icon turns blue and then back to gray... haven't looked for that. If anyone has thoughts on this, I'm all ears!!
Click to expand...
Click to collapse
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
# Automatically connect both A2DP and HFP/HSP profiles for incoming
# connections. Some headsets that support both profiles will only connect the
# other one automatically so the default setting of true is usually a good
# idea.
#AutoConnect=true
Click to expand...
Click to collapse
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
jjohns63 said:
I suspect it has something to do with Android's attempts to auto connect to the headset profile when a A2DP profile is connected.
See:
from https://github.com/android/platform_system_bluetooth/blob/master/data/audio.conf
I have seen the code where this happens and it seemed that if the headset profile failed to connect, the A2DP connection was also disconnected. Though, I can't recall what file it was.
Click to expand...
Click to collapse
Strangely enough, the phone paired with the device twice without issue yesterday and failed once later on that same day. I'm toggling BT off and then on to get connection for now.
It seems like the phone and device are connecting without issue but I know I haven't done anything to change it. I'm on AOKP M3 and Leankernel V1.8 if that helps. When I first flashed those two, I still had connections issues, so switching to them wasn't a resolution.
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
I have been trying this for weeks and this app solved it!!! Thanks for making the app!
jroal said:
I am not sure this really helps your issue but it is related. I wrote an app that will auto-connect Bluetooth devices. It is free on the market and is called A2DP Volume. The current implementation of auto-connect looks for one device connection and then connects another. I started another widget that will simply connect a Bluetooth device but I have not finished that one. A2DP Volume is free, open source, and ad free. You can find the open source project on Google Code. Just search for A2DP Volume.
Click to expand...
Click to collapse
jjohns63 and bigdawgr6,
Any update on this problem? I don't have the Nexus, but I have Droid Incredible 2. I also run into the same problem when I use CyanogenMod 7.2, which is a AOSP based ROM. The connection is fine with the stock ROM. I have tried to change things in the audio.config but it does not seem to help. I think I ran into a post somewhere saying HTC stock ROM uses a propietary bluetooth stack and AOSP and CyanogenMod uses BlueZ open source stack, and that is where the problem is.
Anyway, it would be nice if you guys can share some info.
Thanks!
Bluetooth cuts in and out when connected to 2 devices (car's "phone" and "media")
I have a GSM Galaxy Nexus on stock Jellybean, and bluetooth streaming works great in my car (Chevy Sonic) until I also connect the "phone" connection. When it's connected, the music cuts in and out constantly. Phone calls seem to do the same thing if "media" is connected.
If I kill 1 connection, the other works great. Is this a Galaxy Nexus problem or Jellybean? I've tried stock, franco's, trinity, etc kernels but I'm guessing this won't matter (since the source was JUST released for JB).
Does anyone else pair to multiple BT devices simultaneously? Do you have issues?
I just came from an iPhone 4S, and it paired nicely with both connections without them cutting out. I hope this is something I can get working because I use both functions all the time.
Thanks!
I connect to 2 devices in my truck and it actually seems to work better since installing Jelly Bean. On ICS I had a similar problem. My truck connects via the "phone" profile and I connect to a bluetooth adapter for the "media" profile. I could use either of them independently without a problem, but with both connected, my call quality was awful and my music would cut out periodically. I believe that the truck "phone" profile was disconnecting and reconnecting every couple minutes as I would see the display on my truck indicate that a bluetooth device had just connected.
Since installing JB, that behavior seems to have stopped. I can't say for sure as I haven't driven very much yet since installing it, but early testing seems to indicate the problem has gone away. I know this doesn't help in your situation, but I did want to share my experience as it was similar to yours.
I've tried to connect my phone via BT to two different cars and have no luck. It will scan for devices but won't find them at all. Does this happen to anyone else with the SIII? Strangely enough, it finds and connects to my JamBox is just fine.
What ROM are u on ? Stock or rooted?
What kind of cars I know my Audi A8 will connect but I always have to connect manually and enter the 1234 paswrd.
Sent from my SAMSUNG-SGH-I747 using xda premium
bbgt2 said:
What ROM are u on ? Stock or rooted?
What kind of cars I know my Audi A8 will connect but I always have to connect manually and enter the 1234 paswrd.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Still rocking the stock and unrooted for the phone. I tried on a Lexus GS and a Scion xB but no results show up. How do you connect manually? I should try that
Phone calls and bluetooth streaming works fine in my 2009 Mazda 6 (GT, no navigation). My phone is stock + root.
I use Slacker Radio everyday, launched by Automateit Pro when the connection to my car is established.
IIRC, I had to input a PIN on my phone, then in my car to do the pairing, and after that, I had to connect the phone manually to the stereo, but only once. After that, it's automatic when I start the car. Watch out for the "Only visible to paired devices" setting on your phone. It must not be checked.
I too have major issues with bluetooth, my phone connects whenever it feels like. I had to flash to cm9 to be able to listen to music in my G37. No problems in my other car (it has aftermaket pioneer system).
PS Just flashed the CM10 since they finally figured out A2DP, but the image is broken. (Note to myself: "Read the thread before flashing") Will wait for the next nightly build.
Nissan's always had a horrid BT stack in it. I'm in an 09 Altima and BT just sucks. I know it's not the phone as I've tried multiple phones from multiple vendors and they all suck. Nissan won't fix it either.
[Q] Bluetooth issue with Cars
I have AKOP Rom and KT Kernel. My bluetooth connectin to Mazda Cx-5 is fine. However, the problem I have is a lot of phone information (Song title, Battery Status) I used to have on stock, now are gone. Previously, I can fast foward or Rewind a song, also, once BT is connected, the default music player will start automatically
Can someone suggest a BT manager app which can change and enhance BT setting?
I have a 2009 Mercedes B200. My phone connects to the car just fine, but no sound comes from the speakers and no sound goes into the microphone. Same thing with my car and the HTC One X, although that was fixed with a stock ROM update. Bluetooth on cars can be very hit and miss.
So I have an Eonon GA1312 Single din (RK3188).
I have been having two bluetooth issues. All have been troubleshot by disabling and enabling/deleteing data/cache of Bluetooth app, different settings and "off" in factory settings for bluetooth tab and a reload of malasyk rom after a factory reset.
Bluetooth will always show every device it sees. I have 6 Devices under "available devices". 2 I know of (game pad and OBD). 4 were because things were in range when scanning. They persist through everything. It's so weird.
Secondly, the ODB, while off is "available", but once conmected it jumps to "paired" devices and connects no problem. My game pad (nes30 pro to test the viability of bluetooth media control without buying one) is there whether in range, on, or not, and if I try to connect, I tap it, I am asked if I want to connect, and it does nothing.
My cellphones connect fine.
I read all over about some bluetooth limitations but found nothing documented on tje wiki or in the forum.
Any help? Sorry if repost, I thought I made a thread but it says it isn't there and I have no move/deleted notices.
Bump for justice.