I read that template and I think I’m doing everything correctly but im still not getting logs, here is a video of exactly what I am doing https://imgur.com/a/0ayjr25
And strangely no missing log error you stop the video too soon, you maybe have an error saying file too big, or something. The link also explains all that and manual upload
.
I use crDroid. I reinstalled like 5 times already. Also the error did not appear as I was recording the app only. I send the matlog if that somehow helps with why symphonium cant store logs.
If there’s no access to that folder then yes no logs and no image cache, but this is not something I can anything about, it’s the OS blocking or bugging. You need to see with cdDroid what those error means,
I tried whatnot since i have root acess but I didn’t manage to get it working. And im not saying its symphonium but this is the only app I have this issue with. I don’t see any crDroid support forums so idk what to do anymore. If you have any ideas on what I can try I will try them out.
/storage/emulated/0/Android/data/<package>/files is the app’s own app-specific external directory, and Android says the app should be able to use it without requesting storage permissions, as long as external storage is mounted. getExternalFilesDir() is the correct API for that.
Your log shows the failure happens inside the framework path creation call:
ContextImpl.getExternalFilesDir()
StorageManager.mkdirs()
IStorageManager.mkdirs()
That means the app is asking Android correctly, but the system is refusing or failing to prepare the directory.
Most likely cause
On a custom ROM like crDroid, this usually points to a broken storage state on that device/user, not to missing app code. The strongest clue is that the system itself throws IllegalStateException: Failed to prepare .../Android/data/<package>/files. A plausible cause is a stale or mis-owned existing folder for that package, often after restore/reinstall/signature changes, or a ROM bug in FUSE/app-data isolation. That exact failure pattern has also been reported on custom-ROM devices where one device works and another does not.
Practical fix for the user
Try these in order:
Reboot the device
External storage state can get stuck. Android’s docs say app-specific external storage is only usable when the volume is mounted.
Clear app storage, uninstall the app, reinstall it
Delete the stale external app folder before reinstalling
Remove:
On newer Android versions this is often blocked for normal file managers, so the reliable ways are:
root shell, or
recovery, or
adb shell with elevated privileges on a rooted/debuggable buildExample:
adb shell
su
rm -rf /storage/emulated/0/Android/data/app.symfonik.music.player
Then reinstall the app.
This is the highest-probability fix if the folder exists with the wrong owner/metadata.
4. Test in a new Android user/profile
If it works there, the primary user’s storage metadata is corrupted. That exact pattern has been observed in similar reports.
5. If rooted, fix ownership/labels instead of only deleting
adb shell
su
ls -ld /storage/emulated/0/Android/data/app.symfonik.music.player
If ownership/SELinux labeling looks wrong, deleting and letting Android recreate it is better than manual mkdir.
Ok, so I did try to remove the folder (which doesnt even exist ls: /storage/emulated/0/Android/data/app.symfonik.music.player: No such file or directory), and even tried making it with media_rw user and groups with 771 permissions. That did not work. But what did is a different user. This is definitely not a issue with symphonium, but if you are willing to help then thanks. If not I’m probably going to figure it out. But once I fix this im probably buying the app. Thanks!
