* USER-ID of current user in case of Multiple Users or Work Profile, normally 0 i.e. * >S> for symlink, >E> for emulated and >B> for bind mount mnt/runtime/default/emulated >E> /data/media storage/emulated >B> /mnt/runtime/default/emulated mnt/runtime/default/self/primary >S> /mnt/user/USER-ID/primary # for services/daemons/processes in root/global namespace (VIEW = default) mnt/runtime/VIEW/emulated >E> /data/media storage/emulated >B> /mnt/runtime/VIEW/emulated mnt/user/USER-ID/primary >S> /storage/emulated/USER-ID # "/storage to VIEW" bind mount is inside a separate mount namespace for every app On Android 6+: # for (Java) Android apps (running inside zygote virtual machine) On Android 5: /sdcard >S> /storage/emulated/legacy >S> /mnt/shell/emulated/0 This is with reference to my previous answer here, but with more relevant details. On Twitter, Facebook, and Instagram./storage/emulated/0/ is actually /data/media/0/ exposed through an emulated / virtual filesystem, not the actual one.
The update WhatsApp rolls out might just move the content from the media folder to the new folder, like you were instructed to do manually.įollow HT Tech for the latest tech news and reviews, also keep up with us If you do not want to do this, you can just wait for WhatsApp to roll out a fix that solves the issue, but we don't know when that might happen. Once you follow these steps, you will be able to see your media content on the app again. Once it is done, you can then open WhatsApp. Wait till all the content is moved to the new destination folder. Remember, you need to just move the contents of the media folder and not the entire folder.ĥ. Now, move the content in the Media folder to Android > Media > com.whatsapp > WhatsApp> Media.Ĥ.
Open your phone's native file manager and go to WhatsApp. Make sure that the app is not running in the background.Ģ. Close WhatsApp on the phone and then clear cache. How to fix the missing media issue on WhatsApp for Androidġ.
0 kommentar(er)
