Hi Shane, I think the /cache/recovery folder gets used during the system recovery process. probably this is cleaned up after the recovery, so you may not see it all the time. You can refer the code (frameworks <http://androidxref.com/4.1.1/xref/frameworks/>/base <http://androidxref.com/4.1.1/xref/frameworks/base/>/core <http://androidxref.com/4.1.1/xref/frameworks/base/core/>/java <http://androidxref.com/4.1.1/xref/frameworks/base/core/java/>/android <http://androidxref.com/4.1.1/xref/frameworks/base/core/java/android/>/os <http://androidxref.com/4.1.1/xref/frameworks/base/core/java/android/os/>/ RecoverySystem.java <http://androidxref.com/4.1.1/xref/frameworks/base/core/java/android/os/RecoverySystem.java>) which seems to be the one creating this folder. One use case when this gets used is when user requests factory reset. This folder contains the command file which contains details on what needs to be done when booted into recovery mode (wipe the data, cache, package update etc..)
On Tuesday, July 8, 2014 8:42:04 AM UTC-5, spo...@gmail.com wrote: > > I have a custom device which I have ported Ice Cream Sandwich to and for > some reason the file system is missing the /cache/recovery directory. > How/where is this directory supposed to be created in the init sequence? I > have the standard permissions changes in the init.rc to change the > ownership, so I assume it should be created at some point before the > post-fs init calls. Any help tracking this issue down would be greatly > appreciated. > > Best Regards, > Shane > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
