That's because your phone uses a sane filesystems that takes into account this use case and isn't writing constantly (write one byte, the disk writes a whole erase block). This doesn't protect you from eventual disk corruption. The wear leveling bad-block type tables will eventually corrupt/run out of memory loooong before your disk space is eaten by bad blocks.
http://arstechnica.com/information-technology/2010/12/ext4-filesystem-hits-android-no-need-to-fear-data-loss/ "Most Android devices currently use YAFFS, a lightweight filesystem that is optimized for flash storage and is commonly used in mobile and embedded devices." My production Beaglebone image does not support this. "Developers who are accessing the filesystem directly will have to be mindful about Ext4's buffering behavior and make sure that the data is actually reaching persistent storage in a timely manner so that it won't be lost in the event of a system failure." It is now an issue with Android! "T'so says that there isn't much need for concern. Google and the handset makers will catch platform-level filesystem reliability issues, ensuring that the high-level storage APIs are safe." Is the API you use for disk writes safe? Nope. -Brandon On Thu, Mar 27, 2014 at 10:26 AM, rh_ <richard_hubb...@lavabit.com> wrote: > On Thu, 27 Mar 2014 07:41:11 -0500 > Charles Steinkuehler <char...@steinkuehler.net> > wrote: > > > On 3/26/2014 10:22 PM, Yiling Cao wrote: > > > Thanks Brandon for your experience. I do agree with that better to > > > put whole disk read only. > > > > > > But how do iPhone and Android survive? Esp for those Android > > > phones? They are very prone to sudden power removal as well. > > > > What? These devices are battery powered, and other than opening the > > case and physically removing the battery they are guaranteed enough > > power to do a proper and orderly shutdown. > > I pull the battery on my android frequently doing devel. Never had any > problems. I pull the plug on my BBB all the time too, at least once/day. > No problems. > > For people having issues I would suspect a problem elsewhere. > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/dV0ctlQykYI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
