Develop Bugs

Vipers script

I am currently on CM 7 with Tiamats latest non sbc kernel and am considering trying out Vipers scripts to improve battery life, but in doing so, hoping to not negatively impact the performance. I don't know much about what settings to change once I have flashed the script and was hoping someone could suggest what changes I should make (if any are needed, does the script automatically change the default voltages?) I get a little nervous changing things when I don't really know what I am doing. Basically, please let me know what to change to get the best battery life possible without noticeably compromising performance.
Sent from my PC36100 using XDA App

yeha just flash -25mv at a time. and then if it gets laggy I would just get into recovery wiper dalvik/cache and then reflash the kernel. Then get into vipermod and flash the last stable undervolt value.

i lowered by 50 mv and my battery life has increased so much and i dont notice a performance change

Ok, just to clarify, am I choosing lower all voltages by 25mv per time, or just choosing to lower the max voltage 25mv per time. I guess I am not clear on that part. Also, do I need to reset these values each time I reboot my phone? Seems to me, my numbers reset after a reboot, does this make sense?

legasus233 said:
I am currently on CM 7 with Tiamats latest non sbc kernel and am considering trying out Vipers scripts to improve battery life, but in doing so, hoping to not negatively impact the performance. I don't know much about what settings to change once I have flashed the script and was hoping someone could suggest what changes I should make (if any are needed, does the script automatically change the default voltages?) I get a little nervous changing things when I don't really know what I am doing. Basically, please let me know what to change to get the best battery life possible without noticeably compromising performance.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
legasus233 said:
Ok, just to clarify, am I choosing lower all voltages by 25mv per time, or just choosing to lower the max voltage 25mv per time. I guess I am not clear on that part. Also, do I need to reset these values each time I reboot my phone? Seems to me, my numbers reset after a reboot, does this make sense?
Click to expand...
Click to collapse
Hello, glad to have another user. A few things... 1) We aren't that scary in the EVO thread, you can always ask questions there 2) If you go to my site, there is an FAQ that should explain everything you need to know. 3) You want to lower all voltages, that's the easiest way to do it. You can get more advanced and set custom values for min or max if you want. Your changes won't stick after a reboot unless you select "Save changes". I would recommend not doing that until you have played around with the phone after lowering voltages to make sure your phone is stable. What can happen is that if you lower them too much and save changes, you phone might run ok for a little bit and then freeze. Then, you will go into a never ending bootloop (solved by flashing the reset .zip on my site)
I hope this clears it up a little bit for you

Voltage control questions

I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks

Yes its safe just don't use the set on boot feature. As for battery improvement some people notice a difference and others don't I personally do undervolt. As for the guide just mess around with it for a while everyone Has different Preferences so results will always be different. I don't undervolt below 75 cause when I do I get lock ups. If you lock up just pull the battery and you'll be fine. I also recommend to use journaling ON cause if you lock up and pull the battery with journaling off you might get data corruption.
Hope this helps.
Sent from my SPH-D700 using XDA App

Yeah that helped but I really just don't know how to use it.

Led4lyf said:
I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks
Click to expand...
Click to collapse
What kernel are you on?
I'm on Twilight and can overclock to 1.3ghz with full stability. I don't undervolt. Combination of my phone doesn't like it and I'm not looking to save that little battery to get wakelocks (phone doesn't come out of sleep mode because the processor speed is too slow or doesn't have enough juice to make that push.)
If you're using a kernel that can go to 1.4 or 1.5 test it for a while before you save your settings. Also consider buying the paid version. It allows over volting which may allow you to supply enough power if 1.4 or 1.5 causes freezes.
The app is pretty basic. The top bar on the first screen is how low you allow the processor to go in speed. The bottom is how fast. Lower than 100 mhz causes wakelock for me. Or used to. Haven't tried since. My settings are 200-1300 mhz. Second page is voltages. They start at default. If you have extreme, moving them to the right will overvolt and give those speeds extra power. Moving the slider to the left undervolts. Some people can only undervolt at the lowest speeds of say 100-400 mhz. It's a lot of trial and error. Have fun though!

So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?

Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
It wont make it much faster
Sent from my SPH-D700 using XDA App

Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
When you turn your phone off then on, does it show those same settings? The speed boost will be slight. It's not like we're resurrecting Jesus here.

[Guide]Using OC/UV Beater for overclocking

This guide on how to use the OC/UV beater app that is used to control my overclock daemon that is included in some roms, and is flashable here for advanced users : http://forum.xda-developers.com/showpost.php?p=21253167&postcount=38 . If you cant find the app, unfortunately its not available in market but installable here: http://forum.xda-developers.com/showthread.php?t=1207546
First of all you need to make sure that any apps like setCpu or other overclocking apps are uninstalled not just disabled. Once this is done you need to reboot for it to take effect.
In the app you will normally have 3 tabs, these can be used to create different profiles. You can set a profile name if you like or just leave them.
You then have 6 dropdown menus for the overclock settings, 3 for each phone state. Your phone has 2 states, awake and asleep, asleep is when the phone is screen off and nothing too cpu consuming is running in the background and awake is for any other time. When you open the app for the first time the will say !set this is normal.
For each state you have a governor, min and max setting. When choosing a governor dont choose smartass as this does not work properly with the daemon (see below for why). Personally i use the normal on demand for awake and conservative for a asleep. Other governors can be used though depending on your preference.
Next you set your frequencies. Normally for minimum its safe to choose the lowest value unless you are having issues. As for the awake maximum choose what ever is the highest your phone runs stable at, or if you dont know, try out the one above your current speed. For asleep maximum either choose the minimum again or the one above (message to all kernel devs- try and enable a speed around 120mhz for maximum battery life).
Now we want to test these speeds out to see if they work, hit save, then temp activate. Now use your phone for a while, preferably trying a few intensive apps. When you are sure its stable use perm activate to set it on boot.
This should be enough for most people, but the app has a couple more features like profile switching based on battery state and ill leave you to work them out if you want as they are fairly self explanatory.
About the smartass governor: this governor was designed to switch maximum speeds based on phone state like screen on and off however the daemon does this for you if you set it correctly and will conflict with each other.

For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM

barzhdu said:
For some reason, I can't set anything except the govs (and they both show the same possibilities - there is no "conservative" for sleep) the rest just says !set and it's the only possibility there is.
Is it the app or is my problem ROM-specific?
Using TurboFire beta 6 ROM
Click to expand...
Click to collapse
Looks like its rom specific the app is rock solid normally. I think that the daemon config has gotten messed up in the mix of roms so ill try and see what is breaking it.

I cant seem to get the 460800mhz freq stable no matter what voltage i set. Is there a way to delete that crequency from ever being used, and how?

Works like a charm altho it seems the cm7 kernel does not support UV only OC or might be just me not understanding the UI. Antway i ll play around with it alot cuz so far it seems to ne runing alot better an utilising all freq properly.
Sent from my Wildfire S using xda app-developers app

[q] under voltage!?!

So i just flashed the new 'code name droid' ROM and its sweet but it also comes with a overclocked kernel up to 1350 mhz and the ability to under-volt. I've heard under-volting can save on battery so i want to try it out!
SO my first question is , what are the pros and cons of playing with voltage?
second, is the amount i can change the voltage determined by each individual kernal? if so what about this one?
AND THIRD what should i under-volt my phone to and why?
also if anyone wants to share what they have volted their phone at please share!
thanks alot!

The worst thing that could happen is that your phone will not boot. Then you have to reflash. Just decrease the voltage carefully. If you notice instability, you undervolted too much.

Let me quote myself from the franco kernel thread.
Nebucatnetzer said:
No I can't.
For all the guys around here which would like to undervolt but don't have a clue how to do it right.
(I don't adress this to you jhericurls).
1. Get and app like Franco's Kernel Updater or setCPU. Both of them are working.
You need as well an app called Stabilty Test
2. Go in to your CPU control app and lock the frequency at the lowest. In our case 350Mhz.
3. Now you go to the undervolting menu. Select 350Mhz.
(Make a backup of your current voltages. In setCPU you can find the option under the voltage tab and then press the menu button.)
The correct way to undervolt would now be to lower the voltage by one step of -25mV. For impatient people like me.
Yes it is possible to take bigger steps. At least in the beginning in the end you have to do it step by step to test it properly.
Important: Do not select the "set on boot" option.
4. Go to the Stability test app and run the Classic Stability Test for a couple of minutes.
I always make at minimum 3 CPU runs.
5. Now go back to your CPU control app. And lower the voltage one step more.
6. Repeat step 4 and 5 until the phone crashes and reboots. Now go back to the voltage tab and raise the voltage by one step.
This is now your lowest "stable" voltage for 350Mhz.
7. Repeat step 2-6 with the other frequencies. When you're finished lock your frequencies how you like them or how the were before.
I recommend you to run now the Scaling Stabilit Test for a couple of minutes. Just to be sure. Now you undervolted your CPU.
IMPORTANT: As long as you're testing you voltages, NEVER, select the "set on boot" option.
If one of your voltages is to low you can end up in endless bootloops.
I don't even select it afterwards until I'm sure they're working fine. Real world usage differs from testing.
So it can happen that your phone suddenly reboots even after the testing.
It this case I recommend you to raise all voltage on step.
If you think you found a bug in the kernel and you're undervolted.
DO NOT REPORT IT. Revert back to the stock voltages, reboot and test if the bug appears again.
Click to expand...
Click to collapse
1. It could cause some instabilities but hey you're flashing custom recoveries so that shouldn't bother you too much.
2. Some kernel are setting a minimal voltage it's like the deepest possible voltage. I don't know if any kernel for the GNEX is having this function.
3. No body can help you with your values since every phone is different. Maybe yours is very good so you can go deeper the most of us.

[Q] Overclock with SetCPU

Hi,
Would anyone be kind enough to list a step-by-step process on how to overclock the Note 8.0 using SetCPU? I'm a new user of this app and I'm afraid I may end up doing some irreparable damage to the device.
I am also just curious to see if I can squeeze some more gaming juice from the Note 8.0.
thanks in advance.

jnolaw said:
Hi,
Would anyone be kind enough to list a step-by-step process on how to overclock the Note 8.0 using SetCPU? I'm a new user of this app and I'm afraid I may end up doing some irreparable damage to the device.
I am also just curious to see if I can squeeze some more gaming juice from the Note 8.0.
thanks in advance.
Click to expand...
Click to collapse
I was going to post a link to a setCPU guide, but its no longer available
Id only push the CPU a little. In order to gain real gaming perfomance increases you need to push the GPU, but in order to do that you will need a kernel that supports it.
I only received my tablet last night and wont be rooting it until the weekend so cant say what settings ill be using yet. my aim is to attempt to overclock slightly and undervolt where I can...

You're not going to break it with SetCPU. If you overclock too much, the system will become unstable, then just back off. Also, the system will shut itself off well before any temperature possible of causing permanent damage was reached.
SetCPU has an option to create a recovery-flashable zip file, which resets the CPU settings to default. I would absolutely take this precaution, as I've had to resort to it on my old HTC Flyer tablet (became unstable, and bootlooped). As long as you select this option, you're pretty safe.
Other than that, just follow the basic rule of overclocking any computer, and push the clock up one or 2 increments at a time, then test for a few hours to see if the tablet is stable under various usage conditions. Repeat until you've either reached a desirable clock speed, or encounter instabilities.
Also, as you may already be aware, higher than "stock" CPU clock steps are normally not available unless you flash a custom kernel.

The trickster app supports GPU overclock on Civato's kernel.
If you're looking to push the GPU that's the way to go.

Thanks for the valuable inputs to all.

roustabout said:
The trickster app supports GPU overclock on Civato's kernel.
If you're looking to push the GPU that's the way to go.
Click to expand...
Click to collapse
Does the Trickster app allow for senario clock settings. Ie. underclock the CPU on screen off or if battery is bellow a certain percentage?
I may have to switch from setCPU to it if it has the same settings and more...