LOL my questions are never interesting enough to get replies, sorry its a boring question and my phone isnt broken, from now on all my threads will say help phone bricked lol. anyhow to hell with it, i have a 16gig card i have space galore, im backing up sd-ext.
So now that i run A2SD i will presumably back things up differently. It says that sd-ext takes a lot of space though. I usually just back up BDS. Can i still skip backing up the sd-ext? I will save space and all I will have to do is restore my apps and run A2SD zipalign when i restore right? no big deal and if it saves some space...?
I have found through MUCH trial & error, that if you are running DT a2sd, you need to back that up as well, & here is why:
Let's just say for whatever reason you are forced to restore a nandroid backup. If you're running a2sd & all of your apps were on the ext2/3/4 partition, but you didn't back up the sdext when you made the backup, when you try to restore the OS to the way it was, it (the OS) doesn't know the apps were actually on the sdext, & the symlinks created by a2sd get lost in the shuffle (for lack of a better term), basically wreaking havoc in the OS cuz it can't find the apps it thinks were still in /system/data & /data/data, when in fact they are on the sd card.
For me at least, not backing up the sdext would leave me stuck at the end of the boot animation... forever. Or, boot looping, or stuck on the splash screen (white HTC screen).
No matter how many times I pulled the battery, booted recovery, wiped caches, flashed the ROM over the top of itself, re-restored the nand backup, etc, etc, I was stuck.
At the time, I was using Amon_Ra recovery, in which you can select what to backup, & I wasn't selecting the sdext.
I've since switched to ClockworkMod v2.6.0.1 (mainly for the automation in ROM Manager), which backs up
everything by default, & is currently the only(?) recovery that is able to flash both
"Amend" &
"Edify" update scripts.
It is pretty much a requirement to back up the sdext if you are running the Dalvik cache on the sdcard, command:
a2sd cachesd or
a2sd cachesdreset, or you
WILL get stuck in boot loops, @ the splash screen, in boot animation, etc.
Personally, running Dalvik on the sdext was very unstable, & I didn't really see any difference in performance. I'm currently running the Dalvik cache on the /cache partition, command:
a2sd cachepart or
a2sd cachepartreset, on both VaelPak v3.2 RC1 and CM7-EX DeStRoYeR. Very fast, & very stable.
Sorry for the long winded post, but hopefully you can learn from "MY" mistakes, & not spend hours at a time trying to figure out WTF happened cuz all you did was reboot the phone... Lol!
