Okay, so would anyone be able to point me in the direction of the best ROM/Kernel/other things to flash out there? Also, a guide on how to install Kernel stuff would be awesome, if someone could point me in the right direction there. Also, In terms of the data drops/3G disconnects, what would be the best way to avoid those? I've heard some speculation that it's due to 2SD scripts, but I'm not sure. I've used the EXT wipe tool that someone posted earlier.
1. If you don't mind the slightly annoying bug in which your battery pct level doesn't change while charging or discharging unless you let your phone go to sleep, turn your screen off and then on...I suggest the 4/14 build of PAC (somehwere in this thread) and the latest Test 80 of bigsupersquid's 3.0.8 kernel. The battery drain is about the same with the original 2.6 kernel that is packaged with the ROM. However, the memory management is far much better and no random reboots (I am on 768/600 Interactive)! Data drops typically will not happen with this kernel as opposed to the one pre-packaged (hell the 3.0.8 kernel hooks on faster after a drop or made/answered call), but where I live, Sprint is in its 3rd and final stage of Network Vision deployment...
2. How to install the 3.0.8 kernel? It is in the Optimus V thread and comes with a pair of keyswaps in case you have the OptiS. But the short of it is:
a. download the Test 80 kernel, put it in root of your SD card (sure you know how to transfer things from your computer to sd card, yes?). For PAC, there's a ramdisk patch for it otherwise you get bootloop, download that to and get it on your sd card.
b. reboot into your recovery.
c. it is: pre-flash wipe (system, data, cache), wipe dalvik as well too. then flash PAC 4.14 BUILD. Then flash Gapps. Then flash the Pac ramdisk patch. Then wipe cache and dalvik. Then flash the 3.0.8 TEST 80 kernel. Then boot.
d. After a reboot or two, you can flash the FIXED cronmod int2ext script. Obijohn's will bootloop the whole setup. However, after flashing, you'll need to reboot twice. Once for the script to boot...and again to refresh the data connection. Seems to bork it on the first reboot after flashing. Second reboot fixes it.