iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Most Android music-player failures have a specific cause: the app lacks permission to read audio, the files are outside its indexed storage, artwork metadata is missing or unreadable, or Android is stopping background work. Work through those causes in that order, then check the player’s media-session and battery settings.
Start with the symptom
| What you see | Most likely cause | First action |
|---|---|---|
| Songs are present in a file manager but absent from the player | Missing or revoked audio permission, an unindexed folder, a .nomedia marker, or inaccessible SD-card storage |
Check the player’s Music and audio/Audio permission, then rescan its library |
| Tracks play but album covers are blank | No embedded image, an inaccessible image path, or unusable artwork metadata exposed by the player | Inspect the file’s embedded cover and the player’s artwork settings |
| Music stops when the screen locks | Battery restrictions, a manufacturer sleeping-app rule, unused-app optimization, or inadequate background playback handling | Set the player’s battery mode to Unrestricted and review sleeping-app controls |
Change one setting at a time and test with a single known-good track. That makes it clear which fix worked and avoids rebuilding a library unnecessarily.
When Android cannot find songs that are on the phone
1. Grant the correct media permission
Android 13 and later use granular media permissions. An app targeting the newer Android API level must request READ_MEDIA_AUDIO when it needs to read audio files created by other apps. The older assumption that one broad storage permission covers every file is no longer reliable.
Open Settings > Apps > [your music player] > Permissions. Look for Music and audio or Audio; wording differs by Android release and phone manufacturer. Set it to Allow. If the permission is listed as denied, allow it and reopen the player. If Android presents a separate media category, grant the audio category rather than only photos or videos.
#1 Best Overall
- Compatible with Nintendo-Switch (NOT Nintendo-Switch 2)
- Expand your storage in a flash: ideal for Android smartphones and tablets, Chromebooks, and Windows laptops.
- Increase your TV show, movie, and Full HD video[4] recording collections dramatically with up to a massive 1.5TB[1].
- Transfer files fast with up to 150MB/s[2] read speeds and SanDisk MobileMate USB micro 3.0 microSD card reader[6].
- Load apps faster with A1-rated performance[3].
Android Developers specifically requires apps targeting Android 13 or higher to request the granular media permissions instead of relying on READ_EXTERNAL_STORAGE. A player that has not adapted its permission flow may show an incomplete library even though the files remain intact.
2. Reopen the app and rescan its library
- Open the recent-apps view and swipe the music player away, or use Settings > Apps > [player] > Force stop.
- Launch the player again.
- Open its library, media folders, or storage settings and choose Rescan, Refresh library, or the equivalent command.
- Wait for indexing to finish before judging the result. Large libraries and SD cards can take several minutes.
Granting permission does not guarantee that a player immediately reruns its media scan. A manual refresh after reopening the app is therefore a separate step.
3. Confirm that the files are real, readable, and in an indexed folder
Use a file manager to verify that the tracks still exist and can be opened. Check the filename extension against the formats your player supports; a file that is renamed to look like an audio file is not necessarily playable. Also check whether the music was moved into a private app folder that the player cannot read.
Android’s media scanner can skip an entire directory when that directory contains a file named .nomedia. The marker is normally hidden, so enable hidden files in the file manager and inspect the music folder and its parent folders. Remove the marker only when you intentionally want Android and music apps to index that directory; some apps place it there to keep private audio out of shared media libraries.
After correcting the location or marker, run the player’s rescan again. If the player offers a folder-selection screen, explicitly add the directory containing the tracks instead of relying on automatic discovery.
4. Check removable storage and SD-card access
For music stored on a microSD card, open Settings > Storage and confirm that the card is mounted. A card that is listed as unavailable, still being prepared, or mounted read-only cannot be indexed normally. Remove and reinsert it only after unmounting it through Android’s storage controls when that option is available.
Storage permissions can restrict access to mounted storage and SD-card content. If the player has a folder picker, use it to grant access to the card’s music directory, then rescan. Test one track from internal storage as well: if internal tracks appear but SD-card tracks do not, the problem is access to the card or its mount state rather than the audio library itself.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Do not format an SD card as a first troubleshooting step. Formatting destroys its contents. Copy the music elsewhere and verify the backup before taking any action that erases or re-partitions the card.
Rank #2
- Compatible with Nintendo-Switch (NOT Nintendo-Switch 2)
- Ideal storage for Android smartphones and tablets
- Up to 128GB to store even more hours of Full HD video (1GB=1,000,000,000 bytes. Actual user storage less. Full HD (1920x1080) video support may vary based upon host device, file attributes, and other factors. See official SanDisk website.)
- Up to 140MB/s transfer speeds to move up to 1000 photos per minute (Up to 140MB/s read speed, engineered with proprietary technology to reach speeds beyond UHS-I 104MB/s, require compatible devices capable of reaching such speed. Based on internal testing; performance may be lower depending on host device, interface, usage conditions, and other factors. 1MB=1,000,000 bytes. Based on internal testing on images with an average file size of 3.55MB (up to 3.7GB total) with USB 3.0 reader. Your results will vary based on host device, file attributes, and other factors.)
- Load apps faster with A1-rated performance (A1 performance is 1500 read IOPS, 500 write IOPS. Based on internal testing. Results may vary based on host device, app type, and other factors.)
5. Check whether Android revoked the permission later
Android can optimize apps that have not been used for a long time. Google’s Android Help says this process can revoke app permissions and stop an unused app from running in the background. Revisit Settings > Apps > [player] and inspect Unused apps, Pause app activity if unused, or a similarly named control. Disable the pause or optimization for a player you use regularly, then confirm that its Music and audio permission is still allowed.
When album art is missing but songs play
Playback and artwork are separate data paths
A track can decode and play even when its cover is blank. Android media controls display artwork supplied by the player as metadata, including the METADATA_KEY_ALBUM_ART_URI field. If the audio file has no embedded image, the image path is no longer readable, or the player fails to expose usable artwork metadata, playback can continue without a cover.
This distinction prevents a common mistake: changing audio permissions or reinstalling the player when the files themselves are already playing correctly.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallInspect embedded artwork first
- Open the track’s details in a tag editor or file manager that can display embedded metadata.
- Check whether the file contains a cover image and whether the image can be exported or viewed.
- Compare two files from the same album. If only some tracks lack art, those files may have been encoded or tagged without an embedded image.
- If the image is present but the player remains blank, continue with the player’s cache and artwork settings rather than editing every file.
Embedded art travels with the file and is available offline, but it increases file size and can be missing after a conversion or tag-cleaning operation. An image downloaded by the player is separate and may disappear when its cache is cleared or when the app cannot reach its artwork service.
Check the player’s artwork options
Look in the player’s settings for options such as Show embedded artwork, Download album art, Prefer local art, or Use folder images. Enable the option that matches where your collection’s covers are stored. If online artwork is enabled, the player may need network access and a correctly tagged artist and album name to find a match.
Clear an artwork-only cache if the player provides that control, then run its artwork refresh. Avoid clearing the entire app’s data until you have verified that playlists, ratings, and custom settings are backed up; a full data reset can remove local app state even though it does not remove music files stored elsewhere.
Understand what a replacement player must expose
If artwork works in one player but not another, compare how each app handles embedded images, local image files, and downloaded art. Also check whether it publishes artwork through Android’s media-session controls. A player that displays a cover only inside its own screen but does not provide metadata to the lock screen, headset controls, or car display has incomplete media-session integration for those use cases.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhen playback stops after the screen locks
Remove battery restrictions
Samsung Support warns: “If music apps on your phone or tablet are not allowed to run in the background, your audio may stop if the phone or app goes to sleep.” The same class of restriction exists under different names on other Android devices.
Rank #3
Open Settings > Apps > [music player] > Battery and choose Unrestricted when that option is available. Other devices may show Allow background activity, Don’t optimize, or a per-app background-use switch. Android and manufacturer menu labels change with software version, so use the app’s own Battery page rather than assuming that a global battery-saver switch controls it.
Unrestricted operation can increase battery use. Apply it to the player that must continue playing, not to every app, and retest with the screen locked for several minutes.
Remove the player from sleeping-app lists
Many manufacturers maintain a separate list of sleeping, deep-sleeping, or automatically managed apps. In Settings, search for sleeping apps, background usage limits, or app battery management. Remove the music player from those lists and disable any rule that automatically puts it to sleep.
Recommended Free Tools
Also review Android’s unused-app optimization. A player that is rarely opened can lose its permissions and background access again, recreating the failure after it appeared to be fixed.
Check media-session and foreground playback support
Android’s media architecture is designed for persistent playback through a MediaSessionService and a media-playback foreground service. These components let the system keep an active session, show lock-screen and notification controls, and resume playback after the display turns off. If a player does not maintain a proper media session or foreground service, aggressive process management can terminate it when the screen sleeps.
Use the player’s notification and lock-screen controls as a practical test. Start a track, lock the phone, and check whether a playback notification remains, whether pause and skip work from the lock screen, and whether the track resumes after a brief interruption. Missing controls do not prove that the app is defective, but they indicate weaker integration with Android’s media framework.
Separate screen-lock failures from network interruptions
Test a locally stored track before diagnosing streaming behavior. If local files continue playing but a stream stops, the issue may involve network handoff, data-saver rules, or the service’s own background policy rather than the audio player’s storage access. For this article’s local-library problem, use an uncompressed or otherwise known-good local file as the control test.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →A complete troubleshooting sequence
Follow this order so that each test isolates one layer of Android’s media stack.
Rank #4
- [NOT compatible with Switch2] Please note that this product is not a microSD Express card and is not compatible with Switch2 for game storage or save data. If used in the Switch2, it may only support limited functions such as storing screenshots or videos, but will not allow game installation or save file access.
- High compatibility for different types of devices including smartphones, tablets, Drones, Android Tablets, Tablet PCs, Action Cameras, DSLR and 4K or Full HD camcorder.
- Compatible with Nintendo Switch *In order to use a microSDXC card on the Nintendo Switch console, a system update is required.* See Nintendo official site for more details
- 5-year limited manufacturer warranty
- Identify the failure. Note whether tracks are missing, art is missing, playback stops only with the screen off, or several symptoms occur together.
- Check permission. In the player’s App permissions, allow Music and audio/Audio. On Android 13 and later, verify that the app has
READ_MEDIA_AUDIO-equivalent access. - Restart and rescan. Force-stop the player, reopen it, and run its library refresh.
- Verify the files. Confirm the tracks exist, use supported extensions, are not in a private or excluded folder, and are not covered by a
.nomediamarker. - Test storage. Confirm that internal storage works and that any SD card is mounted and accessible. Grant folder access when the player requests it.
- Fix artwork separately. Inspect embedded covers, then review local-art, downloaded-art, and cache controls.
- Fix background execution. Set the player’s battery mode to Unrestricted where offered, remove it from sleeping-app lists, and review unused-app optimization.
- Retest after locking the screen. Use a local track and verify that the media notification and lock-screen controls remain available.
If the player still fails after these checks, test the same files in another reputable player. Matching results across players point to storage, permissions, or file metadata; a failure limited to one app points to that app’s indexing, artwork, or background-service implementation.
How to choose a different Android music player
Do not choose solely by interface or codec list. The problems above are governed by Android permissions, storage access, metadata handling, and background services. Use this checklist when evaluating another player:
| Capability | What to verify | Why it matters |
|---|---|---|
| Android 13+ permissions | The app clearly requests and explains Music and audio access rather than depending on an obsolete broad-storage assumption | Without granular audio permission, a library can appear empty or incomplete |
| Folder and SD-card indexing | Manual folder selection, reliable rescans, and access to mounted removable storage | Automatic scanning may skip folders or lose access after a card is remounted |
| Artwork handling | Embedded-art display, optional online-art retrieval, folder-image support, and a way to refresh artwork | Playback can succeed even when artwork metadata is absent or unreadable |
| Background reliability | Persistent notification, lock-screen controls, and behavior under Android battery restrictions | Screen-off playback depends on background execution and media-session integration |
| Media-session integration | Playback controls and resumption through Android’s system media controls, headphones, or a car interface | A proper media session helps the system coordinate long-running playback |
Before moving a large library, copy a small test folder to the intended location and verify all five capabilities. This catches permission and indexing problems without forcing a full migration.
Free tools Windows power users keep installed
One-click scans. No signup required.
What the symptoms tell you
Only some tracks are missing
Selective omissions usually indicate different folders, a .nomedia marker, unsupported extensions, or files on storage the player cannot currently access. Compare the path and metadata of one visible track with one missing track.
The whole library vanished after an update
Check permissions first. An operating-system update or a change in the app’s target Android API can expose an old storage-permission assumption. Regrant Music and audio access, restart the app, and rescan before altering files.
Artwork disappeared after moving files
Moving a track can invalidate a player’s cached image path even when the audio remains playable. Refresh artwork and verify that the embedded image is still present. If the image was stored as a separate file, confirm that it moved with the music and that the player still indexes that folder.
Playback stops only after the phone sits idle
This pattern points to battery or sleeping-app management. Apply the player-specific Unrestricted setting, remove it from automatic sleep lists, and confirm that Android’s unused-app control is not revoking its permissions.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Quick Recap
Key takeaways
- On Android 13 and later, an old storage-permission assumption can leave a music player without access to audio files; verify granular Music and audio access.
- A rescan cannot find files hidden by
.nomedia, stored outside indexed folders, or located on an unmounted or inaccessible SD card. - Album art is metadata delivered by the player through Android’s media framework, so blank covers do not necessarily indicate damaged audio.
- Screen-off playback depends on battery policy, sleeping-app controls, unused-app optimization, and proper media-session foreground playback.
- When replacing a player, evaluate permission handling, SD-card indexing, artwork support, and background media controls together rather than judging the interface alone.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
