Can anyone tell me how to disable autostarting of Music app when headphones are pluged in?
Can't find anything about this in settings (both in app and mod settings).
Didn't find anything about this here (or somewhere in the internetz).
Am I the only one annoyed by this "feature"?
Music app starts because of a loose contact in the headphone jack.
Whenever you plug in your headphones the phone thinks you pressed the media button on the headset that shipped with the phone (it has a fourth contact on it's jack).
To disable this I used an App called Autostarts: https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts
In this app you have to look for the event "Media button pressed" and then disable forwarding this event to music app.
Eiertschik said:
Music app starts because of a loose contact in the headphone jack.
Whenever you plug in your headphones the phone thinks you pressed the media button on the headset that shipped with the phone (it has a fourth contact on it's jack).
To disable this I used an App called Autostarts...
In this app you have to look for the event "Media button pressed" and then disable forwarding this event to music app.
Click to expand...
Click to collapse
Thanks for the suggestion!
...But it sounds a bit like cracking nuts with a microscope.
What I can think of is to install an application that "steals" the event from the music app and disable autostarting from within this app. But this solution is far away from elegance also.
There should be a quick and elegant solution.
Maybe a short script that prevents forwarding of this event to music app?!...
...which, unfortunately, is beyond my abilities. :/
I don't think you can "steal" the event from a specific app.
The more media players you install the more receivers of the MediaButtonPressed event are in the list so I guess the event is a broadcast that every app can choose to receive and react to.
Autostarts' description says it can disable app components, but needs root access too - otherwise it will be in read-only mode.
So I guess if you knew exactly what the app does with root rights you should be able to reproduce it without the app.
But it's getting complicated again.
I think the easiest and also most comforable way is to somehow get this app (there's no free version unfortunately) and disable receiving of the broadcast for music apps.
Done.
Eiertschik said:
I don't think you can "steal" the event from a specific app.
The more media players you install the more receivers of the MediaButtonPressed event are in the list so I guess the event is a broadcast that every app can choose to receive and react to.
Autostarts' description says it can disable app components, but needs root access too - otherwise it will be in read-only mode.
So I guess if you knew exactly what the app does with root rights you should be able to reproduce it without the app.
But it's getting complicated again.
I think the easiest and also most comforable way is to somehow get this app (there's no free version unfortunately) and disable receiving of the broadcast for music apps.
Done.
Click to expand...
Click to collapse
You were right.
I installed Winamp first. Plugging the headphones began to start Winamp. When I turned off its option to control the headset, the music app began to start.
Then I decided to freeze the music app via Titanium Backup, and voila. Problem solved. After restarting the phone even music app icon disappeared from the menu.
Not the most elegant solution, but it works.
Thanks for the useful info!
Now I just have to find a lightweight player that doesn't autostart when the headphones are plugged in or that has an option to disable autostarting. Winamp is not so good lately.
I prefer Player Pro - but yet again - this app is not free...
Eiertschik said:
I prefer Player Pro - but yet again - this app is not free...
Click to expand...
Click to collapse
DeaDBeeF Player Pro... This one?
(Too many "Player Pro"s in Play Store.)
Sorry - I mean this one:
https://play.google.com/store/apps/details?id=com.tbig.playerpro
Here's a 7 day trial version:
https://play.google.com/store/apps/details?id=com.tbig.playerprotrial
I have a persistent problem that I can't figure out how to avoid ...
Problem #1
Whenever my Galaxy Note-3 makes a connection to Gear via bluetooth, it triggers Samsung "Music" to start. However, Music crashes at that instant, with an error message, "Unfortunately, Music has stopped".
Problem #2
Media Controller on Gear works on any music app other than Samsung Music. It works on Google Play Music and PowerAmp. However, that is limited to working properly on following commands: Play/Pause, Skip forward, Skip backward. But - if I attempt to control the volume up/down, then it fails. At this point, I see that Samsung Music has restarted on Note-3 with the same error message.
Note:
I have a stock Note-3. The Gear is also stock, with latest update (MK7).
I don't use Samsung Music. I notice that I can't uninstall it, nor can I disable it. Whenever I force it to stop (Applications setting), then it reactivates at the time of either above two problem events.
HELP PLEASE !
============== UPDATE
-> SOLVED: see page 2 below.
Can anyone confirm (unlike my experience):
1) Does Samsung "Music" work?
2) Does Gear's Media Control allow volume to be controlled up/down?
Honestly. My best advice is just to uninstall (or freeze in titanium) Samsung music player.
Sent from my GT-N7100 using Tapatalk
le3ky said:
Honestly. My best advice is just to uninstall (or freeze in titanium) Samsung music player.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
I wish I could but I can't.
I have a stock rom and want to continue with it. As such, native apps like Music can't be uninstalled.
The Application Manager doesn't offer "disable" for this one app.
I love stock too I couldn't find the option to stop the stock music player doing anything, so that was my only option :/
Root doesn't mean custom rom. Like I said it's pretty easy to root your phone, and stay stock (like me). Root just means you have more privalidges with the file system (essentially).
It's an option if no one else can offer anything better!
Sent from my GT-N7100 using Tapatalk
le3ky said:
I love stock too I couldn't find the option to stop the stock music player doing anything, so that was my only option :/
Root doesn't mean custom rom. Like I said it's pretty easy to root your phone, and stay stock (like me). Root just means you have more privalidges with the file system (essentially).
It's an option if no one else can offer anything better!
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
That is good news then. If I could ask you something, before I begin the root process ...
If I root my phone:
- do I have to reinstall all my apps?
- do all loose all my settings (emails accounts, etc)?
How do I root the phone?
Go to the Note 3 section on xda. They'll probably have a sticky explaining the best way
Sent from my GT-N7100 using Tapatalk
Skeleton said:
I have a persistent problem that I can't figure out how to avoid ...
Problem #1
Whenever my Galaxy Note-3 makes a connection to Gear via bluetooth, it triggers Samsung "Music" to start. However, Music crashes at that instant, with an error message, "Unfortunately, Music has stopped".
Problem #2
Media Controller on Gear works on any music app other than Samsung Music. It works on Google Play Music and PowerAmp. However, that is limited to working properly on following commands: Play/Pause, Skip forward, Skip backward. But - if I attempt to control the volume up/down, then it fails. At this point, I see that Samsung Music has restarted on Note-3 with the same error message.
Note:
I have a stock Note-3. The Gear is also stock, with latest update (MK7).
I don't use Samsung Music. I notice that I can't uninstall it, nor can I disable it. Whenever I force it to stop (Applications setting), then it reactivates at the time of either above two problem events.
.
HELP PLEASE !
Click to expand...
Click to collapse
I had a similar issue with my S4. Samsung music stayed persistant in my notifications bar running in the background. It was also on my lockscreen as a widget. I was able to go into settings/app manager and Turn Off the app. I did a reboot of the phone and all is well. I have since gone back in and turned the app back on and it does not repeat the errant behavior.
It's really weird that whenever you connect your phone to the Gear it starts the Music app, mine hasn't done that ... yet. However, as far as controlling music, mine has worked perfectly fine with Google Music (or Play Music or whatever it's called now). Also, volume up and down should work, however, the first time after you connect your Gear, if you try turning up the volume on the phone, an alert will pop up saying something like "Are you sure you want to increase volume? Loud music can be damaging" (forgive my inaccuracy), you have to press OK on the phone first, then it will work fine. It's really irritating, but better than nothing.
I hope that made sense?
Thanks to all for your comments and suggestions.
What I have deduced is:
- Samsung Music consists of two modules, but the user is aware of only one. The front end is what the user interacts with; it is essentially a file manager. The back end is the audio processor. In my case, there is a disconnect between the two. I can enter the front end and see the list of song files, but I can not play any song which is because the back end is not able to be accessed.
- There is evidence of disconnect between front end and back end. In the front end, I can enter [Settings ^ Play speed]; what I should see is a sliding scale from 0.5x to 2.0x. In my case, the labels are missing when moving the slide bar, and the slide bar does not remember my change rather it remains at 10% setting. I suspect the speed setting is stored in the back end, for which the front end (in settings) can not access the variable's parameter, nor can it later update the value.
- The back end program of Music does work for me. This is proven by selecting a song file in "My Files" explorer, then choosing "Sound player" from the context menu. For me, the song file then successfully plays. I suspect the player is the back end of Music because the icon in the context menu is the same (blue triangle with green music note).
- When Gear is making a connection with Note, it asks Note for the name of default media player. This causes Note to open momentarily the Samsung Music player in silent mode. Note then closes Music as experienced by most users, but in my case Music stays open because of a bug on my system/configuration.
Why is this happening?
- Some writers elsewhere wrote about the interconnection between many Samsung apps because of their interdependence on TouchWiz. Perhaps Music is one such program. Maybe something (other app or my configuration) has triggered Music to break for me.
- At this point I am left suspecting another user app has caused Samsung Music to break between the front and back end. Note, this problem has only arisen in the past month, but in that time I have installed a few more apps and the previous apps have auto-updated themselves. So, I am now left to uninstalling them and testing their effect.
Problem SOLVED
Alas - Problem SOLVED.
It is frequently suggested that Music Player can be repaired by flushing the cache in "Music". In my case, this never solved my problem.
However, today I discovered another cache that can also contribute to the problem, and thus offer a solution.
The following worked for me ...
Step 1
- Settings ^ Application Manager
- App = "Media Storage"
- Action = "Clear data"
Step 2
- Samsung Music
- All song files are removed.
Step 3
- Scan Media
Step 4
- Samsung Music
- All song files are relisted.
- All song files now play. YEAH
The stock media remote app seems to work fine with Spotify playing on the phone, however it would be pretty cool to see a spotify-specific app, maybe with the following features:
- like track
- albumart
- track/album name
- playlist selection
There are a few remote apps on the play store, but they are PC to phone, an existing phone to phone one may work, if one exists?
Any one have any idea's if the above is possible?
Aghh I just asked this on a different thread!
I don't know if a "Remote Control" app exists for Android, but if it does, it would still probably looks awful on the Gear, since it won't be optimized for it.
Hopefully there could be something created or "hacked" to, at least, transmit song info to the Gear native application. An Xposed module would be awesome!
So every time I want to load some playlist or folder through my AA music player (Cloudplayer), after 3-4 taps I get this message and I can't do anything other than actually stop the car (not always possible or advisable anyway) for it to receive commands. Voice search within the music player is clearly not working (it can't browse folders or playlists) so it makes the whole experience of using my phone for music streaming super annoying, especially on longer journeys.
Are there any ways to bypass this on a non-rootable phone (P20 Pro)? I mean thanks Google for thinking about safety but I need to do more screen tapping to set the aircon how I want it or browse trip details than I am allowed to tap on the AA app...
I don't have the phone you have, but have a Pioneer unit running Android Auto, and for me the lockout was part of the reason why I decided to stop using AA.
As far as I know with Android Auto, your request is not possible.
Your only option is to just not use AA and use something else.
In my case, I've just ordered a different headunit. But you may get away with just using different apps on your phone and avoid AA altogether.
My Note 8 & current 9 worked to allow Bixby to open Samsung Music (hands free in the car) but now it just says you need spotify to complete this action?
Why would you hobble your own APP and push Spotify? Money?
Bit short sighted, and makes Bixby drop another couple of points in the 'is this any use' league table!!
Unless you guys no how to make it work?