> 1. Have you been getting reports of problems from Nexus One owners? In > other words, is this a DROID/Milestone thing or a 2.0+ thing?
Nope, Droid/Nilestone only, not Nexus One. I had one possible report from an HTC Hero owner, but have yet to confirm. Will follow up. > 2. Are you writing other local files directly (e.g., using File objects > and java.io)? Are you sure you're not clobbering your files yourself by > accident? Nope, SQLite and SharedPrefs only. > 3. Since you mentioned rooting the phone and looking at directories, I > assume these files are stored on the built-in flash, not the SD card -- > right? That would eliminate Mr. Thomas' comments regarding FAT, because > the on-board flash is not FAT. Correct - internal storage only. Gets stored in the standard app data directory - /data/data/com.preinvent.batteryleft/ > > It must be a filesystem problem (delayed writes?), or something buggy > > in the underlying sqlite code. > > Can't be the latter, as that would not affectSharedPreferences. I now believe that the SharedPrefs issue was a red herring. Since I set all my app preferences to use persistent storage (I didn't realise this was NOT the default) I only experience problems with the DB. The most recent DB failures have not affect my shared preferences. The reason they were both getting lost is that when the DB gets corrupted, my process was killed, losing all non-persisitent shared prefs. ie lost SharedPrefs was a consequence of my process being killed which was a consequence of the DB corruption problem. > That probably won't help. Your reported symptoms indicate that multiple > file types (SQLite databases and shared preference XML files) are being > harmed. You could switch from SQLite to JSON files, and those will may > well get trashed too. As above - I don't think Shared Prefs are an issue now. > If you can get a database in the "database disk image is malformed" > state, we can examine it to figure out how it is damaged: I can try.. problem is that Android deletes the DB file as soon as that error occurs so I don't know how to get the malformed DB. -- 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 To unsubscribe from this group, send email to android-developers+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
