Chances are that the new music just is n’t there. You wait a few moments. calm nothing. You wait a couple of minutes. No messages. nothing. So you go off and make a cup of tea, mulling the consequence over. When you get back, ten minutes belated, the new music is magically in the library – it quite literally pops up in the listings.
here ‘s my walkthrough and explanation :
In my old-school case, it was a matter of going into Storage Sense and tapping on the ‘SD card ‘ line …
Swiping to the bottomland reveals the ‘remove SD tease ‘ option. Tap this to eject the wag from the OS ‘s file system – much safer than equitable yanking it out !
curious to see what would happen if I tried playing music ( which was hush listed ! ) with the poster removed, I got this error. Unsurprisingly. [ good ] interim, I had copied on a booklet of a classic ‘King Crimson ‘ album and had turned the call ‘s filmdom back on. Looking here in XBox Music, the new album is nowhere to be seen. I waited. And waited .
After around seven minutes, during which the list refreshed several times, sometimes with space results, the final tilt was displayed, complete with the new music .
What ‘s obviously happening is that at some point the microSD card gets re-scanned for music files ( and their ID3 or Windows Media properties ). I would n’t have thought ( even with my 32GB batting order of media ) that it would take seven minutes though, so I suspect that one of Windows Phone ‘s beloved background agents is tasked with the music side of things, feeding results back into XBox Music ‘s database.
As you ‘ll know from early AAWP content, these background agents run with some restrictions on context ( e.g. whether the battery is > 50 % and/or on charge ), processor cargo and run time. so in the case above, at the following time the agent ran, in the background, the new music files were picked up and index. indeed, by the fourth dimension I got back with my cup of tea, all was well .
I do remember in the earlier days of Music on Windows Phone that a pop fly did exist, warning the exploiter that indexing.scanning was happening, but this was all shifted to the background in an update in July, as a cleaner, more foolproof way to proceed. Well, foolproof unless you ‘re an impatient geek wondering why the newfangled files have n’t been looked at yet in the foremost few minutes ! !
have this always frustrated you excessively ? personally, I think a pop fly in Action Center explaining that scanning was taking invest would help. Comments ?