Develop Bugs

[Kernel][2.6.32][OC/UV][Up to 1.4ghz configurable][2nd Dec][Froyo][Fast Scaling]

New Directions:
As there will be more tweaks and findings out by xda members, i will not include much tweaks (unless those i run) into my kernel but to release source so others can incorporate my oc/uv into their "all-in-one" kernel threads.
im glad someone took the liberty to add voodoo kernel and hope he eventually get voodoo to merge nicely with modded cwm.
UV control version 2.1 and above
- voltage scaling
- full UV user control via sysfs
- works on all governor
- echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
- column 1 for 1.2ghz, 2 for 1ghz, 3 for 800mhz, 4 for 400mhz, 5 for 200mhz, lastly 100mhz
- values are mV
- Use latest xan's app if you dont want to mess with commands - here
Info:
- based from the jpm froyo 2.6.32.9 kernel drop
- using sztupy ramfs (it has sztupy modded cwm but i did not test all options esp lag fix)
- Mem config based from here - free 341mb
- BLN by Neldar
- sysfs user configurable Undervolt
- FS supports - ext2 / ext4 / JFS
- sourcery 4.4.1 g++ 2009q3
- linpack 16 MFLOPish
- supported frequencies 100/200/400/800/1000/1200
- rooted adb shell
Stock voltage info
1200000 - 1300 (<-added)
1000000 - 1275
800000 - 1200
400000 - 1050
200000 - 950
100000 - 950
Max vdd_arm is 1.31v according to datasheet so dont go crazy OV'ing
To-do
- a lot
How to install:
- download any latest .7z file
- extract .tar from the .7z file
- use odin, load tar file under pda and flash
Credits
- sztupy
- supercurio
- unhelpful
- hardcore
- xan
- neldar
enjoy!
OC / UV 101
This question has been asked a lot so I will try my best to answer this question to my knowledge. Our phone although uses the same hardware, they can vary in terms of stability and performance. I believed even same hardware varies because of production tolerances & variations. Our stock 1ghz system per datasheet should run at 1.2v, however, in the source code, samsung set it at 1.275v. There are a lot of speculation why this happens but my personal believe is due to production fallouts. In production environment, to increase the yield, they increased the voltage to make them more stable. This is the easiest way to increase yield and sound most logical in business standpoint.
Our phones do frequency scaling. Meaning it doesnt stay at a particular frequency all the time, the frequencies fluctuate depending on load and thresholds. At high load, it will go to high frequencies and when low load or idle mode, it will stay around 100-400 range. In this way, you get load balance and uses lesser power.
Back to how adjusting UV to suit your phone. I've enabled via sysfs (/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table) the ability for user configurable UV, unlocking this allows for UV'ing at all supported frequencies 100/200/400/800/1000/1200mhz. In this table is an array of values in mV, column 1 for 1.2ghz, 2 for 1ghz, 3 for 800mhz, 4 for 400mhz, 5 for 200mhz, lastly 100mhz. What this means is each column allows an UV setting at you can change to suit your phone. In boot up stage, all the values in the array is zero hence no UV'ing. You can set it and here is how it works:
Taking for example, you echo "0 50 50 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table, looking at the stock voltage info I've described above, you will get:
1200000 -> 1300-0 = 1300mV
1000000 -> 1275-50 = 1225mV
800000 -> 1200-50 = 1150mV
400000 -> 1050-75 = 975mV
200000 -> 950-75 = 875mV
100000 -> 950-100 = 850mV
At 1.2ghz, i disabled UV by setting the value to 0. This is because 1.2ghz is already OC'ed so some phones may not be able to run stable so UV'ing makes the situation worst. At 1ghz, i reduced by 50mV, this is trial and error, i wouldnt know if this is stable unless i do some benchmark, run some programs, etc. So the question is "how do i know the UV i set is stable?" You can do this by a few ways. For my case, this is how I do it:
1) Set the voltage for 1ghz at 25mV
2) Use SetCPU to limit max and min scaling frequency to 1ghz
3) Run test, play some media, surf the web, open market place, etc.
4) Run it for 30-45 mins and if it doesnt crash, its good.
5) Increase the mV to 50mV and repeat 2-4 until it hang or crash
6) Find the mV that you phone likes without hanging or crashing then move to 800mhz
For lower frequencies, you can "usually" have higher UV but you cannot use setcpu to test the lower frequencies as the system will run above the max scaling frequencies even if you try to limit it lower (edit: this happens only if min and max frequency is not equal). For example, you limit the max scaling frequencies to 200mhz, it wont stay max at 200mhz but jump higher. The easiest way to test the lower frequencies UV is by letting your phone standby, sleep or do less intensive stuff and see if it runs stable, I believed most phones can do 75mV at 100-200mhz range but you can try more and see how it works out for you.
You can also test the lower frequencies by setting both min and max scaling to the same frequency. However, do note that setting low frequency will be very slow especially if you try it at 100mhz. It may take several seconds just to change apps.
FAQs
Q - What is UV? Why UV?
A - UV stands for Undervolt. The idea is to run at lower than stock voltage at any frequencies hence saving battery and longer battery performance
Q - Does UV also slow down the performance?
A - Theoretically it doesnt but under certain circumstances when the voltage gets too low for the cpu to operate properly, you may encounter some glitches so the idea is not to run it at the all the way down but find a suitable voltage that it doesnt happen. For example, running 75mV is stable but sometimes see some slow down so up it to 50mV and it should run fine.
Q - I am not convinced, I do not want to OC, how can I stop that?
A - Simple, using xan's app, check the box "limit max clock to 1ghz (no overclocking)" or using adb shell echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Changelog
v300
- ULF v0.4pre
-frequencies supported are 1400/1360/1280/1200/1120/1000/800/400/200/100 (in this order)
- echo 0 0 0 1 0 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
- Frequencies state can be enabled by echoing a "1" into the column position (1.4ghz - 1st column, 1.36ghz - 2nd column, 1.28ghz - 3rd column,... etc)
- examples above will enable 1200/1000/800/400/200/100
- At default stage, all the OC frequencies will be disabled so user will have to enable if they want to OC.. it will only run ONCE when scaling start (so using init.d to set the states) but i've added a trigger called /sys/devices/system/cpu/cpu0/cpufreq/update_states which by default will be 0. echoing a 1 will force an update if you want to change the state.
- There will also be UV for each frequencies same as previous version
- Stock voltage
1400000 - 1300 (<- added)
1360000 - 1300 (<- added)
1280000 - 1300 (<- added)
1120000 - 1300 (<- added)
1200000 - 1300 (<-added)
1000000 - 1275
800000 - 1200
400000 - 1050
200000 - 950
100000 - 950
Max vdd_arm is 1.31v according to datasheet so dont go crazy OV'ing
v217 UV alpha
- quick fix on corrupted /system
- /sbin/busybox mount -t rfs -o check=no /dev/block/stl9 /system
Highly Experimental 1.28Ghz / 1.4Ghz kernels v216
- Only for those that know what they are doing - no support
- BACKUP YOUR STUFF
- Disable UV and UV startup script
- Post your benchmark for bragging rights
- Linpack 17.9 (1.28Ghz) / 19.8 (1.4Ghz)
v216 UV alpha
- added BLN
- release source for 1.12ghz
v215 UV alpha (1.2ghz and 1.12ghz OC support)
- 100->400mhz fast scaling (less aggressive than v212 for better battery life)
- tweak for faster response
- bootanimation support
- do Linpack benchmark of your current kernel vs my kernel for comparison. Only benchmark 5 mins after system bootup (without USB cable attached)
- Linpack: [email protected], [email protected],[email protected]
v212 UV alpha
- hz = 300
- fast scaling speed jump
- tweak for faster response
- fix sztupy's startup script so it will run any files in /etc/init.d at startup
- may use more battery so keep track and let me know
v2.1 UV alpha debug
- full UV user control via sysfs
- works on all governor
- echo "50 50 150 75 75 100" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
- column 1 for 1.2ghz, 2 for 1ghz, 3 for 800mhz, 4 for 400mhz, 5 for 200mhz, lastly 100mhz
- values are mV
- Use latest xan's app if you dont want to mess with commands - here
v2.0 UV alpha
- PMIC VS UV
- user configurable UV settings (default value = 0 for UVLF and UVHF) for conservative governor only
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (for 100-800mhz)
- /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (above 800mhz)
- for example # echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV (will UV by 50mV for 100-800mhz)
- for example # echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV (will UV by 25mV for 1-1.2ghz)
- If you do not want to mess with commands, use Xan's app for easy GUI control - here
- if you tried 100mV and still doesnt crash, use command method to set higher. my phone crashed when i set 125mV @ UVLF and 75mV @ UVHF
- Hz @ 500
- source patch attached
v1.0 UV alpha
- bug fixes
- optimization flag back to O3
v1.1 alpha
- added JFS
- compile optimization level to O2 from O3
- Mem config based from here - free 341mb
- release alpha patch source code
v1 alpha
- initial release

Oc to what? xD
Sent from my GT-I9000 using XDA App

thx will give it a try!

jaju123 said:
Oc to what? xD
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
- supported frequencies 100/200/400/800/1000/1200

look forward to hardcore incorporating this into his kernals.

REALLY interested in this.
I'll install this when it's further in the development stage.
Will you be adding features/themes to this rom or will it be OCing only?

INeedYourHelp said:
look forward to hardcore incorporating this into his kernals.
Click to expand...
Click to collapse
Me too..! (I have 14MFLOPS with the latest hardcore´s kernel.. and with OC it can be really interesting)

Aery said:
- supported frequencies 100/200/400/800/1000/1200
Click to expand...
Click to collapse
he was right, i forgot about frequencies until he asked

Thanks, tha OC King is back
Update: functional on Doc_Kalpik 5/6 roms

http://forum.xda-developers.com/showthread.php?t=821514
maybe you can share your knowledge with those guys, they said they want to port that that kernel to every modell
But good work =)

Impressive: Linpack 17.4 ,
Quardrant, no lagfix, 1150+

ups wrong link, i meant this one:
http://forum.xda-developers.com/showthread.php?t=821514
like i said, maybe you can share knowlegde about OC

now we need the memory hack (to get back 40MB of ram)
run quadrant with ext4 on all 3 partitions, score is 1774 (previously it ranges for 1400-1500 for lagfix kernel with memory hack)

DocRambone said:
Impressive: Linpack 17.4 ,
Quardrant, no lagfix, 1150+
Click to expand...
Click to collapse
nice numbers.. i hope more can test on the cwm as i dont have time to test all options.

Kryston said:
ups wrong link, i meant this one:
http://forum.xda-developers.com/showthread.php?t=821514
like i said, maybe you can share knowlegde about OC
Click to expand...
Click to collapse
i will share the source in a bit once i know its stable enough

zenkinz said:
now we need the memory hack (to get back 40MB of ram)
run quadrant with ext4 on all 3 partitions, score is 1774 (previously it ranges for 1400-1500 for lagfix kernel with memory hack)
Click to expand...
Click to collapse
some link will be nice as i just got back into the scene and didnt get much time to read all the posts

raspdeep said:
nice numbers.. i hope more can test on the cwm as i dont have time to test all options.
Click to expand...
Click to collapse
Yes, this makes V6 rom to kick a$$

YES YES hes back!
May I make a first request:
Consider basing this kernel on sztupy's work, making it fully compatible with ext4, jfs and his CWM.
AFAIU(as far as I understand? lol) JFS is not supported in this release?

raspdeep said:
some link will be nice as i just got back into the scene and didnt get much time to read all the posts
Click to expand...
Click to collapse
no prob.
here's the config of the memory and compilation option you can take reference to
http://forum.xda-developers.com/showthread.php?p=8850760#post8850760
credits to ykk_five and hardcore for their research in the memory tweak.

xan said:
YES YES hes back!
May I make a first request:
Consider basing this kernel on sztupy's work, making it fully compatible with ext4, jfs and his CWM.
AFAIU(as far as I understand? lol) JFS is not supported in this release?
Click to expand...
Click to collapse
not sure about jfs, but this works well on my set which was previously on sztupy's kernel (and the memory-tweaked kernel that's based on sztupy)

[Kernel][Sense]2.6.35.14/OC/UV/CFS/Vdd_sysfs

Freq & Voltages:
245760: 900
368640: 925
768000: 1000
1024000: 1050
1113600: 1075
1209600: 1125
1305600: 1175
1401600: 1225
1497600: 1250
1516800: 1250
1612800: 1350
1708800: 1400
1804800: 1425
Kernel Features:
LZMA
Ext4
TUN
CIFS
SLBQ
Tiny_RCU_Preempt
SCHED_AUTOGROUP backport to 2.6.35
VDD & Smartass Sysfs see here for use
Audio Moderately Increased
Readahead to 4096
Numerous compiler optimizations
Kernel max boot freq set @ 1024mhz
Kineto_gan incase we have some sim-unlocked on t-mobile(still will need userspace stuff)
Some Code Aurora Foundation FS & QSD optimizations
Almost all debugging turned off
Governors:
greaselightning
superbad
scary
smartass
minmax
conservative
ondemandX
powersave
ondemand - default
performance
Thanks & Credits in no particular order:
Umaro
Thederekjay
Ziggy471
Imoseyon
Erasmux
Cyanogenmod Team
Tiamat
changelog:
#17 Had included mismatched wifi module in #16 and fixed install zip to handle ext4 /system partitions also.
#18
Removed sysfs tuneables for smartass
Fixed smartass gov that didn't scale properly. Just like interactive gov that I didn't include smartass has random lockups at freqs above 1612mhz especially @ 1804mhz.
Added smartassV2 this newer revision of smartass does not have the lockups at highest freq like original smartass does.
#21 This one is for sense 2.3.4+ only usb mounting is fixed for 2.3.4+
GPL Source

Download section:
Beta Unsigned:
inc2_2.6.35.14#16-gnm.zip
inc2_2.6.35.14#17-gnm.zip
inc2_2.6.35.14#18-gnm.zip
inc2_2.6.35.14#21-2.3.4.zip

Nicely done. Sense needs kernel like tiamat.

have to try it!
Sent from my HTC Incredible 2 using XDA Premium App

<---- totally ignorant here. Is this for sense 2.1 or 3.0?
Sent from my cyanogen(mod) turbocharged Incredible 2

Clutch McWinner said:
<---- totally ignorant here. Is this for sense 2.1 or 3.0?
Sent from my cyanogen(mod) turbocharged Incredible 2
Click to expand...
Click to collapse
Both. Can be used on either

Clutch McWinner said:
<---- totally ignorant here. Is this for sense 2.1 or 3.0?
Sent from my cyanogen(mod) turbocharged Incredible 2
Click to expand...
Click to collapse
doesnt matter, as long as its 2.3.3 sense based rom

nitsuj17 said:
doesnt matter, as long as its 2.3.3 sense based rom
Click to expand...
Click to collapse
Only matters that its a gingerbread sense rom. 2.3.x sublevel doesnt matter.

Thanks , can you advise me the right voltage to increase my battery life with it ?
I will give it a try
EDIT : i got connection closed but the server , can you please upload it in megaupload ?

zozor said:
Thanks , can you advise me the right voltage to increase my battery life with it ?
I will give it a try
EDIT : i got connection closed but the server , can you please upload it in megaupload ?
Click to expand...
Click to collapse
Its already undervolted. Power users can adjust it even more via sysfs.
Stock voltages were:
245760 1000 100mv undervolt on mine
368640 1050 125mv undervolt on mine
768000 1100 100mv undervolt on mine
1024000 1200 150mv undervolt on mine
1305mhz is running at 1175mv which a 25mv undervolt from the stock voltage at 1024mhz.

Can you make a megaupload link , i cant download .

How does greased lightning governor work? And ondemandx. I've heard of the others
Sent from my ADR6350 using XDA App

Anyone can make a megaupload link for me please ?

So far so good. Initially had a lockup in SetCPU but after battery pull all is good. Hope the undervolting adds a little to my already awesome battery life.

Anyone can make a megaupload link for me please ?
I cant download the link in my way

zozor said:
Anyone can make a megaupload link for me please ?
I cant download the link in my way
Click to expand...
Click to collapse
Yes.
http://www.multiupload.com/MVY42UF32I
megaupload- http://www.multiupload.com/MU_MVY42UF32I

Thanks Andy

zozor said:
Thanks Andy
Click to expand...
Click to collapse
anytime man.

droidxplorer said:
So far so good. Initially had a lockup in SetCPU but after battery pull all is good. Hope the undervolting adds a little to my already awesome battery life.
Click to expand...
Click to collapse
+1
Sent from my ADR6350 using xda premium

anyone else achieving a surreal performance with this? it's INSANE....... wow.

Good rom / kernel combo for performance and batterylife

Hi,
After reading many posts about battery draining issues and trying different rom / kernel combo's i would like to share my current settings as they give me great batterylife and really good performance; the UI is still very responsive and smooth.
Also my phone doesn't get as hot at the rear near the camera as it did before...
rom: Modaco http://forum.xda-developers.com/showthread.php?t=1361108
[ i really like the brightness settings on this rom + the faster screen rotation and the 'search button' mod ]
kernel: Stock kernel for Android Revolution HD 1.3.x (ITL41F) http://forum.xda-developers.com/showthread.php?p=16419842#post16419842
[ great stock kernel for batterylife and performance ]
SetCPU settings:
max 920; min 350; interactive gov.; screen off max/min 350
uv patch: uv control only http://forum.xda-developers.com/showthread.php?t=1380064
[ gives the ability to undervolt the stock kernel ]
UV settings:
1200mhz --> 1125 mV
920mhz --> 975 mV
700mhz --> 900 mV
350mhz --> 800 mV
*please play around yourself with these settings as each phone can handle different values
launcher: Stock Launcher | No Search Bar | 4x5 Portrait Grid | More Bacon Added! http://forum.xda-developers.com/showthread.php?t=1385425
[ i use the no landscape version; i like it without the searchbar at the top and the 'search button' mod from modaco is really nice with it ]
I hope to hear some of your experiences and ideas about even better combinations in the rom / kernel department...

You forgot to mention that gpu is bumped up to 384 mhz with the uv patch. I also suggest bumping your sleep profile with max freq. to 700mhz. If you look at your for an extra ~100mv you get twice the speed. And this should be set as a higher priority than other profiles.
But here are my undervolts.
1200 mhz = 1128 mv
920 mhz = 952 mv
700 mhz = 867 mv
350 mhz = 757 mv.
My low frequencies are probably lowest theyre going to get. ~36 hours stable on those. I am still bumping my top 2 freq. down but will probably give it more time this weekend because i need the stability at work.
Sent from my Galaxy Nexus using xda premium

You guys may already be doing this but I'd check each frequency with benchmarks at stock voltage and record values (set min and max to each freq. to lock it to one) and then re-check at the undervolt.
I discovered that even though the phone was stable at some voltages the performance actually started dropping off in tests enough where you could rule out run-run variation. (indicating that although there were no FC/crash/reboot the hardware was not happy)

What are stock voltages? How to see my CPU voltage levels?

Does anyone know what the stock voltages are?
Also, how can I find out what the voltage levels are that are currently set on my phone for each frequency?
It seems like every custom kernel out for our T989's is undervolted by default. I've been seeing some random reboots, and wanted to return to stock voltages, but am having trouble figuring out how to do that on a custom kernel.

I'd like to know this as well.

manekineko said:
Does anyone know what the stock voltages are?
Also, how can I find out what the voltage levels are that are currently set on my phone for each frequency?
It seems like every custom kernel out for our T989's is undervolted by default. I've been seeing some random reboots, and wanted to return to stock voltages, but am having trouble figuring out how to do that on a custom kernel.
Click to expand...
Click to collapse
System Tuner from the market will give you the option to overvolt and tell you the current voltages at all the frequencies. Stock voltages (I believe) are the following:
384Mhz - 800mV
1.02Ghz - 1000mV
1.13Ghz - 1050mV
1.29Ghz - 1125mV
1.51Ghz - 1200mV
1.72Ghz - 1287.5mV
1.83Ghz - 1300mV
I'm interpolating from the voltages I'm currently running, which I believe is 75mV undervolted, so I just added 75mV to the numbers I have and posted the sum. I'll double check later tonight by flashing back to stock and checking my voltages. There are frequencies in between, but those should be good enough for you to determine what the global undervolt on your kernel is.

Okay here's the full list of default voltages. Ignore my previous post.
(Mhz/Ghz) - (mV)
192 - 800
310 - 825
384 - 825
432 - 850
486 - 850
540 - 875
594 - 875
648 - 900
702 - 900
756 - 925
810 - 975
864 - 975
918 - 1000
972 - 1025
1.02 - 1025
1.08 - 1050
1.13 - 1075
1.18 - 1100
1.24 - 1125
1.29 - 1150
1.35 - 1150
1.4 - 1175
1.45 - 1200
1.51 - 1225
1.62 - 1250
1.67 - 1275
1.72 - 1300
1.78 - 1312.5
System tuner will allow you to change the voltages at each frequency or do a global under/overvolt. But make sure your kernel supports UV/OV in the first place, otherwise system tuner won't do diddly squat.

yoft1 said:
Okay here's the full list of default voltages. Ignore my previous post.
(Mhz/Ghz) - (mV)
192 - 800
310 - 825
384 - 825
432 - 850
486 - 850
540 - 875
594 - 875
648 - 900
702 - 900
756 - 925
810 - 975
864 - 975
918 - 1000
972 - 1025
1.02 - 1025
1.08 - 1050
1.13 - 1075
1.18 - 1100
1.24 - 1125
1.29 - 1150
1.35 - 1150
1.4 - 1175
1.45 - 1200
1.51 - 1225
1.62 - 1250
1.67 - 1275
1.72 - 1300
1.78 - 1312.5
System tuner will allow you to change the voltages at each frequency or do a global under/overvolt. But make sure your kernel supports UV/OV in the first place, otherwise system tuner won't do diddly squat.
Click to expand...
Click to collapse
I was wondering what stock voltages are as well just to see how much I have undervolted compared to stock for informational and learning purposes.
I have flashed as many kernel’s as I could try so far that’s compatible with my rom. Those voltages look like Darkside’s Kernel to me. I am not saying those aren’t stock voltages, but I do know that it is possible those are not stock voltages because the stock Kernel would only go to 1.5GHz, anything beyond is an overclock.
Your 75mv underclock could refer to the standard kernel version that is released; however, it could refer to stock but I will flash back to stock to verify this.
If you could post or PM me your currently used undervolted settings I would appreciate it. I would like to collect info and eventually make a graph with what works, what doesn’t and what kernels come with what standard.
I use System Tuner as well, it was well worth my money.

goldfingerfif said:
I was wondering what stock voltages are as well just to see how much I have undervolted compared to stock for informational and learning purposes.
I have flashed as many kernel’s as I could try so far that’s compatible with my rom. Those voltages look like Darkside’s Kernel to me. I am not saying those aren’t stock voltages, but I do know that it is possible those are not stock voltages because the stock Kernel would only go to 1.5GHz, anything beyond is an overclock.
Your 75mv underclock could refer to the standard kernel version that is released; however, it could refer to stock but I will flash back to stock to verify this.
If you could post or PM me your currently used undervolted settings I would appreciate it. I would like to collect info and eventually make a graph with what works, what doesn’t and what kernels come with what standard.
I use System Tuner as well, it was well worth my money.
Click to expand...
Click to collapse
Depending on what version of darkside you're using, you could very well be running stock voltages. Tdj has gone back and forth in using and not using undervolt in his kernels. You are correct in saying that when I recorded these I was in the darkside kernel (hence the voltages listed for overclocked speeds) but I made sure that it was a version running stock voltages and I crossed checked the standard clock speeds with a stock kernel.
Disregard my post where I talked about a 75mV undervolt, those numbers are wrong. My second post has accurate numbers.
And fyi I'm using -112.5mV undervolt capped at 1.35GHz. But it doesn't work at 1.8 GHz (I haven't tested anywhere in between) because undervolting isn't linear.

yoft1 said:
Depending on what version of darkside you're using, you could very well be running stock voltages. Tdj has gone back and forth in using and not using undervolt in his kernels. You are correct in saying that when I recorded these I was in the darkside kernel (hence the voltages listed for overclocked speeds) but I made sure that it was a version running stock voltages and I crossed checked the standard clock speeds with a stock kernel.
Disregard my post where I talked about a 75mV undervolt, those numbers are wrong. My second post has accurate numbers.
And fyi I'm using -112.5mV undervolt capped at 1.35GHz. But it doesn't work at 1.8 GHz (I haven't tested anywhere in between) because undervolting isn't linear.
Click to expand...
Click to collapse
So that's -112.5mV across the board up to 1.35GHz?
example:
192MHz @ 687.5mV
486MHz @ 737.5mV
756MHz @ 812.5mV
1026MHz @ 912.5mV
1350MHz @ 1037.5mV

goldfingerfif said:
So that's -112.5mV across the board up to 1.35GHz?
example:
192MHz @ 687.5mV
486MHz @ 737.5mV
756MHz @ 812.5mV
1026MHz @ 912.5mV
1350MHz @ 1037.5mV
Click to expand...
Click to collapse
It is across the board but with the caveat that 800mV is the minimum. That number is widely accepted to be the lowest you can undervolt without actually worsening the battery life. So your numbers are right except 702 mhz and below are all 800 mV.

[Q] Best kernel for battery life?

Hey, what's the best kernel for battery life?

There's no definitive answer, only recommendations that you can try out for yourself. Give ktoonsez kernel a shot.
Sent from my SGH-I747 using Tapatalk 4 Beta

Domoo said:
There's no definitive answer, only recommendations that you can try out for yourself. Give ktoonsez kernel a shot.
Sent from my SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'm currently using kt747

TimeAndroid said:
I'm currently using kt747
Click to expand...
Click to collapse
Which governor are you using? Some are aimed at improving battery life. Are you playing around with the CPU frequencies?

Enmitix said:
Which governor are you using? Some are aimed at improving battery life. Are you playing around with the CPU frequencies?
Click to expand...
Click to collapse
Yes, I undervolted and unclocked one step. I am currently using nightmare

Running HyperDrive (newest) and its been amazing. Unplugged from charger yesterday at 4:00 pm (91%) and hasnt touched a charger since. its now 9:00 pm the next day and still at 36%. 29 hours and still at almost 40% charge..not bad!!
Havent flashed a seperate kernel, just using the one that comes with the ROM.

cadorette said:
Running HyperDrive (newest) and its been amazing. Unplugged from charger yesterday at 4:00 pm (91%) and hasnt touched a charger since. its now 9:00 pm the next day and still at 36%. 29 hours and still at almost 40% charge..not bad!!
Havent flashed a seperate kernel, just using the one that comes with the ROM.
Click to expand...
Click to collapse
HyperDrive is a ROM, yes?

TimeAndroid said:
Hey, what's the best kernel for battery life?
Click to expand...
Click to collapse
Have u flashed the tk mod with ktoonsez kernel? When I used that kernel I had great results with ktoonservative/bfq combo.

DMF1977 said:
Have u flashed the tk mod with ktoonsez kernel? When I used that kernel I had great results with ktoonservative/bfq combo.
Click to expand...
Click to collapse
What does bfq do?

TimeAndroid said:
What does bfq do?
Click to expand...
Click to collapse
It's one of the choices for the scheduler. Such as row, sio, bfq, cfq, etc.U should really check out the tk mod thread though... Good stuff!

TimeAndroid said:
HyperDrive is a ROM, yes?
Click to expand...
Click to collapse
Yeah, http://forum.xda-developers.com/showthread.php?t=2176793 which is interesting as it runs the stock kernel...

DMF1977 said:
It's one of the choices for the scheduler. Such as row, sio, bfq, cfq, etc.U should really check out the tk mod thread though... Good stuff!
Click to expand...
Click to collapse
Link please?

TimeAndroid said:
Link please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2201555
There ya go bro... Check it out!

I would suggest :
81-1728 or 1809
Keep the scheduler that works best for you
Ktoonservative:
Boost cpu:1134
Down threshold: 70
Down threshold hotplug:55
Freq step:3
No 2nd cpu screen off:1
Sampling down factor:2
Sampling rate:25000
Sampling rate screen off:45000
Up threshold:88
Up threshold hotplug:93
And with any app that can run scripts( i prefer busybox installer) run this script to apply my asswax settings on your cpu1 instead of interactive.
Dropbox link: http://db.tt/YlJqAV52
echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo 486000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq
echo 50 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us
echo 1026000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq
echo 85> /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load
echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load
echo 200000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step
echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step
echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq
echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq
echo 1250 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
http://forum.xda-developers.com/showthread.php?p=44346137

liltitiz said:
I would suggest :
81-1728 or 1809
Keep the scheduler that works best for you
Ktoonservative:
Boost cpu:1134
Down threshold: 70
Down threshold hotplug:55
Freq step:3
No 2nd cpu screen off:1
Sampling down factor:2
Sampling rate:25000
Sampling rate screen off:45000
Up threshold:88
Up threshold hotplug:93
And with any app that can run scripts( i prefer busybox installer) run this script to apply my asswax settings on your cpu1 instead of interactive.
Dropbox link: http://db.tt/YlJqAV52
echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
echo 486000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq
echo 50 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us
echo 1026000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq
echo 85> /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load
echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load
echo 200000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step
echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step
echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq
echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq
echo 1250 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us
http://forum.xda-developers.com/showthread.php?p=44346137
Click to expand...
Click to collapse
I would suggest :
81-1728 or 1809
Click to expand...
Click to collapse
You suggest overclocking?
Boost cpu:1134
Click to expand...
Click to collapse
Isn't this overclocking?

TimeAndroid said:
You suggest overclocking?
Isn't this overclocking?
Click to expand...
Click to collapse
Boost cpu isn't overclocking. You can just run 81-1512 if you prefer, the setting I gave you will work anyway