[Kernel] Xionia Kernel (v014 - v008, & v005) For Optimus V (4/13/2011)

[drezliok]

I just want to be sure that I know what I am getting myself into.

Side note, can I rename my backups to something like "Xionia-V005" or something so I know what it what?




EDIT
I took the plunge. I noticed the kernel wasn't as smooth but just overclocked it. Before now I left the governor at interactive but I recently read the battery optimization thread so I Min/Maxed it at 768. VERY SMOOTH. I think that it changing frequencies was the cause of the lag.

the main reason I took the plunge was the 005 charge bug got on my last nerve. My wife's stock V charges in alittle over 2 hours from drained. Mine? was 6 hours plus. 013 sped that up, I don't know how much but I will drain my phone and find out and post.

 

[obijohn]

Before now I left the governor at interactive but I recently read the battery optimization thread so I Min/Maxed it at 768. VERY SMOOTH. I think that it changing frequencies was the cause of the lag.

What you want to do is put SetCPU in "performance" mode. It may not be obvious, but what happens is that "performance" mode basically locks the CPU to the max speed. If you just set min and max to the same value and leave it on "interactive" or "ondemand", SetCPU will still be working to change frequencies. The CPU will set the new frequency to the same value, but it still registers it as a frequency change. In other words, "performance" locks the value in so that no frequency changes are attempted.

Make sense?

 

[drezliok]

What you want to do is put SetCPU in "performance" mode. It may not be obvious, but what happens is that "performance" mode basically locks the CPU to the max speed. If you just set min and max to the same value and leave it on "interactive" or "ondemand", SetCPU will still be working to change frequencies. The CPU will set the new frequency to the same value, but it still registers it as a frequency change. In other words, "performance" locks the value in so that no frequency changes are attempted.

Make sense?

I would have used performance mode but strangely it was absent from the options.

 

[obijohn]

I would have used performance mode but strangely it was absent from the options.

Strange... Which version do you have? I'm using 2.1.1a and it's there.

 

[mmarz]

Strange... Which version do you have? I'm using 2.1.1a and it's there.

It is based on your kernel. This kernel does not provide a "performance" option.

 

[denshigomi]

It is based on your kernel. This kernel does not provide a "performance" option.

Does it provide powersave? If the min and max values are the same, then powersave will accomplish the same effect as performance.

 

[mmarz]

Does it provide powersave? If the min and max values are the same, then powersave will accomplish the same effect as performance.

It doesn't have it, but I set it to "interactive". Then set the min sample rate to 500000000 us (500s). That should be good enough.

 

[mmarz]

I have added two new kernel ports and updated the original 013 kernel. All of these should keep the original LG boot logo. If you have the Sprint Logo, these will switch it back. They, of course, will also change the kernel and tweak some stuff. Make a backup if you ever want to uninstall them!

 

[overthinkingme]

Does the 008 have the same bugs as 013?
Thank you!

Sent from my VM670 using Tapatalk

 

[mmarz]

Does the 008 have the same bugs as 013?
Thank you!

Sent from my VM670 using Tapatalk

It only has the bugs that you guys report. This 013 is different from the one posted earlier, but it still has the USB bug. I haven't tested any of them thoroughly.

 

[one80oneday]

For some reason I got stuck on LG boot logo with 013 on ASOP CM7. I'll try again.

 

[mmarz]

For some reason I got stuck on LG boot logo with 013 on ASOP CM7. I'll try again.

Try reloading your CM7 nandroid backup and then using the 013 anykernel version I just posted. That might fix the issue.

 

[harukay]

Running rodimusrom. Flashed 013 and rebooted to system but it didnt boot got stuck at the green android. Took off the battery and tried it again and this time it booted but i got a bunch of fc. Fixed it by wiping dalvik cache and flashing the kernel again. Everything works fine now

 

[one80oneday]

Try reloading your CM7 nandroid backup and then using the 013 anykernel version I just posted. That might fix the issue.

New 013 booted but now the home & menu keys are switched, not a big deal

 

[harukay]

013 with bootimg broke my wifi. Gives me an error every time I try to turn it on. Flashed 013 without bootimg and wifi works now.

 

[antipasta]

It only has the bugs that you guys report. This 013 is different from the one posted earlier, but it still has the USB bug. I haven't tested any of them thoroughly.

What exactly has changed in this version of 013 versus the previously posted one?

 

[mmarz]

What exactly has changed in this version of 013 versus the previously posted one?

The previous version would create a boot.img while installing by using the ramdisk that your phone currently used. This could lead to problems if you started with an awkward rom. The new version uses a complete boot.img that works with our phone.

 

[thexxoffspring]

from my experience 008 is way faster and smoother than 013. 013 i had to battery pull twice will booting and then it would work.

 

[mmarz]

from my experience 008 is way faster and smoother than 013. 013 i had to battery pull twice will booting and then it would work.

Have you tried the new one I posted today? It should be different. I haven't had those issues with it so far.

 

[drezliok]

REMOVED