Hey all,
I hope someone can help as I've searched this issue here and on Reddit and found various answers to the problem but no solutions. My brother has a Pixel 5 and the "media storage app" hogged around 50 gb of storage (same issue as Oneplus, however Oneplus solved it with an update) and filled the device. In my searches I found 3 answers; it's the media on the phone just displayed incorrectly, it is a wrong reading from the phone, or it is duplicated media which doubles the used storage (makes more sense as you'll see below).
Another Issue was Android System taking only 2 gb of space when normally it should be around 11-12 (as on my Pixel 2 and Pixel 4a), but this was solved with a wipe.
Due to various software issues with the phone I convinced him to do a complete wipe and reflashing of the stock firmware through Android flash tool. Also knowing Whatsapp caused weird issues in the past (with his Pixel 1) I also made him delete all previous backups from the phone and Google drive and clean his media (deleted only a few hundred mb) then back up again. The backup was 27 gb (not around 50 as media storage showed).
We did the wipe and flashing and everything worked well. But when we started restoring the data again and Whatsapp started restoring media then the Media Storage app started growing again, I am yet to determine if it is duplicating or not, but I am 100% convinced that there is something wrong because I checked my Pixel 2 with Android 11 and my Pixel 4a with Android 12 beta and in both cases this app barely takes a few mb of storage, all the other "media" is properly organized as it should be in it's respective category, on his phone though its all in "other".
I am really out of solutions other than wiping Whatsapp completely clean without media, only backing up chats, but this doesn't guarantee that all the media won't duplicate or fill up in Media storage again. At this point I'm thinking of waiting until Android 12 official but it also doesn't guarantee anything since it's not clear where the issue is coming from exactly.
I hope someone can help as I've searched this issue here and on Reddit and found various answers to the problem but no solutions. My brother has a Pixel 5 and the "media storage app" hogged around 50 gb of storage (same issue as Oneplus, however Oneplus solved it with an update) and filled the device. In my searches I found 3 answers; it's the media on the phone just displayed incorrectly, it is a wrong reading from the phone, or it is duplicated media which doubles the used storage (makes more sense as you'll see below).
Another Issue was Android System taking only 2 gb of space when normally it should be around 11-12 (as on my Pixel 2 and Pixel 4a), but this was solved with a wipe.
Due to various software issues with the phone I convinced him to do a complete wipe and reflashing of the stock firmware through Android flash tool. Also knowing Whatsapp caused weird issues in the past (with his Pixel 1) I also made him delete all previous backups from the phone and Google drive and clean his media (deleted only a few hundred mb) then back up again. The backup was 27 gb (not around 50 as media storage showed).
We did the wipe and flashing and everything worked well. But when we started restoring the data again and Whatsapp started restoring media then the Media Storage app started growing again, I am yet to determine if it is duplicating or not, but I am 100% convinced that there is something wrong because I checked my Pixel 2 with Android 11 and my Pixel 4a with Android 12 beta and in both cases this app barely takes a few mb of storage, all the other "media" is properly organized as it should be in it's respective category, on his phone though its all in "other".
I am really out of solutions other than wiping Whatsapp completely clean without media, only backing up chats, but this doesn't guarantee that all the media won't duplicate or fill up in Media storage again. At this point I'm thinking of waiting until Android 12 official but it also doesn't guarantee anything since it's not clear where the issue is coming from exactly.