[Galaxy S II General] titanic_fanatic:
Hey Socim, I just want to thank you for your input :D I know your working on another device, and for you to take time to watch this thread and post your comments is extremely appreciated. So Thank You!

I thought about using the /preload partition (mmcblk0p27), but I wasn't sure that 26MB extra would be enough. Do you think it's enough? I was thinking that I wanted to at least double it from 100MB to 200MB, but that might be overkill, maybe the 26MB is enough. I think what I'll do is run a build with the /cache/dalvik-cache mounted to /system/dalvik-cache and flash the full gapps package (unmodified - all apps in /system/app) and see how much space the dalvik takes up after everything is setup. That should give us a better idea as to how much cache we actually need ;)

I'm going to re-work the gapps package to fix these FC's. This is a lot easier (and quicker) than my other suggestion of moving the dalvik-cache which I have already done successfully, but manually. for my suggestion of moving the dalvik-cache, this will take a little longer as I need to add the correct entry into the fstab file and I'm not exactly sure what that looks like right now since I will be binding the /cahce/dalvik-cache to /system/dalvik-cache. [MENTION=4896139]Socim[/MENTION], do you know what this fstab entry should look like?

On the VM notification, you say it's a small issue, but it's a big one to me. That was one of the most exciting parts about moving to cm-10.2 for me is that VM notification worked, so I'm very sad that it's not working for you. You said on G+ that your on Bell, so it can't be a carrier issue. All VM settings are pre-set in this ROM, so you couldn't have done anything there, and you previously checked to make sure those settings were correct and they were. A log would most definitly be helpful, although I'm not sure that an "error" is occurring and therfore, a logcat may not show anything. I will definitely have a look to see though.

You can send me your logcat by email to titanic.fanatic.xda@gmail.com. That should get you around the filesize restriction ;)

The E:unknown volume for path [/sd-ext] error is ok. The paths are managed differently in recovery and because the recovery is intended to work on many devices it runs checks for various variations of the same path, where /sd-ext exists on another device, ours is /external-sd. The recovery checks them all and is only letting you know what it couldn't find and we do not use /sd-ext so your good ;)

As per your second question about waiting until your apps are restored, it shouldn't make a difference as user apps dalvik-cache is stored in /data/dalvik-cache and are not the apps that are FC'ing. The system apps dalvik-cache gets stored in /cache/dalvik-cache and the problem here is that there is only 100MB there and more than 100MB of required space for the dalvik-cache there. The wiping of dalvik should happen after you boot for the first time and go through the initial phone setup (setup wizard). It seems though that I need to move more apps to /data/app in this gapps package so I'm re-working it right now. I'm just uploading new copies of the ROM and gapps. The updated ROM has the QuickSearchBox.apk removed from system as it's now in data and I have moved two more apps from system to data in the gapps package. Just tested it and it's working without FC's ;) Will post this as soon as the uploads are done!

A Note For Everyone

I will be fixing the issue of status error 7 in cwm on all ROMs. The fix here is to use the update-binary from my cm-11.0 ROM. This allows the Roms to flash on the latest recovery. I have not tested this on an old recovery, so there may be a side effect of not being able to use the older version of the recovery with the new update-binary. [MENTION=5306474]irenek[/MENTION], can you please let me know if this is the case for you as you are on the older version.

If it turns out that the update-binary are not cross-compatible, I'll have to sit down and think about how to get around it.