Develop Bugs

[APP][24Nov] - 4.9 - SGS1+2] Voltage Control - control OC/UV for OC kernels

I take no responsibility for ANY damage / data loss may occur. Use this at your own risk. Beta quality software!/Alpha quality features!
The news:
4.9 - THIS IS HIGLY TEST RELEASE
+ Profiles support
+ Bus frequency switching for Siyah kernel
+ Widget with profile switcher and app launcher (passive!)
+ Recovery instructions: lets you place CWM flashable boot settings deleter
+ CPU history: now can reset and refresh graphs
+ Root detection improvement (I hope...)
Voltage Control Extreme unlock Key on Android Market!
For now features exclusive to Extreme version are:
+ More than two profiles
+ CPU History page
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Click to expand...
Click to collapse
Sources available, project on google code:
http://code.google.com/p/voltage-control/
Look for kernels with this label:
Kernel developers who added VC support please show this image in your topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Uploaded with ImageShack.us
Features:
- minimum/maximum CPU frequency choosing
- selecting IO scheduler
- selecting CPU governor
- changing voltage per frequency
- chosing which frequencies should be used and which shouldnt
- saving settings to be automatically applied at boot (init.d script)
- saving/loading a OC profile
- well designed and highly optimised UI (I hope..)
- robust kernel detection, support of not-so-well-working kernels
- Siyah kernel interfaces (Charging current and GPU OC/UV)
- device info page
- (extreme) CPU usage history page
About donations:
This software is available free of charge.
It cooperates with OC kernel by raspdeep.
It uses some code from: MarketEnabler (Fool your market to make all apps visible!)
If you find this software useful, please consider funding a beer and pizza. There is a "Donate to me" link just over my avatar.
Donator list:
nitr8
kalpik
laststufo
glitterballs
screwyluie
Gembol
Coreym
Thanks!
How to?
Generally idea is simple: make changes to one tab and hit apply. If any changes have been made apply/discard buttons appear on bottom.
The first tab, "General" allows to change Scheduler,Governor/min and max frequencies.
Make changes and click apply
So, you want to pick a maximum/minimum frequency?
Just chose from slider and hit apply.
Governor/scheduler can be choosen by picking from the list, then hitting apply.
You can always discard changes before applying if you want start from loaded settings.
The "Advanced" tab has sliders to control undervolting settings and green/red icons, representing enabled/disabled state.
(green = enabled, red = disabled)
Pick your settings and hit apply, or discard and start over.
Profile support:
If you want to save as boot or as profile, you need to make adjustments and on "General" or "Advanced" tab and then apply them where applicable.
To save as boot -> press menu key, then select "Save as boot settings".
To save as profile -> press menu key, then select "Save profile".
Boot settings are automatically loaded on every device boot.
Profile settings can be loaded by pressing menu -> "Load profile"
Both "boot" and "profile" settings can be deleted from menu.
RECOVERY
If Your device freezes after boot because of too agressive boot settings:
Flash Voltage Scheduler Remover by user Coreym, via CWM. Don't forget to press thanks under one of his posts!
FAQ:
Q: Extreme version?
Yes, I wanted to give some extras for people that support my work.
For now features exclusive to Extreme version are:
+ overvolting capability (max +50mV, 1500mV absolute maximum)
+ increased uv range (max -250mV)
Q: What is it?
Its voltage control app for undervolt and overclocking kernels providing sysfs interface, designed and implemented by raspdeep (thank You!) It is being tested on his kernel releases and I can guarantee (kind of) its functionality on those kernels.
The idea of the app is to keep all simple as possible, not adding any startup services and reusing existing solutions (such as init.d support).
Q: What does it mean to undevolt, and what is overclocking?
Read more in "OC / UV 101" section That is a detailed(sort of) explanation what UV/OC means.
Check this great overclocking/undervolting guide by shaolin95 (thanks!) and discussion topic!
Prerequisites:
-root (superuser + su)
-busybox
-OC kernel supporting either UVLF and UVHF (Version 1.61) or UV_mV_table (1.97 and up)
-init.d scripts support for apply on boot
3.0.1 - OLD version;

Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.

Thanks for this app! it's a nice tool. Once feature request for the OP would be an explanation of the different schedulers. I'm using noop after some research.
Edit: I guess it would be an OP request, not a feature request.

curious, may i ask what is the difference between noop, anticipatory, deadline, and cfq?

Just search it on wikipedia.
It seems noop is the best with flash memory.
Sent from my GT-I9000 using XDA App
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.

Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works

oswade said:
Doesn't seem to work with YA-OK kernel (which supposably implements rasdeeps oc 1.1). Black screen same as above poster.
Might be a kernel problem, so I'll wait for the next version, hopefully it works
Click to expand...
Click to collapse
YA-OK is not using my UV code hence this app wont work. he hardcoded the UV values if im not wrong

Lio78 said:
Thank's, this app is awesome.
Now i've Super Optimized JPM-JP6 Kernel v.3.7 and this run with -50 Low -25 High scheduler anticipatory (Lagfix NO RFS overkill JFS Bind=false)
and all works great.
Click to expand...
Click to collapse
I use the same kernel and same settings but all i get when i open this app is a black screen and the su popup. Is there something else i have to setup so that app will work?
May it have something to do with setcpu?

An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.

ggonzalez7777 said:
An recommendations for stable UV on 1200MHz OC kernel? Specifically for the 1000-1200MHz range? I have the 100-800MHz range at -50mV.
Click to expand...
Click to collapse
I've been on 0, 25, 50, 75, 100, 100 on 1.2 Ghz - its been stable for "normal" use - but i dont stress it out with video/ 3D etc - so YMMV.

New version posted, first post updated.

nice bro!
one suggestion: add checks so it wont show blank screen if the values are not read properly or folders/file not found and display messages
sometimes peeps run a wrong kernel and expect your app to work

Which version is better for SetiroN's 1.2 kernel?

Will look into it, most of checks are there, but I might have forgotten about some
MikeyMike01 said:
Which version is better for SetiroN's 1.2 kernel?
Click to expand...
Click to collapse
As of today: 1.61. Both use old UVLF and UVHF implementation.
0 50 100 75 75 125 seems to be working here

Alright... I wont upgrade then.
Sent from my SAMSUNG-SGH-I897 using XDA App

Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
DataInputStream osRes = new DataInputStream(process.getInputStream());
BufferedReader br = new BufferedReader(new InputStreamReader(osRes));
res.add(br.readLine() + "");
br.close();
Click to expand...
Click to collapse
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.

xan said:
Cant get over this "blank screen issue". I've *almost* isolated the issue, it lies in these lines:
Cat command returns under 64 chars when file is found, when it isnt output is >64 chars.
Thats the reason for block, somewhere in these lines.
Click to expand...
Click to collapse
Glad you know of this issue, on my captivate the older version works fine but when upgrading to the new one it is stuck on the black screen forever. It says SU permission granted but just stays on the black screen. I tried uninstalling the old first, rebooting, then installing and also just overwriting the old with new. Nothing but black.
Good luck on the fix, this is a very handy app

loco- said:
Just search it on wikipedia.
It seems noop is the best with flash memory.
Click to expand...
Click to collapse
I agree, here are a couple of comments that convinced me:
You want to use noop scheduler on devices where there are no seeking penalty, such as flash drives. That's why USB stick wants noop. Unfortunately, harddisks are very mechanial beasts and their performance is highly controlled by their seeking abilities. All these schedulers above are really trying to figure out how to extract maximum performance off the harddisk without causing bad behaviour in other cases.
noop is often the best choice for memory-backed block devices (e.g. ramdisks) and other non-rotational media (flash) where trying to reschedule I/O is a waste of resources.
http://www.linuxhowtos.org/System/iosched.htm
http://stackoverflow.com/questions/1...-i-o-scheduler
Click to expand...
Click to collapse
E: doesnt work for me anymore. Blank screen only.
Just reflashed jpo yesterday and oc kernel 2.1 by rasp.
Click to expand...
Click to collapse
When I installed the new version 1.97beta, it too sat at a black screen for an unusually long time, then after almost a minute, the supperroot permission screen poped up, I granted it root rights, and then voltage control came up fine.

Hm, read first post.

xan said:
Hm, read first post.
Click to expand...
Click to collapse
Umm, what post is this comment directed to?
Unclear what topic, and what in the first post we are looking for?

[ACS]Battery Tweak for the NS4G RC1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shabbypenguin and the Android Creative Syndicate
present to you
Battery Tweak RC1​
This is really a tool for power users
If you don't consider yourself 'comfortable' with messing with your phone, then don't.
This is mostly the work of collin_ph, all the ideas are mostly his and I have only contributed in part to getting some things functioning correctly and some optimizations for the NS4G.
What does it do?
This tweak creates a service that periodically checks the phone's power source.
If the power source changes, it reconfigures the device for maximum performace, battery and safety.
Tweaks memory settings for current power source
Re-clocks CPU based upon battery remaining or current power source
Reclocks for maximum performance if on AC power
Reclocks for maximum performance and charging safety if on USB
Reclocks for performance and battery if on Battery
As Battery life is diminished, Maximum CPU frequency is lowered
Tweaks scaling charactaristics depending on power sourcee
CPU Scales up less frequently on battery power
CPU Scales up more frequently on USB/AC power
The CPU is allowed to scale dynamically in all charging states based upon CPU usage
Includes a batt-cfg utility to configure the system
You may load 1 of 3 pre built profiles
Manually configure CPU Frequencies in all charging states
Determine the percentage of underclocking as the battery drains
Configure how often to poll the power state / battery statys
Disable batt.sh service from running at startup
Includes a batt-rm.sh uninstall utility
Includes a batt-diag diagnostic utility
Includes optional Disk performance tweaks (enabled by default)
Includes overheating controls to lower your cpu if the phone starts to overheat
The Tools
The entire 'application' is written in shell code and was first written just to give a performance and battery boost, but since has evolved more and more.
All the tools mentioned will be utilized either through the terminal, or in adb shell.
batt.sh
This is the core of the entire script. Don't mess with it.
The one thing you should do after installing the script:
Code:
Code:
pidof batt.sh
If theres any number showing up after it, then it's working fine.
batt-cfg
This is the 'main menu' of sorts, as it gives the user all the options and allows them to toggle tweaks/mods on the fly.
batt-diag
It's a diagnostics utility, allowing you or someone knowledgeable to figure out any issues that you may be having with your device and be able to pinpoint exactly where the problem is.
batt-diag -v gives a more thorough output as you can see here; http://pastie.org/1162034
batt-rm.sh
It's a battery tweak removal script, follow the onscreen prompts and it should remove just about any trace of the battery tweak script.
The Presets
The presets are just default configurations that I have set up that can make your phone more efficient without you, the user, having to manually set everything.
The preset of 800 literally means that 800000 is the scaling_max_freq, or the max frequency, that your phone can achieve after you enable it.
Just typing 1, and then enter, you'll be ready and set to go. Same with 2 or 3.
Customize Settings
This is only for the experienced user, and it allows you to manipulate most/ifnotall the configurables on your device.
Note, you do not need to configure anything to enable this battery mod. Default settings will be assigned at 800MHz.
All the settings explain what each option does, so read them carefully.
Disk Boost
Remounts via noatime and nodiratime. Look up what that means on your own, and why it benefits performance the way it does.
Prerequisites needed to run this
netarchy's kernel
Matr1x kernel
seems to work with every rom
If you're running any other kind of kernel, feel free to try it but i cannot guarantee that it will work.
This script will WORK even if you don't have the import call at boot, but it won't survive on the next reboot. AKA if you dont have this rom kernel, when the phone boots it may not start batt.sh if you are willing please check and let me know if the rom/kernel supports it.
You can check via:
Code:
Code:
pidof batt.sh
NOTE: This script will also prompt you to try to run itself as root if you use it in terminal.
Contributors:
Collin_ph
Decad3nce
myn
onicrom
shabbypenguin
nullghost (aka tehdarkknight)
nubecoder - so he might not cry any moar
Download
*make sure to ignore some of the finer things on the screens they came from the epic version which im working on *
*make sure you are running these as root*
*disable setcpu while running this*

reserved for something

Makes me want to get a Nexus...
EPIC PORT [email protected]!!!!!

why so you can try it on your evo3d?

Great job bro!
Sent from my Nexus S 4G using Tapatalk

I can't wait to try this.
dreamsforgotten said:
Great job bro!
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
OT: but those lyrics are from Tears for Fears, he simply did a cover
Sent from my Nexus S 4G using XDA App

derekwilkinson said:
I can't wait to try this.
OT: but those lyrics are from Tears for Fears, he simply did a cover
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well I covered my ass by citing a reference : p
Sent from my Nexus S 4G using Tapatalk

Now that's what I'm talking about, great job can't wait to get this up and running
Sent from my Nexus S 4G using XDA Premium App

Nice job. I might play around with this later tonight. Nicely done.

I install it but were i go for settings?
Sent from my Nexus S 4G using Tapatalk

renizo said:
I install it but were i go for settings?
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
batt-cfg check the op for more
Sent from my Nexus S 4G using Tapatalk

either thru terminal emulator or adb shell

Anyway to add support for init.d by putting or editing a different script? Using opensoju, i dont know much about init.d or how it is implemented into a rom.

I love this original mod by collin. Glad to see you guys working w him
Uncle Jimmy says hello

uhh no idea all i know is the init script is there

It's been forever since I've used Collin's tweak with my Hero so please forgive the stupid question: if I flash a Rom or kernel do I need to reflash the batt tweak zip?
Sent from my Nexus S 4G using Tapatalk

rom yes, kernel no

shabbypenguin said:
uhh no idea all i know is the init script is there
Click to expand...
Click to collapse
After flashing netarchy beta 1.3.5, init.d was created and is executing at boot. In the kernel. Learn something new everyday Thanks for this mod. Ima big fan of ACS.
Uncle Jimmy says hello

running deck's ROM 1.2x, netarchy kernel 1.3.0.12 CFS universal and it survives reboot,.
Thanks for this. I also ran this on my hero back in the day.

so you can just flash this zip & you're ready to go if you want to leave everything at their default state?
everything seems to be working for me with KingsROM & Netarchy Kernel!

[TIP] Single/Dual/Quad Core Mode (Configurable)

While ago I posted a reply on a thread on how to control the CPU speed and override Tegra 3 controlling it and setting it to dual core mode. I forgot to reply back on that thread, but instead I thought it would be better to create a new thread, since not much people would read it (Credit to k0rner for reminding me... (k0rner thread)
/sys/kernel/debug/tegra_hotplug/max_cpus
This is not touched by the Android OS, and will remain in whatever state we set until reboot (back to 4).
Set this to "1" will make the phone only use 1 core (Doesn't work, only 2,3,4 does)
Set this to "2" will use 2 core
Set this to "3" will use 3 core
Set this to "4" will use 4 core (default)
1) Use Root_Browser (Free) or Root Explorer
2) Go to /sys/kernel/debug/tegra_hotplug/
3) Hold max_cpus
4) 'Open With', Text Editor
5) Change Value (Default 4) to how many cores you want (ie 2 = dualcore)
6) Download Tegrastats and see the result
EDIT: http://forum.xda-developers.com/showpost.php?p=26056320&postcount=48 (Control Core, via App, credit Meltus)
EXTRA: http://forum.xda-developers.com/showpost.php?p=25637797&postcount=10 (credit kolargol)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

http://forum.xda-developers.com/showthread.php?t=1627517
not sure if this is the same mate but if you access the powersave settings there is an option as well were you can switch only one core on and drop the cpu clock speeds to 1GHz. Just check the thread out that i gave the link to

NoobTerminator said:
http://forum.xda-developers.com/showthread.php?t=1627517
not sure if this is the same mate but if you access the powersave settings there is an option as well were you can switch only one core on and drop the cpu clock speeds to 1GHz. Just check the thread out that i gave the link to
Click to expand...
Click to collapse
Thats only when you reach to lower than 10%, thats when it clicks in, correct me if im wrong.

MrPhilo said:
While ago I posted a reply on a thread on how to control the CPU speed and override Tegra 3 controlling it and setting it to dual core mode. I forgot to reply back on that thread, but instead I thought it would be better to create a new thread, since not much people would read it (Credit to k0rner for reminding me... (k0rner thread)
/sys/kernel/debug/tegra_hotplug/max_cpus
This is not touched by the Android OS, and will remain in whatever state we set until reboot (back to 4).
Set this to "1" will make the phone only use 1 core (Single Core Mode + Low Companion Core)
Set this to "2" will use 2 core
Set this to "3" will use 3 core
Set this to "4" will use 4 core (default)
1) Use Root_Browser (Free) or Root Explorer
2) Go to /sys/kernel/debug/tegra_hotplug/
3) Hold max_cpus
4) 'Open With', Text Editor
5) Change Value (Default 4) to how many cores you want (ie 2 = dualcore)
6) Download Tegrastats and see the result
Now enjoy your phone with less heat
NOTE: I will edit later on how to change clockspeed without Tegra 3 controlling it through SetCPU.
Click to expand...
Click to collapse
Sorry for the obvious question, but I am orientating for buying X or S.
Is the heating problem that serious to go back to 2 cores?

JacoA said:
Sorry for the obvious question, but I am orientating for buying X or S.
Is the heating problem that serious to go back to 2 cores?
Click to expand...
Click to collapse
It is a bit of an overkill having four cores, I find than two cores is enough for me and games don't lag on it. It does get quite warm, depending what you do, alot less with two cores.
I wouldn't recommend the One S at all. I would just wait for the S3.

All good great too lol I will add that tegra stats is a massive battery drain.
Also controling the speed will be nice ill be sure to let the setcpu dev know once you let us know
Sent from my HTC One X using xda premium

Do I need to root my phone for this?

luba6ky said:
Do I need to root my phone for this?
Click to expand...
Click to collapse
yes

Hello,
Further to Kolargol's post here : http://forum.xda-developers.com/showthread.php?t=1633245
i set up the tasks in tasker but it's not working
Checking, I don't have tegra_hotplug folder in sys/kernel =(
I'm using root explorer.
What am I doing wrong ?
Thanks for your help

My sys/kernel/debug folder is empty too. I'm on Android Revolution 5.0.

It's there on leedroid have you tried adding the folder to see if it works?
Sent from my HTC One X using xda premium

I also tried with sys/devices/cpu/cpuX/online with 4 commands per task (1 per CPU) but it's not working either =(

treebill said:
It's there on leedroid have you tried adding the folder to see if it works?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Getting "new folder creation failed" in bought root explorer with su right and r/w enabled. Think I'll install LeeDrOiD tonight.

SAme here

Sure you checked carefully? I've been on both Leedroid and ARHD and they do exist.
/sys/kernel/debug/tegra_hotplug

MrPhilo said:
Sure you checked carefully? I've been on both Leedroid and ARHD and they do exist.
/sys/kernel/debug/tegra_hotplug
Click to expand...
Click to collapse
Quite sure. Nothing there. And can't be created.

Flashed Leedroid and the folder is there, trick with tasker working perfectly well !

ARHD 5.X.X
Originally Posted by mike1986.
ok, my fault this time, sorry!
Open root explorer, go to system/etc/ and open init.post_boot.sh
navigate to line 115 and remove:
umount /sys/kernel/debug
save and reboot!
sorry! BTW what does it allows you to do?
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
rahan95 said:
Flashed Leedroid and the folder is there, trick with tasker working perfectly well !
Click to expand...
Click to collapse
can you share wht you did?

Well, I flashed Leedroid too, and now I'm able to change it no problem. However it doesn't really obey my 1 CPU rule and activates a 2nd core whenever it feels it really needs it. That's ok I guess. Really smooth, though. No lag at all.
I've also played around a bit with the throttle settings in the CPU-tegra folder. It has a throttle_table where you can set individual frequency settings, but so far no matter what I set it to, it seems to throttle to 340Mhz which is slooow.
A reboot sets everything straight. Hopefully this'll be able to save us some sweet battery time.

Little bit where it all comes from:
Code:
mount debugfs debugfs /sys/kernel/debug
is inside init.endeavoru.common.rc in ramdisk
init.endeavoru.common.rc contains also following code:
Code:
write /sys/module/cpu_tegra3/parameters/no_lp 0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor ondemand
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor ondemand
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_max
chown system /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
chown system /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy
chown system /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
chown system /sys/devices/system/cpu/cpufreq/ondemand/touch_poke
chown system /sys/htc/power_save
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate_min 10000
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate 50000
write /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor 4
write /sys/devices/system/cpu/cpufreq/ondemand/io_is_busy 1
write /sys/devices/system/cpu/cpufreq/ondemand/up_threshold 90
write /sys/devices/system/cpu/cpu1/online 0
write /sys/devices/system/cpu/cpu2/online 0
write /sys/devices/system/cpu/cpu3/online 0
[COLOR="Red"]write /sys/kernel/debug/tegra_hotplug/max_cpus 1[/COLOR]
write /sys/module/cpuidle/parameters/lp2_in_idle 1
So changing /sys/kernel/debug/tegra_hotplug/max_cpus is not permanent, it will be back to the default value each reboot.
Also keep in mind that /sys/kernel/debug contains details about kernel settings, I don't think that changing it can reflect in anything.
I may not be right of course, please feel free to correct me if I'm wrong

[KERNEL]Lightning Zap *OC/UV* (Updated 1/9/13)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Krazeecracker, Thomas.Raines and Team Fah-Q! presents
The Lightning Zap! kernel for the Hercules
ATTN:
I Krazeecracker, thomas.raines, Team Fah-Q!, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise screw up your device.
I revamped the Lightning Zap! kernel across the board. Since I have so many of them I was loosing where I was on each one. So I have now broken it down into 3 phases:
Phase 1: Introduction of LZ kernel to device
Phase 2: Fine tuning of tweaks, values, etc
Phase 3: Implementation of OC/UV
Phase 4: Continue updating and adjusting as necessary
From now on I will name the .zip accordingly as well:
Sky_p2.1
On a good note, I think this latest update will finalize phase 2 and now I can work on OC/UV...
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Instructions:
Make a backup
Download LightningZapv1Sky.zip to PC
Transfer LightningZapv1Sky.zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Phone will automatically reboot after install**
Wait 10 minutes
Enjoy the Lightning Zap!
ATTN!
If you are currently on any version of Lightning Zap! kernel, you must either replace your build.prop from your ROM or re-flash your current ROM. Or you can open your build.prop with a text editor and delete all lines below the Lightning Zap Tweaks entry.
This kernel was tested on ParanoidAndroid. This kernel and tweaks will work with any version of CM10 post 14OCT.
**First boot, especially after a fresh install of your ROM (wipe system cache etc, flash ROM gapps Lightning Zap) will take a while. It will seem to hang between a blank screen (which use to be the 2nd boot splash) and the boot animation. There is no need to panic. Everything is fine. It is the vacuum script trying to clean databases that have yet to be created. After first boot, your phone will boot as normal (a little faster actually)...
After first boot, ensure your I/O scheduler is set to cfq and your governor is set to ondemand to gain the maximum benefits of Lightning Zap!
See 3rd post for further instructions on improving and customizing your Lighting Zap! experience.
Source Code:
msm8660-common_lz_kernel
vendor_lz-kernel.git(scripts and zipalign binary)
Special thanks to:
gs2usr for the link to source code...
xan for Voltage Control app

Download links and changelog
Downloads and changelog
Sky_p3.2-1.zip
Vibration fixed thanks to tmob.
Sky_p3.2.zip with rotation fix included
Skipped 3.1 because it was incomplete
Added userspace voltage control (You can now use an app or script to control your voltage. I tested with Voltage Control (preferred) and Antutu CPU Master)
For badass battery life, I am using noop io-scheduler, Lionheart governor, underclocked at 1026Mhz, and globally dropped voltage by -100mV
Deep sleep is working right again (doesn't take forever for it to enter ds)
Leaned up thread and removed old versions. They are gone for good so please don't ask...
Sky_p3.0.zip
Fixed the ability to set max/min cpu frequency. Thanks to car vs driver for pointing me in the right direction
Added OC/UV from flappjaxxx h0tcakez kernel source
Fine tuned ondemand governor
Archived changelog
Plans:
I want to trim down the oc frequencies. I think that 29 is just too much. I also want to cut back on the governors and io-schedulers. There are so many to choose from and everyone has their preferences. How bout some feedback in the general scetion here
Enjoy the Zap!

More tips and tricks
This is already included but left for reference.
The governor tweak is set for a fairly balance of performance and battery life. If you find yourself needing battery life over performance, you can make some minor changes. Here's how:
1 Download Script Manager from the market (it's free)
2 Open Script Manager and navigate to /system/etc/init.d
3 Press menu/more/advanced options and select mount as RW
4 Select 01governor and select "edit" at the top (this will open the file in atext editor)
5 Uncomment (remove # in the particular line) and change:
Code:
echo "45" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
To:
Code:
echo "[COLOR=red]70[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
6 Select menu/save
7 Press the skull and cross bones icon at the top (this will allow Super User)
8 Press run, close app and enjoy
This will result is slightly slower performance but higher battery life.
If you want even better battery life:
1 Following steps 1-4
2 Add a # at the begining of lines 11 to 19
3 Scroll to "pwoersaver" section
4 Remove the # at the begining of lines 28, 30-38 and 43
Code:
#AWAKE_GOVERNOR="ondemand"
#SLEEP_GOVERNOR="ondemand"
# echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
etc
Code:
AWAKE_GOVERNOR="powersaver"
#SLEEP_GOVERNOR="powersaver"
echo "20000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate;
5 Follow steps 6-8 (no need to select super user icon if you already did)
This will result in lower performance, but ultimate battery life
When running in a higher performance mode (especially for gaming) you can disable powersave_bias by changing the 1 to a 0 like this:
Code:
echo "1" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo "[COLOR=red]0[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
Powersave_bias only allows the CPU to peak for small increments at a time, and not allow the CPU to remain peaked even when the system calls for it. In gaming, that could result in choppy, laggy perofrmance and slow FPS..
Although it says not to in the script, you can change the sampling rate as well. Do not go below 50000. I left it at 57500 as I found this seems good setting for smooth scrolling and performance.
Code:
echo "[COLOR=Red]57500[/COLOR]" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
Always leave SLEEP_GOVERNOR="powersave" uncommented (no #) and do not uncomment any other SLEEP_GOVERNOR as this will keep ultimate battery save while screen is off.
Only change values in increments of 5 for the up_threshold.
This is already included but left here for reference.

Source code tips
Needs updating.
just add this to your local_manifest.xml:
Code:
<remote fetch="https://github.com/TeamFahQ" name="LZkernel" />
<project name="msm8660-common_lz_kernel.git" path="samsung/msm8660-common" remote="LZkernel" revision="jellybean" />
<project name="vendor_lz-kernel.git" path="vendor/lz-kernel" remote="LZkernel" revision="master" />
Then add this to your cm.mk file i your device directory:
Code:
# adding Lightning Zap tweaks to build
$(call inherit-product, vendor/lz-kernel/lightningzap.mk)
And don't forget to remove the kernel entry in your cm.dependencies found in your device directory...

First! This should be fun...
Sent from my Nexus 7 using xda app-developers app

Nice... If only it had OC/UV... the dev said he would add it later.

Nice, but I have to admit this is quite confusing for me to read, a lot of stuff. (I'm ADHD)

TheLastSidekick said:
Nice, but I have to admit this is quite confusing for me to read, a lot of stuff. (I'm ADHD)
Click to expand...
Click to collapse
Lol, basically just flash with the rotation fix and your good to go. If you have the need for more juice then follow the third post. And fourth is for adding to an existing ROM your going to build, i.e. your kangs

Wait so this is the same as the one on skyrocket? So we still need rotation fix?
Sent from my All-Starred P.A.C SGH-T989

ArcticFish said:
Wait so this is the same as the one on skyrocket? So we still need rotation fix?
Sent from my All-Starred P.A.C SGH-T989
Click to expand...
Click to collapse
Correct lol

Couldn't you just merge the rotation fix zip and the kernel together? It would make things easier in a sense.

Shmi117 said:
Couldn't you just merge the rotation fix zip and the kernel together? It would make things easier in a sense.
Click to expand...
Click to collapse
done!

Thanks! I'll be sure to incorporate your kernel in an upcoming build dedicated to battery life!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

https://www.dropbox.com/s/vofmxdvp1mbuqkp/SkyLZv3.zip rotation fix included and now in OP!

Pardon me if I missed it, but is this kernel for Jelly Bean or Ice cream sandwich? Thanks.

GreggoryD502 said:
Pardon me if I missed it, but is this kernel for Jelly Bean or Ice cream sandwich? Thanks.
Click to expand...
Click to collapse
Jellybean only

I am currently on all-star ROM and on speed test the download is about 1mb slower but the upload was about 1.5mb higher on my network. I also notice the vibration isn't as strong is that me or does it have to do with the kernel as for battery I'm not sure yet. Thanks
Sent from my SAMSUNG-SGH-T989 using xda premium

Flashed on Dec 1 AOKP nightly.. working good so far.. thanks!!!
Sent from my Jellylicious T989

Running now, thanks man! Gonna run a full cycle tomorrow and will report back on battery

droidz79 said:
I am currently on all-star ROM and on speed test the download is about 1mb slower but the upload was about 1.5mb higher on my network. I also notice the vibration isn't as strong is that me or does it have to do with the kernel as for battery I'm not sure yet. Thanks
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Vibration is fine on my end. And its also sleeping like a baby. And running it through the yes yesterday before posting it ran comparable to kko! :thumbup:

Boost every millimeter of ur GPU

Guys...was just browsing few forums on XDA and found this ...
This is supported for all android versions(as i realised from reading comments).
Here is link to thread...
All credits to dev..
#me not responsible if flashing bricks device(but don't worry it surely wont )...
Will increase ur graphics score on antutu by +200....
Just try it...
http://forum.xda-developers.com/showthread.php?t=2295010
@iceyhotguy , would like your comment about it...
All here who use it, just lemme know if it butters up something(not a placebo effect at all ..dont worry)... @testerforgrand ..all comments are awaited and welcomed...
Hope i helped...
Sent from my GT-I9082 using Tapatalk

Moderator pls move thread to general section..i mistakenly posted here :-|...
Sent from my GT-I9082 using Tapatalk

raghavsharmaxda said:
@iceyhotguy , would like your comment about it...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Ok, the build.prop edits he mentions,
busybox echo "debug.sf.hw = 1" >> /system/build.prop ----- renders UI with GPU
busybox echo "video.accelerate.hw=1" >> /system/build.prop ----- Increases responsiveness of the video
busybox echo "ro.HOME_APP_ADJ=1" >> /system/build.prop ---- this is to force the default launcher into memory. I excluded this because most launchers already stay in memory and this tweak is known to fail when the launcher used is heavy. Probably why the line has been striked off in the OP's post but seems to still be there in flashable zip
busybox echo "persist.sys.use_dithering = 1" >> /system/build.prop ----- this is to enable surface dithering, in other words this may improve visual quality but is also known to cause banding in some devices that's why I didn't include it in my post. It's safe enough to try but you know what to remove if it gives you lines across the screen whenever the color contrast is changing.
Other than that the graphics library included is essentially a touchscreen driver to re-calibrate the touch response, this will definitely work, it is not a placebo but I cannot say if it'll actually make it better or less responsive.
As far as the script included goes, there's a good chance that it won't work.
The script is referring to "/sys/class/touch/switch/set_touchscreen" but we don't even have a touch class
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And even if we did, I'm not sure I would use the same values as he has.
As far as the antutu score goes, I don't trust the scoring system even a little bit
It's highly unreliable in terms of accessing the exact performance index, but it is good for dividing the phones performance in quadrants confirming you have a better (or worse) hardware than other phones
Conclusion : You can flash this if you want to, but I wouldn't.
Build.prop tweaks can be manually tested and removed.
You can recalibrate your touch on your own although you don't really need to.
And like I said, the script is referring to an address that doesn't exist at that location in our phone.

iceyhotguy said:
Ok, the build.prop edits he mentions,
busybox echo "debug.sf.hw = 1" >> /system/build.prop ----- renders UI with GPU
busybox echo "video.accelerate.hw=1" >> /system/build.prop ----- Increases responsiveness of the video
busybox echo "ro.HOME_APP_ADJ=1" >> /system/build.prop ---- this is to force the default launcher into memory. I excluded this because most launchers already stay in memory and this tweak is known to fail when the launcher used is heavy. Probably why the line has been striked off in the OP's post but seems to still be there in flashable zip
busybox echo "persist.sys.use_dithering = 1" >> /system/build.prop ----- this is to enable surface dithering, in other words this may improve visual quality but is also known to cause banding in some devices that's why I didn't include it in my post. It's safe enough to try but you know what to remove if it gives you lines across the screen whenever the color contrast is changing.
Other than that the graphics library included is essentially a touchscreen driver to re-calibrate the touch response, this will definitely work, it is not a placebo but I cannot say if it'll actually make it better or less responsive.
As far as the script included goes, there's a good chance that it won't work.
The script is referring to "/sys/class/touch/switch/set_touchscreen" but we don't even have a touch class
View attachment 2537152
And even if we did, I'm not sure I would use the same values as he has.
As far as the antutu score goes, I don't trust the scoring system even a little bit
It's highly unreliable in terms of accessing the exact performance index, but it is good for dividing the phones performance in quadrants confirming you have a better (or worse) hardware than other phones
Conclusion : You can flash this if you want to, but I wouldn't.
Build.prop tweaks can be manually tested and removed.
You can recalibrate your touch on your own although you don't really need to.
And like I said, the script is referring to an address that doesn't exist at that location in our phone.
Click to expand...
Click to collapse
Turns out that this thread was nonsense share :|..sorry..(i realised i do type alot after its 12am in my country(staying awake whole night even when sleepy, which leads to typing mistakes and poor judgements..and sometimes illogical helping answers ..
Sorry for trouble )..
Thanks for always helping and guiding me !!
Sent from my GT-I9082 using Tapatalk

raghavsharmaxda said:
Turns out that this thread was nonsense share :|..sorry..(i realised i do type alot after its 12am in my country(staying awake whole night even when sleepy, which leads to typing mistakes and poor judgements..and sometimes illogical helping answers ..
Sorry for trouble )..
Thanks for always helping and guiding me !!
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Haha, it's no trouble at all. You didn't make poor judgements, you shared something that you thought would improve performance for our phones, and if this was our device specific there might have been improvements in atleast the touch rendering through GPU.
You asked me to comment on it, so I opened the code and explained each part to the best of knowledge . That's what xda is for, to learn new things about the devices we use everyday and explore what more can be done with them!
This is a thousand times better than the usual spam that flows through grand duos community, so keep exploring XDA for useful threads till you know enough to start developing yourself

@raghavsharmaxda icehotguy is Indian too
Sent from my GT-I9082 using Tapatalk

akiratoriyama said:
@raghavsharmaxda icehotguy is Indian too
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
oh i didnt knew that
sorry sorry !!