Obsolete
Status Update
Comments
kr...@gmail.com <kr...@gmail.com> #2
I have this same problem on a different phone and its driving me crazy lol. Found any solution?
sy...@google.com <sy...@google.com> #3
I also have this problem and with only 1.4gb the file fills the phone immediately. Please address this issue as my phone is virtually unusable. I have to clear the file to use other apps. I have to wait half an hour to regenerate the file to use the camera our three gallery.
kr...@gmail.com <kr...@gmail.com> #4
Me, too!
Thumbnail files become bigger than the combined size of all other photos, so it has to be a bug.
Gallery and Camera become extremly sluggish after a while (because they have to read those massive thumbnail files?). They become responsive after deleteing those files. But the files become autocreated, and keep growing again.
Only workaround seem to ba a couple of hacks that stop the Gallery App from re-creating those darn files (e.g. chmod a-w, or creating directories with those filenames names)
Thumbnail files become bigger than the combined size of all other photos, so it has to be a bug.
Gallery and Camera become extremly sluggish after a while (because they have to read those massive thumbnail files?). They become responsive after deleteing those files. But the files become autocreated, and keep growing again.
Only workaround seem to ba a couple of hacks that stop the Gallery App from re-creating those darn files (e.g. chmod a-w, or creating directories with those filenames names)
sy...@google.com <sy...@google.com> #5
as far as I know it's a bug from Android, that spread to all devices and there's no official solution at the moment.
The only workaround to temporary fix it is trough command line:
1) delete these files and make the .thumbnail folder read-only
2) create a script that every now and since cleanup this folder
Unfortunately, the CPU consumption will still be there in both cases. Try to use as less as possible the official gallery, and use instead another one (e.g. xperia gallery, or any app)
Ciao
Pietro
The only workaround to temporary fix it is trough command line:
1) delete these files and make the .thumbnail folder read-only
2) create a script that every now and since cleanup this folder
Unfortunately, the CPU consumption will still be there in both cases. Try to use as less as possible the official gallery, and use instead another one (e.g. xperia gallery, or any app)
Ciao
Pietro
wi...@gmail.com <wi...@gmail.com> #6
I too have same problem.if any of u find a solution pls mail me
lo...@google.com <lo...@google.com>
em...@gmail.com <em...@gmail.com> #8
the same problem...thumbnails is eating 1.7GB of storage.
so...@gmail.com <so...@gmail.com> #9
Does Google know about this issue? This is a major issue and is completely unacceptable. My thumbnails folder got to almost 3 GB and when I deleted it I didn't get the space back! This has happened twice already! Google, get off your collective ass and fix this extremely irritating issue!
bo...@gmail.com <bo...@gmail.com> #10
[Comment deleted]
ka...@gmail.com <ka...@gmail.com> #11
can someone confirm if this is still happening on kitkat
ba...@gmail.com <ba...@gmail.com> #12
Same problem......thumbnails occupide 1.2 GB please any one can help
tg...@gmail.com <tg...@gmail.com> #13
Same for me, but i dont have a linux PC, i found there is a sudo command to redirect the creation of this folder to a null.
bk...@gmail.com <bk...@gmail.com> #14
Same here. Basically, the thumbnail file eat every free storage I have. How large the free space there are, how giant it is. It can be deleted but will re-created if start the build-in camera app or any app that need to show the thumbnails for media that in my device. If the camera app told you the storage is out of the space during taking photos, thumbnail file manually will not free the space until you reboot and delete the thumbnail file which show up in the folder "LOST.DIR" with a random name.
In my case, the largest record for the file "thumbdata3-(random digits)" is 3.7G.
--
Device Model: Sony XPERIA P (Lt22i)
Android Version: 4.1.2
ROM Version: Sony official ROM 6.2.A.1.100
In my case, the largest record for the file "thumbdata3-(random digits)" is 3.7G.
--
Device Model: Sony XPERIA P (Lt22i)
Android Version: 4.1.2
ROM Version: Sony official ROM 6.2.A.1.100
mt...@gmail.com <mt...@gmail.com> #15
I notice a direct correlation between using the phone camera and the file size growth. So I don't think it's the stock gallery. I think it's the phone camera thumbnail file. I have seen solutions for those running rooted phones, but none for stock phones. Deleting the file repeatedly is a work around. Where is the official response from Google?
mi...@gmail.com <mi...@gmail.com> #16
This problem is really ridicolous... amateur!!!
Huawey Ascend Y300, phone is totally unusable, 1GB eaten by NOTHING!!!!!!!
Huawey Ascend Y300, phone is totally unusable, 1GB eaten by NOTHING!!!!!!!
ra...@gmail.com <ra...@gmail.com> #17
I've had luck creating a FOLDER with the same exact name as the thumbdata FILE. I tried a file with the same name, but it got overwritten. If you use a folder, it works. You'll need some type of file browser with view hidden files enabled. BTW, you must add the . at the begging of your folder name to make it hidden.
ad...@google.com <ad...@google.com> #18
Hi all, i found out this file is being created by Whatsapp, when sending a picture to a contact. I created the empty folder using winrar because windows didnt allow that .name, however it still rewritting. Any other idea?
Description
MMS either incoming or outgoing, including picture, audio, vcf, group messaging etc. does not work with AOSPs new MMS protocol.
I've tried several VPNs including:
FreedomeVPN
Vypr
BetterNet
Hotspot Shield
Disconnect
Even VPNs that have app whitelisting cause MMS to fail.
I tried Textra as a texting replacement app (for other reasons). In the settings it has an option to use either System or Legacy protocols for MMS. It even tells the user to try System if they have a VPN enabled. I switched to System from the default Legacy, and now my MMS works flawlessly with a VPN running.
I've double checked to see if MMS still fails using other texting apps, including Google's own Messaging app, and several others, MMS still fails.
Something about the protocol differences causes MMS to fail when running a VPN. This leads to a poor UX, and defeats the purpose of running a VPN causing users to constantly have to enable and disable it just to send messages. Whether it's to connect to servers for work, or for users who just want a little extra privacy, users should be able to run VPNs and still be able to send MMS.
Side note: This issue also causes regular SMS to send and receive much slower than normal. THey all go through eventually it just takes a lot longer, up to a couple of minutes.