[Samsung Galaxy Nexus] kenstyle:
Been on the 11/1 build for a while after having had to recover a saved build AND had to flash clean straight for multiple times (with CW 6.0.4.3 of course!) that still left me with recurring issues with the Rom.

Here's what I've learned after having experienced many heartaches with multiple reboots, safe recoveries, and fruitless reflashes with a few moments of the rollercoaster-heart-sinking-into-your-stomach feeling that you might've bricked your legendary GNex:

-The rom runs BUTTER SMOOTH as is. My phone would rarely have any hiccups, FCs, or random reboots as is if I leave it "stock."

-However, when you start tinkering with the mods in the Vanir customization menu, i.e. when you overclock the CPU, mess with the LED light settings, remove the Vanir boot animation, add Halo/Pie/Apps drawer, enable the brightness feature in the status bar, add the app destroy feature with the Back button, etc, THAT'S when the problems start to arise.

What do I mean by problems?

1) I'm talking about if you reboot your phone, it will NO longer boot up to the home screen. It loads up to the Google animation (doesn't even make it to the awesome metal Vanir animation), and then the screen blanks out. Holding the power button after that will NOT allow you to reboot the phone again, and even pulling the battery to boot into the Bootloader/Recovery to reboot the phone will not alleviate this problem. Wiping cache and dalvik cache, and restoring a previously and RELIABLY saved build in CWR will not fix the problem either. You will have to do a CLEAN flash from scratch to get your GNex working again.

2) The hotspot tether starts to act finicky after you tweak the Vanir customization settings, meaning that sometimes webpages will no longer load on your desktop/laptop/tablet anymore in which you would have to restart the Hotspot in order to get your webpages and Espn streaming highlights of the Denver Broncos to load again. I would NEVER encounter this problem right after a clean flash until I'd start to get "greedy" with enabling the kickass mods in the Vanir menu. I can't speak for which "certain" modification starts to make the phone finicky as I usually add/remove a bunch of features all at the same time, but all I can say is that the more you "tweak" the mods in the Settings menu, the more likely your Vanir build will produce hiccups.

3) The phone will have a hard time relocating the 4G signal upon entering a deadzone/tunnel/etc even having had turned off both LTE and Mobile Data and turning them back on afterward, but I believe this issue has already been addressed for some time by multiple users in this thread so at the risk of beating a dead horse, I will leave it at that. A quick and simple reboot that the developer has graciously programmed into Vanir will fix that problem, granted that you haven't made too many tweaks with the mods that would leave you stranded after the Google boot animation.

To the developer, please don't get me wrong because I'm not trying to ***** and whine about your Rom. I think this is by far one of THE best Roms I've ever flashed on my GNex, Paranoid, Shiny, and MMuzzy including. I just wish that there had been more R&D time placed into each "secure" build with the "enabling" of some of the amazing customization features in the Settings menu. If you're going to ask for my feedback as to which of the customization features is the "bad apple" of the group, my guess would be the CPU overclock feature, but again, that is simply a speculation. For some of you Vanir users who have been having issues with this Rom, the bottom line is this: it could simply be because you've been a little too "trigger-happy" with all of the mods and customization features, or perhaps flashing a custom kernel that you previously and religiously subscribe to that was never approved by the original developer of Vanir, and that is simply all that I'm saying so I will leave it at that.

I've since clean flashed the 11/1 build of Vanir, SU 1.65, and JB 4.3 Gapps again, and it's working brilliantly again. I'm going to continue to use this rom "stock" straight out of the box for reliability purposes. Hopefully this post was able to shed some light to the developers though I'm not sure how much it was able to pinpoint the exact issue in regards to enabling the customization features.

I just hope my post has been informative with some of the troubleshooting on here, no more and no less.

Edit again: all of the observations procured above were run on the stock kernel and radio. I'm not the type to run a custom kernel or radio unless the developer of the rom had given it his blessing.