WhatsApp media sharing and backup fail on Android 16

[arsalanbakal]

Issue type

Other

Device

OnePlus 7T (hotdogb)

crDroid version

crDroid 12

Exact version / Build date

12.11/2026-07-25

Bug description

WhatsApp has multiple media-related failures on crDroid 12.11 / Android 16.

Photos and videos cannot be sent or downloaded, WhatsApp Camera media cannot be sent, and WhatsApp chat backup fails.

The same issue occurs with multiple WhatsApp versions. Normal network connectivity, system Camera, Chrome downloads, Gmail sharing, storage capacity, WhatsApp permissions, and MediaStore access have been tested and work normally.

Relevant system logs show MediaProvider rename failures with EACCES and BadTypeParcelableException errors from UriGrantsManagerService during media sharing.

Steps to reproduce

1. Install crDroid 12.11 on OnePlus 7T (hotdogb) with GApps.
2. Install WhatsApp and grant the required Photos/Videos, Camera and Microphone permissions.
3. Open WhatsApp and try to send an image from the Gallery.
4. The message "This media doesn't exist on your internal storage" is displayed.
5. Try sending the same image as a Document; it also fails.
6. Try downloading an image received in WhatsApp; the download fails.
7. Open WhatsApp Camera, capture an image and try to send it; it fails.
8. Go to WhatsApp > Settings > Chats > Chat backup > Back up; the backup fails with "Unable to back up messages."
9. From Google Photos, select an image and share it to WhatsApp; the share also fails.
10. Reboot the device and repeat the tests; the issue persists.

Relevant log (logcat/build log)

MediaProvider:
Rename /storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Databases/msgstore.db.crypt14 to /storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Databases/msgstore-2026-09-05.1.db.crypt14 failed.

android.system.ErrnoException: rename failed: EACCES (Permission denied)

at libcore.io.Linux.rename
at libcore.io.ForwardingOs.rename
at android.system.Os.rename
at com.android.providers.media.MediaProvider.renameInLowerFs
at com.android.providers.media.MediaProvider.renameFileForFuse
at com.android.providers.media.MediaProvider.renameFileUncheckedForFuse
at com.android.providers.media.MediaProvider.renameUncheckedForFuse
at com.android.providers.media.MediaProvider.renameForFuse


UriGrantsManagerService:

android.os.BadTypeParcelableException:
About to unparcel a java.util.ArrayList, which is not a subtype of type android.net.Uri required by caller.

The exception occurs during normal media sharing to WhatsApp, including ACTION_SEND_MULTIPLE from Google Photos.

Screenshots or videos

Solution

No response

Additional context

WhatsApp versions tested:

• 2.26.34.81
• 2.26.33.75

Both versions show the same behavior.

WhatsApp permissions are granted, including READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, CAMERA and RECORD_AUDIO.

The device has approximately 187 GB free storage.

Normal storage operations work:

• System Camera can capture and save images.
• Chrome downloads work.
• Gmail can share the same image successfully.
• MediaStore can index and read Camera images.
• MediaStore can read WhatsApp database files.
• Files in the normal Download directory can be created and renamed.

The WhatsApp database directory and files have normal ownership/permissions, and the directory has the SELinux label u:object_r:fuse:s0.

FUSE is enabled and /storage/emulated is mounted normally.

The issue appears to involve Android 16 framework/storage handling, potentially MediaProvider/FUSE and URI grant handling, rather than WhatsApp permissions or network connectivity.

Acknowledgements

• I've checked device is officially supported and that no support is provided for unofficial devices (for device specific reports and not source related).
• I'm running latest version available on crdroid.net for this device and that the device is still maintainer supported (not flagged unsupported on download page)
• 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 and understand that not doing so will automatically result in closing of ticket.