If that's really it, I wonder why you never see ads or reviews saying "This 32 core, 6GHz device with a 6" 4x HD screen can corrupt your data up to four times faster than the closest competitor"!
Seriously, why is this not part of the compatibility test (I realize it maybe a difficult thing to detect, but it's users' data at stake). Some of us still shiver from all the data storage issues that the original Galaxy S had. Curiously, I'm also getting - admittedly rare - reports of shared prefs values randomly changing, including some in files that the user can't touch in the app's UI. On the other hand, if this is flash memory going bad on some specific devices (as opposed to device models), then how does the user run chkdsk / fsck / surface scan / whatever to detect it? -- K 2013/9/20 Anthony Prieur <anthony.pri...@gmail.com>: > From my guess the database gets corrupted because of (some) flash disk > controllers that lie to the OS and do not flush/sync properly the FS before > crash/reboot, so even with transactions the DB gets corrupted in some cases. > > Le vendredi 20 septembre 2013 02:34:51 UTC+2, Kostya Vasilyev a écrit : >> >> Yes, but if the database can't be opened at sqlite level, it would only >> help the app know that, not recover the data... And there are other ways to >> detect that. Back to square one: why do they get corrupted in the first >> place? >> >> >> Nathan 20 пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ 2013пїЅпїЅ. 4:05:53 >> пїЅпїЅпїЅпїЅпїЅпїЅпїЅ: >> >> >> >> On Thursday, September 19, 2013 4:31:23 PM UTC-7, Kostya Vasilyev wrote: >>> >>> >>> http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/2.1_r2/android/database/sqlite/SQLiteDatabase.java >>> >>> Look for a method called onCorruption. >> >> >> It looks like we could, in 4.0+, define a custom DatabaseErrorHandler that >> could do something different. >> >> I have not done so. >> >> Nathan >> >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to android-d...@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 >> --- >> You received this message because you are subscribed to the Google Groups >> "Android Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to android-developers+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. > > -- > 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 > --- > You received this message because you are subscribed to the Google Groups > "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-developers+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
