Uneasily, I allowed the latest Mixzing update to install. I just had a feeling I shouldn't but was responding to a text when I received the prompt. Immediately afterward, I found that sound files (mp3s, etc.) would suddenly quit after playing for thirty or forty seconds. I hastily uninstalled Mixzing, only to find that every music player I try now produces the same result. Has anyone else experienced this? How would you go about troubleshooting without reverting to your last backup, if possible?
Yes, I powered off the phone and turned it back on after the uninstall -- multiple times in fact. I've been working ever since and could only now return to this site. Has anyone else encountered this problem? Does anyone have the slightest idea what might cause it?
And now, of course, my soundfiles are playing normally (though I can't check FLAC with the stock player). Two nights of reboots and charges and only now, for whatever reason, is my music player behaving. Something I've noticed: the phone seems to be calling up the Amazon mp3 app and Pandora to do searches for the music I'm already playing. Could the combination of forced searches and Juice Defender/Task Killer have caused the force quits? Mixzing is a pushy, ad-mounting app. I'm wondering whether Android is at all like Linux, and Mixzing created associations that are time-consuming to trace and eradicate.
