search

goodev / a2dpvolume

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

Prevent automatically starting Music app on connect. #159

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I had to stop using the app because every time my car (or any device that 
supports a media stream) pairs with my phone (Both a Galaxy S3 and a 
Thunderbolt,) it launches the Android music app and stops any other music app 
(Pandora, WTOP, WinAmp.)

Since I primarily use the app for reading text messages, I find that behaviour 
quite disruptive and have not found an obvious way to disable it. (I don't have 
anything listed under "Start app on connect.")

Original issue reported on code.google.com by thevirtu...@gmail.com on 9 Apr 2013 at 7:22

GoogleCodeExporter commented 9 years ago 
This app only starts programs, playlist, shortcuts etc. that you specify.  If 
you don't configure one to start it does not start it.  It does not 
automatically configure this for you either.  There is nothing started by 
default.  I suspect this behavior is driven from another app like Tasker or a 
music player feature, or the device makers Android overlay.  If you have 
nothing configured in my app to auto start it will not start anything.

Original comment by JimR...@gmail.com on 10 Apr 2013 at 10:53

GoogleCodeExporter commented 9 years ago 
One other thing to keep in mind: some BT devices connect as 2 devices.  Make 
sure both are configured correctly.  You may have no app to launch in one but 
the other could be configured with an app or shortcut to launch.  Also true if 
you force connect a 2nd device.  Make sure all your devices are configured 
correctly.

Original comment by JimR...@gmail.com on 10 Apr 2013 at 10:58

GoogleCodeExporter commented 9 years ago 
It's very strange. I don't have Tasker installed and the only time this 
behaviour shows up is when the A2DP Volume service is started. Oh well. It was 
worth asking.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 2:30

GoogleCodeExporter commented 9 years ago 
Very strange. Can You send your xml data export of your configuration?

Original comment by JimR...@gmail.com on 10 Apr 2013 at 2:55

GoogleCodeExporter commented 9 years ago 
Yes, I can as soon as I get home this evening. Thanks for looking into this.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 3:05

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 10 Apr 2013 at 3:08

GoogleCodeExporter commented 9 years ago 
What version did you start with?  Are you on 2.9.3 or 2.9.4 now?  What Android 
version do you have?  Did the problem exist on older A2DP Volume versions?  It 
may be possible I introduced a bug somewhere along the way but I have not 
observed this behavior on any of my devices.  Understanding what version it 
started happening on would really help.

Original comment by JimR...@gmail.com on 10 Apr 2013 at 3:42

GoogleCodeExporter commented 9 years ago 
I'm running 2.9.3 (the latest version on Play Store, it seems.) I can install 
2.9.4 when I get home and give it a try.

The Galaxy S3 is running 4.1.1, stock but rooted.
The Thunderbolt is running 4.0, though it also did it on the old 2.3 ROM. 
Custom ROMs.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 3:50

GoogleCodeExporter commented 9 years ago 
It done it as long as I can remember. Unfortunately, I don't Play Store doesn't 
track when an app was originally installed. I usually work around it by 
disabling the A2DP stream on the device in question, but that's a rather 
cumbersome process on Android.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 3:58

GoogleCodeExporter commented 9 years ago 
I just did some experimentation with the two devices I have with me at work 
today. (Galaxy S3 and Satechi FM Transmitter) and was not able to reproduce the 
issue. I'll try it again on my other phone and BT devices when I get home. It 
may be device specific and I've just been incredibly unlucky.

If it turns out to be device specific, this is going to turn into a feature 
request. Add a checkbox to stop media on connect to work around badly designed 
bluetooth devices.

I've attached the A2DPDevice.xml from the Galaxy S3. The "CAR_M_MEDIA" device 
(F9:71) is the device that has persistently given me problems. The "Carkit" 
device (21:C2) is the device that I just tested with.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 4:31

Attachments:

GoogleCodeExporter commented 9 years ago 
To clarify, I *have* had issues with the Carkit device. It just wasn't acting 
up today.

Original comment by thevirtu...@gmail.com on 10 Apr 2013 at 4:32

GoogleCodeExporter commented 9 years ago 
I reviewed your data and don't see anything that would cause this issue.  I 
also looked through the code and followed the connection event through.  
Nowhere did I see anything that would invoke a music player.  I thought I might 
have left some test code in there somewhere but found none.  Which music player 
starts?  Some devices may toggle the play/pause command on connect.  If you 
left your music player paused on a song, and it was active (showing when you 
open the phone) then this could happen and my app would not effect this.  

I don't have any Samsung devices so I am not familiar with their Android 
overlay.  Check the music player settings for the player that starts.  Also 
look to see if there are any triggers in the settings for Android.  Have you 
Google searched for this issue?

Original comment by JimR...@gmail.com on 10 Apr 2013 at 10:32

GoogleCodeExporter commented 9 years ago 
I've done some research and more experimenting, and I'm reasonably certain that 
the "CAR M_MEDIA" device is sending the "play" command as soon as it connects. 
I have searched Google for it, and the solution is to disable the media stream. 
The other device doesn't send it, but I think my old device probably has a 
setting somewhere that simulates that. I did find your A2DP Switch program 
which will hopefully make that a bit less cumbersome.

So, at this point, I'm thinking we can close this issue and turn it into a 
feature request. Is it possible to intercept the initial play/pause command on 
connect and cancel it?

Original comment by thevirtu...@gmail.com on 11 Apr 2013 at 2:07

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 11 Apr 2013 at 9:44

GoogleCodeExporter commented 9 years ago 
It may be as simple as letting users set A2DP Volume as the default music 
player and ignoring any commands that come over bluetooth.

Original comment by thevirtu...@gmail.com on 13 Apr 2013 at 1:45

GoogleCodeExporter commented 9 years ago

Original comment by JimR...@gmail.com on 7 Sep 2013 at 3:59

GoogleCodeExporter commented 9 years ago 
I can find no resolve to this issue. When every I activate my phone bluetooth 
earpiece Google music starts playing. Which is extremely annoying, I have 
removed the app from my phone. 

I enjoy the app otherwise, please advise if there is a fix for this issue.

Original comment by gunsmith...@gmail.com on 2 Feb 2015 at 4:29