What you need to know
- Google removed the manual search button in March, frustrating users when automatic detection failed.
- The latest update to the Now Playing app restores the “Tap to see what’s playing” option.
- The button triggers cloud search, allowing broader and more accurate song identification.
If you have a Google Pixel, you’ll probably agree that Now Playing is one of those features that makes it hard to switch to another phone. It feels great to look at your lock screen and immediately see the name of that obscure indie song playing at the coffee shop, without having to do anything at all.
But recently, Google made a change to the interface that left many users confused. When The standalone Now Playing app launched in March, removing the manual search button, the one tool you need if automatic detection isn’t working.
The good news is that Google listened. A new update is rolling out now that brings back the “Tap to see what’s playing” prompt on the lock screen. reddit user noticed (through) 9to5Google).
Article continues below
Offline recognition is great – until it isn’t
For starters, Now Playing uses a database on your phone to identify songs, which helps protect your privacy and saves battery. However, since this database only includes a limited selection of popular tracks, it often misses less common songs. The manual search button helps with this by launching a cloud-based search that can identify almost any song.
The latest version of the Now Playing app puts the manual search tool back on the lock screen immediately after your phone no longer recognizes a song automatically.
Other than that, 9to5 didn’t notice any major changes after the update. This probably means the release is mostly about background improvements rather than new features.
You can expect this update to reach all compatible Pixel devices in the next few days. It’s a small step in the right direction, but for those who love discovering music, it’s the best update this month.
Android Central’s Tech
Honestly, I’m glad Google finally fixed this, but we shouldn’t be causing an uproar just to save a basic feature from being removed. It’s disappointing to expect to celebrate the return of a button that should never have been taken away. This sounds a bit like asking someone to thank you for returning your wallet when half the money is gone.
