[SCRIPTS] OC/UV for DEVIL2, AGNI and Nadia kernels (V7, V8 for Nadia) [2014-07-19]

mohit141785

Senior Member
Mar 28, 2013
680
364
0
Just use smanager app from play store and see the instructions for using that app in the first page of this thread. And for draining part as I told you earlier wait for at least two complete charge and discharge cycles. As the changed values need time to settle down.
 

[email protected]

Senior Member
Dec 29, 2013
408
130
0
33
New Delhi
Bro I'm a bit confused, what do you mean by running scripts and which scripts and what voltage draining can you explain it a little more [emoji53]

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi
I meant to say 'Battery Drain'. Mistype. My bad.

For more understanding on 'running scripts', go through OP and first few posts thoroughly. It seems from your post that you do know how to 'run' a script. Don't you? :p
 

SLMI

Senior Member
Jan 31, 2012
199
22
0
26
Istanbul
I meant to say 'Battery Drain'. Mistype. My bad.

For more understanding on 'running scripts', go through OP and first few posts thoroughly. It seems from your post that you do know how to 'run' a script. Don't you? :p
Yes i do ?, but running which scripts nadia's own scripts or mat9's scripts

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi

---------- Post added at 05:58 PM ---------- Previous post was at 05:57 PM ----------

Just use smanager app from play store and see the instructions for using that app in the first page of this thread. And for draining part as I told you earlier wait for at least two complete charge and discharge cycles. As the changed values need time to settle down.
Thanks bro, trying to do ??

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi
 

Saluco

Senior Member
Dec 17, 2010
2,563
1,955
0
Constanta


I have Nadia kernel on Phoenix Rom and I flashed
Script_Nadia_OC_1800_666 - V8 - mid_UV script, but I noticed that the CPU frequency was not changed. So I used S manager (SU & BOOT ) and I run the script the way was instructed, all went good except that, as you can see in screenshot there's a folder missing or can't be created... Is that normal behavior?

Also, after reboot Synapse (kernel app control) always ask me if I want to save settings with cpu back to 1600 MHz.

I also flashed the ultrasmooth zip for 1800 and above
 

mat9v

Senior Member
Apr 3, 2010
1,879
1,151
143
Gdynia
I have Nadia kernel on Phoenix Rom and I flashed
Script_Nadia_OC_1800_666 - V8 - mid_UV script, but I noticed that the CPU frequency was not changed. So I used S manager (SU & BOOT ) and I run the script the way was instructed, all went good except that, as you can see in screenshot there's a folder missing or can't be created... Is that normal behavior?

Also, after reboot Synapse (kernel app control) always ask me if I want to save settings with cpu back to 1600 MHz.

I also flashed the ultrasmooth zip for 1800 and above
My script must be reflashed after every Nadia kernel flash because Nadia installs it's own scripts that locks cpu frequency.
Try reflashing my script. The output from running my script is perfectly fine, the existing error messages refer to the universal way that scheduler settings are applied (they are universal for various names of sdcard).
Please do not use Synapse or any other tool because they often override my script settings.
The question Synapse asks is normal, as far as I know, that is how it is supposed to work.
 
  • Like
Reactions: Saluco

[email protected]

Senior Member
Dec 29, 2013
408
130
0
33
New Delhi
@mat9v Mate, is there a way to check which frequency caused the phone to hang? 1800_666 Max UV seems to be working perfectly fine for me except some random hanging once in 2-3 days. I don't want to shift to high UV, just want to reduce the UVing of this particular frequency causing problem.

PS: Your Overvolted ABB values for your ASV1 were Undevolted values for my ASV2. I've changed the slice voltages to 900,1000,1000,1000 for further battery saving. Is it ok or should I use your ABB settings instead? ROM: Emotion V7.5; Kernel: Nadia r6.1.1
 

mat9v

Senior Member
Apr 3, 2010
1,879
1,151
143
Gdynia
One question, after removing Synapse, how can I enable touch to wake feature, cause the scripts seemed to disable it
No, the script does nothing to touch wake - I think it's disabled by default, and synapse is enabling it on every boot. What you can do is search your phone using root explorer or similar app for "touchwake" or "touch_wake" and when you find that you can add an entry to my script that configure the future.

@mat9v Mate, is there a way to check which frequency caused the phone to hang? 1800_666 Max UV seems to be working perfectly fine for me except some random hanging once in 2-3 days. I don't want to shift to high UV, just want to reduce the UVing of this particular frequency causing problem.

PS: Your Overvolted ABB values for your ASV1 were Undevolted values for my ASV2. I've changed the slice voltages to 900,1000,1000,1000 for further battery saving. Is it ok or should I use your ABB settings instead? ROM: Emotion V7.5; Kernel: Nadia r6.1.1
It's difficult to check because it strongly depends on what you are doing at the moment and on which core the calculations are being done. The same string of operations may hang the phone if it's on core2 while on core3 it went without problems. Even such simple change as outside temperature or if the cpu was mildly warm or hot during calculations may produce different results - that's how sensitive the configuration is when it's close to physical limits of cpu. That is if it's even cpu problem and not gpu :)
But to answer your question - the best way, even if it's not an easy way is to just change voltage values in the script:
the 1800_666 voltage table for Nadia kernel is like this:
"1375 1325 1300 1275 1200 1100 1050 1050 1025 1000 975 968 938 900 875 850 825 812 775"
you can change this by adding 12 to any of the values, try starting with the lowest voltages in groups of lets say... 3 values.
Save (remember to modify both entries in t99mat9v file) and reboot the phone or just re-run the script.
Test for a few days if that fixed the problem, if not - revert the changes and try with next 3 values - rinse and repeat until you find stable values.
Frankly, that's how I did it in the beginning :)
As to the ABB settings - please read back some of my posts in this thread (or if you are interested, all of my posts in this thread) to find the answer - the gist of it is that you should have high ABB values only up to 1200Mhz - above that it causes more energy loss than it saves, more than that it forces you to increase voltage supplied to transistor (those normal voltages defined above). So slices should be configured as they are in my nadia V8 scripts:

echo "300000" > /sys/devices/system/abb/arm/arm_slice_1_freq
echo "800" > /sys/devices/system/abb/arm/arm_slice_1_volt

echo "600000" > /sys/devices/system/abb/arm/arm_slice_2_freq
echo "1000" > /sys/devices/system/abb/arm/arm_slice_2_volt

echo "1200000" > /sys/devices/system/abb/arm/arm_slice_3_freq
echo "1100" > /sys/devices/system/abb/arm/arm_slice_3_volt

echo "9999999" > /sys/devices/system/abb/arm/arm_slice_4_freq
echo "750" > /sys/devices/system/abb/arm/arm_slice_4_volt

You can experiment, but remember to never increase ABB voltage above 1200mV (or you can damage your cpu) and the best practice is to keep ABB for high frequencies at 750mV (though you may experiment in setting it as low as 600mV).

Have fun and good battery life :)
 

[email protected]

Senior Member
Dec 29, 2013
408
130
0
33
New Delhi
No, the script does nothing to touch wake - I think it's disabled by default, and synapse is enabling it on every boot. What you can do is search your phone using root explorer or similar app for "touchwake" or "touch_wake" and when you find that you can add an entry to my script that configure the future.



It's difficult to check because it strongly depends on what you are doing at the moment and on which core the calculations are being done. The same string of operations may hang the phone if it's on core2 while on core3 it went without problems. Even such simple change as outside temperature or if the cpu was mildly warm or hot during calculations may produce different results - that's how sensitive the configuration is when it's close to physical limits of cpu. That is if it's even cpu problem and not gpu :)
But to answer your question - the best way, even if it's not an easy way is to just change voltage values in the script:
the 1800_666 voltage table for Nadia kernel is like this:
"1375 1325 1300 1275 1200 1100 1050 1050 1025 1000 975 968 938 900 875 850 825 812 775"
you can change this by adding 12 to any of the values, try starting with the lowest voltages in groups of lets say... 3 values.
Save (remember to modify both entries in t99mat9v file) and reboot the phone or just re-run the script.
Test for a few days if that fixed the problem, if not - revert the changes and try with next 3 values - rinse and repeat until you find stable values.
Frankly, that's how I did it in the beginning :)
As to the ABB settings - please read back some of my posts in this thread (or if you are interested, all of my posts in this thread) to find the answer - the gist of it is that you should have high ABB values only up to 1200Mhz - above that it causes more energy loss than it saves, more than that it forces you to increase voltage supplied to transistor (those normal voltages defined above). So slices should be configured as they are in my nadia V8 scripts:

echo "300000" > /sys/devices/system/abb/arm/arm_slice_1_freq
echo "800" > /sys/devices/system/abb/arm/arm_slice_1_volt

echo "600000" > /sys/devices/system/abb/arm/arm_slice_2_freq
echo "1000" > /sys/devices/system/abb/arm/arm_slice_2_volt

echo "1200000" > /sys/devices/system/abb/arm/arm_slice_3_freq
echo "1100" > /sys/devices/system/abb/arm/arm_slice_3_volt

echo "9999999" > /sys/devices/system/abb/arm/arm_slice_4_freq
echo "750" > /sys/devices/system/abb/arm/arm_slice_4_volt

You can experiment, but remember to never increase ABB voltage above 1200mV (or you can damage your cpu) and the best practice is to keep ABB for high frequencies at 750mV (though you may experiment in setting it as low as 600mV).

Have fun and good battery life :)
Thank a ton Mat! I'll try that.

About ABB, I only tried to gain from a post where it was said that default voltage for an ASV1 chip was 750mV while for ASV2 chip it was 1000mV; i.e. equal for all slices. But it occurred to me that low FBB in higher frequencies might be causing the problem with my settings. So I reduced those settings to 850 1000 1100 900. I'll see for a few days if that fixes my problem. If not, I'll try changing the voltage table as suggested by you. Thanks :)
 

J. Terrell

Senior Member
Mar 27, 2013
175
96
58
Red Bluff, CA
Strange. It's there for me, and I don't know why it shouldn't be there.
Can you please try rebooting, with the script removed before, and check again.
I removed the script, rebooted and now its there. I ran the script again and still got the unknown error 22. Forgive me if this is an ignorant question but could it be the file name? The script output says Dev/block/nvswap0 and in my files I have Dev/block/15:25 nvswap0.
 
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone