search

Omeya / a2dpvolume

Automatically exported from code.google.com/p/a2dpvolume
0 stars 0 forks source link

No audio transmitted after a call #83

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Device (phone) brand: Samsung
Device (phone) model: Galaxy S2
Android OS version: 2.3.6
App version: A2.1 or main
What steps will reproduce the problem?
1.Connect phone to Hands-free in the Car
2.Connect phone to a A2DP BT dongle
3.Play music on phone via A2DP dongle
4.Make a phone call to someone who's already talking
5.The phone will not send data to the BT Dongle until a phone call is done

What is the expected output? What do you see instead?
Normally when I make a phone call, music stops, I can talk using my handsfree 
and then when the call is over music starts again.
If I try to call someone who is already talking the call it's over but music 
data is not send to the A2DP, I know it because I can change the songs without 
problem but I cant hear anything. If I unpair the handsfree music is played 
again on the speakers

Please provide any additional information below.
I don't know the exact problem, but I think It must be something about the 
PHONE/MEDIA pair. 

Thank you so much

Original issue reported on code.google.com by maranell...@gmail.com on 24 Jan 2012 at 1:02

GoogleCodeExporter commented 9 years ago 
Sorry I forgot to say that im using the lastest version 2.3.14

Original comment by maranell...@gmail.com on 24 Jan 2012 at 1:02

GoogleCodeExporter commented 9 years ago 
So when you say "call someone who is already talking" do you mean you get a 
busy signal and you end the call?  My app does not respond to phone calls in 
any way.  The pausing and resuming of music is completely handled by the phone, 
as is the directing of the music stream.  A2DP Volume does respond to text 
messages and it will direct a text-to-speech stream to read the text. Does this 
problem happen in you turn OFF the A2DP Volume service before connecting?  Test 
that scenario with A2DP service OFF to see if it still does it.  Let me know 
the result.

Original comment by JimR...@gmail.com on 27 Jan 2012 at 12:33

GoogleCodeExporter commented 9 years ago 
Yes I mean that, my phone recieves the busy signal. I've also noticed that 
after that issue happens, when I'm far away from the car (and the BT Dongle) 
and I try to turn up/down the volume of the phone it keeps me saying BLUETOOTH 
VOLUME when there isn't any BT device connected.
What do you mean? I will try turning off the A2DP Volume and then turning it up 
again, that's what you want me to test??
Apologise my English (Spanish english hehe)
Thank you!

Original comment by maranell...@gmail.com on 27 Jan 2012 at 12:41

GoogleCodeExporter commented 9 years ago 
Some phones are slow to release the Bluetooth connection.  Sometimes Android 
can even show the connection as active when it is not.  I had that happen once. 
 Try with A2DP Service OFF or exit A2DP Volume completely (there is an exit 
button in the preferences menu) and see if you still have this issue.

Original comment by JimR...@gmail.com on 28 Jan 2012 at 3:26

GoogleCodeExporter commented 9 years ago 
I cannot verify this issue.  Unless you have more details, I will close this 
issue in one week.

Original comment by JimR...@gmail.com on 4 Feb 2012 at 1:05

GoogleCodeExporter commented 9 years ago 
Here I am again, sorry for the delay.
As you said, I've tried to exit the A2DP Volume app using the exit button on 
the menu and the problem still there.
Thank you for your time

Original comment by maranell...@gmail.com on 4 Feb 2012 at 1:09

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 4 Feb 2012 at 1:13