IssueRaiser

In the link #440 reports that disabling "NuPlayer" fixed the issue.

In the link #440 reports that disabling "NuPlayer" fixed the issue. This setting is in Settings > Developer options under "Media". I've also found that NuPlayer plays unpredictable havoc with an audio playing app I wrote that is currently on Google Play. Some users on Lollipop report audio glitches, silence or weird bluetooth issues. Disabling NuPlayer fixes these issues. I wish there was a way for me, as a developer, to force use of the old AwesomePlayer system for my app in particular, but have no idea if this is possible technically. I certainly haven't found a way to do it. But what I find surprising is that NuPlayer is labelled "experimental" in Developer options but is enabled by default . Isn't that a bit weird?

Posted by gabemart on Jan 16, 2015, 2:44 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.8,000 issues0 comments

complaint (SaaS)

In the link #440 reports that disabling "NuPlayer" fixed the issue.

gabemartJan 16, 2015, 2:44 PM

In the link #440 reports that disabling "NuPlayer" fixed the issue. This setting is in Settings > Developer options under "Media". I've also found that NuPlayer plays unpredictable havoc with an audio playing app I wrote that is currently on Google Play. Some users on Lollipop report audio glitches, silence or weird bluetooth issues. Disabling NuPlayer fixes these issues. I wish there was a way for me, as a developer, to force use of the old AwesomePlayer system for my app in particular, but have no idea if this is possible technically. I certainly haven't found a way to do it. But what I find surprising is that NuPlayer is labelled "experimental" in Developer options but is enabled by default . Isn't that a bit weird?

Comments (0)

No comments yet. Start the discussion.

Comment on this issue