Here is some more information on what's happening. There is a problem in yaffs2 where unlinked files are not removed from a check-pointed filesystem. Whenever Android sleeps, it check-points the filesystem. When you uninstall an app the files are unlinked. If the device then goes to sleep before the unlinked files are actually removed, they won't be.
The proper way to work around this it to shut down your phone by holding down the end call button until you get a dialog asking to shut down your phone. Turn your phone back on. BEFORE your phone can sleep after it reboot, shut it down again. This will clean your unlinked files. This works because when the system starts it has no check-points in the filesystem and one won't be created if the system doesn't sleep. The unlinked files are actually removed then when the file system is mounted or unmounted (I'm not sure which it actually is). Cheers, Justin Android Team @ Google On Jan 12, 1:56 pm, "Greg White" <debauchedsl...@gmail.com> wrote: > On Mon, Jan 12, 2009 at 4:54 PM, Joel Knighton <joel.knigh...@gmail.com>wrote: > > > Okay, someone who can replicate this problem, can you perform a "cat > > /proc/yaffs" and then post the output here. Curious to see the YAFFS > > debugging info. > > I don't have the output handy, but I went from ~12K unlinked files to ~2K. > This makes a difference. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
