Can't use images or audio with messanger apps after upgrading from v9.15 to v11.0 (browser works fine)

[fredi-python]

Issue type

Other

Device

vayu

crDroid version

crDroid 11

Exact version / Build date

crDroidAndroid-15.0-20241216-vayu-v11.0
and
crDroidAndroid-15.0-20250112-vayu-v11.1

Bug description

I recently upgraded it from android 13 (crDroid 9.15) to android 15 (11.0), now I cant send or receive media files (Images, Audio and Video) in messaging apps. It works fine in firefox though.

I can only see a very very blurred preview from whatsapp, like when you don't download the image.

Errors I found in MatLog:

[CODE]Failed to set project id on /data/media/0/Android/data/com.whatsapp/: Operation not supported on transport endpoint

and

StorageManagerService(1728): Failed to fixup app dir for com.whatsapp[/CODE]

For me this looks like either whatsapp can't write to the external storage, even though it has the permissions, or the ROM upgrade messed up my directory structure.

I have already flashed the most recent recovery image too. I also reflashed the ROM a few times, but it didn't fix the issue.

I used TeamWin, before I flashed the latest crDroid recovery.

Tried to use

• crDroidAndroid-15.0-20241216-vayu-v11.0

and

• crDroidAndroid-15.0-20250112-vayu-v11.1

Another thing I noticed when I used TeamWin, on my second flash (with 20250112 build) there were some mount errors, I think "cannot mount /vendor" and something with an mtp or similar, but the ROM still flashed successfully (at least booted good)

With the new recovery, there were no errors like that, but I still can't receive media files

Thanks in advance,

Fredi

Steps to reproduce

Descrbed in the bug description

Relevant log (logcat/build log)

Failed to set project id on /data/media/0/Android/data/com.whatsapp/: Operation not supported on transport endpoint

StorageManagerService(1728): Failed to fixup app dir for com.whatsapp

Screenshots or videos

No response

Solution

No response

Additional context

No response

Acknowledgements

• I've checked device is officially supported (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device
• I have searched the existing issues and this is a new and no duplicate or related to another open issue.
• I have written a short but informative title.
• I filled out all of the requested information in this issue properly.

[gwolf2u]

was this a clean flash?

[fredi-python]

It was a dirty flash (I didn't wipe any data).
I was searching for how to upgrade to a newer crDroid version, so dirty flash seemed to be the easiest.

[gwolf2u]

Clean flash needed
We don't support upgrading through major revisions

[fredi-python]

Can I do a backup so I dont need to reinstall all the APPs?

[gwolf2u]

Not really
Unless you want to backup via some root apps, but even that is not full backup

[fredi-python]

Ok sad, do you think there will be problems if I downgrade again? Or should that work fine?

[gwolf2u]

Downgrade not possible
Anyway, this is getting off topic now

[fredi-python]

OK, thanks for the reply though

[ossilator]

in fact, crdroid includes seedvault backup, which you can store on internal storage, and restore either in the first start wizard, or later. unless either of your crdroid builds is sufficiently botched.

of course, there is a risk that the backup preserves exactly the setting that causes the problem.