Originally Posted by ezterry

Anyway what I might try is over-volting slightly to see if you can find a stable state
System Tuner (not SetCPU) will allow you to overvolt some; try +25 the default on all levels <=608MHZ (you can still undervolt the higher levels as they are currently if you like)

Okay - I'll try the overvoltage thing tonight after work (can't take my tab to work because our security rules don't allow it ). However, Civato says System Tuner Pro (which I own) is still buggy with Flexreaper so I've been using SetCPU. Guess I'll reload System Tuner Pro and find out if the bugs have been fixed...

Thanks again.

Originally Posted by BakaNeko59

Okay - I'll try the overvoltage thing tonight after work (can't take my tab to work because our security rules don't allow it ). However, Civato says System Tuner Pro (which I own) is still buggy with Flexreaper so I've been using SetCPU. Guess I'll reload System Tuner Pro and find out if the bugs have been fixed...

Thanks again.

They fixed the bug that caused OCTestV3 to restart .. and I fixed the bug that caused the panic to make it restart..

A few versions back they set more UV levels than our devices had levels to undervolt. This will cause none of the levels to be set as we don't know what to do with the extra data.. but isn't supposed to cause the reboot; that was bad logic in the kernel)

Originally Posted by ezterry

I see you cloned my repo on got you just need to push it there. (Preferably with the updates I've added since you made the clone)

There are shortcuts for the origin and remotes but the command looks like:

git push <URL> <local branch>:<remote branch>

Once its in your github account you can use github to send me a pull request or just message me I'll pick it up.

Another option is git format-patch (see its help) to make patch files zip them and post here.

Both the above assume you already have the changes in one or more git commits on your local PC.

If you only have a patch file not git formatted post it here and I'll look into it. But in the long term there is benefits to learning the git commands.

Sent from my Galaxy Nexus using Tapatalk 2

Here is a patch file : http://klood.me/public.php?service=f...-Support.patch

You may have a look before applying it since i'm not a kernel expert, maybe you can make things works better.

Originally Posted by ezterry

They fixed the bug that caused OCTestV3 to restart .. and I fixed the bug that caused the panic to make it restart..

A few versions back they set more UV levels than our devices had levels to undervolt. This will cause none of the levels to be set as we don't know what to do with the extra data.. but isn't supposed to cause the reboot; that was bad logic in the kernel)

I see System Tuner does not have a profiles feature. Do you think it would be OK to keep SetCPU to manage profiles and System Tuner to manage the Normal OC functions?

Sent from my A500 using XDA Premium HD app

Originally Posted by BakaNeko59

I see System Tuner does not have a profiles feature. Do you think it would be OK to keep SetCPU to manage profiles and System Tuner to manage the Normal OC functions?

Sent from my A500 using XDA Premium HD app

I think it best to pretend setcpu doesn't have profiles either..

Can't 100% say what you are using profiles for.. so can't say if there is any possible benefit.. but if its screen off profiles disable it.. that is why lulzactive as the screen_off_min_step tunable.

At 5 (the kernels default) when the screen is off the CPU will be your current min, and Max the lower of your current Max or 816mhz.

If you want a lower screen off speed you can lower the tunable.. but if you are hoping to force 0 (min and Max = 216MHz and get a sleep of death or non responsive tab, notifications fail or any other problem I don't think any dev wants to support you until you raise the value again.. I recommend raising it to 5..

If you really must use profiles just make sure the profiles and system tuner are not fighting to set the same values. But remember profiles require setcpu always running in the background and it may thus slow the tab or use more batter than it helps you save.

This is particularly true for screen off, as extra CPU is needed to trigger the event, and if the system was going into full suspend this means additional work before the CPU can enter deep sleep.

Lulzactive is c code running anyway (if its your governor) and really just notes the screen is off.. and on the subsequent adjustment ensures its in the alternative range.. thus if you are already at minfreq it literally does nothing to change that.

Sent from my Galaxy Nexus using Tapatalk 2

Amazing work man, been waiting for awhile to get an OC kernel for ICS. I'm a very happy guy now.

Sent from my A500 using XDA

Originally Posted by ezterry

I think it best to pretend setcpu doesn't have profiles either..

Can't 100% say what you are using profiles for.. so can't say if there is any possible benefit.. but if its screen off profiles disable it.. that is why lulzactive as the screen_off_min_step tunable.

At 5 (the kernels default) when the screen is off the CPU will be your current min, and Max the lower of your current Max or 816mhz.

If you want a lower screen off speed you can lower the tunable.. but if you are hoping to force 0 (min and Max = 216MHz and get a sleep of death or non responsive tab, notifications fail or any other problem I don't think any dev wants to support you until you raise the value again.. I recommend raising it to 5..

If you really must use profiles just make sure the profiles and system tuner are not fighting to set the same values. But remember profiles require setcpu always running in the background and it may thus slow the tab or use more batter than it helps you save.

This is particularly true for screen off, as extra CPU is needed to trigger the event, and if the system was going into full suspend this means additional work before the CPU can enter deep sleep.

Lulzactive is c code running anyway (if its your governor) and really just notes the screen is off.. and on the subsequent adjustment ensures its in the alternative range.. thus if you are already at minfreq it literally does nothing to change that.

Sent from my Galaxy Nexus using Tapatalk 2

I was following Civ's advice in an earlier post and using it to profile screen off/minimum CPU. Sounds like that's not really needed any more, so no more setcpu then

And by the way - I tried bumping up the voltage on the slower frequencies like you suggested, but still get SoD with any kernel other than .022. Oh well.

Sent from my A500 using Tapatalk 2

Kernel log as requested.

MD

v1.0.0

---

Version 1.0.0 is out See OP for the download and source links

This version improves stability on the A100/500 systems, plus adds experimental support for the A501 devices (3G is not yet at 100%, but other kernel functions ought to behave as expected)

Please note the additional A501 installation instructions in the OP. (Most users will simply need to flash the patchkit, then the kernel, if unsure re-flashing the patch-kit will do no harm, This is different from A500 users that just flash the kernel w/o the kit)

@ezterry : Do you have some feedbacks from A501 users ?