• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [WIP][Kernel]Un-named Kernel[1.4Ghz]

rbheromax

Android Expert
I figured out how to set more than 5 freq. :D

Basically to up the freq on the board, you would edit cpu-freq.c but one of its dependents (cpu-freq-v210.h which is in another folder) has a line which goes:
MAX_PERF_LEVEL = Lx,
Originally its set to 4 (so L0-L4 which is 5 freq.) but you can add the # of freq you will scale to and from here.

So now it scales as follows:
1.4Ghz
1.3Ghz
1.2Ghz
1.1Ghz
1 Ghz
800 Mhz
400 Mhz
200 Mhz
100 Mhz

Init.d
Custom Gov'n


Src released under GPL (zip): https://github.com/newkid313/android_kernel_samsung_s5pv210/tree/2.6.35
 
WORK IN PROGRESS
Needs to be extensively tested before release :p

Frequencies set are:
1.2 Ghz
1 Ghz
800 Mhz
200 Mhz
100 Mhz

I had to get rid of 400 Mhz because it would refuse to build with more than 5 freq. set. I will look in to this. Since I dont have a confirmed "boot.img" I am releasing the zImage for people to pair with their own ramdisk.

https://www.dropbox.com/s/02ifojyeqhhm7gm/1dot2ghz.zImage

Ok only one issue i see with pairing the zImage to a ramdisk on the Illusion is it runs on a zImage.md5 the ramdisk is compiled into the zImage at compile time, it doesn't use boot.img/recovery.img
 
I will push the src to github in a bit, my username on github is "newkid313". Expect it up within the next few days :D
 
No wonder my first attempt at OC failed in a dead kernel. Now I just have to figure out WTH is causing my recent builds to loop.

Also, be warned: You need to "make modules" and copy them to the ramdisk before doing "make". Otherwise you run into vermagic problems and a dead kernel.

The boot kernel is mmcblk0p6 by the way :).
 
Re-downloaded from your site, but still the same issue.

<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage.md5

Odin flash gets stuck on that last step and just sits.

Here's the log when re-flashing stock:

<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage.md5
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
 
Back
Top Bottom