[Galaxy Note II Original Android Development] gundal:
STWEAKS PROFILES! and proper bootloop fix.

Alright! now that Perseus Kernel .28 is out we have a new added feature that lets us implement override profiles!

What does this mean?

Well now this UNCHECK SET ON BOOT zip will actually just update your current default.profile and uncheck the set on boot options.

Which makes it the best fix for a bootloop, because you can then go back in to your old settings that failed and modify them.

I also am going to be generating 5 profiles. (will edit this post)

Each more aggressive overclocking and undervolting.

For people who are unsure of how to do do this properly with Stweaks,

You can just flash any of my profiles.

I recommend you download them all start at 5 and flash, if you bootloop or crash move up a profile until your stable!

Profile 5G is the one I run everyday (and is the lowest values for voltages)

It also is 200-1800 mhz overclocked and gpu 160-640 mhz

My custom governor tweaks (I believe the cpu is too aggressive and also the cores dont respond as much as id like to see them responding, 1 core on idle, 4 cores when needed.)

Profile 5 is the one I run everyday (and is the lowest values for voltages)

It also is 200-1800 mhz overclocked and gpu 160-640 mhz

STOCK governor settings

Profile 4 is slightly less aggressive on the voltages

200-1800 mhz 160-640

Profile 3 is slightly less aggressive on the voltage curve

200-1800mhz 160-533

Profile 2 is slightly less aggressive on the voltage curve

200-1600mhz 160-533

Profile 1 is slightly less aggressive on the voltage curve

200-1600mhz 160-533

Profile 0 is the DEFAULT profile the kernel came with. (it just deletes your profile and rebuilds it so its safe for all versions inlcuding S3-i9000)

EDIT: I have also included a zip with just the governor tweaks, these will not alter your voltages on cpu/gpu and will not change your max cpu

custom governor tweaks detailed below:

here is my logic

defaults parameter mine

30000 sampling rate 20000

82 up threshold 90

5 down diff 10

40% thres for response 81

1200 freq for fast down 1600

95 up thres fast down 98

37 up step 18

6 splice amount 4

13 down diff 8

With the default settings when the load is measured if the cpu load is over 82% off current freq step it will scale up.

New logic added in perseus .27 now gives us 3 up steps instead of just a fixed one.

so your cpu will step up more aggressively based on how much above the threshold it is, not just if its over, this is

great.

Right now, if we are coming in with a

load of 83%-88% we increase freq by 300mHz

if we are 89-94% we increase freq by 400 mHz and

if we are 94-100% then we increase freq by 700 mHz.

This is too fast for me.

For a few reasons the main one being that the amount we jump has gone up because our max cpu is 1800 instead of 1600 (at 1600 the jump ups are 200,300,600mhz)

The logic I use on my N2 is as follows:

Load of 90-94 = 100 mhz jump

load of 95-98 = 200 mhz jump

load of 99-100 = 400 mhz jump

The responsiveness of the phone is not compromised at all, the cpu just steps up less and only when it has really high loads(keep in mind the load is calculated every 20000 microseconds or 50 times in one second.)

It still gets to 1800 and does many operations there, but it comes out of 1800 fast and when it jumps down it jumps down further.

The fastdown has been upped from 1200 to 1600 , meaning it now requires 98% or higher load to jump up when above 1600 mhz not 1200 mhz, I found that the CPU was always in 1800 or like way lower,

never in the 1700 - 1200 range as it used to need 95% load to be in that range.

The cores hotplug has been slightly changed to turn off cores quicker when not in use and takes more samples to turn them on so they only turn on if load exists for longer duration of time.

PLEASE NOTE

Flashing any of these zips OTHER THEN THE UNCHECK SET ON BOOT will REMOVE your STWEAKS settings and replace them with the profile. PLEASE back up your profile if you want to save it.

Where is it?

/data/.perseus/default.profile << back this guy up. rename to default.profile2 works. or copy to sdcard.

Due to the way that these changes are applied (at initial boot) it will take longer then usual before beginning to display the boot animation for the first boot after changing profile.

This also means that you cannot flash 2 of these files in one boot, for example profile 3 and the governor tweaks.

You would need to flash the governor tweaks or the profile first and then reboot, and then flash the other.