Jump to content

"Failed to play file" after updating to Android 13 / OneUi 5


artacar
 Share

Recommended Posts

Hello,

Poweramp build number: build-945-bundle-play [945004-2d535bbf]
Device model: Galaxy A52 5G
Android version: 13 / OneUI 5.0

After updating my phone to Android 13 / OneUI 5.0, I am unable to listen to any music on my phone using Poweramp, and I am getting a "Failed to play file" error on almost every file (which consists mostly of FLAC files). Other music players working fine, and playback worked fine using Poweramp before updating to Android 13 / OneUI 5.0

What I have tried:

  • clearing the app data 
  • re-add the music folder with giving permissions
  • create a new folder and put all music in the new folder
  • uninstall and reinstall app
  • reboot the phone
  • verify that all permissions granted to the app in Android settings
  • turn on "File Access Legacy Mode"

Nothing of this has changed anything. Is there something else I am missing, or this is a bug?

Link to comment
Share on other sites

Same boat here, as shown in this link. Library seems to read the files, and other players do play them properly, but Poweramp won't seem to for whatever reason.

I tried some older versions of Poweramp too, to see if that'd make a difference, but unfortunately not.

 

Poweramp build number: build-945-bundle-play [945004-2d535bbf]

Device model: Galaxy S21 Ultra

Android version: 13 / One UI 5.0

Edited by Larry 609
Link to comment
Share on other sites

So both of you are experiencing the same thing - you can adjust the Settings=>Library=>Music Folders option to point to the folder or folders that contain your music (not to a root location) and you can grant access to them. Then songs are properly scanned into the Library - i.e. you can see all the Titles, Artists, Albums, song-durations, cover art, etc. But when you try to tap on any of those songs from a category list such as 'Folders' or 'All Songs', none of them will play? And you've also tried using File Access Legacy Mode?

And it was working fine before the Android 13 upgrade occurred? Have you both tried reverting Poweramp to its default (just-installed) options for Android 13, which could be done by deleting app data, and letting it re-scan? (I see @artacar has already done this)

What happens if you long-press on any song in the list and select Info/Tags, do you see the correct path details and tag info?

Andre

Link to comment
Share on other sites

3 hours ago, andrewilley said:

So both of you are experiencing the same thing - you can adjust the Settings=>Library=>Music Folders option to point to the folder or folders that contain your music (not to a root location) and you can grant access to them. Then songs are properly scanned into the Library - i.e. you can see all the Titles, Artists, Albums, song-durations, cover art, etc. But when you try to tap on any of those songs from a category list such as 'Folders' or 'All Songs', none of them will play? And you've also tried using File Access Legacy Mode?

And it was working fine before the Android 13 upgrade occurred? Have you both tried reverting Poweramp to its default (just-installed) options for Android 13, which could be done by deleting app data, and letting it re-scan? (I see @artacar has already done this)

What happens if you long-press on any song in the list and select Info/Tags, do you see the correct path details and tag info?

Andre

After I deleted the app (and data), I reinstalled and selected the usual Music folders. I'm not sure of the difference between that and the "root" location, but I chose the usual one like normal. I had tried using an alternate location earlier today, but it didn't fix the issue.

After Rescan, the # of folders/playlists/songs show up under the correct numbers. However, when I go to the song view, it does not list the artist name, album art or length of the tracks... just the song titles. When I try clicking on a song, it'll show the "Failed to Play File!" quote before going through a few songs the same way, and then automatically stopping.

The long-press appears to show the proper locations (mine would be something like "primary/Music/My CDs/Various Artists/(Album)/(Song).mp3"). Hitting the file folder icon next to it also brings me to the proper file location in the phone.

It was working perfectly fine before the Android 13 update. It was only after the update was implemented that the problems started.

The FIle Access Legacy Mode has been chosen, but does not work, unfortunately.

Edited by Larry 609
Link to comment
Share on other sites

Update: The music files finally show up after going through the "File Legacy" option properly. I went into the Library's music folders, as you said, and selected the "Music" folder again... just under Internal Storage "File Access Legacy Mode" instead of the second one listed, which was selected the first time I started the app.

I'm still unable to import the prior library/settings files though, which are located within that Music folder too. But the good news is that the files are showing up and playing again!

Link to comment
Share on other sites

Yes, using the 'Music' folder is fine. What Android 11+ does not allow is selecting the whole of your storage area (i.e. without choosing any particular folder). I tend to set up my own 'Audio' or 'My Music' folder so I can avoid the default Music folder, as that system folder has a few minor restrictions placed upon it (e.g. you can't put a .nomedia file in it). But for most uses, 'Music' is fine.

The initial/ Full scanning process is in two halves. First PA crawls through the subdirectory structure of any folders you have designated, finding all of the contained music files. This is quite quick, probably just a few seconds. Then the longer phase two tries to access each one of those found files and read the tag metadata (Title, Artist, Album, etc). This may take several minutes, or even longer with large libraries.

If phase one worked, you will at least see the filename for each found song file. If phase two also worked (i.e. the contents of the files are properly accessible) you will see all the extra metadata information (Artist, Album, etc) instead of just the filenames. It sounds in your case like the directory crawl is working, but the files are not available via Android's Storage Access Framework for reading.

Andre

Link to comment
Share on other sites

  • 1 month later...
On 12/8/2022 at 4:02 AM, Larry 609 said:

Update: The music files finally show up after going through the "File Legacy" option properly. I went into the Library's music folders, as you said, and selected the "Music" folder again... just under Internal Storage "File Access Legacy Mode" instead of the second one listed, which was selected the first time I started the app.

I'm still unable to import the prior library/settings files though, which are located within that Music folder too. But the good news is that the files are showing up and playing again!

Thanks Larry 609, this worked for me! I did already try something like this before but dit not select the right directory under internal storage (with the legacy option). Make sure to de-select the other directory to avoid double files that still don't work.

Link to comment
Share on other sites

I wrote a longer reply about a month ago, but it didn't get posted for some reason. The solution provided by @Larry 609 worked (thanks!) for making it work like before the Android 13 update.

For me it's unclear why it only works with the legacy mode (while other music apps work out of the box), and given the note on this option which says "The file access legacy mode won't be supported in the future versions of Android" this seems like only a temporary fix - until a future Android update breaks it. So I would wish there was a way to understand what is wrong with the "non-legacy" option.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...