Related
THIS COMES WITH ABSOLUTELY NO WARRANTY.
I AM NOT RESPONSIBLE FOR WHAT THIS KERNEL MAY OR MAY NOT DO TO YOUR PHONE, ESPECIALLY WHEN YOU OC!
This is based on CM's 2.6.35.13 kernel.
Credits include Cyanogen, x99percent, scaryghoul, faux123, -snq, LordClockaN, and others that I couldn't find out who to credit for. If I used your code and you're not mentioned here, let me know!
GPL IN, GPL OUT: github
Version 1.0
- Added SmartAss Governor
- Added Scary Governor
- Added MinMax Governor
- Minor UV, as it depends on your own device. I suggest using the VDD sysfs interface to tweak them yourself.
- Added VDD sysfs interface (OV/UV on the fly) info/usage
- Added SLQB
- Added OC up to 1.9Ghz - SetCPU failsafe profiles are a MUST!
- Allocated more GPU memory
- Enabled swap
- Compcache is still disabled until I can get it working properly
Version 1.01
- Fixed 1.9Ghz OC
Version 1.02
- Fixed modules inside zip
Version 1.03
- Minor bugfixes
- Added TINY_PREEMPT_RCU (should help with multitasking)
Version 1.04
- Fix smartass (wouldn't go below 768mhz while awake)
- Minor bugfixes
- BFS
Version 1.05
- Added USB Mass Storage speed tweak
- Tweaked ext4 extensively
- LOTS of bugfixes
Version 1.06
- Added new governor "GreaseLightning" based on smartass
- Tweaked max readahead to 4096
- backported changes from 2.6.36.1 and 3.0rc6 (Imoseyon)
- Added Simple I/O Scheduler and set as default
- various PM fixes
- Merged HTC's vision-2.6.35-gb-MR release
- Tweaked charging code to "overcharge" for ~2 hours, should be safe and improve battery life
- Fixed netflix playback issues
GOVERNOR EXPLANATIONS:
'minmax' - this driver tries to minimize the frequency jumps by limiting
the the selected frequencies to either the min or the max frequency of
the policy. The frequency is selected according to the load.
Originally posted by erasmux -
smartass - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 - why?! - it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Originally posted by scaryghoul -
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Click to expand...
Click to collapse
I hope to add some more user-friendly control to UV/OV, hopefully in the next version.
I tested this on my device, but as stated below, there's no guarantee it will work on yours.
This kernel should only really be used on CM7 nightly 78 and above. Not sure what'll happen if you use it on earlier nightlies, but it's definitely not supported.
Performance should be as good as or better than stock kernel.
Download:
MD5SUM: 71031df052b62d276657190cd4ec94d8
dropbox (will probably go over quota and stop working) - UmaroKernel-1.06.zip
MultiUpload: UmaroKernel-1.06.zip
This kernel excites me greatly. I will be flashing it right away. Thanks!
Sent from my HTC Vision using XDA Premium App
Great work bro! I'll def. give it a shot right now!
Thanks, gonna give this a try.
You sir just made my day. So we will need to use terminal to edit our UV values until you get that dealt with, correct? Will they persist through a reboot or not?
Now this is what I was waiting for
Thank you
KCRic said:
You sir just made my day. So we will need to use terminal to edit our UV values until you get that dealt with, correct? Will they persist through a reboot or not?
Click to expand...
Click to collapse
not to get off-topic, but your sig says youre using the pyro kernel with the CM nightlies. You do know that blah said the recent nightlies are no longer compatible with that kernel, due to the CM kernel being rebased on a different kernel than the base of the pyro kernel. However, I can attest that this kernel DOES work with both nightlies and pyromod
Thanks for the 1.9GHz Will test in conjunction with the latest CM7 nightly when I get home!
Thanks. Flashed and working great. On build 91
Sent from my HTC Vision using XDA App
I just flashed this and everything is working without any issues
However, I noticed that there is no 1.9GHz option in SetCPU...
theSpam said:
I just flashed this and everything is working without any issues
However, I noticed that there is no 1.9GHz option in SetCPU...
Click to expand...
Click to collapse
Sorry for the dumb question, but did you do the autodetect?
Sent from my HTC Vision using XDA Premium App
heybobitsme said:
Sorry for the dumb question, but did you do the autodetect?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I just did and the max frequency is still 1516MHz...
theSpam said:
I just did and the max frequency is still 1516MHz...
Click to expand...
Click to collapse
Ya I just noticed the same with the built in settings as well.
Sent from my HTC Vision using XDA Premium App
heybobitsme said:
Ya I just noticed the same with the built in settings as well.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I'm having the same issue.
I know the og post said that this should mainly be used with CM7 nightlies, but I decided to give it a try with the MIUI ROM that I'm using. No dice. Wouldn't even load the bootscreen. I'm thinking I may flash over to the current CM7 nightly to give it a try though.
Sent from my HTC Vision using XDA Premium App
Im using the MIUI rom on my G2 and the smartass kernal... Freakin great if you ask me. I have about 30 to 35% battery and its about to be 1010 pm and i unplugged from charger at 730 am. Beat kernal so far.
Sent from my HTC Desire Z (actually its a G2) using XDA App
Updated OP with fixed kernel, OC up to 1.9Ghz is now supported.
Enjoy!
umaro said:
Updated OP with fixed kernel, OC up to 1.9Ghz is now supported.
Enjoy!
Click to expand...
Click to collapse
Nice! How much more memory was allocated to the GPU? Just curious...
Nice work any one test out WiFi and the kind of stuff?
Sent from my HTC Vision using XDA App
sino8r said:
Nice! How much more memory was allocated to the GPU? Just curious...
Click to expand...
Click to collapse
I think it's just under a meg, for a total of 4 megs of GPU ram instead of 3 megs.
I don't know what kind of performance gain comes from it.. I'll have to benchmark it and let you guys know.
The added memory doesn't look like it was being used by anything else, though.
*WARNING! I Am Not Responsible For Anything That Happens To Your Device*
PLEASE READ ENTIRE OP CAREFULLY, THANKS! and remember: when reporting issues, please provide more info than "my phone rebooted, anyone know why?"
Based on HTC source code. Found [HERE]My github: [HERE]
BIG THANKS TO:
Faux123, Erasmux, Scaryghoul, Nick Piggin, LeeDroid, Umaro, mdeejay, imoseyon, LorDClockaN for the reference or code I may have used
Raycaster3 for being my crash test dummie
Anyone I didnt mention.. it's not intentional, please let me know!
Included:
COMPATIBLE WITH ALL GINGERBREAD 2.3.x SENSE ROMS
Patched to 2.6.35.14
CPU OverClocked up to 1.90GHz (Higher Frequencies may be unsatble for some devices)
CPU frequecy supports 122MHz up to 1.90GHz
DARKSIDE Governor default Gov set @ 122/1017MHz
Under Volt
Lower Wifi Voltage
NOOP scheduler default
SLQB Memory Management
Extensive Ext4 tweaks
SVS support (VDD interface code thanks to @snq)
Built in WiFi Calling support
Available CPU Governors:
DARKSIDE, superbad, scary, smartass (optimized), smartass v1 (orignal smartass), smartass v2 (2nd Generation), savagedzen, lagfree, conservative, performance, ondemand, interactive, minmax, powersave, userspace
Optional I/O Schedulers:
anticipatory, deadline, cfq, bfq, vr, sio
Instructions on flashing Kernel:
1. Download and place on your SD card
2. Boot into Recovery Mode
3. Do a NAND BACKUP!!!
4. Wipe Dalvik & Cache
5. Flash Kernel
6. After flashing is complete, Reboot..
7.Wait a few minutes for Os to load and reboot again
8.If using SetCPU, make sure you reselect "autodetect speeds recommended"
9.Done!
10. Welcome to the DARKSIDE!
My Change Log:
Code:
[U][B]2.6.35.14::demonspeed v7:: (10.25.2011)[/B][/U]
-UPDATE: freq and voltages *minor*
-REVERT: "ADD: float charge after 90%"
-REVERT: "ADD: Fast charging while connected via USB"
-ADD: Frontswap
-ADD: support for XZ decompression into the kernel'
-UPDATE: Improve latencies under load
-UPDATE: use spin_lock_irqsave and spin_lock_irqrestore
-UPDATE: Fix ordering of calls in suspend error path
-UPDATE: deactivate invalidated pages
-UPDATE: mark_inode_dirty barrier fix
-UPDATE: overhaul of governors (ADDED: DARKSIDE,smartass v1, smartass v2, savagedzen, lagfree and optimized others)
-REVERT: "ADD: enable HRTICK"
-UPDATE: remove the per cpu tick skew
-UPDATE: wireless drivers
-UPDATE: PMEM_CACHE_FLUSH fixup
[U][B]2.6.35.14::demonspeed v5:: (10.1.2011)[/B][/U]
-UPDATE: increase GPU and Camera memory allocation
-ADD: put eMMC in sleep (cmd5) mode before suspend
-UPDATE: Back off suspend if repeated attempts fail
-UPDATE: prevent multiple syscall restarts
-ADD: demonspeed governor
-ADD: cleancache
-ADD: enable HRTICK
-UPDATE: Create cpufreq workqueue for freq changes
-UPDATE: decrease default dirty ratio
-UPDATE: arch/arm/mach-msm/acpuclock-7x30.c
-UPDATE: CFLAGS for Increased peroformance
-ADD: Automated per tty task groups
-UPDATE: Audio drivers | ADD: 2WCR support
-other stuff...
[U][B]2.6.35.14::demonspeed v3:: (9.10.2011)[/B][/U]
-UPDATE: CPU governors
-UPDATE: adjust audio boost, lower handset
-REVERT: "ADD: Tweaked charging to slowly "overcharge" more than 2 hours a..."
-ADD: float charge after 90%
-ADD: Jhash3
-UPDATE: FileSystem tweaks
-UPDATE: Patches from Code Aurora
-UPDATE: Set correct divx codec type
-UPDATE: fix my mistake for I/O Sched
-UPDATE: USB drivers for 2.3.4
-ADD: Fast charging while connected via USB
-UPDATE: HTC G-Sensor drivers
-Other stuff...
[U][B]2.6.35.14::demonspeed-INSANITY v1:: BETA01 (8.12.2011)[/B][/U]
-Initial release
*WARNING!* PLEASE READ INSTRUCTIONS CAREFULLY! IF YOU DO NOT UNDERSTAND WHAT YOU ARE READING, PLEASE ASK ANY QUESTIONS BEFORE FLASHING!
[DOWNLOAD HERE] 2.6.35.14 ::demonspeed v7:: (10.25.2011)
md5: 60b65131bd3dd7d62899e555dbefb8f5
INFOBFS (Brain **** Scheduler):
BFS: The objective of BFS, compared to other schedulers, was to provide a scheduler with a simpler algorithm, that did not require adjustment of heuristics or tuning parameters to tailor performance to a specific type of computation workload. The BFS author asserted that these tunable parameters were difficult for the average user to understand, especially in terms of interactions of multiple parameters with each other, and claimed that the use of such tuning parameters could often result in improved performance in a specific targeted type of computation, at the cost of worse performance in the general case.[4] BFS has been reported to improve responsiveness on light-NUMA (non-uniform memory access) Linux mobile devices and desktop computers with fewer than 16 cores.
Information Source: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler & http://ck.kolivas.org/patches/bfs/bfs-faq.txt
Swap:
Swap: Swap is a way to extend your physical memory. The OS moves the less accessed memory pages to slower, and cheaper storage medium. This frees up RAM for things that require the speed.
Governors:
demonspeed! Governor: this governor is rather similar to the 'ondemand' governor both in its source code and its purpose, the difference is its optimisation for better suitability in a battery powered environment. The frequency is gracefully increased and decreased rather than jumping to 100% when speed is required. Based off a lag free concept, with screen off profiles built in. demonspeed has not been tested against battery life performance, but rather for speed and user interaction.
[*]SuperBad Governor: A "superbad" super smooth rendition of a highly optimized "smartass" governor! Low latency and more responive to the user.
[*]SCARY Governor (@Scaryghoul): Scary - A new governor Scaryghoul wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
I/O Schedulers:
V(R) I/O Scheduler: V(R) is similar to, and based on, Linux's deadline I/O scheduler. It implements request deadlines which try to limit starvation, but provide no hard guarantee of request latency. It also merges and batches requests in a similar manner, but unlike deadline, read and write requests are issued together. This means there is no preference to reads over writes. Thus, higher throughput can be achieved at the cost of interactive performance. Secondly, V(R) could be used for situations where maximal throughput it the primary concern, such as batch processing systems, where per-request latency is not important. By scheduling read and write requests together and setting sufficiently high deadlines, V(R) can theoretically produce a better schedule than deadline, AS or CFQ.
RCU SubSystem:
RCU Concept: The basic idea behind RCU (read-copy update) is to split destructive operations into two parts, one that prevents anyone from seeing the data item being destroyed, and one that actually carries out the destruction. A "grace period" must elapse between the two parts, and this grace period must be long enough that any readers accessing the item being deleted have since dropped their references. For example, an RCU-protected deletion from a linked list would first remove the item from the list, wait for a grace period to elapse, then free the element. See the listRCU.txt file for more information on using RCU with linked lists.
Click to expand...
Click to collapse
Tiny Preempt RCU: This implements a small-memory-footprint uniprocessor-only implementation of preemptible RCU. This implementation uses but a single blocked-tasks list rather than the combinatorial number used per leaf rcu_node by TREE_PREEMPT_RCU, which reduces memory consumption and greatly simplifies processing. This version also takes advantage of uniprocessor execution to accelerate grace periods in the case where there are no readers. The general design is otherwise broadly similar to that of TREE_PREEMPT_RCU.
maybe????????
Nice 1 Derek,almost tempted to flash sense just to check it... there all gonna be blown away from the speeds of this.
Sent from my HTC Glacier using XDA Premium App
Aw hell yeah bro!!! Been waiting to try ur new kernel..dling now!! Thanks my man
Sent from my HTC Glacier using XDA Premium App
d12unk13astard said:
Nice 1 Derek,almost tempted to flash sense just to check it... there all gonna be blown away from the speeds of this.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah speeds are good but nothing compared to cm7 or miui.. I was testing the kernel on VU for a few hours and I forgot how much different sense really is.. The high quad score I got was 3500, I hope that is on par for a sense rom.. The responsiveness is there, just hope battery life is good?? I basically ported all the stuff from my. Other kernel, so should be good.. Going to need feedback on this one cause I don't really use sense, not my cup of tea... So let me know all you sense users and abusers
Sent from my HTC Glacier
thederekjay said:
Yeah speeds are good but nothing compared to cm7 or miui.. I was testing the kernel on VU for a few hours and I forgot how much different sense really is.. The high quad score I got was 3500, I hope that is on par for a sense rom.. The responsiveness is there, just hope battery life is good?? I basically ported all the stuff from my. Other kernel, so should be good.. Going to need feedback on this one cause I don't really use sense, not my cup of tea... So let me know all you sense users and abusers
Sent from my HTC Glacier
Click to expand...
Click to collapse
Will do bro
Sent from my HTC Glacier using XDA Premium App
Flashed...expecting great things...
Sent from my HTC Glacier using XDA App
Awesome a new kernel. Will try it out soon.
Was JUST about to ask you about this on G+ last night, if you would ever do a Sense Kernel, I wake up this morning, and BAM! Here this is... can't WAIT to give it a go!!
Does this work for your miui rom?
Sent from my HTC Glacier using XDA App
joemoss said:
Does this work for your miui rom?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No he has an Aosp kernel that works with miui
which is here http://forum.xda-developers.com/showthread.php?t=1113554
Ok, so definitely noticing an improvement in battery life, and everything is running smooth. Just a couple questions : 1) will the undervolt scripts from ur aosp kernel work with this one? 2) what's the low down on the superbad gov?..oh yeah, I don't get anywhere near 3500 on quadrant, how'd u do that? All in all, an excellent kernel bro..much thanks!!
Sent from my HTC Glacier using XDA Premium App
Oh yeah..TDJ, any relation to MDJ? Mighty odd coincidence 2 kernel devs are so closely named...lol
Sent from my HTC Glacier using XDA Premium App
joemoss said:
Does this work for your miui rom?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
My miui rom is always onestep ahead of my kernel thread.. i am dropping a new v6 kernel today with miui
marseillesw said:
Ok, so definitely noticing an improvement in battery life, and everything is running smooth. Just a couple questions : 1) will the undervolt scripts from ur aosp kernel work with this one? 2) what's the low down on the superbad gov?..oh yeah, I don't get anywhere near 3500 on quadrant, how'd u do that? All in all, an excellent kernel bro..much thanks!!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
no.. i have different frequency table now, those scripts will not support it.. if u r brave enough, download an app from the market called "incredicontrol" you can manually adjust each frequency voltage or do in increments of +/-25mv
marseillesw said:
Oh yeah..TDJ, any relation to MDJ? Mighty odd coincidence 2 kernel devs are so closely named...lol
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
No.. he is a great kernel dev tho..
thederekjay said:
My miui rom is always onestep ahead of my kernel thread.. i am dropping a new v6 kernel today with miui
no.. i have different frequency table now, those scripts will not support it.. if u r brave enough, download an app from the market called "incredicontrol" you can manually adjust each frequency voltage or do in increments of +/-25mv
No.. he is a great kernel dev tho..
Click to expand...
Click to collapse
Oh I'm brave enough..will try it out, thanks...and the superbad gov?
Sent from my HTC Glacier using XDA Premium App
marseillesw said:
Oh I'm brave enough..will try it out, thanks...and the superbad gov?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Superbad is badass! Use it!
vqt said:
Superbad is badass! Use it!
Click to expand...
Click to collapse
Ok will do..and damn, that incredicontrol app is the ****!!
Sent from my HTC Glacier using XDA Premium App
marseillesw said:
Ok will do..and damn, that incredicontrol app is the ****!!
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Yeah, I saw that post so I downloaded it. Gonna mess with the voltages a little to see how low it can go.
vqt said:
Yeah, I saw that post so I downloaded it. Gonna mess with the voltages a little to see how low it can go.
Click to expand...
Click to collapse
Yeah thats what I'm doing, so far I've dropped it a 100 and still running stable
Sent from my HTC Glacier using XDA Premium App
Updated to V0.10
Code:
[B][U]v0.10[/U][/B]
- uppatched to 2.6.35.14
- reverted my unreleased changes of the disabling of samsung debugging, it breaks lo power mode and causes SOD's
- Misc config tweaks
- Misc compiler tweaks
[B][U]v0.08[/U][/B]
- Up patched to 2.6.35.13 source
- merged some changed with Da_G's skyrocket source to fix cpu1 hot-plugging
this shiould solve issues of users having min clock stuck at 384mhz and/or max
stuck.
- fixed vdd_tables, system tuner will be supporting my kernel in up coming releases for this
system tuner, should no longer cause issues. as the hotplug fix solved this
[B][U]v0.06[/U][/B]
- Found tome Carrier IQ **** in tty consoles, removed it
sneaky sneaky...
- patched for call recording <--- DERP apparently it works with out my patch LOL
[B][U]v0.05.6[/U][/B]
- redid source tree from scratch
- Switched on OTG config options again (had them shut off)
- Battery issues resolved
- minor tweaks to autogrouping
- set kernel HZ to 300 for a smoother more responsive feel
- minor tweaks to lag free and smartass
- undervolts have been tested stable by many users and are in this release
[B]- PLEASE UNINSTALL SYSTEM TUNER AND CLEAR DALVIK CACHE THIS RELEASE[/B]
[B][U]v0.05.2[/U][/B]
- loosened up lag free so its not so twitchy at low freqs and ramping up and down constantly
- undervolted all freqs a fair bit
- added smartassv2 back in *Please TEST, i think i have solved the hang at max freq on wake*
- probably forgetting something else i messed with
[B][U]v0.05[/U][/B]
- sourced a multiprossesor service that actually wasnt ****ed and added to kernel
- turned on multi prossesor service and set it to shut off the second core on screen off
or when not needed, and only turn back on when needed
- Patched in BLN *thanks to romanbb*
- Patched services.jar to allow bln to notify you for most notifications from apps now
eg: gtalk, mms, sms app and ect..
- spiffy new boot logo ;)
[B][U]v0.04.1[/U][/B]
- removed smartassv2, its useless in its semi-working state, causing battery drain. I will figure out what its up to.
[B][U]v0.04[/U][/B]
- Lowered stock voltages a bit to get some better battery
- Fixed (i think) smartassv2 ramping up to max clock and then neglecting to ramp back down on wake from sleep
- Recommend using lagfree :)
[B][U]v0.03.2[/U][/B]
- fixed scheduler settings for new min freq, causing me SOD's on screen wake with notification
[B][U]v0.03.1[/U][/B]
- disabled 192MHz in the clock table so users cannot select it and cause a sleep of death situation.
- Default min freq now 384MHz
[B][U]v0.03[/U][/B]
- added in BFQ scheduler if users choose to use it you can use system tuner or other favored apps to change from CFS
- Added SmartassV2 and Iterative schedulers
- Tweaked SmartassV2 for our device
- Added ability to change voltage on the cpus with vdd_tables
[B][U]
v0.02:[/U][/B]
- 1.8ghz lag fixed ;)
- Autogrouping of scheduler added
- lagfree cpu scheduler added, with fully working sysfs interface to edit settings not set by default but recommended! its TITS!
- optimized build flags
- removed sysfs for vdd tables, we have not got it working yet. no worries you shouldn't need it yet ;)
- kernel compression changed for much faster boot times
[U][B]v0.01[/B][/U]
CK3+ Patch Set (Thanks to fellow Team Synergy member Ziggy471 for backporting)
OC 1.8 (Thanks to Romanbb's source tree)
Global UV Tables (Thanks to Romanbb's source tree)
All Debug shut off except samsung debugging (needed)
LZMA compressed
Carrier branded boot splash removed
init.d support
Voltage Control
You can control it via shell/init.d scripts as follows
To over volt ALL frequencies by 10000 uv:
Code:
echo "+10000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_table/vdd_levels
To under volt ALL frequencies by 10000 uv:
Code:
echo "-10000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_table/vdd_levels
To set a specific frequency (ie 1.8 GHz) with a specific voltage (ie 1.25 volts) ]
Code:
echo "1836000 1250000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Use SetCPU as a gui or sysfs to control CPU freq
DOWNLOAD
CWM FLashable zip:
V0.10
Here
Call Recording app by skvalex
http://dl.dropbox.com/u/44644505/CallRecorder_v.1.0.27_alpha_build05.apk
The app is offered on XDA for free but you can promote his work by Buying it in the MARKET
Trial of full version ( has more features )
http://forum.xda-developers.com/showpost.php?p=19345181&postcount=750
SOURCE
V0.10
http://www.androidfilehost.com/.mrx/
Whoa thats a first, Im first thanks for your work and welcome.
haha thanks
Question: Does this matter that its for the Telus T989D? Will this work for both phone versions? Not a noob, but a noob question sorry. Confused a bit.
Sooo, this is exactly the same as jugs? Just compiled by you?
Sent from my SGH-T989 using Tapatalk
jmercil said:
Question: Does this matter that its for the Telus T989D? Will this work for both phone versions? Not a noob, but a noob question sorry. Confused a bit.
Click to expand...
Click to collapse
should work on tmobile or telus
mikeyinid said:
Sooo, this is exactly the same as jugs? Just compiled by you?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
no, its based off a compleetly different source tree (as the verry first sentense in my post says), i have stripped all debugging possible, its using ck3+ patch sets not bfs 404 and my stock voltages and clock tables differ.
its also a few mb smaller then juggs and has all boot animations stripped from the ramfs
what did you set stock clock to? i'll be the guinea pig and try it out for tmobile user
-Mr. X- said:
should work on tmobile or telus
no, its based off a compleetly different source tree, i have stripped all debugging possible, its using ck3+ patch sets not bfs 404 and my stock voltages and clock tables differ.
its also a few mb smaller then juggs and has all boot animations stripped from the ramfs
Click to expand...
Click to collapse
Thanks for the response. You answered alot more than just my questions I'm sure. I thought for v0.2 roman used the same source. Idk
Is this uv'd as much as jugs v0.1? My phone runs like a champ at 1.8 on that and battery is excellent so that is the voltage I'd like to stick with if possible
Sent from my SGH-T989 using Tapatalk
G1_enthusiast said:
what did you set stock clock to? i'll be the guinea pig and try it out for tmobile user
Click to expand...
Click to collapse
the stock clock is 1.5 like factory.
mikeyinid said:
Thanks for the response. You answered alot more than just my questions I'm sure. I thought for v0.2 roman used the same source. Idk
Is this uv'd as much as jugs v0.1? My phone runs like a champ at 1.8 on that and battery is excellent so that is the voltage I'd like to stick with if possible
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
romanbb uses the drivers only from the T989D source i use the whole tree as it contains less debug code.
-Mr. X- said:
should work on tmobile or telus
no, its based off a compleetly different source tree (as the verry first sentense in my post says), i have stripped all debugging possible, its using ck3+ patch sets not bfs 404 and my stock voltages and clock tables differ.
its also a few mb smaller then juggs and has all boot animations stripped from the ramfs
Click to expand...
Click to collapse
Thanks for the reply!
-Mr. X- said:
the stock clock is 1.5 like factory.
romanbb uses the drivers only from the T989D source i use the whole tree as it contains less debug code.
Click to expand...
Click to collapse
Actually I merged all the changes
Sent from my SGH-T989 using Tapatalk
Romanbb said:
Actually I merged all the changes
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
That's what I thought
Thanks for the new option Mr. X
Sent from my SGH-T989 using Tapatalk
kind of sluggish...
Romanbb said:
Actually I merged all the changes
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ah didn't know
Thanks for the looksee at your source tree btw
mikeyinid said:
That's what I thought
Thanks for the new option Mr. X
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
No probs, just fiigured it post whhat i personally make and run
G1_enthusiast said:
kind of sluggish...
Click to expand...
Click to collapse
Can't say i'm having this, i've been running these builds all day. aside from adding more changed and testing i didn't need to reflash because of performance issues.
G1_enthusiast said:
kind of sluggish...
Click to expand...
Click to collapse
Are you using ondemand gov? There's something not right about ondemand in this source. Gonna need to be re-worked.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
Are you using ondemand gov? There's something not right about ondemand in this source. Gonna need to be re-worked.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Ive been using on-demand exclusively @ 1.7GHz and have had zero issues. Although i don't put any faith in quadrant scores i was getting 4500+
I'm going to be working with Ziggy471 on lagfree and smartass v2 govs soon and see if i can get them to cooperate better with dual core setups.
-Mr. X- said:
Ive been using on-demand exclusively @ 1.7GHz and have had zero issues. Although i don't put any faith in quadrant scores i was getting 4500+
I'm going to be working with Ziggy471 on lagfree and smartass v2 govs soon and see if i can get them to cooperate better with dual core setups.
Click to expand...
Click to collapse
I get 3400 Max and some lag using ondemand with jugs. At 1.8. So Idk if its just my phone but ondemand isn't playing nice.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
I get 3400 Max and some lag using ondemand with jugs. At 1.8. So Idk if its just my phone but ondemand isn't playing nice.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
its the clock rate, 1.8 kicks the **** out of my device too so i stick with 1.7
i tried increasing the vdd but it didn't help much, if at all and i was not satisfied with wasting the voltage for 100mhz. with 1.8 2d accel really suffers too in quad i experienced.
-Mr. X- said:
its the clock rate, 1.8 kicks the **** out of my device too so i stick with 1.7
i tried increasing the vdd but it didn't help much, if at all and i was not satisfied with wasting the voltage for 100mhz. with 1.8 2d accel really suffers too in quad i experienced.
Click to expand...
Click to collapse
OK. That makes sense. Ill clock it down to 1.7 and see if that makes a difference. Thanks for the feedback
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
OK. That makes sense. Ill clock it down to 1.7 and see if that makes a difference. Thanks for the feedback
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
no prob
10 char
hello folks,i present before u a custom kernel ,nothing much atm(testing time),but u can test it out.
This was compiled from AT&T source,but should work on Roger's devices.
Test it out-Flash via odin.
Download(v1 beta)- http://www.mediafire.com/?x81icy317yy02iv
DownloadV2(1.35 Ghz)- http://www.mediafire.com/?bhaklnqyuo1ax6p
kernel Source - https://github.com/sakindia123/Cranium_I927
I will test this now
Sorry if i did not make it yesterday. I am testing this one now and so far, working great.
I will be on school in next hour, if you'd upload a CWMR version, I can test both CWM and your kernel at the same time
EDIT: Booted up and working fine
Linux Kernel 2.3.36.3
PREEMPT Mon Jan 23 16:07:38 IST 2012
woot! so it worked
now compiling another kernel with some tweaks.Comin' up soon
sakindia123 said:
woot! so it worked
now compiling another kernel with some tweaks.Comin' up soon
Click to expand...
Click to collapse
yeah and that is great!
I will be on school in next hour, if you'd upload a CWMR version, I can test both CWM and your kernel at the same time
I don't have access to a computer with Odin during school hours but I will assure you that I will continue to be a guinea pig for this one.
updated with v1 beta....
@gabby-sorry dude.Uploaded the ODIN one
sakindia123 said:
updated with v1 beta....
@gabby-sorry dude.Uploaded the ODIN one
Click to expand...
Click to collapse
No worries.....that will be tested, odin or non-odin
EDIT: version 1 beta booted on my glide. New sio and vr i/o scheduler, removed some governors (ondemand, interactive, performance available). Everything is working and this is my daily driver for school this morning.... cheers!
gabby131 said:
No worries.....that will be tested, odin or non-odin
EDIT: version 1 beta booted on my glide. New sio and vr i/o scheduler, removed some governors (ondemand, interactive, performance available). Everything is working and this is my daily driver for school this morning.... cheers!
Click to expand...
Click to collapse
ooh.Ran any benchmarks yet?
Will soon release an overclockable version (upto 1.7 Ghz)
sakindia123 said:
ooh.Ran any benchmarks yet?
Will soon release an overclockable version (upto 1.7 Ghz)
Click to expand...
Click to collapse
Not yet....but I see that haptic feed back is not that strong or not as intensified as normal but not a big deal.
Vibration is also weak, it's on the state that you cannot feel it if it's in your pocket.
1.7ghz is mind blowing! there's UV too right?
EDIT: Benchmarks that I initiate.
Quadrant: 3300 (sio, interactive, 216mhz ~ 1000mhz)
Linpack: 34.815 MFLOPS (sio, interactive, 216mhz ~ 1000mhz)
Thanks for the quick work! Working well so far.
Sent from my HTC Desire HD using XDA App
any difference in benchmarks?
btw,Samsung had gone crazy and set performance as default governor
and yes,there will be uv,and phone will boot at 1 ghz
sakindia123 said:
any difference in benchmarks?
Click to expand...
Click to collapse
big difference in my observation on Quadrant (before hackzzzz ) almost no change in Linpack
sakindia123 said:
btw,Samsung had gone crazy and set performance as default governor
Click to expand...
Click to collapse
WHAT? is that on the leaked FW??? They are planning to blow up every Captivate Glide
sakindia123 said:
and yes,there will be uv,and phone will boot at 1 ghz
Click to expand...
Click to collapse
AWesOme!!!!! looking forward to the OC version
Oh BTW, i am sorry if i repeat myself, but the v1 beta has low vibration intensity on haptic feedback and notifications.
gabby131 said:
big difference in my observation on Quadrant (before hackzzzz ) almost no change in Linpack
WHAT? is that on the leaked FW??? They are planning to blow up every Captivate Glide
AWesOme!!!!! looking forward to the OC version
Oh BTW, i am sorry if i repeat myself, but the v1 beta has low vibration intensity on haptic feedback and notifications.
Click to expand...
Click to collapse
check ur settings.......i didn't mess with drivers..yet
i will first go upto 1.3 Ghz,then 1.7
sakindia123 said:
check ur settings.......i didn't mess with drivers..yet
i will first go upto 1.3 Ghz,then 1.7
Click to expand...
Click to collapse
my setup under Settings > Sound > Vibration Intensity are all maxed out.
Rebooting does not solve it. I will try reflashing the kernel. Thanks
EDIT: apologies for my ignorance, I can say my statement is a false alarm. Wiped Dalvik and cache partition before and after reflash of v1 beta and vibration is back to normal
updated with overclocked version.Plus some more changes.Too lazy to write changelogs!
sakindia123 said:
updated with overclocked version.Plus some more changes.Too lazy to write changelogs!
Click to expand...
Click to collapse
nice....but i think i am dreaming, the higher the frequency the lower the voltage? hooh haah!
EDIT: screw that, it's a voltage control app bug! >_< using cpu master atm
EDIT 2: Overclocked to 1.3ghz using CPU Master! UV of -100mV in each step > 1000mhz and so freakin' fastastic! I can't believe how low voltage Tegra chips are
can u post some benchamark results?antutu is more reliable imho
sakindia123 said:
can u post some benchamark results?antutu is more reliable imho
Click to expand...
Click to collapse
y u can read my minds? doing that atm.....
EDIT: They say "no screenies, or it did not happen!"
Voltages
benchmark (antutu)
Do you think you can make a version that can be flashed via CWM? Thanks for your work.
Hello everyone i know there are few threads about battery/gaming so i tought to make a thread with a review about battery life + gaming performance and add guides along with it.
Ok 1st i'd like to say i've pretty much flashed every single rom ,kernel, battery saving apps, performance boost apps, mods etc that are currently avilable so trust me i know what i'm writing here.
THREAD NAVIGATION:
Post 1 contains: Undervolting guide & everything related to undervolting CPU & GPU, EMC Overclocking, Rom setup guide, kernel setup (gaming / battery ), kernel settings list of updates
Post 2 contains: Rom & kernel battery life reviews + benchamrks , Performance may cry setup added (battery life settings)
Post 3 contains: Additional info about kernels / governors and what they do , schedulers and what they do & additional scrips.
FAQ Link for rookies and EVERY other question / guide about your HTC One X - Thx to Geko95 = HERE
Wakelocks guide for those with bad battery life - Thx to Goku80 = HERE
=========================================================================
First of all i'd like to give credits and massive thank to these guys who made all this possible:
- Hamdir - for all his guides and contribution for One X , he is one of the main reasons why we have smooth gaming !
- Xmister - kernels ( xm106 )
- Maxwen - the battery saving governor - Smartmax Governor
- Mwilky and his team for Renovate rom
- Patrics83 and his team for RomCleaner tool
- RichmondUK and his venom team for ViperX Rom
- n3ocort3x Kernels
- TripNdroid Kernels
---Excuse me if i've forgot someone.
----------------------------------------------------------------------------------------------------------------
Thread Updates:
FInally cleaned the whole damn thread , still some left overs
PMC v8 interactive/battery setups added @ post 2. UPDATED 15.5.2013 ///bottom of the post 2
Added New SetCPU v2 profiles Read post 2 at the bottom UPDATED 15.5.2013 ///bottom of the post 2
Added AOSP/AOKP/CM SetCPU , profiles Read post 2 at the bottom UPDATED 2.4.2013 ///bottom of the post 2
Added NEW SetCPU , profiles Read post 2 for changelog ( everything fixed ) UPDATED 25.3.2013 ///bottom of the post 2
Added SetCPU GUIDE and my Save with SetCPU Profiles BALANCE Version this is only for those who have SMARTMAX & PMC GOVERNORS in their kernel UPDATED 25.3.2013 ///bottom of the post 2
Added EMC OC Guide, this is only for those who use XM kernel 235# and above UPDATED 12.3.2013 /// post 1
Added PMC v5 this is only for those who use XM kernel 226# and above (PMC is now the new governor at XM kernel read post 2 for more info ) UPDATED 10.3.2013 /// post 2
Added *Performance may cry setup v2* (battery life setup)- UPDATED 3.3.2013 /// post 2
Added info about schedulers and what they do - UPDATED 22.2.2013 /// post 3
Added info about governors and what they do - UPDATED 26.2.2013 /// post 3
Kernel updates:
XM kernel beta version(s) :
#304
Disable JRCU, according to maxwen it caused lockups.
#303 cpu clock changes reverted.
Switching governors will no longer update calibration control.
Touch-screen updates(S2W,DT2W) from maxwen.
Variant info added back.
#303
Included maxwen's double-tap to wake (needs sysfs enable), and inner CPU clock changes.
#302
Included maxwen's fixes for freq. locks and LP mode switch with OC.
#301
Default UV removed.
Xm-Kernel STABLE version(s) :
#106
#106v2
#106v3
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Kernel reviews @ Post 2
========================================================================================[/CENTER]
- If you'd like to donate to any of these ppl please do so because they're the ones who made this possible, i'm just making it simple and hopefully preventing questions from everywhere about battery/kernels/roms , which is the best etc etc. And remember the kernel is most responsable for your battery life. So the point is you can use any rom of your choice with this kernel as long as you do things right. And follow what i wrote down there.
As for me i'd be happy just with simple *thanks* button if this was helpful to you in any way.
------------------------------------------------------------------------------------------------------------------------------------------------
ROM, Kernel, Undervolting, underclocking, overclocking settings:
ROM Settings:
Roms should be cleaned with RomCleaner tool just i used my own scrip since i wanted to keep some apps and widget, after cleaning i had 114 system apps on my hox , Renovate rom comes with around 200 or so + the apps you'll install. (rom cleaner also improves the battery and rom speed a little) Other then that nothing else changed except i added tons of mods but thats up to you what you'll add. And the only setting you'll need to enable in Renovate rom is 2d rendering This improves alot scrolling times in apps especially the ones like *Advanced system care and Rom Toolbox lite*
Kernel settings:
Battery settings
the only thing you'll have to do manualy is switch the governor after flashing Xm kernel onto Smartmax And thats all you have to do to have great battery life, in my case i underclocked my CPU to 1200mhz with smartmax governor + RoW scheduler , if you want to keep it faster (but you don't really need any more speed with this governor) leave it as it is, or to make it even faster use Smartmax + deadline + sampling rate 30000 + touch poke freq 1500000 ] , you can make it even faster but trust me no need for that. Use this governor and it's settings as daily settings for light tasks and light usage of your phone.
Gaming settings:
For this you should be using interactive / gaming governor + deadline scheduler and that's all you need to do of course if you do underclock your CPU make sure you reset it back to 1500 after you change the governor , no need for apps that boost your phone, if you wanna make things even faster and governor more aggressive change this value in governor settings : go max speed load 45 this will increase speed ( remember this will make battery drain even faster ) , and if you wanna push max performance that your hox can deliver at current time change min frequency 1500 as well remeber THIS will make your hox battery drain fast as hell ! And sd card read ahead speed should be 4096 if is not set like this by default you can use system tuner and change it. For tuning governors and freqs you could use SetCPU easier and faster to do so.
Games that i used for testing are: NFSMW, MC4 , Shadown gun deadzone, Wildblood.
Each of this games were incredibly smooth and playable like never before.
Undervolting
Ok so as many of you heard undervolting should improve your battery life and it does by maybe 5% tops 10% if you're lucky.
But the main reason why i undervolt is so i keep my phone cooler when gaming you wont notice big difference in avarage daily use without gaming but with gaming you should notice the difference but again this mainly depends on your CPU variant, in my case i have variant 3 which means i can undervolt more then variant 2-1-0 , thats the only good thing about undervolting , of course i could overclock more then other variants but we don't need overclocking with this kernel and rom.
The difference and battery improvement you'll be able to see only this way really and none other this is how : without undervolting and lets say playing NFSMW my phone ON charger reaches around 55c TOPS ( which is overheating and you lose more battery then what your charger can recharge for you ) but with undervolting my phone is reaching TOPS 45C and avarage 40C ( this also depends on the room temperature and your hands body temperature ) The reason why i did tests on charger is because thats the fastest way to test overheating and undervolting and NO do NOT play heavy games while charging this is KILLING your battery and lowering it's life cycle ! it's like eating while sh1tting !!!
Now i can't tell you which values to use since like i said above none chip is the SAME nor the variant so you'll have to figure out this on your own but i can give you the ROUGH idea how-to.
Update - rough idea how to undervolt CPU properly:
ok i'll mark frequencies with colors:
Before we start remember this: Undervolting depends mostly on your ROM , Kernel , USAGE !
RED = Don't undervolt too much
BLUE = Undervolt normally as you do
BLACK =Don't undervolt or undervolt just a little this will depend on your variant and rom mostly
1500+ , 1400,1300,1200,1100,1000 e.g 1500mhz freq. has 1237mV by default if you're a gamer you can undervolt this one to lets say -50-100 (up to the variant) if you're not a gamer you can go even up to -125/150 , now this can depend also on which freq do you use the most in gaming lets say , if you're using quad lock e.g 1500 , -75 should be enough, === freqs under 1500 can be undervolted more since they wont be used, but if you don't use quad locking then you need to balance the undervolting between -50-100 (this depends on the game and which freq it uses the most)
860 , 760, 640 are the freqs in the *middle* those can be undervolted even more , up to -150 (default UV should be around -100 here) since they are barly used but you can use cpySpy to check which freqs your device uses the most and then use that info to balance your undervolting and find right freqs.
475,340,204,102,51 are the freqs more like *screen on standby freqs, mostly 340/51* or the LP core freqs, these should be undervolted MAX -50/75or not at all these freqs are used also for e.g. listening to music while screen off , if you undervolt too much you can experience laggs etc.
Important: Variant 3 can undervolt more then this but it *shouldn't* really up to you to decide
IMPORTANT: Those who use XM kernel USE TRICKSTER MOD APP ONLY !
First of all you can use guide what i made above for undervolting but since we have accurate undervolting now you SHOULD undervolt THIS way and this way only:
Variant 0 = you can use undervolting max up to -50 MAX ! or if you're doing step by step undervolting you might push some freqs -75
Variant 1/2: You can undervolt MAX up to -75 or at some steps -100 tops.
Variant 3: you can undervolt MAX -100/125 and on some freqs MAYBE -150 , but of course you need to do step by step.
Remember: this are the SAFE undervolting values for all 4 variants You can try undervolting more if you like but i wouldn't recommend it since i'm sure it will most likely cause issues for you.
Remember: The UV values i've used above are supposed to be *DEFAULT* uv you should use , but users with variant 0 MIGHT suffer and have to use lower values
Note: I guess 90% of ppl are lazy to mess with per freq undervolting and finding what works for them and what not since consumes alot of time, anyway you guys should be good with -50-75 variants 0, 1 ,2 , as for variant 3 you should be able to go up to -100-125 on all freqs.[/SIZE]
GPU - Undervolting - Safe values
[*]Ok so for GPU undervolting you need to be on XM #153 kernel and above and follow this steps:
Use some root explorer to enable GPU undervolting and navigate here:
sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage
Click to expand...
Click to collapse
, open it , the default value is
0 to enable GPU undervolting type 1
Click to expand...
Click to collapse
and SAVE make sure to enable *system as writable*
After you do that you need to download this app from playstore *Trickster MOD* This is the ONLY app whit which GPU undervolting works for now. After that install app and you'll see GPU freqs like this: For e.g. *520000, 484000* etc those are the GPU freqs and their voltage.
The safe values:
Variant 0 = -25MV on all freqs.
Variant 1/2 = -25/50 on all freqs.
Variant 3 = -50-100 on all freqs.
The 1st freq i wrote is 100% safe, the second is ASSUMED to be safe as well, but you wont know unless you try it :cyclops:
How to test are these values safe and wont freeze/reboot your phone.
Probably many of you know when you undervolt too much your phone eventually feezes and reboots this happens because phone can't give enough of voltage to the certain frequency that is in that time used mostly so it has no other way out but to freeze and reboot. and the way to test this is it *safe* is either to use *antutu bechmark app* , *epic citadel* or *stability test* Those 3 tend to push max performance very fast and easy out of your phone so if any app gonna show you is it safe it's these , tho sometimes but rarely your phone will run them both without reboots so i suggest you do each of them 2x just to be sure, and even if then sometimes very very rarely if your phone doesn't reboot the last way you could've find out is it gonna reboot is by playing NFSMW for 10mins.
----------------------------------------------------------------------------------------------------------------------------------
GPU Overclocking & underclocking - Safe freqs
For this to work use some root explorer and navigate here: sys/devices/system/cpu/cpu0/cpufreq/gpu_oc , open it there you'll see default GPU freqs like this: 520 520 520 520 484 400 304 267 247 those are the DEFAULT freqs on XM kernel and make sure to enable *system as writable* before you start doing anything. Those freqs are great balance for GAMING and BATTERY but if you're an ADVANCED USER you might wanna make those freqs EVEN HIGHER for better performance (not needed imo ) or LOWER for better battery life
- Maximum performance freqs that works for everyone: 560 560 560 560 560 484 400 304 247
- Freqs for battery life while keeping some poor performance (gaming speaking): 304 304 304 304 304 304 304 304 247
- Default freqs ( battery & gaming ): 520 520 520 520 484 400 304 267 247
Thx to Neo for this freqs.
-----------------------------------------------------------------------------------------------------------------------------------------
All kernel settings: S2W Configs: , DoubleTap2Wake Configs: , Activate fast charge: , Enable smartdimmer: , To get your variant: , 3D Tuning: , 2D Tuning: , EMC Tuning ( ram ): , Auto-BLN Control: , Backlight button brightness: , GPU Voltage control: , LP OC: , Audio Min. Freq.:
Thx to Xmister for this.
S2W Configs:
Turn off:
Code:
echo "0" > /sys/android_touch/sweep2wake
Click to expand...
Click to collapse
Or you can download "Sweep2Wake-Widget" from Google Play.
Button panel locks to s2w after this distance:
Code:
/sys/android_touch/s2w_register_threshold
Click to expand...
Click to collapse
Screen turns on/off after this distance:
Code:
/sys/android_touch/s2w_min_distance
Click to expand...
Click to collapse
Direction independent(1 - Yes, 0 - No):
Code:
/sys/android_touch/s2w_allow_stroke
Click to expand...
Click to collapse
DoubleTap2Wake Configs:
Turn on:
Code:
echo "1" > /sys/android_touch/s2w_allow_double_tap
Click to expand...
Click to collapse
Activate fast charge:Code:
echo '1' > /sys/devices/platform/htc_battery/fast_charge
Click to expand...
Click to collapse
Enable smartdimmer:Code:
echo "1" > /sys/devices/tegradc.0/smartdimmer/enable
Click to expand...
Click to collapse
To get your variant:Code:
cat /sys/kernel/debug/t3_variant
Click to expand...
Click to collapse
(Or see it in a root explorer)
cpu_process_id is your variant.
3D Tuning:If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Click to expand...
Click to collapse
If you want to set them at boot, use an init script. Here is one. Just copy to /system/etc/init.d and set the permissions to executable by everyone with a root explorer. (Thx to Byrana)
Here is a flashable script that will work on newer kernels too for everyone. It also enables fast_charge. (Thx again Byrana)
2D Tuning:If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '520 520 520 520 492 484 380 247' > /sys/devices/system/cpu/cpu0/cpufreq/two_d_oc
Click to expand...
Click to collapse
You should NOT OC this higher than 3D.
EMC Tuning:If you want to change clocks, you have to write the whole clock table again, from up to down. In case you want to reset to default, this is it:
Code:
echo '667 667 667 667 408 408 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
Click to expand...
Click to collapse
If you want to OC let's say to 800MHz:
Code:
echo '800 800 800 800 667 667 408 408' > /sys/devices/system/cpu/cpu0/cpufreq/emc_oc
Click to expand...
Click to collapse
Auto-BLN Control:Interface:
/sys/class/leds/button-backlight/auto_bln
Click to expand...
Click to collapse
Values:
0: BLN OFF/Green led ON
1: BLN ON/Green led ON
2: BLN ON/Green led OFF
Example:
Turn off Auto-BLN:
Code:
echo '0' > /sys/class/leds/button-backlight/auto_bln
Click to expand...
Click to collapse
The changes will apply from the next notification.
Backlight button brightness:Interface:
/sys/class/leds/button-backlight/button_brightness
Click to expand...
Click to collapse
Values:
0-255: 0 is off, 255 is the maximum possible.
Example:
Code:
echo '50' > /sys/class/leds/button-backlight/button_brightness
Click to expand...
Click to collapse
The changes will apply from the next backlight turn on.
GPU Voltage control:If you want to enable this you should write '1' to /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage.
In command line that is:
Code:
echo '1' > /sys/devices/system/cpu/cpu0/cpufreq/gpu_voltage
Click to expand...
Click to collapse
After that you need to restart your voltage control app (Trickster Mod).
Now you will see the GPU frequencies multipled by 1000 to separate them from the CPU frequencies. So you will see 520000MHz, etc.
Be advised that there are a really few HOX's that can handle more UV on Core, than the preset 50.
Also incrasing your Core voltage over 1300mV is NOT ADVISED AT ALL. Almost everything uses this voltage on your motherboard.
If you want to enable the values at boot, you need an init script that enables it, so later Trickster mod or anything can set them.
LP OC:Interface:
/sys/module/cpu_tegra/parameters/enable_lp_oc
Click to expand...
Click to collapse
Values:
0: LP OC OFF
1: LP OC to 620MHz
Example:
Turn on LP OC:
Code:
echo '1' > /sys/module/cpu_tegra/parameters/enable_lp_oc
Click to expand...
Click to collapse
Audio Min. Freq.:Interface:
/sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Click to expand...
Click to collapse
Example:
Change audio min. freq. to 204MHz:
Code:
echo 204000 > /sys/module/snd_soc_tlv320aic3008/parameters/audio_min_freq
Click to expand...
Click to collapse
Save settings:
If you want any of the above settings saved, you can use Ibas21 recovery package
Click to expand...
Click to collapse
=======================================================================
Remember you wont probably get same screen on time as i did , you could get even more then i did or less, it ALL DEPENDS on your USAGE/Screen brightness!
That should be all enjoy.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------The screenshots and my usage are in post 2, hope this helps , if not sorry for wasting your time if you read this , cheers and good luck to everyone
If you have any question please feel free to post them and i'll give my best to answer them.
Also as the kernel updates and rom updates go i'll try to update in here as well.
----------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And lastly i will not be held responsible for anything that may or may not happen to your device ! All you do you do at your own risk.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And of course please hit *thanks* button if this was helpful :highfive::good:
==================================================================================
Bechmarks - updated.
------------
------------
Viper X Rom 3.3.7 XM Kernel 139#[Beta]
Usage:
Somewhere between normal and heavy , battery life was great, not so much on the wifi this time, and all in all great kernel with one tiny bug, if you use autobrightness you'll see flickering , tho this got fixed in 147#. And i plugged the phone right before screen shots for maybe a minut to put pics on the pc and in the meantime i made those screenshots, you can see that in the usage. Brightness varied between low (15%) and maximum. The most used brightness used was 35%.
-----------------------------------------
-----------------------------------------
Black Pearl unofficial beta Rom 4.0.4 - XM Kernel 188#[Beta]
Usage:
- 1st of all , extreme undervolting and underclocking was done for this test.
- The rom and kernel were also flashed for the very 1st time.
--------
--------
================================================================================================
1st how PMC works:
Well simply i made it use as *ideal_freq* 340mhz , minimum freq is 51mhz , the freq you'll be using alot would be 340/475 , that is your main freq on PMC for boost to avoid huge laggs, another thing is it will try and use most of the time only 1 core unless that core is at 90% cpu load , and min cpu load is 50 to make sure you don't get frequent wakes of 2nd/3/4th cores.
Interactive PMC Version:
This version is 90% similar to PMC Battery setup except this version is much faster since it acts like INTERACTIVE Governor.
@ Those who don't have PMC Governor in their kernel until / if their kernel dev includes it use *Smartmax governor* for tunning and using my setup
Important ! : While setting your CPU/GPU values don't enable *Set on boot* unless the values are 100% safe for you and by ALL MEANS DO NOT USE MY CPU/GPU VALUES even if you're VARIANT 3 i wouldn't advise it , if you DO USE my values you will 99.9% end up in freeze or reboot !
GPU UV For max battery
2d GPU Underclocking: 304 304 304 304 267 267 267 200
3d GPU Underclocking: 247 247 247 247 247 200 200 200
As for GPU uV i'd suggest -50mv if you're not variant 3. Try first -25 then -50.
NOTE:
Don't even think about gaming with this setup , you'll notice laggs mainly at loading apps and speed of loading apps and mainly speed reduction overall in system , but not so much , the main slowdown is with loading apps and when multitasking you'll see some laggs as well, or for e.g. when playing music and then using volume up/down , that will lagg as well, if you wanna keep it *smoother* you can set *Ideal freq to 475000*
Performance may cry - setup v8a( XM Kernel 302# + ONLY or Kernels with latest Maxwens updates)
A This settings of PMC Governor should / will deliver you the performance 90% identical to Interactive governor with much much less battery drain ! , this settings can be / should be used for those who MULTITASK alot , this settings/governor should give you 95% lag free experience whatever you do except gaming ! [/I][/B]
PMC v8 INTERACTIVE SETUP for EVERYONE ( Xm kernel users don't need this since PMC governor is in the kernel by default with these values ):
awake_ideal_freq 475
boost_duration 0
boost_freq 760000
debug_mask 0
down_rate 60000
ignore_nice 1
input_boost_duration 90000
io_is_busy 1
max_cpu_load 75
min_cpu_load 40
ramp_down_step 200000
ramp_up_during_boost 1
ramp_up_step 300000
sampling_rate 20000
suspend_ideal_freq 340
Touch_poke_freq 620000 ( 640 if your kernel kept the old freq table )
up_rate 20000
Cpu freqs:
Min CPu freq : 51
[*]Max Cpu freq: 1100
[*]Scheduler: RoW
Multicore power saving : 2
GPU max frequency : 416
Undervolting: At your choice and how much your variant can support:
Suggested SAFE values for all 3 variants NO GAMING for gaming use +25 more then my values under, example : if variant 1 is -100 NON GAMING , for gaming use -75.
This goes for both INTERACTIVE and BATTERY PMC setups.
variant 0 : -75
[*]variant 1/2: - 100 ( use -75 if you experience reboot )
[*]variant 3: - 150 / -175 in my case.
PMC BATTERY SETUP v8 For everyone with TUNNABLE Smartmax/PMC governors:
awake_ideal_freq 204000
boost_duration 0
boost_freq 760000
debug_mask 0
down_rate 60000
ignore_nice 1
input_boost_duration 90000
io_is_busy 1
max_cpu_load 90
min_cpu_load 50
ramp_down_step 200000
ramp_up_during_boost 1
ramp_up_step 300000
sampling_rate 40000
suspend_ideal_freq 204000
Touch_poke_freq 620000 ( 640 if your kernel kept the old freq table )
up_rate 20000
Cpu freqs:
Min CPu freq : 51
[*]Max Cpu freq: 1000
[*]Scheduler: SiO
Multicore power saving : 2
GPU max frequency : 416
Undervolting SAME AS on interactive ( look above )
And heres what users reported with PMC V7 performance setup =)
fade2blak said:
XM 188v2 with your PMC v7 performance version gave me the best results ever. period. thank you :highfive:
Click to expand...
Click to collapse
Insecret said:
now v241 on Viper 3.4.0 with row and pmc gov, UC at 1200 and the rest like Shan89 sayed in previus page ... Unthinkable how much improves in performance and batt life <3 Xmister and Shan89
Click to expand...
Click to collapse
bienjie said:
U r superb dude! U are gifted! Damn u r sooo good in this....(^~^)/
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
kkarnaout said:
im using the the new kernel with viperx 3.4.0 and all pmc settings, phone is amazing FB app is working i didnt see any problem till now this is the best kernel i tried till now from all the passed weak!
All thanks go to Xmister and Shan89
Click to expand...
Click to collapse
-------------------------
---------------------------
===============================================================================================
How to use FULL PMC setup.
Simple:
1st: thing to do enable 2d GPU rendering in developers options.
2nd: lower your CPU max freq to 1000mhz ! Yes 1000 mhz ( you wont feel much of a difference in terms of fluidity except when loading apps )
3rd: Use RoW or Sio scheduler ( for more info about these schedulers look at my signature guide theres explanation of every scheduler we use )
4th: Undervolt your CPU - here are the SAFE FREQS for these variants v0 - 50 , v1/2 , -75 , v3 - 100/125 (this are safe you could do more on some freqs)
5th: This is for those who don't play GAMES Underclock the GPU freqs here are the freqs you should use:
2d UC = 304 304 304 304 267 267 200 200
3d UC = 267 267 267 267 200 200 200 200
6th: Those who game you SHOULDN"T play with GPU UC only CPU UC.
Important: Make sure you use Trickster MoD app from playstore when using XM kernel for tuning and another vital thing to do is set in trickster app Multicore Power saving to 2 This will try to use as long as it can 1/2 cores unless desperate need for 4 cores.
A tip how to speed up loading times of the apps:
Since we have boost at 500 mhz if you open some app , lets say for example *Trickster MoD* after clicking on it you can hold your finger on the screen and move it in any direction , that way your CPU wont be locked onto 51 MHZ freq it will be on either 620 / 640 mhz ( boost freq ) or at MAX freq you set for CPU ( 700 if you use full PMC setup )
Final words:
PMC will try to force your phone spend 90% of the time in LP (low power) cores which barely use any power , if you do use PMC full setup the only real battery drain you'll have is your SCREEN and when in desperate need for some boost it will use your highest CPU freq you set.
Note:
Don't complain about bad speed etc etc etc , this governor is made only and only for BATTERY LIFE with basic usage.
And of course if this governor is *too laggy/slow* you can always use original *Smartmax governor*
NEW - SetCPU profiles setup balance v2 = SENSE =:
SENSE SetCPU profiles v2
This profiles fixed every little issue that exited in 1st release , just make sure to re-read the guide , some things has changed.
Anyway to make some kind of *changelog* if i can even call it like that this is what has got fixed / added:
Gaming works perfect now
Added profile for 2d games
Added profile for safety ( over heating to prevent it 2 steps )
Added more apps into profiles
Changed freqs on some things for better performance/battery life
Some other stuff i can't remember right now lol
Click to expand...
Click to collapse
Q) What does this do ?
A) Makes your phone smarter , boosts it when needed and downscales CPU freqs when not needed , It changes Governor / scheduler / CPU Freqs / .
Improves Loading times alot vs old PMC setups. The default loading times speed varies between 1100 mhz and 1300 mhz now.
Example:
Sense launcher: is set to use 640 MAX Cpu freq with smartmax governor + SiO scheduler.
Messaging: email / sms / gmail / etc = It will switch governor to PMC v7 ( Interactive version ) Boost max CPU freq to 840 and use Deadline scheduler so it makes sure it's liquid smooth and rotation works perfect.
Gaming: When you hit some , in my case NFSMW , MC4 , RR3 it will change to interactive governor + Row Scheduler and use MAX Cpu FREQ 1300mhz.
HOW TO SETUP ( Important ! )
1st: download SetCPU ( google it if you can't buy it you should be able to find it for free)
2nd Set max CPU Freq to 1300 and min freq to 51
3rd: Go to trickster and do the following:
Trickster settings:
PMC Governor = Leave as it IS
Scheduler = SiO
Multicore power saving = 0
Gpu Max freq = 520
Smartmax Governor settings = Change the settings to PMC V7 BATTERY Settings ( This is important thing to do if you want the profiles to work )
Undervolting - UPDATED:
Variant 1/2 = freqs 51/1250 undervolt - 100 ( if is unstable for you use -75 ) Freqs 1300-1500 Undervolt - 50 ( if is unstable use -25 )
Variant 0 should use 25mv more compared to v1/2 and variant 3 can do additional -50 on freqs 51/1250 and 1300/1500 freqs -25 compared to variants 1/2.
And last thing to do is *Set on boot / enable* - Do this only if UNDERVOLTING doesn't cause any reboots for you , it shouldn't anyway.
4th: copy my SetCPU Profiles to your SDcard and open SetCPU App , load the profiles and Apply them , make sure to tick * Enable Profiles * Also on the *MAIN* settings for CPU / Governor / Scheduler tick *Set on boot* and finally @ *Governor* also tick *Set on boot & Set With profiles*
5th: Download greenify app from playstore:
Set greenify app at your likings but make sure you don't put Trickster and SetCPU Apps in there.
6th: Downlaod LagFix (Fxstreem) App from playstore as well. Use this app once a day or whenever you like it.
Note: This will work ONLY With XM kernel unless another kernel dev includes PMC Governor in their kernel.
Tips:
[*]New - for MAX Speed when not using apps listed in profiles set in trickster & SetCPU Max Freq 1300 ( For absolute max performance 1500 ) min 51 INTERACTIVE governor and DEADLINE Scheduler. What will this do: Well simply it'll use max freq 1300 / 1500 depends on your choice whenever you're using something that is not listed in the profiles E.G. when you hit *Settings* it'll use interactive + deadline , same goes for other things that are not listed in the profiles.
[*]If you do full reboot make sure to open SetCPU app so profiles start working after the reboot.
[*]For 2d games *temple run* Etc just add them into *2d gaming profile*
[*]Tip for heavy 3d games sucha are Mc4 NFSMW , RR3 etc etc , i've set on 1300 max CPU freq so we avoid heat etc , note that those games are on MAX DETAILS for me and i don't have laggs so you guys who use those games without those details you should be fine in fact you can change max freq from the profile onto 1200 if you like. If you play some other 3d heavy games just add them in *Gaming* profile.
[*]A Tip for gaming with low details: Change the max freq from my profiles to 1100/1000 , i played NFSMW on max details with some FPS Drops on 1000mhz freq.
[*]@Those who use more social apps then facebook , simply add those apps in my profile where is facebook. If you use another messaging apps simply add them to my messages profile. Do the same to the other apps that you use which are similar to the apps in my profiles.
Click to expand...
Click to collapse
@Those who don't game at all and want maximum battery life they can get , also this would be useful for those who game as well , just apply those 2 things after you done with gaming:
Go to trickster app and do the following:
Max Gpu speed = 416
Multicore power saving = 2
If you want even more battery life visit my signature theres everything else you need to know on the post 2.
IMPORTANT: I've set on every profile *Notification* just so you guys can see it does it work , for those who want to remove it simply do this:
SetCpu > Profiles > click on the profile > Next > Untick *Show a notification* and that's it , do the same for other profiles.
Click to expand...
Click to collapse
If by any chance you don't see notifications after first time applying my profiles make sure you enable *Set on boot * where ever i wrote above and reboot your phone. That should fix it.
If anyone experience any issues ETC please lemme know.
AOSP/AOKP/CM SetCPU profiles + PMC v7 Setup - NEEDS UPDATE DON"T USE THEM - Will add them in few days when i switch to AOSP.:
DOWNLOAD THE AOSP PROFILES HERE
Download these tools 1st:
SetCPU app
Trickster app
Greenify app
Trickster settings:
Choose smartmax governor and apply these values in governor control:
Boost_freq: 620
Ideal_freq: 340
max_cpu_load: 90
min_cpu_load: 50
touch_poke_freq 620
Click to expand...
Click to collapse
Apply the values
Scheduler:
Deadline
Click to expand...
Click to collapse
Cpu settings:
Max freq 1000
Min freq 51
Click to expand...
Click to collapse
After that change to PMC Governor and apply.
Next thing to do swipe to specific settings
Smartdimmer: ON
Multicore power saving 2
GPU Max freq: 416
Undervolt how much you can.
Click to expand...
Click to collapse
APPLY all these and SET ON BOOT
Next thing to do open SET-CPU app make sure it's showing same CPU freqs as on trickster and same governor and scheduler.
Set on boot
Go to PROFILES and load my AOSP profiles after that tick Enable profiles
Important:
This profiles will work ONLY on AOSP rom and ONLY on XMkernel since other kernels don't have PMC interactive governor.
After applying the proffiles go to LAUNCHER and if you don't USE NOVA remove NOVA from that profile and ADD your launcher that you use.
TIPS / IMPORTANT:
[*]After you apply the PROFILES and you don't use INVERTED BLACK FACEBOOK APP delete that from profile and add the facebook app you use.
Click to expand...
Click to collapse
As for your own apps just go to profiles and add those apps into profile you like.
Click to expand...
Click to collapse
Lastly Thx to Xmister for the great kernel and his devhost link for uploading the profiles.
Heres the screenshoots from ICJ 2.8.1 with PMC v7 battery/interactive SetCPU Profiles:
----------
--------
-------
==================================================================================================
Note:
You shouldn't really relay and trust benchmarks at least not in antutu and quadrant , the most reliable and most accurate benchmark we have is Epic citadel , almost every single time same results. and 52.6 is quiet high result for sense rom. Btw for those who care s3 scores average 44-45fps on epic and note 2 scores average 46-47fprs.
]]=====>>> Wakelocks guide thx to Goku80 <=====[[
This is for those who have bad battery life !
http://forum.xda-developers.com/showthread.php?p=38629490#post38629490
Guys who follow this guide and use it , Please leave us the feedback about your battery life and rom you used. It's gonna be easier for us to locate the best battery life RoM, Thx in advance ! Also rating the thread would be nice
And those who USE this guide but apparently *doesn't help them* please post a replay with what you did and what happened, your battery/undervolting , whatever that came out from this guide, theres a chance you didn't do something RIGHT so we can try and help out. THX !
ADDITIONAL INFO - UPDATE:
I tought it would be nice to add some info about schedulers , and governors so ppl better understand what they are and what they do
Update: added governor info.
Update: added info about MpDecision and Cpu Quiet per request..
---------------------------------------------------------------------------------------------------
Governors:
- OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.
OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.
This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.
- Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).
- Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.
Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.
However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.
Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.
- Suggestion : Use this governor (Interactive) for GAMING , it's the best when using Xm kernel for this purposes +deadline or Row scheduler.
- Smartmax
Long story short if you want crazy battery life USE this governor with either noop/sio/row governor, depending on what you want , read about schedulers under and chose what fits your needs.
- PMC ( Performance may cry )
ok so i made this governor based on Smartmax except it's heavily tweeked for better and maximum battery life you can get out of HOX.
- TouchDemand:
This governor pretty much do what the name says, boosts cpu freqs by touches, this one actually can be pretty great for battery life if you underclock the CPU imho and use max 2 cores, you can do that by doing this: edit touch_min_cores under governor tuneables and set 2
Anyway i still prefer *SmartMax* for battery life. But up to you to test and find out.
As for other governors like : Conservative and powersave , i wont be adding info about them since i doubt anyone ever uses them , all they do is take more space in the list
-----------------------------------------------------------------------------------------------------------------------------------------------------
Schedulers:
- Noop:
This scheduler assumes I/O performance optimization will be handled at some other layer of the I/O hierarchy , on the more simple way this scheduler is MOSTLY used for battery life since it's slow - it raises freqs slower then other schedulers.
- Deadline::
This scheduler attempt to guarantee a start service time for a request It does that by imposing a deadline on all I/O operations to prevent starvation of requests. It also maintains two deadline queues, in addition to the sorted queues (both read and write). Deadline queues are basically sorted by their deadline (the expiration time), while the sorted queues are sorted by the sector number. To make it more simple this scheduler raises freqs much faster then noop and keeps them longer active then noop which means more battery drain ( not by much anyway ) and faster I/O as well the gaming should be the best with this scheduler.
- SIO:: - ( my favorite )
This scheduler in simple words is basically this : It's a mix of noop and deadline schedulers , noop is more for battery while deadline is more for performance , and sio is perfect balance between them ^.^ to be more specific it's more like almost having noop+deadline activated at the same time.
- ROW::
ROW: stands for "READ Over WRITE* The ROW scheduler is in favor for user experience upon everything else (means it should make things stupidly smooth ),so that why ROW scheduler gives READ IO requests as much priority as possible. Usually it¡¯s a single thread or at most 2 simultaneous working threads for read & write. Favoring READ requests over WRITEs decreases the READ latency greatly. == Even more speed.
The main idea of the ROW scheduler is // == If there are READ requests in pipe - it WILL dispatch them but don't starve the WRITE requests too much.
Also this scheduler is much better optimised for our phones since in the smart phones we use flash memory and not hard drives.
Finally : Think of this scheduler as a mix OF deadline+ Performance governor put in scheduler while you can use another governor e.g. Smartmax. It's quiet fast scheduler and even good for daily usage without much of impact on the battery life.
Hope this prevents the question about schedulers / governors and which one to use
And a tip: Sio scheduler should be PERFECT with smartmax governor for battery life + speed , in fact it's the best scheduler if you guys want speedy performance while saving the battery life.
-------------------------------------------------------------------------------------------------------------------
MPdecision:
MORE INFO >
For us mpdecision is a cpu hotplug system, which replaced the default nvidia hotplug system. It was written by showp1984(Dennis Rassmann).
It's more configurable, better for battery life, and much much better for gaming.
Cpu quiet:
- Cpu quiet driver regulates the cores by them acting more syncronized. they scale up n down in a more uniform fashion. therefore it gets better battery life without losing performance. You can't manage each core like with morrifics. so the cpu quiet driver is doing all the regulating. So the cpu quiet driver basically replaced hotplugging as far as cpu core management goes.
- In simple words it should give better battery life.
Good thread mate!
I know people have been looking for a guide for ages.
Goku was gonna do one in fact, guess you beat him and me to it.
geko95gek said:
Good thread mate!
I know people have been looking for a guide for ages.
Goku was gonna do one in fact, guess you beat him and me to it.
Click to expand...
Click to collapse
Lol thx, i was actually waiting for you or him to make one, i guess i got tired of waiting and besides that i saw tons of questions in past few days about *which kernel , rom* are the best so i guess they have their answer now.
Oh and if you have anything to add that i might forgot or anyone else please feel free to do so.
Edit - I'll probably add new screenshots when i manage to waste this 9% i got left, this battery refuses to die, i feel like i have note in my hands lol.
Shan89 said:
Lol thx, i was actually waiting for you or him to make one, i guess i got tired of waiting and besides that i saw tons of questions in past few days about *which kernel , rom* are the best so i guess they have their answer now.
Oh and if you have anything to add that i might forgot or anyone else please feel free to do so.
Click to expand...
Click to collapse
I'll have a think, I've got a little battery guide of my own that I wanted to write.
I'll have to see if wilky will want to put it in the OP, if not then you can use it in this thread.
Also I'll talk to wilky and see if he wants to add a link to your thread when we next edit the OP.
geko95gek said:
I'll have a think, I've got a little battery guide of my own that I wanted to write.
I'll have to see if wilky will want to put it in the OP, if not then you can use it in this thread.
Also I'll talk to wilky and see if he wants to add a link to your thread when we next edit the OP.
Click to expand...
Click to collapse
Sure , i'd be honored :good:
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
What is maxwen governor? Where can i find it?
Sent from my HTC One X using xda app-developers app
jarein95 said:
What is maxwen governor? Where can i find it?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Its called Smartmax and its included in NCX and XM kernels.
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
geko95gek said:
Its called Smartmax and its included in NCX and XM kernels.
Click to expand...
Click to collapse
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app
jarein95 said:
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Maxwen is the nick of the guy who wrote it.
jarein95 said:
xD jajajaa is what I am using since yesterday jajajaa but i didnt recognised it with the name of maxwen!! Jajajajaa
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Lol, anyway looks like i'll have to edit OP so ppl know the name of the governor
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
If you use the repacked xm I posted it's set to smartmax automatically
Sent from my HTC One X using xda premium
mwilky said:
If you use the repacked xm I posted it's set to smartmax automatically
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah i did use your repack cuz of original s2w Also cuz of Smartmax as default on boot. thx for that.
Btw OP updated with final battery results. Ppl i think we have the perfect match here about battery + gaming + speed. It's simply revolution of HoX. And all thx to everyone who developed for HoX sucha amazing stuff, and we must not forget things can get only BETTER for hox from now on not worse, so we might expect even better stats.
Just a small comment on smartmax
Setting boost_freq has actually not much of an effect
This is only used for the "external" boost interface of smartmax
This can be used e.g. from the android power module to boost
the cpu if required. But thats of course not implement in most roms
So only touch_poke_freq has an effect since this is use to boost
on input events from the touchscreen
maxwen said:
Just a small comment on smartmax
Setting boost_freq has actually not much of an effect
This is only used for the "external" boost interface of smartmax
This can be used e.g. from the android power module to boost
the cpu if required. But thats of course not implement in most roms
So only touch_poke_freq has an effect since this is use to boost
on input events from the touchscreen
Click to expand...
Click to collapse
Thx on the correct info.
Edit - Benchmarks updated.
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Hi. What app did u use to change governers? Any preferred?
Sent from my HTC One X using XDA Premium HD app
gilbertvpuen said:
Hi. What app did u use to change governers? Any preferred?
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Hello , for changing the governors and schedulers undercloking , overclocking and changing the governor values i use SetCpu you can find it on apkmania site, as for undervolting and further more tweeking i'm using System tuner , you can find that one on the playstore. Btw it's in the Op
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Shan89 said:
Hello , for changing the governors and schedulers undercloking , overclocking and changing the governor values i use SetCpu you can find it on apkmania site, as for undervolting and further more tweeking i'm using System tuner , you can find that one on the playstore. Btw it's in the Op
Click to expand...
Click to collapse
Hi shan,thanks. One last thing. I noticed you have changed your fonts, im also in renovate rom with xm106. I dont see any options for that. Can u guide me too a link? Cnt find it in themes/ add ons thread.
Sent from my HTC One X using XDA Premium HD app
Re: The ULTIMATE BATTERY LIFE+ GAMING PERFORMANCE setup/guide
Thnks shang, will try it in SkyDragon rom to see how it works, as Base 3.17 its better, hope to get better results,
Btw.. Kernel Devs makes our roms better.
Cheers
SkyDragon Team© No Kangy rom allowed.