You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just throwing this here to address Play Store visibility once this policy becomes enforced.
Targeting a higher API becomes quite difficult in the way XMP Android works, since the biggest feature set is the file browser.
Android Scoped Storage (SAF) is... well... terrible and limits the heck out of app access on mobile devices. I've looked into this time and time again to figure out a good way to adapt XMP Android in my fork, but I cant find a nice solution to it without getting rid of the browser and limiting modules to be downloaded in the Downloads or Music folder.
There is private storage for the app using Scoped Storage, but that is only visible to the app itself and everything in it will be deleted if the app is uninstalled for whatever reason.
I believe you can make sub folders in Scoped folders, so maybe something can be done about keeping modules in a tidy spot, but if they go in music, some music players look at mimetypes in that folder and most modules (on my phone) tend to identify as application/octet-stream which is pretty much a wildcard for lots of apps.
Also the app will pretty much need to be adopted to mimic an actual media player; more and more, to use some of the new feature sets Android is releasing every year (Cast, Android Auto, New MediaBrowserService, etc)
Edit for some notes to look into whenever I get back into this:
https://android-developers.googleblog.com/2022/04/expanding-plays-target-level-api-requirements-to-strengthen-user-security.html?m=1
Just throwing this here to address Play Store visibility once this policy becomes enforced.
Targeting a higher API becomes quite difficult in the way XMP Android works, since the biggest feature set is the file browser.
Android Scoped Storage (SAF) is... well... terrible and limits the heck out of app access on mobile devices. I've looked into this time and time again to figure out a good way to adapt XMP Android in my fork, but I cant find a nice solution to it without getting rid of the browser and limiting modules to be downloaded in the Downloads or Music folder.
There is private storage for the app using Scoped Storage, but that is only visible to the app itself and everything in it will be deleted if the app is uninstalled for whatever reason.
I believe you can make sub folders in Scoped folders, so maybe something can be done about keeping modules in a tidy spot, but if they go in music, some music players look at mimetypes in that folder and most modules (on my phone) tend to identify as application/octet-stream which is pretty much a wildcard for lots of apps.
Also the app will pretty much need to be adopted to mimic an actual media player; more and more, to use some of the new feature sets Android is releasing every year (Cast, Android Auto, New MediaBrowserService, etc)
Edit for some notes to look into whenever I get back into this:
https://commonsware.com/blog/2021/11/06/about-environment-undeprecations.html
https://developer.android.com/training/data-storage/use-cases#if_your_app_targets
The text was updated successfully, but these errors were encountered: