[KERNEL][14APR-K13E]Insane OC/UV kernel

Search This thread

xan

Retired Recognized Developer
May 21, 2006
1,407
455
Crack-ow
Advice: 1) don't try to fix something that isn't broken. Don't change speedmode settings (saving size, preemt config, noop).
Thanks for valuable feedback.
Its always good to look behind and reevaluate some statements.
I wont be doing this much, I dont want to break it.
The smoothness can be related to so many things... like kernel tick hz, preempt, scheduler, clock changes, maybe even compiler used.

My main aim will be to leave the hard work to hardcore and focus on oc changes, however there will be no new features to oc code. It just needs to be stable, change states accordingly.
 

sakuhei

Senior Member
Jun 19, 2010
113
9
OnePlus 7
Samsung Galaxy S21 Ultra
Hi Xan
I am new to OC and I am messed up with those setting in Voltage Control.
Would you mind telling how to set up those figures in the app?
It will be great if this can save more battery while increasing the performance than speedmod :p
 

MarlowXim

Senior Member
Oct 29, 2010
163
9
@xan how did you get preempt to work?

I've always had the samsung drivers bork it up, I believe it's the fsr modules. Or is it preempt desktop which essentially does not interrupt anything anyway.
 

xan

Retired Recognized Developer
May 21, 2006
1,407
455
Crack-ow
@xan how did you get preempt to work?

I've always had the samsung drivers bork it up, I believe it's the fsr modules. Or is it preempt desktop which essentially does not interrupt anything anyway.
Yes, drivers dont load with preemptible kernel
Its volountary preemptive desktop.
It does nothing? I had no idea, you got me here.
 

sheevy

Member
Oct 21, 2010
9
1
Would it be problem for you to release 355 MB free RAM version of your kernel? I'd love to see it.
 

dupel

Senior Member
Jun 2, 2010
1,394
23
London
Hi Xan,

I'm a noob in oc. So can you specify on wich mhz i have to set the uv? e.g. 1200-75?

Thanks

Sent from my GT-I9000 using XDA App

Thats very individual. Most cpu's (80%) should be able to handle 1120 mhz and 99% should handle -25 on lower (100-800).

Mine isnt best but can handle 1200 and -50 on 100-400 and -25 on 800. Thats very stable and safe for me, probably if I spend enough time I can find a bit higher values.
 

uberberben

Senior Member
Jul 25, 2010
223
22
Mine is stable too with some UV on lower fq, -75 on 100MHz, -50 on 200-800 and -25 on 1GHz . However i can't OC to 1280MHz, it's unstable on all OC kernels i've used so far. 1.2GHz works fine.
 

gon9999

Senior Member
Jan 20, 2010
152
18
Berlin
Mine is stable too with some UV on lower fq, -75 on 100MHz, -50 on 200-800 and -25 on 1GHz . However i can't OC to 1280MHz, it's unstable on all OC kernels i've used so far. 1.2GHz works fine.

With setcpu mine is stable at 1280, but i will try to use uv to vet more battery life....

Sent from my GT-I9000 using XDA App
 

freakonaleash

Senior Member
Sep 28, 2010
265
70
Siracusa
I just did a few tests with an OC at 1.2 Ghz, and for me it seems to be pretty stable atm, I have no freeze etc, and the phone seems to be smoother. But I've tested for 10 minutes so, I'll give you a more consistant feedback tomorrow.

For information, I ran a Quadrant test (I know it means nothing, but just for numbers), and without lagfix it gives :
- 1180 with no OC/UV
- 1270 @1.12Ghz
- 1390 @1.20Ghz

Thank you a lot for your work xan !

Quadrant is a bad benchmark software for sgs,try smartbench instead



Sent from my GT-I9000 using XDA App
 

Ibanez33

Senior Member
Mar 29, 2010
430
55
Is anyone else getting a signature error when trying to install the voltage control app?
 

Ibanez33

Senior Member
Mar 29, 2010
430
55
Voltage control 3.0.3 installed successful...

Sent from my GT-I9000 using XDA App

Cheers worked it out in the end, still had v3 alpha installed as a system app... (ticked in rom kitchen)

For anyone else with the same problem just use titanium backup to uninstall the old version and install the new one again..
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    This is an alpha release!
    It is nowhere as stable and tested as Speedmod itself!


    What it is?
    All I did was to compile Speedmod (To be honest, I'm clueless what gizmos are sitting there, but its great)
    Credit should go to hardcore. He is author of this kernel, I'm responsible for breaking it and making bugs.

    What did you break?
    + OC/UV features (this might fry your device)
    + some clock changes to keep it stick more to 100mhz (should be at least)
    + preemptive config (needs testing)
    * optimised for size (not sure if this is good)
    * noop is being the default scheduler (i just like it)
    * 341MB ram (if someone is curious about this)
    - everything I have broken along the way (maybe nothing)

    So (as you can see) its pretty alpha

    How do I?
    Just flash the CWM package.
    This kernel is being tested on Insanity ROM
    32luwng
    , which I personally use.
    If you want some more power, extras like nitrality (Ha I bet you dont know what it is!) I recommend you flashing this one.
    By default no OC is applied. You need to download and use Voltage Control.
    BE SURE TO USE LATEST (3.0.1)
    32luwng
    Voltage Control app!
    32luwng


    Voltage Control in Adroid Market:

    img.php


    Wooah, I think its stable...
    You can never be sure.
    My device freezes just after going into menu in Asphalt 5 (Samsung apps), so thats the test I can recommend.
    I suggest you do the following:
    OC 1120Mhz -> 1x Asphalt race,
    OC 1200Mhz -> 1x Asphalt race,
    OC 1280Mhz -> 1x Asphalt race.

    If that is stable.. Well you can be 99% sure, but you know, 1% off one week is ****loads of time ;p



    Why?
    Because I can :)
    Consider this a tribute to all developers who constantly work on improving Galaxy S kernels!


    Then tell me who was that?
    - hardcore - its his source
    - sztupy - excellent recovery
    - supercurio - sound fixes, lagfix ideas
    - raspdeep, unhelpful, laststufo, trasig -> oc code
    - all others involved, sorry if I missed anyone! (its late)
    - personal thanks to nitr8 - support and testing, some recovery tweaks (more coming, if hardcore releases sources for recovery)

    So what you gonna do?
    Basically wait for feedback. As always it will be mixed.
    I dont have many plans for this kernel, I will just upgrade with every new Speedmod (well, if time will allow).
    However, I dont want to release kernel more than once a week.

    Erm, sources, bit#^?
    See: insane.7z (fixed)

    Its code prior cleaning, some leftovers are there.
    Lots of debug info, to track whats going on (kmsg is disabled in release, so they dont work anyway)

    F...udge! I'm stuck at bootlogo!
    Flash back your previous kernel and disable lagfix from recovery!

    F...udge! My device is totally unstable
    Code:
    cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
    Check it after few mins of runnning. If it goes over desired frequency -> report here with output
    2
    I think I just had an orgasm jsut reading it. My dream come true =)

    Do we continue to use your app for this kernel?

    I think :)
    Be careful, use 3.0.1 version.
    2
    Ok 13E for testing... I think it definitely works maybe.
    1
    Flashed the alpha release over Laststufos SOK 4.7.8 and Darky's ROM 9.3 Beta 3 (pele78 black theme, your voltage control app for uv). Flashing works fine, but does not boot further than the first screen (Samsung i9000 whatsoever).

    Reverted to SOK 4.7.8 - fine again.

    Waiting for your next releases to test.

    Did you have a lagfix on as K13c only reads rfs and EXT4 ?? I flashed over DamianGTO and it was fine, but I disabled lagfix first
    1
    Well if you choose max freq 1120 then have 1120 frequency enabled in advanced screen (assuming you use Voltage Control 4) then something is wrong with kernel.
    At this moment kernel its provided 'as is', without any support, its simply outdated.

    I made some tests with Insane GB kernel, however ATM I'm running CM7 and awesome TK-Glitch, so I'm in no need of working on kernel for stock-based ROMs.