Music app doesn't play any audio at all.

[Angutivik Casper Rúnur Tausen Hansen]

I am not sure what is causing this, but I will give as much information I can give.
The music app loads and all, and lists all the audio as it should, no problem there. I tap the audio file and it doesn't play at all. At the first end it shows 0:00 but also on the other end, which has kept me wondering. It also doesn't show the song title, artist, etc, and it just gets black in that area. To me it stopped working after a certain update, but I cannot remember which one and when, besides that Ubuntu Phone was pretty much in its early stages, and we only had BQ Aquaris E4.5 on the market.

I have all my files on the SD card, and it seems to me that it's not only the music app that has problems with loading from the SD card, but I will report that on each app.
I'm using Aquaris E4.5, and I just updated today (28/01/2016) to OTA-9.

I have attached a picture of the problem.

[Victor Thompson (vthompson)]

Hi, thanks for taking the time to file this issue and for making Ubuntu better!

Could you provide the following log files so we can get a better idea of what might be happening:

/home/phablet/.cache/upstart/application-click-com.ubuntu.music_music_*.log
/home/phablet/.cache/upstart/mediascanner-2.0.log
/home/phablet/.cache/upstart/media-hub.log

Thanks!
Victor

[idhir MADJOUR (idhir-madjour)]

Hello,
I currently facing the same issue as Angutivik.
 I've download CuteSpotify and it works.
I will try to provide you with the file as soon as coming home (at work can not plug my phone to my computer :( ).

[Domingo Pinho (domingospinhoo)]

I'm having the same problem on my BQ 4.5.
I was reading another reported bug
https://bugs.launchpad.net/music-app/+bug/1424309
and it's true the problem is caused when the title of a song is #

[Domingo Pinho (domingospinhoo)]

Here's the test where I started by playing music and then tried to play a song with the problem of #

[Andrew Hayzen (ahayzen)]

The problem of playing songs which contain a '#' is bug 1449790, and any discussion for that bug should occur there.