Pixel’s ‘Now Playing’ issues should now be fixed

For many Pixel users who rely on the handy “Now Playing” feature (it comes in so handy, so often), recent months have presented a frustrating experience. A once-reliable tool for music identification has been less-than reliable, leaving many a bit frustrated and concerned about the root cause and a potential resolution. Fortunately, Google has acknowledged the issue and confirmed that a fix is on its way.

The problem basically came down to inconsistent performance of Now Playing across the board. Users reported difficulties with both ambient identification failing to activate and manual search functionality becoming unreliable. One commenter even pointed out that they are “embarrassed to show this feature off to friends because most of the time it doesn’t recognize the song playing in the background passively, or the button doesn’t show up at all.”

In a recent update to the Issue Tracker thread on February 26th, Google stated that the Now Playing problems have been resolved, and the fix will be incorporated into an upcoming release. While the initial focus of the thread was on manual search issues, follow-up comments harped on the broader problems with ambient song identification, so it would seem that Google’s fix addresses the feature’s overall performance.

The exact timeline for this update’s rollout remains unclear, however there are anecdotal reports suggesting improvements in Now Playing’s reliability. Folks at 9to5Google have observed a recent uptick in the feature’s performance since the initial reports of issues surfaced. For what it’s worth, I haven’t noticed this issue at all, though I don’t heavily rely on the feature.

With Google’s confirmation of a fix, Pixel fans should anticipate a return to the consistent performance they’ve come to expect over the years with Now Playing. Though not a completely necessary thing to have on your phone, it has become a great tool over the years that should be working properly on a regular basis for Pixel users. It’s good to see Google own up to the issue and get it promptly fixed.