Thanks to drezliok, mmarz and LeslieAnn for explaining some of the issues with flashing this on your phone which was previously flashed with Xionia. I will explain further.
Thanks to mmarz for posting a "fix" to flash. I don't have a V and haven't tested it (or pulled it apart to see what it does) but as people test it, if it makes sense I can add it to the top post.
I'm also considering whether to change the picasticks .zip or offer an "alternate" version. Many thanks to LeslieAnn, I've been working with her to make a build of Aphrodite with picasticks preinstalled, and in doing so have learned a lot about the various Optimus V hacks and the the history behind them, which coming recently from the S I didn't expect.
OK, so ... the basic issue is this. The Xionia kernels, built for the S, require various workarounds to swap the buttons and "fix" the accelerometer to work with the V. These are problems you guys solved weeks ago to make Xionia run well on your phones. These fixes go into the initial filesystem ramdisk. The ramdisk and kernel together make up the /boot partition (called boot.img when it's a dumped to a file image).
I came from the S where making these changes to the ramdisk are unnecessary, so the ramdisk is "clean". When my AnyKernel updater runs, it takes your *existing* ramdisk and merges it with the new kernel. So, if you have a "clean" ramdisk and add my kernel to it, everything's good. Ditto if you're coming from a ROM like Aphrodite Extra Pure which flashes a "clean" ramdisk.
The problems occur when your ramdisk has the workarounds: i.e., if you most recently flashed a Xionia boot.img (Xionia AnyKernel doesn't touch the ramdisk) or a ROM (probably most V ROMs) that includes these workarounds.
So, while distributing the kernel as AnyKernel worked great on the S (because there aren't any inconsistencies in people's ramdisks), on the V it might make more sense for me to give you a whole boot.img (including ramdisk) so that when you flash my kernel it will "just work".
The only problem with that is, you or your ROM might have made mods to the ramdisk that you like (boot animation, edits to default.prop, edits to init.qcom.post_boot.sh), and for me to just wipe those out would be bad. (This is why AnyKernel in the first place!)
I could do like zefie does and have both boot.img and AnyKernel editions, but I think that's too confusing because I know the first time he did that, I was like WTF does that mean? and probably didn't make a good decision about which one to use.
I think the right thing to do is along the lines of what mmarz has done, and to post a separate update .zip to give people something to optionally flash to restore a "standard-like" ramdisk. i.e. stock ramdisk but with ro.secure=0 in default.prop since *every* ROM does that.
Anyway, let me know what you think.
p.s. this is also why just having my kernel built into a ROM like Aphrodite will be great, because then we can make sure everything will just work for people who flash the ROM.