Can we underclock with undervolt our CPU like Desire, Nexus,...?
lynx2k50 said:
Can we underclock with undervolt our CPU like Desire, Nexus,...?
Click to expand...
Click to collapse
You can underclock with SetCPU app. Never heard about undervolt so. Maybe you ment Underworld with Kate Beckinsale ?
yeah that wud be excellent.. i know it makes a huge difference on the wattage wasted on pc's.. dunno how much it'll help battery life with so many components on a phone.. n it'll be near impossible to fiddle with all the voltages
Hehe no i mean undervolt. One Nexus one and Desire there are allready kernel. The Kernel reduces the cpu voltage so we save battery.
lynx2k50 said:
Hehe no i mean undervolt. One Nexus one and Desire there are allready kernel. The Kernel reduces the cpu voltage so we save battery.
Click to expand...
Click to collapse
Change your CPUFREQ_MIN and change IDLE_TO_SLEEP timeout to a lesser value. Also set NO_SLEEP_LIMIT and FULL SLEEP (power down suspend), and there's no need to undervolt.
Battery lasts forever.
adwinp said:
Change your CPUFREQ_MIN and change IDLE_TO_SLEEP timeout to a lesser value. Also set NO_SLEEP_LIMIT and FULL SLEEP (power down suspend), and there's no need to undervolt.
Battery lasts forever.
Click to expand...
Click to collapse
Thnx for the quick reply.. ur fix wud be luvly only if i understood how to do that
red4 said:
Thnx for the quick reply.. ur fix wud be luvly only if i understood how to do that
Click to expand...
Click to collapse
Me too!
no need to go to the kernel source..
adding this line in a "init.d" script really help:
Code:
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
MaXo64 said:
no need to go to the kernel source..
adding this line in a "init.d" script really help:
Code:
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
Click to expand...
Click to collapse
Does that really work?? is it that easy to get the battery usage very low?
and does it still play music with this line added?
ybinnenweg said:
Does that really work?? is it that easy to get the battery usage very low?
and does it still play music with this line added?
Click to expand...
Click to collapse
i'm using it with both aHero and HeroDroid, and everything works perfectly even when Screen is off..
MaXo64 said:
i'm using it with both aHero and HeroDroid, and everything works perfectly even when Screen is off..
Click to expand...
Click to collapse
and what exactly does that line in the script do? doubt it's undervolt.
MaXo64 said:
i'm using it with both aHero and HeroDroid, and everything works perfectly even when Screen is off..
Click to expand...
Click to collapse
wow, well, then i'm going to ADB rightnow, and add that line!!
just use the ADB from the SDK right??
interesting! how do we do this? do we just go into adb shell and type that command?
Ya just open up an adb shell and paste that line
It'll create a file called powersave_bias with the value of "1" inside.
I'm testing it out today we'll see how it does.
VR 10 had mobile network always on so it killed my battery in 12 hours last night, normally it's around 50% after 12 hours, so we'll see if turning off always on and turning powersave on helps.
petsasj said:
and what exactly does that line in the script do? doubt it's undervolt.
Click to expand...
Click to collapse
it doesn't undervolt but it makes the CPU works much less when idle.
see this, page 26: http://kernel.org/pub/linux/kernel/people/lenb/acpi/doc/OLS2006-ondemand-presentation.pdf
ybinnenweg said:
wow, well, then i'm going to ADB rightnow, and add that line!!
just use the ADB from the SDK right??
Click to expand...
Click to collapse
you can use it temporary by executing this command in adb:
Code:
adb shell echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
but it's gone after reboot..
djdavis said:
interesting! how do we do this? do we just go into adb shell and type that command?
Click to expand...
Click to collapse
yup..
kool, so how would one make this permenant?
djdavis said:
kool, so how would one make this permenant?
Click to expand...
Click to collapse
i get a "the system cannot find the path specified" error in cmd, when typing
Code:
adb shell echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
correct command (thanks to kendon)
Code:
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
running a bogomips returned the exact same value in mhz as i've set for in setcpu (352mhz). so what does this do essentially? drop mhz? how does it lower workload?
so does this make it permanent?
petsasj said:
i get a "the system cannot find the path specified" error in cmd, when typing
Code:
adb shell echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
correct command (thanks to kendon)
Code:
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/ondemand/powersave_bias
running a bogomips returned the exact same value in mhz as i've set for in setcpu (352mhz). so what does this do essentially? drop mhz? how does it lower workload?
Click to expand...
Click to collapse
Are you sure that command from kendon is correct? From what I can tell, that should simply tell you what is in that file (thats what cat does).
djdavis said:
so does this make it permanent?
Click to expand...
Click to collapse
don't know, but my guess is no.
why would you want to make something permanent if you haven't tested it for a few days?
Related
Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Edit:
This script is released to public domain, so it can be freely used for derivative works without permission!
Good thinking!
Thanks for sharing.
do we flash this in clockwork?
bradputt said:
do we flash this in clockwork?
Click to expand...
Click to collapse
Nope, it's just a init script for the ROM devs...
but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx
Awesome work you do
+10
This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!
bartito said:
but is possible to applu in a rooted phone simply copying to /systen/etc or nope? needs setcpu or works without?
thx
Click to expand...
Click to collapse
You can push this script to /system/etc/init.d but it has some dependencies e.g. the interactive governor, perflock disabler when you want to underclock, ...
NeoPhyTe.x360 said:
Awesome work you do
+10
Click to expand...
Click to collapse
It was your idea, so same goes to you!
ivicask said:
This is supercool, we wont need to use SETCPU anymore, just flash this and enjoy super battery life, big thanks FloHimself!
Click to expand...
Click to collapse
That's the reason we are doing it this way: make the governor switching a bit more low level without SetCPU. But remember, this is not a update.zip and not flashable from recovery...
nice work. i really appreciate this. lets hope all the devs see this
FloHimself said:
Attached init script changes the CPU frequency governor based on the screen state:
Code:
screen on -> interactive governor
screen off -> powersave governor
Don't use this with SetCPU!
Thanks NeoPhyTe.x360 for the idea...
Click to expand...
Click to collapse
Useless... Interactive governor sets low speed when idle.
sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
You are right, the interactive governor sets the lowest speed when idle. But idle != screen off.
sbricout said:
Useless... Interactive governor sets low speed when idle.
Click to expand...
Click to collapse
Applications and services can still ramp up the CPU speed during the screen being off, so not useless at all. Switching to the powersave governor for when the screen is off, will stop it ramping up during this time.
I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling
sfjuocekr said:
I modified the script abit to include frequencies for min and max.
http://linux-box.nl/~sjoer/90screenstate_scaling
Click to expand...
Click to collapse
Nice, that`s something I`ve done later, too :
http://dl.dropbox.com/u/31174/android/90screenstate_scaling
Thought about extending it some more...
don't punch me, but... how can this be installed?
Kinda complicated, you`ll need a modified init.rc to run the scripts from /system/etc/init.d/ at startup, you have to push the governor modules and perflock_disabler module compiled for your kernel in /system/lib/modules/ the insmod scripts for the governors, perflock_disabler script and the script above to /system/etc/init.d/
FloHimself thank you very much for the scripts and the modules.
Is it me or is this script constantly looping with no breaks/sleeps?
I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?
sub0min0us said:
I've installed Neophytes' ArauxtSense 7.1 rom and he already added this on his rom. The question is, do I have to uninstall my SetCPU now? I have my referred settings on it and don't know how to disable it. I have unchecked the "Set on Boot" but everytime I boot my device, I can see that the SetCPU is still running on the background. Any advice? Any risks when having them both?
Click to expand...
Click to collapse
There shouldn't be any risks, but one of them will force its set freq, and the other one will be constantly changing it
Sent from my HTC Desire using XDA App
Thanks for clearing that out. I guess I'll have to uninstall it then not unless I install another rom. Thank you...
Hm If I use setcpu ,and I set it at 122-244 will I gain more battery?)(it will run slowly but still...)
SSJGohan3 said:
Hm If I use setcpu ,and I set it at 122-244 will I gain more battery?)(it will run slowly but still...)
Click to expand...
Click to collapse
Yes, it will make your battery last longer. I use "CPU tuner" (free) to set my processor to 246MHz all the time (using the "Extreme Save Battery" governor).
I also use "AutomateIt" (also free) to disable mobile data and disable sync when the screen turns off, and re-enable them when the screen comes on.
wil the set cpu slow down my desire hd?
real77055 said:
wil the set cpu slow down my desire hd?
Click to expand...
Click to collapse
if you set it too slow yes it will slow down your dhd.. if you like try to set it to powersave. it will get a bit slower but it will also save a lot of battery
122-244? Isn't that very laggy?
It will be much slower than any other phone.. Even ZTE Blade will go faster
Sent from my Desire HD using Tapatalk
wildwings said:
122-244? Isn't that very laggy?
Click to expand...
Click to collapse
you mean 122MHz min and 244MHz max?
when i tried that it turned off my phone .. i dont think that its a good idea because it's a pity to have such a powerful phone and set it to that low..!
your choise
patomo09 said:
you mean 122MHz min and 244MHz max?
Click to expand...
Click to collapse
yup, that's what OP stated
patomo09 said:
if you set it too slow yes it will slow down your dhd.. if you like try to set it to powersave. it will get a bit slower but it will also save a lot of battery
Click to expand...
Click to collapse
be careful and don´t go under 100 mhz because can be possible that your DHD don´t has strong enough to exit of the standby mode!
I use a modified CM7.1 and at 122-244 it works pretty smoth and fast....I could get used with it...and on quadrant i get around 600
First off i take no credit for the virtuous oc daemon itself, it was developed by rmk40.
And credit goes to -viperboy- for the idea, i used his rom and really liked the oc daemon and saw the difference it makes. Check his rom out here. It has a nice interface to control the oc daemon and other features of the rom.
You can get more info here
DON'T use any apps to adjust cpu with this ie., setcpu, cpumaster, etc.
Ok, here is the deal flash the zip file the script will run by itself the only adjustment you have to make is the virtuous oc settings. This should work with any rom and probably any device i just don't have any other devices to test it on.
Here is how:
Open root explorer (or whatever file manager you use) and navigate to /system/etc/virtuous_oc, you will see 6 files named:
sleep_governor
sleep_max_freq
sleep_min_freq
wake_governor
wake_max_freq
wake_min_freq
These are the files you edit to your liking, i only edited wake_max_freq to read 1863000 or 1.8ghz
The two governor file have different settings and they are:
conservative
userspace
powersave
ondemand
performance
Again edit to your liking i left them ondemand myself seems to work good. I don't really know what the settings do exactly when it comes to these but they seem pretty self explanatory.
To see if it's working all you need to do is open terminal emulator or adb shell and type one of the following:
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
It autostarts using init.d, so MAKE SURE your rom supports init.d, if it doesn't you can still use it but it has to be started manually by entering the following in terminal emulator:
Code:
/system/xbin/virtuous_oc
If you overclock MAKE SURE your kernel supports it, I'm not responsible for any damage incurred
In the future i want to make an app to control the settings but i am still learning that part.
Big thanks to rmk40 for this awesome daemon and -viperboy- the bad ass idea !!
EDIT:
A basic rundown of the oc daemon is it scales up your cpu when you screen is on and scales it down when it is off, so your cpu is not overclocked continuously. It does save on battery as long as you don't get crazy with the overclocking.
rugedraw said:
The frequencies are:
Underclock: 192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000 918000 972000 1026000 1080000 1134000 1188000 (stock)
Overclock: 1188000 (stock) 1296000 1404000 1512000 1620000 1782000 1836000 1944000 2052000
There may be some extra ones not listed here. From doing basic math, it seems you have to go up or down in increments of 54,000 when adjusting the CPU speeds. So if you want to UC higher than 192000 but lower than 384000, then you SHOULD be able to add 54,000 to 192000 and use that, or subtract 54,000 from 384000 and go that route.
Click to expand...
Click to collapse
Changelog:
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
I tested this for the My Touch 4G last night and it works great, installs in seconds. I'll help out watching the thread and answering questions for those whom need it if Smokin isn't around to answer them.
What does this exactly do for your phone?
Sent from my HTC Glacier using XDA Premium App
codey895 said:
What does this exactly do for your phone?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
This is an OC Daemon, its designed to control the processing speeds of your device. SetCPU does the same thing but this method is more stable and works without using any voltage. You can read some of the information listed in the links above.
whats the difference of the 2 zip files?
bstylz911 said:
whats the difference of the 2 zip files?
Click to expand...
Click to collapse
Changelog:
-Added Juwe11 ram optimization script
-Added speed up SD hack (Set at 3072) Details here
Click to expand...
Click to collapse
That's the information for the second ZIP file, the other one doesn't have that optimization.
so is it safe to say that i can use this on my MT4G running CM7 latest nightly?
I'm a little confused here. I got this up and running using the intstructions in the OP. But the frequencies don't match my kernels frequencies. Shouldn't they match?
Sent from my HTC Glacier using XDA App
estallings15 said:
I'm a little confused here. I got this up and running using the intstructions in the OP. But the frequencies don't match my kernels frequencies. Shouldn't they match?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
No, the kernel gives you a range of highest to lowest frequency range in which they are able to run. You tune the kernel to run at the frequency that you want it too so if you run the kernel at the highest frequency the phone will run fast but you will use the battery faster, if you tune the kernel to run slow the phone will run slower but your battery will last longer.
What your looking to do is adjust the kernel to the closest frequency to give you the best performance but low enough to continue to keep a long battery life.
Kernels run by using Governors, if you select "OnDemand" as your governor it will run what ever Highest frequency you set it for when ever your device is out of sleep mode, (Example: MAX 1836000 and Minimum 192000) when ever you put the device in sleep mode it will automatically run at the lowest setting. This conserves battery while you still use better performance when actually using the phone.
Hope this clears it up for you.
itzsmokey: so is it safe to say that i can use this on my MT4G running CM7 latest nightly?
Click to expand...
Click to collapse
Yes this will work for that ROM, it's designed to be flashed after the ROM is installed, there are ways to check if it is working for you in the "OP". I would take the time to look through the links provided in the OP as well.
Orical said:
No, the kernel gives you a range of highest to lowest frequency range in which they are able to run. You tune the kernel to run at the frequency that you want it too so if you run the kernel at the highest frequency the phone will run fast but you will use the battery faster, if you tune the kernel to run slow the phone will run slower but your battery will last longer.
What your looking to do is adjust the kernel to the closest frequency to give you the best performance but low enough to continue to keep a long battery life.
Kernels run by using Governors, if you select "OnDemand" as your governor it will run what ever Highest frequency you set it for when ever your device is out of sleep mode, (Example: MAX 1836000 and Minimum 192000) when ever you put the device in sleep mode it will automatically run at the lowest setting. This conserves battery while you still use better performance when actually using the phone.
Hope this clears it up for you.
Click to expand...
Click to collapse
Lol. Thank you, but that's not what I meant. My kernel uses different frequencies. It has a range of 122000 to 203000. The numbers don't directly match up to the numbers in the OP, even in multiples of 54,000. See what I mean?
Sent from my HTC Glacier using XDA App
That was my point, your using MIUIs kernel it looks like, yes the kernel says 2.03 for the Max and 122 for the min the frequency in the output says 1188000 for the Max, that's what the daemon was preset too you go in and edit the files yourself. I first tested this before it was released on MIUI and it worked fine, look through and you'll find info on how to change the frequencies
Sent from my HTC Glacier using XDA App
Orical said:
That was my point, your using MIUIs kernel it looks like, yes the kernel says 2.03 for the Max and 122 for the min the frequency in the output says 1188000 for the Max, that's what the daemon was preset too you go in and edit the files yourself. I first tested this before it was released on MIUI and it worked fine, look through and you'll find info on how to change the frequencies
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
CM7 kernel. I'm obviously not making myself clear, so I'll just figure it out myself. Thank you for your help, though.
Sent from my HTC Glacier
Is there a smartass version or one being worked on?
Sent from my HTC Glacier using XDA App
estallings15 said:
CM7 kernel. I'm obviously not making myself clear, so I'll just figure it out myself. Thank you for your help, though.
Sent from my HTC Glacier
Click to expand...
Click to collapse
OK I'll put it like this..
The daemon your flashing is preset, you have to go in the files and change them to what ever frequencies your kernel is set for if you want them to work for the minimum and maximum settings.
I can't make you understand it, I hope you figure it out but personally before I do anything that could potentially be harmful to my device I read everything I can find before doing anything to it.
jayb222 said:
Is there a smartass version or one being worked on?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
This is directly made from Virtuous Unity, the Governors associated are pretty much in every kernel release but the OP was mainly released for those interested in using the daemon it's self and it wasn't modified because there was no permission to do so.
Sorry about that though but I know Smokin isn't trying to step on any toes with this so that's why it remains as it was originally released.
Orical said:
change them to what ever frequencies your kernel is set for if you want them to work for the minimum and maximum settings.
Click to expand...
Click to collapse
That answered my question. Thanks buddy. I read the OP repeatedly and this isn't my first custom kernel or ROM. I crack flash like nobody's business. Drives my wife nuts. I'm no stranger to frequencies or voltages, but this is my first OC daemon. My confusion was in how specific the OP was in its frequency listing.
Sent from my HTC Glacier using XDA App
jayb222 said:
Is there a smartass version or one being worked on?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I edited the governor type file to smartass. Terminal output says smartass. Voila!
Sent from my HTC Glacier using XDA App
Just use the Viper app mentioned in the OP, it makes editing easier and much quicker, with a nice UI instead.
Ace42 said:
Just use the Viper app mentioned in the OP, it makes editing easier and much quicker, with a nice UI instead.
Click to expand...
Click to collapse
That's what I suggested before it was posted but I think it's important that people learn where all of the files are and how to edit the files and set the permissions for them.
Sent from my HTC Glacier using XDA App
I like the idea of this setup. It works well in Virtuous unity.
I know they have a GUI app that makes it easier to set this up. It would be great if we could get this daemon and GUI flashable for all ROMs.
The GUI app will probably need an auto detect CPU speeds function added for those that use custom kernels. Maybe we can talk to some of the overclock app devs (like the SetCPU dev) And see if we can get this functionality built into them.
It would be great if we could get this daemon in all ROMs and get the overclock app devs on board as well. As this app disables itself if there are overclock apps we would need them to be on board as those apps have so many other benefits (like profiles for low battery and the like) that I would hate to lose that as well. The apps could have the option to to enable or disable the daemon and then control it as well. The custom GUI app could be included in the ROMs for those that do not need or want to use the overclock apps.
I take no credit for this mod, just made it work for myself, thought I'd share it. rmk40 and viperboy are the ones that made it happen.
I used this OC daemon on my MT4G, it worked very well. Ive noticed that cpu tuning apps seem to not play well with our phones. So I changed the updater script to make this mod work for our phone. Im running it with Bullet 2.2 and Juggernaut 3.1 and its very smooth, it really works.
So what makes this mod cool? When you set a screen off profile in setcpu, it takes a few seconds for the changes to take effect when the screen goes off/on. With this daemon, its instant. Ive checked it with shell commands and it always changes min/max and the gov as it should. I will share the shell commands to get the available clock speeds and govs. for the kernel you are using, you have to manually set them.
The daemon is configured with 6 files in the folder /system/etc/virtuous_oc/.
There are 3 files for the wake state and 3 for the sleep state. For each state one file for the governor, one for the minimal frequency and one for the maximal frequency.
You can easily edit these files eg. with RootExplorer or any other app which can edit system files. So you can adjust the frequencies and the governor for each state just like with SetCPU.
In order to get the available frequencies for the current kernel, just open your favorite terminal app and type
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
You could also use adb shell to show the frequencies on your computer.
To get the available govenors use a similar approach
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
To make sure its working, you can use these commands the same as the ones above.
Current CPU frequency
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Current CPU governor
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Current min CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Current max CPU Freq
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
The kernel and ROM you are using have to support init.d scripts. As I said, Ive tested with Juggernaut 3.1 and bullet 2.2, the files are set by default at:
screen on gov-lagfree
screen on max-1620
screen on min-384
screen off gov-conservative
screen off max-540
screen off min-384
These are the available speeds and govs. for bullet 2.2
192000 384000 432000 486000 540000 594000 648000 702000 756000 810000 864000
918000 972000 1026000 1080000 1134000 1188000 1242000 1296000 1350000 1404000
1458000 1512000 1566000 1620000 1674000 1728000 1782000 1836000
conservative ondemand userspace powersave lagfree performance
Installation: Make sure you uninstall any CPU apps before flashing, or this won't work.
Boot into recovery, wipe dalvik, flash zip, reboot.
YOU CAN USE THIS APP TO CONTROL THE DAEMON. IT ALLOWS 3 OC PROFILES AND 2 UV PROFILES. WORKS VERY WELL! THANKS TO Killbynature FOR SHARING THIS!
*MAKE SURE YOUR ROM/KERNEL SUPPORT INIT.D!!!
Word......
I've been messing around with jugs 3 and if you just change screen on gov to ondemand, leaving all the other settings, it really runs smooth. I also learned that the app I linked in the op to control the daemon doesn't work on jugs.
Sent from my SGH-T989 using Tapatalk
Thank you!!!
I used this on my mt4g and was wondering when it would be available for
my sgs2.
if anyone else is considering giving this a shot, I strongly recommend doing so.
Get Root Explorer and get familiar with the text editor. This is a more natural, more efficient, and faster way to control your CPU.
Sent from my SGH-T989 using XDA App
I had the defaults jacked up in the first zip i posted. If you tried the mod, used default settings and had issues, try the new one. I was getting sod's because I had the sleep freq's backwards.
Thanks for this! Love OC Daemon! Much smoother than any app controlling the CPU. I'm currently on Juggernaut 3.7 with Faux's latest kernel. I'm trying out that new Daemon controller you linked on your fist page but UV doesn't seem to work. Faux said his kernel was capable of it. Are you undervolting using that app? If so, what kernel are you running right now?
---------- Post added at 09:16 AM ---------- Previous post was at 09:16 AM ----------
One more thing, I cannot believe this thread hasn't received more attention. Maybe most people here don't know what OC Daemon is?
App worked great on my Sensation, let's see on my S2. Thanks BTW.
I haven't been able to uv using the app. Not with any of the available kernels.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
I haven't been able to uv using the app. Not with any of the available kernels.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
If I manually type in terminal:
Code:
su
echo "-100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
it takes. It undervolts but that goes away as soon as I reboot. I then tried to add an UV script to the init.d folder but it wont work. The script is here, can you take a look and tell me if I'm missing something? Thanks.
setzer715 said:
If I manually type in terminal:
Code:
su
echo "-100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
it takes. It undervolts but that goes away as soon as I reboot. I then tried to add an UV script to the init.d folder but it wont work. The script is here, can you take a look and tell me if I'm missing something? Thanks.
Click to expand...
Click to collapse
the init.d script would need to look like this:
#!/system/bin/sh
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
and you cant uv in the app because it also needs a script. ill look into the proper script so that uv and oc can be contolled.
Will this work for synergy kernel?
Dfjcisnv
rmarquez1974 said:
Will this work for synergy kernel?
Dfjcisnv
Click to expand...
Click to collapse
Yes. Any custom kernel. With jugs you will have to manually edit the scripts because the app isn't compatible. But yea, any kernel
Sent from my HTC Glacier using Tapatalk
mikeyinid said:
the init.d script would need to look like this:
#!/system/bin/sh
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
and you cant uv in the app because it also needs a script. ill look into the proper script so that uv and oc can be contolled.
Click to expand...
Click to collapse
Yeah, that's how the script I used looks. I don't know what is wrong.
setzer715 said:
Yeah, that's how the script I used looks. I don't know what is wrong.
Click to expand...
Click to collapse
Are you rebooting after placing it in init.d?
Sent from my HTC Glacier using Tapatalk
mikeyinid said:
Are you rebooting after placing it in init.d?
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Yeah. Don't know why its not working. I'll keep plugging away.
Update: I just don't get it. If I go into root explorer and manually run the script it doesn't work. If I enter the script in terminal it works fine. All voltages are UV'd. Maybe I'll try removing Deamon and see what happens.
setzer715 said:
Yeah. Don't know why its not working. I'll keep plugging away.
Update: I just don't get it. If I go into root explorer and manually run the script it doesn't work. If I enter the script in terminal it works fine. All voltages are UV'd. Maybe I'll try removing Deamon and see what happens.
Click to expand...
Click to collapse
I'm running the UV script and the daemon and everything is working fine. I always add it to whatever rom I'm flashing so its there on first boot.
Sent from my SGH-T989 using Tapatalk
mikeyinid said:
I'm running the UV script and the daemon and everything is working fine. I always add it to whatever rom I'm flashing so its there on first boot.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
How did you verify it's working?
Code:
cat /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Does that show all voltages lower? How far are you undervolting?
Maybe I'll just try a whole new fresh install.
Well, I did what you said, added everything to the ROM. Wiped and reflashed, still not work. Can you post the script your using?
Also, what ROM are you on?
setzer715 said:
Well, I did what you said, added everything to the ROM. Wiped and reflashed, still not work. Can you post the script your using?
Also, what ROM are you on?
Click to expand...
Click to collapse
ill post the script im using. and this will work for any rom as long as the kernel supports init.d
just unzip the attached zip, the script is inside. also, i can tell its working by opening the app i have linked in the op and going to the voltage sections. it shows the current voltage for each freq. i would look what they are, add the script, reboot and look again. keep in mind the 18x freq "available" on the kernels wont be uv'd, so look at the next freq up to check.
Well I used your script and it worked. I made mine match yours and it was still a no go. Only difference between them is mine is -100000 instead of -75000. Maybe it just doesn't like -100000? Either way, thanks for your help. Now undervolted and OC'd using OC Daemon on Jugernaut 3.7 with Faux .006r2. Man this thing is smooth now!!!
how can i reduce screen resolution to 1080p ? on htc 10 with adb commands
I'm not sure why you want to do this, but do a search for changing DPI. There are a few threads and tutorials here on XDA.
xunholyx said:
I'm not sure why you want to do this, but do a search for changing DPI. There are a few threads and tutorials here on XDA.
Click to expand...
Click to collapse
thanks, i already do it
i want to do it to save more battery life
this true or not?
elawady.2014 said:
thanks, i already do it
i want to do it to save more battery life
this true or not?
Click to expand...
Click to collapse
Code:
su
wm size 1080x1920
wm density 417
for example. But I don't think it saves much battery.
RogerF81 said:
Code:
su
wm size 1080x1920
wm density 417
for example. But I don't think it saves much battery.
Click to expand...
Click to collapse
other questions, please
why CPU clock speed is 1500mh not 2200mh ??
I read in specs that snapdragon 820 clock speed is 2200mh
elawady.2014 said:
other questions, please
why CPU clock speed is 1500mh not 2200mh ??
I read in specs that snapdragon 820 clock speed is 2200mh
Click to expand...
Click to collapse
settings > developer options > high performance mode ~ turn it on
This will make a difference in battery life though.
xunholyx said:
settings > developer options > high performance mode ~ turn it on
This will make a difference in battery life though.
Click to expand...
Click to collapse
i do it but speed still in 1500 mh
ok thanks:fingers-crossed::fingers-crossed:
elawady.2014 said:
i do it but speed still in 1500 mh
ok thanks:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Well, it has nothing to do with high performance mode. But only the max frequencies of the little cluster are shown actually. This is due to Selinux security changes in Android 7. Change Selinux to permissive and the big cluster frequencies should be shown as well :good: