An "chown -R media_rw:media_rw /home/nemo/android_storage/* seems to have fixxed it for me. But i also have no idea if this breaks other things - does anyone know how the permissions are on new installed devices?
Folders and files have been owned by “nemo:nemo” before.
I have no idea how this could affect the “Gallery” function in telegram/signal.
2 Likes
I’m having the same problem on an XA2. Changing permissions on android_storage didn’t help. Can’t see any Gallery images from Android apps like Signal.
Edit: ownership change fixed the problem after a reboot.
2 Likes
having this exact problem. is there an official resolution yet?
permissions change + reboot did not work
I do not have these problems on my XA2. But, mine is a new install, never updated before. yours seems older because of user nemo.
On my XA2 your change is the default. What ist now the directory itself? 770 oder 775? would be intressting to know.
root@Sail02:/home/defaultuser# ls -l | grep android
drwxrwx— 15 media_rw media_rw 4096 Jul 1 23:08 android_storage
yes its an “old” X10 - should be around one year.
The folder is:
drwxrwx— 16 media_rw media_rw 4096 May 31 09:32 android_storage
but I cannot tell you if i did modify this - but i think i only changed the user and group
Did you try changing user and owner with:
Yes, using “defaultuser” rather than nemo, as that directory doesn’t exist (X10 Plus in my case)
you could also try to delete your cache of the defaultuser.
$ rm -r /home/defaultuser/.cache/*
and reboot phone after this
To be honest, I had no issue like this after the deletion of folder I already mentioned. But still have one major issue - both external and internal SD card for Android apps outside their respective “Android/data & obb” folders are readable only…
will this mess with other configuration data? the first suggestion in the thread deletes all your android apps with no warning as to what it does
It is not harmful in this way, but a “mess” could be, that your system is much slower for a while, to regenerate some files.
will attempt and report back
okay so:
deleting .cache did not work
permission change did not work
deleting .android also did nor work.
rebooted after each fix attempt
factory reset attempted out of desperation. nothing installed until fully upgraded OS. problem persists.
Sorry to necro/repeat but i’ve tried a ton of stuff and still can’t get things working. No idea why a factory reset didn’t resolve the issue, but im at the end of my rope with this. Maybe it’s a problem with whatever the tracker equivalent in dalvik is, or with android permissions instead of file permissions? If I open android gallery i get this:
Could someone with it working again post the permission status of their android_storage folder and subfolders? What groups/users would be compatible with the aliendalvik 10 service in the first place?
If anyone here could pointe to some docs or resources on the subject or offer any other advice I’d really appreciate it.
UPDATE: yeah tried a second factory reset, and the apps can read from and write to android_storage again until I install and use either defender or MLS manager. After a reboot with those programs, it stops functioning.
1 Like
Hello @tkoham, everyone,
was there a solution to the issue after all? I experience the same issue since the update to 4.1. My best hope was that 4.2 “magically heals” the issue again. I admit, that approach did not work out.
The installation on my device is kind of antique: it only has account “nemo”, but no defaultuser. So it might boil down to some changed ownership / permission thing.
For me it seemed like an SD card issue.
I had the same symptoms, removed SD card, restarted Android and it began working. The SDcard in question was as incompatible as possible - cheap, vFAT formatted on ancient camera.
I suspect there is a setting somewhere “Use SDcard as primary storage” or similar.
Hi, there.
I have a problem with AD not showing SFOS multimedia files (just those from AD and SD card). Thought that there is an ownership problem, but after running the command:
chown -R media_rw:media_rw /home/nemo/android_storage/*
AD apps started to crash whenever they tried to reach any media files. Fortunately, before chown I’ve stored original permissions and could restore them.
So it seems that on Xperia10III with SFOS 4.5.0.24, ownership scheme changed to:
501023:appsupport-media_rw.
Not sure why user is some arbitrary number, more - directories created by some apps have even different ownership (like 501080:501080).
And nothing changes with my issue. Still AD shows only AD files what is really annoying.
Different apps behave differently. Since you didn’t name any, install Fossify Gallery and Fossify File Manager from your favorite Android App Store and see what works and what doesn’t.
Moving all your multimedia files to SD card is one solution.
Do you really need to open local multimedia files with Android apps instead of sharing from Sailfish? Usually the problem was the other way around: accessing android_storage with native apps, mainly (deleting) WhatsApp attachments.
I mentioned my issue just to show a background. Answering to your comment - any reference to media files crashed given app - all gallery managers (downloaded few) but also signal and telegram.
The main reason for posting was that things changed since this topic began, and using the information on recent SFOS may lead to make things even worse. Reference to most recent info on permissions at the moment is here:
in the “Android AppSupport is upgraded to Android 11” chapter:
Android AppSupport is upgraded to Android 11
OS release 4.5.0 contains a major upgrade of the AppSupport, from Android 10 to Android 11. This upgrade brings in modified and relocated app launchers, different access rights for the data directory of the apps, optimized apps, new app icons, and other changes.
When the phone has rebooted at the end of the OS update, AppSupport will start running a migration script transforming the Android apps for Android 11.