Android - MediaServer eating battery?

Question

Android

The other day I put some music on the LG Optimus T (on an SD card), installed MortPlayer, and after a few hours I found that the battery was draining just before my eyes. The Android System and Media Server were to blame. Decided that it was a glitch of the player (he found many more funny glitches that make him unusable). Demolished it nafig - everything stopped right there, the battery began to live, as before, for several days.
But today it started again - all the same processes came out in the first place in battery consumers. Useful to google. Found references to similar behavior. The author assumed that some files are to blame, which are incorrectly indexed by the Media Server, because of which it enters an endless loop and eats resources.
While demolished from the map all the music. I left a couple of audiobooks with which, it seems, there were no problems before. I'm waiting for the battery meter to show.
I did not find any other information, but I would very much like to understand what exactly the problem is. What exactly could he not like in simple mp3s? Russian tags (UTF-8)? Something else?
Maybe someone came across and knows how to treat. I would not want to give up music completely, but charging every half a day (or even more often) is not an option.

Answer 1

Add an empty .nomedia file to the root of the music folder, otherwise the content would not be indexed, and use a player that can scan the folders specified for it and not use the system library. for example the same powerAMP

Answer 2

maybe the player is naughty? :)

Answer 3

Necroposting. On Xiaomi Redmi Note 4, a complete rejection of Chrome helped me. Unable to delete it. I deleted the chrome cache, forcibly turned it off (chrome), deleted it from startup in the background, in short, I did everything I could and do not use it. While there is silence for a day, the phone is cold, charging from morning to evening is 71% and earlier and 40% happened less and generally sat down. The advice, oddly enough, was caught on the Samsung forum.