Closed GoogleCodeExporter closed 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
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
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
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
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
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
Original comment by JimR...@gmail.com
on 4 Feb 2012 at 1:13
Original issue reported on code.google.com by
maranell...@gmail.com
on 24 Jan 2012 at 1:02