Thanks, but don’t spend too much effort on it, I don’t use the Google App Store anyway. 
For the time being, I’m ok.
All the files are in mp3 format, I can play them with the filemanager, which indicates the files are not corrupt. However, I can’t load them into both the players audio libraries. This seem to be a global issue and not limited to a certain audio player.
Where are they located, according to the file manager?
Update: I “assume” the following … the database for the music player still knows about the “old” location of the files, but the files are gone from that location (“upgrade to Koala Nut 1.8.7”), all you see are the “ghost” entries. Somehow you have to tell the Music app where to look for the files again and forget about the old paths. That what’s what I think could be the reason. Maybe there is something about this in the forum already, I have to look …
1 Like
I don’t want to undermine the search, but would like to add: I have never had any issue playing AAC files in the default MUSIC app. And MUSIC always found music files regardless of location. Right now my music files are in 2-3 different locations, both in the internal storage and the SD card.
Maybe there is a problem with Google Apps interference?
The files are located in “SD_root/Music”.
There are no “ghost entries”. The music player can’t see any files.
So both, VLC and Vanilla cannot play the files although you can “access” them? So you can go to “SD_root/Music” through their interfaces and choose a file, but not play it?
But in the File Manger selecting and playing a .mp3 works? I tried to understand what you mean with “load”.
I can select and play them with the internal filebrowser of Vanilla, but it can’t add the files to the music library. I can also play them with the standard Android filebrowser.
As I said, the mp3 files are present (no “ghost entries”) and not corrupt. The problem is, that all players I use are not able to add the files to the music library. If I scan the SD card for music from within any player, there seem to be nothing on SD card nor on internal memory.
Maybe there is a hardcoded search path for the SDs? Can the SD Card be remounted? I currently have a unofficial ROM on my FP1. The Music app there seems to automatically find my Music if mounted under /storage/. Is your SD_root also mounted under /storage?
Update: With vlc I can choose any directory to be included into the media library as long as I can access it. (Settings -> Directories).
Both, internal memory and SD card are mounted there. Internal memory “storage/sdcard0” and SD card “storage/sdcard1”
As far as I can see it, you tried all the know workarounds to reset the music app and there are no .nomedia files … Strange. Sorry, nothing more comes to mind here for now.
Maybe backuping & formatting the sd card and carefully moving just the mp3 files onto the card again for testing? Or just trying another empty card with just a few mp3 folders?
I have my music in subfolders of a folder Music in the root of the SD card on 1.8.7, which seems like the setup you have. No problems here, so it’s not a general issue - which means it should be fixable, whilst I agree you’ve tried the obvious database-related issues.
I’m nearly 100% certain you’ve tried this, but just in case:
[quote=“An_Mel, post:1, topic:10881”]
There are no “.nomedia” files present in the music folders.[/quote]
When using the built-in file manager, I’m assuming you have turned ‘show hidden files’ on. Are there any .nomedia folders in the root of your sd-card, or in any folder you need to go through to get to the actual music files? It seems the indexer doesn’t recurse into folders from the point where it encounters a .nomedia file. Might even be worth checking upwards from the mount-point.
I don’t have another SD card. I’ll backup my stuff and try the solution with the phone reset.
There’s another thing I noticed. With the previous version of Koala Nut the internal memory was mounted to my laptop when I connect the phone. Since the upgrade, only external (SD card) memory is mounted when I connect to the laptop.
The idea is just to have a clean SD to prevent hidden .nomedia files. No reset of the phone needed.
You can make your computer search for the .nomedia file:
Under Unix/Apple open a shell and cd to the mounted sd-card, run:
$ find . -iname “.nomedia” 2>/dev/null
Someone has an idea for windows? I think you can just use search, but you have to activate the feature that you can see “hidden” files.
I have the same issue with audio files on internal memory. I use Linux on my laptop.
Where you able to find “.nomedia” files on your SD card?
No, I did a full reset of the phone and formatted the SD card. The problem still persists.
So right now you have a “storage upgraded” FP1 (OS version “1.8.7”/Android 4.2.2) and music (as working .mp3s) on the fresh SD card without any .nomedia files. Strange. Right know I cannot think of anything else. 
I just reinstalled 1.8.7 on my phone again and copied 420 MB .mp3s to my SD card. It worked, the music is found, both in VLC and in the standard(?) android music app. I can even “see” how the new music gets updated in the player on the fly (Update: using MTP mode, btw). Strange.
@Johannes - is there something we overlooked? Broken upgrade? Will triggering a forced update with the Fairphone Updater change anything? I think not …
Are you using a first batch FP1 and did you apply the storage upgrade when you updated? After the storage updater the behaviour of the USB connection is different. To see the internal memory you will need to use MTP mode.
It may be worth a shot - the full reset seems to only wipe user data, so if something got stuck during the update a reset wouldn’t necessarily clear it.
These files were showing up normally before the update, right? So unless the indexer changed in the update (not sure how closely the indexer is linked to to the stagefright stuff that is addressed in the update), the files should still be capable of being indexed - i.e. they are all tagged with metadata in a format that the indexer can parse (when you play them via the file manager, artist and title should show up on different lines. If the filename is shown instead, then the metadata isn’t being parsed).
1 Like
This topic is old but I finally found a solution after playing around with the old FP1 because my dad needs a phone
The solution is to set the mp3 tags. The mp3 files had empty tags, that’s why they were not recognized. But I still can’t understand why they worked prior the software update.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.