does this happen to anyone else? the application color fills the entire space despite having 7+ gigs of free space.
bueller..
No sorry, my phone is reporting normally. I have 9.21gb free after what the OS takes up. Since your phone is pretty new (at most 3 or 4 days old) i would do an FDR and see if it fixes it and if not swap it out. Obviously something is corrupt if an FDR doesn't fix it and you didn't actually put 7gb+ of stuff on the phone.
Eric
Related
I posted this issue on Android Central as well, but not as much chatter over there. Here is my issue:
I had this problem with my Samsung GSII as well and thought it may just be a fluke, but now I am having the same issue with my new Note.
Due to lack of free application storage, I move (VIA the App manager) most of my larger games on to the Micro SD card. Which looks like it works fine, however, after a while, not so much.
The Note (and all Samsungs) go through the scans when you boot up the phone on the internal storage and the memory card... Upon completion of this scan, the phone just keeps resetting. Once I pull the memory card out, I am good to go, but all my games were on the memory card.
I am using a PNY Class 10 card and am thinking maybe it is corrupt? Or maybe I am really not supposed to load everything on to the card like that?
Thoughts? Anyone else run in to this?
Thanks!
you do realize that most apps including large games take less than 50mb of space. and we have a 2GB storage partition you can store hundreds of apps with no problem. TBH i wouldnt bother with moving them until you do actually run out of app space.
As much as I hate to admit my app problem... I have long ago surpassed the 2G app storage..
After years of purchasing apps and many very good free apps of the day from Amazon, 2GB no longer cuts it for me.
Thanks.
wow really well the issue is that the phone itself uses the internal memory as the default storage location. There are some hacks but i wouldn't recommend using them on this phone as they are untested. Do you honestly use all those applications? I have tons of apps that I really dont use anymore that were from the donut days of android.
Your response sounds like some of the responses I get from our developers... "Well, tell them not to use it and it wont break!".
I say that in good fun. No, I dont use them all, but whenever I get a new device, I like to load it up with my stuff to test it out.
I could definitely remove or just not install about half of them, but again, that doesnt fix the problem. It simply avoids the problem.
Thanks again for your response.
codeworks said:
I posted this issue on Android Central as well, but not as much chatter over there. Here is my issue:
I had this problem with my Samsung GSII as well and thought it may just be a fluke, but now I am having the same issue with my new Note.
Due to lack of free application storage, I move (VIA the App manager) most of my larger games on to the Micro SD card. Which looks like it works fine, however, after a while, not so much.
The Note (and all Samsungs) go through the scans when you boot up the phone on the internal storage and the memory card... Upon completion of this scan, the phone just keeps resetting. Once I pull the memory card out, I am good to go, but all my games were on the memory card.
I am using a PNY Class 10 card and am thinking maybe it is corrupt? Or maybe I am really not supposed to load everything on to the card like that?
Thoughts? Anyone else run in to this?
Thanks!
Click to expand...
Click to collapse
I have the same problem & no solution. I ended up restoring the Note on day 3 of ownership due to the constant resetting. Is there a way to make the internal 16GB the default install location?
Sent from my Amazing White AT&T SG Note using XDA Premium
Honestly, I have about 8 gigs of apps installed, all moved to external SD card - a 64GB Sandisk Class 6. No reboots and no issues at all. Always move everything I can to external SD. Not sure why, just some mental preference in me likes to keep the phone itself as free as possible. Never had a restart or a crash because of it. Always used App2SD Pro app or Force to SD if rooted andnits been flawless - same experience on the SGS2 as well. Sounds like a corrupt card to me, honestly. Were you using he same card when you had issues in your previous Samsung devices?
Sent from my SAMSUNG-SGH-I717 using xda premium
I've had this problem for about a year. I've finally gotten to the point that I am tempted every 5 minutes to throw my phone into oncoming traffic. Have no idea how I've lived with it for this long. It is rooted and I have Th3Bills CM10 on it. Haven't updated ROM for almost a year because I have lost interest in anything to do with it because it is basically nonfunctional. Also in fear of getting the dreaded "low storage space". I don't know if I did something wrong when I did all of that, which is a huge possibility. But basically, I bought a 32gb SD card because I started getting the low storage space notifications all the time on my 16gb one, and at first I thought I really did fill it. So I went up in size. After that I kept getting it with the 32gb and I knew there was no way possible that it was full. My phone shows 2 internal storage's. One is 3gb which I think should be the part of the internal that's allotted to apps?, and the other is my SD card at 32gb with 10gb available. The only thing that should be on it is music that I manually added through the computer. And the storage that shows as SD card is the internal storage. So it's all messed up. Can anyone tell me how to fix it and get my phone to register my SD card as an SD card and how to make it useable? I'm going to need thorough step by step instructions, too. haha. That's the only way I know how to do any of this kind of stuff. TIA =]
Hi,
Over the last week, I've had two SD cards die on me:
The first card I've had since I got my i9300 S3 (13 months). Prior to last week, it worked flawlessly (KomputerBay 32GB class 6). Then suddenly after rebooting I see an SD card damaged error. After trying chkdsk and fsck it looks like the card is certainly damaged but was able to recover some of the files.
Thinking it was just bad luck and the card dying, I purchased a 32gb class 10 Lexar card brand new. In the meantime, I used a 4GB Samsung SD card that came with the S3 for approximately 5 days and it worked fine with no errors or corruption.
With the new card, I copied over all my files, music etc. After an overnight using the phone, some calling etc. I rebooted the phone only to get the same error. Windows didn't even recognise the card let alone recover it. fsck likewise. Did a full format again and restored some files from original backup, it's been less than 24 hours and so far so good but I am not ready to relax just yet.
I'm really baffled as to what could be causing it as the card seems only to fail after a reboot. Prior to then, the card displays as mounted in system settings and files are accessible. The only other strange thing I've noticed is that when playing music/podcasts and turning off the screen the playback jitters for a moment or two before returning to normal. This started quite recently. I'm using UltimaROM 13.0 at the moment with Boeffla kernel. Have disabled all SD related optimisations and have no CPU or GPU overclocking or undervolting. I've been using Ultima for months with no major config changes recently.
I'm at the point now where I am almost scared to reboot! Last time I rebooted I unmounted the SD just in case. The only other possible difference in behaviour is that as I was travelling I had my phone on charge all night and although I can't be 100% sure rebooted with the phone charging (though again, its not the first time I've rebooted while charging). I've googled this far and wide and most SD related issues seem to be caused by the card randomly unmounting. I've never seen this in my instance.
Any ideas on what this might be or what I could do to troubleshoot further? I don't want to restore to stock, unroot, reset counters etc. and return to Samsung unless I can be at least reasonably confident its a hardware issue.
Thanks,
thegrantonstarcause said:
Hi,
Over the last week, I've had two SD cards die on me:
The first card I've had since I got my i9300 S3 (13 months). Prior to last week, it worked flawlessly (KomputerBay 32GB class 6). Then suddenly after rebooting I see an SD card damaged error. After trying chkdsk and fsck it looks like the card is certainly damaged but was able to recover some of the files.
Thinking it was just bad luck and the card dying, I purchased a 32gb class 10 Lexar card brand new. In the meantime, I used a 4GB Samsung SD card that came with the S3 for approximately 5 days and it worked fine with no errors or corruption.
With the new card, I copied over all my files, music etc. After an overnight using the phone, some calling etc. I rebooted the phone only to get the same error. Windows didn't even recognise the card let alone recover it. fsck likewise. Did a full format again and restored some files from original backup, it's been less than 24 hours and so far so good but I am not ready to relax just yet.
I'm really baffled as to what could be causing it as the card seems only to fail after a reboot. Prior to then, the card displays as mounted in system settings and files are accessible. The only other strange thing I've noticed is that when playing music/podcasts and turning off the screen the playback jitters for a moment or two before returning to normal. This started quite recently. I'm using UltimaROM 13.0 at the moment with Boeffla kernel. Have disabled all SD related optimisations and have no CPU or GPU overclocking or undervolting. I've been using Ultima for months with no major config changes recently.
I'm at the point now where I am almost scared to reboot! Last time I rebooted I unmounted the SD just in case. The only other possible difference in behaviour is that as I was travelling I had my phone on charge all night and although I can't be 100% sure rebooted with the phone charging (though again, its not the first time I've rebooted while charging). I've googled this far and wide and most SD related issues seem to be caused by the card randomly unmounting. I've never seen this in my instance.
Any ideas on what this might be or what I could do to troubleshoot further? I don't want to restore to stock, unroot, reset counters etc. and return to Samsung unless I can be at least reasonably confident its a hardware issue.
Thanks,
Click to expand...
Click to collapse
Have you read the other SD Kill thread? Should come up in a search
rootSU said:
Have you read the other SD Kill thread? Should come up in a search
Click to expand...
Click to collapse
Do you mean http://forum.xda-developers.com/showthread.php?t=1906058 ? If so, yes though the key difference for me is that my card doesn't seem to randomly unmount like most reports indicate. Also, it's very recent. Don't also see any possible solutions in there unless I'm missing something?
Anybody know the best way to really, I mean REALLY deep clean out the SD Card/Internal Memory of the XTZ? I've been running low on space for a while now, and no amount of SD Maid/Cleaner etc seems to help. I've gone through and deleted everything I can, but frankly I only really see 1-2gb of files, another 1-2gb of TB backups, and then <1 gb of miscellanous app data and what not. Nowhere close to the 16gb, even giving a little leeway for system/os size.
I therefore figure it has to be the internal memory/android secure -- something like that. Can anyone give me a good idea of how I might totally release all that storage?
Alternately, if anybody knows a way to TRULY zero out the XTZ -- rom/software wise -- I'd be willing to completely rebuild my setup from the ground up, just to get a bit more breathing room.
Thanks very much for any assistance/ideas, I really do appreciate it.
marlowe310 said:
Anybody know the best way to really, I mean REALLY deep clean out the SD Card/Internal Memory of the XTZ? I've been running low on space for a while now, and no amount of SD Maid/Cleaner etc seems to help. I've gone through and deleted everything I can, but frankly I only really see 1-2gb of files, another 1-2gb of TB backups, and then <1 gb of miscellanous app data and what not. Nowhere close to the 16gb, even giving a little leeway for system/os size.
I therefore figure it has to be the internal memory/android secure -- something like that. Can anyone give me a good idea of how I might totally release all that storage?
Alternately, if anybody knows a way to TRULY zero out the XTZ -- rom/software wise -- I'd be willing to completely rebuild my setup from the ground up, just to get a bit more breathing room.
Thanks very much for any assistance/ideas, I really do appreciate it.
Click to expand...
Click to collapse
Flash firmware with flashtool with all wipes or do wipes via recovery (need to be installed manually). Or you can try factory reset of device.
For stock 16Gb model, ~11Gb are free after clean reflash.
begin edit:
Eh, no one seems to have an answer. I'm just going to learn to live with it. If you found my post, may you have more luck than me.
end edit:
Lemme get the things out of the way that I don't think are particularly relevant:
I"m using a Samsung Galaxy TAB E, without the GSM slot, but this appears to be in google's area in particular, not Samsung's.
I'm using marshmellow, which might matter, but I bet this was never fixed, given how things like this work (mainly, once i rooted, i have gotten afraid of upgrading for fear that old apps i like quit working and possibly even loosing my root).
I had to replace the battery at one point (i doubt it's relevant, but apparently the camera autofocus bug involved what day of the week it was).
So, the actual problem. Smart Manager, powered by Clean Master, i can let that thing sit for hours or even days, and it'll never finishing checking how much space i have. I'm using adopted storage, not that it matters, because things appear to be installing to actual internal memory, anyway, because the actual space i have left is several gigabytes, but google play is saying i only have 1GB remaining, and it won't install updates that are only 200MB.... Meanwhile, I got a notification that I only have 2 or 3 GB remaining. If I use DF (via the Termux app), it tells me /mnt/knox has 1GB free, /storage/emulated has 22.9GB free, /efs, /cache, /persist, /firmware, etc are all incredibly low, but i think this was intentional. /su has 24.5MB, and /storage, /storage/self, /dev/sys/fs/cgroop, and the like are all reporting 704.5MB about.
The obvious conclusion to me is that DF is telling me the truth. I want to say that google play and other packages are using some sort of "free space cache" rather than actually calculating how much space is actually free on the device.
The question: How do i find said "free space cache" and forcibly delete/fix it and if it doesn't exist, how can I figure out what's actually on internal memory so i can move it and symlink to it with my root powers?
I have root.
This isn't my first rodeo with linux.
I have command line access through Termux.
Android Studio is way too bloated for my potato of a computer, but I do have access to gcc in Termux if necessary.