Hi
Sorry not a high tech question but would appreciate some help
Re. my viewpad 7
Seems to be constantly short of inbuilt memory.
(should be 512mb)
was down to zero today though have not addded anything for a while.
Clearing cache and history via browser took it back up to 8 mb but already with an hours use down to 6mb again.
Have moved everything that Apps manager allows over to the (16GB) SD card, which still has lots of space.
Neither of the "File Explorer" or "Settings/SD card and phone storage" routes let me actually see what's in phone memory.
Pad is "as bought" re rom's etc
Would appreciate any help.
thx
Russ
It's got 512mb total, which is split over different partitions.
You are running out of space on the /data partition, try uninstalling some apps, or use an app like apps2sd to move some to your sd card.
Thanks for quick response but have tried deleting a few apps and have already moved everything that can be moved onto sd card
have downloaded a couple of versions of app2sd apps 2sd etc but they do not offer any more suggestions on apps that can be moved as I say I have aready moved all that seem moveable
It does seem that it's some sort of data thats the problem but I can't see into the inbuilt memory to see what data it is or from what app
rgds
russ
It is stupid Android. When you move apps to SD, than still some (usualy bigger) parts is still in internal memory. When you move apps to SD, than info about occupied space is valid only for occupied space on SD by the apps. If you want to know how big is the application than you have to move back to internal memory, than info is correct.
Also some updating of system apss can consume very big space of internal memory. For example Aldiko can occupy 6MB !!!!
The problem is, when you install a new app either from Android Market, Amazon App Store or anywhere else, the system retains the .apk install file somewhere in memory. I'm yet to find where those files are stored.
You can use a file manager like Astro File manager to see all the files on your viewpad 7's internal memory however, manipulating those files is a bit trickier. I thought I found them in a \sys\data directory or something like that but the system refuses to let me delete them.
Does anyone know for certain where these .apk files are stored. I've deleted/moved everything I can and am down to the apps that I need on the unit. If I have to delete more, then there is no sense having a small form-factor tablet. The space that is being used is far above the applications that I have installed so there has to be garbage files somewhere that need cleaned up.
I captured a full res video on my AT&T Samsung Galaxy S II (unrooted) for the maximum time (~1Hr), which created a file about 4GB in size. The file played fine several times.
Now it has a filesize of 0 bytes. The file was stored in the camera RAM, not on the external SD card, so I can't use file recovery programs as they don't see the camera memory. I haven't added new pictures since, so I am hoping the file space is not overwritten, but it has been through several power cycles.
Any ideas how I can recover the file?
HiTach said:
I captured a full res video on my AT&T Samsung Galaxy S II (unrooted) for the maximum time (~1Hr), which created a file about 4GB in size. The file played fine several times.
Now it has a filesize of 0 bytes. The file was stored in the camera RAM, not on the external SD card, so I can't use file recovery programs as they don't see the camera memory. I haven't added new pictures since, so I am hoping the file space is not overwritten, but it has been through several power cycles.
Any ideas how I can recover the file?
Click to expand...
Click to collapse
Couldn't have been stored in RAM. You must mean internal SD. Internal SD DOES get assigned a drive letter when you connect to a computer in USB storage mode, you could try that.
Also, you should note that this is the forum for the International Galaxy SII, which is the I9100. You have the AT&T variant, which is the SGH-I777. While this question is pretty general, and any solution presented would probably be applicable to you, you should really be in the correct forum for your device.
Thanks for the quick tips.
Yes, the wrong forum I'm afraid, sorry. I shall use the correct place next time.
I had connected my device several times without seeing drive letters assigned, and found I had to enable USB debugging, (Menu->Settings->Applications) which did produce the drive letters for both the internal system storage and external SD storage.
Using FinalRecovery 1.21, which I have used successfully on SD/CF cards, I found the file was deleted, but the size is shown as a negative number (-3670016), probably overflowing the sizes allowed, so I shall explore other apps to see if the file can still be recovered.
I appreciate your help in any case!
I'm using a GS3 w/ a Sandisk 64GB microSDXC card formatted as exFAT. I'm hoping someone here with knowledge of exFAT can help me troubleshoot an issue I've seen. This is probably going to end up fairly detailed, so bear with me.
I recently copied ~40GB of data to my new 64GB card in Windows using the card reader in my laptop. It appeared to go off without a hitch. Today, however, I noticed an issue with my music files (mostly .mp3 and .wma). I had transferred a new song to the card and it seemed to go through. However, on the device, the file didn't appear. So I did it again, transferred the file, and it seemed to go through. It didn't tell me there was a duplicate file on the device either, so I played it on the card through Windows to test it. No issues. Unplug my device and the file disappeared again.
So I go into ES File Explorer (and later I used the My Files application that Samsung loads, with the same results) and go into my music folder to see what's going on. It appeared that at some point, the file name got corrupted and concatenated with part of another file name; instead of being "artist - song.wma", it was "artist - song.wmas Track).wma". So I think that the OS doesn't like the .wma in there, and try to rename it to what it should've been. The system says that that the file system already exists. I tried to delete the file, and it won't let me. The file explorer is also reporting that the file is 0kb in size. At this point, I open up a terminal emulator and try to delete the offending file through the command line, but I cannot delete/rename the here either, despite being listed (I'm told the file does not exist). Finally, I plugged in back into my Windows box but the bad files will not even show. The file on my computer is good and plays fine.
So I scratched my head for a little while. Then tonight at the gym I wasn't able to find the song I wanted. Sure enough, it was tied to this issue. I went back into the file explorer and found ~50 files (of ~4200) that had corrupted file extensions. These differed from the original in that only the file extension had been altered (ie .mp3p3 or .wmaa). However, I am unable to delete/rename any of the files. Also worth nothing is that some of these files had sizes. It's possible that other files exist like the original where the file extension is valid, but the original file extension is within the file name.
I have not confirmed this yet, but it is also possible that the issue is not limited to music files. I was looking through my pictures the other day and noticed that some images weren't loading; I deleted these files at the time and didn't think anything of it because a few weeks back my epic 4g corrupted my microSD and I had used some file carving tools to recover some images (obviously, not a perfect fix).
So the problem is beyond my expertise at this point. I'm not sure how to handle these damaged file remnants. I'd like to get rid of them because they prevent the existence of the good file in that particular folder in addition to taking up space. As a short-term solution I re-copied the files I wanted to a temporary folder on the card and they are working without issue.
Right now I'm leaning towards wiping the card, reformatting it, and transferring again. However, before I do that, does anyone have any ideas? Is there any chance this could be an issue with the card itself? Or a GS3 issue? The files on the computer are still good and the problem seems to manifest itself regardless of the method used to transfer to the card as the original files were transferred using an SD adapter and card reader, and the file that triggered this issue was transferred using the usb cable.
I appreciate any insight or opinions.
Tim
it's caused by long/speciafic filename of the file.
just put the sdcard into your cardreader and then connect to your pc, delete/rename the file which caused the issue.
The files don't appear for me to be able to delete them. The file explorers won't allow me to delete them. A terminal lists the file but tells me it doesn't exist when I try to delete it.
UPDATE: I formatted my memory card using the device itself and transferred the files again. This did not resolve the issue. Interestingly, the SAME files that were corrupted last time were corrupted this time. I can still transfer the same files from my computer to a separate folder and they work. The file remnants cannot be deleted or altered. What could be causing this issue?
Is this a genuine card? I once bought a 16 GB memory card that was actually just 2 GB but reported the full 16 GB to Windows. I found out I had been scammed when I started getting errors similar to yours when I copied more than 2 GB of data.
Sent from my GT-I9300 using xda premium
Yeah, it's a genuine SanDisk 64GB SDXC card.
H2test
http://mympx.org/Downloads/p13_sectionid/2/p13_fileid/13
Sent from my GT-I9300T using xda premium
I'll give it a shot when I have more time, but I'm leaning towards a software issue. It's either an issue with the file system itself, or with the SGS3 software. The same files are corrupted in the same way each time (in the same folder). However, in the new folder where I moved the copies of the problem files, there were also some corruption, but different from the original folder. Moved new copies to a third folder, some files were good, a few more remained corrupted. By the time I moved copies into a fourth folder, there were no more issues. The problem is now I probably have an extra 500MB+ worth of garbage that I can't do anything with. The search for the underlying issue continues...
FailDeadly said:
I'll give it a shot when I have more time, but I'm leaning towards a software issue. It's either an issue with the file system itself, or with the SGS3 software. The same files are corrupted in the same way each time (in the same folder). However, in the new folder where I moved the copies of the problem files, there were also some corruption, but different from the original folder. Moved new copies to a third folder, some files were good, a few more remained corrupted. By the time I moved copies into a fourth folder, there were no more issues. The problem is now I probably have an extra 500MB+ worth of garbage that I can't do anything with. The search for the underlying issue continues...
Click to expand...
Click to collapse
try formatting in the device, then transfer over one of the files and see if it has a problem....I would guess the file name of the problem file is too long. if the file transfers and is still a problem try renaming it to like test.mp3 and see if it transfers ok.
tillithz said:
try formatting in the device, then transfer over one of the files and see if it has a problem....I would guess the file name of the problem file is too long. if the file transfers and is still a problem try renaming it to like test.mp3 and see if it transfers ok.
Click to expand...
Click to collapse
I thought exFat had really large limits on filenames? That, along with the greater than 2gb file limit removal, are some of the pluses of this over regular Fat. I could be way outta line here, but that's what I remember about it. ExFat should rock! FWIW, I've had a Kingston hyperX flash drive formatted with ExFat and have never had a filename issue copying 10's of thousands of .mp3's, .jpg's, etc...
The files in question don't have particularly long names though. I'm guessing that there's a small handful of files elsewhere on the folder with a name that's causing the file system to freak out. I'm curious if tag info or metadata could cause an issue as well. This last time I transferred via sub directly to the device instead of taking the card out and using a card reader. My next move might be to transfer via the reader and see if there are any issues BEFORE putting the card in the device; it might still be a sgs3 issue...
Not sure if you have tried this yet but since it seems to be repeatable by way of the same files, have you tried copying the offending files to internal storage to see if the same problem occurs?
This would definitely rule out the MicroSD card and lend itself towards being a software issue.
SOLUTION: Format the microSDXC card as FAT32. All my files transfer, show up, and work just fine. Either the exFAT file system is broken, or (more likely) Samsung broke the exFAT support somehow. I might experiment with exFAT on an 32GB card to see if I can find the root of the issue, but for now I've lost my patience.
FailDeadly said:
SOLUTION: Format the microSDXC card as FAT32. All my files transfer, show up, and work just fine. Either the exFAT file system is broken, or (more likely) Samsung broke the exFAT support somehow. I might experiment with exFAT on an 32GB card to see if I can find the root of the issue, but for now I've lost my patience.
Click to expand...
Click to collapse
My Sandisk MicroSDXC 64GB card should be arriving today. I was hoping to use exFAT so will try it out tonight and report back. I have lots of HD TV shows to transfer so it will be full straight away.
Hi there
I also got the SanDisk 64GB SDXC card in my SGS3 and it is formatted as exFat. I think this exFat does not run correctly on the Galaxy.
I also encountered some corrupt file names on the SDcard and even some of my music folders do not show up as folders but as an unknown file that cannot be accessed.
Furthermore I copied some .flac files to my phone. The files work without a problem when being put on the internal storage. As soon as I put them on the SDCard the stock-music player does not recognize the .flac format anymore and thus the music cannot be played.
I guess I will re-format the SDcard to FAT and hope that Samsung (or maybe even a DEV) will come up with a solution to this problem. Another positiv aspect of having the card formatted as FAT is that I probably can apply some custom kernels and they will mount my FAT-64GB card (currently the custom kernels cannot mount or detect exFat formatted drives).
Hope this info helps a bit.
Working perfectly for a couple of week now in my S3, formatted exFAT.
I tried my Sandisk 64GB exFAT card last night and all seems to be working perfectly, I have filled it and can see all the files on the S3. Very happy with it.
Not Stable exFAT
Looks like exFAT is not yet fully finished in SGS3, thats why Samsung didn't include information about exFAT on their manual / user info.
When i use exFAT format, the problem is almost non existent in few file, but when i filled the SD card with many data and lot of small files (ex. HD Game data), the card says corrupted in my SGS3.
Screenshot is in here : LINK
The problem is only exist when the sdcard is start to filled with many files.
But when i filled it with few file but large size (ex. 4 files of *.mkv, that totals to 42GB), the card runs fine.
So the problem is only exist if the sdcard is filled with many data.
Please all of you try this, if my problem can be repeated in every SGS3, then it is definetely bug from the exFAT support on SGS3.
*also has tried it with siyahkernel that listed have exFAT support, but the problem is still the same in that kernel, maybe the support/patch/mod of exFAT that gokhanmoral use is the same that come with our stock SGS3.
Mine if near full, lots of app and game installs and small files and no problems here.
NZtechfreak said:
Mine if near full, lots of app and game installs and small files and no problems here.
Click to expand...
Click to collapse
hmm.. maybe its different firmware that causes it ?, mine on XXALE8-DXLE8
My SDcard is filled with Tintin HD game data, and that makes my exFAT SD card to show corrupted on SGS3, but normal on everything else (computer, laptop).
Hi, I'm a total noob to Android phones, I admit it. I just got my first smartphone, and it's an old one - an HTC Aria. Thanks to a lot of info here in XDA-developers, I got it rooted with clockwork mod and am using the Cyanogen ROM with Android 2.3 (Gingerbread).
Well, it's such an old phone, I see that it only has ~185 mb internal storage. I added an 8GB SD card. Even though I move my apps to external storage, I can see that the data didn't get moved and is still quickly eating up all the phone's internal storage. I'm trying to use Madmack's "FolderMount" but am having trouble figuring it out. I think it might be an understanding of Android file/folder structure (I have very little). I'm considering buying the "pro" version (if it works for me), just so I can move the whole data folder at once and free up my internal memory again.
Here's my efforts at testing to see if it works. I'm trying to move the data from the "Plague, Inc." game to the external card (the app is already on the external card). So, when I choose source, it automatically starts me in the /mnt/sdcard/ but doesn't allow me to go "up" to any further root folders of that. So I found in the "Android" folder the "data" folder. I tried to FolderMount that but it gave me the error about the non-Pro version. So I tried the "com.miniclip.plagueinc" folder (knowing that it's currently using 15MB of data) and then using an app called SDCardManager (which I understand is supposed to make it easier for me to access my SD Card, like Windows Explorer or something), I made a folder with this path "/mnt/sdcard/foldermount" I think it should be the right path because it's also where my "android.tether" folder is that I know I created myself.
Anyway, when I pair those two folders in FolderMount, it copies stuff over, and the pin looks green, but it shows my internal memory hasn't changed, still almost entirely full. So what do I do to clear it up? I think my problem is in my understanding of the Android's file structure. I think on "source", I should be able to access some folder before "/mnt/sdcard", but I can't get there. Please give this noob help from anyone who can! Thanks!
Can anyone help me with this? Particularly the developer, madmack? I really need to find a way to move the app data to the external memory so I can clear up space. Even if someone could help me understand the file structure better, that'd be helpful. Thanks!
Hello guys!
1 month ago I had this problem with my LG l9, i had loads of memory free but whenever I tried to install any apps it would tell me I didn't have any storage available. I am rooted. I restored my phone and nothing happened. Then, I managed to install storage analyser, and saw that one of the folders was taking up like 10GB of space and the app was telling me I only had -8GB of space (yes, negative!)
I deleted the folder (from gameloft) and then I managed to install some apps. Now i have the same problem. Some apps install perfectly, like riptide 2, even if they are huge, and some small apps like chrome and google play music don't
What can I do to fix it? Restoring won't help and neither does storage analyser....
aristide1997 said:
Hello guys!
1 month ago I had this problem with my LG l9, i had loads of memory free but whenever I tried to install any apps it would tell me I didn't have any storage available. I am rooted. I restored my phone and nothing happened. Then, I managed to install storage analyser, and saw that one of the folders was taking up like 10GB of space and the app was telling me I only had -8GB of space (yes, negative!)
I deleted the folder (from gameloft) and then I managed to install some apps. Now i have the same problem. Some apps install perfectly, like riptide 2, even if they are huge, and some small apps like chrome and google play music don't
What can I do to fix it? Restoring won't help and neither does storage analyser....
Click to expand...
Click to collapse
Have you tried Link2SD? If not, it does work. I just set it up on my P769. First you'll need to enable init.d support. Just create a folder named 'init.d' in /system/etc. You will also need to partition your SDCARD so that is has two partitions. A primary FAT32 partition and a primary ext2, ext3, or ext4 partition. The second partition is the one Link2SD will actually use. I have a 32 GB SDCARD with 3 partitions. FAT32 partition is 27 GB, 1st ext4 partition is 4 GB, and the 3rd partition is 1 GB for SWAP if I get around to seeing if SWAP works with the stock kernel or not. SWAP is not necessary and more than likely is NOT supported by the stock kernel anyway.
I'd suggest looking in to the Link2SD thread prior to attempting this.