Related
Hey everyone. So I find I have an annoying issue that is kind of pissing me off. I guess a majority of car makers have this wonderful "feature" that sends a "play" signal to the phone while connecting. This would be nice IF I could pick the app it would play with but the epic and other phones like to pick the defauly music player.
The downside is that I tend to stream pandora or slacker while on the road so each morning I get 2 songs playing at once lol.... rather annoying. I then need to load the music player and stop it. There are some good parts to what the cars do....like if an incoming call is answered it pauses the active player (usually slacker for me) while on the call.
Does anyone have any ideas on how to change any of this behavior? I guess that would have to be a kernel change or possibly a bluetooth apk if there is one? I would love to try to find a way to leave the pause portion there for calls but maybe like a check if there is a active player on top then play or pause is OK, but if in background, dont do anything.
I have searched a lot on this and it seems to be a common issue. But I just wanted to see if anyone has any ideas. I tried the app "autostarts" but it complains about not having root access even though the phone is rooted so that isnt an option it seems. It's probably wishful thinking, but was hoping maybe someone has an idea.
Or is there something I could use to kill Music Player for example "if" it was auto started and not run by me directly?
I suppose you could use a task killer and set it to kill the music player whenever it starts up. You could always disable it when your not using it. I wouldn't use it for anything else besides the music player that you wish to kill.
The problem I see with that is with most task killers they use a timer... unless I am missing one that will kill it automatically when it opens? The downside to that is if I use another app to monitor that app I have a feeling I am going to kill my battery life if it constantly monitoring.
You may be able to do this using tasker. It's not free (five bucks) and it's a bit complicated, but there is a week's trial on the developer's website.
I'm not allowed to post links, but just google tasker for android. The version in the market doesn't have the trial, though.The one on the developer's website is a buck cheaper and offers a trial.
If you aren't familiar with it, you can basically use it to take any input the phone uses (phone, sms, location data, gesture, bluetooth data, whatever) and make it output any event, so you could have it give a media all stop command every time you connect it to bluetooth. You could even have it automatically bring up a little menu with pandora, music player, last FM.. whatever media players you use.. after that. You could probably even get it to perform different behaviors depending on which bluetooth radio you connected to (so you could have it do something different in your car than in your friend's car for instance).
It's really a lifesaver of a program, well worth the five bucks I dropped on it, it's replace multiple other apps in my life. Not trying to sound too much like a commercial, but I have every reason to think it would do what you want. It is a bit complicated until you get the hang of it, though.
megabillzilla said:
You may be able to do this using tasker. It's not free (five bucks) and it's a bit complicated, but there is a week's trial on the developer's website.
I'm not allowed to post links, but just google tasker for android. The version in the market doesn't have the trial, though.The one on the developer's website is a buck cheaper and offers a trial.
If you aren't familiar with it, you can basically use it to take any input the phone uses (phone, sms, location data, gesture, bluetooth data, whatever) and make it output any event, so you could have it give a media all stop command every time you connect it to bluetooth. You could even have it automatically bring up a little menu with pandora, music player, last FM.. whatever media players you use.. after that. You could probably even get it to perform different behaviors depending on which bluetooth radio you connected to (so you could have it do something different in your car than in your friend's car for instance).
It's really a lifesaver of a program, well worth the five bucks I dropped on it, it's replace multiple other apps in my life. Not trying to sound too much like a commercial, but I have every reason to think it would do what you want. It is a bit complicated until you get the hang of it, though.
Click to expand...
Click to collapse
+1... was just about to say, Tasker can do it. Tasker has been the best $5 I've spent in a loonnnng time.
I got tired of getting up in the morning for my 1.5 hour morning commute (gotta drop the kid off to daycare in another county) and getting to work late because it had been rainy and terrible. Setting the alarm crazy early just to check and see if the weather was any good was not a pleasant prospect, and with winter on the way, I needed a solution.
So I spent an evening with Tasker. I had it perform an HTTP GET at Accuweather.com after passing my zip code to the website. I then had it search the returned text for words such as "rain", "snow" and storm". It runs this search at about 5:00 AM, and dependent upon the result, sets an alarm (with a snooze function that I programmed in). After the initial alarm, since I knew I'd be too tired to pay much attention to WHY it had woken me up early, I have it speak out loud "Good morning, you have been woken early today because it is [X weather] and [X degrees, after performing a Celcius to Farenheit conversion]. It is currently [time].
I plan on posting the Tasker profile to my blog in a couple days after I'm sure it contains no bugs (it'll probably snow in the morning so I'll be able to test that scenario).
Anyhow, this just gives a taste of what Tasker can do. I have it launch a list of apps when I plug into the headset jack, silence my phone if I get within 300 meters of work, or sound an alarm, vibrate, flash an LED, take pictures, and redirect outgoing calls to my girlfriend's phone if I send it a certain text message, to name a few very useful profiles I've got set up.
Tasker does everything without forcing you to learn any syntax or do any coding at all. It would be a matter of minutes to set up a scenario where, if you connect via Bluetooth, it waits a moment and terminates the default video player application and then launches the other application you want to use. One of the profiles I've forgotten to mention is one that, when I launch Navigation with the GPS off, closes Navigation, enables GPS, and loads Navigation back up. When I'm in the car I just want to touch Navigation, not screw with GPS settings.
Anyhow, enough of my gushing about Tasker. Seriously, best $5 app you'll ever buy. Trust me.
That might be pretty nice... wonder if it can tell the difference between a bluetooth headset and AD2P. I'll have to try it. Wonder if it could start my car with its application too like 30 min after my alarm hehe.
Sent from my Emotionless Beast Epic 4G via Tapatalk Pro
I've been playing with Tasker and it will do what I need Thanks! I ended up setting up a profile that when it connects to my vehicle only, it will kill music player, wait 3 seconds and then kill it again... it took that due to the fact the car doesnt send the play signal for a few seconds.
First the tip: Don't use the "Show Station ID" option, it causes a massive battery usage.
Here are some numbers, with it turned on 4 hours of uninterrupted radio listening drains 36% of my battery. With it turned off the same 4 hours only drains 20% of my battery.
This is caused because with it turned on the phone never goes to sleep when the screen is off. When it is off the phone actually goes into deep sleep will still playing music which causes the drastic difference.
My numbers are based on 40 hours a week listening for 5 months of Station ID being turned on without thinking about it and getting a consistent 36%/4hr daily
Then I did my only factory reset when going to a ICS rom a couple weeks ago and not thinking to set it I started only losing 20%/4hr and noticed I was spending time in deep sleep.
It's great leaving work after a 8 hour day with a extra ~30% battery then I have been used to.
Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.
I think this may be due to the HUGE number of messages written to logs when RDS is enabled. I see this with my FM app using the RDS in my app's Samsung FM API mode, and there's not too much I can do about it in that mode.
====
BTW, I very much need people with S2's to help me get my app working on stock or stock derived ROMs on which the stock FM app works. It works fine on Galaxy S for a while and probably just needs a tweak or 2. See my post here and respond via PM or on my thread, since it's Off Topic to this thread.
Except that... perhaps my app can use less power when in background or screen offm since it can turn the RDS off then.
bpivk said:
Actually that's not an accurate comparison seeing that you've switched roms.
Try to compare it now on your new rom so that the comparison is done on same roms.
But thanks for the info anyway.
Click to expand...
Click to collapse
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.
shadowofdarkness said:
I did a quick 1 hour test with it on and the numbers still match up. My phone lost 9/hr which does equal 36/4hr.
Click to expand...
Click to collapse
I'll run a test on my Galaxy S and I'd bet the same thing happens. I think a dozen or more log messages every second can do the battery in faster.
For you or anyone else looking to test my app, there's not much to it:
Feb 26 release on the Market: https://market.android.com/details?id=com.mikersmicros.fm
Possibly better Feb 28 release: http://www.mediafire.com/file/i5654nm9vzd9d9m/Spirit_FM_Radio_v120228.apk
Just ensure a wired headset is plugged in, install the app and run. If you are rooted you should deny SU when it starts. At the Intro screen, press "Disable".
Hopefully, it will "just work" at that point.
NOTE: I just realized now that if you give my app SU, it will not try the Samsung FM API, it will go straight to the low level mode which gives no audio on the GS2. So set Menu->Settings->Debug->FM API to "OEM Proprietary" to force use of the Samsung FM API. If this API fails, I think the app will fall back to the low level mode. That can be prevented by setting Debug->FM Chip to "TI" and if the OEM API fails, then power up will fail.
Working or not, please give SU to my app, restart the app and send me a debug log with Menu->Help->EM Logs. After a few seconds. enter "GS2" and/or any useful phone or ROM etc. information in the email text and press send.
Remember, this test request is for stock or stock derived ROMs that can run the stock FM app only.
My app has been running in a "low level device driver mode" for over 6 months now on rooted GS2s, but without audio, except I think on the MIUI ROM which supports the CyananogenMod audio method. I need no testing for this mode, unless you know how to enable the FM audio or want to try the different Audio Methods to see if any magically work.
I have done a ton of reading about this mediaserver process, but nobody seems to have a definitive fix.. (.nomedia file etc etc)
It is ALWAYS greater than my "google play music" app usage or "poweramp" when I play music and sometimes it goes rampant and is the highest usage... (see pic)
I know the phone up time is pretty good for that charge level, but the killer is I only listened to music for about half an hour..
It just grinds my gears that this relatively unknown process is all but useless to my needs (poweramp has it's own media library), but cant be stopped..
Is anybody able to shed some light on how to stop this process, even if it is a temp disable while poweramp is running or something?
Anyone else sick of mediaserver feel free to chime in..
Oh, and to make matters worse, my friends Galaxy SIII can stream BT music all day long and mediaserver uses about 3%...
Both his phone and my phone seem to have the same "keep awake" time, but his uses almost no battery.. What gives?
My N4 is stock 4.2.1 rooted and i have no files on it apart from one album in the music folder, no google music sync, no ringtones, no pics.. Nothing..
I had the exact same problem on my Nexus S too..
http://forum.xda-developers.com/showthread.php?t=980575
It seems reasonable that corrupted media files is the cause. The phone might have scanned the damn file(s) over and over.
This might help.
https://play.google.com/store/apps/...SwxLDEsImNvbS5hZGR6Lm1lZGlhc2Nhbm5lcnJvb3QiXQ
Edit: I also suggest changing the music player.
Try Apollo
http://forum.xda-developers.com/attachment.php?attachmentid=1227099&d=1343478747
This (slightly outdated) version works better and less buggy than the one on Google Play.
Less features, less bugs.
I have the same worry, I think it uses too much juice for about 30 minutes of music. I use the default Google play music app though. Hopefully someone can help
Sent from my Nexus 4 using xda premium
1) "Mediaserver" is allegedly using up a huge amount of battery
2) Your battery's at 39% after 29 hours
...these two things don't work together.
Here's what's probably happening: Android is misinterpreting something as being related to mediaserver alone when in fact it's only partially related or even unrelated altogether. This is probably caused by an app you've installed, but could just as easily be an actual bug causing Android is assigning too high a percentage to a small amount of real usage, that's all it is. In any case, if your battery has lasted 29 hours, you're not suffering from any kind of "battery-drain" condition.
IIRC, in Android the ability to request music playback is separated from the ability to actually play music for the purpose of allowing music to be automatically muted or have the volume reduced under certain circumstances (phone calls, voice navigation prompts, etc) and probably various other reasons people smarter than me would understand. This generic process that plays audio is called "media server". When your music player of choice plays music, it's probably outputting the audio via mediaserver for compatibility and usability reasons - so you see "Google Play Music" and "PowerAMP" down at a tiny percentage because they're doing very little to speak of as applications, while mediaserver is running continuously whenever audio is playing.
When an app uses a service, or a service uses an app, or a service uses another service, the "blame" for battery consumption often goes to the wrong place in this way. For example, you might also have "Android OS" being blamed for "Google Play Music" using wifi to stream music, and various other perplexing scenarios. You might have "Android System" at 50% battery usage when in fact Android by itself is doing very little - it's the things that work through "Android System" that are actually responsible.
Another good example is MX Player, which IIRC uses mediaserver in order to provide hardware decoding, but is still really the app to blame for that video needing to be decoded in the first place. Etc etc etc, bla bla bla.
What's your screen-on time? I'm guessing around 1.5 to 2.5 hours, right? You're doing fine. Worry less about statistics and more about observable reality.
TL;DR: Sh!t fewer bricks.
You know i got the exact same thing as you have except mine is "google service." In a way I'm kind of disappointed with this. I expected a lot better quality from Google. Especially when these things are running on stock straight from Google.
nawoa said:
1) "Mediaserver" is allegedly using up a huge amount of battery
2) Your battery's at 39% after 29 hours
...these two things don't work together.
Click to expand...
Click to collapse
Thanks for the reply, and the information, but I still think something is not right... As I said before, ignore the long battery life as I have heaps of stuff turned off to try and investigate this bug..
I have previously played music all day over BT and had about 30% battery drain (70% left) which was about 60% mediaserver and 40% google play music.. This is perfectly fine for 5 or 6 hours of music playback... Google play music only.
However on this particular day for some reason I have 13% drain for 30 mins (21% of the 61% used) .. Something is not right.. I had not played music for the entire 28 hour period and mediaserver was nowhere to be seen in the usage stats, and then drove home with BT audio on, and BAM it's number one.. Using PowerAMP..
Perhaps the problem is with PowerAMP and how it handles the service?
Cheers, Tai
Bit of an update,
I ran the MP3 checker utility and found two corrupted, one of which was my ringtone!
I have since run the phone for two days and the mediaserver process has behaved itself and is just higher than the google play music app..
I still think that this needs to be fixed somehow, it shouldn't go pear shaped because one file is not 100%..
I got 2 days 10 hours on the last charge with over 1 hour of screen time and a few calls, dozens of sms's and emails, and music over bluetooth to and from work each day (3 trips)
Gotta be happy with that..
All right. Quick consideration. On my S2 there is a somewhat mediaserver that kind of drains the battery. The cause of this was the "sound when pressing" and "vibrate on press" (sry if translate isn't accurate) on sound settings.
In addition to that, make sure all vibrate and/or sound pressings on keyboards are disabled too.
Hope it helps.
Enviado desde mi Nexus 4 usando Tapatalk 2
Taijohnsen said:
Bit of an update,
I ran the MP3 checker utility and found two corrupted, one of which was my ringtone!
I have since run the phone for two days and the mediaserver process has behaved itself and is just higher than the google play music app..
I still think that this needs to be fixed somehow, it shouldn't go pear shaped because one file is not 100%..
I got 2 days 10 hours on the last charge with over 1 hour of screen time and a few calls, dozens of sms's and emails, and music over bluetooth to and from work each day (3 trips)
Gotta be happy with that..
Click to expand...
Click to collapse
What kind of mp3 checker utility?
:/
Sent from my Nexus 4
I'm lucky to get 15 hours of battery life... How???
Sent from my Nexus 4 using xda premium
First it was Google services, then Android OS, I got them both to behave, now it's Android Media Server, when I click on it, I do see Poweramp full unlock app there.
Not sure if it's poweramp though because a lot of people still say it isn't.
Any ideas?
If you're playing sounds at all it's going to be in use. It keeps your CPU awake to keep a song playing...
If you don't have any songs playing and it's awake, then it's bugged and you should reset the process.
Maybe I'm missing the point of this thread but it (this thread) seems rather off.
"Unknown process useless to my needs."
definitely need mediaserver to use your phone.
Seemonsters said:
"Unknown process useless to my needs."
definitely need mediaserver to use your phone.
Click to expand...
Click to collapse
I thought that the process only scanned the phone for media, and wasn't needed, but now I know what it does.. I still think that it should not have this problem dealing with corrupt files..
This is the checker I used..
http://download.cnet.com/MP3-Checker/3000-2141_4-10543407.html
How 2 days??
I have all the location crap turned off and only sync email, contacts and calendar.. Other than that, my phone is stock (rooted)
The mp3 checker doesn't see my phone when it's mounted via usb, I assume you have to copy everything off the phone to your computer and scan from there. This could take a while.
I had a similar problem before. I posted a possible solution in this other thread.
http://forum.xda-developers.com/showpost.php?p=35116498&postcount=8
First mediaserver, now the phone app?? wth.
I haven't even looked at the phone app today.
Having the same problem with Mediaserver, if I listen to a podcast on Doggcatcher I'm draining 15% per hour and battery stats show Mediaserver killing my battery. Listening to a podcast drains 15% per hour, it should hardly be draining anything. Simply listening to a podcast stored on my device takes more juice than browsing the Internet with the screen on, that's not right.
here's what i've done
# created a .nomedia file in every damn directory on the sdcard:
for d in `find /sdcard -type d`; do touch ${d}/.nomedia;done
#Then went through the directories which I wanted to allow Mediaserver to scan
#(DCIM/Pictures/Movies/Music etc...) and removed the .nomedia
for dir in DCIM Pictures Movies Music media subsonic; do find /sdcard/${dir} -name .nomedia|xargs rm;done
I'll let ya know if this changes anything.
As many of you may be aware, the Z2 has an amazing battery giving possibilities of 10 hours screen on time and over a week in standby time but this is all pointless when we get wakelocks that remain active with no way to end them.
Now ordinarily I would continue this discussion within the battery performance thread but because of how large the thread has become and it is more about the performance of the battery rather than problems within android, I decided it might be better to create a thread so people can easily access.
Now we can certainly do many things to limit applications from remaining active such as stamina mode and using the greenify application (and further enhance it if root access is available) as a form of further redundancy to prevent mischievous applications running amock.
So with all this done many people including myself still have problems with wakelocks stemming from "Android System". Now I have traced two problematic wakelocks both being "handlemediaevent" and "startingdockservice", the former I have been able to trace exactly how it occurs while the latter seems to be random.
In the case of "handlemediaevent" this problem in my research I have found occurs on many other devices and the conditions for it to occur is exactly the same so this is a fault in android which i guess will need the attention of rom devs and sony to fix (this has happened in every firmware version I've used so far including custom roms). So how does "handlemediaevent" occur? It's fairly simple, when using media controls such as play/pause skip etc on an external device such as on an inline earphone control or on bluetooth controls such as on a car stereo etc so basically, anything external to the application responsible for playing media.
As for the "startingdockservice" wakelock, I've yet to reliably find what causes this has it's infrequent and random in nature, sometimes it occurs straight away after docking the phone, other times it only occurs after repeatedly docking/undocking in fairly quick succession.
Back to "handlemediaevent" how do we fix it? This is where I have stalled, I've yet to be able to find a solution for this (and "startingdockservice" too), from the other devices that have had this issue, it seems that rom updates have been key in fixing it so until then all I can suggest is to refrain from using media keys external to the phone, so if one wants to skip a track, to do it from the walkman app or whichever application is playing media, I have tested this several times playing media from bluetooth or with earphones on and not using the external controls and the wakelock never activates/becomes stuck. And when it does occur, to restart the phone, I've not been able to find a service responsible for it in the running apps/services.
So what can we do to properly fix these wakelocks? Is there a fix? Can a fix be made? Or is it a case of going to sony and ask them/wait for new firmware?
TheOnlyIntruder said:
As many of you may be aware, the Z2 has an amazing battery giving possibilities of 10 hours screen on time and over a week in standby time but this is all pointless when we get wakelocks that remain active with no way to end them.
Now ordinarily I would continue this discussion within the battery performance thread but because of how large the thread has become and it is more about the performance of the battery rather than problems within android, I decided it might be better to create a thread so people can easily access.
Now we can certainly do many things to limit applications from remaining active such as stamina mode and using the greenify application (and further enhance it if root access is available) as a form of further redundancy to prevent mischievous applications running amock.
So with all this done many people including myself still have problems with wakelocks stemming from "Android System". Now I have traced two problematic wakelocks both being "handlemediaevent" and "startingdockservice", the former I have been able to trace exactly how it occurs while the latter seems to be random.
In the case of "handlemediaevent" this problem in my research I have found occurs on many other devices and the conditions for it to occur is exactly the same so this is a fault in android which i guess will need the attention of rom devs and sony to fix (this has happened in every firmware version I've used so far including custom roms). So how does "handlemediaevent" occur? It's fairly simple, when using media controls such as play/pause skip etc on an external device such as on an inline earphone control or on bluetooth controls such as on a car stereo etc so basically, anything external to the application responsible for playing media.
As for the "startingdockservice" wakelock, I've yet to reliably find what causes this has it's infrequent and random in nature, sometimes it occurs straight away after docking the phone, other times it only occurs after repeatedly docking/undocking in fairly quick succession.
Back to "handlemediaevent" how do we fix it? This is where I have stalled, I've yet to be able to find a solution for this (and "startingdockservice" too), from the other devices that have had this issue, it seems that rom updates have been key in fixing it so until then all I can suggest is to refrain from using media keys external to the phone, so if one wants to skip a track, to do it from the walkman app or whichever application is playing media, I have tested this several times playing media from bluetooth or with earphones on and not using the external controls and the wakelock never activates/becomes stuck. And when it does occur, to restart the phone, I've not been able to find a service responsible for it in the running apps/services.
So what can we do to properly fix these wakelocks? Is there a fix? Can a fix be made? Or is it a case of going to sony and ask them/wait for new firmware?
Click to expand...
Click to collapse
I've been looking into this lately. What app are you using? Wakelock detector? I'm thinking about getting the app "Deep sleep battery" on mine soon and see if it solves the wakelock problems.
I used BetterBatteryStats to diagnose which wakelocks were active. I'm not sure about using Deep Sleep Battery as this wouldn't fix the issue, just circumvents it (if it would work).
Also you didn't need to quote my whole post, it is a long post after all.
Wakelocks for me are due to "mediascanner". My bet is on some corrupted file on my SD card. Did you install yours as a system app or just install it?
Same problem here with wakelock "handleMediaEvent". Is there still no solution?
I am more and more convinced that this is caused by some apps that do not release the wakelock properly in some cases (e.g. when the display is off). I am having the problem on a Z3C as well as i9100 when using the play/pause controls when the screen is off.
In my case, it's because of the PodcastAddict app, what app are you using when you find the handleMediaEvent wakelock ? The stock sony walkman app ? In any case, i'm pretty much convinced that although this should be fixed upstream by android (e.g. with some timeout which releases unreleased wakelocks after some time automatically), the culprit are the apps using the feature and unreleasing the wakelock unproperly.
Please refer to my post in podcast addict's feed where i found reproducible steps that cause the problem: http://forum.xda-developers.com/showpost.php?p=57767863&postcount=134
If you can also have the problem happen consistently (and to see that, you'll need a rooted device in order to run BetterBatteryStats during testing) then i suggest you contact the developer of the app to let him know.
That's still work in progress, but so far i couldn't reproduce the issue using other standard apps (Apollo, Youtube, Walkman).
Okay, is there any solution to unrelease handlemediaevent wakelock via the command or anything else without reboot? So many results in google and no one permanent solution.
TheOnlyIntruder said:
As for the "startingdockservice" wakelock,
Click to expand...
Click to collapse
I have found solution on 4PDA.ru forum.
You need to install MyAndroidTools, then go Applications -> find Settings (com.android.settings) -> click All information -> find Sevice - DockService, it should be disabled, then go Receivers and find - DockEventReceiver, and disable it.
I use n7 for my music player... I just noticed that it's 3rd on my battery consumption list?? Even before charging it, when I was down around 50%, it was still #3 on the list but with almost 10% usage. I haven't used my player since Sunday and I've restarted a few times since then. It does show up on the lockscreen from time to time (not sure why that is either)?
FYI: I'm also going to ask this on the n7 G+ board..... Because this may not be a "Samsung" question?
It's still running in the background. Probably auto booting also. Try killing it in processes and see if you can stop it from auto start. Maybe some other app that uses it and runs it in the background? You got some audio editing software on your phone?
Verstuurd vanaf mijn SM-G955F met Tapatalk
Use package disabler and disable it from booting (you'll have to adb sideload extra permissions to get it to work without root) and install greenify, enable auto hibernation so it kills the programs you don't use when you turn the screen off.
You may want to just try greenify first. Also enable aggressive doze function which puts your phone in doze mode minutes instead of hours when your phone isn't in use.
Sent from my LG-H918 using XDA-Developers Legacy app
evo4g63t said:
Use package disabler and disable it from booting (you'll have to adb sideload extra permissions to get it to work without root) and install greenify, enable auto hibernation so it kills the programs you don't use when you turn the screen off.
You may want to just try greenify first. Also enable aggressive doze function which puts your phone in doze mode minutes instead of hours when your phone isn't in use.
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Started with a disabler..... I disabled a bunch of junk, but not all of the bloatware (I like a couple things).
I also found a setting that shows the music widget/info on the lockscreen..... I disabled that, and my music player no longer is eating up battery.