Does anyone have any ideas what is going on in the root of my Storage Card? (See pic)
Lots of oddly named files have appeared. They cant be renamed, deleted or opened from within either my PPC, via activesink or with a card reader in my XP PC. The dates are very odd too.
I am currently copying all the data off the card so I can format it but was wondering if anyone else has seen this or if they know where they are coming from?
Any info gratefully received!
I got the same problem, but in my camera folder. Same kind of non-sense files appeared and caused my album software to malfunction.
Re-named the folder and created a new "original" and moved my photos there. Everything is working now and I didn't have to format the whole card.
But I too are curious as to why they get created and if there is a clever way to get them removed
fixed
xp's disk error tool fixd it so i guess its just coruption in fat. problem solved but cause not found.
I had the same problem coused by removing my card without closing my phone. Now I shut down the system first and than remove the card.
Whenever I try and upload a file to Google Drive or add a picture from my gallery to instagram, my phone creates a file called .thumbdata3 in the thumbnails directory on my SD card. The problem with this is not the creation of the file, it's that the file is exactly the size of all the free space on the memory card... When plugged into the computer it displays "0 Bytes Free" on the SD card...
So when I choose a file from the gallery to upload to google drive or instagram, it will hang on a black screen until this file has been created (filling up the SD card), and then upload... Then i check the free space, and it is 0Bytes.
Anyone else had this and fixed it?
PS Sorry for being a noob here
Bumping this...
Anyone had this? Or have a solution?
Same thing here, unfortunately no solution. Apparently it is safe to delete the file, but it will be recreated at some point, taking up all the space on the SD card again.
For me, it grew up to 400 MB and even beyond (IIRC), which seems a bit excessive, even taking into account that there are > 2000 pictures in the DCIM folder of my SD-card at the moment. Still, 400 MB is more than a quarter of the 1.4 GB that the pictures take up, which surely does not make much sense if that is supposed to speed up the process of reading/displaying the thumbnails!?
Does anybody know a fix? Is it ICS related? I'm on Stock 4.0.3 ICS BTW, and I never noticed this behaviour before the update...
Same here, with a SE Xperia Mini Pro (4.0.4). It happened with me when the phone tried syncing Evernote notes (with pictures attached).
Maybe this topic should be moved to a more generic sub-forum; apparently it's an ICS problem...
thumbdata3
I am also currently having this problem, specially when trying to upload/import photos from gallery to instagram. the ".thumdata3...." file can go as large as 2.5 gig for me, depenending on how much space I have on my SD card before importing pics from gallery to instagram
Same happenned to me - a siolutions that worked for me
Same happened to me the .thumdata3 ate up all remaining space (1.2G) on my Samsung Galaxy S2, android 4.0.3. Any time I deleted it, it was recreated any time I opened the camera app. Then the camera app was unable to take any pic due to sd full. If I deleted this file it was re-created any time I started camera again.
Installing and running the SDrescan app (from play store) helped. Though SDrescan made stock ringtones disappear. However reboot helped that, and the large file did not came back even after restarting camera.
This worked for me, though I am not sure in the reason. Might work for you as well, or not. I must say that android 4.0 is much worse than I expected. Not the first annoying error I have found.
My guess for the reason of the error happening: I once inserted an sd card with LOTS of media content. Then all this was cached somehow in gallery.
My guess for the reason this solution works: the app erases cached SD data thus helps reducing the thumbnail cache.
rasnadas said:
Same happened to me the .thumdata3 ate up all remaining space (1.2G) on my Samsung Galaxy S2, android 4.0.3. Any time I deleted it, it was recreated any time I opened the camera app. Then the camera app was unable to take any pic due to sd full. If I deleted this file it was re-created any time I started camera again.
Installing and running the SDrescan app (from play store) helped. Though SDrescan made stock ringtones disappear. However reboot helped that, and the large file did not came back even after restarting camera.
This worked for me, though I am not sure in the reason. Might work for you as well, or not. I must say that android 4.0 is much worse than I expected. Not the first annoying error I have found.
My guess for the reason of the error happening: I once inserted an sd card with LOTS of media content. Then all this was cached somehow in gallery.
My guess for the reason this solution works: the app erases cached SD data thus helps reducing the thumbnail cache.
Click to expand...
Click to collapse
I had the same issue, but unfortunately your solution didn't help me. Initially I thought it did, but after a reboot and launching Camera app, it hanged and created the .thumbdata3 file once again.
I also tried messing up with databases using SQLite Editor, as described here: http://forum.xda-developers.com/showpost.php?p=28466334&postcount=9, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
I have an issue with the size of the thumbdata3 file in DCIM/.thumbnails on internal memory (camera is set to store to ext SD) at the moment it is 314MB on internal memory but the thumbdata3 file in the DCIM/.thumbnail folder on ext SD is less than 1MB (I only have around 100 photos and pictures on my phone) - but camera still works (other than in the scenario described below)
If I delete the large thumbdata3 file from internal memory and then attempt to use the camera, the photo is taken without any problem but when I try to view it in either gallery or QuickPic by clicking through from the 'last image taken thumbnail' in the camera and then click back to carry on taking another picture the camera FC's. It usually does this twice and is then absolutely fine - apart from the fact that the large thumbdata3 file has been recreated on internal storage.
I've tried it numerous times and every time the same results - delete thumbdata3 from internal memory, couple of camera FC's, large thumbdata3 file recreated, no more problems (bar the loss of 314MB of storage)
I've tried replacing the thumbdata3 file on internal memory with a copy of the smaller one from Ext SD, creating a blank thumbdata3 file and setting it as read only/no write permission and neither have helped.
Its a bit weird and annoying but I won't let it take the shine off my fun with CM9, however it would be nice to recover that large chunk of storage space to be put to better use.
All the same, many thanks Arco - Beta 1 is my first CM9 install and its great :good:[/QUOTE]
Hi - haven't full troubleshooted this issue yet, but see my notes here. I have the same issue (GNEX JB 4.1.1 stock) and for me it is caused by the app KeepSafe which hides/unhides pics/videos on your phone. Note I believe this is an interaction issue between this app and the media scanning functionality in JB (and I suspect ICS), and so there are likely other apps that have the same issue. For me it creates 1 or 2 .thumbdata3 db files each around 1.3GB.
Certainly, irrespective of app causing it, you can follow the steps to purge Gallery and Media Storage, resync your gmail account and they should disappear on their own. Opening the camera and taking a photo causes the db to come back at around 400MB with a single thumbnail - one of the test files I was hiding and unhiding with KeepSafe but has since been deleted. Can't really explain this behaviour!
Any way, I made some notes on what I tested, the results and some ponderings in case this helps someone work it out:
Thumbdata3
Hiding in keep safe seems to create both the thumbnails and thumbdata file.
Clearing data/cache for gallery and media storage removes all these files? So far doesn't seem to be the case. File and db still there after. Rerunning the media scanner now. Perhaps they caused it? Also forced resync of all items in gmail account. Thumbs and db now gone. Not clear if it was the media scanning completing or the re-sync, but steps to resolve issue now appear deterministic.
Tested with single pic. Restored. No thumbs. Re-hid, thumbnail appeared for this pic and a 435MB db file.
All thumbs were for pics hidden in keep safe. However previously there were far more thumbs. Speculate - cumulative issue thru successive hide/restore cycles, possibly due to file name collision avoidance.
Deleting pic in file explorer also causes the problem? Does not appear to be the case. Gallery/Media Scanner/Media Storage handles this manual intervention far better under ICS/JB. Previously, manually removing a picture rather than deleting it thru Gallery tended to mean the tile/thumb remained. Scanner didn't or didn't very effectively detect this. Probable algorithm change in ICS. Now it sees the deletion immediately. Possibly implicated in keep safe not correctly interacting with the gallery/media scanner properly under ICS/JB.
I´ve the same problem.
After restarting the phone, the camera freezes for a while and regenerates the file, no matter how many media files are in the phone or sd card, it always growth to 431mg after restarting.
(I also find many lost files in the LOST.DIR (almost 2.300gb...many are dissapeared files that I forget about them!)
The .thumbdata files on my SGSIII take up ~4 GB worth of space. Already a quarter of my phones internal memory is being wasted. I wonder if this is a bug or "working as intended"? It makes me wonder how google can still justify the lack of an external microsd card slot on their nexus phones when there is so much space being mismanaged by the OS.
It's works
strom87 said:
I had the same issue, but unfortunately your solution didn't help me. Initially I thought it did, but after a reboot and launching Camera app, it hanged and created the .thumbdata3 file once again.
I also tried messing up with databases using SQLite Editor, as described here: http://forum.xda-developers.com/showpost.php?p=28466334&postcount=9, but that didn't help either.
I've done some more research and found a solution here: http://www.mobilephonetalk.com/show...in-memory-card&p=311954&viewfull=1#post311954. After I deleted the .thumbdata3 file, created a blank one with Root Explorer and removed write permission to it, the file stays at 0 bytes and Camera and Gallery apps still work fine.
Click to expand...
Click to collapse
It's works with me!
that works
That works for me:
1. copy name of thumbdataX--x file
2. delete that file
3. create folder named the same as deleted file; reboot your device
4. look in folders named LOST.DIR (you can find it in the root directory of your internal memory and your SDcard) - huge temporary files may be left in these folders, so delete these files
New thumbdata file can't replace the folder and doesn't appears :victory:
until now the folder solution works :laugh:
Kyonex said:
That works for me:
1. copy name of thumbdataX--x file
2. delete that file
3. create folder named the same as deleted file; reboot your device
4. look in folders named LOST.DIR (you can find it in the root directory of your internal memory and your SDcard) - huge temporary files may be left in these folders, so delete these files
New thumbdata file can't replace the folder and doesn't appears :victory:
Click to expand...
Click to collapse
It doesn't work, camera still overwrites the .thumbdataX--x folder. And as /mnt/sdacard is using FAT32, I also can't set file permission to 000 or use /dev/null symlink.
Been trying to figure this out for some time and after doing as much research as I could, I've discovered no solution.
Hope I put this in the right thread -- marking these things out:
--Windows 7 Computer - HTC Sensation 4G
--Hidden Files and Folders are set to show
It shows all of the folders from Android, but it doesn't show my other folders, like music and pictures. I have to type the directory manually to gain the access to the folder, and this only happens on some computers. I've put my SD card into other computers and the folders show fine, which is really weird to me. I can't remember all the folders I have aside from the ones my phone have on there, and it's frustrating having to go into my phone's file explorer to remember the names of folders, or which ones are there. I've even tried mounting my sd card direct from my phone and still nothing. Only shows the same folders I always see.
These are not folders that are on my phone. These are folders and files on my SD card that I can't see without manually typing "D:\DCIM" or "D:\Music"
Has anyone else had this problem and found a solution?
i have the same proplem
Hopefully someone can figure it out for us then because this is annoying not being able to shift through folders the way I'd like. Ah well...
It might be how the SD Card was formatted. If it's over 16GB it should be type Fat32.
Sent via SGS3 using Tapatalk
I have swapped my older microSD card (64GB) for a larger newer one (256GB), both are formatted as external SD with the exFAT file system (so it can be read with a computer using a microSD card reader for faster and easier file transfers).
The swap initially appeared to be a success, with photos and videos taken with the Samsung stock camera app able to be stored on the new external card. A third party video recorder also worked the same on the new card as it did on the old one (able to select a specific folder and saves properly). Playing back and accessing content from the new card worked fine in a variety of applications (accessing file types: various videos, audio mp3 and FLACs, .PDF, .doc, .epub, .cbz, etc.)
Unfortunately some apps will simply not work, while others which needed to have save locations redirected returned surprising effects.
Titanium Backup v8.1.0 simply does not launch with the new card (returns error Unfortunately, Titanium Backup has stopped.) I have tried first clearing cache and then even uninstalling/re-installing the app - no dice. I swap back to the old card and all works fine. This is the failure that smarts the most as it breaks my phone's app backup plan.
Zedge v5.70.3 app launches and seems to work until I go to install anything to the phone (ringtone, notification sound or wallpaper), then I get a Download failed error and the chosen item is not added. There is no way to swap the download location for the new card. Again I have cleared cache, un-inistalled and re-installed without success. I have sent them a support ticket.
Call Recorder Pro v 1.9 (Tohsoft) required me to change the ''Location of recording'' folder to SD card (no choice of which folder) and this selection resulted in a totally different and complex directory structure used on the new card:
Code:
/storage/emulated/0/Android/data/com.tohsoft.call.autocallrecorder.pro/files/CallRecorders
while on the old card I was able to use a more sensibly located folder in the root of the microSD card as follows:
Code:
/storage/6958-0839/CallRecorders
As the app works and the files can be retrieved this is not a deal breaker, but it is an added hassle now to locate the recordings!
I checked both cards using ES File Explorer and in the folder
Code:
/storage
they each show up as different folder names
old card: 6958-0839
new card: 0102-1A79
A bit of poking around searching online and I determined these were the unique volume IDs and not the volume names. Apparently these can be changed on a PC but I am unsure if this would have other implications. I also looked around for symlinking (which I use on my PCs to map my NAS shares), to see if a virtual link could be made to fool the operating system into thinking the cards were the same one. There was some info about this but I am not sure where I would put the symlink if the file system allows me to create it (on FAT file systems such as the microSD card's one this is a no no apparently, but I do not know the file system of internal memory where the link to the external SD would need to be - I wonder, is it using one of the Linux Ext file systems that support symlinks?)
I was guessing that a symlink for the new card named 6958-0839 (to look like my first working microSD card) should be placed in the following folder (after selecting Device in ES File Explorer):
Code:
/mnt/media_rw/
My handset is a Samsung Galaxy Note 4 N910U Android 6.0.1 stock rooted
I have tried searching here about this issue without success. Apologies if I am asking something that has already been answered - please direct me accordingly in this case.
Any assistance will be greatly appreciated.
Ok so I have solved it I think (TitaniumBackup launches ok again).
I changed the exFAT Volume Serial Number on the new card to be the same as the old one.
I ended up using Krylack Volume Serial Number Editor. I tried first using SysInternals VolumeID v2.1 and I was able to run the command but I was receiving an "Unrecognised Drive Type" error and the documentation says NTFS and FAT support (no mention of exFAT so maybe the tool is too old).
After applying the fix mentioned above I noticed that I am also running an app called XInternalSD with "Custom path to internal SD" ticked and the path set to
Code:
/storage/6958-0839/
I have not tried, since everything works for me now on the new card that I edited the VSN on, but I assume that if I had changed the numbers in the path field in the XInternalSD app to the new VSN that would have worked also...
So my Gallery used to use a lot of battery and when I looked it up the best solutions were for me to remove the permissions to read files and just not use the app. So I switched to Google's Gallery app, and while it's good and all, I still prefer Xiaomi's Gallery.
Afaik my main issue with Gallery using a lot of battery in the background is caused by a damaged image that the app is always trying to recover, but it always crashes and restarts itself, putting it in a loop. So I want to file my damaged file(s) and make this issue non-existent. Thanks for the help!
A few random ideas:
Remove card from phone, insert it into a USB reader, run chkdsk in Windows, to rule out file system corruption.
If you are rooted, use fsck_msdos in shell ( on phone ) to check external card directly.
Backup contents of external card on disk while skipping unreadable files during copy procedure, put it back into phone after copying files back to it.
Else, install F-Stop app and see which file is not displaying a thumbnail and delete it.
Monitor phone log with logcat app to see what causes the error.