[Defy Android Development] Antiga Prime:
The safest way to restore your data is using Titanium Backup, and extracting your apps/app data from the Nandroid backup. I've had that 80% of the times with these new builds, and I figure that if the data partition is corrupt, restoring the same data back will restore the same corrupt data, so it's pointless unless you only restore your actual apps and app data.

A few days ago I was on the 26/06 CM 10 build, and now I'm on the latest CM 10.1, and on both I've experienced sudden reboots, which have corrupted data in some way. On CM 10 it erased my google contacts once and swiftkey settings twice. On the current CM 10.1 build it rebooted suddenly just when I was running a script with Smanager to lock some apps in memory (namely Whatsapp), and just then I got an incoming Whatsapp message. I don't know if they are related, but right after reboot I saved a dmesg log and catlog.

I expected the dmesg log to be larger, but it just showed this:

<4>[ 80.215240] select 1863 (ndroid.settings), adj 12, size 7081, to kill
<4>[ 80.215270] select 2389 (dutta.superuser), adj 13, size 6559, to kill
<4>[ 80.215301] select 2578 (roid.automemman), adj 13, size 9574, to kill
<4>[ 80.215301] send sigkill to 2578 (roid.automemman), adj 13, size 9574
<4>[ 81.805633] select 1863 (ndroid.settings), adj 12, size 7081, to kill
<4>[ 81.805694] select 2634 (ng.overclocking), adj 13, size 6591, to kill
<4>[ 81.805694] send sigkill to 2634 (ng.overclocking), adj 13, size 6591
<3>[ 82.338409] init: untracked pid 2073 exited
<7>[ 82.667327] turning off regulator
<4>[ 83.308837] select 1863 (ndroid.settings), adj 13, size 7081, to kill
<4>[ 83.308898] select 2722 (m.rs.autokiller), adj 13, size 7437, to kill
<4>[ 83.308929] send sigkill to 2722 (m.rs.autokiller), adj 13, size 7437
<4>[ 85.531646] select 1863 (ndroid.settings), adj 13, size 7081, to kill
<4>[ 85.531707] select 2741 (tats_xdaedition), adj 13, size 8080, to kill
<4>[ 85.531707] send sigkill to 2741 (tats_xdaedition), adj 13, size 8080
<4>[ 87.889862] select 1863 (ndroid.settings), adj 13, size 7081, to kill
<4>[ 87.889892] send sigkill to 1863 (ndroid.settings), adj 13, size 7081
<3>[ 89.576171] init: untracked pid 2368 exited
<3>[ 89.843109] init: untracked pid 2421 exited
<3>[ 89.979949] init: untracked pid 2428 exited
<3>[ 90.499145] init: untracked pid 2455 exited
<3>[ 94.600830] init: untracked pid 2563 exited
<3>[ 95.244506] init: untracked pid 2675 exited
<3>[ 96.600769] init: untracked pid 2890 exited
<3>[ 96.601287] init: untracked pid 2898 exited
<3>[ 166.409973] init: untracked pid 7013 exited
<4>[ 222.585754] select 2222 (d.process.acore), adj 12, size 8599, to kill
<4>[ 222.585784] select 2699 (criptmanagerpro), adj 13, size 6797, to kill
<4>[ 222.585815] send sigkill to 2699 (criptmanagerpro), adj 13, size 6797
<4>[ 224.507629] select 2222 (d.process.acore), adj 12, size 8599, to kill
<4>[ 224.507690] send sigkill to 2222 (d.process.acore), adj 12, size 8599
<3>[ 227.315765] init: untracked pid 7101 exited
<3>[ 227.785675] init: untracked pid 7108 exited
<3>[ 228.023986] init: untracked pid 7132 exited
<3>[ 228.024017] init: untracked pid 7133 exited
<3>[ 228.048004] init: untracked pid 7137 exited
<3>[ 230.583526] init: untracked pid 7136 exited
<3>[ 230.781433] init: untracked pid 7143 exited

Which from what I've read, might be a booting problem related to init.rc. Catlog is attached.

Also, a bug I discovered in both the 26/06 build of CM 10 and the latest CM 10.1, is that I' turn on Airplane Mode between 3am and 5:30am, and after that when I turn Airplane Mode off I never get a signal, I've tried turning the radio off/on, changing from 2G to 3G and it won't connect, the only way to get it back up is by rebooting. This has happened for that last 5 or 6 days, so I know it can't be just a coincidence. Something is preventing the phone from getting a signal once it's been in Airplane Mode for a while.