On top of that, even applications with permission don't have control to write into the same *physical* location, because of wear leveling.
Basically, every time you write to an flash memory card location, the card actually places this data into a *different* physical location. This is because writing the same location repeatedly will wear it out. So to try to make the entire thing wear out at the same time, rather than one highly-used location wear out very early, the actual data storage locations are moved around on the chips. So: If you really care about erasing the data, what you want to do is put it through your shredder, and then incinerate it. For protection from more casual interlopers, just opening the file for read/write, positioning to the front, and replacing all the data may be adequate. If not, there really is very little middle ground. You can write until you fill up the filesystem, repeatedly, and hope for the best, or opt for physical destruction. On Jan 14, 9:18 am, Dianne Hackborn <hack...@android.com> wrote: > Fwiw, the limitation is not an issue of running in Dalvik vs. native code, > but the permissions / uid an application is running as. Third party apps > can not run with permissions to be able to do this kind of stuff. -- 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
