Originally Posted by distINCtINC

Sure. I'll post the one I'm using now, but if Franco has any problem with me posting this I'll take it down ASAP.

It's Franco's 140 and has the modified lazy governor I mentioned before, but it also has Ezekeel's Vibrator control, FSync control, SIO scheduler, and a bunch of other governors I was testing before settling on Lazy.

FYI it has low regulator voltages that work fine on my device, but may cause display issues for you.

I don't support any troubleshooting from this compile, if users want to use that then they are on their own. But some clarification is needed:

- My kernel has fsync off since day 1
- SIO is added and enabled since a few releases already

Originally Posted by Serious_Beans

Do you plan on adding voltage control for the screen like Ezekeel has on his app? If not do you plan on adding experimental kernels with lower screen voltages? What are they now? O_o THanks!

Dunno. My kernel already has VAUX and VUSIM voltages reduced.

with lazy governor is it best to use 300mhz or 700mhz for your minimum cpu?

Originally Posted by macellaio

Francisco, a couple questions:

1. Have you been following the FIOPS scheduler development? If so, do you think you'll be looking at it's performance for inclusion in your kernel?

2. Have you explored the use of the C4 state in your governor tweaks? Ezekeel makes use of it in his Wheatley governor and I think it's an interesting concept.

1 - FIOPS is still too experimental.
2 - It's interesting but I don't like the concept but I respect Ezekeel's idea and thrill for inovation.

Originally Posted by franciscofranco

Dunno. My kernel already has VAUX and VUSIM voltages reduced.

What are the voltages at? Anyway to change them with terminal?

Sent from my Galaxy Nexus using xda premium

Originally Posted by Serious_Beans

What are the voltages at? Anyway to change them with terminal?

Sent from my Galaxy Nexus using xda premium

Nop.

Its 2750 for VAUX3 and 1800 for VUSIM if I'm not mistaken.

r141
* Disable Sync framework for now - it seems too experimental and it was slowing the kernel down. I also think it was causing few random reboots to some users which makes sense since in the patch description it says it can give a few kernel deadlocks. Everything should be ok now
* Merged another Interactive patch
* Merged a patch from TI that adds 3 local caches for DSSCOMP that improves reliability, autonomy and efficiency of the module

Been really busy - don't have time to sift through the dozen or so pages I've missed so excuse me if this is repetitive.

Went from 135 -> 140 tonight. Noticing constant dropped signals associated with screen_off.

1228
729
Lazy
No UV
Gen Hotplug ON
SR ON

EDIT: Should I try 141, was there any patching for this implemented Franco?

flashing r141 now

holy smokes. Im on like the third kernel in as many days! I can hardly keep up! let alone test each one!

keep up the good work my phones flying

flashing 141