[Kernel][ICS] Driving Always For User Quality (04/23/2012)

---

DAFUQ!!!!

This will be a sparse post for now... I'll fill in the documentation later, I'm kinda fried after fighting this stability bug.

Source: https://github.com/Entropy512/kernel...py_kernel_main
Initramfs: https://github.com/Entropy512/initramfs_galaxys2_ics/

Features:
CWM 5.5.0.4
Hopefully fixed SetCPU stability issues
fuel_alerted wakelock fix
Voltage control (use SetCPU)
Mali 3-step clock/voltage control (READ THE CHANGELOG - IT IS DIFFERENT FROM SIYAH)
Legacy Gingerbread hotplug code (including all tuning features from the final GB DD release)
Not much else for now, thank Samsung for their broken frequency control code that took a team effort of multiple kernel developers (gokhanmoral, simone201, franciscofranco, and others) to track down the problems in and fix.

Tested base: I9100 XWLP7
Should work: Any I9100 official release
Guaranteed not to work: Any I9100 leak (XXLPJ or older)

Not supported: AT&T leaks. UCLC2 won't boot for the same reason as XXLPJ and older - giving you a sign of how old the codebase is. Any leaks that do boot will have the microphones reversed in calls.

Planned features - short term:

• Overclock
• CIFS

Planned features - mid-term:

• Try to reduce power usage during suspend/resume
• Apply the "target down threshold" concept used for GPU clocks to the Conservative governor - a single down_threshold doesn't work well when 200 MHz is less than half of 500 MHz, but 1000 MHz is more than 80% of 1200 MHz.

Known issues:
"Internal" SD card in recovery is actually the external one

04/23/2012:

• Some more stability fixes (hopefully)
• Legacy Gingerbread hotplug code - More stable, and includes all of the Daily Driver tunables from Gingerbread
• Mali 3-step GPU clock/voltage control - NOTE: Down thresholds are different from Siyah. Instead of being percentage of current load, they are desired load at the next frequency step down. So "normal" thresholds will be much higher. For example, if your second frequency is 100 MHz and the third is 200 MHz, a down_threshold of 80 for 200 MHz on this kernel is the same as setting down_threshold to 40 on Siyah. (e.g. siyah_threshold=down_freq*down_threshold/cur_freq)

04/10/2012: - SUCK!!!!!!

• Revert a patch that turned out to be useless (see github)
• Swap internal/external SD cards in recovery to be consistent with CM9 - this creates a known issue (see known issues)

04/04/2012: - ZOMBIE ASS!!!!!!!

• Voltage control
• sio and v(r) ioscheds
• Hopefully last of the stability issues fixed (a glitch deep in the bowels of cpuidle)

04/02/2012:
Fixed CPU hotplugging

04/01/2012:
Initial release, pulled due to issues.

FAQ

---

FAQ will go here when I have time.

Reserved for future use.

Nice!!!!!!!!!!!!!!!!!! glad you finally released!!!

Dangerous stuff here?

Posting in a closed thread.

Ill update stuff here too.

Seems to still be issues in exynos4_enter_idle()...

Edit: If you have any issues, disable all SetCPU or similar clock control profiles and run the standard min/max of 200/1200.

hurr hurr I dun broke (and fixed in 4/2) teh hotplug

ZOMBIE ASS!!!!!

New release, last one until after the Easter holiday. Too much cleaning to do and family visiting.

I'll clean up the thread and open it up after the holiday.

Oh, and ERDs shouldn't have their thread titles auto-lowercased if too many caps!