On Mon, Jan 12, 2009 at 10:55 PM, Dianne Hackborn <[email protected]> wrote: > > Another place to look -- there is a filesystem bug that can sometimes happen > where unlinked files are not recovered. Here is the comment from an > engineer who knows more about it: > > "They can easily tell by looking at the number of unlinked files for the > user partition in /proc/yaffs. If that number is very large, then they can > reboot the device, wait a few second after they see the android, then pull > the battery again. That should make the number of unlinked files drop back > down. If that number isn't very large, then it is probably something else."
I read about this on the net -- I thought it was some sort of a dark joke or something -- apparently not :) I did pull the battery though - nothing (good) happened. This developer you're talking about - can he elaborate on how the "battery pull trick" actually works -- I'm genuinely interested. > > Unfortunately it looks like only root cat read /proc/yaffs (though that > seems a little overly restrictive). However you can try the pulling the > battery trick and see if that helps. > >> >> Well, the over-the-air patch @#$%ed root access so I can't look anywhere. > > The /data/local directory is owned by the shell user, so you don't need root > for that -- just "cd /data/local" and look at what is there. There is a > chance that some temp .apk files have been left there from "adb install", or > some other files created by other shell sessions. I already reset the phone but if I encounter this again I'll check there (+ I'll have root this time :) Thanks, Stoyan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
