OK I came across this problem last month & tried to find a solution. I discovered many posts to the same problem however I was only able to fix it by doing a factory reset. The problem has come up again & I'd rather not reset it again. It only comes up after numerous picture uploads to Facebook. Until I do that my phone runs fine. I'm running Open Kang if that makes a difference. Given this information does anyone have a suggestion as to how to fix it? It was suggested that I flash a new ROM as maybe the one I have is too big? Starting to get extremely frustrated with a phone I've only had since April & really know nothing about
Sent from my SGH-T959 using xda app-developers app
Mentalmama said:
OK I came across this problem last month & tried to find a solution. I discovered many posts to the same problem however I was only able to fix it by doing a factory reset. The problem has come up again & I'd rather not reset it again. It only comes up after numerous picture uploads to Facebook. Until I do that my phone runs fine. I'm running Open Kang if that makes a difference. Given this information does anyone have a suggestion as to how to fix it? It was suggested that I flash a new ROM as maybe the one I have is too big? Starting to get extremely frustrated with a phone I've only had since April & really know nothing about
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
This is (as others suggested) a problem with the ROM you have installed. There really is no way of getting around a wipe, but you can download an app called "Titainum Backup" and backup your apps from there. Once you get into your new ROM, simply download Titainium Backup again and restore your apps.
As far as fixing the problem goes, I would reccomend using ODIN to flash back to stock, then flash CM9. (However, I am sure that flashing from your current rom directly to CM9 would work just as well)
The real reason this is occurring is the mounting of the /datadata simlink to the /data/data partition, this is actually in the kernel and sets it when flashing, not the rom. That partition stores the data for applications, and continues to grow as apps run. Often times when you sync alot of emails it will also fill the partition when its mounted as /datadata, so that makes sense with your pic uploads to facebook, now I'll tell you why.
Early on in ICS builds, we had two schools of thought. If you mount with the /data/data partition, you have essentially 2GB of space for that app data, however, this comes at the cost of decreased performance and much slower application response times. If its mounted with /data/data symlinked to /datadata, it clips that partition at about 180MB, a lot smaller, but the increase in performance is phenomenal.
So it was damned if you do (slow response times) or damned if you don't (less space) for those of us in the rom game. I think most (myself and DD included) made a conscious decision after lots of testing, to use /datadata with less space, for faster performance.
You may be easily able to resolve it by performing some simple app maintenance. On apps like email and gmail, set your sync interval down to a few days, uninstall unnecessary applications, and with facebook, I don't use it myself, but try clearing its cache if there is a setting for that, or go into apps in settings, and clear the data for the application. You may have to sign in again, but it should not effect your uploaded content, merely clear the local cache on the phone freeing up that /datadata space.
Hope this sheds some light on the issue for you, and how you can avoid it or remedy it going down the road.
Sent from the ICZen Experience
Br1cK'd said:
The real reason this is occurring is the mounting of the /datadata simlink to the /data/data partition, this is actually in the kernel and sets it when flashing, not the rom. That partition stores the data for applications, and continues to grow as apps run. Often times when you sync alot of emails it will also fill the partition when its mounted as /datadata, so that makes sense with your pic uploads to facebook, now I'll tell you why.
Early on in ICS builds, we had two schools of thought. If you mount with the /data/data partition, you have essentially 2GB of space for that app data, however, this comes at the cost of decreased performance and much slower application response times. If its mounted with /data/data symlinked to /datadata, it clips that partition at about 180MB, a lot smaller, but the increase in performance is phenomenal.
So it was damned if you do (slow response times) or damned if you don't (less space) for those of us in the rom game. I think most (myself and DD included) made a conscious decision after lots of testing, to use /datadata with less space, for faster performance.
You may be easily able to resolve it by performing some simple app maintenance. On apps like email and gmail, set your sync interval down to a few days, uninstall unnecessary applications, and with facebook, I don't use it myself, but try clearing its cache if there is a setting for that, or go into apps in settings, and clear the data for the application. You may have to sign in again, but it should not effect your uploaded content, merely clear the local cache on the phone freeing up that /datadata space.
Hope this sheds some light on the issue for you, and how you can avoid it or remedy it going down the road.
Sent from the ICZen Experience
Click to expand...
Click to collapse
Br1ck'd to the rescue! I knew you still lurked these threads!!
Sent from my GT-I9000 using xda premium
Related
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
yelped said:
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
Click to expand...
Click to collapse
Delete the data.img, let the system create a new one. Problem solved.
So it got corrupted? I feared so. At the rate I'm re-creating Data Images, I should buy the Pro version of Titanium Backup for Batch Restore.
yelped said:
So it got corrupted? I feared so. At the rate I'm re-creating Data Images, I should buy the Pro version of Titanium Backup for Batch Restore.
Click to expand...
Click to collapse
That's what I did! I found myself using the app so frequently, I decided to pay for it.
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
rpierce99 said:
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
Click to expand...
Click to collapse
Yea, I always forget that. I haven't had to blast out a data.img in a while tho... Hrm.
yelped said:
Hi, I'm running the latest rootfs and Ril on Rhod400, even though this issue is almost definitely not related. I think that the battery died in middle of the night (I forgot to plug it in), and when I turned it on after charging it, a lot of apps started to Force-Close. This happens even after a reboot.
Thanks for all the help.
Click to expand...
Click to collapse
Happened to me also after it paniced and rebooted one day. I had to install all of the apps that force closed over again after uninstalling them. Seems like info got corrupted. I didn't want to start from scratch, especially since I just successfully got my work VPN working, so I just spent the time to uninstall and reinstall the stuff as I go. Have no clue what causes this other than something got corrupted.
slickdaddy96 said:
Happened to me also after it paniced and rebooted one day. I had to install all of the apps that force closed over again after uninstalling them. Seems like info got corrupted. I didn't want to start from scratch, especially since I just successfully got my work VPN working, so I just spent the time to uninstall and reinstall the stuff as I go. Have no clue what causes this other than something got corrupted.
Click to expand...
Click to collapse
I ran into a similar issue. My phone hard locked after running Android for the better part of a day. When I rebooted it ran extensive disk checks on the system. It still does every time I boot and I am get force close messages constantly. Windows also found and fixed errors with the FAT32 partition on the card. It's possible my card is dying but I also didn't notice any of that until the forced reboot. It didn't say what file was damaged but I can take a guess.
I believe that the FAT32 file system on the card was corrupted because files were open when I was forced to reboot. Because the linux file system is hosted as a file on the fat32 partition, it is subject to damage if the host file system gets messed up. It's sort of like when MS offered the option in DOS to compress your hard drive. It was all stored as a giant compressed file on your disk. If something happened to the integrity of that file it caused all sorts of problems.
This is why I use a partitioned build...
might be a stupid question but what is that ^
manny05 said:
might be a stupid question but what is that ^
Click to expand...
Click to collapse
Instead of using looped files (system.ext2 file is really an entire file system that is 'loop mounted' within Linux/Android) you use native partitions.
So a separate partition for data, separate partition for system, etc. It's a little more difficult to setup, but in theory it causes less corruption. Not sure if it's true or not, hyc is pretty convinced it does .
arrrghhh said:
Instead of using looped files (system.ext2 file is really an entire file system that is 'loop mounted' within Linux/Android) you use native partitions.
So a separate partition for data, separate partition for system, etc. It's a little more difficult to setup, but in theory it causes less corruption. Not sure if it's true or not, hyc is pretty convinced it does .
Click to expand...
Click to collapse
I've been running with the same data partition since the middle of January, haven't needed to recreate it even once. It boggles my mind how often you tell people to blow away their data.img and start over whenever they run into problems. That just ain't right, and an approach that encourages that style of problem-solving is inherently flawed, IMO. And a build layout that leads to that type of solution is also inherently flawed.
Plus the simple existence proof - my /data partition is fine, despite having reinstalled /system several times, switching between original FRX05 and FRX06, rewritten rootfs scripts, plus all of the built-from-scratch system images I've tested, replacing framework.jar, etc. etc... My SDcard has seen a lot of churn, but all of my downloaded apps, settings, and data have come thru unscathed.
A couple times I've needed to run fix_permissions. But now with my current framework and rootfs that does a clean shutdown and unmount of /data, I haven't needed that in a while either.
Oh, and also, with a partitioned build, you get full use of USB mass storage. Everything just works.
highlandsun said:
I've been running with the same data partition since the middle of January, haven't needed to recreate it even once. It boggles my mind how often you tell people to blow away their data.img and start over whenever they run into problems. That just ain't right, and an approach that encourages that style of problem-solving is inherently flawed, IMO. And a build layout that leads to that type of solution is also inherently flawed.
Click to expand...
Click to collapse
I agree, it's horrible troubleshooting - but it works, and until we get a solid fix then there's really not much to do...
I know you love your partitions, but that's not going to be for everyone. Anyone can do it, and how many do?
highlandsun said:
Everything just works.
Click to expand...
Click to collapse
LOL at this statement. I won't poke holes in it, c'mon guy, that's just silly.
arrrghhh said:
LOL at this statement. I won't poke holes in it, c'mon guy, that's just silly.
Click to expand...
Click to collapse
Ok fine. 500 patches later, and everything works...
Sent from my TP2 using Tapatalk
highlandsun said:
Ok fine. 500 patches later, and everything works...
Click to expand...
Click to collapse
Heh, much more accurate statement .
Also good to note - everything works, related to USB mass storage, etc. This isn't some magic voodoo fix for BT, so don't take this out of context people!
rpierce99 said:
Advanced users willing to do a little research will also find that sometimes the fix_permissions script will fix your data.img in these situations, it fixed mine a few days ago.
Click to expand...
Click to collapse
Nearly all other post-crash forceclose issues seem to be database corruption.
Android seems to like to store a LOT of stuff other than contacts (including call logs) in the contacts database. As a result it tends to be more prone to corruption.
Piece of advice - when complaining about an issue like this where obtaining a logcat is possible, please do so. (A logcat would be able to narrow down exactly where your problems likely were.)
DB corruption can still happen even on partitioned builds. I forget where the best HOWTO for this is, but it involves partitioning your SD card such that:
Partition 1 is FAT (main sdcard stuff)
Partition 3 is ext2 (system partition)
Partition 4 is ext2 (data partition)
I can provide a reasonably good HOWTO for doing this on a Linux box when I return from business travel, can't help the Windows-only users.
fix permission script? where can i find more about this?
I loaded CM 7.1 stable on my Fascinate a couple months ago and sometime there after I started getting Force Closes all over the place.
Rebooting my phone only seemed to temporarily alleviate the issue for an hour or so, but shortly after it would start occurring again. It wasnt until I opened Touchdown that I found the potential cause as it reported I was "Low on space". I found this pretty odd seeing as I had several GBs free on both internal and SD storage.
After searching around a bit I believe it's my cache thats filling up. I ran Clear Cache in CWM it cleared up the issue for several days but eventually it starts occurring again.
First question: is clearing the Cache via CWM on regular intervals going to hurt anything?
Second (and more important) question: Is there any way to fix this without going with a different ROM?
Thanks a bunch in advance!!
I got it too!
I'm having the same issue, or I believe I am. You get a notification saying your low on space, and you can't receive any txtmsg's? Once you clear up the space the msg's come through fine.
I was using the stable for a long time.. and didn't get the error, and then I flashed the latest nightly and that's when I got the error.
I don't think the nightly is what caused the error, I actually believe it's pure coincidence. I've managed to keep in under control and can fix it when it happens.
I clear my cache as well, but I found out that the /data/data also needs some cleaning to get rid of the error. When I free some space in the /data/data I don't even need to touch my /cache at all.
I will post any other findings... info.. etc.. that I find.
Maniac
your datadata folder is full most likely. You can try uninstalling some apps, or try running ng cache cleaner from market, or read this thread and try this tweak JT posted!
http://rootzwiki.com/topic/5635-problems-with-datadata-causing-force-closes-for-google-apps/
A novice question Im sure, but whats the best/easiest way to see how much free space is available on these partitions?
use the disk usage app from market.
Hey guys,
My phone was quite fast and responsive when i first bought it. But now aftre 9 months of use i have found that it has slowed down. I shifted from GB to ICS but that hasnt made any difference. The load up of contacts takes especially long.
I was woundering if like in computers we defragment the HD do we need to do the same on phones ocasionaly.
Please let me know if there are apps for this or any solutions.
If u do this u can break ur phone
Sent from my GT-I9100 using xda premium
if your device has become slow, you might want to think about performing a wipe / factory reset every once in a while. also, delete contents from your sd card, apart from music, videos and pictures.
defragmenting from a pc won't help, but also won't break your phone.
The filesystem that Android uses doesn't fragment like Windows' one does, therefore defragmentation isn't possible. You could try clearing up some space though. E.g. deleting apps, music, photos etc.
Sent from my GT-I9100 using XDA
do like mine..
You can download DX Tools Optimizer from Playstore
It's free & has all of the answers of your asking about..
Go thru w/ it & u'll find much fun tools u'll need..
But don't forget to press thanks...
vurp0 said:
The filesystem that Android uses doesn't fragment like Windows' one does, therefore defragmentation isn't possible. You could try clearing up some space though. E.g. deleting apps, music, photos etc.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
only half true. sure, the filesystem on the system partitions can not be defragmented, but they are not directly accessible from a windows pc anyways, i believe the op was talking about /sdcard/ and the external_sd/ or /emmc/, which usually are formatted in fat32 and can be defragmented. if he copied several things simultaneously, it might even be fragmented.
Check the free space available on the internal sdcard - my Wife's GSII had a similar problem where it would almost grind to a halt. It turned out the sdcard was full, and transferring the photos/videos off the 'phone returned performance to normal.
Thnks all. I think they are good suggetions and i will try them out and let you know the result.
Phone freezes, reboots, or does "nothing" at all when moving app/s to SD Card
Ah, the age old problem with moving apps.
I recently found my way back to a PA, AOKP, CM ROM (Jellybam).
Unfortunately, I have some nerve damage in my hand. Since the invention of the 4.2 JB keyboard, I've been able to use my Note more frequently, and thoroughly. There are various reasons why I need to use this ROM in particular, one of them being that customizability is a necessity, and Roms like Avatar, Chameleon, and PACMan just aren't there yet, either in performance, or stability. I spent the whole day looking for an alternative, but none came closer to meeting my needs, while still being callable of daily driving.
My issue is, I have a large collection of apps, and I'm leaving for vacation. Many of them hold an extremely large cache of offline data, while others are games that have 100+APK files, and 1-2GB of OBB or other SD Data. I still have a ton of apps I need to install, and the inherent 2gb limit of Android is seriously going to make my life tough. My family is counting on me for maps, itinerary, and even entertainment.
These apps could easily be installed if I could simply move a dozen or so of the largest apps, and a dozen or so of the medium sized apps to the SD card.
However, upon clicking the "Move to SD Card" button in the app info panel, one of a few things happens. The button might Greg out, and say "moving" for hours, and never get there, the phone could freeze, requiring a reboot as soon as I try to back out, hit the home button, or do anything except scroll; or the phone might freeze and reboot, or just reboot immediately upon clicking the move button.
Occasionally, I'll be successful. I've tried clearing a the data from a few system apps, like "Media Storage", and I'm not sure if it worked or not, but over a period of around ten restarts, I managed to get three apps transferred to the "SD Card", although they definitely were not the apps I needed to move. The ones I managed to move were ones I chose at random while I flashed several kernels, root .zips, recoveries, mods, etcetera. They were all less than 25mb.
I'd owe you forever, and would be willing to assist you on a project, or finding a fix for some of your own technological ailments, if you can help me with this.
A search of XDA, and Google's hive-mind brings up a couple thread where the issue is discussed, but those were from years ago, and only one was on the same ROM as I am, and that thread was deleted--all that remains was a description and the details of it in the search index.
So, a penny for your thoughts? Even if you don't have anything concrete, the discussion, suggestions, and conversations might help.
Mad thanks all around.
Jamesyboy said:
Ah, the age old problem with moving apps.
I recently found my way back to a PA, AOKP, CM ROM (Jellybam).
Unfortunately, I have some nerve damage in my hand. Since the invention of the 4.2 JB keyboard, I've been able to use my Note more frequently, and thoroughly. There are various reasons why I need to use this ROM in particular, one of them being that customizability is a necessity, and Roms like Avatar, Chameleon, and PACMan just aren't there yet, either in performance, or stability. I spent the whole day looking for an alternative, but none came closer to meeting my needs, while still being callable of daily driving.
My issue is, I have a large collection of apps, and I'm leaving for vacation. Many of them hold an extremely large cache of offline data, while others are games that have 100+APK files, and 1-2GB of OBB or other SD Data. I still have a ton of apps I need to install, and the inherent 2gb limit of Android is seriously going to make my life tough. My family is counting on me for maps, itinerary, and even entertainment.
These apps could easily be installed if I could simply move a dozen or so of the largest apps, and a dozen or so of the medium sized apps to the SD card.
However, upon clicking the "Move to SD Card" button in the app info panel, one of a few things happens. The button might Greg out, and say "moving" for hours, and never get there, the phone could freeze, requiring a reboot as soon as I try to back out, hit the home button, or do anything except scroll; or the phone might freeze and reboot, or just reboot immediately upon clicking the move button.
Occasionally, I'll be successful. I've tried clearing a the data from a few system apps, like "Media Storage", and I'm not sure if it worked or not, but over a period of around ten restarts, I managed to get three apps transferred to the "SD Card", although they definitely were not the apps I needed to move. The ones I managed to move were ones I chose at random while I flashed several kernels, root .zips, recoveries, mods, etcetera. They were all less than 25mb.
I'd owe you forever, and would be willing to assist you on a project, or finding a fix for some of your own technological ailments, if you can help me with this.
A search of XDA, and Google's hive-mind brings up a couple thread where the issue is discussed, but those were from years ago, and only one was on the same ROM as I am, and that thread was deleted--all that remains was a description and the details of it in the search index.
So, a penny for your thoughts? Even if you don't have anything concrete, the discussion, suggestions, and conversations might help.
Mad thanks all around.
Click to expand...
Click to collapse
So, after some more screwing around, I found that indeed, clearing the data for the "Media Storage" app temporarily fixes the problem for all but 2 minutes. I'm woefully unprepared to understand the app-- particularly whether it's a contaner of sorts for media thumbnails, tags, etc...or...whateer....the...other....option.....is.....
I suppose i'll try pulling a TiBu Pkg of a "Media Storae" app from another ROM, import it into this one, and fire it up.
Before i cleared it, the app had 27mb of data and cache, and aftered i cleared it, it slimmed down to 7. Within a minute or two, it was back up to 27mb, and my phone was freezing on the transfer of apps to my sd card again.
Possibly your phone is just too low on memory and you don't have enough memory to do the move to sd card. Try temporarily removing some apps and then move your big ones and all that you can and then install the apps back.
Or you could backup a few apps with TB that you don't use much which will free up some memory. Then when you need the app use TB to restore it quickly.
Cache can be a killer. Just removed a little over 200MB of cache files myself this morning. Try a good cache cleaner like "Clean Master."
If your phone is loaded with media files then your media data will be that high. Sounds like to me your phone is simply overloaded.
First of all, I know this have been asked numerous times but I only got more confused of the threads that were aboout this...
My S2 has been showing the message "Insufficient storage available" for the past 8 or 9 months, but it has gotten worse since. At first I couldn't download any big apps, now I can't even download apps that are small (like 5mb). Anyway, I don't exactly know how it started but it probably has something to do with Android 4.x.x ... It has gotten really annoying because I needed to do some necessary updates on certain apps (WhatsApp for example) and I can't use them anymore because of this problem.
It's probably something with System Data. (yes I know I still have about 600mb of apps, but those are either apps I really need or apps that are on my phone as a default.) But as far as I know, I can't reach that System Data... It's just a chunk of (useless??) data that's just there. I don't really what it consists of, because the app (DiskUsage) I used to look into me storage won't let me open that map (as can be seen).
I WANTED TO SHOW A PICTURE HERE BUT I CAN'T SINCE I'M A NEW MEMBER BASICALLY, THE SITUATION IS LIKE THIS:
DATA [2015 MB]
- APPLICATIONS [574 MB]
- SYSTEM DATA [1397 MB]
- FREE SPACE [what's left. this ranges between ~90mb and ~10mb since I clear cache now and then]
I've been to a store with this problem and they basically said that there is nothing I can do... Is there really nothing I can do? I tried wiping my cache but that didn't do enough. I usually clear 90mb of cache when I do this once in every 3 days (after those 3 days I have about 5mb of space left), but like I said, this doesn't do enough.
Any suggestions? Sorry again as I know there are some threads already about this, but I looked into them and didn't really got a lot out of them...
Thanks in advance.
Did you try *#9900# on phone call menu?
From what I think, it's because of your application files. For example if you always use whatsapp(what I mean here is, if you keep on chatting), it'll store your chat messages into your phone memory which will 'eat' your memory bit by bit. And also, this is from what I've experienced, whenever you uninstalled an application, let's say TubeMate, you'll see tubemate's folder(s) is/are still inside your phone.
So what I'm trying to suggest here is, whenever you want to clear some space, try to delete some of your whatsapp chats or maybe other chat apps that stores chat messages if you don't want to uninstall other app. And when you want to uninstall an application, make sure you delete the app's folders inside your phone.
I'm don't know much about phone memory, so if I'm wrong about it, correct me
p/s: If you can't post link your image since you're new here, you can put your images as attachment.
Artwing said:
Did you try *#9900# on phone call menu?
Click to expand...
Click to collapse
Why haven't I thought of that 2 months ago... I thought that option was only for clearing my storage of calls and texts and since I don't call or text a whole lot, I thought it wouldn't be beneficial.
I've cleared over 1,2 GB by this. Thanks for your help, really appreciate it!