My new Lumia 520 puts occasional momentary pauses into music playing from a MicroSD card.
Yesterday I opened a thread on this blaming Bluetooth but I've deleted that as I was mistaken and the title was misleading; the Bluetooth works just fine from internal memory and it turns out all outputs (Bluetooth, headphone jack and speaker) are affected by the fault if the music's played from MicroSD. Sorry to cause any confusion.
So the symptom is: Music stops for about half a second then restarts, followed a fraction of a second later by another very short stop/start. This happens seemingly at random, and can occur a couple of times in a track, or not at all for a a few tracks.
I've checked more closely and the glitches, when they do occur, always happen at regular multiples of 66 seconds within any track (that suggests to me some kind of addressing/paging problem reading data from the card).
Glitches on the old phone's card show up at multiples of 64 seconds. Otherwise it's identical.
Any suggestions gratefully received.
Solved! Go to Solution.
Update: Had to nuke and pave, but it appears to be fixed.
Called my service provider and they put me through to Nokia who concluded I needed to try resetting the phone and starting from scratch.
It's been playing for the last half an hour or so with no glitches. Fingers crossed that's fixed it.
Well, another factory reset has not cured it, so it's going back.
Orange intend to attempt to repair rather than replace it, though I'm pretty sure it'll need replacing. I did initially report the fault within 14 days (as noted above) but Orange say they have no record of my call. I couldn't be bothered to argue.
I've got the exact same issue with a Lexar Mobile SDHC 32 Go class 10 card.
I don't think your phone is in cause there, as Lumia 820 also have issues with class 10 cards. I've read on these forums that we must use class 4 cards.
What class is your old card ?
My old MicroSD card is Class 2.
Both it and the Class 10 card play just fine in my old Nokia 6303.
Is your problem also with a Lumia 520 phone?
Today I received a return envelope to send my phone for repair, but I'm increasingly convinced this is not a hardware fault at all, so I'm in a quandary trying to decide whether to send it away or not. I'd probably just lose my phone for 2 weeks only to learn they can't find anything wrong with it. But if I don't send it, then I'd be relying on Nokia or Microsoft to come up with a firmware update to fix it and I can't find any way to discover whether this is a known fault that's being worked on.
I just checked the status of my repair, and the phone is being sent back to me: "No fault found."
That doesn't particularly surprise me, but how do I resolve this problem now?
S.B.E., on behalf of EE, on behalf of Orange, couldn't find anything wrong with my Nokia's hardware. But I never really thought the problem was the hardware at all, I'm increasingly convinced the problem is that Microsoft's OS just isn't very good at handling SD cards.
What should I do? Ask Orange to take it back and give me a Samsung instead?
Thanks for the suggestion, rambosaha. I've seen various comments suggesting Class 6 cards may work more reliably than faster or slower cards. It's a pity they're rarer than other classes; shops only seem to stock Class 4 and 10 cards.
If I could be sure it would work, I might buy a larger Class 6 card, 32 or 64GB, but that still seems a bit risky and I'm not keen on throwing good money after bad.
I don't suppose you've found any announcement by Nokia stating what type of cards they recommend, have you?
I looked up the definition of the different classes of card, and it seems to be a bit more complicated than I thought.
Classes 2, 4 and 6 define a minimum sustained write speed even with fragmented storage. Class 10 defines a faster write speed, but only for a non-fragmented card.
Also, it appears not all cards of the same class are equal;
"The speed class rating does not totally characterize card performance. Different cards of the same class may vary considerably while meeting class specifications. In addition, speed may vary markedly between writing a large amount of data to a single file [...] and writing a large number of small files (a random access use common in smartphones)."
It looks like what we need is an approval list of specific cards.
So far I can say a Hama 16GB MicroSDHC Class 10 ain't on the list.
Congratulations on fixing your problem. I wish I could say the same.
I pinned my hopes on a new MicroSD card that was specifically supposed to work well with smartphones: A SanDisk Mobile Ultra microSDHC 32GB. The packaging proudly announces: "Works with Windows Phone".
Still keeps doing the same glitching trick.
In fact it's decided to throw a few more problems in just for fun. Most songs appear twice in the track list. When I started to test it, it played a couple of tracks then stopped. When I switched on the phone to see what was happening, it started again. At the end of the next track it stopped again, and I couldn't turn the phone on again until I'd removed the battery. Now there are 3 copies of most songs. Having played a dozen tracks or so with occasional glitches it just stopped dead in the middle of a song.
I won't bore you with the rest but I've just reset the phone using the Volume Down and Power buttons. Instead of fixing a problem, I appear to have created a flakey, unstable monster.
Can't wait to see what happens next.
Now it's decided there are 4 copies of each of those songs.
Windows Phone 8 will probably be really nice, when it's finished.
Thanks for the warning Kenny. Much appreciated.
When it decided I now had 5 copies of each song, I'd had enough and reformatted the MicroSD card.
Then I reloaded my music but this time instead of synching it to the phone using Windows Media Player, I took the card out of the phone, plugged it into my PC and dragged and dropped my iTunes library folder contents into the Music folder on the card. Last time I did that it didn't start creating multiple phantom files and it looks as if that has worked again this time.
Hasn't stopped the random pauses though.
I think the next logical step must be to ask Orange to replace the phone.