Connection back to the same device doesn't work anymore (Android Nougat)

jroal / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume

http://jimroal.com/slist.htm

95 stars 33 forks source link

Connection back to the same device doesn't work anymore (Android Nougat) #257

Open thosie2 opened 6 years ago

thosie2 commented 6 years ago

Environment: Samsung S7 Edge SM-G935V, patch level 2017-08-01 (Nougat), A2DP Volume Service 2.12.9.1

It seems that the connection back to the same device under Android 7 (Nougat) doesn't work anymore. This trick worked without any problems before updating to Android 7.

jroal commented 6 years ago

That is odd it worked to begin with actually. It is also strange that this would be needed in the first place. I don't know what to do with this. It was not intended function to begin with so I lean towards just not fixing it. Can you explain more this use case?

thosie2 commented 6 years ago

The use case listed in the tips (https://github.com/jroal/a2dpvolume/wiki/Tips) is exactly what I was looking for:

“My Bluetooth music device won't connect when I connect to my car hands free …

You have a Bluetooth device that supports hands free and A2DP but it does not automatically connect to A2DP. This has been an issue with some devices. In this case use A2DP volume to also connect back to the same device. When the hands free profile connects, it will force connect A2DP.”

Until the update to Android nougat it worked fine, so it would be great if it would work under nougat again. I'd be very grateful.

Lubosi123 commented 6 years ago

I have the same use case as thosie2 and the very same issue. I would be deeply thankful for a fix.

jroal commented 5 years ago

@thosie2 , @Lubosi123 I have now made many changes but none directed at this specific issue. However, many of the changes fixed crashing at various points. I know this is an old issue now and I would liek to close it if it is no longer an issue. Feedback please.

Lubosi123 commented 5 years ago

@jroal thanks for following up, I tested, and unfortunately the issue is still there.

jroal commented 5 years ago

2.12.11.1 did not have a fix for this issue, none was attempted. You can see what is in each update here: https://github.com/jroal/a2dpvolume/wiki/Log-of-Updates. I don't have a good way to duplicate this as all my devices that support both hands free and A2DP will automatically connect A2DP when hands free connects. Force connecting Bluetooth devices is a tricky back-door process. It's a bit of a hack really. I will likely not be able to fix this issue unfortunately.

As a test, can you install A2DPConnect2 from the Play Store: https://play.google.com/store/apps/details?id=a2dp.connect2. When your device connects, see if this will connect A2DP on it. It uses some of the same code from A2DP Volume actually. It is just a widget so please read the instructions here: https://github.com/jroal/a2dp-connect2.

You should also check your Bluetooth settings to make sure all the profiles are checked for the Bluetooth device in question. You can set up Android to only connect some profiles.

jroal commented 5 years ago

Please test 2.12.11.8, just pushed to beta on the Play Store. There were many issues that would cause the app to crash during connect and disconnect. Let me know if this is fixed.

thosie2 commented 5 years ago

@jroal I tested 2.12.11.8, but unfortunately the issue is still there.