Recent content by MWisBest

It'd be a nice project over break to try and get it going on my LG Vortex. I want to see what was done with the androidarmv6 sources to get it built and booted on the Optimus V as the hardware isn't too different between the V and Vortex.

Would be nice to see the source code for what you have so far put on GitHub.

tdm, do you know if the voltage to the CPU is locked via the kernel or the hardware? It'd be interesting to adjust the voltage of this, because with a little more juice I'm certain I could push 800+ MHz (I used to only be able to do 748MHz, but recently found out with your kernel that 768MHz is...

tdm, were there any changes between beta2 and the beta3pre that didn't install besides trying to make the ROM flashable on every device with 1 zip?

Are you wiping /system? Make sure you do that...

Things have always been able to be received... By the way, the build.prop doesn't include the fixes that Powmining's zip added. >ro.product.brand=LGE >ro.cdma.home.operator.numeric=310004 >ro.cdma.home.operator.alpha=Verizon Those last 2 are in 3 things all next to each other too...

I don't understand your last sentence at all. Also, MMS is not working for me. Sending, that is. I've always been able to receive them fine, before any "fixes" were added or anything. And in that fixed config, I think the max sizes are messed up. I was able to send screenshots (480x320) when I...

Seeing as how my post was completely ignored, here it is again... FYI, I have not had a single random reboot on this ROM at all. I have not done anything to my build.prop either. EDIT: Also, seeing all you people running stuff like 600/480 on InteractiveX (not specific to anybody, just an...

I decided against sticking those changes into my build.prop. There were a decent amount of people reporting issues with it, and I haven't had any issues with my current setup anyway. Couple things to report: On AOKP, do NOT use the Honeycomb lock screen. I don't know how to explain it, but it...

Something that may help improve battery life is using the SmartassV2 CPU governor. Set your clocks to ???/122. After I had mentioned it in the VS660 thread, a user replied and stated that after using the SmartassV2 governor he had experienced much better battery life and has not had any lag that...

Something that may help improve battery life is using the SmartassV2 CPU governor. Set your clocks to ???/122. After I had mentioned it in the VS660 thread, a user replied and stated that after using the SmartassV2 governor he had experienced much better battery life and has not had any lag that...

One thing about the smartass governor is that when the screen is off it will lower the maximum CPU frequency, which on our device I believe will be either 320MHz, or if your minimum CPU frequency is above that, it will use that instead. That could explain how it is helping with battery.

I haven't had any issues with reboots, but I'll go head over to the VM670 thread and put clodfelterac's changes in my build.prop and see if any new issues come up. BTW, my CPU clocks are 729/128 on smartassV2.

I have not used CM9 extensively so I'm not sure about that, however AOKP has decent battery life for me. It's not as good as what BobZhome's CM7 ROM was, but I can make it at least a day without a charge so it suits my needs.

Going to test out the latest builds of CM9 and AOKP soon and report back with my findings. :) EDIT: CM9 seems fine and stable, no issues as far as I can tell except for all the current known issues. :P Flashing AOKP now... EDIT2: AOKP is running good. The issue with the power menu popping up...